I do not understand this behavior at all but I have noted on the same set
of devices as I have moved from OS 4.3 to 6.0 that discovery of Bluetooth
Low Energy devices using the 'settings/bluetooth' option is progressively
worse. In 5.1 and 6.0 it is so bad that there are certain devices I do not
Anything with Error 133 gives useless information. First, are the other two
devices pairable (require security/encryption) or is it just the custom
device? If it is the former I have found that on Android 5+ there is a bug
where one is allowed to try to read or write characteristics that require
James,
This sounds weird. PINs were only used in classic Bluetooth as far as I
know and have since been replaced with SSP. I don't think iOS can do
classic Bluetooth so I would expect your are being requested to enter an
SSP passcode exposed by a peer device in BTLE. In that case a 6-digit
num
Welcome to the club of those who have no idea. 129 has the description
'Gatt Internal error' which means Android has no idea either. Something
didn't work. Another error code which is equally as obscure and useless is
133 'Gatt error'. I guess the only difference is that with 129 something
mess
4 matches
Mail list logo
