Bluetooth device will not reconnect unless powered off, then back on after update to GOS 2024030900 #3315
Comments
|
GOS version: 2024030900 I'm having the same issue. Since 202403900 my bluetooth device will not reconnect if bluetooth connection is lost. Galaxy Watch 5. I have to reset the watch and re-pair again and it'll work until the connection is broken. Looks like its constantly trying to reconnect. Tried resetting bluetooth with sane results. |
|
GOS version: 2024030900 Pretty much exact same issue as @jsea76 has: Devices loses connection after a long period of time and doesn't want to reconnect. Resetting and repairing the watch only works for a few hours until it loses connection and doesn't want to connect again. EDIT: A similar thing happens when my phone tries to connect to my PC over bluetooth, which I use for Windows Phone Link. |
|
GOS version: 2024030900 Same behavior as @bleuthoot-sven reported, following error is reported in logcat: |
|
@ionspin This appears to indicate that the device done not properly implement encryption and Android 14 QPR2 Bluetooth security fixes break it. Can you update the watch? |
|
Sorry. I was traveling and not able to get a log until now. These lines repeat themselves constantly while it tries to reconnect. Only stopping when bluetooth is off or the device is forgotten. 2024-03-12 16:17:19.155 2403 2505 com.android.bluetooth W btm_acl: packages/modules/Bluetooth/system/stack/acl/btm_acl.cc:1149 - BTM_SetLinkSuperTout: Role is peripheral so unable to set supervision timeout:80.00ms bd_addr:xx:xx:xx:xx:b8:95 |
@thestinger I've checked, the watch (at least Watch 4) is already at the latest version. Also the fact that it can pair and work for some time before failing is suspicious. I saw that GrapheneOS tag 2024030800 contained a Bluetooth related fix, but it was for Bluetooth LE, and the issue here seems to be Bluetooth Classic. I'll try to follow the source from the logs and get a cleaner picture Is there a list of Bluetooth security fixes that are in QPR2? That might give some additional pointers. |
|
I have the same issue with my ticwatch pro 5. A re-connection cannot be made after the connection has been disconnected once |
|
These are likely buggy devices broken with Android 14 QPR2. Need to test them with stock OS. |
|
Just a quick update after testing with Steps I took to reproduce:
Logcat with filter |
|
I have same experience with a galaxy watch 5 and also on beta 2024031400 |
|
I have the same issue. Also with Galaxy Watch 5 on 2024031400. |
|
I can confirm that 2024032100 solves the issue for Pixel 7A and Galaxy 4 watch, I'll test with Galaxy 5 a bit later and confirm if that works as well. Thanks for getting the Galaxy Watch for your developers and fixing this, I'll make sure to donate to GrapheneOS. |
|
Latest release (https://grapheneos.org/releases#2024032100) should fix this. If people are still experiencing issues, it might make sense to make a new issue. |
|
Confirmed my headset now reconnects properly in all scenarios I could think of. |
Problem
As of 2024030900, my Willful M98 bluetooth headset will not auto-reconnect in the following two scenarios, meaning the only working method for reconnecting is to power the headset off, then back on.
Previously tapping the headset from
Settings > Connected deviceswould reconnect the headset.The current (broken) behavior displayed on-screen is (1) tap the headset entry from
Settings > Connected devices, (2) the headset is briefly moved (~100ms) toConnected devices, then is removed and placed back underSaved devices.It wants to connect, but something in this update is preventing it. All previous GOS system OS updates worked fine.
What I've tried to fix
The text was updated successfully, but these errors were encountered: