Need to see a system log right after the crash. When the crash happens again, capture the log by going to Settings -> System -> View logs -> Share (or Save). Send the log file to my email: muhomorr@grapheneos.org or Discord: muhomorr_ (with underscore at the end).
Request for testing and feedback with Bluetooth on Android 14 QPR2 GrapheneOS
- Edited
Hi all,
hm, so this is strange. I still can't get the Pebble Time paired using the Gadgetbridge app though I can still pair it using the system preferences. With latest alpha release, of course.
BUT using the old, original Pebble app, it now works! 🥳
I used the Pebble app for initial configuration; but as it didn't work well with GrapheneOS 13 when I set everything up in autumn 2022 I deactivated it (but kept it). Now with current GrapheneOS the app seems to work well again and I'll keep it to the disadvantage of Gadgetbridge. Have to do a longer term test (fingers crossed).
Now it seems to me the problem is not the watch - but rather the Gadgetbridge app, maybe in conjunction with GrapheneOS?
I added my comment to their specific issue here: https://codeberg.org/Freeyourgadget/Gadgetbridge/issues/3596
Cheers
- Edited
@GrapheneOS Thank you, yes it was indeed a hardware error. I bought the phone to use GrapheneOS without trying stock Android. Bluetooth is broken on stock Android as well. Phone was returned. Thank you for all your work!
justanotheruser We'd need confirmation about how this goes for you on stock, as @emilycestmoi just confirmed it was a hardware issue in their case.
[deleted]
- Edited
Bluetooth tests with Pixel 5 on 2024032100 alpha release:
Garmin watch (2021) syncs fine through bluetooth with garmin connect app = WORKING
Polar watch (2020) syncs fine through bluetooth with Polar Flow app = WORKING
Polar bicycle computer (2015) syncs fine through bluetooth with Polar Flow app = WORKING
All worked fine before & after QPR2 .
matchboxbananasynergy Yes, broken on stock as well. However, there is another observation.
This issue occurs only when WLAN adaptor is switched on simultaneously (not with mobile data on or when WLAN is switched off) with Bluetooth. So, probably not purely a hardware issue and probably stems from the HAL.
However, for anyone else facing the same issue, check if the WIFI is switched off. It works then.
Hi guys, yesterday the update of 2024032100 landed on my phone. Did not have yet the opportunity to test it with my medical device just yet as I am on a journey.
However, I am able to report that this version somehow broke the internet sharing between 2 android phones via bluetooth (ie. not WiFi hotspot). Tested between Pixel 7 with GOS and Pixel 5 with LineageOS
doffactory Doesn't sound like an issue on the GrapheneOS end.
GrapheneOS the OBDlink Bluetooth device mentioned above is working for me now after recent update .
- Edited
@GrapheneOS Like the OBDLink I can confirm BlueDriver scan tool is working with the 2024032100 release.
Thanks for all devs' hard work!
I can also confirm that the Galaxy Watch 5 Pro works like before. Nothing I needed to change on my end. Just installed the Alpha and the watch was back on track.
Thanks a lot for that!
Pixel 7 Pro - beta channel 2024032100
Can confirm this update fixed my issues with OBFLink MX+
Thank you!
I can confirm both Watch 6 Classic and my Oppo running AsteroidOS are working properly, battery on the Samsung watch seems to drain a little faster than I expected, its seems to run the watch down faster than Wifi did, but it last me the day so I dont care at this point, good work GOS team.
Since this does not yet seem to have been reported yet:
With version 2024032100
on the Pixel 4a (5G) (updated via Beta release channel), the battery percentage of paired Bluetooth headphones is no longer shown (neither in the Bluetooth quick toggle nor in System Settings > Connected Devices).
Is this the currently expected behavior? And will the battery percentage display return in the next versions?
With the new version 2024040300
, the battery percentage of paired Bluetooth headphones is showing up again on the Pixel 4a (5G).
Locking this thread as enough time has passed and we don't think any future issues will be tied to this. New threads can be made as needed. Thank you all for helping us test.