Develop Bugs

Bluetooth connections problems.

Has anyone encountered issues with connecting with a car bluetooth? My wife phone conntects with no issues.. She can use the cars remotes to make and receive calls.. Mine I have to pick a contact from the phone for it to work, it will not work with the car or my work truck controls.. It seems everytime it ask if my car or truck can access my contacts, I always choose allow, but nothing happens, but it works with the wifes.. This is with the Lollipop update, that we both have...

happened to me I just rebooted my phone and it connected, also check settings for that paired device

Rom-Addict said:
happened to me I just rebooted my phone and it connected, also check settings for that paired device
Click to expand...
Click to collapse
Got one to work, in my truck.. The car it worked for a while, then quit.. I will try it agian to see if it will stcik... Most likely caused by the 5.0 update..

I've noticed a Bluetooth problem that suddenly started in the last week or so. I upgraded to Lollipop when it first hit, and didn't have any problems.
Now, however, after Bluetooth works fine for awhile (I can connect to a Pebble watch, Bluetooth speaker, car Bluetooth, etc) all day long - then all of a sudden it can't connect to ANYTHING. Toggling Bluetooth off\on doesn't fix it.
Restart the phone, then everything works just fine for awhile. Until it doesn't, and I have to restart again.
Anyone else experiencing this pattern?

I've actually had the opposite happen. I have a iSimple bluetooth box in my car. I've never been able to auto connect with either VZW Note2 or 4. The CS rep told me it had to do only with VZW phones and he couldn't help me out. On another forum, another member mentioned he didn't have any issues with his older phone, so I dug out my old HTC Incredible. Sure enough, it would auto connect. Something changed with Lollipop, and now my Note4 will finally auto connect to the iSimple box. I tried using a third party Bluetooth app prior, but it didn't fix the problem.

Finally got the one in the car working as well... Because the wife and I have the same phone, I just simply changed the name of my phone and it works fine..

If your talking about the developer edition one rom update.. YES.. What fixed mine was wiping everything and redoing the one rom lollipop, then twrp, then installing Ricks Rom Lollipop, things have been perfect. I even addressed it in the ricks rom thread the week.

I haven't had any issues connecting devices but since Lollipop, when I am connected to a bluetooth speaker (car, bose, other bluetooth speakers) the audio gets choppy randomly.
I have done some searching and found others (LG g3) who had the exact same issue after updating to Lollipop.
I have tried rebooting, using different music apps, unpairing/pairing, forgetting the device ect and nothing seems to work. Anyone else having this problem after updating to lollipop? Anyone know how to fix it?

Bluetooth error

Hi,
Couple weeks ago I update my device HTC One (M8) with 5.0.1 android version. After update I'm having issues with my built in car bluetooth device. It is older version 2.0 bluetooth. It connects as usual, but when I am trying to make a call, it connects and disconnect every second or so. It is not related voice, or "beep" sound. It just disconnects, and immediately connects to my car bluetooth.
Is there any way to fix this problem? Or maybe there's a way to rollback bluetooth device software (but not all system update)?
I have already tried standard issues - unpairing, changing device names, restarting. Nothing seems to work.
Thanks

try safe mod
just search for ./.how to enter safe mod on htc one m8?.,.,,./
if that fixed it then another application is making the problem

Bluetooth Not Connecting - Worked Previously

OK, so I got everything working on my unit back in November. Bluetooth worked fine and connected with my phone and OBD device (OBDLink LX).
Suddenly within the last couple of weeks, it's stopped connecting. I have tried rebooting the radio, unplugging/replugging my bluetooth OBD, unpairing the phone, repairing, etc... Nothing seems to work for more than a few minutes. Sometimes it will work for one trip, but then the next trip it's back to REFUSING to connect to either bluetooth device. Remember - BOTH worked before, and I didn't change anything.
Since it's happening with both my Phone and my OBD device, it appears like it is a fault in the stereo. I really don't want to do a full factory reset as that would entail many hours sitting in the car wasting gas idling while I reinstall/reconfigure EVERYTHING only to not even be sure it won't do this again.
Anybody have any tips on something I can do to fix this? There does not appear to be any kind of "unpair" option in the bluetooth settings on the radio itself. I'm wondering if there's a way I can manually reset just all of the bluetooth settings - blow them away and start over without resetting the whole device.
This is a pretty big deal - one of the #1 reasons I bought this device was for OBD datalogging. If that feature does not work, I will rip it out of my dashboard and ebay it. PERIOD...
Adcice?

Nobody?
I tried changing the bluetooth device name, changing the PIN and re-pairing my devices. They work intermittently, but 90% of the time won't connect, or if they do, they won't stay connected.
This is turning my radio into an expensive piece of garbage...

lotherius said:
I tried changing the bluetooth device name, changing the PIN and re-pairing my devices. They work intermittently, but 90% of the time won't connect, or if they do, they won't stay connected.
Click to expand...
Click to collapse
Try keeping wifi on all the time (even if not actually connected to any network).

themissionimpossible said:
Try keeping wifi on all the time (even if not actually connected to any network).
Click to expand...
Click to collapse
I do have Wifi on all the time. I have an LTE Hotspot I keep in the glovebox of my car that powers up as soon as the car powers on. So there's 100% wifi coverage for my stereo no matter where I'm at.
I can randomly get it to connect, but it won't stay connected. When I'm in the bluetooth menu, the devices will actually disappear from the paired devices list. Both paired and available will go blank just suddenly as the devices drop off. Then they'll reappear on their own. So it appears to be the bluetooth stack is crashing - but I'm not sure why.
It is a KLD RK3188 unit. Running latest MCU (came preloaded, just bought it in November - I haven't put a new MCU) and recent firmware, which is a stock firmware, not MalaySK (MalaySK doesn't support the digital display below the screen on my unit)...

At this point this unit is trash if I can't keep Bluetooth working more than 10% of the time.
Sent from my OnePlus One.

lotherius said:
I can't keep Bluetooth working more than 10% of the time.
Click to expand...
Click to collapse
Some smartphones might show an incompatibility with the radio's BT stack. To be sure try with another smartphone.

I would see if it pairs reliably with just one device at a time. My phone has issues connecting with the HU if I first connect my BT headset to the phone but works fine if I do it after. Also the construction of these seems to be sub-par and it could be the bt device or antenna in yours was not connectec/mounted well and you hit a pothole and now its not attached/broken/loose. It may be worth opening and looking inside for something that broke off or is loose. Finally, I have had (well still have) my factory settings change randomly and have to go in and reset. There are settings in the for BT module and it may be worth looking to see if yours are correct.

I also have problems with mine but I'm running Marshmallow in my OPO. As soon as i go back to Lollipop (CM 12.1) it works again.

stormlabs said:
I also have problems with mine but I'm running Marshmallow in my OPO. As soon as i go back to Lollipop (CM 12.1) it works again.
Click to expand...
Click to collapse
Turns out I think it's the OPO. Mine has issues even with 12.1. I think it's based on Modem version not firmware version. Your modem may have been changed when you went back to 12.1.
For me changing modem versions is something I really want to avoid. I hunted forever for a modem version that didn't constantly drop WiFi and LTE, finally found one, and I think that's when the Bluetooth issues started. Every time I flash a modem to the OPO it becomes a nightmare. That phone really does not want you messing with the firmware which is not what I expected when I bought it.
For now I'm back on my old Nexus 5. No problems. I may just sell the OPO and never stray from Nexus again.
Sent from my Nexus 7 using Tapatalk

Hmmm.
My OPO doesn't connect to the headset but my chinese BT OBD dongle connects fine and works.

I have the same problem with my unit but phone working.Only obd2 adapter some times not connecting.Have you find any solution?

I have a similar issue with the Pixel XL.
Previous I was on a Nexus 5 Bluetooth worked perfectly every time without fail, could make calls, listen to music and sync address book no issue.
Now since moving to the Pixel XL I have an issue connecting to the head unit. The head unit shows as a connected device, but then flashes green then grey, green, grey showing connected, disconnected... I can still stream music from my phone over Bluetooth, but voice is not achievable.
Like suggested it's likely to be the BT stack in the handset rather than the head unit as works fine with Nexus 5. Highly frustrating and likely no fix unless it can be patched by software update

I'm also having the same problem as you noodlemctwoodle on a Nexus 6P with 7.1 developer preview.
I've un-enrolled from the beta program this morning, waiting for the ota to come down, as soon as it does will re-test and let you know if it's working, as I suspect it is a problem with the bluetooth stack in 7.1

MTCD MLT (Xtrons TD618AS) Bluetooth and OBD Reader
I have had issues with the Bluetooth on the MTCD MLT V1.76_1 (Xtrons TD618AS).
I found a work around which allows me to use the OBD reader successfully. I downloaded an Android Bluetooth App and toggled off the Bluetooth. Once the Bluetooth was toggled off I was able to access the OBD reader by using the "Piston" OBD app. I tapped on the car picture and waited for the app to think about things. Once the app finished thinking I was able to start capturing the live OBD data by pressing the play picture. I am only speculating, but I feel as though perhaps the firmware engineers goofed. This is even the OBD reader that Xtrons promoted as compatible with the TD618AS stereo I bought with it at the same time. Not to mention that I continually lose FM radio even though the stereo was professionally installed and no wires were cut. I was very excited, and now only depressed.

mr.hackerly said:
I have had issues with the Bluetooth on the MTCD MLT V1.76_1 (Xtrons TD618AS).
I found a work around which allows me to use the OBD reader successfully. I downloaded an Android Bluetooth App and toggled off the Bluetooth.
Click to expand...
Click to collapse
Which Bluetooth app did you download?

Bluetooth disconnects every 12 minutes

Hi all,
I have a Tune2Air Bluetooth adapter in my car which works great with my Nexus 9 and my partner's iPhone. But when I'm connected to it with my G4, the Blueooth connection drops out almost exactly every 12 minutes (+/- 1 minute). After 30 seconds or so the phone reconnects but it's annoying as hell, especially when the dropout occurs when Google Maps is giving me a crucial navigation instruction. My phone is an international H815, totally stock, running build 20D of Marshmallow.
Here's what I've tried/observed:
The phone stays connected without any problems to my Bose Bluetooth speakers at home.
I have made sure that all power saving modes are turned off. I have added Bluetooth to the Ignore Optimizations list in case MM's Doze mode is causing this.
I noticed that when on long drives in the country the phone seems to stay connected to the Tune2Air without the usual dropout. This made me wonder if it could be an interaction to do with the cell radio that is causing the dropout. I tried just sitting in my driveway (in case it was cell-tower handoff) but the dropout still occurs. I have tried disabling mobile data and WiFi while driving but the dropout still occurs.
My mobile provider supports Fast Dormancy and I usually have this enabled. I wondered if maybe this is causing the problem (because of some difference between the city and country cell towers) so I tried disabling it, but the problem persists.
I looked in the log using logcat but couldn't see anything indicating why the connection is dropping. I tried enabling Bluetooth logging from the Developer Menu but unfortunately this doesn't seem to work.
I'd really like to solve this problem but I'm running out of ideas. Can anyone suggest anything else that I could try? Are there any other Bluetooth or mobile network timers of this approximate duration that could be causing the problem? Or any other settings in the service menu that I could try?
Thanks,
james

You can try Flashing the 20e version, much more stable than D

I don't see an update to 20e, either OTA or using LG Bridge. Reading the forums, the consensus seems to be that 20e does not differ significantly from 20d. I think I'll stick with 20d for the time being as I can't bear the thought of doing another factory reset right now.

sladflob said:
I don't see an update to 20e, either OTA or using LG Bridge. Reading the forums, the consensus seems to be that 20e does not differ significantly from 20d. I think I'll stick with 20d for the time being as I can't bear the thought of doing another factory reset right now.
Click to expand...
Click to collapse
then downgrade to a previous version of MM

Hi, This is a bit of a wild stab in the dark but with the seeming regularity it could be a service / polling issue. Have you checked the location based profiles - Perhaps the "turn off Bluetooth when I'm away from home" option is set and this is happening every 12 minutes? Like I said, bit of a wild stab in the dark/ suggestion but might be worth a check. You could also check it whilst sitting in your driveway and see if it happens....

monkeydogger said:
Hi, This is a bit of a wild stab in the dark but with the seeming regularity it could be a service / polling issue. Have you checked the location based profiles - Perhaps the "turn off Bluetooth when I'm away from home" option is set and this is happening every 12 minutes? Like I said, bit of a wild stab in the dark/ suggestion but might be worth a check. You could also check it whilst sitting in your driveway and see if it happens....
Click to expand...
Click to collapse
Ooh, you could be onto something here. I'm going to try disabling "Bluetooth scanning" setting under the Scanning menu on the location screen and see what happens. Another possible culprit is Google Location History so I can try disabling that. As a last ditch effort I will try switching my Location Mode from High Accuracy to Device Sensors Only and see if that helps. I'll report back once I can get a chunk of time in the car.
Thanks!

So I tried all of the things I mentioned previously, rebooted, and it was still doing it - disconnecting every 12-13 minutes.
BUT after some more experiments last week the problem seems to have "fixed itself". Here's what I did...
I was wondering if it wasn't an app that was interfering and causing the dropout so I decided to boot the phone into Safe Mode and see if it helped. Unfortunately it exhibited the same behaviour... Google Play Music played for 12 minutes and then dropped out. So thinking that was pointless I rebooted back to normal mode. My phone then connected to the car stereo but was in this strange mode where audio was still coming out of the speaker rather than being sent across Bluetooth. So I deleted the phone pairing and re-paired and since then, whenever I've gotten in the car, the phone has stayed connected to the car stereo without dropping. Note that this isn't the first time I've deleted and redone the pairing... I'd tried that several times to try and fix the problem. The only new ingredient was going into Safe Mode. Not sure if this cleared something some state in the Bluetooth settings but I'm not complaining.
On the other hand, this is also fairly unsatisfying as it's not clear what "fixed it", and should it happen again I don't have a great degree of confidence that I'll be able to fix it again. Still, it's a step in the right direction and I'm going to enjoy it while it lasts.

So I think I've finally fixed this once and for all. Thought I'd share here in case it's useful to someone one day.
The problem started happening again after I accidentally deleted the pairing and had to re-pair it. Not sure why but I thought to tap the little cog next to the Tune2Air entry in the Bluetooth Devices list. I was surprised to see that under PROFILES both Call Audio and Media Audio were selected (the Tune2Air device I am connecting just supports Media Audio and doesn't do phone calls). So I unticked the Call Audio, reconnected the device, and everthing's been fine since.
I'm not sure whether the device is advertising that it supports Call Audio or whether the G4 is just assuming that it does. Actually the G4 connects just fine to my Bose soundlink (and just shows the Media Audio profile) so I'm think there's something funny with the BT implementation of the Tune2Air device.
Nevertheless, it seems odd that the phone should drop the whole BT connection after 12-13 minutes if it can't connect to call audio. Maybe someone more familiar with the Bluetooth stack can tell me if this is acceptable behaviour or if the G4 is doing something weird.

sladflob said:
So I think I've finally fixed this once and for all. Thought I'd share here in case it's useful to someone one day.
The problem started happening again after I accidentally deleted the pairing and had to re-pair it. Not sure why but I thought to tap the little cog next to the Tune2Air entry in the Bluetooth Devices list. I was surprised to see that under PROFILES both Call Audio and Media Audio were selected (the Tune2Air device I am connecting just supports Media Audio and doesn't do phone calls). So I unticked the Call Audio, reconnected the device, and everthing's been fine since.
I'm not sure whether the device is advertising that it supports Call Audio or whether the G4 is just assuming that it does. Actually the G4 connects just fine to my Bose soundlink (and just shows the Media Audio profile) so I'm think there's something funny with the BT implementation of the Tune2Air device.
Nevertheless, it seems odd that the phone should drop the whole BT connection after 12-13 minutes if it can't connect to call audio. Maybe someone more familiar with the Bluetooth stack can tell me if this is acceptable behaviour or if the G4 is doing something weird.
Click to expand...
Click to collapse
Just wanted to give a huge thankyou to you from the future, sladflob. Doubt I'd ever have thought to disable call audio for pairing to my bodged Bovee bluetooth adapter, and this has solved my constant dropout and reconnects.
Happy days!

OTA May 2018 Update + Car Bluetooth Music issues

Hi all,
Has anyone experienced any weird Bluetooth issues after installing the latest May OTA update (OPM1.171019.011-RZR-180509.5038)? I've realized that the BT controls on my 2015 Nissan Sentra no longer work properly. It doesn't automatically connect to BT anymore and no track information shows on the head-unit. The weird thing is that I CAN get music to play, at least.
I just wanted to know if I happened to be losing my mind after numerous reboots and re-pairing between the car and the phone.

Same for me. I can delete it. Pair it again and it works. Next time I get in the car it won't reconnect.. worked fine before the update at the weekend.
Sent from my Phone using Tapatalk

It's a fire an miss actually. Sometimes it reconnects automatically with the car's unit (alpine aftermarket) and sometimes it doesn't. I had noticed that if I get in the car for the 1st time today (for ex), it won't reconnect back and i have to cycle around the input in order to "kickstart" the reconnecting process. If I make a stop along the way, stop the car, get out (thus interrupting the connection) and getting back after a while, it will reconnect automatically without any issues. I'm not even taking it out of my pocket. But this scenario is happening since day one, not necessarily from the last update.
On the other hand, I got a smartband (coincidentally after the last update) and now, while the smartband is connected via BT, when I turn on my BT wireless headphone adapter, it won't re-connect anymore (simultaneously with the smartband) and if it does, it's without media playback. As a workaround, I have to 1st turn off the smartband, clear the BT of any active connection (And also any other device with media playback capabilities), turn on the BT adapter so it will connect full, then turn the smartband back on. And not always works like this.
So, I do have on an off issues with the BT stability and connections with various devices, not just car unit.

Strangely though my smart watch connects no problem and the stereo in my motorhome was connecting at the weekend. It's just the car ( a Vauxhall Astra) that refuses to connect unless I delete and re pair....
Sent from my Phone using Tapatalk

I can't get music to play with Spotify or YouTube. The phone connects fine, shows song info but just won't play no matter what I try.
The weird thing is that calls work perfectly. Sound through car speakers and mic works. Just doesn't want to play music.
I've tried unpairing, re-pairing, deleting, even factory reset on both phone and stereo. Worked fine before the 8.1 Oreo update. (I'm on 3 UK handset).

Im having issues as well, it will connect the first time when I manually connect the phone and stereo to MyLink. It will say connected but (No Media) so i try to pair the media and it disconnects my phone from BT and then i have to delete device and re connect device manually. As well if i leave the vehicle or turn it off then it will disconnect. Not just my vehicle but the other showroom vehicles do that as well. Can someone let me know if there is a bluetooth upgrade or a firmware upgrade that can fix this problem? is there anything that we can do for this let me know. Thanks!!

I am having the same issue in my bmw.
I can delete the phone and re-pair... But it sucks having to do that every thing.

also having issues as well. It connects to my headphones and the after market HU in my truck but it will not connect at all to the factory HU in Genesis Coupe. I have tried to delete and re pair and still nothing.

So currently it all works for me with the latest update. It definitely takes a little bit longer than normal though. Not sure how long some of you waited, but compared to my old phones it feels like an eternity during the time it doesn't connect. I also use a smartwatch and it is always connected to that. If you guys need or want any files, let me know. I'm currently waiting for a usb-c to usb-a cable in the mail, so once that is here I can try to help.

I think this is all more of an Android issue. I was having most of the exact same issues mentioned here on my LG V20 on Oreo.
I just for a Razer Phone 1 off eBay this week. I did the Pie update and within a day, the bluetooth issues have returned. Sometimes phone won't connect to car stereo - sometimes reboot stereo, sometimes toggle phone bluetooth off/on, or sometimes just wait 10-30 seconds. Doing the same showing info on car stereo display, but no audio transmitted. I also had similar issues using a OnePlus 3 with both Dirty Unicorns and Resurrection Remix Pie ROMs. I was beginning to think it was my car stereo until I read the comments on this thread. Seeing so many others having the exact same issues on factory and aftermarket stereos (mine is an aftermarket), and knowing it's happening on different devices and both Oreo and Pie , I'm thinking it's an Android 8 and 9 issue.