Related
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?
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.
Lite. LitHi all,
I bought this morning a Pioneer MVH-S100UB radio receiver for my car. It has an USB connection for charging android phones and reading music, as well as controlling radio, music and more from your phone via the Pioneer ARC app.
I tried many times to connect my Huawei P9 Lite. The best I got was control of the radio from the app, and being able to pause/press next song from the Pioneer, but the sound was coming from my phone, never from the receiver.
I connected an other phone, HTC Desire 620, which was instantly recognized and launched the ARC Pioneer app (which doesn't happen with my Huawei). However, sound from HTC Desire to Pioneer is really bad, speeded or cut each second.
My main goal is to play music from my Huawei. Every time I connect the USB cable, I try to set the connection to MTP on the phone, but it instantly switches to charge only mode.
I tried different cables, MTP works on PC, but not on Pioneer app, i also tried USB debug mode, and switch USB connection to "audio source" via developper's options.
The fact that HTC Desire 620 is instantly recognized makes me think it's a Huawei related problem, as I have been able to see on several forum threads, including this one :https://forum.xda-developers.com/mate-8/help/play-audio-usb-mate-8-t3324704/page5
Could a ROOT save me, I'm willing to go this far hahaha.
Thanks a lot for reading meguys, have a good one
Hi.
SAd that I don't have any answer
Could a root help me solve my issue ?
Trying to pair a PS4 controller through Bluetooth and it's not working on my note 10 plus. It pairs fine but the phone seems to receive no input from it. Trying to unpair the controller hangs and never finished disconnecting. If I turn off the controller, the phone still thinks it's connected. Turning off Bluetooth takes a minute or so as well.
It works perfectly fine on my wife's s10 plus, and after it failed to work on my note 10 I tried pairing it with my note 8 for the first time and it also worked perfectly. I was really looking forward to using Samsung Dex with my living room TV and the PS4 controller to play emulated games.
Hoping this is a software issue that can be fixed and not a bug with the Bluetooth radio on my phone. My gear fit 2 paired fine and works great as far as I can tell. My headphones work fine through bluetooth and so does the bluetooth/aux adapter in my car. So it leads me to believe it could be software issues. The controller works fine on everything else.
I checked for updates and there was an Android update from Verizon but it did not fix the issue.
Also the controller works if I hook it up to USB via the USB C adapter included with the phone but the input is all wonky. Shoulder buttons are start and select, up is triangle, etc. I know there's ways to alter the input to fix that but it works perfectly by default on bluetooth on my other two Samsung phones.
I tried to see if anyone posted a similar question but haven't found anything. Is anyone else having issues with their Pixel 6 Pro while connected to Android Auto? I have 3 issues that are bugging the crap out of me.
1. Every time I connect my phone to the car, it always pops up asking permission to connect to this "new" uConnect device. Its been connected hundreds of times, and even adding it as a trusted device, it still pops up.
2. The sound quality is absolute garbage. Its muddy and heavy on the mid level. I have tried to compensate by adjusting the EQ in the head-unit, and Spotify. It helps, but not much. I have tried my old Note 10+ and the quality is perfect.
3. Often when receiving a phone call, I can answer and control the call using the head-unit, but the audio is going to the phone and not the car speakers.
I have been able to replicate this with both of our Pixel 6 Pro's, and in both of our vehicles (2019 Durango R/T, and 2020 RAM 2500)
Anyone have any ideas?
EDIT: this is wired using different cords for troubleshooting purposes.
I have none of those issues but my issue with aa is that it keeps turning off preview incoming message
Issue #3 I do get from time to time. Annoying AF. Also trusted device only last 4 hours I believe which I think is ridiculous.
imo... Spotify always sounds like crap.
Haven't had any of these issues at all. Everything works well for me on the December update.
I have none of these issues, but the issue I get is specific to Google Maps on Android Auto. When I'm navigating somewhere, often at the start of the trip Google Maps cannot get a GPS lock on me and the map skips all over the place, constantly rerouting me. After I continue to drive I eventually will get GPS lock and then everything works fine.
Using Waze on Android Auto, everything works fine. I get GPS lock instantly when I switch to the Waze app on Android Auto. So all I can conclude is the issue is specific to Google Maps... It's not that big of a deal but can be very annoying.
Edit: I'm on wireless with a Pioneer AVH deck.
My wifes Pixel 6 works fine apart from the battery icon constantly flashing on and off (on the car display)
I don't have any issues with Android Auto in my 2020 Subaru, and neither does my wife.
No, I don't have these issues either. Working fine for me on Lexus NX.
Edit: "wired" that is (to be clear).
I am not seeing any issues in my 2020 Kia Soul. I use the wireless android auto adapter (AAWireless from Indiegogo) so I do not have to plug it in though.
Could your uConnect system need an update? You can check here for one: https://www.driveuconnect.com/support/software-update.html
Caveman419 said:
I am not seeing any issues in my 2020 Kia Soul. I use the wireless android auto adapter (AAWireless from Indiegogo) so I do not have to plug it in though.
Could your uConnect system need an update? You can check here for one: https://www.driveuconnect.com/support/software-update.html
Click to expand...
Click to collapse
Great Idea, unfortunately they are already up to date on the software. That AAWireless thing is pretty cool, but plugging it in doesn't bother me that much, plus I know its charging.
GtarSkater said:
Great Idea, unfortunately they are already up to date on the software. That AAWireless thing is pretty cool, but plugging it in doesn't bother me that much, plus I know its charging.
Click to expand...
Click to collapse
I always have issues with cables that keep disconnecting and have to unplug and re-plug in (both my car & my wife's 2016 Hyundai Sonata). The AAWireless is very handy in that regards. It will occasionally freeze up, but very rarely after a few OTAs ago. The only downside that I have found is that if you get too close to the vehicle with BT Headphones (mowing or other yardwork typically), it will connect to the AAWireless and cut off audio to the BT Headphones. I just unplug the AAWireless from the car until I am done then.
I should mention all my issues only occur when I'm wireless in my car. When I use wired in my friends car, it works fine.
GtarSkater said:
I tried to see if anyone posted a similar question but haven't found anything. Is anyone else having issues with their Pixel 6 Pro while connected to Android Auto? I have 3 issues that are bugging the crap out of me.
1. Every time I connect my phone to the car, it always pops up asking permission to connect to this "new" uConnect device. Its been connected hundreds of times, and even adding it as a trusted device, it still pops up.
2. The sound quality is absolute garbage. Its muddy and heavy on the mid level. I have tried to compensate by adjusting the EQ in the head-unit, and Spotify. It helps, but not much. I have tried my old Note 10+ and the quality is perfect.
3. Often when receiving a phone call, I can answer and control the call using the head-unit, but the audio is going to the phone and not the car speakers.
I have been able to replicate this with both of our Pixel 6 Pro's, and in both of our vehicles (2019 Durango R/T, and 2020 RAM 2500)
Anyone have any ideas?
Click to expand...
Click to collapse
Personally, I do not have an Android Auto enabled car.
I can tell though that there were numerous reports in the past (XDA, Reddit, Discord, Telegram) of people having problems with Android Auto. Now the problem with that, is...
a) Android Auto has always been buggy - even with cable. I have friends that have been trying to get Android Auto to reliably work with their Samsungs (cable) for years, and their attempt are still a work in progress. It's a hit-and-miss. Sometimes it works, sometimes it doesn't.
b) Android 12 is extra buggy and has been known to cause problems with Android Auto (reports of Samsung owners upgrading to A12)
c) Pixel 6 Pro is extra special buggy and it's more or less unknown at this point, if Android Auto issues are caused by Auto Auto being a buggy mess, Android 12 being a buggy mess, Pixel 6 being a buggy mess or a culmination of the three together.
d) Plus, there is a massive difference in reliability between Android auto cable vs. wireless.
I did see some workarounds floating in the web, you might be able to find them in Reddits GooglePixel group.
In the end though, your best bet (longterm) would probably be: Go into settings, report the problem directly to Google and make sure that all your friends and family that also use Android Auto do the same.