Related
My issue today is that my bluetooth will not pair properly and remember its configurations. My initial pairing on my phone with my car's flexsmart X3 works perfect, however when I turn off my bluetooth on the phone or turn off my car and turn it back on the phone will still see the flexsmart and it will say it is paired but I get no sound. Upon further investigating I find that in the options setting that neither the call nor music tick box is checked. If I try to tick them it will think for a few seconds and then gray out and do nothing again.
I never had a problem with my note 2 or my temp replacement evo 3d remembering these settings. All I would do with those phones was pair it once and then any time I hopped in the car I would just turn onm,y phone's bluetooth and go. Now with my note 4 I have to unpair and repair the devices each and every time which is a huge pain.
I have read a little bit that this is due to samsung note 4 using a newer bluetooth standard than its predecessors. Is there anyway to circumvent this issue by maybe rolling back the bluetooth drivers or something? I even thought about creating a tasker profile to help with this but still I would have to physically press the search button on the flexsmart eachtime.
Any and all suggestions would be great. Also right now I am on rooted stock 5.0.1
PS: I will try and post some photos to help when I get the chance to get to my car.
I've been start for a solution to this since the phone came out as well. I have the same Bluetooth issues with my phone in my car. Nothing more annoying than having to turn Bluetooth on and off for 10-15 minutes of your drive before you can use the damn thing. Oh wait, more annoying would be when it's been working for a solid 45 minutes or so and then suddenly, with no warning, the Bluetooth connection ends for no reason and your cars stereo comes on instead of what you were streaming only the volume on the cars radio is far louder and it scares the ever living crap out of you
flyhighx said:
I've been start for a solution to this since the phone came out as well. I have the same Bluetooth issues with my phone in my car. Nothing more annoying than having to turn Bluetooth on and off for 10-15 minutes of your drive before you can use the damn thing. Oh wait, more annoying would be when it's been working for a solid 45 minutes or so and then suddenly, with no warning, the Bluetooth connection ends for no reason and your cars stereo comes on instead of what you were streaming only the volume on the cars radio is far louder and it scares the ever living crap out of you
Click to expand...
Click to collapse
Odd....I dont seem to have that issue. Once I have initially paired the bluetooth it will stay connected without any interruptions. Also pairing for me is really fast and only takes a minute or so. My problem is that instead of my phone remembering the current device settings that it is paired with, it will forget to associate it with calls and data after I turn the bluetooth off and then later back on even though the phone will still remember it is paired with the car bluetooth.
First world problems I know but it gets a tad annoying having to unpair and repair my phone each and everytime I hop in my car to go somewhere if I want to listen to my music.
In the car I don't get a lot of skipping. But when connected to my BT speakers audio does skip a lot and starts playing in ffw then disconnects completely. It's driving me nuts. I've tried all the usual trouble shooting also. No help. Wtf Samsung/Google
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,
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!
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?
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.