Google Pixel 5 loses bonding info after BT adapter cycle about rxandroidble

[dariuszseweryn]

Hello, two questions:

• is your peripheral bonded?
• does your app scan the peripheral before trying to connect?

I guess that to both questions the answer is: no. There is a (pretty outdated, but still valid) wiki section about this problem.

[dariuszseweryn]

Closing due to lack of information and inactivity of the original poster.

When more data will be available—feel free to add that information and reopen this issue.

Best Regards

[neowhoru]

Hello Darius,
sorry i just was out of order a bit.
I will try to answer:

Hello, two questions:

* is your peripheral bonded?

* does your app scan the peripheral before trying to connect?

I guess that to both questions the answer is: no. There is a (pretty outdated, but still valid) wiki section about this problem.

Yep it was bounded before and normally it does a scan but not on devices that are "already bounded".
However we found out its not an issue with RxAndroidBle - its an issue with the Android Ble Stack and the Google Pixel 5.

Also you don't need to wait 2 days.

To reproduce the issue:

• bound a device with your custom app as usual
• on your google pixel 5 disable bluetooth and re-enable it
• your bounded devices is no longer in the "bounded" device list and not bounded anymore

We don't know why and we don't know which devices this occurs but on Samungs devices for example same app same device works pretty well.

I just post here for the guys who might search for the same :)

[dariuszseweryn]

Good that you've pinpointed the issue. You may probably workaround it by always scanning your peripheral before attempting to connect.