Database Info

MM and Android Auto

I flashed the MM upgrade on my US 5.5 and then did a factory reset, but now my Android Auto will not connect to my phone. I've tried swiping down and choosing MTP, but still does not connect. The phone is connecting to Bluetooth. After researching it seems to be a problem with Marshmallow and Android Auto. Does anyone know a fix?

Uninstall drivers and reinstall
Sent from my 6039S using XDA-Developers mobile app

There aren't any drivers. This is for Android Auto when I plug in to my Kia Sportage. Android Auto did work before the MM update, and it still works on other phones running 5.1.

Cant you just remove the device from android auto and then reconnect it?
Sent from my 6039S using XDA-Developers mobile app

I did remove the device, but Android Auto will not find the phone with the MM update. Seems to be a know issue with Samsung and LG devices.

I finally got Android Auto working by using the Developer options, Select USB configuration, RNDIS (USB Ethernet)

paulsaz said:
I finally got Android Auto working by using the Developer options, Select USB configuration, RNDIS (USB Ethernet)
Click to expand...
Click to collapse
I have the same problem and i tried to put RNDIS but my cell doesnt get the configuration. Did you do something to put it on RNDIS?

I got a new car (Hyundai Kona) with android auto but my Idol 3 5.5 (6045I) will not connect to the car screen. I have MM on it (but not the 2 latest garbage updates). I have tried USB debugging, multiple(10) USB cords. I cannot get RNDIS to work on the USB -it reverts to charging. So my USB is set to MTP. My phone plays AA on it's own screen just fine but will not send it to the car screen. Bluetooth works fine.
The auto dealer rep tried his iphone (apple carplay) and another android phone and they connected just fine so it is not the car.
Any suggestions?

USB does not recognize my phones

I have a MTCD head unit MX (witson) with Android 5.1, my problem is that the USB port cannot recognize my phones, A note 4 with Android 6.0 (eRobot ROM) and a Samsung GT386T no rooted with stock ROM 4.4.2. The USB port works find with a usb stick, I can play music, pictures, etc. but not my phones. Both have the USB debugging enable.
When I plug a phone it is charging but nothing happens, my note 4 after a few minutes pop a windows saying that there is a problem with the connection MTP and that I need to download samsung Sync etc.
What I want to do is to use the mirror link function.
Any of you know something about this issue?
Thanks in advance for your help.

paniqueado said:
I have a MTCD head unit MX (witson) with Android 5.1, my problem is that the USB port cannot recognize my phones, A note 4 with Android 6.0 (eRobot ROM) and a Samsung GT386T no rooted with stock ROM 4.4.2. The USB port works find with a usb stick, I can play music, pictures, etc. but not my phones. Both have the USB debugging enable.
When I plug a phone it is charging but nothing happens, my note 4 after a few minutes pop a windows saying that there is a problem with the connection MTP and that I need to download samsung Sync etc.
What I want to do is to use the mirror link function.
Any of you know something about this issue?
Thanks in advance for your help.
Click to expand...
Click to collapse
I believe i read that there is a specific app that you have to run on these to do the mirror link...easy connect, maybe? Did your HU come with an instruction booklet? I was looking through mine earlier and it went over in detail how to setup mirroring through that app.

Yes, when I tried to use EasyConnected is when I saw the problem. The app waits for my phone to be connected, It says that it must be turned on USB debugging, but it is on. Then I checked in the File manager and the USB was not enable there, like if nothing is plug it. If I plug a USB memory it works fine.
I will try today to do a factory reset.
Thank you!

paniqueado said:
Yes, when I tried to use EasyConnected is when I saw the problem. The app waits for my phone to be connected, It says that it must be turned on USB debugging, but it is on. Then I checked in the File manager and the USB was not enable there, like if nothing is plug it. If I plug a USB memory it works fine.
I will try today to do a factory reset.
Thank you!
Click to expand...
Click to collapse
You ever get this solved? My easyconnected never stays connected. WiFi and USB both are garbage.
WiFi randomly disconnects.
USB also disconnects asks me to allow USB debugging every couple of minutes. The phone never remembers the headunit, so it constantly asks me again to allow connection. Must be a crap RSA fingerprint coming from the headunit.

JordanB said:
You ever get this solved? My easyconnected never stays connected. WiFi and USB both are garbage.
WiFi randomly disconnects.
USB also disconnects asks me to allow USB debugging every couple of minutes. The phone never remembers the headunit, so it constantly asks me again to allow connection. Must be a crap RSA fingerprint coming from the headunit.
Click to expand...
Click to collapse
Nope, Still does not work for me. Same symptoms as you. I already tried with 3 differents phones, factory reset and different versions of easyconnected.

I seem to have USB connection working now with only one "allow USB Debugging?" popup, only when I first connect.
What I did was turn wifi off on the headunit. I am not sure why it worked, but I just wanted to turn everything not needed off, and see if the headunit would stop disconnecting all the time. So far so good. I can probably live with one annoying popup, instead of one every few minutes.
Of course you have to keep the screen on the phone on, and the battery in the phone will deplete faster than the headunit charges it, but still an improvement. I had a 30 minute drive today, and the USB never disconnected!

paniqueado said:
Nope, Still does not work for me. Same symptoms as you. I already tried with 3 differents phones, factory reset and different versions of easyconnected.
Click to expand...
Click to collapse
paniqueado, try the da_anton ROM. I just installed it and easyconnect finally works as it should. I just plug in my phone to the USB and it fires right up! One prompt if any on the head unit, and NO disconnects whatsoever.

Bluetooth issue in Android 10

In Android 9 my Bluetooth used to connect automatically. After updating Android 10 i have to connect manually Everytime. Any solution for it ??

Strange, on android 10 my devices connect automatically if I turn bluetooth off without manually disconnecting the device first. It remembers what was last connected and attempts to reconnect to the device when I turn Bluetooth back on. Try un-pairing the device, then re-pairing. when you wish to disconnect from the device try turning Bluetooth off on the phone. Then turn Bluetooth on again and see if the phone tries to auto-connect.

iwantademo123 said:
Strange, on android 10 my devices connect automatically if I turn bluetooth off without manually disconnecting the device first. It remembers what was last connected and attempts to reconnect to the device when I turn Bluetooth back on. Try un-pairing the device, then re-pairing. when you wish to disconnect from the device try turning Bluetooth off on the phone. Then turn Bluetooth on again and see if the phone tries to auto-pair.
Click to expand...
Click to collapse
I reset my Bluetooth 4 times, now it connects automatically. I don't know what was the problem.

Oneplus 6 not connecting to Android Auto. Oneplus 5 works fine.

I've just had my 2016 Mazda MX5 Miata's original equipment MZD Connect head unit upgraded to run Android Auto via a USB cable.
They tested it in the workshop with a couple of different phones and it all worked fine, but, alas - not with my Oneplus 6.
I'm running Android 10 and OxygenOS 10.3.0 and I can feel the phone vibrate in my hand as it repeatedly connects and immediately disconnects again. My wife's OnePlus 5 with Android 9 and OxygenOS 9.0.9 has no problems.
I've tried different cables, but it seems clear that it's a phone issue as all the other phones seem to connect with no problems.
Any suggestions would be very welcome.

jesus4c said:
I've just had my 2016 Mazda MX5 Miata's original equipment MZD Connect head unit upgraded to run Android Auto via a USB cable.
They tested it in the workshop with a couple of different phones and it all worked fine, but, alas - not with my Oneplus 6.
I'm running Android 10 and OxygenOS 10.3.0 and I can feel the phone vibrate in my hand as it repeatedly connects and immediately disconnects again. My wife's OnePlus 5 with Android 9 and OxygenOS 9.0.9 has no problems.
I've tried different cables, but it seems clear that it's a phone issue as all the other phones seem to connect with no problems.
Any suggestions would be very welcome.
Click to expand...
Click to collapse
Make sure it is not in charging mode from the menu when you plug it in. Also check the USB debugging. I connected easily to a 2019 Subaru.BTW, assuming Android auto app is on phone.

Right2Bear said:
Make sure it is not in charging mode from the menu when you plug it in. Also check the USB debugging. I connected easily to a 2019 Subaru.BTW, assuming Android auto app is on phone.
Click to expand...
Click to collapse
I've just set the default USB configuration to File Transfer. USB debugging is Off and Android Auto is built into Android 10, I believe (so you can't install the app anymore), but I have installed Android Auto for phone screens anyway - which is what you do if you still want to see the app on your phone. Does all that seem correct?

I had many issues with android auto and my O+6. I solved it with the solution given by "johr claessens" in this post : https://support.google.com/androidauto/thread/4455995?msgid=15130627
You can follow directly the step by step : https://actuallydavide.com/blog/2019/04/13/how-to-remove-work-profiles-on-oneplus-devices/

bilool said:
I had many issues with android auto and my O+6. I solved it with the solution given by "johr claessens" in this post : https://support.google.com/androidauto/thread/4455995?msgid=15130627
You can follow directly the step by step : https://actuallydavide.com/blog/2019/04/13/how-to-remove-work-profiles-on-oneplus-devices/
Click to expand...
Click to collapse
I'm actually doing a very tentative victory dance ATM. I think I've solved the problem.
I opened the Android Auto for phone screens app, went to settings and found there were no 'Accepted Cars' and the 'Add new cars to Android Auto' was switched off. I switched that on, it then connected and added the MX-5 as an Accepted Car. And seemingly all is working fine. I'll do more tests tomorrow.
The bit that is odd, though, is that the Android Auto app is no longer required with Android 10 - it's built in and does everything automatically. If I hadn't installed that extra 'Android Auto for phone screens' I wouldn't even have access to those settings.
Also - the solution may have had to do with the steps Right2Bear suggested. Something seems to have worked. But if it all goes wrong tomorrow, I'll certainly try your suggestion, bilool. Thanks!!

Question Android Auto stopped working after Android 13 OTA

Hi,
I just updated to the Android 13 OTA on the S22 Ultra (VZ, USA). All of a sudden my android auto stopped working. Wireless completely. Before AA wireless would connect to my car within a few seconds of my head unit booting up. Now it just waits at "Connecting". It knows my phone is available, but doesn't seem to want to connect.
If I plug in the phone, it works for all of ~20 seconds before disconnecting. If I just simply reconnect the cable it works again, 20-30-40 seconds before disconnecting.
Before the 13 OTA, it was working perfect, no disconnects on wired or wireless. So I 100% know it's not the cable or my headunit. Literally last night it was working, now it's not.
I checked sleeping apps on the phone and AA or Maps is set to never sleep/not optimized. Not sure what else might have changed.
I've uninstalled/reinstalled/cleared cache etc of AA on my phone. still nothing.
I fully reset my headunit to factory settings, I've done the network reset on my phone multiple times. I'd -really- like to avoid having to fully wipe my phone and try from there...
Has anyone run into this on their newly updated S22? Tips?Suggestions?
Thanks!

Me too. S22 ultra. Car is Mercedes A250 e. It's only a few days I have the car and I was able to connect only with usb cable in Android 12. I don't know if it is a limitation of the car not to be able to connect in wireless mode. Yesterday after OTA upgrade to android 13 I get the error unable to connect to android auto in the MBUX of the car.