Related
I've been using my Galaxy 3 for a couple years with my car's stereo to listen to MP3s and Audio Books and hoped to continue doing the same with my new Note 4 DE.
Previously, once everything was paired up and working fine, if I turned off the car to go into a store or work or whatever, when I got back in and started the car up, after a couple seconds the bluetooth device would just continue playing where I left off.
Now, when I start the car the stereo flashes "acquiring Bluetooth data" and then for like half a second it shows the normal screen with the info on what the phone is trying to play, like track listings and all that, then instantly flashes back to the "acquiring..." message, and repeats endlessly.
I have to turn off Bluetooth on the phone for a second to get it to stop, then I re activate Bluetooth and have to either re-pair, or change the stereo source to FM/CD/etc, then back to Bluetooth, and then it will start working as intended.
This thing is brand new, all stock software except the basic root done on it.
It's not a Bluetooth or note 4 issue and maybe more of an interoperability issue. I have a Rav4 with my note 4 stock retail and it functions like you describe with automatically starting when I enter the car. It starts where I left off.
Is anyone else having issues with their 5x connecting to their car's bluetooth automatically (I drive a 2015 Subaru Forester)?
My Nexus 5 would always just automatically connect, but since I switched to the 5x I have to either connect to the car from the phone or vice versa.
I'm sure I could work something out with tasker or whatnot, but that feels to me as though it should not be necessary?
I have yet to get back in my car after pairing to my bluetooth adapter (I just paired this morning) but I will check later.
Do you have a list of saved or prioritized devices in the car? I wonder if the Forester bluetooth is trying to connect to your first device (Nexus 5) unsuccessfully.
I have a 2014 Ford Focus. The bluetooth will connect automatically, but I have noticed weirdness when placing calls. The car will take a while to initiate the call and then display an error saying "call cannot be completed". Then, 2 seconds later the call audio (ringing) will occur.
I am hoping that these are just some initial bluetooth issues that will be ironed out.
I had deleted my old device from the car's memory.
Another thing I am experiencing is that even if my phone IS connected, the calls are going through the device, and not my speakers.
It still pauses the music...
It could be either my car or the device. I've heard of other Subaru owners having issues with multiple devices in their car, just wasn't sure if it was a little of Column A and B. It seems likely enough it's a little bit of both.
No issues at all. I have a 2012 Dodge charger with the 8.4 Uconnect. This phone actually connects quicker than my S6 edge did and the sound is louder at max volume (on the phone) than the S6E. The only thing that doesn't work is the text messaging from the Uconnect, but overall I am very pleased.
stu_brainsurgeo said:
I had deleted my old device from the car's memory.
Another thing I am experiencing is that even if my phone IS connected, the calls are going through the device, and not my speakers.
It still pauses the music...
It could be either my car or the device. I've heard of other Subaru owners having issues with multiple devices in their car, just wasn't sure if it was a little of Column A and B. It seems likely enough it's a little bit of both.
Click to expand...
Click to collapse
My in-laws own a 2015 Forester so perhaps next time I see them I'll try to pair my 5X. May be a while before that happens though so don't hold your breath
2013 Honda Civic here (so cool, I know). I'm getting mixed results on it automatically connecting. Sometimes yes, but other times I need to connect manually. Yesterday, Bluetooth audio got really choppy in the car, and I had to restart in order to stabilize that again. Have not seen the choppiness issue with my other Bluetooth devices.
Sent from my Nexus 5X using Tapatalk
I had no problem with my Mazda 5 connecting to my Moto E on 4.4.4, but since the upgrade to 5.1 I now have to turn bluetooth off then back on every time I get in the car for it to connect. Also, the connection can drop. I tried deleting existing connection data from both car and phone, setting up from scratch, but it hasn't made any difference. Wish I could downgrade by phone's OS back to 4.4.4.
Might depend on the sound system. Reconnects to my 2013 VW Passat every time.
Sent from my Nexus 5X using Tapatalk
No issues in my Audi or aftermarket radio in the Subie... It sounds like you may not have calls being routed through the phone (based on your comment), maybe that is causing the connection issue? Something like only a phone connection is automatically connected (and the audio comes with it), but an audio connection is not?
I have a 2011 Mitsubishi Ralliart and i don't have any issues with my 5X auto connecting to the factory bluetooth system, my problem is the factory bluetooth is garbage since any time someone calls there is too much interference i can't hear what the other person is saying.
JC Why said:
I have a 2014 Ford Focus. The bluetooth will connect automatically, but I have noticed weirdness when placing calls. The car will take a while to initiate the call and then display an error saying "call cannot be completed". Then, 2 seconds later the call audio (ringing) will occur.
I am hoping that these are just some initial bluetooth issues that will be ironed out.
Click to expand...
Click to collapse
Exact same issue here but with a Kia. As soon as the phone "reacts" to a call being started on the headunit, the headunit says "call was hung up". As soon as the call is answered, it offers to be used for handsfree. It's as if the phone's "CallStatus" messages over bluetooth aren't correct
Subject crosstrek 2014, BlackBerry z10 never had an issue whatsoever, but since I got my 5x, I get half a connection (Bluetooth connects with no audio), with 6.0.1, no automatic connect... Blackberry's reputation may be downhill, but I sincerely miss its reliability and the hub...
Nexus 5X and 6P Uconnect 8.4 Grand Cherokee 2014
I recently started experiencing a similar issue.
I use my 6p for music and audio only, and my 5x for phone calls and sms.
About a week ago, they would stay connected as long as nothing was being streamed. However, as soon as I received a call on the 5X, the phone would lose BT connection to the system, and then connect back after about 30 seconds. It would do that throughout all of the calls, regardless of the length of each call. After the first 2 calls, I started streaming music from Google Play Music on my 6p, and the same thing would happen.
I removed Uconnect from both phones, and both phones from Uconnect. Paired them back again, and it is still doing the same thing.
I will try resetting the Uconnect to factory default later today and see if it has any positive effect, and will post my findings here.
If anyone else has a uconnect system with the same issue, please post it here, and we can try looking for a solution together.
Thank you,
Didn't get any response after nearly a week in the AT&T forum, so I'm reposting here on a more active section.
I'm having an issue with my bluetooth holding a connection with my 2013 Honda Civic LX. When listening to music through any music playing app, the connection always stays steady. When there is no music running from the phone, I'll frequently get a message from the display on the dash that the phone has been disconnected. The phone will usually reconnect in a second or two, with another display indicating that it has been connected. This will happen at least two times during my commute to work (25 minutes), oftentimes as many as five times. When I am actively in a phone call, the disconnects seem to be more frequent. It has a timer on the display that shows how long the phone call has been active through the car, and it rarely gets above 3 minutes before the call gets routed back to the phone's speakers while the bluetooth reconnects. The strange thing is that my wife's LG G4, also AT&T, has absolutely no connection issues at any time. I switched phones with her for a week just to confirm since I'm the one generally driving this car, and I didn't have the car drop the connection to the phone even once. Before that week, her phone would have occasionally been used when we were both in the car and she wanted to listen to music through her phone, so it had been connected to the car for more than a week.
I factory reset the phone just to see if there was a strange software issue causing the problem. After the factory reset, the phone and car had a steady connection with no drops for about a week. When the problem came back and was obviously just as bad as before, I tried another factory reset. Once again, the connection stayed steady for about a week before I would get disconnects again. At this point, I contacted AT&T, who replaced my phone thinking that it could be a hardware issue. A week after getting my replacement, the issue popped up once again.
Besides factory resetting, which is the only thing I've found to fix it at least temporarily, I have tried a few different troubleshooting steps. I have cleared cache using the storage screen in the settings menu. I've deleted the phone from the car's connection list. I've re-paired the phone to the car without giving permission for contacts or messages. Also tried to just do a simple reboot of the phone, as well as turning bluetooth off and back on. None of these have any effect on the connection issues once they start coming up.
I can take the car to Honda, but judging on the fact that my wife's phone works just fine in the car, I'm convinced that it is somehow an issue with the software on my phone. My phone is not rooted, and is currently running Android 5.1, S/W H81010o, Build LMY47D.
I don't know what the solution is but I'm having the same problem with my verizon g4. I also drive a 2013 civic but wife's galaxy s6 doesn't have any connection issues.
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?
Anyone else having issues with connecting the 7T to their car and getting audio going out of it? My OG Pixel didn't have a problem, but I have to toggle off/toggle on Bluetooth and then manually tap the car's bluetooth listing to get it to actually 'connect' the audio portion.
Rather annoying, considering I'm only in the car for a few minutes at a time, this either eats into the time entirely, or makes me sit in my car for a couple minutes before even driving to fiddle with the bluetooth settings.
Car has stock headunit, 2015 Evo X. Like I said, original Pixel XL had no issues, but this is annoying. I've tried changing bluetooth versions to no avail. I can see it connecting and dropping the bluetooth connection fairly frequently while staring at it and trying to 'get it going'. But once it connects, it stays there.
My bluetooth headphones (Some knock off cheap Chinese ones for $20) don't seem to have an issue.
My connection to my aftermarket stereo is fine. Just seems a little quieter than my last phone. Connecting is kind of slow too when I start my car but it is automatic.
I don't have any issues with connecting to all 3 cars (2014 Honda Accord, 2009 Pontiac G8 Gt and a 2018 Honda Fit) but I do agree that the volume seems a little lower than my previous phone (Galaxy S8).
Sent from my [device_name] using XDA-Developers Legacy app
Hmm. Weird. Is there anyway I can check for logs to find out what exactly is happening? I haven't rooted, just don't know if it's something I can naturally pull from Android as a whole.
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
My bluetooth is quiet, but its also static-y. I never had any issues with my G6 and now I get static clipping every 10 or so seconds. Its unbearable.
jagadeesh16 said:
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
Click to expand...
Click to collapse
I'm not really having an issue pairing it, but it's just connecting after pairing is the problem.
I have changed the default pin. I can see it popping up and down the car stereo a few times in the bluetooth settings before it just gives up.
As for the other issues, I'm not having a problem at all with audio volume, nor popping/static when it finally does connect.
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Phreak411 said:
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Click to expand...
Click to collapse
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Milkshakes00 said:
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Click to expand...
Click to collapse
LOL that would be my luck
.
My OnePlus 7t connects fine and phone works for calls on 2014 cts. The sound comes out of phone can change song on head unit but I can't get audio to play through car. Anyone else get this?
Yeah music stutters with car player... Only calls work. Music works on headphones etc. I couldn't find solution, did network reset, cleared cache. Nothing works.
Seriously!
I've wasted at least two hours already trying all the recommended steps: from flicking icons on and off to a full phone reset.
Still no connection to my Suzuki S-cross car. Multiple previous phones have connected effortlessly.
Even the $50 temporary five year old borrowed phone could handle it.
Anyone got any other suggestions? Yes, tried the AVRCP setting change from 1.4 to 1.6. That didn't work either...
Barebones system reset from scratch running O2 OS 10.0.6HD65AA
Any suggestions greatly appreciated.
I need to be able to talk and drive!
Reset the car radio and clear all pairing data if you can. Then try again.
autosurgeon said:
Reset the car radio and clear all pairing data if you can. Then try again.
Click to expand...
Click to collapse
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
mikefnz said:
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
Click to expand...
Click to collapse
Yep most have lots of tedious steps that are different model to model and if not followed exactly will cause this problem on occasion..
In my case music starts to be scrambled after 10 minutes or so of listening. When I take the phone (so the watch pops up) or turn on the screen it immediately works fine again, but when being put aside and the screen turns off, the issue starts again ..
Also in the early days of my previous 5t I had the same issues but some fix was delivered together with oxygen os update. And now the same story again
I have a different issue with Bluetooth:
- OP7T connects to car Bluetooth fine
- I can make/answer calls
- Bluetooth media works fine
The problem is with Google Assistant & car audio:
- it was working as intended until the latest update - 10.0.15 - I was pressing the button on the steering wheel the google assistant was answering questions through the car bluetooth, no need to switch to bluetooth media.
- after the latest update, when I press the button on the steering wheel, Google assistant pops on the phone , starts to answer question, but cuts off after 5 seconds. the command still goes through and Assistant still runs, but does not come up on the car audio.
- it looks like the Assistant is not connecting to the car as a hands free, but as to a bluetooth handsets.
Anyone experiencing this?