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

xaz2fiaghi

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.

emacsomancer

xaz2fiaghi How are you getting it to pair? Are you removing and re-adding it to Gadgetbridge?

Steve868686

Still using my pixel 6a with Sw build: 2024030900

A Galaxy Watch 6 update released today.
But I have still the same failure.

pinpin

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.

User321795

I just reverted to stock Android and I can confirm that galaxy watch works properly again. Pixel 7a.

p0well34

User321795

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?

Psymos

User321795

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

matchboxbananasynergy

User321795 When you reverted to stock OS, did you confirm that this was on the Android 14 QPR2 release of stock OS?

xaz2fiaghi

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

emacsomancer Situation has not changed with the Pebble Time. If I reboot both the watch and the phone and attempt to pair the Pebble Time I can get a pairing dialog on the watch and the phone, accepting both results in the little happy heart symbol on the watch but gadgetbridge enters a neverending spinning cycle of trying to connect. It is not able to even after a restart.

carlD

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

Fakeemail123

ECU Connect - Ecutek app not working on latest Bluetooth update. OBD interface not connecting via Pixel 7 Bluetooth. Was working seamlessly before update.

NXG-3D

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.

vontroxler

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.

jet_silver

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.

matchboxbananasynergy

pinpin Could you please provide logs for this?

NXG-3D

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.

matchboxbananasynergy

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.

matchboxbananasynergy

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.

NXG-3D

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.

NXG-3D

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.

GrapheneOS

NXG-3D

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

That's not possible. The data was migrated to the new version and won't work with the old version anymore.

It would also be insecure. It would require disabling verified boot and update downgrade protection. That's not going to happen. We don't disable standard Android security features, it's not the kind of project it is.

NXG-3D

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

« Previous Page Next Page »