this post was submitted on 23 Mar 2024
35 points (97.3% liked)

GrapheneOS [Unofficial]

1713 readers
1 users here now

Welcome to the GrapheneOS (Unofficial) community

This feed is currently only used for announcements and news.

Official support available on our forum and matrix chat rooms

GrapheneOS is a privacy and security focused mobile OS with Android app compatibility.

Links

More Site links

Social Media

This is a community based around the GrapheneOS projects including the hardened Android Open Source Project fork, Auditor, AttestationServer, the hardened malloc implementation and other projects.

founded 3 years ago
MODERATORS
 

Our latest release has been confirmed to resolve Android 14 QPR2 Bluetooth module issues causing connectivity issues with 5th/6th generation Galaxy Watch devices. 2nd set of upstream Bluetooth bugs we've fixed this month. Please provide feedback here:

https://discuss.grapheneos.org/d/11383-request-for-testing-and-feedback-with-bluetooth-on-android-14-qpr2-grapheneos

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 7 months ago (3 children)

The update did not fix the issue for me. Using a Pixel 6a with Graphene OS and a Samsung Galaxy Watch 5 Pro. The watch had been working just fine with Graphene OS until the recent OS changes.

Since the most recent update, nothing really improved. The watch had to be factory reset in order to get it to connect the the phone via Bluetooth. That worked for less than 5 hours and it lost connection to the phone and would not reconnect.

Still the only way to get it to reconnect it to factory reset the watch and re-pair it to the phone. Since that connection still only lasts less than 5 hours (sometimes on an hour or so), I'm tired of doing that and have quit wearing the watch.

[–] [email protected] 2 points 7 months ago (2 children)

Sorry to see that are experiencing this. Sounds like a problem with the watch itself, since you have to reset the watch to fix the problem. Hopefully the manufacture of the watch fixes this issue soon.

[–] [email protected] 2 points 7 months ago (1 children)

Doubt it is a watch issue, only started when the Bluetooth bug started with Graphene OS