Indicate not working about rxandroidble HOT 6 CLOSED

For future references, I share my experience, because I didn't find a better thread related to this error.
GATT_CONN_TERMINATE_PEER_USER(19) also happens with bonded device if ... device forgot bonding, but Android OS doesn't know that.

Happened to me, costed few good hours to troubleshoot.
Long story short: I'm working on an app which communicates with custom hardware via BLE. I received new firmware and uploaded it to previously bonded device. App connects for a second and then immediately receives GATT_CONN_TERMINATE_PEER_USER(19). Rolling back to previous FW didn't help either. Searching in issue trackers wasn't fruitful. Somehow, I started to suspect that firmware manipulation was the root cause. Obviously, it's a bug - FW update shouldn't clear bonding status.

Solution: You have to 'unpair' device in bluetooth settings.

from rxandroidble.

Hello,

status 133 is a GATT_ERROR
status 19 if received from onConnectionStateChanged is GATT_CONN_TERMINATE_PEER_USER
That is according to: https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/android-5.1.0_r1/stack/include/gatt_api.h

Since I cannot recreate your problem it is quite hard to judge - it seems that the device you're connecting to drops the connection. Maybe it is possible to compare your framework and the RxAndroidBle to check out what is different in the framework and how you do use it?

Best Regards

from rxandroidble.

Hello, any news?

from rxandroidble.

No news. I have moved on from what I was doing with Android on to other things. Should I get back to evaluating RxAndroidBle I will dig more into it and provide an update. Thanks!

from rxandroidble.

@fracturedpsyche Did you eventually find out what was causing the disconnection with the error status 19?

from rxandroidble.

from rxandroidble.