Related
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!
So I had been on the beta version since it was released and participated a few times in the thread here: https://forum.xda-developers.com/pixel-xl/how-to/android-o-beta-issues-t3609335 and others were having the same issue.
The issue is no song/artist information being displayed on my touchscreen stereo, and I cannot use the stereo to pause/skip to the next track (I have to do it through my phone). Ive tried a local audio player, Google Music, and Pandora all to no avail. The deck is a Pioneer double-din AVH-P8400BH.
In my daily car, my phone bluetooth name appears and I can change song ect thru the deck. It is not a touchscreen and it probably 10 years old.
Ive gone into the bluetooth settings and have tried changing the AVRCP from 1.4 to 1.6 (neither work), and audio codec from default to enable optional (neither worked).
Anything else I should try out?
TIA
Please add your experiences to this website... they currently have over 100 replies of this issue and some other Bluetooth issues. https://productforums.google.com/fo...eDphsoOJ4;context-place=forum/phone-by-google
I had the same issue, but a simple unpair and forget from both devices then repair fixed my problem
marcjc said:
Please add your experiences to this website... they currently have over 100 replies of this issue and some other Bluetooth issues. https://productforums.google.com/fo...eDphsoOJ4;context-place=forum/phone-by-google
Click to expand...
Click to collapse
Ill throw in my comments, thanks for the link!
mjc2251 said:
I had the same issue, but a simple unpair and forget from both devices then repair fixed my problem
Click to expand...
Click to collapse
Ill have to give this a shot!
mine has awful streaming. It has so many skips...snags...audio blanks...whatever term you want to call it....its not "uninterrupted".
I was hoping google IMPROVED Bluetooth. I don't understand why they have this struggle to be honest. Its 2017....Bluetooth is not new technology.
Maybe they should stop expanding their department to provide data to the government to spy on private citizens using smart devices, and they would use those resources to fix bluetooth
Pioneer brand head units in particular I have seen Bluetooth streaming issues when paired to flagship model phones for years...even back as far as my LG G3. I got a Kenwood head unit instead, never had an issue.
As far a the Pixel XL and BT streaming...I have only had issues with dropouts zap sounds or pops, when i am out mowing my back property with my tractor...phone in pocket and BT headphones on. But my previous phones did this...most certainly due to the railroad nearby and high rise high voltage power lines and towers that are above me in that area.
speedingcheetah said:
Pioneer brand head units in particular I have seen Bluetooth streaming issues when paired to flagship model phones for years...even back as far as my LG G3. I got a Kenwood head unit instead, never had an issue.
As far a the Pixel XL and BT streaming...I have only had issues with dropouts zap sounds or pops, when i am out mowing my back property with my tractor...phone in pocket and BT headphones on. But my previous phones did this...most certainly due to the railroad nearby and high rise high voltage power lines and towers that are above me in that area.
Click to expand...
Click to collapse
Pioneer uses a cheaper bluetooth and never updates the firmware of the chips to fully support the available Bluetooth profiles even when they are developing their units and new profile updates are available. I have had a very long and annoying history with them to the point where I was in direct contact with their build team after all my complaining. That was back in 2012. Never used another of their products again. :good:
I have the same issue on my Chevy Colorado 2017. Everything works fine on Spotify on my Huawei Mate 9, and iPhone 7. It also worked fine on 7.1.2. Spotify works and music comes through but no info is displayed. I unpaired both things with no success. Frustraring.
I tried unpairing mine as well, no luck either
stupidchicken03 said:
I tried unpairing mine as well, no luck either
Click to expand...
Click to collapse
Have you tried unticking "media" in the profile hitting ok, going back in and ticking media again?
pcriz said:
Have you tried unticking "media" in the profile hitting ok, going back in and ticking media again?
Click to expand...
Click to collapse
I have not. Ill give it a shot today.
No idea if this problem is related or not but might be worth a check if you have time. First time I put Oreo on my phone it was fine. Then I screwed something up and just ADB flashed the image again. Everything was fine until I tried bluetooth a few days later. It wouldn't connect until ticking that media box many times. Then I flashed the image again and it worked fine again.
So I just got the 8.0 OTA (not on beta). I see in the dev options that it shows what BT codec it is using.
I have noticed that only the option "Bluetooth AVRCP Version:" is the only value that changin it does it stick. The other setting appear to be on auto and revert to auto depending on what device u pair supports.
My first test on my Kenwood KDC-BT762HD it paired fine and it said it was using AptX. Streamed for a few min fine. Then after I got back in the car and it auto paired, music started skipping every several seconds. I turned radio off then on to repair it and it started streaming fine again....but was using SBC according to Dev options.
When I changed AVRCP version to 1.6.....it connects and uses AptX fine. However, the radio display no longer displays the BT media metadata(title/artist), but the controls on the radio still work. I change to AVRCP ver 1.4 and that restores metadata, but then it uses SBC again. (using ver 1.5 results in SBC and no metadata).
I don't really care about the song info not being displayed on my radio....but definitely seems to be something fishy with BT in this new update.
EDIT Update: so now I am noticing it auto re-connecting and using SBC all the time now. WOnt use aptX unless i delete the device and re-pair it. then it works for a few reconnects, but then drops to sbc cagin.
Thanks for posting, I won't be updating. The Bluetooth has never been right and now seems to have regressed.
Sent from my SM-T280 using Tapatalk
i think i'm having slightly fewer drop outs with oreo than with nougat. my moto x pure on marshmallow was really bad.
FZ1Darren said:
i think i'm having slightly fewer drop outs with oreo than with nougat..
Click to expand...
Click to collapse
i agree and although i dont get the proper song listing on my car stereo it seems everything else is better. on nougat my BT headset i use for work all day (moto buds) would often stop connecting properly and i would make a call and have to select "phone" then "headset" again to get audio back on headset and om Oreo it happens less frequently
fletch33 said:
i agree and although i dont get the proper song listing on my car stereo it seems everything else is better. on nougat my BT headset i use for work all day (moto buds) would often stop connecting properly and i would make a call and have to select "phone" then "headset" again to get audio back on headset and om Oreo it happens less frequently
Click to expand...
Click to collapse
If you switch to a rom that uses the CAF based bluetooth (all lineageos based ones should, crDroid does for sure as that is what I use) implementation this won't happen. Still haven't been able to track down exactly why, but for now I'm sticking with CAF based ROMs to avoid this.
Do any of you guys having this issue have an Android wear watch? I've had heaps of issues with Bluetooth streaming being all "jittery" and just skipping since the update. However, I found this is basically completely fixed when I turn my android wear (LG urbane) off, or at least the Bluetooth on it.
Tried all the developer options for BT but hasn't made a difference. At the moment, my solution is turning off BT on my watch when I'm listening to music. Bit crap but it works.
I have factory reset the watch and cleared BT cache on pixel.
Any other ideas?
Is anyone else still having problems with Bluetooth on Oreo? I was hoping the official 8.1 release would help me, but I'm seeing no change. I have a Kenwood BT952HD, and experience issues similar to what the OP describes. Audio is plays fine, no unreasonable stuttering. But I get no song info, and can't skip tracks. Also, the pairing isn't as automatic. Every time I turn on the car, I have to wake the phone up, and wait for the pairing to complete, which takes longer than usual.
I've tried playing with the AVRCP settings, along with clearing registrations at both ends and repairing, with no luck. Is anyone else still seeing similar issues?
8.1 working fine with my Kenwood BT762HD. I use PowerAmp v2 alpha build 704 app.
Bluetooth was working fine until today. Out of nowhere, the phone wouldn't connect to my car that it was connected to prior.
Tried toggling BT off and on, didn't work. Tried rebooting the phone, still won't connect. Tried deleting the phone from the car and re-syncing it, didn't work. Other phones still connect, so it isn't an issue with the car.
Anyone have any ideas for me?
a.demarco said:
Bluetooth was working fine until today. Out of nowhere, the phone wouldn't connect to my car that it was connected to prior.
Tried toggling BT off and on, didn't work. Tried rebooting the phone, still won't connect. Tried deleting the phone from the car and re-syncing it, didn't work. Other phones still connect, so it isn't an issue with the car.
Anyone have any ideas for me?
Click to expand...
Click to collapse
call support asap..
I've read of BT issues and Oreo in general. My phone connected to my car, but I cannot use it for hands-free phone, music/media only.
Jaybird Freedom F5 headphones, fwd/back, vol up/down worked fine, but start/stop for reasons unknown did not work without kicking on/off Assistant first. That was yesterday. Today all fine. no idea why.
Problematic in
Cloud Player
Spotify
Smart Audiobook Player
I have Button Mapper to enable squeeze to launch flashlight, and even after setting up headphone button to start/stop yesterday, after several reboots it still didn't work properly. Today, however, all behaving NORMAL.
I haven't been able to have my phone connect to my car since I've gotten this. Looks like it connects then when my car asks for me to name it, it says pairing failed. Going to check and see if I can connect it to my sound bar tomorrow morning. Hopefully they push an update that fixes it
I have two pixel 2 XLs one would connect to my Bose SoundLink mini for a few seconds and disconnect repeatedly. The other one, is perfect and have no issues.
I have the same bluetooth issue. My 2XL paired with my car without any problems but won't stay connected. If I connect and make a call it stays connected for the call but disconnects when I hang up the call. My S5 always connected automatically when I turned on the car.
cavediver said:
I have the same bluetooth issue. My 2XL paired with my car without any problems but won't stay connected. If I connect and make a call it stays connected for the call but disconnects when I hang up the call. My S5 always connected automatically when I turned on the car.
Click to expand...
Click to collapse
I also am having exact same issue on my P2XL. Paired and connected fine first time, played a ton of Spotify, haven't been able to get it to reconnect ever since. Need to check another phone in car as well as check P2XL with another BT device. Will report back but I may just exchange it as I am within in 14 days. It very well could be software related but don't want to risk them giving me a refurb once I am outside 14 days. Rather get the brand new one and if issue persists, hope that it is resolved in software update.
Report back soon.
EDIT: My phone pairs with everything BT very very quickly; however, it will never connect. I still have several days left on my exchange for brand new device period (they extended it from 15 to 21 days per the Google rep I just spoke with). I am inclined to just exchange and get a brand new one versus waiting until outside of that period and exchanging for a potential refurb; however, I noticed that Google now provides what we are getting in our updates before they come and the November update is full of Pixel 2 and Pixel 2 XL bluetooth fixes so I think I might hold out to see if that fixes our issues, most of them seem specific to our issues of connectivity.
https://www.androidcentral.com/pixe...tw_card&utm_content=63809&utm_campaign=social
Hope this helps.
a.demarco said:
Bluetooth was working fine until today. Out of nowhere, the phone wouldn't connect to my car that it was connected to prior.
Tried toggling BT off and on, didn't work. Tried rebooting the phone, still won't connect. Tried deleting the phone from the car and re-syncing it, didn't work. Other phones still connect, so it isn't an issue with the car.
Anyone have any ideas for me?
Click to expand...
Click to collapse
NOSTALGIA said:
call support asap..
Click to expand...
Click to collapse
WorldOfJohnboy said:
I've read of BT issues and Oreo in general. My phone connected to my car, but I cannot use it for hands-free phone, music/media only.
Click to expand...
Click to collapse
enzeem2010 said:
Jaybird Freedom F5 headphones, fwd/back, vol up/down worked fine, but start/stop for reasons unknown did not work without kicking on/off Assistant first. That was yesterday. Today all fine. no idea why.
Problematic in
Cloud Player
Spotify
Smart Audiobook Player
I have Button Mapper to enable squeeze to launch flashlight, and even after setting up headphone button to start/stop yesterday, after several reboots it still didn't work properly. Today, however, all behaving NORMAL.
Click to expand...
Click to collapse
Lawlrus said:
I haven't been able to have my phone connect to my car since I've gotten this. Looks like it connects then when my car asks for me to name it, it says pairing failed. Going to check and see if I can connect it to my sound bar tomorrow morning. Hopefully they push an update that fixes it
Click to expand...
Click to collapse
shinasurada said:
I have two pixel 2 XLs one would connect to my Bose SoundLink mini for a few seconds and disconnect repeatedly. The other one, is perfect and have no issues.
Click to expand...
Click to collapse
cavediver said:
I have the same bluetooth issue. My 2XL paired with my car without any problems but won't stay connected. If I connect and make a call it stays connected for the call but disconnects when I hang up the call. My S5 always connected automatically when I turned on the car.
Click to expand...
Click to collapse
Hi all,
Just downloaded the November release and can confirm that Fast Pair works now and BT is fully functional. I forgot the device on my car and on my phone upon reboot after installing the update. Turned my car on, turned BT on and it really paired and connected within seconds. Tested with 3 more speakers and even went back to car to test again. All good to go. There were a ton of patches listed for BT specific to P2 and P2XL, glad they fixed this so quickly.
cwburns32 said:
Hi all,
Just downloaded the November release and can confirm that Fast Pair works now and BT is fully functional. I forgot the device on my car and on my phone upon reboot after installing the update. Turned my car on, turned BT on and it really paired and connected within seconds. Tested with 3 more speakers and even went back to car to test again. All good to go. There were a ton of patches listed for BT specific to P2 and P2XL, glad they fixed this so quickly.
Click to expand...
Click to collapse
Where do you get the November release? I just checked system updates and nada.
Regardless, I fixed my BT issue with Google support's help... press and hold home button. Press blue icon in upper right. Press three dots, then settings. Tap phone, then scroll down to other voice settings. Make sure Bluetooth headset is enabled. Also, reset your network settings. Delete the pairing on your car, then pair again. Mine worked like a charm.
WorldOfJohnboy said:
Where do you get the November release? I just checked system updates and nada.
Regardless, I fixed by BT issue support's help... press and hold home button. Press blue icon in upper right. Press three dots, then settings. Tap phone, then scroll down to other voice settings. Make sure Bluetooth headset is enabled. Also, dessert network settings. Delete the pairing on your car, then pair again. Mine worked like a charm.
Click to expand...
Click to collapse
I just went into System Updates and checked and it was available. It started rolling out today, I am sure you get it soon. I tried support's help, made sure BT headset was enabled, deserted network settings and deleted pairing on car and phone multiple times to no avail. With the new update I can swap between 2 different BT speakers almost instantly. The update includes many other fixes/improvements. Some to do with screen, most of that though coming in December patch I believe.
EDIT: added screenshot of About Phone screen to show November 5th patch. Hope you get yours soon!
cwburns32 said:
I just went into System Updates and checked and it was available. It started rolling out today, I am sure you get it soon. I tried support's help, made sure BT headset was enabled, deserted network settings and deleted pairing on car and phone multiple times to no avail. With the new update I can swap between 2 different BT speakers almost instantly. The update includes many other fixes/improvements. Some to do with screen, most of that though coming in December patch I believe.
Click to expand...
Click to collapse
I don't see anything. I'm on 8.1 though. I'd downgrade if this works, but hopefully there is a patch for 8.1 too.
Moostafa29 said:
I don't see anything. I'm on 8.1 though. I'd downgrade if this works, but hopefully there is a patch for 8.1 too.
Click to expand...
Click to collapse
Not sure if there is a November patch for the dev version just yet, I'm sure there will be but might not be on the 5th/6th like we are used to seeing. Could be wrong though. I do know they started rolling it out today so it might just take a bit to get to you, I didn't see it this afternoon around 2 pm but did around 5 pm. Hope this helps.
WorldOfJohnboy said:
Where do you get the November release? I just checked system updates and nada.
Regardless, I fixed by BT issue support's help... press and hold home button. Press blue icon in upper right. Press three dots, then settings. Tap phone, then scroll down to other voice settings. Make sure Bluetooth headset is enabled. Also, dessert network settings. Delete the pairing on your car, then pair again. Mine worked like a charm.
Click to expand...
Click to collapse
Thank you sir, this worked for my new to me, Original Pixel XL that replaced my 6P.
Sent from my Pixel XL using Tapatalk
CTownTap said:
Thank you sir, this worked for my new to me, Original Pixel XL that replaced my 6P.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
NP, glad you could understand me--I just realized the typos I had in my original post, so I edited it...
Is the Bluetooth power level changing for anyone since the November patch? I've been running Jaybird X2 since early this morning and there is no way I'm still at 100% four hours later. I paired them after the patch. Turned them off and on, Bluetooth off and on. I'll try rebooting next, but it's strange all the same.
edited: still 100% (4hrs use)
edited2: now 60% (6hrs use)
These typically have 8-10 hours use per charge.
edited3: now 10% (9hrs?)
I didn't see when it changed or what the increments were.
"Battery Low" warning at 20 minutes power left.
Anyhow, just my experience.
enzeem2010 said:
Is the Bluetooth power level changing for anyone since the November patch? I've been running Jaybird X2 since early this morning and there is no way I'm still at 100% four hours later. I paired them after the patch. Turned them off and on, Bluetooth off and on. I'll try rebooting next, but it's strange all the same.
edited: still 100%
Click to expand...
Click to collapse
I noticed this too, not a huge issue for me as most, if not all, of my BT devices have battery indicators on them. I don't typically go into BT settings to check battery of BT devices but that's just mw
Audio through Bluetooth for Google Assistant still isn't working for me with the November update. I've delete my headset and re-paired it but on activating Google Assistant with my headset, it still doesn't pick up my voice through my headset mic. [emoji17]
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Audio through Bluetooth for Google Assistant still isn't working for me with the November update. I've delete my headset and re-paired it but on activating Google Assistant with my headset, it still doesn't pick up my voice through my headset mic. [emoji17]
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
This sucks.
I have the same problem where I can't use Google Assistant in my car. It won't listen through Bluetooth or play sound over speakers
Sent from my [device_name] using XDA-Developers Legacy app
So, since I got my 3xl in October, the audio information would not show in my truck. A person on here showed me the dev settings to make this work back in like December or January (out of the box settings do NOT work though, which is ridiculous). And it did, at least until the February patch. Now it works sometimes, others it either doesn't show, or shows the info from the first song indefinitely. Also, when I first got it, there was no skipping (like my 2xl did the entire time I had it), after the November update, it skips... Is anyone else having any of these issues? I've messed around with the Bluetooth settings in dev options, and nothing seems to work for long. This is super annoying. I have an hour round trip commute, and I drive a lot otherwise, so, being able to see what's playing is important.
How does Google mess up Bluetooth so bad anyway? I've had like 6 other Android phones, and NONE of them ever had stupid issues. Seems like Google needs to hire some better engineers for dealing with it.
I'm sorry to hear you're having this experience. I've never had a single Bluetooth problem.
I have not so good experience with Bluetooth as well. Sometimes my Samsung gear S3 doesn't auto connect. I need to go into settings.
Bluetooth is crap on this phone totally agree otherwise good phone but disappointed in bt performance
I actually did a factory reset when the January patch came out even. Didn't fix it at all.
What developer settings are you talking about? I haven't had any real bluetooth issues, BUT, almost all of my recent flagships have had audio delay issues through bluetooth. It's not a lot, but it's annoying watching Youtube with about a second delay.
kos26 said:
What developer settings are you talking about? I haven't had any real bluetooth issues, BUT, almost all of my recent flagships have had audio delay issues through bluetooth. It's not a lot, but it's annoying watching Youtube with about a second delay.
Click to expand...
Click to collapse
Bluetooth AVRCP version. You can change which version it uses. It's kind of a trial and error but sometimes you get lucky and find that a different version works better with some of your Bluetooth devices.
TonikJDK said:
Bluetooth AVRCP version. You can change which version it uses. It's kind of a trial and error but sometimes you get lucky and find that a different version works better with some of your Bluetooth devices.
Click to expand...
Click to collapse
Hm, I'll have to try that tomorrow with the car and see if I still have a delay, that would be awesome to fix. It is a 2013 so it's using old tech
What kind of head unit are you talking about in your car? Some specs there might be helpful to determine if this is a phone specific issue or has to do with your car's stereo itself. Reason I say this is my old Kenwood KDX-897 receiver in my truck started acting up with Bluetooth and I was able to confirm it's the receiver itself that's having issues not my phone. Not surprising considering the unit is probably about 5 years old now from when I bought it new. You may want to look into updating your receivers firmware which may solve this issue (if possible) or looking at a new head unit. Just some food for thought.
gettinwicked said:
So, since I got my 3xl in October, the audio information would not show in my truck. A person on here showed me the dev settings to make this work back in like December or January (out of the box settings do NOT work though, which is ridiculous). And it did, at least until the February patch. Now it works sometimes, others it either doesn't show, or shows the info from the first song indefinitely. Also, when I first got it, there was no skipping (like my 2xl did the entire time I had it), after the November update, it skips... Is anyone else having any of these issues? I've messed around with the Bluetooth settings in dev options, and nothing seems to work for long. This is super annoying. I have an hour round trip commute, and I drive a lot otherwise, so, being able to see what's playing is important.
How does Google mess up Bluetooth so bad anyway? I've had like 6 other Android phones, and NONE of them ever had stupid issues. Seems like Google needs to hire some better engineers for dealing with it.
Click to expand...
Click to collapse
Do you have any issues with headphones or other bluetooth speakers?
rspkt said:
What kind of head unit are you talking about in your car? Some specs there might be helpful to determine if this is a phone specific issue or has to do with your car's stereo itself. Reason I say this is my old Kenwood KDX-897 receiver in my truck started acting up with Bluetooth and I was able to confirm it's the receiver itself that's having issues not my phone. Not surprising considering the unit is probably about 5 years old now from when I bought it new. You may want to look into updating your receivers firmware which may solve this issue (if possible) or looking at a new head unit. Just some food for thought.
Click to expand...
Click to collapse
It's the stock 2018 Nissan Pathfinder head unit. I did not have the info not showing problem with my 2xl with the same SUV. I'll check if there's an update when I have it in the shop in a couple weeks. It DID work fine though before the Feb. update. I did have to change the dev settings though, as I said, out of the box did not work... The cutting out seems to have gone away, at least for now, so, that's an improvement. Hopefully, the March patch fixes the other issue.
Also, there is not cutting out that I've heard ever on my Bluetooth speaker. Obviously, it does not show audio info.
gettinwicked said:
It's the stock 2018 Nissan Pathfinder head unit. I did not have the info not showing problem with my 2xl with the same SUV. I'll check if there's an update when I have it in the shop in a couple weeks. It DID work fine though before the Feb. update. I did have to change the dev settings though, as I said, out of the box did not work... The cutting out seems to have gone away, at least for now, so, that's an improvement. Hopefully, the March patch fixes the other issue.
Also, there is not cutting out that I've heard ever on my Bluetooth speaker. Obviously, it does not show audio info.
Click to expand...
Click to collapse
I have the same issue on my 2011 Mazda 3, though my OnePlus 6 works with it fine. Of course, the OP6 can't connect to by earbuds, so there is that. Audio does seem to be working fine, no drop outs or anything, but that track info seems to be gone for good. None of the AVCRP options worked for me beyond 1-2 songs either. Though, in my case, it's been that way since Marshmallow - I've always kind of assumed it was the updated BTs, they're backwards compatible for the audio, but not for the track info it seems. Once we hit 4.0 it dropped out (again except the OP6).
Seamonkey79 said:
I have the same issue on my 2011 Mazda 3, though my OnePlus 6 works with it fine. Of course, the OP6 can't connect to by earbuds, so there is that. Audio does seem to be working fine, no drop outs or anything, but that track info seems to be gone for good. None of the AVCRP options worked for me beyond 1-2 songs either. Though, in my case, it's been that way since Marshmallow - I've always kind of assumed it was the updated BTs, they're backwards compatible for the audio, but not for the track info it seems. Once we hit 4.0 it dropped out (again except the OP6).
Click to expand...
Click to collapse
I should also add, my wife's Moto Z2 Force has ZERO issues with my Pathfinder. It shows info always, no cutouts, nothing at all, and out of box Bluetooth settings. I really doubt it's my SUV's head unit. It also has Bluetooth 5.
the weirdest things happen to me with bluetooth.. even on the latest update.. i'll be streaming to my wireless jabra's and all of a sudden music stops. it's not disconnected. music didn't pause but it isn't playing either, i have to start the track over, doesn't happen otherwise .
PS it happens the same to my bluetooth speaker
almost same here with latest updates.
masri1987 said:
the weirdest things happen to me with bluetooth.. even on the latest update.. i'll be streaming to my wireless jabra's and all of a sudden music stops. it's not disconnected. music didn't pause but it isn't playing either, i have to start the track over, doesn't happen otherwise .
PS it happens the same to my bluetooth speaker
Click to expand...
Click to collapse
bush911 said:
almost same here with latest updates.
Click to expand...
Click to collapse
it's so annoying, i yelled out at my phone in frustration yesterday when it did it 9 times while at home playing music via bt speaker
I can definitely confirm the Feb. update didn't fix my problem. I even removed the phone from my car and vice versa, nada. I just cleared data from YouTube music then reinstalled. I'm going to see what that does. If nothing, I give up. This is seriously going to become a deal breaker if they can't make their sh$t work right... Music is what I use this phone the most for.
gettinwicked said:
I can definitely confirm the Feb. update didn't fix my problem. I even removed the phone from my car and vice versa, nada. I just cleared data from YouTube music then reinstalled. I'm going to see what that does. If nothing, I give up. This is seriously going to become a deal breaker if they can't make their sh$t work right... Music is what I use this phone the most for.
Click to expand...
Click to collapse
Sooo, I cleared the data and reinstalled YouTube music. It seemed to work, even so I was able to put Bluetooth on the out of box settings (codec). Or, so I thought... It worked for two days then out of nowhere it won't show the info at all again, no matter what I change the settings to... I've reconnected and reinstalled again. Nothing. This is effing ridiculous. $950 phone and Bluetooth, which has been out since the mid 2000's, won't work right. This is really starting to sway me towards looking for a different phone. If I can find a stock Android one that releases updates within 30 days or so anyway. Ugh
gettinwicked said:
It's the stock 2018 Nissan Pathfinder head unit. I did not have the info not showing problem with my 2xl with the same SUV. I'll check if there's an update when I have it in the shop in a couple weeks. It DID work fine though before the Feb. update. I did have to change the dev settings though, as I said, out of the box did not work... The cutting out seems to have gone away, at least for now, so, that's an improvement. Hopefully, the March patch fixes the other issue.
Also, there is not cutting out that I've heard ever on my Bluetooth speaker. Obviously, it does not show audio info.
Click to expand...
Click to collapse
I have a 2018 Pathfinder work a pixel 3 xl too. I do have strange Bluetooth issues too. However I blame the Pathfinder because when I use my Jabra Bluetooth receiver and my motion66 Bluetooth earphones the Pathfinder is the only way that is wonky.
The worst thing with the Pathfinder is the delay. I think it buffers the audio for me so everything is delayed. I push play/pause on the Pathfinder and there is a several second delay. Additionally when streaming YouTube and audio through Pathfinder there is a delay.
Sent from my Pixel 3 XL using Tapatalk
icanrule said:
I have a 2018 Pathfinder work a pixel 3 xl too. I do have strange Bluetooth issues too. However I blame the Pathfinder because when I use my Jabra Bluetooth receiver and my motion66 Bluetooth earphones the Pathfinder is the only way that is wonky.
The worst thing with the Pathfinder is the delay. I think it buffers the audio for me so everything is delayed. I push play/pause on the Pathfinder and there is a several second delay. Additionally when streaming YouTube and audio through Pathfinder there is a delay.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Mine seems to work with my Plantronics headphones and my Anker speaker fine also. Thing is though, this was not a problem with my 2xl. It cut out a bit, but always showed the info and no delay. My 3xl stopped cutting out with the Feb update, but the audio info is all over the place. It's currently back. It'll start being crazy again I'm sure. I'm not sure I can blame my Pathfinder though? I will try with my wife's Mazda 3 (2016) to see what happens there. My wife's Moto Z2 Force works perfectly with my Pathfinder BTW.
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.