• Announcements

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

GrapheneOS We can't do anything about old insecure devices which no longer work due to security improvements which also applies to the stock OS.

Is the Galaxy Watch 6 one of the old, insecure devices? Meaning we'll have to wait for Samsung to release an update that fixes it?

      eladris
      No! The Galaxy Watch 5 and 6 models received a security update yesterday. I also spoke with Google and Samsung. The security firmware is up to date.

        Please make sure to do this:

        Before testing, please disable developer options, enable "Notify about system process crashes" in Settings > Security and reboot.

        We haven't gotten a crash report tied to the Galaxy Watch issue yet, although it might not involve a crash.

          We're coming up with some workarounds to ship in the next release. We want to try to provide them in a way that users can help us determine the problem through flipping some toggles. We can then try to act based on the knowledge gained from that to fix the actual problem.

            Pixel 7 Pro - Graphene Build # 2024031100

            Bluetooth Devices broken since QRP2:
            OBDLink MX+ - Worked well before QRP2, but now I am unable to connect to this device.

            Bluetooth Devices operating normally since QRP2:
            Galaxy Watch 4 Classic
            Galaxy Buds Live
            Pioneer DEH-X6900BT

            Before testing, please disable developer options, enable "Notify about system process crashes" in Settings > Security and reboot.

            Tried this, but haven't been notified of any crashes or logs. I'm not sure how to generate a relevant log

            I have issues making phone calls in Android Auto via Bluetooth. I get the message "Bluetooth not connected". Only Phone Speaker Audio works in Android Auto.
            Phone calls with a direct Bluetooth connection between the phone and car work fine.

            I'm using a Pixel 7 Pro and I'm Graphene Newbie.

              Gianca Did you enable the toggle for this in the Settings > Apps > Sandboxed Google Play > Android Auto configuration?

                  We have a new release which will reach the Alpha channel soon with a potential workaround for any issues not occurring on the stock OS. Anything that broke on the stock OS with Android 14 QPR2 will remain broken on GrapheneOS, which will mostly be very old insecure devices.

                  xaz2fiaghi You can switch to the alpha channel, download the update (now in alpha), and then immediately switch to the stable channel, so that you will only get the next update when it reaches the stable channel. You can switch whenever you wish.

                  All releases go through the alpha, beta and finally stable channel.

                    Thanks. Just updated to new alpha version, went to Apps / See all / Show system / Bluetooth / Hardened memory allocator, and switched it to Disabled. Rebooted. Unfortunately, it still no longer connects to my OBDLink LX car adapter.

                    Maybe others will have better luck with this temp fix though?

                      snackguy That might be a case that's also broken on stock OS. Unclear at this point. They made many Bluetooth changes in QPR2 which is the source of all these issues. Some of them cause breakage with stock OS and GrapheneOS. Some are memory corruption bugs which may mostly not break it on stock OS but get detected / uncovered by our security features which leads to them causing more breakage on GrapheneOS. These temporary changes SHOULD eliminate nearly all the extra breakage on GrapheneOS but it remains to be seen. If it doesn't help with anything, that's somewhat good news in a way because we can add back the hardening but it's bad news in that we need to go back to the drawing board with trying to figure out what broke and why.