Anyone having connection issues with Bluetooth with the Marshmallow update? With Lollipop, the phone connected to the car and I never had issues. With the update it connects, disconnects, connects constantly (in a 15 min drive connects/disconnects like 3 or 4 times).
I have unpaired and connected again with the same results. Never had issue like this with Lollipop - connected once and stay.
thanks
-brad
I had some initial connection issues between my car and phone. It wasn't what you were describing. Mine just wouldn't pair. I had to delete my old pairing from the car, then pair my phone again.
---------- Post added at 09:41 PM ---------- Previous post was at 09:41 PM ----------
I'm on stock rooted 6.20.531.5
Related
Hi there!
Is anyone here the owner of a current mercedes c class W/S/C204 facelift? Im trying to connect my One X via bluetooth to the cars multimedia system, but the car wont accept it. The pairing process fails all the time. The One X lists the car in its paired partners, but the car wont. Im on stock firmware 1.26.401.2. Maybe its a problem between the different bluetooth versions? And yeah i know, its not yet officially supported by mercedes, but shouldnt the standard bluetooth connection work anyway? Any suggestions or tips? Thanks!
Phil
-Vulture- said:
Hi there!
Is anyone here the owner of a current mercedes c class W/S/C204 facelift? Im trying to connect my One X via bluetooth to the cars multimedia system, but the car wont accept it. The pairing process fails all the time. The One X lists the car in its paired partners, but the car wont. Im on stock firmware 1.26.401.2. Maybe its a problem between the different bluetooth versions? And yeah i know, its not yet officially supported by mercedes, but shouldnt the standard bluetooth connection work anyway? Any suggestions or tips? Thanks!
Phil
Click to expand...
Click to collapse
If you car stereo does not support A2DP then it will not work.
dr9722 said:
If you car stereo does not support A2DP then it will not work.
Click to expand...
Click to collapse
Hm i dont think it has, at least not the audio 20 soundsystem...but i dont know. My old Desire HD with Android 2.3.5 on the other side worked flawlessy, but it was officially supported bei mercedes...did it not use A2DP then?
I have the older W204 (2008) and have found the BT to be finnicky. I haven't tried pairing my 1X yet though. Think I'll go give it a shot and report back.
---------- Post added at 11:29 AM ---------- Previous post was at 11:25 AM ----------
Ok, did it no problem. Here's what I did -
Went to telephone mode, went to phone list, update - options - external authorization, went into the Bluetooth menu on the phone, clicked MB Bluetooth, clicked yes on MB screen, typed in 0000, did the same on the phone, pairing successful.
Hope this helps The external authorization bit is what always makes it work. Sometimes the car doesn't find the phone correctly if you try to auth from the car but when you force the car to accept the phone (external auth) it tends to work just fine.
I have a new Note 4 (Verizon) and a 2011 Kia Soul. Prior to the Note 4 I had a Note 2 (Verizon) that I paired with my car for the last 2 years without issue. I am able to successfully pair the Note 4 and the car and use all of the Bluetooth functions I would expect to work. The problem is, often (not 100% of the time), the next time I try to connect the phone to the car that connection fails. I then have to unpair and re-pair them to get them to connect. Neither side gives me anything useful in the way of error messages.
I'm at a loss as to how to troubleshoot this further. Is there a way to pull Bluetooth connection logs out of the phone?
I have the same issue, but worse. I have a 2011 KIA Sorento, and a Samsung Note 4. The Bluetooth connectivity is very intermittent. One minute is works and then stops. One minute it plays music fine and all of a sudden, the music will start going in and out, like a bad cellphone call and then disconnect. I try to reconnect and it won't. I've gotten in the car and it works great and the next time it works like crap! I've been on a cell call, talking through Bluetooth and it will automatically disconnect, but still shows connected. I have to switch to speakerphone to talk and then it all of a sudden reconnects back to Bluetooth. Does anyone know if this is a known Samsung issue? I saw a previous post from Dec 2014 which stated, " Apparently, the Note 4 and Edge all use the newest AVCRP 1.5, which nobody else uses yet. Nissan told me that they were told by Samsung, that in their next update, they're going to revert the phones back to AVCRP 1.3, which is the standard in the industry." Has this occurred?
I had the same kind of problems with my Galaxy S 6 on my 2013 F150 with Sync. I was only able to fix it by getting rid of the S6. The Note4 I had before (on 4.4.whatever) and the Note4 I have now (on 5.0.1) have no issues.
The problem is to connect Bluetooth on a Moto Z Play Android 7.1.1 patchlevel 2/2018 (current in reteu, was same result with Android 6.0.1 12/2016) with a Volvo XC40 car.
The first pairing with Bluetooth succeeds for a second. Then, nearly immediately, both displays (car and mobile) show reconnecting for about 10 seconds. It has a connect for a fraction of a second, and then is reconnecting and so on.
Trying flight mode and then only Bluetooth enabled on the mobile did not help. IIRC it showed some message about "My Volvo Carnull not bonded" (the name of the car for Bluetooth is "My Volvo Car" and some message with typo, something like "conecnting not successful". After that I rebooted, result was the state before with reconnecting.
Did try this several times. Also did try to reduce the amount of Bluetooth access types the car tries. There are 4 connected: phone, audio, internet, contacts. Did also not help.
Has anyone an idea how to get a successful connection or what the cause of the problem is? Did search for similar problems with Bluetooth in cars, but could not find anything (except for that hint with flight mode which did not help).
What I tried by now:
- Flight mode, only Bluetooth (as already mentioned). No change
- Remove all bluetooth connections. Pair new. No change
- Delete data for sytem app "Bluetooth Freigabe". No change
All other bluetooth connections are working fine. Another Moto Z Play using Android 7.0 (01/2017) is working flawlessly with that car. Strange for me is that it didn't work on 6.0.1 in the same way it does now fail on 7.1.1, but the other Moto Z Play using 7.0 is connecting stable.
Still the question: Does anyone have an idea how to get the connection working?
Factory reset?
I see that you deleted all bt connection but do you have some apps that are using bt? Like for smartwatch, headphones...?
I have Amazfit and watch must be connected to be able to pair a new device. Drow me crazy first time when I had that problem. I thought that car audio is broken, then phone... After pairing, watch doesn't have to be connected to reconnect.
Sent from my KFSUWI using Tapatalk
Zeljko1234 said:
Factory reset?
Click to expand...
Click to collapse
I was afraid this reply could come. When doing a factory reset, I do following: Pack /data/media somewhere because Nandroid omits this. Backup all partitions using twrp. Backup all apk using adb. Export SMS. Export contacts. Screenshots of the launcher screens. All this takes about 2-3 hours. Then I struggle a week until my device behaves like before. I'd be willing to do it if I saw a reason why it could help.
Zeljko1234 said:
I see that you deleted all bt connection but do you have some apps that are using bt? Like for smartwatch, headphones...?
Click to expand...
Click to collapse
Headphone, yes, there is August EP650 configuration tool that is not necessary. Thank you for the hint, will try it. Also I read somewhere it may help to delete cache partition, that's also worth a try before doing factory reset. Maybe I'll wait for Oreo before trying factory reset, could be they fixed some bug there.
Edit: BatOn which shows Bluetooth battery for external devices could also be the culprit.
Zeljko1234 said:
I have Amazfit and watch must be connected to be able to pair a new device. Drow me crazy first time when I had that problem. I thought that car audio is broken, then phone... After pairing, watch doesn't have to be connected to reconnect.
Click to expand...
Click to collapse
That's a strange behavior indeed. Amazfit seems to do something wrong.
It doesn't get any better if you upgrade to Oreo, I've been having problems with my Moto Z play disconnecting and reconnecting to the radio in my Corolla constantly ever since I went up to nougat. To be honest I just bought a good pair of headphones and stopped using the radio. Good luck though, if someone finds something that helps let me know.
I'm using bt with car audio, headphones, smartwatch... No problems at all, except one with Amazfit. And that is related to their bt implementation, not Moto fault.
Sent from my KFSUWI using Tapatalk
Seems the last action to remove Bluetooth related apps was the right one . There were two apps installed:
1. BatOn showing the state of battery of connected Bluetooth device
2. August configuration app for August EP650 headset
Removed both as they are usually not needed and it seems to work now. Will see later if it only worked for the short test I did today (currently I try to avoid driving because of an injury) or if it keeps stable.
Good, you didn't have to factory reset after all
Sent from my XT1635-02 using Tapatalk
Hello, I have some problems with the bluetooth connection to my Seat Leon (2016). Pairing worked fine but once I return to my car only the A2DP profile gets connected. In the car menu media control is working correctly but the phone part is shown as disconnected. The bluetooth connection state in the phone settings shows "connected (no phone)" then.
To fix this I have to manually disconnect and reconnect bluetooth on the phone - afterwards everything is working as expected. This is very annoying though and I had no such issues with my previous Nexus 6P (stock 8.1).
Any suggestions? If there is no solution I try to fix this with tasker, however I'd clearly prefer a "native" solution.
Thanks in advance.
Seems like it's working with the app Bluetooth Auto Connect, will test it more intensively in the next days. But I'm still wondering why it's not working out of the box...
I've noticed here lately that my Bluetooth devices don't automatically reconnect after I've turned them off and then try to use them again. I have to run pairing again. Stock November, custom kernel... But this happens to me on pure stock too..
I have the same issue. Can't remember paired car audio device. I have to manually connect everytime...it is pretty annoying. Let's hope december update will fix this.
This article describes a similar problem: https://thedroidguy.com/2018/08/how...eeps-disconnecting-from-car-head-unit-1087866
Sent from my Pixel 2 XL using XDA Labs
capt_f0r3st said:
I have the same issue. Can't remember paired car audio device. I have to manually connect everytime...it is pretty annoying. Let's hope december update will fix this.
Click to expand...
Click to collapse
No problem whatsoever on stock November with stock Kernel (2017 Audi A4 MMI plus).
But I did have issues in the past, Bluetooth is a mess. Usually a new patch fixes or breaks things ?
I have 2007 mazdaspeed 3. But the radio unit is not original, as the original one doesn't have bt. On my previous galaxy s8 everything worked well. So I suppose radio is alright. Once the pixel is connected, there aren't any issues ( maybe some little skips here and there) but no complete disconnects or something.