I've paired my pixel 2 with my uconnect system in my Jeep. Two issues, 1 the metadata (song titles and track info) doesn't show on the screen in my car. This worked fine on my last several phones. I've tried deleting and pairing again but it doesn't help. 2, the navigation directions from Google maps do not come through my car's speakers despite having that option checked in gmaps settings. Anyone having similar problems and figured out a fix? I'm on 8.1 Dev preview, and this also did not work on 8.0. I can't imagine that the phone isn't capable.
It appears there are lots of issues with Bluetooth on the Pixel 2s but no fixes that I can find. Hopefully Google will fix these soon as it's very frustrating getting a new very expensive phone which doesn't even do what you're old one did.
Sent from my Pixel 2 using Tapatalk
pabarker said:
It appears there are lots of issues with Bluetooth on the Pixel 2s but no fixes that I can find. Hopefully Google will fix these soon as it's very frustrating getting a new very expensive phone which doesn't even do what you're old one did.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Terrible, hope they fix it soon. Thought maybe 8.1 would help but no luck.
I feel sorry for you guys. OG Pixel had bluetooth issues on some cars and some of those issues are still not fixed 1 year later.
Bluetooth is great for me on my cars. Both newer GM vehicles. One with Android Auto, one without.
I have an SRT Hellcat with UConnect. It completely does the same type of stuff. Sometimes it fails to transfer calls. It also shows "Pixel 2" often rather than song titles, etc. If I disconnect BLE and reconnect it usually works better the second time. It is annoying.
How do they screw this up every year. Using play music now completely locks up my uconnect RHR radio. I really wish Google would test things before rolling out. I wish they would just release there new phones on the previous Android version and have a beta of the current since they always screw something major up.
---------- Post added at 04:53 AM ---------- Previous post was at 04:17 AM ----------
I upgraded my uconnect from 2.600 to 2.700 and deleted the device pairing a couple of times and now I can at least play media again although I no longer have song data displaying which was there before at least before my radio would lock up.
I also tried changing the Bluetooth codec via developer settings to ACC. However, after changing, it reverts on its own. I read that the November security patch supposedly contains some BT fixes, fingers crossed!
On my car (BMW 335i from 2008) the Bluetooth is so messed up that while I can pair the Pixel 2, if I actually play any audio it reboots the car's entertainment system and deletes all Bluetooth pairings.
The 8.1 beta doesn't fix the problem, either, so I'm not too hopeful about the next patch.
fishsupreme said:
On my car (BMW 335i from 2008) the Bluetooth is so messed up that while I can pair the Pixel 2, if I actually play any audio it reboots the car's entertainment system and deletes all Bluetooth pairings.
The 8.1 beta doesn't fix the problem, either, so I'm not too hopeful about the next patch.
Click to expand...
Click to collapse
Interestingly, I found a fix for my Bluetooth issue at least. In Android 8.1, they added the ability to set the AVRCP version back to 1.3 in Developer Options. (8.0 moved the default up to 1.4 and in 8.0 there was actually no option to set it below 1.4) Setting AVRCP 1.3 and the SBC audio codec fixed my vehicle Bluetooth issues.
Hmm didnt know of bluetooth issues. So mine paired but wont connect to my 2012 mazdaspeed3, but my aftermarket headunit in my 89 ram50 connects right up and has no issues. (Also connects right to my garmin 2589 and allows all functions including traffic reports)
I just assumed it was something bugging with the radio in my mazda since its always seemed a little weird with bluetooth
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
Hmm didnt know of bluetooth issues. So mine paired but wont connect to my 2012 mazdaspeed3, but my aftermarket headunit in my 89 ram50 connects right up and has no issues. (Also connects right to my garmin 2589 and allows all functions including traffic reports)
I just assumed it was something bugging with the radio in my mazda since its always seemed a little weird with bluetooth
fishsupreme said:
Interestingly, I found a fix for my Bluetooth issue at least. In Android 8.1, they added the ability to set the AVRCP version back to 1.3 in Developer Options. (8.0 moved the default up to 1.4 and in 8.0 there was actually no option to set it below 1.4) Setting AVRCP 1.3 and the SBC audio codec fixed my vehicle Bluetooth issues.
Click to expand...
Click to collapse
Tried this but the codec keeps reverting to system default. The AVRCP version however will stay on 1.3. Still waiting for the November security patch with hopes that it will cure this all.
Not just with vehicles
760hacker said:
Tried this but the codec keeps reverting to system default. The AVRCP version however will stay on 1.3. Still waiting for the November security patch with hopes that it will cure this all.
Click to expand...
Click to collapse
Hello team,
I have seen similer problems with one of my Pixel 2's when using a simple Bluetooth device which may suggest that this goes beyond just vehicles. I tried turning on and off both the phone and device and ended up having to delete the connection profile and starting over.
The device would only partially handshake during the connection process and then hang which appears to be what's happening with the vehicle systems.
I thought I'd should mention this here as an FYI.
phonefreedom said:
Hello team,
I have seen similer problems with one of my Pixel 2's when using a simple Bluetooth device which may suggest that this goes beyond just vehicles. I tried turning on and off both the phone and device and ended up having to delete the connection profile and starting over.
The device would only partially handshake during the connection process and then hang which appears to be what's happening with the vehicle systems.
I thought I'd should mention this here as an FYI.
Click to expand...
Click to collapse
This is similar to what I see, both with my new Pixel2 and also my previous OnePlus3 on my Mazda 3. Phone will pair, but after a few seconds (or sometimes minutes) disconnect. Usually it will try to reconnect, and then be fine until the next time I use my car. Both phones behave identically, so it seems to be more a problem with vehicle systems that some phones (none I've owned unfortunately!) are more forgiving of.
Anyone know of a fix for this? I'm using uconnect and same issue, however my maps navigation does play over Bluetooth. Sometimes it seems to disconnect or mute after songs change, and the metadata issue is there. Super annoying that we go backwards in technology. My HTC M9 does this stuff flawlessly.
So I did the developer preview thing and set it back to 1.3 which helps the metadata issue. However, the music still pauses every once in a while, mostly between songs. I have to click to my AM/FM radio and back to bluetooth to fix that.
Well, it's always the same circle. There's a new device with a brand new Android version. Of course buggy a.f. They fix it over the time. The device works perfect. And then... a new major upgrade, which is buggy again.
7.1.2 worked perfect on my Pixel. Then came 8.0.
Bluetooth was messed up again. Now i use the Pixel 2, which is a great phone. But still has the complete bandwidth of bugs that were present in 8.0 on the Pixel 1.
Nice to have monthly patches. But instead of fixing so called security issues, they should focus on functionality bug fixes instead. Who has had a major security issue with hs phone at all, yet??
Google is like: "Fix: Someone could attack your phone using a backdoor in your bluetooth driver."
WTF?!
I can't even use my bluetooth to listen to audio correctly! Fix that first!
Long story short:
Yes, I have the same issue with meta-data in my car audio (Pioneer AVH-X2800BT). Sometimes it works. Sometimes it doesn't.
Just got November security patch which is supposed to include Bluetooth fixes but hasn't changed anything.
Sent from my Pixel 2 using Tapatalk
I'm on Nov update and I don't see AVRCP 1.3 anymore. Lowest is 1.4.
Haven't had to use BT (didn't drive the last 2 days) since the update but before that I had no issues with it linking to my wife's CX9 or my ancient 3-series. Calls work just fine and track information shows up accurate on the CX9.
scoliosis said:
I'm on Nov update and I don't see AVRCP 1.3 anymore. Lowest is 1.4.
Haven't had to use BT (didn't drive the last 2 days) since the update but before that I had no issues with it linking to my wife's CX9 or my ancient 3-series. Calls work just fine and track information shows up accurate on the CX9.
Click to expand...
Click to collapse
AVRCP 1.3 wasn't available in stock 8.0 either -- I had to put the 8.1 Developer Preview on to unlock it.
What is your Uconnect firmware version?
> the metadata (song titles and track info) doesn't show on the screen in my car
Mine does unless I'm running Android Auto
If your car has an older head unit with Bluetooth compatibility, you may have seen that with Android O, some of the metadata won't show up when playing audio from the phone. I found a tweak in the Android developer options that fixes it:
http://www.androidpolice.com/2017/0...ight-developer-preview-2-adds-avrcp-selector/
On my Honda Accord 2014, I set it to AVRCP 1.4 or 1.5, and Bluetooth shows the artist/track/etc again. Pandora runs more reliably as well.
There's no way I can get the audio system in my 2017 Subaru Forester to show remaining time on individual playing audio tracks. I have tried the various different developer options settings and it doesn't seem to make any difference.
I can confirm that setting version to 1.4, do fix this issue for pioneer radios. (Tested on DEH-X8500DAB).
After changing this, I can now switch tracks over bluetooth in my Honda Fit. Thanks!
In my case, after upgrading to Android 8.1 (Xiaomi Mi 5 @ AOSPExtended.mod by DennySPB) track infos won't work.
It doesn't matter if I choose AVRCP 1.3, 1.4, 1.5 or 1.6. It's just "no time, no title" etc.
Any other suggestions to fix that - apart from downgrading to 7.0?
(post removed by author, as it was not directly applicable to thread)
In my case, this solution worked, but I only post it "as is", without any warranty, that it will work for you.
1. Unpair audio device.
2. Go to Applications > show systems apps
3. Find "Bluetooth" and "Bluetooth MIDI", clear data for both of them
4. Go to developer settings, change AVRCP to 1.5 or 1.6
5. Restart phone.
6. Pair audio again.
Hi, thanks for the information, just reporting that this didn't work for me.
Android V9
Peugeot 508 JBL 2013
I have this problem with the Android Pie version on both MIUI versions. After a few minutes the cell phone is disconnected from the handsfree car radio. Bluetooth media continues to work and voice call also works, but it does not connect to the car radio in handsfree mode although I can speak through it. Sometimes I can't even connect with it but only the phone mode. I've tried everyting, clean install and wipe everything on the car radio, but no luck. It works perfect on the Oreo version of 10.0.2.0 but all the Pie versions have this problem. From what I found it looks like there is some problem on Android Pie about the handsfree bluetooth issue, but most of the people report that after the Security Patch update of October, all the issues are gone, but for me the issue remains. My car radio is based on R-link 2 from renault, which is based on Android. Does anyone knows how to handle this? Thanks.
Hi all,
I've had my Pixel 3 for almost a year now, and it's been great until just recently (possibly a recent software update?)
I tend to use bluetooth audio connections quite a bit with my car and headphones, but I've found that after such successful connections, the phone's own speaker (and mic, I think) stop working and I'm getting no sound for notifications, media, or phone calls. A reboot of the phone fixes the issue and the audio/mic starts working again fine - at least until I do another bluetooth connection.
Because it can be fixed with a reboot, it certainly seems like a software issue to me, but I've not been able to find any forums etc (here or otherwise) mentioning this particular issue. Any ideas? Is this something that's an Android 10 issue, rather than Pixel specific?
I have:
Android version: 10
Security Patch level: 5 December 2019
Build number: QQ1A.191205.008
I would just do a factory reset and see if it persists
Hello,
After recent Android 10 to Android 11 update (latest patch from july 2022) on my Nokia 5.3 I have issue with my bluetooth car handsfree set.
It's working fine overall, but I have button which when was pressed twice automatically called last dialed number.
After update button is not dialing last number anymore - nothing happens when phone is locked or unlocked.
Button however works fine - I know this for sure, since it also stops multimedia play and end phone call when pressed once.
I tried to reset network and bluetooth settings, clear phone app and bluetooth cache, re-pair devices or even change bluetooth settings in developer menu.
It seems like some permissions issue, but all looks fine there.
Any idea what else may I try?