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.
We're currently working on the Wi-Fi hotspot after factory reset issue. We can't yet replicate any of the other Bluetooth issues. We need clear information on which device model, GrapheneOS version and Bluetooth peripheral any remaining issues occur with and people also ideally need to test the stock OS release of QPR2. It's not helpful to test the stock OS QPR1 release. We need more complete info about the peripherals which still have issues. Also, if the peripheral is tied to an app, please try exploit protection compatibility mode for that app.
Apologies in advance for limited info, but want to contribute that I'm seeing a similar situation where I can no longer connect to OBDLink LX car adapter using OBDLink app over bluetooth (not BLE). Pairing appears to be fine, but the app struggles to connect - sometimes (maybe 1 out of 10 attempts) it does connect, but the vast majority of times it cannot.
This is similar to what "topro" is experiencing (similar adapter).
As you suggested above, I tried enabling "exploit protection compatibility mode" but it didn't seem to make a difference in my case.
Other info: device=pixel 5A, build 2024031100.
Pixel 6
Watch 5 Pro
compatibility mode doesn't work.
Galaxy Watch uses Samsung Watch Manager App
Google says It should work and to consider taking my phone to a repair center and contact Samsung.
I'm talking to Samsung as I'm typing this. They have heard no one say that their Watch was not connecting after QPR2.
They are now telling me to call Pixel support because something is wrong with my phone.
Balance3767 verified the watch works on stock with QPR2 not QPR1.
hopefully if there's more info needed he can offer it since he's already flashed stock.
So the Galaxy Watch 6 uses the Galaxy Wear app, which uses another application called Galaxy Watch6 Plugin. I suspected the latter was at fault as it was updated on March 5th. I downgraded the plugin app to a the November 2023 version and tried to factory reset the watch.
I ended up with the exact same problem. Initial pairing works fine, but if I go in airplane mode, it doesn't connect back nor will any devices connect to the phone until I turn off Bluetooth on the watch.
Disabling exploit protection has no effect either.
It used to work fine before the qpr2 grapheneos update. Did not test/flash back pixel os to test.
Just to let you guys know my watch is getting an update right now. Fingers crossed...
No Dice
Are there issues with anything other than Galaxy watches which are confirmed to not happen on QPR2 stock OS?
GrapheneOS
Devices:
Pebble 2 HR (multiple pair dialogs even when it's already paired but eventually does connect)
Pebble Time (repeatedly moves between saved devices and other devices, does not ever successfully connect, and now I can't seem to pair it at all)
Gadgetbridge for managing the wearables, exploit protection compatibility mode is enabled, though it didn't make any difference.
GrapheneOS build number (I think? there's no real clear version but I've never looked for it before): 2024031100
I only have one phone and I rely on it so unfortunately I can't reset to the stock OS right now.
EDIT: Forgot to mention that both worked until the above mentioned QPR2 update, or at least they worked until a few updates ago which is when I found this thread. There's been an update every day or two since but the situation has not improved.
GrapheneOS I can confirm after the GOS update yesterday, the follow devices all connect and disconnect properly and they can all connect at the same time:
Apologies on the them of two's :) only just noticed that.
But my Galaxy Watch6 Classic will not connect at all.
GrapheneOS as I reported 4 days ago my OBDLink MX+ (non-BLE) will pair but refuse to connect to Pixel 8 on GrapheneOS since 2024030800. The update next day did not improve on that. Socket.connect() takes some time, then returns:
Connection failed: read failed, socket might closed or timeout, read ret: ‑1
Testing on a Pixel 8 Pro with latest QPR2 stock (version details mentioned above) works flawlessly.
There has been a similar report yesterday of someone describing the exact same behavior on an older Pixel device and a similar OBDLink non-BLE device, just some posts above.
I forgot to state the build: 2024031100
GrapheneOS Yes, as described earlier, a medical device (Accu-Check Insight), I am unsure the exact Bluetooth version it uses but the device was released around 2015 so certainly non-BLE
Need to see a system log. To capture it, try to connect to the affected Bluetooth device again, then go to Settings -> System -> View logs -> Share (or Save). Send the log file to one of the following places:
doffactory It was captured on a previous OS version. Need to see log from the current OS version.
muhomorr will do as soon as the latest update arrives
muhomorr I disabled developer settings, enabled "Notify about system process crashes", forgot the Bluetooth device, factory reset the watch, rebooted the phone, waited a bit for stuff to finish starting up, then went through the process of re-pairing the watch and signing in to all the accounts.
After pairing, waiting for the watch to finish starting everything, and confirming that it was actively paired with the Galaxy Wearable app, I went into the phone's Bluetooth settings and tapped the watch's Disconnect button. It didn't actually disconnect though. Rather than putting the phone in airplane mode, I turned the watch's Bluetooth off and back on. A second after re-enabling it, the same behaviour on the phone resumed; rapidly moving between Other devices and Saved devices.
Watch model: SM-R950
Phone model: Pixel 6
Hardware version: MP1.0
Hardware SKU: GB7N6
GrapheneOS build num: 2024031100
I'll send my log file to your Discord after I look through it for sensitive info I'm not comfortable sharing.
We're going to be making a new release today with a workaround for the remaining upstream memory corruption bugs introduced in the Bluetooth app in QPR2. We can't do anything about old insecure devices which no longer work due to security improvements which also applies to the stock OS.
