Pebble watch Bluetooth pairing loop after Android 14 QPR2
Basic info
- Device: FP4, Pixel 6 series, probably all devices
- CalyxOS version: 5.5.2 (build AP1A.240305.019.A1.24505020)
Brief description of the issue
Since the middle of March (I believe now two updates ago) Bluetooth connectivity to some of my Pebble smartwatches has stopped working - I would be prompted to (re-)pair the watch when attempting to connect to it even though it was already paired, and completing the pairing process doesn't actually connect the device - the watch reports a successful connection, but my phone immediately disconnects and after approx. 15 seconds pops up another pairing dialogue. This continues ad infinitum if pairing is not cancelled, but the connection is never made. I've asked around in the Rebble Discord server and they note various issues with Android 14, but this Bluetooth issue appears specific to the phone OS (some suspect tweaks to BT security) as nothing has changed on the watch side.
Steps to reproduce
- Install (now via ADB due to outdated SDK) Pebble app and open it.
- Add a new watch, selecting the relevant model (I've had this issue with Time and Time Steel.)
- Observe that the watch is seen in the app and in Android Bluetooth settings (two listings, one for BLE.)
- Attempt to pair, confirming the PIN matches on both devices.
- Pairing completes on both sides but the phone does not connect to the watch.
- After approximately 15-20 seconds the pairing process repeats unsuccessfully until cancelled.
Reproducing this exactly would require access to a working Pebble device which may be a tall order these days. I know two other users in the Rebble Discord server have encountered the same issue - one is another CalyxOS user, while the other uses GrapheneOS.
Expected result
Phone running CalyxOS should pair to the smartwatch as before.
Actual result
Bluetooth listings for watches are present in the settings but when used do not make a connection - attempting to connect just starts the loop.
Attempting a connection with the Gadgetbridge app rather than the Pebble one provides a pop-up noting 'Bonding to [BT address] failed immediately.'
Logs (if available, they make fixing much easier)
(Logs can contain sensitive info, you can also email to [bugreports@calyxos.org](mailto:bugreports@calyxos.org) - please mention
your gitlab username and some details about the issue)
(If there are Bluetooth specific logs, I'm happy to provide them - just advise me how to generate them.)
Any other info
Pebble is EOL and only community supported by the wonderful folks at Rebble - it remains my favourite smartwatch but I'm not blind to the fact they will eventually become unserviceable as time moves forward. If this issue is caused by new security measures and/or deprecation of older features then I'll know it's time to move on; if whatever changed is optional/configurable however I'd love to get to the bottom of it.