As I am writing this in July 2016, almost 2 years after I initially got the OPO, I would say that this phone, although decent for the price, has been more of a hassle than a smooth operator (see what I did there ). Anyways, after searching through xda, other forums and general googling, I can't fine a solution to this issue; hence I am looking for some answers here. Also, I wonder how many others there are with an OPO and a Ford equipped with the Sync systems.
What's the issue?
OPO does not stay connected to the Ford Sync bluetooth system.
Background:
Ever since we got the lollipop update (now on the latest one), the phone has been very sketchy when it comes to Bluetooth connection, particularly with the sync system. It will pair and connect just fine, but when you go to do something real with it (like stream any kind of media), the connection is instantly drops. Phone calls may or may-not work, depending on how the OPO is feeling that day.
The weird part is that it displays similar behavior with a bose speaker and a generic speaker, but is perfectly fine with the Hyundai Elantra bluetooth system. Also, I have tested the OPO with many different ROMs with the same results. The Galaxy s4 and s6edge I tested work perfectly with the sync system.
Now, kind people, please share what you have experienced with the bluetooth performance of your phone, especially when connecting it to the ford Sync system.
Did you have the same issue? How did you fix it?
I read through all the threads and did not see this one. I can't connect to the Android head unit in my truck with the Pixel. It worked fine with the 5x on Nougat 7.0 but not the Pixel. I have reset them both to no avail. I read today that it is a known issue with 7.1 that Google is addressing "Google's new phone is having trouble pairing or staying connected to Bluetooth in many cars" but worried since I did not see it on here maybe its my phone. Plus my head unit is essentially an Android tablet in the dash. Has anyone else experienced this?
I have mine connected to my 2006 Charger Uconnect without any problems. It sounds wonderful and does not disconnect. I have also connected it with several wireless speaker without any issues.
Sometimes rebooting the phone temporarily fixes bluetooth connections issues.
Has any experienced no ring-back tones when doing an outgoing call when connected to a Bluetooth headset device but making the call from the phone? It only stated occurring(I think) with the November release. I am on Verizon.
It appears the phone does switch to handset speaker until the call is connected. Very annoying for me as I use an in house Bluetooth device that connects to my in house phone.
There are known issues with Bluetooth connections and vehicles. See this thread from the product forums:
https://productforums.google.com/forum/#!msg/phone-by-google/SZrziPyWiHw/jmV8CjeRBwAJ
heyho,
since im using KGL MTCD i have massive problems with BT in combination with apple.
First issue:
-BT autoconnect wont work every time, sometimes out of box (only enabling on smartphone) and sometimes i have to connect manually with apple to get i connected
#2:
-When im using speakerphone auto, mostly on every conversation, the soundquality has some massive dropouts, so i have to disable immediatly BT and switchin to my phone directly while im calling. first i tought it was an load problem with the device (maybe internal_sd or ram overloads) but the issue appears after clean and idling device,too.
i've contacted the reseller (erisin) to help me. so the sended me the newest stock-rom from oct 2016 and issue was GONE. Now im using malysk 11.1 and the issue is back again. i've tried some apks to fix it (like headunit.apk where i can switch the protocol from 2016 to 2015) but nothing realy helped.
anyone else has this problems?
i have really no idea how i can fix the call-issue. i need it 3-4x per day but in this case, it absolutely unusable
thanks
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
In August I got the Miui 11.0.1.0 (QFGE EXM) with the july security patch updates on my global versions note 7. Since then my bluetooth headsets (plantronics voyager legend) constantly have problems with the audio. Basically, the headset is connected but sound is not played. Sometimes the loudspaeker on phon eplays sound, sometimes the sound is playing nowhere. Switching off on of the headset sometimes helps, often not. The only thing that helps always is restarting the phone.
Anyone else has the same problem?. What could be the cause? I understood 11.0.4 is already circulating but wasn't offered yet to my phone. Does anyone have a problem on those phones?