Pixel Bluetooth issues

[anon(21918)]

I have had similar issues with my 2016 Honda Pilot. This is only a year old vehicle that worked fine with plenty of other phones, but is not working correctly over Bluetooth with the pixel. I am also having issues connecting to my Lifejacket 2 speaker through Bluetooth from my pixel. Based on some of the information that we are seeing here and the various types of devices we are trying to connect to, I think something needs to be resolved.

 

[tk-093]

Doesn't the 2016 Pilot support Android Auto? Do you have the same problem if it's connected as an Android Auto device?

It does not. Their infotainment center is running Android, but Android Auto did not make it into this model.

 

[tk-093]

I doubt it's a problem with the phone. Cars tend to use really outdated Bluetooth. My 2015 uses bt 2. I've had issues with iPhone, wp, Samsung, and 6p. It's probably not the phone.

Pretty sure it's a problem with the phone. I've found several folks online complaining about the same issues using Nexus devices. I've used the Note 5, Note 7, iPhone 6 with no issues.

 

[russell1997]

I would love to see google make cast enabled headphones. Bluetooth is the suck.

Is android auto a way to cast to your car?

 

[j1cardona]

Pixel XL, 2013 Chevy Malibu, G Watch R, Motorola 360. Connects with car but loses connection upon call initiation or incoming text message (could be any notification, haven't thought to check until now).

For those worried about other Bluetooth: Phone pairs fine with multiple watches and speakers at the same time at home, just an issue with the car. I have a Samsung soundbar and a Bose mini soundlink that have caused no issues. I haven't tried my LG Tones yet, though I do know someone who has a smart watch and tones with no issues from his Pixel XL.

 

[loraque]

In my experience, BT is always hit or miss with devices and phones. Yes, I have seen issues with previous Nexus devices, and I have seen problems with Samsung Galaxy, HTC, Apple, etc. Every new phone and every new BT device (or vehicle) is a wonderful new opportunity for a hardware conflict. Google typically adheres to specs perfectly, it is the rest of everyone that doesn't, that cause issues. Google will need to step in here and do what they can to smooth this out, just like Apple does, so their BT stack works with as many devices as possible, and be damned about the specification adherence. My $.02.

That said, unlike previous Nexus devices, Google IS actually paying for licensed drivers (like the LTE voice codec thing). I expect things to improve here.

Lastly, my Pixel seems to work fine with my Toyota Camry 2015 (non nav setup). I do get occasional hiccups on the audio stream, maybe 3-4 times in my 45 minute commute, that I cannot explain for. New OS, new phone, not all apps upgraded... like all new OS releases, it might take some time for the details to smooth out.

 

[Edgecruser]

I'm having the same problem as the original post with My Pixel and my 2016 Honda Pilot. Everything works great except for the Bluetooth calling. I can not place or receive a call in the car, but I can list to audio via Bluetooth without a problem.

The strange thing is that the Pixel works perfectly in my 2009 Honda Civic. I can place and receive calls without a problem. I also tried a Galaxy Note 5 in the 2016 Honda Pilot and it worked just fine. This seems to be an issue specifically between the Pixel and the 2016 Pilot. Not sure who's end the issue is on, though.

 

[vlok16]

This is a potentially deal breaking issue for me, I live in NY and hands free is the law, my Droid Turbo connects to my car perfectly. If/when I get this phone and it doesn't connect properly, it's going to have to go back.

 

[qfnol31]

This is a potentially deal breaking issue for me, I live in NY and hands free is the law, my Droid Turbo connects to my car perfectly. If/when I get this phone and it doesn't connect properly, it's going to have to go back.

I haven't had any troubles so far, and it's required here in DC/MD too.

A few weeks ago there was a podcast about BT issues on Nexus devices. I bet Jerry Hildebrand has the best information on BT if you contact him.

 

[Pigman]

I have a 2015 Chevy SS. I hope they get this sorted by the time my phone actually arrives!

 

[adebo]

No issues with old Ford Sync or New Ford Sync. Also paired no problem with JBL bluetooth speaker.

 

[trekk]

I have a 2015 Chevy SS. I hope they get this sorted by the time my phone actually arrives!

Not to be a bummer, but I have been waiting for the bluetooth fix for 1 year in my 6P. I will be surprised if they do fix it.

 

[imartez]

Not having any issues so far. It works in a 2015 Infiniti Q50 and a B&O Beolit 15 Speaker

 

[mzanette]

Since this is a Bluetooth thread I'll post my question/issue.

So when the Pixel is paired with my car, if I'm listening to the radio and a phone call comes in the audio immediately cuts to the phone ringing -- which is as expected and good of course so you know when a call is coming in over Bluetooth.

The other day I had the radio on and driving with Google Maps going, set to route sound over Bluetooth, but the radio doesn't cut out whenever a direction is read out? I can confirm that in the same car, my wife's iPhone 6 has the radio cut out and broadcast a google maps direction change correctly over the bluetooth, so i I don't think it's the car's issue.

Anyone else know about this, or see similar behavior? My car is a 2013 Toyota Sienna.

 

[dobo84]

My 2015 Camaro has a issue where I have to manually pair it each time it's rather annoying

 

[Pigman]

My 2015 Camaro has a issue where I have to manually pair it each time it's rather annoying

Well crap, I am likely in the same boat as you. Probably worse, I don't think the 2015 Chevy SS has as new a mylink system as the Camaro has. They never shipped it to the Holden plant apparently.

 

[JDub313]

I had the same issue in my car (2015 BMW 328) with the Nexus 5X and still have the same problem with the Pixel. Not sure why the phone can override the radio, but Google Maps (or Waze for that matter) can not.

What I find even more annoying is if I'm listening to a Podcast on Google Play Music (which means my phone is the main source of audio) and using Google Maps - the sound cuts out when Maps says something - but I can never hear it. The podcast just cuts out, I hear silence for a few seconds, and then the podcast comes back on.

Anyone have any suggestion?

 

[mzanette]

One day when I have time to kill I'm going to fire up the Pixel 24/7 support for the Google Maps bluetooth issue. See if the live rep has any suggestions for me that actually work....

 

[thunderup]

Since this is a Bluetooth thread I'll post my question/issue.

So when the Pixel is paired with my car, if I'm listening to the radio and a phone call comes in the audio immediately cuts to the phone ringing -- which is as expected and good of course so you know when a call is coming in over Bluetooth.

The other day I had the radio on and driving with Google Maps going, set to route sound over Bluetooth, but the radio doesn't cut out whenever a direction is read out? I can confirm that in the same car, my wife's iPhone 6 has the radio cut out and broadcast a google maps direction change correctly over the bluetooth, so i I don't think it's the car's issue.

Anyone else know about this, or see similar behavior? My car is a 2013 Toyota Sienna.

Same thing here, 2013 Ford Explorer. If I'm on any other source besides Bluetooth Audio, Maps won't cut in and read out the directions. What I've done is gone into navigation settings in Maps and turned off the option to play voice over Bluetooth so the directions are read out through the phone's speaker. But the kicker is if I'm connected to my Gear Fit 2 and the car's system at the same time, I can't get any audible directions at all. Not through the phone and not through the car's system. I usually just turn off the phone's Bluetooth at that point. Frustrating.

Edit to add: I think the iPhone treats the Maps directions as a phone call, thus the reason it will cut in regardless of the source you're on? That's the way Moto voice would work when text messages came in while driving and allows you to speak responses through the car's system.

 

[mzanette]

Same thing here, 2013 Ford Explorer. If I'm on any other source besides Bluetooth Audio, Maps won't cut in and read out the directions. What I've done is gone into navigation settings in Maps and turned off the option to play voice over Bluetooth so the directions are read out through the phone's speaker. But the kicker is if I'm connected to my Gear Fit 2 and the car's system at the same time, I can't get any audible directions at all. Not through the phone and not through the car's system. I usually just turn off the phone's Bluetooth at that point. Frustrating.

Edit to add: I think the iPhone treats the Maps directions as a phone call, thus the reason it will cut in regardless of the source you're on? That's the way Moto voice would work when text messages came in while driving and allows you to speak responses through the car's system.

Seems like it would be an easy fix for Google to implement into Maps no? No idea why this hasn't ever been addressed.