• Announcements

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

doffactory Your device likely broke due to the major security improvements for Bluetooth in Android 14 QPR2. It's likely also broken on the stock Pixel OS. The only way it would be broken specifically on GrapheneOS is if there's ANOTHER new memory corruption bug that's being detected. If you have a Pixel 8 or Pixel 8 Pro to test with, that could largely rule out this possibility since MTE would detect it and make a crash report that's easy for us to deal with compared to weird symptoms stemming from something like use-after-free combined with zero-on-free defending against it which can result n the functionality not working due to memory corruption bugs but protects against exploits.

    Galaxy Watch Pro 5 is still not connecting. Will there be another release/fix? Thank you

    GrapheneOS

    GrapheneOS Pixel 7 - Sony XB900N headphones wok perfectly. LDAC works same as before updating. I have not been able to test whether or not the Fast Pair prompt works when pairing for the first time.

        Pixel 6a here

        • hybrid watch Withings Scanwatch2 works perfectly (BLE),
        • loudspeaker JBL GO2 works perfectly,
        • DIY amplifier Beocreate works perfectly,
        • HP ProBook 445R G6 works perfectly,
        • Pixel buds A series work perfectly,
        • Withing wireless Blood Pressure Monitor works perfectly.

        P8. Galaxy watch 6 and Bose Mini II SoundLink still can't connect.

        P8Pro | Build 2024030800

        Bluetooth runs smoothly with:

        • Jabra Elite 7 Active
        • Adidas RPT-01
        • JBL Go 2

        Just to let all the Galaxy Watch owners know, I factory reset the watch, reconnected fine and re-set up. Took about an hour. Then I disconnected from Bluetooth and the watch will not reconnect.

          Pixel 6a - no problem with speaker (Edifier), headphones and car. The only thing that is much worse is that to enable bluetooth, you have to click bluetooth tile and than click turn on bluetooth, instead of just clicking bluetooth. I wonder who is creating these nonsensical "improvements", that makes things more complicated.

          Hi.

          Unfortunately I am also impacted by this.

          Tested with:

          • 6 Pro
          • 6a
          • 8 Pro

          Some facts about the devices
          Tanita Scale= OK
          HONOR CHOICE (in ears) = OK
          Google Pixel Buds Pro (in ears) = OK
          Omron Evolve (blood pressure) = OK
          Oral B IO 10 (Toothbrush) = OK
          Samsung Galaxy Watch 5 Pro (Smartwatch) = NOK / KO
          Mercedes Benz E Class (car built 2023) = NOK / KO

          So with two devices I have issues.

          1. Unfortunately the smartwatch is kinda useless without a connection to the Samsung Health App. Here I have the same issues as the others. I tries again and again to connect, what will also drain the battery of the smartwatch. As Samsungs update policy is also not "that" bad, I would not expect that they did not see this coming.

          2. There is no connection from the Smartphone to the car. Many of the functions I cannot use anymore. For instance that the car realizes it's me and fits the seat automatically to my position and lots of other things.

          Side note: I understand your point that you would like to tshoot the situation to help us. But I definitely won't install any stock image on my phones just for testing purposes. Especially since I do not trust the backups of seedvault.
          If I can provide anything else, beside install a stock rom, I am happy to help.

          This is the first time since I use GrapeheneOS that I have issues. In other words: You guys rock and I highly appreciate your work. Thanks a ton!

          p0well34
          I can confirm that the exact same thing is happening with Galaxy Watch 5 and Pixel 6 after QPR2 update.
          2024030900 release has not fixed the issue.

            My Pixel8 just installed 20240309 and after a reboot I have to report that connecting to classic (non-BLE) dongle (OBDLink MX+) is still not working. Again, I do not get any crash reports, pairing works, but then connecting fails. E.g. when trying connect in Serial Bluetooth Terminal it takes some time, then returns an error, something like "read ret -1“.
            It happens that I was able to do a test with another Pixel8Pro which is on latest stock rom (2024-03-05) and on this one connect works flawlessly, so I assume it is a grapheneos specific issue.

              Adding an extra confirmation, Samsung Galaxy Watch 6 still doesn't connect through bluetooth after the 20240309 update. I was only able to get it connected remotely through wifi

              The remaining issues likely also occur on the stock OS and are likely caused by bugs in the Bluetooth accessories. It's likely a consequence of the security patches. Those devices need updates fixing them. Google repeatedly rolling back security patches from prior months due to broken devices isn't really a good solution.

                GrapheneOS

                Thanks for replying. So if I'm hearing you correctly Samsung watches do not connect with Bluetooth to the Google factory image as well? So I guess going back to the factory image will not fix it either. Damn!

                  topro It happens that I was able to do a test with another Pixel8Pro which is on latest stock rom (2024-03-05) and on this one connect works flawlessly, so I assume it is a grapheneos specific issue.

                  Well, so now we have at least one evidence of something working with QPR2 stock OS and not working with QPR2 GrapheneOS.
                  Can anyone confirm this phenomenon with any other device?

                      GrapheneOS well, if there would be 1 rollback release to pre-QPR2, and moving the QPR2 back to beta would be a solution for few, if I am reading this thread correctly

                          p0well34 Galaxy Watch 6 is connecting and working on friends P6a running stock.

                          When reporting "works on stock" it would probably be best to specify the build number from the stock device (if it's pre-QPR2 stock that is not diagnostic).

                              p0well34 Thanks for reporting that. If there are a couple more reports the developers can look into whether they can reproduce on the stock OS.