I have a 2015 Hyundai Sonata. The G4 will not display any data when connected to Bluetooth in my car. GS6 works, iPhone 6+ works, gs5 works... It isn't working in My wife's 2015 Santa Fe either, or the 2015 F150 at work... I know this has been discussed, just curious if anyone has had similar issues in their respective vehicles, THEN solved it? I tryed cache clearing, uninstalling Google Music, then reinstalling. It doesn't work on any media apps, native or 3rd party. It's minor as the functions work, just really annoying.
The latest update from Verizon fixed this.
I hope it fixes the fact bluetooth messaging can't be turned off permanently. I hate having the Dodge read messages every time it's started.
Related
I have a new Note 4 (Verizon) and a 2011 Kia Soul. Prior to the Note 4 I had a Note 2 (Verizon) that I paired with my car for the last 2 years without issue. I am able to successfully pair the Note 4 and the car and use all of the Bluetooth functions I would expect to work. The problem is, often (not 100% of the time), the next time I try to connect the phone to the car that connection fails. I then have to unpair and re-pair them to get them to connect. Neither side gives me anything useful in the way of error messages.
I'm at a loss as to how to troubleshoot this further. Is there a way to pull Bluetooth connection logs out of the phone?
I have the same issue, but worse. I have a 2011 KIA Sorento, and a Samsung Note 4. The Bluetooth connectivity is very intermittent. One minute is works and then stops. One minute it plays music fine and all of a sudden, the music will start going in and out, like a bad cellphone call and then disconnect. I try to reconnect and it won't. I've gotten in the car and it works great and the next time it works like crap! I've been on a cell call, talking through Bluetooth and it will automatically disconnect, but still shows connected. I have to switch to speakerphone to talk and then it all of a sudden reconnects back to Bluetooth. Does anyone know if this is a known Samsung issue? I saw a previous post from Dec 2014 which stated, " Apparently, the Note 4 and Edge all use the newest AVCRP 1.5, which nobody else uses yet. Nissan told me that they were told by Samsung, that in their next update, they're going to revert the phones back to AVCRP 1.3, which is the standard in the industry." Has this occurred?
I had the same kind of problems with my Galaxy S 6 on my 2013 F150 with Sync. I was only able to fix it by getting rid of the S6. The Note4 I had before (on 4.4.whatever) and the Note4 I have now (on 5.0.1) have no issues.
My Pixel XL is having a hard time connecting to my car's Bluetooth (Mazda 3). I had no problem pairing, but connecting seems to be hit or miss. Once it connects, things seem to work fine. Any advice?
My advice is get used to it. Not being mean saying that, its just that Android bluetooth has been hit or miss for a long long time now. Some will work well with some devices and some will not. And it will change every once in awhile after an update.
Toss a Bluetooth toggle on your home screen
Aqua1ung said:
My Pixel XL is having a hard time connecting to my car's Bluetooth (Mazda 3). I had no problem pairing, but connecting seems to be hit or miss. Once it connects, things seem to work fine. Any advice?
Click to expand...
Click to collapse
If you're not on the latest security update, I'd suggest that you install it. Older GM vehicles had an issue connecting to BlueTooth. It was resolved with the December 7.1.1 update.
cam30era said:
If you're not on the latest security update, I'd suggest that you install it. Older GM vehicles had an issue connecting to BlueTooth. It was resolved with the December 7.1.1 update.
Click to expand...
Click to collapse
Yes, I am currently on 7.1.1.
Is there an official Google PixelXL forum where I can voice my concerns so that Google/Pixel people come in contact with my grievances in a more direct manner?
Thank you!
Aqua1ung said:
Is there an official Google PixelXL forum
Click to expand...
Click to collapse
Here > productforums.google.com/forum/#!forum/phone-by-google
I think I've noticed a pattern that might be relevant for this issue: After rebooting, connection happens pretty much instantly. It gets gradually slower everytime i connect afterwards, until the A2DP profile stops connecting altogether, after the 4rd or 5th connection attempt. Rebooting the Pixel resets this cycle.
Interestingly, these connection issues happen only with my Mazda car. No other BT devices have problems connecting to the PixelXL, which makes me think that this might be a Mazda issue rather than a Pixel issue. But then again, I had no such problems when connecting my Mazda to my Galaxy S6. Not sure what to think.
http://www.androidpolice.com/2017/0...-random-bluetooth-disconnects-pixel-pixel-xl/
When on oxygen is can see the song that's playing on Spotify on my radio of my ford fiesta mk7 2011.
But when I flash all of the roms Bluetooth streaming works great but the radio don't show the song title.
What can be the cause of this, i tested with various settings but nothing really helps.
Someone got ideas where to look to fix this problem? Or how to fix this?
bassbounce said:
When on oxygen is can see the song that's playing on Spotify on my radio of my ford fiesta mk7 2011.
But when I flash all of the roms Bluetooth streaming works great but the radio don't show the song title.
What can be the cause of this, i tested with various settings but nothing really helps.
Someone got ideas where to look to fix this problem? Or how to fix this?
Click to expand...
Click to collapse
I assume you're already in Oreo? This is a well known Oreo issue.
I suffered this on my Nexus6p when I upgraded to 8.0 and 8.1.
When I switched to OP5T, the same thing happened after the 8.0 update.
I heard that this metadata issue does not occur on Google Play music. But like you, I prefer Spotify.
eric_son said:
I assume you're already in Oreo? This is a well known Oreo issue.
I suffered this on my Nexus6p when I upgraded to 8.0 and 8.1.
When I switched to OP5T, the same thing happened after the 8.0 update.
I heard that this metadata issue does not occur on Google Play music. But like you, I prefer Spotify.
Click to expand...
Click to collapse
Thank u, yes I am om android 8.1 hope Google will fix it soon! :good:
bassbounce said:
Thank u, yes I am om android 8.1 hope Google will fix it soon! :good:
Click to expand...
Click to collapse
Hi, are you still having BT metadata issues?
Try this:
Go to Developer Options, and look for Bluetooth AVRCP Version.
On Android 8.1, this should be set to 1.4, but you should see an option for 1.3. Set it to 1.3.
My Spotify song titles working again on my Honda Head unit.
eric_son said:
Hi, are you still having BT metadata issues?
Try this:
Go to Developer Options, and look for Bluetooth AVRCP Version.
On Android 8.1, this should be set to 1.4, but you should see an option for 1.3. Set it to 1.3.
My Spotify song titles working again on my Honda Head unit.
Click to expand...
Click to collapse
Hi! Just came across this thread here on the forum. I currently have a Volvo V40(2017) and it worked flawlessly with my iPhone 6S through Bluetooth. Every app I used to stream managed to get the metadata there, that being Spotify, Apple Music or even Twitch!
I ditched the iPhone and bought a OnePlus 5T and now when I do pair the device with the car and stream music through Bluetooth this happens to me. The only thing shown on the car monitor is Audio Streaming without any additional information about it. I already tried every single Bluetooth AVRCP version available (1.4[Default], 1.3, 1.5, 1.6) and not one works. Also I'm currently using Apple Music but I don't think it matters because other applications also don't pass the metadata as well.
It's really annoying not being able to see what is currently playing and its also the only thing about my recent iOS to Android change I'm sad about so far
Any other ideas on how I can solve this?
Thanks!
mariocosme14 said:
It's really annoying not being able to see what is currently playing and its also the only thing about my recent iOS to Android change I'm sad about so far
Any other ideas on how I can solve this?
Thanks!
Click to expand...
Click to collapse
I feel your pain.
Back in 2014, I had a nexus phone that was running on Kitkat. And in addition to the song metadata, etc., I am also able to use my car's voice dialing function to make calls on my phone. But when Lollipop came out, my car's voice dialing suddenly stopped working. But at least I could still make calls and I still had metadata.
When marshmallow came out, my car's dialer suddenly stopped showing the profile picture of the person I'm calling (or calling me). The clock sync function also stopped working. But at least I can still make calls, and I still had my audio-track metadata..
Up until Nougat 7.0, the audio metadata still worked.
It was when Nougat 7.1 came out that I lost the metadata.
When Oreo came out, it was a hit-or-miss affair. Sometimes I get metadata. Sometimes I don't. I could not figure the correct sequence that I followed to get the metadata to work.
I was lucky enough to find the AVRCP tip from a Honda Car forum.
I'm sorry I don't have any other ideas at this point.
i have Pixel 3xl with Android 10, - Bluetooth connects fine there is no metadata - song info. this problem started with 8.1 Android version and I have not been able to get it to work. I really cant believe google cant fix this issue or even aware of it. plenty of threads on google. I think they all use Iphone, i am guessing ...this is very annoying. I have change the avrcp version from 1.4 to 1.6. no luck, also I read that turn off battery optimization on Bluetooth. no luck. any suggestions would be appreciated
Hello
I'm facing the problem that the bluetooth connection to my cars multimedia unit is a big mess since 2020.
But not only when connecting to the cars BT. Every BT connection will randomly asks for permission to the contacts or messages...
The phone will not store this information correctly anymore. My car is an 2020 Opel and sometimes it says that the bt connection can't be established, but it actually plays music over this connection and phonebook is also transfered.
I have the pixel 3XL since it came out and it is completely stock non rooted or something like that (I'm to old for this stuff as a daily driver )
So, did google mess the driver up that it will not work correctly anymore? Or does someone know what's going on in the device?
Daimonion1980 said:
Hello
I'm facing the problem that the bluetooth connection to my cars multimedia unit is a big mess since 2020.
But not only when connecting to the cars BT. Every BT connection will randomly asks for permission to the contacts or messages...
The phone will not store this information correctly anymore. My car is an 2020 Opel and sometimes it says that the bt connection can't be established, but it actually plays music over this connection and phonebook is also transfered.
I have the pixel 3XL since it came out and it is completely stock non rooted or something like that (I'm to old for this stuff as a daily driver )
So, did google mess the driver up that it will not work correctly anymore? Or does someone know what's going on in the device?
Click to expand...
Click to collapse
Have tried different ROM's on this Pixel 3 XL so I completely understand the Bluetooth issue. Have grown to rely on turning off Bluetooth before using the passcode; kind of helps with the new ViPER4Android FX,
Since using ScorpionROM, haven't had any Bluetooth issues. Maybe give it a shot and see if it helps
Ever since installing the September update I have had troubles with Bluetooth connecting and staying connected to my Galaxy Watch 3 and my hearing aids. Everything worked flawlessly until that installation. Is this a known issue or has anyone else observed this?
Quite the opposite for me, this update has made my phone more reliable to Bluetooth connections.
My BT headphones disconnect all the time. I think my Fitbit does too
With A13, the Bluetooth stack used by Android was changed. I saw some issues early on (problems pairing, needing to forget and repair, pairings simply disappearing), but after redoing some pairings, things seem to be getting better. Still some odd stuff, like impossible options enabled (like "Input Device" and "Contact Sharing" on speakers without that capability).
It's obviously a work in progress.
As mentioned above by Mike, I did also do a fresh start no restore for Android 13 since I thought I was having issues with other things that was really annoying me with android 13 after upgrading to that, all the problems that caused me to fresh start were still present but almost all of these have gone after Sept update