I read through all the threads and did not see this one. I can't connect to the Android head unit in my truck with the Pixel. It worked fine with the 5x on Nougat 7.0 but not the Pixel. I have reset them both to no avail. I read today that it is a known issue with 7.1 that Google is addressing "Google's new phone is having trouble pairing or staying connected to Bluetooth in many cars" but worried since I did not see it on here maybe its my phone. Plus my head unit is essentially an Android tablet in the dash. Has anyone else experienced this?
I have mine connected to my 2006 Charger Uconnect without any problems. It sounds wonderful and does not disconnect. I have also connected it with several wireless speaker without any issues.
Sometimes rebooting the phone temporarily fixes bluetooth connections issues.
Has any experienced no ring-back tones when doing an outgoing call when connected to a Bluetooth headset device but making the call from the phone? It only stated occurring(I think) with the November release. I am on Verizon.
It appears the phone does switch to handset speaker until the call is connected. Very annoying for me as I use an in house Bluetooth device that connects to my in house phone.
There are known issues with Bluetooth connections and vehicles. See this thread from the product forums:
https://productforums.google.com/forum/#!msg/phone-by-google/SZrziPyWiHw/jmV8CjeRBwAJ
Related
OK, so I am curious as to whether or not anyone else is having issues with the A2DP performance on this guy. When it works its great, sounds pretty good for BT. But here are two issues I have found.
When playing music over bluetooth, get/make a call it switches to handsfree fine, but when is switches back it the music clips on and off.
2nd. It seems to only pair with one A2DP device. I have a blackberry bluetooth gateway which works great. But when I pair it to my pioneer head unit, it only connects to the hands free profile, not A2DP. My deck works fine on all my other devices. I have to delete both pairings, reboot, and re-pair.
Idk but are they Bluetooth 4.0 compatible?
Hey,
So I do not have my HOX yet but your problem reminds me of another issue with bluetooth on some other phones.
Try this when you set up your pairings make sure you pair it FIRST whit the device you want to do A2DP streaming on (probably your head unit) then set it up with any other devices. Some times some phones or bluetooth head units will only connect A2DP with the first devices that it is paired with (what is some times considered the primary device).
Also when it cuts out on your rather than messing with your phone shut off your head unit or BT mount for like 15 seconds and turn it back on. Also toggle it off on your phone then toggle it on after the units are powered up. I had that bug with music after a call happen a lot in the past but it turned out it was my BT unit on my visor (it needed a firmware update) but still shutting it off would usually fix it.
EDIT
Also see if you can update the firmware on your BT units. If the phone is using 4.0 and they are using 3.0 there could be some comparability issues.
I have issues with my bluetooth also. Sometimes it just won't connect to my car's bluetooth. Usually it seems like it happens when it connects then i turn off the car, then when i go back in the car(like running in to the store real quick then coming back out) and it wont' reconnect unless I restart the phone. Not sure what the problem is.
I just flashed the OTA update for Android 6.0 last week on my Nexus 5 and I noticed that with the new update, phone calls no longer get routed through Bluetooth on my Mazda3. It is able to pair fine with the car and can stream music through Bluetooth, but calls do not go through.
Here is what happens:
When I place a call, the audio automatically gets routed back to the phone. If the other person picks up, calls will continue going through the phone speaker unless I manually select route through Bluetooth. Sometimes this works and sometimes it doesn't, but it does get frustrating trying this workaround especially while driving.
I tried unpairing and re-pairing bluetooth with the car, cleared the data and cache of the Bluetooth app on the phone, and even tried a factory reset, but the problem still persists. Anybody else run into the same issue and found any possible fixes?
For the record, when I did this with Lollipop 5.1.1, it worked without a hitch.
Thanks!
I am having a similar problem trying to connect my Nexus 5 running Android 6.0 to my JVC car stereo. It continually complains of an invalid key, albeit both phone and car head unit show the correct key.
I am unable to make a bluetooth connection at all with the stereo. I had no issue with my Nexus when it was running 5.1, and my iPhone 5 continues to pair with the stereo.
I had this issue on the last preview but haven't seen it yet on final 6.0. For either regular calls or Hangouts calls.
I just rolled back to 5.1.1 and Bluetooth calls work fine with the car now. So it appears that it is a problem that is resident in 6.0.
Same here, but a little different: It pairs and when I start a call from the menu it goes down but the call is still up on the phone. When the other person picks up the call is re-routed to the car speakers... very strange behaviour!
Same behavior as what you are seeing when paired to a '15 Accord but works fine on a '14 Camry.
im at 6.0.1 and has the same problem, streaming music through bluetooth is ok but no voice call...
Any news on this? My wife's nexus has same problem. Nexus 5 with Android 6.0.1. compiling version M4B30Z.
I read on a different site to disable wireless scanning in location. Just tied that and have been able to make and receive calls from the car. Will be interesting to see if it continues to work.
I'm having an issue with my bluetooth holding a connection with my 2013 Honda Civic LX. When listening to music through any music playing app, the connection always stays steady. When there is no music running from the phone, I'll frequently get a message from the display on the dash that the phone has been disconnected. The phone will usually reconnect in a second or two, with another display indicating that it has been connected. This will happen at least two times during my commute to work (25 minutes), oftentimes as many as five times. When I am actively in a phone call, the disconnects seem to be more frequent. It has a timer on the display that shows how long the phone call has been active through the car, and it rarely gets above 3 minutes before the call gets routed back to the phone's speakers while the bluetooth reconnects. The strange thing is that my wife's LG G4, also AT&T, has absolutely no connection issues at any time. I switched phones with her for a week just to confirm since I'm the one generally driving this car, and I didn't have the car drop the connection to the phone even once. Before that week, her phone would have occasionally been used when we were both in the car and she wanted to listen to music through her phone, so it had been connected to the car for more than a week.
I factory reset the phone just to see if there was a strange software issue causing the problem. After the factory reset, the phone and car had a steady connection with no drops for about a week. When the problem came back and was obviously just as bad as before, I tried another factory reset. Once again, the connection stayed steady for about a week before I would get disconnects again. At this point, I contacted AT&T, who replaced my phone thinking that it could be a hardware issue. A week after getting my replacement, the issue popped up once again.
Besides factory resetting, which is the only thing I've found to fix it at least temporarily, I have tried a few different troubleshooting steps. I have cleared cache using the storage screen in the settings menu. I've deleted the phone from the car's connection list. I've re-paired the phone to the car without giving permission for contacts or messages. Also tried to just do a simple reboot of the phone, as well as turning bluetooth off and back on. None of these have any effect on the connection issues once they start coming up.
I can take the car to Honda, but judging on the fact that my wife's phone works just fine in the car, I'm convinced that it is somehow an issue with the software on my phone. My phone is not rooted, and is currently running Android 5.1, S/W H81010o, Build LMY47D.
My guess is hardware problem. My G4 seems to do the same thing with my Jaybird X2 headphones. I've had Jaybird swap them and I'm having the same exact issue of disconnect as with the previous set. I doubt I'd get two bad sets, so its gotta be something hardware related. Sorry I wasn't any extra help. I'm just searching to see if anyone else is having my issue.
My hunch would be whatever the BT protocol is that's being used to pair the devices. Or possibly just an isolated hardware incompatibility. I'm on my second G4 (totally separate reason from BT), and neither has had issues with pairing or staying paired. Even if I were to pause or altogether stop playback of audio, the connection remains stable for me. I pair mine with a Sony BT speaker, a Kinovo receiver for streaming to my car stereo, and even a receiver attached to my Yamaha A/V receiver at home. No issues whatsoever.
For what it's worth: I use PowerAmp Pro when I stream, almost exclusively.
upyouratrix said:
My guess is hardware problem. My G4 seems to do the same thing with my Jaybird X2 headphones. I've had Jaybird swap them and I'm having the same exact issue of disconnect as with the previous set. I doubt I'd get two bad sets, so its gotta be something hardware related. Sorry I wasn't any extra help. I'm just searching to see if anyone else is having my issue.
Click to expand...
Click to collapse
The strange thing for me is that my wife's LG G4 (now 6 months old) works fine in my car under the same circumstances, but I've had 2 LG G4's of my own that essentially showed the exact same symptoms almost immediately. I'm leaning far more towards it being software, with whatever glitch not being present immediately after I factory reset but shows up within a week on my Google profile. My guess is that it's related to the phone related data transferred to the car since it stays connected just fine during media playback but disconnects soon after the media stops, but I can only block contacts to test that theory.
I have a 2014 Toyota tundra. Before the update my Bluetooth was working perfect. Since the update, anytime I turn on the Bluetooth, it reboots/crashes my stereo. Just wondering if anyone else has had this same problem?
Sam
I have a Toyota Avalon and I am also having bluetooth issues since the 6.0.1 update. I have to power down the stereo and bluetooth on the phone to get the Media audio portion of bluetooth to connect. The Call audio connects fine automatically.
I called Verizon and they have has some reports of issues with this. They documented the issue and transferred me Samsung with no resolution.
Marshmallow on all the Nexus devices appear to have issues with Bluetooth according to these sites, could the issue be a marshmallow wide issue?
http://www.androidpolice.com/2015/11/30/bug-watch-vehicle-bluetooth-call-audio-problems-being-reported-on-all-four-nexus-phones-with-marshmallow/
https://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=189188&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=189188
I just wanted to chime in. I have a 2004 Corolla and I don't have native Bluetooth audio connectivity so I use: FlexSMART X3 Bluetooth FM Transmitter. So far so good since the update to Marshallow and use with my LG HBS 750 Bluetooth Headset is ok as well. Sorry, sort of not really the same issue, but its working ok since Monday, when I took the OTA update to Marshmallow. Hopefully they Verizon/Samsung has a fix for this issue.
Same issue
I have a 2015 Highlander and have exact same issue. If you go to settings and then bluetooth, click the sprocket next to the paired toyota device and turn off contact and call sync, it will stop crashing your Toyota stereo. It does mean that your contacts and call history will not show in your Toyota system. I reinstalled android 5.1.1 from www sammobile.com/firmwares/database/SMN920V/ download 5.1.1 and follow the instructions at the bottom of the page. The download takes about 2 hours but worth having my toyota stereo working again. I have contacted Toyota and Verizon and both have been zero help. :crying:
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
nickelnine said:
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
Click to expand...
Click to collapse
I am having the same issue with 9.0.2 OOS. So not sure if this us a compatibility issue with more than 1-2 years old vehicles or something else? Glad to hear that OB7 is working fine for you. Hope fix is coming soon. It's simply annoying.
I am having car connection issues as well. I have a 2010 Ford Edge. Just moved from Sony Xperia XA1 Ultra on Orea to my first OP device - OP6 Pie 9.0.2 - I can connect to my car initially but once I turn off my car, I have to go through a series of reconnect steps. I called tech support and we spent about 45 min troubleshooting - of course I was told I was the only one who had complained of this issue - anyway no resolution. The only way I can "reconnect" is to go into my car's system settings and select "connect to BT device" then toggle bluetooth off and on in the phone - sometimes this works with the first go, other times I have to repeat this cycle 5 or 6 times. Simply selecting "previously paired devices" in the phone app doesn't work either.
Really a pain in the tush, because I am usually in a hurry and don't have time to go through all this scenario to get a connection.
On the other hand, I have a bluetooth ear piece (made by Samsung that is like 5 or 6 years old) that reconnects every time I turn it on, no problems.
Car connections too but was not present in omni
I found for stock, performing a network reset (mobile, wifi Bluetooth) then restarting the device fixed the Bluetooth connection issue.
For custom non-stock ROMs, for my issue at least, I found its not a Bluetooth issue at all but rather the mobile network drops and the car Bluetooth cannot reconnect. The same network reset as above does not work but what does work is toggle off the "automatically select network" and manually select the mobile network from the menu that pops up. This keeps the mobile network intact (until the next device reboot, at which point repeat the steps) with the car and all is good.
I only figured it out by accident; hope this helps others.