Expected
For creating a connection, I am using method connect() with autoConnect flag set to true. This is setup once and it is expected that after setting up this "autoConnect", there is no other action required and Android OS BLE stack will notify the app, once remote device becomes available, and this call will never time out.
Actual
Sometimes, I can reproduce following behavior:
App is capable of connecting to device, but when app attempts to write bytes, it results in following exception: "BluetoothGatt: android.os.DeadObjectException"
To Reproduce
Steps to reproduce the behavior:
call connect method with autoConnect flag set to true
Wait a few hours
After reconnection, writing to device will always result in "BluetoothGatt: android.os.DeadObjectException"
Note: Even restarting the BT module will not solve the issue. What will solve the issue is reinitialising BlueFalcon library.
Smartphone (please complete the following information):
Expected For creating a connection, I am using method connect() with autoConnect flag set to true. This is setup once and it is expected that after setting up this "autoConnect", there is no other action required and Android OS BLE stack will notify the app, once remote device becomes available, and this call will never time out.
Actual Sometimes, I can reproduce following behavior: App is capable of connecting to device, but when app attempts to write bytes, it results in following exception: "BluetoothGatt: android.os.DeadObjectException"
To Reproduce Steps to reproduce the behavior:
Note: Even restarting the BT module will not solve the issue. What will solve the issue is reinitialising BlueFalcon library.
Smartphone (please complete the following information):