Related
Bluetooth appears to be broken on my Galaxy Nexus I can discover other bluetooth devices fine, and they can discover the Nexus, and pairing appears to be successful from either direction. But as soon as I try to connect/transfer a file immediately I get a notification on the Nexus saying 'connection unsuccessful', 'transfer cancelled by user' (when I didn't cancel anything!) etc.
I've tried this with three different devices (my old HTC Desire, my wife's HTC Legend and my MacBook Pro) with the same results on all three.
Has anyone else run into similar problems, or does this sound like I've got a faulty unit and should send it back? Is there anything I can do to troubleshoot this any further? (I've not rooted the phone and its running the stock Android 4 ROM).
I wish I had an answer; just got my Galaxy Nexus yesterday; it won't pair with any of my bluetooth(s) -- they were all working fine in my Droid so I know how to pair. Any suggestions? Help!! Thanks
After further investigation, it seems it's just outgoing connections that don't work on mine. I can transfer files from other devices to the GN fine, just can't transfer from the GN to any other devices. Haven't tried connecting to a headset or anything like that as I don't have one.
I asked an acquaintance who also owns a GN to test it out on theirs and they experienced exactly the same thing - everything works ok except for outgoing connections/transfers.
I'm wondering if its a software bug if that's the case. If it were hardware related you'd have thought the whole bluetooth thing would be broken.
FWIW: I have been able to pair and connect via bluetooth with my car, with no problem. Downloaded my phonebook to my car via bluetooth as well.
Bt phonebook pairing
I'm having BT issues as well with my G-Nex on Verizon. Will connect/pair with my car, works for making/receiving phone call audio, but will not synch the contact list. Thus, cannot use voice dial in my car (Nissan).
Have searched all over the internet, no real answers. Tried to disable the existing bluetooth PBAPservice as suggested somewhere else - no dice, and it just restarts itself anyway. I've seen some suggestion about rooting the phone and replacing the PBAPservice which may be my next step. Hate to root a phone this new when I may end up returning it if I can't make this work ... sorta a deal breaker for me.
Anyone have any suggestions? Could my phone just be defective? Seems like there are a number of BT issues around, but I can't find anything "official" acknowledging the issue(s) ..
Thanks ...
I'm having a problem with my new GNex bluetooth as well. I'm using a Blackberry Stereo Gateway (an A2DP adapter) in my car and it -does- work, but only after I toggle bluetooth off and back on again. That's kinda annoying.
Previously I had been using an Incredible and it was working fine.
Having problems with Bluetooth as well. I have a BlueFusion unit installed in my car. Worked perfectly fine with my Droid X. Every time I got in the car, it just connected and calls and music both played over the stereo fine. Got my Galaxy Nexus paired and it worked great. However, whenever I get back in the car and the Galaxy Nexus reconnects, the audio does not work. It says it's connected, it plays with no audio coming out of the phone or the car speakers though. Tried re-pairing, no go. Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
DoubleVision81 said:
...Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
Click to expand...
Click to collapse
Okay, I don't feel so bad now. Ouch.
---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------
cam30era said:
FWIW: I have been able to pair and connect via bluetooth with my car, with no problem. Downloaded my phonebook to my car via bluetooth as well.
Click to expand...
Click to collapse
Does A2DP work properly? And what sort of bluetooth device are you pairing with?
Same here, sending files works, receiving doesn't. Pairing with my bt headset also works fine....
Sent from my Galaxy Nexus using XDA App
mattots said:
Bluetooth appears to be broken on my Galaxy Nexus I can discover other bluetooth devices fine, and they can discover the Nexus, and pairing appears to be successful from either direction. But as soon as I try to connect/transfer a file immediately I get a notification on the Nexus saying 'connection unsuccessful', 'transfer cancelled by user' (when I didn't cancel anything!) etc.
I've tried this with three different devices (my old HTC Desire, my wife's HTC Legend and my MacBook Pro) with the same results on all three.
Has anyone else run into similar problems, or does this sound like I've got a faulty unit and should send it back? Is there anything I can do to troubleshoot this any further? (I've not rooted the phone and its running the stock Android 4 ROM).
Click to expand...
Click to collapse
I had this problem when I fist boot the Nexus and after the first boot of the update to 4.0.1. Reboot the phone, re-pairing the devices and everything is fine since then.
Sent from my GT-P7300
I can't even get my Nexus to pair with my car (Kufatec FISCON unit for Volkswagen). Just straight up error "unable to pair" when I try it. :/
And I have a problem as well. I did get it to pair with my PC but I can't send any files from my PC to Nexus (it works fine with Desire).
I have two Nexus (one is my wife's) and both car have Blackberry Bluetooth Gateways in them. In both cases I am seeing the same issue as the OP, the bluetooth will not connect automatically. However if I manually power on the bluetooth on the phone when the gateway is in connecting mode than they will connect. I never had a problem like this with previous phones.
Is there a official way to inform Samsung of this issue?
I'm also having problems with bluetooth on my Galaxy Nexus. I wanted to transfer files via bluetooth from my old Incredible 2 to my new Galaxy Nexus and it just wouldn't work.
Edit: A reboot appears to have fixed the problem.
DoubleVision81 said:
However, whenever I get back in the car and the Galaxy Nexus reconnects, the audio does not work. It says it's connected, it plays with no audio coming out of the phone or the car speakers though. Tried re-pairing, no go. Tried bluetooth on/off, no go. The only way to get it to work, is to reboot the phone every time I get in the car.
Click to expand...
Click to collapse
I have this same issue exactly - and had this issue after a System Update on my Droid Incredible for a few weeks before I ended up buying the Galaxy Nexus. I had hoped the new phone wouldn't have this issue. Anyways, it also seems to happen when I take a phone call.
Scenario: I'm listening to music over bluetooth to my bluetooth audio enabled headunit in my car. I receive a phone call, and toggle the bluetooth off so I can take the call privately over my phone's earpiece. When the call is finished, I toggle the bluetooth back on and the phone will connect - however the music is playing, but no audio comes through the phone nor the speakers of my car.
I started having this -exact- scenario issue when System Updates started rolling out for Droid Incredible, and they added the options for "Phone Audio" and "Media Audio" under the bluetooth options. Before these System Updates, my Droid Incredible had worked perfectly with bluetooth audio in my car.
Bluetooth Phone and Stereo
SnarfvsMaximvs said:
I'm having a problem with my new GNex bluetooth as well. I'm using a Blackberry Stereo Gateway (an A2DP adapter) in my car and it -does- work, but only after I toggle bluetooth off and back on again. That's kinda annoying.
Previously I had been using an Incredible and it was working fine.
Click to expand...
Click to collapse
I am having similar problems with both my car's BT phone and BT audio.The phone through my car gets terrible static until I stop and start Bluetooth again, which is dangerous on the highway.
I hope it can be fixed with a little software update.
I have the same problem with new nexus galaxy, pairs well with car bluetooth audio, can hear a confirmation beep on car speakers but no luck in the phone. It just stays on paired but not connected. It doesnt allow to remove pairing and redo it untill rebooting the device.
I'm also having issues with the bluetooth audio in my car. I pair okay with my Sony Xplod head unit, then when I turn off the car and reconnect, the GN starts playing music through the internal speaker instead of the car speakers.
I'm having the previously mentioned A2DP issue as well. Everything connects fine but occasionally, no audio is heard via the deck in my car. Phone calls via bluetooth work, just no A2DP audio.
For those having this same problem, you can fix issue by toggling airplane mode on and off. This is quicker than rebooting (which also fixes the issue).
This has to be a bug. I'm running 4.01. Anyone having the same issue with 4.02/4.03?
AdamUpNorth said:
I'm having the previously mentioned A2DP issue as well. Everything connects fine but occasionally, no audio is heard via the deck in my car. Phone calls via bluetooth work, just no A2DP audio.
For those having this same problem, you can fix issue by toggling airplane mode on and off. This is quicker than rebooting (which also fixes the issue).
This has to be a bug. I'm running 4.01. Anyone having the same issue with 4.02/4.03?
Click to expand...
Click to collapse
Yes. I just got mine last night...ran some errands today. Paired fine in my car, can make and receive calls through the car's audio system, but no sound. I'm running 4.02. Tried this with my BT headphones and the same thing happens.
The airplane mode trick works, however. Thanks!
Hopefully this will get fixed rather quickly!
I just bought a new car, 2017 Honda Accord Hybrid, that the cool kids refer to as HAH, anyways.....
Bluetooth output is sketchy at best.
Sometimes I get the side info like artist names and title songs.
Most of the time the sound has been playing from my phone speakers insteead of the car stereo.
Car indicates that the phone is connected but I cant get the output to function correctly.
Past ROMS and some apps have an output option but i cant seem to find any in youtube or play music.
Old 2012 Honda had no such issues.
thoughts or advice?
thanks
Maybe try to go back to stock and see what happens? What rom are you on?
Make sure you don't have any other Bluetooth devices outputting also like a smartwatch, it will interrupt your phone connection
Sent from my Pixel XL using Tapatalk
parakleet said:
Most of the time the sound has been playing from my phone speakers instead of the car stereo.
Click to expand...
Click to collapse
If you go to System Settings | Bluetooth and then click the gear icon on your current Bluetooth connection, it'll give you options to select media and phone.
Did you verify both were selected? If media is not selected then music won't play on your car stereo.
So I have a 2016 Accord EX-L...The Bluetooth connection is sketchy for me as well. To get it to work I sometimes I have to toggle the Bluetooth on and off on my phone...Sometimes I have to change to a different source on the car head unit and then back to Bluetooth for it to output correctly...Sometimes it shows it is connected but only outputs sound through the phone. Additional, phone calls never worked through Bluetooth in the car. All of this was improved for me through the February security patch. I connect more often automatically like it should and my phone calls work now. However, time to time I have the same issues. I've done some research since I got the phone and it seems to be an issue on 2016 accords and now looks like 2017 have them too. I am holding out that the 7.1.2 update will resolve this problem but I have not found a solution yet.
Sent from my Pixel XL using Tapatalk
CZ Eddie said:
If you go to System Settings | Bluetooth and then click the gear icon on your current Bluetooth connection, it'll give you options to select media and phone.
Did you verify both were selected? If media is not selected then music won't play on your car stereo.
Click to expand...
Click to collapse
Yes at the time of occurrence I verified that all the boxes were checked.
It was my first thought too, thanks
jetboy8090 said:
So I have a 2016 Accord EX-L...The Bluetooth connection is sketchy for me as well. To get it to work I sometimes I have to toggle the Bluetooth on and off on my phone...Sometimes I have to change to a different source on the car head unit and then back to Bluetooth for it to output correctly...Sometimes it shows it is connected but only outputs sound through the phone. Additional, phone calls never worked through Bluetooth in the car. All of this was improved for me through the February security patch. I connect more often automatically like it should and my phone calls work now. However, time to time I have the same issues. I've done some research since I got the phone and it seems to be an issue on 2016 accords and now looks like 2017 have them too. I am holding out that the 7.1.2 update will resolve this problem but I have not found a solution yet.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Sounds exactly like my experience.
Bluetooth issues are now getting a lot of press on the usual Android blogs and sites. Google acknowledges that they are working on it. So there is hope.
TonikJDK said:
Bluetooth issues are now getting a lot of press on the usual Android blogs and sites. Google acknowledges that they are working on it. So there is hope.
Click to expand...
Click to collapse
Yep! http://www.androidpolice.com/2017/0...-random-bluetooth-disconnects-pixel-pixel-xl/
Last update screwed up bluetooth for sure. Literally bought a new SUV a couple days before I got the update. The phone worked like a dream with the 12 speaker Sony head unit before and now can be a nightmare at times.
Looks like google has a fix, but no ETA on release.
http://phandroid.com/2017/02/24/google-identifies-bluetooth-issue-pixel/
At least Google admits something is wrong and a fix is in the works. I'm glad I don't have any issues on Resurrection Remix ROM with my 2013 toyota rav4.
Has anyone had any luck on getting their pixel to consistently connect to their Honda Accord? If I restart my phone it will be fine for the day but continue with the issue after that. Sometimes if I toggle "media audio" on and off it will connect normally. Other than that I have the same old issue. Has anyone solved this through rooting?
I have to toggle media on every time I connect to my Kia pixel kind of sucks
Sent from my Pixel XL using Tapatalk
Hey all,
So I got the OTA Oreo update a few days ago and my Bluetooth seems to be working better so far. It connects to my car consistently and fully (I can control it from the head unit and the song info displays).
Only once has it had an issue like it use to before the update where it shows it connects but plays music through the phone.
Hopefully the update solves some of the issues we have been having to deal with!
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.
Anyone else having issues with connecting the 7T to their car and getting audio going out of it? My OG Pixel didn't have a problem, but I have to toggle off/toggle on Bluetooth and then manually tap the car's bluetooth listing to get it to actually 'connect' the audio portion.
Rather annoying, considering I'm only in the car for a few minutes at a time, this either eats into the time entirely, or makes me sit in my car for a couple minutes before even driving to fiddle with the bluetooth settings.
Car has stock headunit, 2015 Evo X. Like I said, original Pixel XL had no issues, but this is annoying. I've tried changing bluetooth versions to no avail. I can see it connecting and dropping the bluetooth connection fairly frequently while staring at it and trying to 'get it going'. But once it connects, it stays there.
My bluetooth headphones (Some knock off cheap Chinese ones for $20) don't seem to have an issue.
My connection to my aftermarket stereo is fine. Just seems a little quieter than my last phone. Connecting is kind of slow too when I start my car but it is automatic.
I don't have any issues with connecting to all 3 cars (2014 Honda Accord, 2009 Pontiac G8 Gt and a 2018 Honda Fit) but I do agree that the volume seems a little lower than my previous phone (Galaxy S8).
Sent from my [device_name] using XDA-Developers Legacy app
Hmm. Weird. Is there anyway I can check for logs to find out what exactly is happening? I haven't rooted, just don't know if it's something I can naturally pull from Android as a whole.
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
My bluetooth is quiet, but its also static-y. I never had any issues with my G6 and now I get static clipping every 10 or so seconds. Its unbearable.
jagadeesh16 said:
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
Click to expand...
Click to collapse
I'm not really having an issue pairing it, but it's just connecting after pairing is the problem.
I have changed the default pin. I can see it popping up and down the car stereo a few times in the bluetooth settings before it just gives up.
As for the other issues, I'm not having a problem at all with audio volume, nor popping/static when it finally does connect.
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Phreak411 said:
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Click to expand...
Click to collapse
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Milkshakes00 said:
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Click to expand...
Click to collapse
LOL that would be my luck
.
My OnePlus 7t connects fine and phone works for calls on 2014 cts. The sound comes out of phone can change song on head unit but I can't get audio to play through car. Anyone else get this?
Yeah music stutters with car player... Only calls work. Music works on headphones etc. I couldn't find solution, did network reset, cleared cache. Nothing works.
Seriously!
I've wasted at least two hours already trying all the recommended steps: from flicking icons on and off to a full phone reset.
Still no connection to my Suzuki S-cross car. Multiple previous phones have connected effortlessly.
Even the $50 temporary five year old borrowed phone could handle it.
Anyone got any other suggestions? Yes, tried the AVRCP setting change from 1.4 to 1.6. That didn't work either...
Barebones system reset from scratch running O2 OS 10.0.6HD65AA
Any suggestions greatly appreciated.
I need to be able to talk and drive!
Reset the car radio and clear all pairing data if you can. Then try again.
autosurgeon said:
Reset the car radio and clear all pairing data if you can. Then try again.
Click to expand...
Click to collapse
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
mikefnz said:
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
Click to expand...
Click to collapse
Yep most have lots of tedious steps that are different model to model and if not followed exactly will cause this problem on occasion..
In my case music starts to be scrambled after 10 minutes or so of listening. When I take the phone (so the watch pops up) or turn on the screen it immediately works fine again, but when being put aside and the screen turns off, the issue starts again ..
Also in the early days of my previous 5t I had the same issues but some fix was delivered together with oxygen os update. And now the same story again
I have a different issue with Bluetooth:
- OP7T connects to car Bluetooth fine
- I can make/answer calls
- Bluetooth media works fine
The problem is with Google Assistant & car audio:
- it was working as intended until the latest update - 10.0.15 - I was pressing the button on the steering wheel the google assistant was answering questions through the car bluetooth, no need to switch to bluetooth media.
- after the latest update, when I press the button on the steering wheel, Google assistant pops on the phone , starts to answer question, but cuts off after 5 seconds. the command still goes through and Assistant still runs, but does not come up on the car audio.
- it looks like the Assistant is not connecting to the car as a hands free, but as to a bluetooth handsets.
Anyone experiencing this?
I tried to see if anyone posted a similar question but haven't found anything. Is anyone else having issues with their Pixel 6 Pro while connected to Android Auto? I have 3 issues that are bugging the crap out of me.
1. Every time I connect my phone to the car, it always pops up asking permission to connect to this "new" uConnect device. Its been connected hundreds of times, and even adding it as a trusted device, it still pops up.
2. The sound quality is absolute garbage. Its muddy and heavy on the mid level. I have tried to compensate by adjusting the EQ in the head-unit, and Spotify. It helps, but not much. I have tried my old Note 10+ and the quality is perfect.
3. Often when receiving a phone call, I can answer and control the call using the head-unit, but the audio is going to the phone and not the car speakers.
I have been able to replicate this with both of our Pixel 6 Pro's, and in both of our vehicles (2019 Durango R/T, and 2020 RAM 2500)
Anyone have any ideas?
EDIT: this is wired using different cords for troubleshooting purposes.
I have none of those issues but my issue with aa is that it keeps turning off preview incoming message
Issue #3 I do get from time to time. Annoying AF. Also trusted device only last 4 hours I believe which I think is ridiculous.
imo... Spotify always sounds like crap.
Haven't had any of these issues at all. Everything works well for me on the December update.
I have none of these issues, but the issue I get is specific to Google Maps on Android Auto. When I'm navigating somewhere, often at the start of the trip Google Maps cannot get a GPS lock on me and the map skips all over the place, constantly rerouting me. After I continue to drive I eventually will get GPS lock and then everything works fine.
Using Waze on Android Auto, everything works fine. I get GPS lock instantly when I switch to the Waze app on Android Auto. So all I can conclude is the issue is specific to Google Maps... It's not that big of a deal but can be very annoying.
Edit: I'm on wireless with a Pioneer AVH deck.
My wifes Pixel 6 works fine apart from the battery icon constantly flashing on and off (on the car display)
I don't have any issues with Android Auto in my 2020 Subaru, and neither does my wife.
No, I don't have these issues either. Working fine for me on Lexus NX.
Edit: "wired" that is (to be clear).
I am not seeing any issues in my 2020 Kia Soul. I use the wireless android auto adapter (AAWireless from Indiegogo) so I do not have to plug it in though.
Could your uConnect system need an update? You can check here for one: https://www.driveuconnect.com/support/software-update.html
Caveman419 said:
I am not seeing any issues in my 2020 Kia Soul. I use the wireless android auto adapter (AAWireless from Indiegogo) so I do not have to plug it in though.
Could your uConnect system need an update? You can check here for one: https://www.driveuconnect.com/support/software-update.html
Click to expand...
Click to collapse
Great Idea, unfortunately they are already up to date on the software. That AAWireless thing is pretty cool, but plugging it in doesn't bother me that much, plus I know its charging.
GtarSkater said:
Great Idea, unfortunately they are already up to date on the software. That AAWireless thing is pretty cool, but plugging it in doesn't bother me that much, plus I know its charging.
Click to expand...
Click to collapse
I always have issues with cables that keep disconnecting and have to unplug and re-plug in (both my car & my wife's 2016 Hyundai Sonata). The AAWireless is very handy in that regards. It will occasionally freeze up, but very rarely after a few OTAs ago. The only downside that I have found is that if you get too close to the vehicle with BT Headphones (mowing or other yardwork typically), it will connect to the AAWireless and cut off audio to the BT Headphones. I just unplug the AAWireless from the car until I am done then.
I should mention all my issues only occur when I'm wireless in my car. When I use wired in my friends car, it works fine.
GtarSkater said:
I tried to see if anyone posted a similar question but haven't found anything. Is anyone else having issues with their Pixel 6 Pro while connected to Android Auto? I have 3 issues that are bugging the crap out of me.
1. Every time I connect my phone to the car, it always pops up asking permission to connect to this "new" uConnect device. Its been connected hundreds of times, and even adding it as a trusted device, it still pops up.
2. The sound quality is absolute garbage. Its muddy and heavy on the mid level. I have tried to compensate by adjusting the EQ in the head-unit, and Spotify. It helps, but not much. I have tried my old Note 10+ and the quality is perfect.
3. Often when receiving a phone call, I can answer and control the call using the head-unit, but the audio is going to the phone and not the car speakers.
I have been able to replicate this with both of our Pixel 6 Pro's, and in both of our vehicles (2019 Durango R/T, and 2020 RAM 2500)
Anyone have any ideas?
Click to expand...
Click to collapse
Personally, I do not have an Android Auto enabled car.
I can tell though that there were numerous reports in the past (XDA, Reddit, Discord, Telegram) of people having problems with Android Auto. Now the problem with that, is...
a) Android Auto has always been buggy - even with cable. I have friends that have been trying to get Android Auto to reliably work with their Samsungs (cable) for years, and their attempt are still a work in progress. It's a hit-and-miss. Sometimes it works, sometimes it doesn't.
b) Android 12 is extra buggy and has been known to cause problems with Android Auto (reports of Samsung owners upgrading to A12)
c) Pixel 6 Pro is extra special buggy and it's more or less unknown at this point, if Android Auto issues are caused by Auto Auto being a buggy mess, Android 12 being a buggy mess, Pixel 6 being a buggy mess or a culmination of the three together.
d) Plus, there is a massive difference in reliability between Android auto cable vs. wireless.
I did see some workarounds floating in the web, you might be able to find them in Reddits GooglePixel group.
In the end though, your best bet (longterm) would probably be: Go into settings, report the problem directly to Google and make sure that all your friends and family that also use Android Auto do the same.