Is anyone else having issues with their 5x connecting to their car's bluetooth automatically (I drive a 2015 Subaru Forester)?
My Nexus 5 would always just automatically connect, but since I switched to the 5x I have to either connect to the car from the phone or vice versa.
I'm sure I could work something out with tasker or whatnot, but that feels to me as though it should not be necessary?
I have yet to get back in my car after pairing to my bluetooth adapter (I just paired this morning) but I will check later.
Do you have a list of saved or prioritized devices in the car? I wonder if the Forester bluetooth is trying to connect to your first device (Nexus 5) unsuccessfully.
I have a 2014 Ford Focus. The bluetooth will connect automatically, but I have noticed weirdness when placing calls. The car will take a while to initiate the call and then display an error saying "call cannot be completed". Then, 2 seconds later the call audio (ringing) will occur.
I am hoping that these are just some initial bluetooth issues that will be ironed out.
I had deleted my old device from the car's memory.
Another thing I am experiencing is that even if my phone IS connected, the calls are going through the device, and not my speakers.
It still pauses the music...
It could be either my car or the device. I've heard of other Subaru owners having issues with multiple devices in their car, just wasn't sure if it was a little of Column A and B. It seems likely enough it's a little bit of both.
No issues at all. I have a 2012 Dodge charger with the 8.4 Uconnect. This phone actually connects quicker than my S6 edge did and the sound is louder at max volume (on the phone) than the S6E. The only thing that doesn't work is the text messaging from the Uconnect, but overall I am very pleased.
stu_brainsurgeo said:
I had deleted my old device from the car's memory.
Another thing I am experiencing is that even if my phone IS connected, the calls are going through the device, and not my speakers.
It still pauses the music...
It could be either my car or the device. I've heard of other Subaru owners having issues with multiple devices in their car, just wasn't sure if it was a little of Column A and B. It seems likely enough it's a little bit of both.
Click to expand...
Click to collapse
My in-laws own a 2015 Forester so perhaps next time I see them I'll try to pair my 5X. May be a while before that happens though so don't hold your breath
2013 Honda Civic here (so cool, I know). I'm getting mixed results on it automatically connecting. Sometimes yes, but other times I need to connect manually. Yesterday, Bluetooth audio got really choppy in the car, and I had to restart in order to stabilize that again. Have not seen the choppiness issue with my other Bluetooth devices.
Sent from my Nexus 5X using Tapatalk
I had no problem with my Mazda 5 connecting to my Moto E on 4.4.4, but since the upgrade to 5.1 I now have to turn bluetooth off then back on every time I get in the car for it to connect. Also, the connection can drop. I tried deleting existing connection data from both car and phone, setting up from scratch, but it hasn't made any difference. Wish I could downgrade by phone's OS back to 4.4.4.
Might depend on the sound system. Reconnects to my 2013 VW Passat every time.
Sent from my Nexus 5X using Tapatalk
No issues in my Audi or aftermarket radio in the Subie... It sounds like you may not have calls being routed through the phone (based on your comment), maybe that is causing the connection issue? Something like only a phone connection is automatically connected (and the audio comes with it), but an audio connection is not?
I have a 2011 Mitsubishi Ralliart and i don't have any issues with my 5X auto connecting to the factory bluetooth system, my problem is the factory bluetooth is garbage since any time someone calls there is too much interference i can't hear what the other person is saying.
JC Why said:
I have a 2014 Ford Focus. The bluetooth will connect automatically, but I have noticed weirdness when placing calls. The car will take a while to initiate the call and then display an error saying "call cannot be completed". Then, 2 seconds later the call audio (ringing) will occur.
I am hoping that these are just some initial bluetooth issues that will be ironed out.
Click to expand...
Click to collapse
Exact same issue here but with a Kia. As soon as the phone "reacts" to a call being started on the headunit, the headunit says "call was hung up". As soon as the call is answered, it offers to be used for handsfree. It's as if the phone's "CallStatus" messages over bluetooth aren't correct
Subject crosstrek 2014, BlackBerry z10 never had an issue whatsoever, but since I got my 5x, I get half a connection (Bluetooth connects with no audio), with 6.0.1, no automatic connect... Blackberry's reputation may be downhill, but I sincerely miss its reliability and the hub...
Nexus 5X and 6P Uconnect 8.4 Grand Cherokee 2014
I recently started experiencing a similar issue.
I use my 6p for music and audio only, and my 5x for phone calls and sms.
About a week ago, they would stay connected as long as nothing was being streamed. However, as soon as I received a call on the 5X, the phone would lose BT connection to the system, and then connect back after about 30 seconds. It would do that throughout all of the calls, regardless of the length of each call. After the first 2 calls, I started streaming music from Google Play Music on my 6p, and the same thing would happen.
I removed Uconnect from both phones, and both phones from Uconnect. Paired them back again, and it is still doing the same thing.
I will try resetting the Uconnect to factory default later today and see if it has any positive effect, and will post my findings here.
If anyone else has a uconnect system with the same issue, please post it here, and we can try looking for a solution together.
Thank you,
Recently got an LG G4 after my trusty N5 suffered from a virtually non-working phone mic and broken charging port. I also have a MK7 Golf with Discover Pro Nav which supports Android Auto. With the LG G4 I have noticed that Spotify will not work. I can see that it is controlling the app from the headunit, able to access playlists etc but I cannot hear anything. Turning the volume knob doesn't seem to adjust the music volume (and you can see it has no effect on screen too)
Google Nav works, but this is apparent as a voice command volume which does take effect.
Tried with the Nexus 5 and an Nexus 6p and it works fine on them so seems to be something to do with the phone. Anyone seen this before? Is there a fix?
Other than that the G4 seems pretty good. Signal strength is amongst the highest I've ever seen on any phone (works in places my N5 did not) and audio quality in calls is great.
I have a story to tell. Not a problem that I want to solve. Just sharing my experience.
I'm using my Sennheiser MX 365 earbud with my Nexus 5X a lot. The earbud does not have a microphone nor a button. Simple as needed.
Some things related to this configuration:
- Sometimes 5X launches the Google Now voice search when I plug the MX in. Only rarely.
- I can use MX to listen the phone calls and I can talk into the 5X holding it to my mouth. Both end of the phone works this way.
- Sometimes the other side can't hear anything at all. Maybe 5X expect sound from MX?
- Sometimes the other side can't hear me if I don't use MX.
Maybe the last 2 microphone issues can be network related because if I switch between 2G-3G-4G, then it solves the issue.
Also sometimes I try to mute-unmute my mic during the call, switch on-off the speakerphone. This can solve the problem also.
I'm using completely stock rom and phone app from play store, latest version.
Has anyone tested the microphone on their bluetooth sets yet with the Pixel 2 XL?
I'm scared I might have a defective phone. My bluetooth headset connects to my phone just fine, and even plays audio just fine, however, the microphone is not picking anything up. This means I can't use hands free calling, or hands free Google assistant.
I know it's not my bluetooth device because it works fine when connected to my older phone (Nexus 6P)
Has anyone else had trouble with doing microphone over bluetooth? I'm not sure if I need a replacement or just a software patch.
For reference, I use the LG HBS-1100 bluetooth headset.
http://www.lg.com/us/bluetooth-headsets-headphones/lg-HBS-1100-Silver-tone-platinum
Later today, I will try a different bluetooth device.
EDIT: I tried with my older pair, the LG HBS-750, same issue.
I've got a soundbuds tag headset, the connection speed is faster and my phone calls seem ok. I've only made like 2 calls so far though.
@Traceguy I've had several lg headsets and they all sucked. No could hear me or I was breaking up all over the place. Switched to the jaybird x3 and it's been perfect ever since.
Disclaimer: I'm on a Nexus 6. Waiting patiently for the 2XL to arrive next week...
I've talked with Google support, they helped troubleshoot, but nothing could be found out of the ordinary, and it's now being elevated to the next level support team. They have my phone number and will call me back when they find anything.
My Bluetooth version is up-to-date, but there is a update pending for my Pixel 2 XL, which hasn't made it to my phone yet. That may or may not help. IDK
I will get a friend later today to connect his bluetooth to my Phone and test the mic. Maybe it's a total LG issue.
I'm gonna say it's an LG issue. I went through 4 pair of the infinium headsets. All had issues with ppl hearing me. Even when paired to different phones.
Larzzzz82 said:
I'm gonna say it's an LG issue. I went through 4 pair of the infinium headsets. All had issues with ppl hearing me. Even when paired to different phones.
Click to expand...
Click to collapse
I don't know much about how Bluetooth works, do Bluetooth devices use drivers similar to USB devices? Maybe the Pixel 2 XL is missing the necessary drivers for the LG HBS sets. That is something that can be fixed with a software update.
It's not an LG issue. It's happening with my car's head unit and others are reporting it in the Pixel User Community. This is one of a few strings that include it. https://productforums.google.com/fo...pPfDGvkNw;context-place=forum/phone-by-google
robsw said:
It's not an LG issue. It's happening with my car's head unit and others are reporting it in the Pixel User Community. This is one of a few strings that include it. https://productforums.google.com/fo...pPfDGvkNw;context-place=forum/phone-by-google
Click to expand...
Click to collapse
I'll just wait patiently to see what happens. I'm hopeful it's not a hardware defect with the bluetooth chip in my phone. I never use bluetooth car's head unit, for whatever reason it drops every few seconds or minutes. I'm driving a 2013 Charger, so I'd expect better results. I use aux, and thanks to the USB-C Dongle, I am not stuck without a way to play my music in the car, though without the microphone input from my headset, I can no longer tell Google which song to play.
I just came here to check.
I can place calls and be hear over bluetooth both on the car and my Sol Republic headphones.
Assistant can not hear over either. Assistant does work over a wired headset.
Support had me boot into safe mode, spoiler: Assistant won't even launch in safe mode, and factory reset which did not fix the issue.
They have no resolution at this time, but are looking into it and wanted me badly to leave feedback on the problem. I'd suggest anyone with the problem leave feedback as well.
At least I'm not the only one. They said I'm the first to call. ut then again they also said it coud be a hardware issue which I just can't see.
Mine, too. I have a Pioneer head unit. Playing is fine, Assistant is fine when not connected to Bluetooth, but Assistant just will not work over Bluetooth. I use this all the time so it's already driving me crazy and it's only been one day. (Same head unit worked fine with previous phones... Pixel 1, Nexus 6p, and OnePlus One.)
I'll add myself here as a +1... Same symptoms. Seems like microphone over BT doesn't work.
I have a Plantronics v5200 and it works for calls. But not for assistant. Sucks......it will activate assistant on a long press. But registers no sound. Works perfect on my original xl. So it's not the headset.
Also confirmed that it WILL work just fine if I launch it with "OK Google" instead of a squeeze or button. So it can work... Starting to seem like a bug in Assistant, which makes me hopeful for a decent fix.
@Anaelith Yes, but did you enable bluetooth Mic input from settings? If not, saying "Okay Google" will use the internal microphone in the phone instead of using bluetooth.
Go to Google Now settings > Voice > Enable "Bluetooth headset". This option "Records audio through Bluetooth headset if available"
That aside. I have tried bluetooth mic in a phone call and it works. I also tried Bluetooth audio with my Car's head unit and have not received a single drop. So the drop problem was related to my Nexus 6p.
Seeing as the mic works for phone calls, the problem seems to truly be software related.
Using a Jabra Eclipse, all settings correctly enabled. Not only does the Google Assistant not work, but neither does voice texting.
Worked fine on my original XL, so I know the earpiece is good.
Guess they better look into this...
Works fine on calls, won't work on assistant.
Man, I'm just gonna get my phones six months after release. It sucks to have to debug all this stuff for Google.
[UPDATE] I wrote here and I have a smaller pixel 2, but I have this issue too.
I'm another one. None of my Bluetooth microphones work on the pixel 2 XL, but do on my 6P
Hi everybody I think I may have found a possible fix/workaround
Settings\search\voice\Ok Google detection
Turn on ok Google anytime turn on trusted voice
(May have to do voice training)
Now when I press the call button and say "OK Google" then the command I hear it in my headset and it works. If I don't say ok google it doesn't work. It may be that it's actually my phone picking it up and not the Bluetooth mic but I hear the audio in my headset and can use it to search Google and play music. And it also picks up my audio in calls
I am on a regular pixel 2
Nealian said:
Hi everybody I think I may have found a possible fix/workaround
Settings\search\voice\Ok Google detection
Turn on ok Google anytime turn on trusted voice
(May have to do voice training)
Now when I press the call button and say "OK Google" then the command I hear it in my headset and it works. If I don't say ok google it doesn't work. It may be that it's actually my phone picking it up and not the Bluetooth mic but I hear the audio in my headset and can use it to search Google and play music. And it also picks up my audio in calls
I am on a regular pixel 2
Click to expand...
Click to collapse
I tried that.no go.. quite frustrated with this right now. Never realized how much I use this feature.
Sent from my Pixel 2 using Tapatalk
I am facing the same issue. When connected to my BT headset or car BT, it's like my mic mutes after the hot word. Also, some phone calls can't hear me at all. Have to hang up and call back, then no issues. I've also contacted support and sent in feedback with system info to create a ticket.
I was having different issues as well, so I wiped my device and manually put all of my stuff back on (vs doing a restore), just to see if this fixes anything. Haven't retried BT yet, but will this evening. Other issues appear to be gone and the phone feels a lot smoother since doing this though. I think my restore from my OG Pixel didn't go so well.
I have a problem with my bluetooth headsets. When I make calls every 10 or 20 seconds I got some annoying noise for maybe 1 or 2 seconds. The person on the other line can also hear this.
I have two different Chinese headsets that shows the problem. With Bluetooth speakers I do not have the same problems, but also short interruptions from time to time.
Currently I am using a Xiaomi Redmi 3 on the latest 14.1 nightly. With my old Samsung GT-i9300 I had the same problem on Lineagos. I can use both headsets without any problems on a iPhone. Some roms on my S3 worked also flawlessly.
Any ideas how this could be solved?