• Announcements
  • Request for feedback on Bluetooth compatibility regressions with Android 14 QPR3

BHydden Edits are limited to 10 minutes. We'd like to increase it to 30 minutes or 1 hour but can't currently do it due to lack of that functionality. Indefinite editing leads to major abuse including for spam.

Pixel 8a on 2024061300

I have not had any Bluetooth issues. I was already paired to Shokz Openrun and Shokz Opencomm headsets, Garmin Instinct smart watch, and 2013 Toyota. My phone connects no problem to these devices, streams audio, handles calls, and receive notifications just fine.

Pixel 8a on 2024061300
Previous connection to Fiio BTR15 reestablished and used without issue.

My apologies for the late response, I live in Europe, it was night.

Pixel Tablet on 2024061400
(Previously on 2024060500
8BitDo gamepad SN30Pro works fine through Bluetooth connection.

Pixel 7 on 2024061400
(Previously on 2024060500
8BitDo gamepad SN30Pro works fine through Bluetooth connection.

Pixel 6a on 2024061400
(Previously on 2024060500
8BitDo gamepad SN30Pro works fine through Bluetooth connection.

Addition: Just tried Samsung Buds Pro on all three devices, they all work fine.
(Pixel 6a, 7 and Tablet on 2024061400, older version was 2024060500)

P8p 14.06.24 after disabling dev option and resetting Bluetooth settings finally managed to work but still not detecting all device's

    pit2p Which devices in particular are not working?

    It seems a lot of people using specific developer options are having trouble with Bluetooth on QPR3, due to the settings being used breaking on QPR3 upstream. We don't recommend using developer options for exactly this reason, among others.

      Pixel 8, 2024060500 -> 2024061400

      iFi Audio xDSD headphone DAC, and Sony WH-1000XM4 headphones both connected and playing audio fine. 👍

      The "Done" button on the Bluetooth quick tile pop-up is square, vs other buttons which are rounded though, minor inconsistency.

        upstage4186 The "Done" button on the Bluetooth quick tile pop-up is square, vs other buttons which are rounded though, minor inconsistency.

        Known upstream issue/feature. Also square in stock PixelOS.

        No issues with Jabra Elite Active 75t
        2024061400

        P8 on 2024061300 works fine with Airpods and Wahoo.

        The only issues reported so far have all been resolved by users disabling developer options. They were likely all caused by having Bluetooth development settings enabled which no longer work on Android 14 QPR3. If you experience any issues, please try disabling developer options.

          Pixel 8 Pro
          This happened, while bluetooth was disabled: https://pastebin.com/FvjTRf6F

          If I recall correctly it happened right after turning on the phone.
          I've been targeted before by a skilled adversary, but I doubt that it's security related.

          Pixel 7 on build 2024060500

          No issues whatsoever with Sony WF-1000XM4 on the stock software that the headphones shipped with (never updated the headphone software).

          Pixel 8 Pro, build 2024061400

          No issues with

          • Jabra Elite 8 Active
          • adidas RPT-01

          Pixel 8
          Build 2024061400

          Bluetooth works perfectly :

          • suunto race watch
          • jbl flip6 speaker
          • suunto wing headphone

          matchboxbananasynergy GrapheneOS you can take developer options from my cold dead hands when Override Force Dark is implemented properly into GOS. Even now it does not work properly as it resets to being off when the phone restarts. I tested other developer options and it seems to be the only one that does that. No really tho personally i would rather not use developer options but Override Force Dark is a must. Some apps refuse to implement dark themes and are blinding.

            gosrox We're talking about Bluetooth related developer options. Disabling developer options resets the values of nearly all the settings there, although it doesn't reset other changes made with it such as changes made with ADB or the power management menus so it's not a great idea to do that in general because it can't be easily undone.