Martijn van Welie

What I see in the code of RxAndroidBle is that only close() is called. That unregisters your callback so you will never receive the disconnected event! This is not an...

@dariuszseweryn , I'll do some tests as well. But assuming you are right, I suspect the issue is related to the asynchronous nature of connectGatt, disconnect and close...if you call...

Ok, I just did a small test: ``` 2019-04-01 17:07:34.571 24229-24229/com.welie.blessedexample I/BluetoothPeripheral: connect to 'Systo MC 300' (CF:A9:BA:D9:62:9E) using TRANSPORT_LE 2019-04-01 17:07:34.572 24229-24229/com.welie.blessedexample D/BluetoothGatt: connect() - device: CF:A9:BA:D9:62:9E, auto: false...

Here is another test on a Samsung S5 running Android 6 ``` 04-01 17:48:42.736 13112-13112/com.welie.blessedexample I/BluetoothPeripheral: connect to 'Systo MC 300' (CF:A9:BA:D9:62:9E) using TRANSPORT_LE 04-01 17:48:42.736 13112-13112/com.welie.blessedexample D/BluetoothGatt: connect() -...

The Battery Service and its characteristics are hidden by the battery plugin that is loaded at startup of bluetoothd. You can simply tell bluetoothd to not load the battery plugin...

Hmmm, I have never ever seen this. It doesn't make much sense if `bluetoothGatt` ever was null....because then I wouldn't be able to do any additional gatt operations... The only...

Another question, does it happen when you are doing a connect? Or when a disconnect happens? Can't see it from the logs...

I have been checking the code and I see a possible improvement in my code. I will add another check in the method `startConnectionTimer` and some other methods to make...

Released 2.2.3 Please check if this fixes your issue

Any update? Does the new release fix the issue?