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?
[I'm running a stock 7.1.1 without root or any other mods]
BT doesn;t work with 2 BT devices which can do phone...
Example:
1) BT watch, Huawei Watch connected - this watch can receive and make phone calls... It has a microphone and speaker, so it works like a full-fledged phone device. It is basically **** Tracy device... look it up ...
2) When the watch is connected, another BT phone device, like a car kit, doesn't connect. You can go to BT settings and manually click on the BT device to connect. Sometimes, it connects w/o extra help. And sometimes, clicking doesn't connect at all. Sometimes it connects automatically. Bugs!
3) When both devices seem to be connected (even though only one is shown to be connected), both can make calls, but only the "active" one receives them...
The active being the one that was connected last.
4)
------ This was not a problem in 7.1.0. Whichever device (watch or car kit) initiated or answered a call, would be used to do the complimentary function - If you make a call on watch, you get audio for the call on watch. If you receive the call on BT car kit, you answer on it. Without fail this worked just fine. Both incoming and outgoing calls. It made sense and it worked beautifully.
-----
Until 7.1.1.
---- Now, if a watch is connected (Huawei Watch, which can act as a phone itself), the BT car kit will not connect. If you connect it manually by clicking on it in BT settings, it will connect, but all phone actions, even initiated from the watch will only work on the phone.
In other words, 7.1.1 killed BT functionality with several BT phone devices.
Why can't they fix it?
UPDATE after 7.1.2
So, 7.1.1 killed phone functionality when both a phone capable watch and another BT phone device were connected simultaneously - both wouldn't work correctly at the same time.
7.1.2 didn't fix this at all.
What 7.1.2 did was introduce new bugs: 1) Weather built-in app no longer works on my Huawei watch, it just spins the circle retrieving weather data and then just goes back to watch face, 2) The watch no longer displays some notifications, for example, SMS.
I played with all of the settings in the watch, phone, and android wear app. Nothing.
I have a theory... Google has two android development teams. Let's call them Team A and Team B. Team A works on a yearly cycle developing new android OSes, for example, they are probably working on Android O right now. Team B picks up development and maintenance duties after Team A makes the initial android release. Team B would be working on Nougat right now. Team B is comprised of rejects from Team A; they have very little talent, attention to detail, or even skill. They may fix 1-2 bugs in an incremental android version, but they introduce 5 more new ones.
This is why Android 7.1.0 was less buggy than 7.1.1, and conversely, 7.1.1 was less buggy than 7.1.2.
Me with my powerbeats it seems to work but eventually it will stop playing music so I turn off headset turn back on and music starts playing again and then the music will start skipping because it hears background noise. It drives me nutts.
..
--
Worked for me.. I could connect to my headphones but yet it acted like it was not connected. Connected to my truck yet it acted like it was not connected.. I for the hell of it wiped dalvik/cache and now it all works with no problems. Headphones instantly worked after doing it. Truck worked just fine this morning..
Sent from my Pixel XL using Tapatalk
--
..
Sent from my Pixel XL using Tapatalk
I'm on stock like the OP. My bluetooth issues are similar and I have one more.
Devices I'm paired to disappear from the BT list. I got in my car yesterday and was surprised the screen needed me to enter my PIN as I had my car in Smart Lock. Go look and sure enough not connected to the car and the BT list doesn't have my car listed as a device. I had to re-pair to the car. Then I had to readd to Smart Lock. This has happened with other BT devices (primarily headsets as that is really the only other things I use with my phone). This happens frequently and almost daily that I lose one or more BT paired devices from the list.
Other times, primarily with my Bose QC35 as I frequently turn it on/off, it will be in the BT list but the phone says I need to pair the device again. This only happens about every 10th time I turn the headphones back on.
Unfortunately, I've only had 7.1.1 on this phone as it is only a few weeks old. So I don't know if stuff would have worked in 7.1.0.
djr4x4 said:
Worked for me.. I could connect to my headphones but yet it acted like it was not connected. Connected to my truck yet it acted like it was not connected.. I for the hell of it wiped dalvik/cache and now it all works with no problems. Headphones instantly worked after doing it. Truck worked just fine this morning..
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'd like to know what you did to make things work.
Updated op with 7.1.2 info.
So I had been on the beta version since it was released and participated a few times in the thread here: https://forum.xda-developers.com/pixel-xl/how-to/android-o-beta-issues-t3609335 and others were having the same issue.
The issue is no song/artist information being displayed on my touchscreen stereo, and I cannot use the stereo to pause/skip to the next track (I have to do it through my phone). Ive tried a local audio player, Google Music, and Pandora all to no avail. The deck is a Pioneer double-din AVH-P8400BH.
In my daily car, my phone bluetooth name appears and I can change song ect thru the deck. It is not a touchscreen and it probably 10 years old.
Ive gone into the bluetooth settings and have tried changing the AVRCP from 1.4 to 1.6 (neither work), and audio codec from default to enable optional (neither worked).
Anything else I should try out?
TIA
Please add your experiences to this website... they currently have over 100 replies of this issue and some other Bluetooth issues. https://productforums.google.com/fo...eDphsoOJ4;context-place=forum/phone-by-google
I had the same issue, but a simple unpair and forget from both devices then repair fixed my problem
marcjc said:
Please add your experiences to this website... they currently have over 100 replies of this issue and some other Bluetooth issues. https://productforums.google.com/fo...eDphsoOJ4;context-place=forum/phone-by-google
Click to expand...
Click to collapse
Ill throw in my comments, thanks for the link!
mjc2251 said:
I had the same issue, but a simple unpair and forget from both devices then repair fixed my problem
Click to expand...
Click to collapse
Ill have to give this a shot!
mine has awful streaming. It has so many skips...snags...audio blanks...whatever term you want to call it....its not "uninterrupted".
I was hoping google IMPROVED Bluetooth. I don't understand why they have this struggle to be honest. Its 2017....Bluetooth is not new technology.
Maybe they should stop expanding their department to provide data to the government to spy on private citizens using smart devices, and they would use those resources to fix bluetooth
Pioneer brand head units in particular I have seen Bluetooth streaming issues when paired to flagship model phones for years...even back as far as my LG G3. I got a Kenwood head unit instead, never had an issue.
As far a the Pixel XL and BT streaming...I have only had issues with dropouts zap sounds or pops, when i am out mowing my back property with my tractor...phone in pocket and BT headphones on. But my previous phones did this...most certainly due to the railroad nearby and high rise high voltage power lines and towers that are above me in that area.
speedingcheetah said:
Pioneer brand head units in particular I have seen Bluetooth streaming issues when paired to flagship model phones for years...even back as far as my LG G3. I got a Kenwood head unit instead, never had an issue.
As far a the Pixel XL and BT streaming...I have only had issues with dropouts zap sounds or pops, when i am out mowing my back property with my tractor...phone in pocket and BT headphones on. But my previous phones did this...most certainly due to the railroad nearby and high rise high voltage power lines and towers that are above me in that area.
Click to expand...
Click to collapse
Pioneer uses a cheaper bluetooth and never updates the firmware of the chips to fully support the available Bluetooth profiles even when they are developing their units and new profile updates are available. I have had a very long and annoying history with them to the point where I was in direct contact with their build team after all my complaining. That was back in 2012. Never used another of their products again. :good:
I have the same issue on my Chevy Colorado 2017. Everything works fine on Spotify on my Huawei Mate 9, and iPhone 7. It also worked fine on 7.1.2. Spotify works and music comes through but no info is displayed. I unpaired both things with no success. Frustraring.
I tried unpairing mine as well, no luck either
stupidchicken03 said:
I tried unpairing mine as well, no luck either
Click to expand...
Click to collapse
Have you tried unticking "media" in the profile hitting ok, going back in and ticking media again?
pcriz said:
Have you tried unticking "media" in the profile hitting ok, going back in and ticking media again?
Click to expand...
Click to collapse
I have not. Ill give it a shot today.
No idea if this problem is related or not but might be worth a check if you have time. First time I put Oreo on my phone it was fine. Then I screwed something up and just ADB flashed the image again. Everything was fine until I tried bluetooth a few days later. It wouldn't connect until ticking that media box many times. Then I flashed the image again and it worked fine again.
So I just got the 8.0 OTA (not on beta). I see in the dev options that it shows what BT codec it is using.
I have noticed that only the option "Bluetooth AVRCP Version:" is the only value that changin it does it stick. The other setting appear to be on auto and revert to auto depending on what device u pair supports.
My first test on my Kenwood KDC-BT762HD it paired fine and it said it was using AptX. Streamed for a few min fine. Then after I got back in the car and it auto paired, music started skipping every several seconds. I turned radio off then on to repair it and it started streaming fine again....but was using SBC according to Dev options.
When I changed AVRCP version to 1.6.....it connects and uses AptX fine. However, the radio display no longer displays the BT media metadata(title/artist), but the controls on the radio still work. I change to AVRCP ver 1.4 and that restores metadata, but then it uses SBC again. (using ver 1.5 results in SBC and no metadata).
I don't really care about the song info not being displayed on my radio....but definitely seems to be something fishy with BT in this new update.
EDIT Update: so now I am noticing it auto re-connecting and using SBC all the time now. WOnt use aptX unless i delete the device and re-pair it. then it works for a few reconnects, but then drops to sbc cagin.
Thanks for posting, I won't be updating. The Bluetooth has never been right and now seems to have regressed.
Sent from my SM-T280 using Tapatalk
i think i'm having slightly fewer drop outs with oreo than with nougat. my moto x pure on marshmallow was really bad.
FZ1Darren said:
i think i'm having slightly fewer drop outs with oreo than with nougat..
Click to expand...
Click to collapse
i agree and although i dont get the proper song listing on my car stereo it seems everything else is better. on nougat my BT headset i use for work all day (moto buds) would often stop connecting properly and i would make a call and have to select "phone" then "headset" again to get audio back on headset and om Oreo it happens less frequently
fletch33 said:
i agree and although i dont get the proper song listing on my car stereo it seems everything else is better. on nougat my BT headset i use for work all day (moto buds) would often stop connecting properly and i would make a call and have to select "phone" then "headset" again to get audio back on headset and om Oreo it happens less frequently
Click to expand...
Click to collapse
If you switch to a rom that uses the CAF based bluetooth (all lineageos based ones should, crDroid does for sure as that is what I use) implementation this won't happen. Still haven't been able to track down exactly why, but for now I'm sticking with CAF based ROMs to avoid this.
Do any of you guys having this issue have an Android wear watch? I've had heaps of issues with Bluetooth streaming being all "jittery" and just skipping since the update. However, I found this is basically completely fixed when I turn my android wear (LG urbane) off, or at least the Bluetooth on it.
Tried all the developer options for BT but hasn't made a difference. At the moment, my solution is turning off BT on my watch when I'm listening to music. Bit crap but it works.
I have factory reset the watch and cleared BT cache on pixel.
Any other ideas?
Is anyone else still having problems with Bluetooth on Oreo? I was hoping the official 8.1 release would help me, but I'm seeing no change. I have a Kenwood BT952HD, and experience issues similar to what the OP describes. Audio is plays fine, no unreasonable stuttering. But I get no song info, and can't skip tracks. Also, the pairing isn't as automatic. Every time I turn on the car, I have to wake the phone up, and wait for the pairing to complete, which takes longer than usual.
I've tried playing with the AVRCP settings, along with clearing registrations at both ends and repairing, with no luck. Is anyone else still seeing similar issues?
8.1 working fine with my Kenwood BT762HD. I use PowerAmp v2 alpha build 704 app.
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.
My Bluetooth in car works great until I either get a phone call or try to make a call. It only comes through the phone. I've deleted both profiles, car and phone, reconnected, still nothing. When I pick up the phone there is no option to use the cars multimedia system. I'm on the pixel beta program, maybe that's the issue, I don't know. Any help would be appreciated, thank you. 2011 Toyota Camry.
Welcome to Google fixing bluetooth issues, ever since they said they fixed the bluetooth issues (I never had any) they broke them for me, since Feb update my bluetooth connections to every device I own drops the connections. I have repeatedly removed and readded, even at one point my phone lost every connection anyways and had to add them again.
THe call issue you raise happens to me on any bluetooth device, I generally have to switch bluetooth off and on again, or just switch to the phone no bluetooth. My car also looses all the information on the display from bluetooth, music will drop and if I press play it will start to play again with no info until I disconnect the phone and connect again, this happens in two of my cars
My Bluetooth has been fine all along, since the end of October when I got my phone, and is still fine now in the car or with anything else I've paired it with.
I wish I could offer some helpful suggestions. I hope the issue gets fixed for you. On a side note, I wonder which old Bluetooth standard your car is based on and if that has any impact on whether someone has an issue or not.
koi102445 said:
My Bluetooth in car works great until I either get a phone call or try to make a call. It only comes through the phone. I've deleted both profiles, car and phone, reconnected, still nothing. When I pick up the phone there is no option to use the cars multimedia system. I'm on the pixel beta program, maybe that's the issue, I don't know. Any help would be appreciated, thank you. 2011 Toyota Camry.
Click to expand...
Click to collapse
You could try changing AVRCP to v1.4 (in Developer options), then re-pair phone.
Last option would be to reflash Android using AFT (back to public stable)
That's what I was afraid of, I'll try the first and most likely end up doing the second.