So I got my Nexus 5 today and have spent most of the afternoon tinkering with it. When I came to drive home, I paired it with my car (2012 Holden Cruze) and just like my Nexus 4 before it, it tells me there is no phonebook available, so I can't call anyone from the car. Also the car's call / disconnect buttons don't work.
I had exactly the same scenario with the Nexus 4 and ended up running CM10 on it, as bluetooth worked fine in that ROM. Clearly, CM has some different bluetooth code ..... my question is, does anybody know how to make this work? Can we somehow extract the bluetooth code from a CM10.2 / 11 ROM and install it into stock? I would really like to stay on stock.
I am interested in finding this out too, I have tried all sorts on my Nexus 4 but with no success. I don't seem to get the request from the car to access the phonebook on stock 4.2, 4.3 or 4.4 but get it straight away with CM10.1 :crying:
Related
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
I have a cheap ELM327 OBD2 Bluetooth adapter that works fine on my old Rooted Samsung Galaxy S3 on factory ROM with CWM Recovery Android 4.1.2, but when I try the same adapter on my new Rooted OnePlus One on Factory CM11 Android 4.4.4 with TWRP Recovery it gets a lot of errors under adapter status and will show timeout errors when trying to clear ECU fault codes. I know the adapter is good because it will still work fine with my old S3 but I would prefer it work with my new everyday carry phone.
I've read that there were some compatibility issues with the Torque Pro app with CM10 Bluetooth drivers but can't find anything about CM11 issues, or if the drivers had ever been fixed. I have the latest version of the Torque Pro app but have also tried previous versions with no success. It will read codes from the car's ECU but sometimes quits reading before the percentage goes to 100% (around half way through) so I don't know if it has read all of the codes that were on the ECU or not. When trying to clear fault codes it quits halfway through showing a timeout message, sometimes it still clears the check engine light from the car but not always.
I've tried checking / unchecking "Faster communication" and "Disable ELM327 auto timing" as others have suggested with no success. I was just wondering if anyone else had run into these issues on the OnePlus One or on other phones with or without CM11 and figured out a fix for this. I did some searching but couldn't find any solid cures.
I'm using this one. Working fine with 5.1.1
So it must be problem with CM11
That's the same kind of adapter I'm using. Mine still woks with my old deactivated S3 but I would like to get it working with my OnePlus One since its the phone I now carry around everyday...
demo84 said:
I'm using this one. Working fine with 5.1.1
So it must be problem with CM11
Click to expand...
Click to collapse
It's a mystery problem, i had it too. Sometimes it starts sometimes it doesn't. No idea why. Try another app like Dash Command, i find that it works better than TORQ with the Oneplus
I have looked for information on my problem. But haven't found any anywhere else.
I'm using a Nexus 5, running the new version 6.0. I bought a jawbone UP Move fitness tracker. And I can't seem to get it to connect through bluetooth. I know bluetooth is working on my device, because I was able to connect my bluetooth headphones to my Nexus 5. The Up Move shows up on my Nexus 5, but pairing is rejected.
I was able to successfully pair the UP Move to my wifes Sony Xperia t2 ultra running Lollipop. So I know it is neither my Nexus 5, or the device.
The only thing I cant think of, is either the app or device is unsupported, or something in the new version of Android.
Is there any known issues with bluetooth in android 6.0 that anyone knows of? Or has anyone came across this issue with the jawbone UP Move and figured it out?
Hi,
I use 3 bluetooth devices at home. With my previous build (rooted and tweaked Kit Kat) everything worked just fine.
I flash the new Marshmallow, root it and tweak it a bit (nothing major) like I did before but now my Bluetooth can only see one device out of my 3.
Doing a Google search I see some problems but nothing recent and no possible fixes.
Anyone else have this problem and get it fixed? Anyone have any thoughts?
It's lonely being the only one.
You're not the only one - since upgrading to STOCK Marshmallow and now 6.0.1, if my phone is more than 6 INCHES from my headset, any of 5 of them, the phone will connect / disconnect every 20 to 70 seconds. If the phone is in my left pocket with the headset in my right ear, I can't connect the headset AT ALL! I'm gettin' my HATE on for Marshmallow in a big way!
Hi everyone,
i just got a xperia Z5, and i'm trying to listen my music.
I have 2 pairs of headphones and 2 pairs of headsets (one came with the device). But my favorite (and most expensive) is a pair of headphones (so without a mic).
I have tested all 4 of these Accessories, but only the ones with a microfoon work on this phone, while the all work on both my laptop and my old nexus 5.
I have searched for a way to make the regular headphones work with the z5, but no luck.
I had this problem both on stock and on RomX, which i am currently running.
The strangest part is that On both roms they worked the first few hours, and once i unplugged the headpones, a few hours later they aren't detected anymore.
Any help?
Now running Paranoid Android, all problems are fixed.
A temporary fix to this, until it's (hopefully) fixed on Android 7.0, is downloading an app called SoundAbout. It works for me, although I don't always have to use it as sometimes the headphones do work. When you open it, go into Media audio: > Choose one of the last two. Go back and into SoundAbout Service > ON With Status. It should work!
Best of luck