ghost
commented
7 years ago Getting error 133 on Android in the process on testing connecting to a bonded device.
Interesting info on error 133:
https://github.com/NordicSemiconductor/Android-nRF-Toolbox/issues/9 https://github.com/NordicSemiconductor/Android-DFU-Library/issues/1 http://stackoverflow.com/questions/23762278/status-codes-132-and-133-from-ble112 https://devzone.nordicsemi.com/question/28473/error-on-writing-characteristic-133/ http://stackoverflow.com/questions/32070944/gatt-writedescriptor-error-status-callback-when-using-bonded-device https://github.com/NordicSemiconductor/Android-nRF-Toolbox/issues/9#issuecomment-132191406
List of error codes in the Android implementation:
Possibly helpful for error 133:
http://stackoverflow.com/questions/25330938/android-bluetoothgatt-status-133-register-callback http://stackoverflow.com/questions/28894111/android-ble-gatt-error133-on-connecting-to-device http://stackoverflow.com/questions/20839018/while-connecting-to-ble113-from-android-4-3-is-logging-client-registered-waiti/23478737#23478737 http://stackoverflow.com/questions/27280402/every-connection-request-is-being-treated-as-direct-connect-request-android-bl
Overview of BLE, lists Android issues on Slide 33:
http://www.slideshare.net/yeokm1/introduction-to-bluetooth-low-energy
Task is to implement support for bonding on Android and iOS.