Please GrapheneOS Team, be careful with upgrading (again) the Bluetooth drivers on Android 15, as the issue with QPR2 (this time v2) broke some essential (medical) devices. Posting this as a heads-up.

QPR2v2 discussion: https://github.com/nightscout/AndroidAPS/issues/3471

QPR2v1 discussion of GrapheneOS on Android 14: https://discuss.grapheneos.org/d/11383-request-for-testing-and-feedback-with-bluetooth-on-android-14-qpr2-grapheneos

And original article: https://www.androidpolice.com/android-15-qpr2-beta-2/

    Dumdum Sorry, I am not on that channel, still I also wanted to warn those users who depend on these important services/devices to be careful with the upcoming updates

        doffactory I also wanted to warn those users who depend on these important services/devices to be careful with the upcoming updates

        AOSP 15 based on QPR2 stable isn't scheduled to be released until several months into the future. GrapheneOS isn't known for shipping production releases based on beta versions of AOSP (not even sure if those exist?). I don't think it's ever actually happened. While making people aware of potential bugs in an upcoming release of an AOSP stable version might be beneficial in some cases, it does not seem clear in this case that a warning is justified.

        doffactory QPR2v1 discussion of GrapheneOS on Android 14: https://discuss.grapheneos.org/d/11383-request-for-testing-and-feedback-with-bluetooth-on-android-14-qpr2-grapheneos

        While the release that is being talked about in that thread also includes the term "QPR2", I am not seeing how a shared term in an old release would automatically mean that a future release would carry similar, already fixed, bugs.

        doffactory And original article: https://www.androidpolice.com/android-15-qpr2-beta-2/

        That article is saying that Bluetooth bugs, including what sounds like the bug your are reporting, will be fixed in an upcoming beta version.

        This doesn't seem to be affecting GrapheneOS at all, so reporting it in the chat room intended for GrapheneOS alpha and beta testing doesn't seem necessary.

        Please note that I do not speak for the GrapheneOS project.

              12 days later

              Well, what I was afraid of just happened. I lost connection to my bluetooth medical device with the latest stable update of build 2025010700. Extremely unpleasant and frustrating. Previous build was working OK. I am unable to reestablish the working connection, it says it pairs but no real connection.

                • fid02

                  • Post #7

                  doffactory Which medical device and which Pixel device?

                  Could you try resetting Bluetooth settings by going to Settings > System > Reset options > Reset Bluetooth & WiFi?

                      fid02 just done that. It pairs, but no connection after that unfortunately. Something changed between the last 2 builds

                          • fid02

                            • Post #9
                            • Edited

                            doffactory Could you please explain in more detail what the symptoms are? Does the medical device show as connected in the Bluetooth menu of GrapheneOS, but after a while it shows as disconnected in the Bluetooth menu? Or does the Bluetooth menu show it as connected, but one of your apps does not detect it?

                            Also, which Pixel device and which medical device (if you're prepared to share that)?

                                fid02 the device is an AccuChek Insight, a rather old device with Bluetooth 2.0 or similar. It never appeared as "paired" under the Bluetooth connection, as it is controlled via AndroidAPS (an app that connects and manages the insulin pumps).

                                Similar issue happened almost a year ago in 2024 with some bad bluetooth drivers provided by Google that since then they try to re-apply under QPR2.

                                All other Bluetooth devices connect correctly, but only the pump stopped with the latest GrapheneOS update, so something got updated... I cannot see anything suspicious from the release changelog.

                                  Hm, interestingly, after resetting the Wifi and Bluetooth, it was not working. Until I set the first Wifi connection, then magically the paired Bluetooth connection started to work. It happened after more than an hour or so after the pairing, while the app is supposed to check on the Bluetooth device every 5 minutes. I was next to the phone with the device all the time. Weird.

                                  These devices aren't properly standards compliant and have security vulnerabilities. That's why they keep having issues with Android security updates. Android is trying to fix Bluetooth security issues but unfortunately that can cause issues with devices which were depending on security holes to function. They're trying to preserve support for these problematic devices but sometimes there's no way to do it and they get dropped or partially broken. It's not something specific to GrapheneOS. It's unfortunate that these devices aren't higher quality and that they tend to lack firmware updates to provide them with security patches and bug fixes. They're quite critical to people and yet not handled at all seriously by the companies making them.

                                    • Dde0u

                                      • Post #13

                                      GrapheneOS It's unfortunate that these devices aren't higher quality and that they tend to lack firmware updates to provide them with security patches and bug fixes. They're quite critical to people and yet not handled at all seriously by the companies making them.

                                      And this is not at all a new problem!

                                        GrapheneOS yup, fully agree, also an FDA/EMA approval of these devices may take easily 10 years, so by then any standard is pretty outdated.