Open KarolMB opened 6 years ago
Hello @Esperanz0
I see a status=133
in your Actual result
. Why do you think it is a problem with the library?
@dariuszseweryn Hi.
When I will kill app and run it again its working so I thought it is something with library.
So if it is no library problem do You have idea how to check where is problem / what failing after bt off/on.
Try scanning the device after adapter off/on
Actually this question should go to the stackoverflow as this is a general usage question or rather an Android BLE stack quirk. Not an issue with the library
Hi @uKL, I saw you added this issue into the 2.0.0
milestone. Is there anything you guys can do from the library side?
I was investigating the issue more deeply recently but unfortunately there is no good solution for the current state of the OS. I will probably create a blog post about the issue
(Android stack flaw description by @dariuszseweryn)
Android uses 48 bits to "uniquely" identify a device. If the device is obtained solely on providing the "unique" mac address or it was scanned before the
BluetoothAdapter
was turned on the last time the stack does not know if the address ispublic
or not until the device is scanned again.Library version
1.4.2
Steps to reproduce actual result
1. Connect with BLE device.
2. Turn off bluetooth on the phone
3. Turn on bluetooth
4. Try to connect again with the same BLE device
Minimum code snippet reproducing the issue
Logs from the application running with setting
Actual result
Expected result
RxAndroidBle will connect to the device after bluetooth off/on.