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!!
Related
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?
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.
Hello all,
I'm fairly new to this phone but I have been loving it so far. I've had a few issues with it, which most have been resolved (such as the phone defaulting to loudspeaker on phone calls).
Now my biggest issue is the USB connection. I first noticed it when I used to llug the adapter in for my headphones. The port worked great for a time and then I believe it was a security update that was released which seemed to jack it all up. Now I cannot use the port in the bottom of the phone for anything other than charging. Cannot use the headphones, cannot plug in my drone mavic pro (requires the phone app for on-screen first person flight), and I cannot plug the phone into the computer for data transfer.
I have pulled out the book of from my IT troubleshooting days and tried these solutions with no luck.
•various USB cables
•went into settings while phone was physically connected to the computer under connected devices, the USB section was greyed out stating not connected.
•checked in developer options us debugging on and off. I tried both ways for good measure.
•checked USB configuration type. I tried MTP, PTP, and RNDIS.
Any ideas?
greasydego said:
Any ideas?
Click to expand...
Click to collapse
I recently had similar USB symptoms on my Pixel 2 XL after the March security update. Also tried it in safe mode and tried factory data reset, but neither helped. I asked Google to replace the phone. Replacement works great, even after March security update.
Umm..I just recently had this issue. TBH I used a 3rd party cable but until last week it could 1. fast charge and 2. transfer data (included adb/fastboot), now however it does only charge, no whatsoever signs of connected device. Bought a new one, it does charge, sync(fastboot, adb,..), no fastcharge but ok.
Have you tried reflashing the March ROM (with the -w removed)? I'm running the March update (did the February too back in February) and I can still enable MTP (I just don't like that it doesn't stick in Oreo - coming from KitKat, that was - and still is - annoying.)
So I tried flashing the March update again and still had no luck. March update was a security update so whatever they did it must be in the coding. I got a warranty replacement for the phone and it works fine. I'm able to do data transfer and fast charging. I was very reluctant to install the March update again but after ignoring the notification for about a week, I installed it and it is working fine.
I talked to Googe about the issue and they said that the bug was fixed but for those phones that had the firmware installed, it has the issue permanently installed. The only option would be to replace the device.
Hi,
Did somebody try to use an android auto function? My car (Peugeot 308SW 2018) and the phone not connecting with latest (8.1.0) android version. I tried to enable an USB debugging (as workaround recommendation), but nothing changed...
Have you other idea or working solution?
thx!
rawen69 said:
Hi,
Did somebody try to use an android auto function? My car (Peugeot 308SW 2018) and the phone not connecting with latest (8.1.0) android version. I tried to enable an USB debugging (as workaround recommendation), but nothing changed...
Have you other idea or working solution?
thx!
Click to expand...
Click to collapse
Yes, it works perfectly in my mid 2017 Kia Cee'd SW. Check if you have android auto enabled(i have the option to disable it and the apple car play). Also, the usb cable is working properly when connecting to a pc?
At the car side is enabled, at phone side i didnt found any additional options...
The best result was the android auto icon at phone appears and disappears continously with 2-3 different cables.
Is it possible the car head unit firmware not compatible with N7P latest SW version?
rawen69 said:
At the car side is enabled, at phone side i didnt found any additional options...
The best result was the android auto icon at phone appears and disappears continously with 2-3 different cables.
Is it possible the car head unit firmware not compatible with N7P latest SW version?
Click to expand...
Click to collapse
Doubt it. The car is from this year, it seems unlikely(to me) that the firmware wasn't up to date.
Stupid question, you have the android auto app installed on the phone right? Android has a Car Mode but to use android auto you need to install the app 1st(https://play.google.com/store/apps/details?id=com.google.android.projection.gearhead&hl=en). If the link says that you have no compatible device, download the latest version from here(https://www.apkmirror.com/apk/google-inc/android-auto/)
For almost a year I thought my head-unit wasn't up to date as the android auto would freeze, the app would say that the head-unit wasn't up to date, waze would display random artefacts, etc.
Now with the N7p it is butter smooth, no funky stuff and way more responsive that when I was trying to use it with my Redmi 4 Prime(same cable but with a micro-b to usb c adapter)...
No issues with AA in Seat Ateca 2018.
Everything works like a charm.
For phonecalls, you need to select default sim first, otherwise the call hangs on a sim selection prompt on the phone.
I write to nokia support and they send:
- clear the bluetooth cache
- do a soft reset
after this steps working fine...
what is Bluetooth cache?
Tequila.CZ said:
what is Bluetooth cache?
Click to expand...
Click to collapse
You found here, how to clear: http://support.hereplus.me/hc/en-us/articles/115003497328-Clearing-your-Bluetooth-Cache-Android-/
Do you install android auto app on your smartphone ? some lands doesn't have android auto on the play store, so you need to download manually on apk mirror web site (arm64 version)
A good quality cable is also needed.
I'm having similar issues.
This phone won't work in both my VW cars.
If I clear all settings it works fine.
I get to my destination, unplug and then when I head out on my next trip it doesn't. Just a blank screen on the head unit and the phone has the green screen saying launch Android Auto on the head unit.
Tried the BT cache clearing as above. Will try a factory reset of the phone shortly too otherwise wait for pie and if still no go then sell the phone which I will miss
Though can't work without Android Auto now
It is definitely problem with Nokia 7 plus. In my car it connect and after few minutes black screen and solution is only disconnect and connect again.
matonka007 said:
It is definitely problem with Nokia 7 plus. In my car it connect and after few minutes black screen and solution is only disconnect and connect again.
Click to expand...
Click to collapse
I've found the bluetooth with my N7P poor anyway. This is my second one and the same as the first.
All HMD will do is send you a list of the bluetooth protocols they support.
So you may need to change your car ?
My 7+ works perfectly now.
Enable USB debugging and disable the extreme power saving settings.
Hi all,
Since 3 weeks I've been having problems with Android auto on my OnePlus 6
One day it was working fine and I was using it daily in my car. Then on the 24th of June, my car just stopped detecting my phone. My car (citroen cactus 2018) shows the option to select android auto, but when I select it, it just straight up tells me my device is not compatible after my phone screen flashes once.
I already checked online for all different solutions. I replaced my USB cables 4 times, checked with both usb debugging on and of, changed usb preference to file, midi, ptp. I reinstalled my phone, flashed different roms, but it just doesn't work.
Currently I am using:
OnePlus 6 Oxygen OS 10.3.4
Android auto 5.4.5
Anyone who can help me with this?