I just would like to quickly check if anyone has the car Bluetooth pairing issue for Nexus 5 and anyone has a solution for that? Thanks.
My wife and I both received the latest Nexus 5 from Google 1 week ago. I have rooted and installed the DroidKang v14 Xmas Edition and Google APK package and also installed the Mod fixing the volume issue. Everything looks fine until we try to pair the nexus 5 to my 2013 honda Accord LX.
the Honda HandsFreeLink Stereo found my Nexus. It connected. However, the stereo disconnects and reconnects repeatedly, with the phone displaying the message, "Unfortunately, the process com.android.bluetooth has stopped." I tried to reboot the phone and also play around the Bluetooth function, the error still come out. It looks like that the error will happen every time when the car Bluetooth tryes to import or read call history or contact info from the phone. So I changed Car Bluetooth setting and disable syncing info from phone. Now the connection does not drop and I could hear the music in car from phone. However, I lose the most function for Car Bluetooth because I cannot see call history directly on car system.
Even the Bluetooth connection stables after we disable syncing function. The bluetooth connection will fail again when we walk back from retailer store to the car. the reconnection will disconnect and reconnect again and again. it is so crazy and unusable.
I do not know if this issue is related to the phone hardware or the CM ROM. I have not tried other ROM but at least I know my old HTC phone and samsung phone seamlessly connected to this Honda Car Bluetooth system. There is no any issue. So I think the issue is related to Nexus 5 or this ROM.
I will try to do more research on this. in the meantime, if anyone has the same experience or a solution for that, please let me know. Thanks.
Viking2015 said:
I do not know if this issue is related to the phone hardware or the CM ROM.
Click to expand...
Click to collapse
Definitely the CM ROM. I have a Nexus 4, and since upgrading from CM 10.2 to 11, I've been experiencing intermittent BT dropouts with my Pioneer car stereo that I've never experienced before.
Viking2015 said:
I just would like to quickly check if anyone has the car Bluetooth pairing issue for Nexus 5 and anyone has a solution for that? Thanks.
My wife and I both received the latest Nexus 5 from Google 1 week ago. I have rooted and installed the DroidKang v14 Xmas Edition and Google APK package and also installed the Mod fixing the volume issue. Everything looks fine until we try to pair the nexus 5 to my 2013 honda Accord LX.
the Honda HandsFreeLink Stereo found my Nexus. It connected. However, the stereo disconnects and reconnects repeatedly, with the phone displaying the message, "Unfortunately, the process com.android.bluetooth has stopped." I tried to reboot the phone and also play around the Bluetooth function, the error still come out. It looks like that the error will happen every time when the car Bluetooth tryes to import or read call history or contact info from the phone. So I changed Car Bluetooth setting and disable syncing info from phone. Now the connection does not drop and I could hear the music in car from phone. However, I lose the most function for Car Bluetooth because I cannot see call history directly on car system.
Even the Bluetooth connection stables after we disable syncing function. The bluetooth connection will fail again when we walk back from retailer store to the car. the reconnection will disconnect and reconnect again and again. it is so crazy and unusable.
I do not know if this issue is related to the phone hardware or the CM ROM. I have not tried other ROM but at least I know my old HTC phone and samsung phone seamlessly connected to this Honda Car Bluetooth system. There is no any issue. So I think the issue is related to Nexus 5 or this ROM.
I will try to do more research on this. in the meantime, if anyone has the same experience or a solution for that, please let me know. Thanks.
Click to expand...
Click to collapse
i have the same issue with my Mercedes A bluetooth connection. it's very annoying. I am running CM11 nightly of yesterday....so far only 1 cm nightly worked....I think is was 14-12-2013.....I wish there was a way to revert to this only with the bluetooth part.....so far...no solution
I have a Honda with Honda link. I have that problem when I have the read sms feature on the car enabled. If I turn it off then it works fine. I use it daily for a 50 minute drive each way to work.
I don't ever use the call history on the car, but the voice call works fine. And of course streaming music, which is mostly what I do with it.
Sent from my Nexus 5 using Tapatalk 2
I'm on kangakat BT to stereo audio call and text with no issues -dodge truck. Worked fine on stock as well so I would try a different ROM and see how it acts.
Sent from my Nexus 5 using Tapatalk
Hi All,
I'm having trouble with Bluetooth on my v10. I've looked through the forums but haven't seen any people with an issue quite like mine.
My car is a Hyundai and the radio was updated to the latest software about 6 months ago. The phone will pair fine and works perfectly for phone calls but I can't get it to play audio over bluetooth. In the bluetooth menu the "Media Option" check box is not visible at all. The particularly weird part is that while the audio still comes out of the phone the rest of the bluetooth features will work, I can change the song with the radio controls and the Artist/Title are displayed on the radio.
It works great with my soundbar, alarm clock, portable speaker, and my moms Dodge truck. That would lead me to believe it's the car however I never had any issues with my gs5 for a year and a half. I tried it with two different iphones and my roommates G4 and all of them worked perfectly.
My phone is an h900 on 5.1.1 rooted(had the same issue before root).
I'm at a loss here. Any ideas? Thanks.
I have a bug report w/ google on this. Please take a look and chime in to get them to fix this. https://code.google.com/p/android/issues/detail?id=221322&thanks=221322&ts=1472583426
Im going to guess you have a 2011 to 2013 hyundai right? Probably with navi?
So google is blaming samsung of course so I have an email into them. Their chat was useless.
Your device is using Samsung's heavily customised version of Android which this website has no visibility of so cannot support. You need to speak to Samsung for user support and issues with their devices and their software. Thanks.
Click to expand...
Click to collapse
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
Fully stock OnePlus 8 - global unlocked version. Current Oxygen OS build is stable OTA 10.5.9.IN21AA.
My phone will not connect to my aftermarket JVC car stereo. I had no problems with my previous phones including my OnePlus 6T. Up until today I had been having a lot of frustration when getting into the car, turning it on, and the phone said it was connected to the radio, but the radio showed it was not. I would have to go into the bluetooth settings on the OP8 every time and de pair then re pair them for it to work. Sounds like first world problems, but having to do it every time the car is started when it should just automatically connect to a remembered device was quite frustrating. Today the problem actually got worse. I went to connect my phone, as per the usual I had to de pair and re pair the radio and it showed as paired. So I loaded up Amazon Music and started playing, but the audio didn't come from the speakers, it came from the phone only. I went into the bluetooth settings for the JVC radio and tried untoggling and toggling "media audio". No dice. Tried rebooting the phone, still no dice. Turned the radio off after saying some choice words and drove in silence.
Then tonight I was outside cooking on the grill and tried to connect the phone to my JBL Charge 3 speaker. It did the same thing. It connected but music didn't play from the speaker, it played from the dang phone.
I have never had a phone do anything like this, and frankly am about to return the dang thing as much as I like the phone's performance I have too many devices that are bluetooth that I use daily to have a phone that is unreliable with those devices.
Has anyone else had a similar problem or have any ideas on something I can try?
Wanted to post an update. I emailed OnePlus and they offered a suggestion that seems to have solved the problem.
1. Network reset:
Open the 'Settings' app on your device > Navigate to 'Backup & reset' > 'Network reset' > 'Reset' Note: This will erase all passwords of connected Wi-Fi networks.
After performing the Network Reset my devices pair as expected.
I am a new owner of the OnePlus 8T 5G and I am very dissatisfied. I plan to contact Sprint/T Mobile today to see if there is something I can do to get a refund or exchange. Today's problem is that I cannot connect to my bluetooth speaker. It took me several tries to connect it to my Subaru and now it will not pick up this speaker. Why is this so complicated? I am also very unhappy with the amount of ads that appear on my phone, even on the lock screen. If this is what 5G means, count me out!!!!
It seems that Android Auto (including wireless via Motorola M1) works flawlessly for a few days after setting it up.
Once it enters the "looking for Android Auto" mode there's no other way than removing cache and app settings and establishing the phone -car connection from scratch. And after doing so, it will work for a few days until it starts looking and not connecting again.
Is this a known issue? Is this specific to the wireless adapter? Once the error occurs, wired connection doesn't help.
I also have the AAWireless device somewhere and I'll have a look.
Check the Android Auto forums, maybe some info there...
Android Auto General
General discussion about Google's Android Auto.
forum.xda-developers.com
My wife and I have been using wireless (and wired) Android Auto in our car with the P7P for three weeks with no issues like this. Our car's head unit doesn't have native wireless AA, though - we're using AAWireless. Could be just the head unit or the car needs a firmware update (my car has occasionally received one when I have it connected to my home's Wi-Fi).
roirraW edor ehT said:
My wife and I have been using wireless (and wired) Android Auto in our car with the P7P for three weeks with no issues like this. Our car's head unit doesn't have native wireless AA, though - we're using AAWireless. Could be just the head unit or the car needs a firmware update (my car has occasionally received one when I have it connected to my home's Wi-Fi).
Click to expand...
Click to collapse
I didn't have these issues with my old Huawei.
domi_niku said:
I didn't have these issues with my old Huawei.
Click to expand...
Click to collapse
I've noticed very different Android Auto experiences with the same phone but different car brands before. I've used Android Auto in either 4 cars so far, two of them rentals. I believe my rental VW's Android Auto was horrendously slow and hard to get the touchscreen to respond, whatever the next rental was, was fine. Chevy and Subaru have been fine, too, although my Chevy Android Auto experience seemed better than Subaru, but the Subaru is acceptable.