Panda-na I dont have wired headphones or a dongle unfortunately, and being tethered to the phone would be a pain in the backside, I use Bluetooth almost exclusivly and I switch back and forth from my phone to a PC, depending on if its a phone call or a Teams call, path of least resistance is to dust of the iPhone until the issue is resolved.
Request for testing and feedback with Bluetooth on Android 14 QPR2 GrapheneOS
hainguyenhoang
Well, even after several manual disconnects/reconnects, turning off/on Bluetooth on both devices, and rebooting both devices, I cannot reproduce the same issue on stock OS, build AP1A.240305.019.A1
- Edited
emacsomancer I have this same issue with my Pebble Time and my Pixel 7 after the QPR2 update. I also have a pebble2 HR which does pair and work just fine weirdly. I have not tested with the stock Pixel 7 QPR2 update, only with GrapheneOS since I don't want to reflash my phone right now.
There's a sortof similar issue posted on the gadgetbridge gitlab https://codeberg.org/Freeyourgadget/Gadgetbridge/issues/3596 . Unconfirmed if it's related or not though.
If I turn off my Watch6 my other devices appear to work properly. If my Watch6 is on nothing will work correctly, including the Watch6.
xaz2fiaghi After some more experimenting the best way to describe my Pebble 2 HR connection with gadgetbridge is "unstable". I can pair it, which takes a few tries. Then if I put the pebble in airplane mode or go out of range for a while, I have to try to pair again which requires tapping the pair button on the android pair dialog popup several times but it eventually does connect again. Happy to provide logs if that's helpful.
Still using my pixel 6a with Sw build: 2024030900
A Galaxy Watch 6 update released today.
But I have still the same failure.
I just reverted to stock Android and I can confirm that galaxy watch works properly again. Pixel 7a.
That's great to hear. Has anyone heard if GOS will be fixing this or are smart watches on the back burner for the time being?
xaz2fiaghi How are you getting it to pair? Are you removing and re-adding it to Gadgetbridge?
ECU Connect - Ecutek app not working on latest Bluetooth update. OBD interface not connecting via Pixel 7 Bluetooth. Was working seamlessly before update.
Ive had to disable Bluetooth completely now, anything like my Watch trying to constantly connect is causing battery drain, my watch went from 2 day battery life to 8hrs, phone was also discharging quicker, once I disabled bluetooth, everything was back to normal.
Build: 2024030900
Phone: Pixel 7 Pro
Apple Airpods (Gen 2) are still working, but sometimes initial connection has issues. It will say there was a device error. Usually resolves on its own or by restarting Bluetooth.
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.
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.