Request for testing and feedback with Bluetooth on Android 14 QPR2 GrapheneOS

p5a on 2024031100 as of today, and before updating I noticed its behavior with BT had changed: there isn't a BT icon at the upper right of the screen after clicking "Show all devices / Bluetooth will turn on." In the home-screen pull-down the Bluetooth oval is illuminated but the phone will not connect to just one of my two UE Boom 2s. The other is fine, everything proceeds normally. I have had the "Notify about system process crashes" on since I loaded GrapheneOS on this phone, and have had none. 2024031100 did nothing to modify the behavior.

My p8 gets in touch with either of the Boom 2s quickly and reliably.

User321795

I figured this would be the case as I haven't seen much of any complaining doing Google searches.

Steve868686 I also got the galaxy watch update. I factory reset the watch. Sure enough, it initially pairs normally, but as soon as it disconnect, it won't connect back, draining both the watch and phone battery.

pinpin Could you please provide logs for this?

Hilarious, I go in and disable all updates in the GOS App, and I pick my phone up 4hrs later: Your system has been updated, please reboot.....

If this update fixes my bluetooth, I will be restricting updating on my phone on a network level as apparently, the switches dont work in the app, I would prefer that any updates on my device are only done with my explicit consent, I prefer to review the change log and wait 7 days before I initiate any updates, Ive had to do this my Winblows machines as they boarderline on malware with the updating of crap in the back ground, not to mention the auto reboots and in some cases breaking things on me.

NXG-3D How did you try to disable the updater?

These are the steps: https://grapheneos.org/usage#updates-disabling

If you did anything else, it would make sense why you updated.

Also, I shouldn't need to explain that staying behind in updates is a really bad idea. People can do whatever they wish at the end of the day, it's their devices, but we are not able to provide support for people who aren't using the latest version of the OS, and if you fall behind, things you may not expect to break can break. Staying on an outdated version and falling behind in security patches isn't the way to go here.

I really think there should be a roll back update feature, as I would have smashed that button on the first sign of trouble.

Bluetooth is still FUBAR I can now connect my headphones or my Watch, but not both, the Watch gets booted as soon as I connect my headphones, then I need to reboot both watch and phone and it will connect again, then I connect my headphones and the watch gets kicked...again.

matchboxbananasynergy I understand all that, but I prefer to trail, for reasons like this, I did the same with my iPhone, I usually hold off and see if any issues arise.

Waiting a week will not compromise my security and should not cause any issues, Im one that only seeks help after an update breaks my crap, or some horrible company removes a feature I had on my device with an "firmware update" for my "security" if get my meaning.

Having a roll back update button would be nice for quick diagnostics.

emacsomancer For the Pebble 2 HR no I am re-adding it but not removing it. Gadgetbridge lets you pair devices that are already "cards" in the device list. So I just go to add device, select the device again, go through the whole pairing dance I described before, and it eventually connects using the same card so I don't lose any data.

I just tried after tonight's update and I didn't have to go through the re-pair dance though, the P2HR just connected on boot like it's suppose to. I haven't tested the Pebble Time yet though.

xaz2fiaghi Yes I have somewhat similar results with my gear, Ive just disabled Bluetooth for now as its causing some series battery drain issues.

Are there any updates to this problem? Are the dev's aware/working on it? It seems like they pushed the blame to the android os update being the issue, but I can't seem to find anyone who has that issue on the stock OS. (In fact, someone above posted they went back to stock and their watch works now).

I don't mind waiting a week or two because I get this takes time. If its not even on the radar to fix, I may be flashing back to stock to prevent my watch being a $600 paperweight.

Psymos
This is how I feel as well. It would be good to at least hear something about it being on the radar. I guess I'll wait a couple more days and if Bluetooth is still broken will have to flash stock, buy a couple Titan keys. Having a phone with malfunctioning Bluetooth is a whole level beyond having a few broken apps.

emacsomancer is it possible to use Gadgetbridge with Samsung Watch6? I didn't think that was supported.

Psymos p0well34 It appears the issue that most people had with Bluetooth because of an upstream bug was already fixed. See this post: https://discuss.grapheneos.org/d/11383-request-for-testing-and-feedback-with-bluetooth-on-android-14-qpr2-grapheneos/24. Make sure you have updated your phone to the latest version and try again.

If a Bluetooth device isn't working after updating, then see this post by the project account: https://discuss.grapheneos.org/d/11383-request-for-testing-and-feedback-with-bluetooth-on-android-14-qpr2-grapheneos/43

other8026
Thanks for replying. The first topic you posted refers to Galaxy Buds not a watch. The second was before users reported that their devices worked with the watch after flashing the stock image. Just looking for a solution none the less.

I did receive an email telling me that i wouldn't get anymore replies to this discussion until i was up to date. Aren't the updates anonymous? What makes you think I personally am not up to date? Just curious why I wouldn't be able to take part of this discussion while looking for a solution? I hope I'm not being reprimanded for being a part of this discussion. Thank you

p0well34 I think what they meant was that someone who previously had an issue with Bluetooth connectivity confirmed that the latest release fixed the problem. I also had a device that wasn't connecting and started working after the update. The update wasn't just to fix headphones, it was to fix a bug in upstream AOSP code.

I now know of 3 people who are reporting issues with their Samsung watches. One person posted logs, but I didn't see anything in the logs. I just checked the listing on Google Play and it looks like multiple people are complaining about the same problem that you're reporting. So, it appears the issue might be affecting people with the Stock OS too if they've updated to a post QPR2 release.

Seems there's a misunderstanding about something here. Locking while I explain.