Workaround for hung service discovery Android bug about rxandroidble HOT 6 CLOSED

Even when I try to disconnect later it's queued but not proceeded (i.e. when I unsubscribe from connection subscription I see in logs RxBle#Radio: QUEUED RxBleRadioOperationDisconnect(237327482) and then silence - it's not proceeded).

from rxandroidble.

It (of course :)) seems to be some kind of problem with BT on Android itself as it does not occur always. And sometimes it may be fixed but switching off/on BT. Sometimes I have to reset whole device.

from rxandroidble.

Could you share more info about this issue? Do you connect to a device that is changing it's services or something?

from rxandroidble.

Do you connect to a device that is changing it's services or something? No, the device I am connecting to definitly does not change its services. It seems that I was so long messing around with BLE on my Moto G that it was the time when nothing works and you have to restart BT or restart Moto G. After 2 years working with BLE in Android I can tell that it happens every once in a while (especially when you make some stress tests and connect/disconnect to multiple devices very frequently). But it would be nice to have at least some way to try to solve this issue.

from rxandroidble.

Or at least to warn the programmer like SweetBlue does with its UhOhListener:

The native stack's bluetooth service can sometimes get into states where it can't be turned on, or even can't be turned off. SweetBlue cannot fix this, but is does detect and report this issue through UhOhListener. Usually this means a phone restart is required.

Just an idea (that unfortunately can't be translated directly).

from rxandroidble.

Long time no see.
The hanging discovery issue should be fixed (+ a workaround) #86

UhOh is a totally different topic.

Best Regards

from rxandroidble.