• Announcements

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

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.

      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.