I have a 2008 Mitsubishi Lancer SE (same electronics as ES) with an added Mitsubishi Bluetooth module added by the dealership from another Lancer. My issue is that the Bluetooth is only stable when running CM 11-44S. I have upgraded to COS12 and 12.1 multiple times but each time it screws up my Bluetooth. It can't keep a connection and is extremely difficult to even register. I go back to 44S and it works perfectly. I need my Bluetooth. Jira wants me troubleshooting but I can't see the point. Does anyone here have a solution so I can go to COS13 when the stable edition is released? (COS12.1 sucks for battery).
No answer?
Hi, I'm from Germany. I have the problem too with the Bluetooth connection with BMW. After paring changed all time the status for telephone functionality in my phone. I mean, in the settings for Bluetooth next to the BMW-device.
There is shown that the telephone not connected. I tried so many times again and again, but always the same. So I couldn't use the phone via Bluetooth in my car.
Please advise.
Related
My touch pro seems to have real bluetooth issues with my JVC KD-NX5000 stereo system. My kaiser worked flawlessly with it but with the touch pro it wont pair at times and when it does it wont let me use any of the many functions that the stereo offers (voice dialing, downloaded phonebook, etc) I assume this is a problem with the ms bluetooth stack and was wondering how tough of a job it would be to switch to a broadcomm stack or if anyone has thought about making a custom rom with the broadcomm stack. Just curious if Im the only one with issues with wm 6.1 and bluetooth.
i have the same problem with my diamnd anbd jvc car audio
Slightly OT rant:-
I had the opposite problem with pioneer + broadcom...
Pioneer only looks for handsets which identify themselves as phone or smartphone, and my device identified itself as a pda.
I actually told pioneer about the problem, and rather than forwarding on to the developers, I got a stock reply:-
"This phone is not on our compatibility list" (so we don't care)
So I went and got an MS based phone (you can change it to smartphone with a regedit).
Never buying pioneer again...
- Anthony
Similiar issue with my opel carkit.
Tried to make the broadcom stack working, but got a memory error when opening its blue tooth manager.
After uninstalling, bluetooth didn't work at all anymore, needed to perform a hard reset.
Has anyone successfully installed the broadcom BT stack on the touchpro/raphael?
I found that my Touch Pro would pair and then drop out when connecting to my Kenwood DDX5032 car stereo bluetooth adaptor. I couldn't dial from the Kenwood kit, couldn't use A2DP (wouldn't even connect), and really couldn't use any Headset Profile functions at all.
I persisted with pairing and unpairing in different ways (you can initiate the pairing from the Kenwood itself rather than the phone), but nothing really worked.
Then trinode's post about changing a registry setting sent me down that track and now everything is working fine
I found the relevant setting from http://forum.xda-developers.com/showthread.php?t=290871, which is [HKLM\Software\Microsoft\Bluetooth\sys\COD], and then changed the HTC TP default value of '5898764' (decimal), to the value from my old Dopod838Pro, which was '5374228' (in decimal).
I didn't even need to repair the Kewood to the HTC TP - it just worked straight away, as if it said "Oh, sorry, did you want me to work? I thought you wanted me to be in 'stupid' mode! My bad - everything will work now."
So all good, and thanks to trinode for pointing me in the right direction.
Codenix.
After hard-resetting my Touch Pro to fix another separate issue, now this problem has come back and this time changing the COD value hasn't fixed it. It would appear my previous post may have attributed my success to the wrong thing
The search for the answer continues!
I found a firmware update for my Kenwood's bluetooth adaptor which fixed the problem. I don't know why it ever worked at all before this update, but there you go!
I'll create a separate thread to share this with others in case anyone else out there has a Kenwood bluetooth kit and a Touch Pro or a Diamond.
Thanks.
The thread I created re the Kenwood is at http://forum.xda-developers.com/showthread.php?p=2835805
@ Trinode
Pioneer sent my unit back, but never told me that my phone was not supported. Where did you flag the smartphone in the registry? Did it fix the BT connection/unti reboot issue? I had a AVIC F500BT (sold it) now have a AVIC X910BT same issue as the 500 had.
@ Trinode. I found the hack , tried it, but it still doesn't resolve my issue. Are there any other mods out there for the BT Stack prob?
Since some months I have a german VW Passat with RNS510 radio system. Pairing with my HTC One S (TrickDroid 9.1, latest Radio 1.15) and addressbook access is no problem. But when I enter the car the automatic connection works only in about 1 of 10 times. If it doesn't connect I will have to manually retry it and after a couple of times it works then. Connection is stable afterwards.
I would like to play a bit with bluetooth system parameters like timeout values and the like. I think there lies the reason for the problems. Can someone please point me to the system files where I could do this? Or any article where this was already described?
I have a 2014 Toyota tundra. Before the update my Bluetooth was working perfect. Since the update, anytime I turn on the Bluetooth, it reboots/crashes my stereo. Just wondering if anyone else has had this same problem?
Sam
I have a Toyota Avalon and I am also having bluetooth issues since the 6.0.1 update. I have to power down the stereo and bluetooth on the phone to get the Media audio portion of bluetooth to connect. The Call audio connects fine automatically.
I called Verizon and they have has some reports of issues with this. They documented the issue and transferred me Samsung with no resolution.
Marshmallow on all the Nexus devices appear to have issues with Bluetooth according to these sites, could the issue be a marshmallow wide issue?
http://www.androidpolice.com/2015/11/30/bug-watch-vehicle-bluetooth-call-audio-problems-being-reported-on-all-four-nexus-phones-with-marshmallow/
https://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=189188&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=189188
I just wanted to chime in. I have a 2004 Corolla and I don't have native Bluetooth audio connectivity so I use: FlexSMART X3 Bluetooth FM Transmitter. So far so good since the update to Marshallow and use with my LG HBS 750 Bluetooth Headset is ok as well. Sorry, sort of not really the same issue, but its working ok since Monday, when I took the OTA update to Marshmallow. Hopefully they Verizon/Samsung has a fix for this issue.
Same issue
I have a 2015 Highlander and have exact same issue. If you go to settings and then bluetooth, click the sprocket next to the paired toyota device and turn off contact and call sync, it will stop crashing your Toyota stereo. It does mean that your contacts and call history will not show in your Toyota system. I reinstalled android 5.1.1 from www sammobile.com/firmwares/database/SMN920V/ download 5.1.1 and follow the instructions at the bottom of the page. The download takes about 2 hours but worth having my toyota stereo working again. I have contacted Toyota and Verizon and both have been zero help. :crying:
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
nickelnine said:
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
Click to expand...
Click to collapse
I am having the same issue with 9.0.2 OOS. So not sure if this us a compatibility issue with more than 1-2 years old vehicles or something else? Glad to hear that OB7 is working fine for you. Hope fix is coming soon. It's simply annoying.
I am having car connection issues as well. I have a 2010 Ford Edge. Just moved from Sony Xperia XA1 Ultra on Orea to my first OP device - OP6 Pie 9.0.2 - I can connect to my car initially but once I turn off my car, I have to go through a series of reconnect steps. I called tech support and we spent about 45 min troubleshooting - of course I was told I was the only one who had complained of this issue - anyway no resolution. The only way I can "reconnect" is to go into my car's system settings and select "connect to BT device" then toggle bluetooth off and on in the phone - sometimes this works with the first go, other times I have to repeat this cycle 5 or 6 times. Simply selecting "previously paired devices" in the phone app doesn't work either.
Really a pain in the tush, because I am usually in a hurry and don't have time to go through all this scenario to get a connection.
On the other hand, I have a bluetooth ear piece (made by Samsung that is like 5 or 6 years old) that reconnects every time I turn it on, no problems.
Car connections too but was not present in omni
I found for stock, performing a network reset (mobile, wifi Bluetooth) then restarting the device fixed the Bluetooth connection issue.
For custom non-stock ROMs, for my issue at least, I found its not a Bluetooth issue at all but rather the mobile network drops and the car Bluetooth cannot reconnect. The same network reset as above does not work but what does work is toggle off the "automatically select network" and manually select the mobile network from the menu that pops up. This keeps the mobile network intact (until the next device reboot, at which point repeat the steps) with the car and all is good.
I only figured it out by accident; hope this helps others.
I'm pretty happy with the phone overall but I can not get Bluetooth media audio to playback on my 2015 Cadillac SRX (generation before Android Auto).
Phone connection is working fine. The phone is paired and Media audio is enabled on the phone. In the car when I try to select the source it just says "No other sources found" (though it does say the phone is connected).
Cue Versions:
Software Info: 23228505
HMI Build (from Home+Vol Down): GMG2_14.0F105
Phone is running Pie v1.11.
Any other Cue users out there? Is it working? What version is your car at ?
I recently had the same issue with 2014 Mitsubishi Outlander SE (suv). I got this phone one week ago and I couldn't play the media over the bluetooth even though bluetooth on my phone said it's connected (Hand Free System- Connected). On the infotainment screen, it said no connected device which is weird. I hope there is solution to this issue.
Thanks for chiming in, crazy1990. I did also post in the ZTE forum. Maybe it'll get some attention there. Guess I could also contact customer service directly.
In the meantime I did order this so I can get audio (through the AUX port) while keeping the phone charged:
https://www.amazon.com/gp/product/B07S33GV3V/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
Hmmm, it worked fine the first time I used it, the 2nd time the phone did charge. I'll play with it some more.
Just a follow-up... Received the Android 10 update from ZTE on Friday and the Bluetooth media problem with the 2015 Cadillac Cue is fixed.
Hopefully this will help crazy1990 too.
That's good to hear! I live in the US, so I don't know when the update is coming and I am waiting for it.
Hello, I received android 10 update few days ago. I confirmed that Bluetooth media streaming is fixed.