Bluetooth connection fails

zionad

I am also having this issue with a pixel 9 fold and a 2012 Volkswagen Jetta. My Pixel 8 Pro with graphene works just fine.

thmf

zionad Are you having the exact same issue with 9 fold? Or is it a bit different behavior?

zionad

thmf its the same issue as others. Enter pin and wait for the error message saying it can't connect.

wolf

zebster I can put the head unit into pairing for either hands free or audio, they're separate options. Hands free has a pre-determined pin you can set in the options, audio needs an input. Either way fails 20 seconds after I hit okay after entering the pin number in the pairing dialog.

AndroidMcPlenty

I've got a pixel 7 pro that has this "pairing failed" issue on my 2014 jeep with uconnect. I was regulary using my phone on stock updated android until I installed GrapheneOS. I tried all the above suggestions including a few I found around google but nothing worked. I finally installed android 15 (may 2025)and was able to connect immediately. My phone has since updated to the current ota and is still working without issue.

zebster

I now have the bluetooth log (btsnoop_hci.log) which is a binary file and well opened in wireshark. But analysis of this log is not straightforward and easy since it requires knowledge of bluetooth communication. I tried to interpret the log with the help of AI but so far I have nothing concrete that would really show the issue.

Is there any other location to make a bug report, other than Discord or Matrix?

thmf

zebster Is there any other location to make a bug report, other than Discord or Matrix?

Yes, aside of the chats for real time support there's the os issue tracker.

thmf

zebster Forgot to mention. If you make an issue about this at the OS issues tracker, please leave the link to it here, so others who find this thread can follow the issue too, and show they are interested in this being fixed by using reactions for the issue's first post.

guss

I have the same problem. My Pixel 8a running GrapheneOS won't connect to my 2009 BMW E90/E91. The error message is exactly the same as zebster's.

From the BMW's MAC address, I've determined that it uses a Bluetooth chip from the French manufacturer Parrot, but that probably doesn't help much.

Pixel 8a, GrapheneOS (latest version)
Error message: “Communication with 00:0E:9F:3D:06:0E is not possible”
BMW E91 2009, Bluetooth MAC 00:0E:9F:3D:06:0E
Pixel 5 and Samsung Galaxy Flip 7 with stock OS pair without any issues

It looks like a issue has already been submitted:
https://github.com/GrapheneOS/os-issue-tracker/issues/7388

nostradamust

I have same issue. Enter pin and wait for the error message saying it can't connect.
Google Pixel 9, 2012 Hyundai Santa Fe

guss

That's the problem as far as I got it:

Google has released new Pixel firmware/drivers designed for Android 16 QPR3, but they have not yet released the actual AOSP source code for QPR3.
The GrapheneOS team is forced to run these new QPR3 drivers on the older Android 16 QPR2 base.
This version gap is causing bugs. Because the drivers are closed-source, third-party developers cannot fix them; only Google can.
My guess is, GrapheneOS has to use the newest drivers because of security reasons.

So the only thing we could do at the moment is to wait till Google releases QPR3 to AOSP and maybe to vote up the google issue even if it's marked as "won't fix" or maybe create the same issue new:

https://issuetracker.google.com/issues/491346038

Horatio_Bunce

Same issue for a couple months with some blue tooth devices, most importantpy my hot tub which maybe a older Bluetooth device. Pin stopped working and can't communicate.

Johnnyloans

The fix will probably come out in the summer. Google updates aosp twice a year.

thmf

@"zebster" @"Aeleon" @"wolf" @"Smlvox" @"zionad" @"AndroidMcPlenty" @"guss" @"nostradamust" @"Horatio_Bunce" New release is in Alpha. Here's a small excerpt from the release notes:

update Pixel firmware, driver libraries, HALs and other components backported from Android 16 QPR3 to CP1A.260405.005

Probably worth checking if the situation with Bluetooth pairing is any better once the release in Stable channel.

guss

I just installed Build 2026040801, but unfortunately the error is still there. I tested it with both 4-digit and 8-digit PINs, and I still get the message "Communication with 00:0E:9F:3D:06:0E is not possible".

plazmafire

I have been having the same issue, also with a Pixel 9a.

It had been previously connected to my work truck stereo (Isuzu 4.5 years old) with no issues. Then when my regular truck was in for service, I had to drive another one for a few days, Same model Isuzu except about one year newer. When trying to connect to the newer truck, the connection sat there thinking about it for a little bit, then came up with 'connection failed' on the stereo, and a message on the phone saying 'Can't communicate with MAC ADDRESS'.

I thought it was an issue with the name of the stereo being the same as the one from the original truck causing a conflict in the phone (they both just say ISUZU), so stupidly, I deleted the original one for the regular truck, and tried again. It still failed. I gave up thinking it was only a few days, and I could live without it.

Then a few days later when I got the original truck back, I went to connect it again, and it fails the same way as the other truck. So now I can't use the bluetooth connection in a truck that has never had an issue previously with GrapheneOS. I have been driving this truck since it was brand new, and using GrapheneOS the whole time. I started with a 3a, then a 4a, then 6a, and now 9a. The annoying part is it had been working just fine with the 9a just a few days earlier, with the original connection I made when I got the 9a about 6 months ago. But now that it needs to be connected again from scratch, it won't do it.

I have tried every other phone I can get my hands on in this truck, and nothing has any issue connecting to it at all. I have tried 3 iPhones, and 5 other Androids, all of them connect virtually instantly when I enter the 4 digit code. Only my GrapheneOS 9a fails. I have not tried one of my older phones, but that will be my next test. I will take the old 6a to work, delete everything from the bluetooth list, then try that. It has been sitting in a drawer for the last 6 months, and has not been updated since.

I can only assume something got broken in one of the updates sometime after I did the initial connection to the truck stereo.

I have tried reseting the bluetooth in the phone's reset options, and it didn't fix it. Luckily it still connected to my car stereo, as I was worried it may not do that too. I have tried most of the suggestions in this thread, but nothing has worked.

I have since updated the phone a couple of times, it is now on build 2026040800.

When is this likely to be fixed, as it's most certainly an issue with GrapheneOS (not a single other device has an issue connecting to the same vehicle stereo). I'm in my work truck 10-12 hours a day, and it would be really nice to be able to answer my phone when it rings without breaking the law.

What good it the most secure OS available when it can't even do basic bluetooth connections like every other device on the planet?

thmf

Hey. Welcome to the failed Bluetooth connection club :)

plazmafire Then a few days later when I got the original truck back, I went to connect it again, and it fails the same way as the other truck.

Could you please check with the guys who serviced the car and make sure they didn't update the car's head unit? I understand it's unlikely, but it would be great to rule out all the possibilities.

plazmafire I will take the old 6a to work, delete everything from the bluetooth list, then try that.

If you have time, please test that GrapheneOS on the 6a Bluetooth connection fails, then flash Stock OS on the same 6a and test if that works. Our guess is it won't work in both cases. This test would be very helpful.

Johnnyloans

It could be every pixel 9a in the world can't connect to your truck.
This person yesterday got off of GOS and still can't connect to 1 of their 3 devices. With stock google OS.

https://discuss.grapheneos.org/d/34226-bluetooth-connection-issue/2

I will take the old 6a to work, delete everything from the bluetooth list, then try that.

If you do this, it'd be another option you don't have--keeping the 6a for truck BT duties. Make sure to charge the 6a.

When is this likely to be fixed, as it's most certainly an issue with GrapheneOS

GrapheneOS (GOS) I would imagine don't have any reason to change bluetooth from what google provides.

Google and every phone manufacturer updates bluetooth periodically. Updates could break things.

Fun fact: NOKIA phones were huge. I remember in the early days of BT, headphones and other bluetooth devices ignored the rules of bluetooth and instead got their devices to work with the buggy Nokia code so most people could use their product.

plazmafire

Johnnyloans

But my own Pixel 9a USED to connect to my truck just fine WITH GrapheneOS.

It literally was working on a Friday, then a week later, when the connection needed to be made from scratch again, it would not work. It also USED to connect to the other trucks in the fleet just fine as well. The only thing that's changed is software updates.

Literally every other phone I've had access to connects just fine. Even brand new Androids with the latest software updates.

Johnnyloans If you do this, it'd be another option you don't have--keeping the 6a for truck BT duties. Make sure to charge the 6a.

So, you're suggesting that I go back to using the older phone for the 10-12 hours a day I'm at work, then swapping my sim card into the newer phone for the couple of hours I'm not alseep inbetween leaving work and going back again?

What's the point of having the newer phone at all?

How does this get logged as an issue that needs to be fixed? Because it's an issue that needs to be fixed.

Johnnyloans

plazmafire

It's certainly frustrating and a big obstacle. I am not saying any of my suggestions are a good fit for you or the ideal solution in our imperfect world. Your current phone probably won't connect 24 hours after your last attempt so an interim plan could be in place.

So, you're suggesting that I go back to using the older phone for the 10-12 hours a day I'm at work, then swapping my sim card into the newer phone for the couple of hours I'm not alseep inbetween leaving work and going back again?

Again, I don't know your situation.
A person in this situation could use android auto if the car supports wired.
Or an ear piece for hands free calling, do a wifi hotspot on the 9a to give your 6a internet access, and play music or podcasts in the car. Keep the SIM inside of the 9a.
Use a phone holder for GPS on the 9a.
1 charging cable in the car should suffice, 2 if you want.

You could try Settings > system > reset > reset wifi & bluetooth This will have your phone forget every wifi network--retype in the password.
Or try factory reset or switching to stockOS.

Weigh your options and decide what's best for you.

When is this likely to be fixed

I don't speak for GOS. Maybe in 2026 Q3 when google releases their biyearly AOSP update, Android 17.

How does this get logged as an issue that needs to be fixed? Because it's an issue that needs to be fixed.

Your issue could be the same as this:
https://issuetracker.google.com/issues/491346038

A key indicator is if it takes a while for it to think and then fail to connect.

Note: Comments on an existing issue on the GrapheneOS github that say "same issue on my ISUZU vehicle" don’t add much context in this situation and are discouraged. If you had technical information leading to a resolution then that'd help. Another comment won't make anything go faster or have them realize the importance of such a fix. On the google issue tracker there's the +1 button for this or a thumbs up reaction on github to communicate this.

plazmafire

Johnnyloans

No, the vehicle isn't not Android Auto capable. But it's also NOT an antique.

Johnnyloans You could try Settings > system > reset > reset wifi & bluetooth This will have your phone forget every wifi network--retype in the password.

I tried this, which I actually put in my original post. It didn't work.

Johnnyloans If you had technical information leading to a resolution then that'd help.

I don't know any of the technical information. I'm just someone trying to get what is 'apparently' the best OS availablke to do basic phone connectivity stuff like every other phone. It USED to connect just fine, Now it DOESN'T.

The problem I see with this is as follows:

If I go to Google, and tell them I'm having this problem, then tell them that I'm using GrapheneOS, they're going to tell me tough luck, ask Graphene (basically their reply in the link you supplied for the issue tracker. Google say it's a GrapheneOS issue. They even marked said issue as closed).

When I go to Graphene, and tell them I'm having this problem, they tell me it's a Google issue and I should go to Google for a solution (or wait 6 months and MAYBE it gets fixed).

GrapheneOS supplies the OS but don't offer support for the entire OS as it's installed. Google doesn't give a flying rat's fart about it because I'm using GrapheneOS.

There's a HUGE gap in the support, and when the thing won't do basic 'phone stuff' no one seems to care.

All I want to do is have my GrapheneOS phone connect to the stereo so I can make and receive phone calls, like it USED TO DO TWO WEEKS AGO. But apparently, that's my own problem, and maybe I should learn coding, and go over every single line of code for the phone, and work out how to fix it myself.

Don't get me wrong, I love GrapheneOS. I've been using it for years, and have had virtually zero issues with it. It's easy to install, it's easy to operate, it's secure. But when something actually important stops working, all of a sudden, it seems like it's my problem, and if I don't like it, that's too bad.

« Previous Page Next Page »