In a news artical I read that the January 2023 pixel build broke blue tooth connection in cars. Can anyone confirm or deny the validity of this report?
Works fine in my car. P6P January update.
I cannot connect to car BT as well. Maybe because I'm on custom kernel. I'm gonna flash stock ROM again and check tomorrow.
I'm on a custom kernel too (Kirisakura) with no car bluetooth issues.
AlDollaz said:
I'm on a custom kernel too (Kirisakura) with no car bluetooth issues.
Click to expand...
Click to collapse
That's strange, definitely there a problem since many people reporting BT issues after January update
Literally just went out to the car to make sure I wasn't crazy. Works fine. I've got a 2012 Scion.
I can't connect to my car since the January update, I'm not on a custom Kernel. Guess I can try kirisakura in the meantime to see if that fixes my issue
DarkShadowMX said:
I can't connect to my car since the January update, I'm not on a custom Kernel. Guess I can try kirisakura in the meantime to see if that fixes my issue
Click to expand...
Click to collapse
It will not, I think that it depends on car, Jaguar XF here, no BT connection at all
felek73 said:
It will not, I think that it depends on car, Jaguar XF here, no BT connection at all
Click to expand...
Click to collapse
That sucks, I already flashed Kirisakura and gonna try in a bit but guess I'm SOL until Google fixes this
DarkShadowMX said:
That sucks, I already flashed Kirisakura and gonna try in a bit but guess I'm SOL until Google fixes this
Click to expand...
Click to collapse
Actually I fixed it. I unpaired my Garmin watch and paired again using Garmin App. Now watch is not visible in BT connection but is connected. BT in car is also ok so it seems that January build can't handle two BT connection at the same time
The reddit complaints are highly-specific to vehicle bluetooth only, not other BT devices. I run the kirisakura kernel but don't see how that would make any difference. I'll skip the January update until that gets fixed. I haven't seen any update publicly or otherwise from Google though.
I just updated to Jan23 and my BMW 5 series, my Galaxy watch, and my Resound hearing aids all work fine fortunately.
Related
SOLVED. Thanks to Fir3start3r.
Change pairing code to 0000
Hello all,
I updated my Android to Nougat over the air on previously fresh installed Android Marshmallow. Everything seems ok, but now I can't pair my phone with my car over bluetooth. A few weeks ago, I tested Android N DP5, and it was the same issue. At that time, I thought that the issue was related to beta version, but now it's official.
Everything worked like charm before on Marshmallow. The error message that I get is "Can't communicate with Hands Free System". The car says "Pairing failed".
Just to clarify, the car is Mitsubishi Spacestar 2014, and before pairing, I wiped the phone from car's Hands Free System, so it's clean/new pairing.
Does anyone experiencing this? Is there any fix?
Thank you.
Antique_Angel said:
Hello all,
I updated my Android to Nougat over the air on previously fresh installed Android Marshmallow. Everything seems ok, but now I can't pair my phone with my car over bluetooth. A few weeks ago, I tested Android N DP5, and it was the same issue. At that time, I thought that the issue was related to beta version, but now it's official.
Everything worked like charm before on Marshmallow. The error message that I get is "Can't communicate with Hands Free System". The car says "Pairing failed".
Just to clarify, the car is Mitsubishi Spacestar 2014, and before pairing, I wiped the phone from car's Hands Free System, so it's clean/new pairing.
Does anyone experiencing this? Is there any fix?
Thank you.
Click to expand...
Click to collapse
I don't know about specifics in bluetooth devices such as your Mitsubishi. But I can tell you my bluetooth connects to my stereo fine in my 2012 Jeep Patriot. I haven't updated to the final release but I'm currently on preview 5. So I don't think it's an issue with bluetooth in Nougat.
I had some issues on the last preview. For me it would disconnect after being connected for maybe 5 min or so. That was with a JVC BT adapter (older aftermarket headunit) and in a Ford with sync (V1) Haven't tested on the new build though. Going back to 6.0.1 resolved all of those issues at the time. I flashed the ota last night and still need to see if it improved anything for me.
Antique_Angel said:
Hello all,
I updated my Android to Nougat over the air on previously fresh installed Android Marshmallow. Everything seems ok, but now I can't pair my phone with my car over bluetooth. A few weeks ago, I tested Android N DP5, and it was the same issue. At that time, I thought that the issue was related to beta version, but now it's official.
Everything worked like charm before on Marshmallow. The error message that I get is "Can't communicate with Hands Free System". The car says "Pairing failed".
Just to clarify, the car is Mitsubishi Spacestar 2014, and before pairing, I wiped the phone from car's Hands Free System, so it's clean/new pairing.
Does anyone experiencing this? Is there any fix?
Thank you.
Click to expand...
Click to collapse
Every time i flash my phone with a major update change or wipe it, i have to delete the current BT profile in the car, as I do not alter the name. That resolves it for me 7.0 syncs just fine on my car
Can anyone help me in getting the vendor image for official nougat build?
Thanks in advance!
I have same issue as OP with a 2nd gen Toyota Prius. Resetting the car's Bluetooth settings hasn't helped, as suggested by others in the thread.
I tried everything and I also wiped my phone. I believe that the issue is Nougat OS because it did sync before on Marshmallow.
Lavrentsii said:
I have same issue as OP with a 2nd gen Toyota Prius. Resetting the car's Bluetooth settings hasn't helped, as suggested by others in the thread.
Click to expand...
Click to collapse
OK so the car is at least 7 years old, so does the car have any profile settings, where it associates your phones BT MAC address with a name of some kind where you can see and choose them. I know some cars can do that, even some older ones. If so does it still show as I do not know if there is a difference between doing a BT reset and deleting profiles?
I can attest that 7.0 works with BT streaming, connecting, etc...
carm01 said:
OK so the car is at least 7 years old, so does the car have any profile settings, where it associates your phones BT MAC address with a name of some kind where you can see and choose them. I know some cars can do that, even some older ones. If so does it still show as I do not know if there is a difference between doing a BT reset and deleting profiles?
I can attest that 7.0 works with BT streaming, connecting, etc...
Click to expand...
Click to collapse
It allows you to delete registered phones and "Reset settings to default". I think those settings might just be Bluetooth name and PIN though, but that's what I tried
Same problem here (Mitsubishi Lancer (2016)) -> changed the bluetooth (pairing) code from the Mitsubishi media system to "0000" -> works perfect now
Lavrentsii said:
It allows you to delete registered phones and "Reset settings to default". I think those settings might just be Bluetooth name and PIN though, but that's what I tried
Click to expand...
Click to collapse
I wonder if something in the upgrade process fouled it up per chance.
What OS version did you come from and how did you arrive at 7.0?
carm01 said:
I wonder if something in the upgrade process fouled it up per chance.
What OS version did you come from and how did you arrive at 7.0?
Click to expand...
Click to collapse
6.0.1 Stock, unrooted etc, thru "Beta" enrollment to expedite OTA delivery. I unenrolled after the update installed.
I plan on resetting in the next week or so to switch to File-Based encryption. Hopefully that will fix it
Lavrentsii said:
6.0.1 Stock, unrooted etc, thru "Beta" enrollment to expedite OTA delivery. I unenrolled after the update installed.
I plan on resetting in the next week or so to switch to File-Based encryption. Hopefully that will fix it
Click to expand...
Click to collapse
I did it differently coming from rooted 6.0.1
This is what I did :
http://forum.xda-developers.com/showpost.php?p=68322783&postcount=4
Maybe that factory reset will help
I have exactly the same problem with my pajero 2014 bluetooth
With marshmallow rooted or unrooted works perfect
With n in dev. Preview or the official yesterday I got " pairing failed "
Any help will be appreciated
Fir3start3r said:
Same problem here (Mitsubishi Lancer (2016)) -> changed the bluetooth (pairing) code from the Mitsubishi media system to "0000" -> works perfect now
Click to expand...
Click to collapse
It worked! Thank you very much!
Fir3start3r said:
Same problem here (Mitsubishi Lancer (2016)) -> changed the bluetooth (pairing) code from the Mitsubishi media system to "0000" -> works perfect now
Click to expand...
Click to collapse
Wow it really works thanks alot dude you made my day
You're welcome!
Fir3start3r said:
Same problem here (Mitsubishi Lancer (2016)) -> changed the bluetooth (pairing) code from the Mitsubishi media system to "0000" -> works perfect now
Click to expand...
Click to collapse
Confirmed as well. 2015 Outlander Sport.
Thank you!
Anyone have any luck on a JVC stereo? It keeps saying wrong code. Idk how to reset it
Mine connects fine to my car stereo but with Play Music it starts playing through the speaker phone after a song completes. I have to pause and resume for it to start playing through the car stereo again. Really obnoxious. Other than that, I'm really enjoying Nougat (besides the terrible name).
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
So, Bluetooth works well with all alter devices but does not recognise my car Bluetooth. I have not had any issues so far testing from all possible android phones to Nokia and iPhone. I have a 2010 C class. Any suggestions? The car says that no devices has been found when trying to pair. Thanks
Same exact problem here with an Audi A1. I contacted support, but they only suggested things I had already tried (like factory reset etc). I'm going to try and get a log to them at some point this week.
Are you on the latest OTA? That's when the problems started happening for me - it was working fine before that.
bladerara1 said:
So, Bluetooth works well with all alter devices but does not recognise my car Bluetooth. I have not had any issues so far testing from all possible android phones to Nokia and iPhone. I have a 2010 C class. Any suggestions? The car says that no devices has been found when trying to pair. Thanks
Click to expand...
Click to collapse
Know issue supposed to be fixed next update.
HomerSp said:
Same exact problem here with an Audi A1. I contacted support, but they only suggested things I had already tried (like factory reset etc). I'm going to try and get a log to them at some point this week.
Are you on the latest OTA? That's when the problems started happening for me - it was working fine before that.
Click to expand...
Click to collapse
Yes, latest update. Unfortunately support gave me "support" I have already tried and if you have a bit of knowledge of android you do not need some to tell you those things. We just have to wait until next update. Thanks
Have you tried turning off HD audio in the device settings?
When the device is connected, go to Bluetooth and select the cog next to the device. Uncheck HD audio.
This worked for me with my JVC Bluetooth car stereo.
kdogguk said:
Have you tried turning off HD audio in the device settings?
When the device is connected, go to Bluetooth and select the cog next to the device. Uncheck HD audio.
This worked for me with my JVC Bluetooth car stereo.
Click to expand...
Click to collapse
For me to be ableto do that, I will need to be connected first. That a my problem.
I've noticed here lately that my Bluetooth devices don't automatically reconnect after I've turned them off and then try to use them again. I have to run pairing again. Stock November, custom kernel... But this happens to me on pure stock too..
I have the same issue. Can't remember paired car audio device. I have to manually connect everytime...it is pretty annoying. Let's hope december update will fix this.
This article describes a similar problem: https://thedroidguy.com/2018/08/how...eeps-disconnecting-from-car-head-unit-1087866
Sent from my Pixel 2 XL using XDA Labs
capt_f0r3st said:
I have the same issue. Can't remember paired car audio device. I have to manually connect everytime...it is pretty annoying. Let's hope december update will fix this.
Click to expand...
Click to collapse
No problem whatsoever on stock November with stock Kernel (2017 Audi A4 MMI plus).
But I did have issues in the past, Bluetooth is a mess. Usually a new patch fixes or breaks things ?
I have 2007 mazdaspeed 3. But the radio unit is not original, as the original one doesn't have bt. On my previous galaxy s8 everything worked well. So I suppose radio is alright. Once the pixel is connected, there aren't any issues ( maybe some little skips here and there) but no complete disconnects or something.