Database Develop

Android Auto connectivity issue

I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?

AA is buggy but I'd have to say......
rafalucas said:
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
Click to expand...
Click to collapse
I think this is your radio hardware and not the AA app. But you never really disclosed what phone you are using and if it has been modified or what so there is no clear help answer that I can assist you with.

hi, i've got the Note 3 (SM-N9005) running stock lollipop 5.0 (baseband N9005XXUGBOI2). my phone was previously running 4.4.2 kitkat with root.
the connection is very hit and miss. it will keep trying to read my phone when plugged to the car and the phone will keep shifting between "connected as a media device" or "connected as a USB accessory". When its connected as usb accessory, the phone screen will black out for a second and then goes back into the previous screen which is usually home page of the launcher. i think the "blackout" might be the phone trying to boot or load android auto app but gets disconnected as it tries to get in.
i have to plug the usb in and out a few times and sometimes by lottery, it will establish a successful connection and AA loads on the car screen. i've found that if i open the app first on the phone and then plug in the usb, it will have higher chance of getting a successful handshake.
hope this makes sense.

I have the exact same issue: VW App-Connect in a new 2016 vehicle with a Galaxy S5 running Lollipop. Very annoying because once the two are connected it does work reasonably well.
rafalucas said:
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
Click to expand...
Click to collapse

I believe Verizon phones were having USB connection issues because of some special app they had that did stuff over USB, and an update fixed it.
Some USB connection issues can be solved by changing the mode of USB: MTP, Charge Only, etc.
Some issues can be worked around by enabling (or disabling) USB debugging. This is under Developer settings after Dev mode is entered by tapping Build number 7 times.

Hi Mike, I've got an Australian stock unbranded note 3.
i've spoken to the vw dealer and apparently vw is working diligently for a software upgrade to the car's infotainment system which may or may not fix the connectivity issue.
it's just frustrating that in order to get a consistent connection, i have to go into the app and "forget" the car, then it will go through the new connection prompts.
i'm hoping the next app update might fix the issue but at the moment its unclear whether its the app, or my phone or the car's problem.

I have similar issues with my 2016 Skoda Fabia Combi. I'm guessing the infotainment system in the Skoda is pretty much the same as in the Volkswagen. Many parts are because Skoda is owned by VW. After tons of trial and error, I've had some success connecting my LG G3 but first let me tell you how I ended up in the current situation.
I have tried to connect thee different android devices (LG G3, HTC One M7 and Nexus 7 tablet all running Lollipop) with bunch of different USB cables. The result is always the same. On the phone I see black screen flashing before it returns to home screen and nothing else happens. From the recent apps view I can see that the black screen was AA trying to launch. CarPlay with iPhone works fine.
I live in Finland so I have sideloaded the AA app and at first I thought that the issue is caused by AA not being officially available here yet. After searching this forum and other android forums I found out that other people are having the same issues in countries where AA is supported so maybe this is not the case. Obviously it's not also a device problem because I get exactly same results with different devices from different manufacturers. Only common nominator seems to be the VW/Skoda infotainment system? Correct me if I'm wrong here..
In the Skoda smartlink menu you can choose your preferred connection protocol from Android Auto and Mirrorlink. This affects the order the car attempts to establish the connection. I read from a Skoda forum that someone had a successful connection after he had changed these options around so I tried it. I checked Mirrorlink as a preferred method and tried the connection: no luck. I changed back to AA as preferred method and to my amazement after this the AA launched on the phone and I had a successful connection! If the VW has similar option I suggest you VW guys also try this.
My current situation is that most of the time the phone does not connect at first try but after changing the preferred method around it does. I have also other issues with AA. After connecting I cannot adjust the volume first from steering wheel/stereo volume knob. Spotify audio goes to a wrong channel at first (I can hear it only when i activate voice command) After changing music app to Google Play Music and then back to Spotify it starts working normally and I can also adjust volume. And of course the restriction on browsing your Spotify library. It is the most stupid thing I've ever seen at that level of software development.

rafalucas said:
Hi Mike, I've got an Australian stock unbranded note 3.
i've spoken to the vw dealer and apparently vw is working diligently for a software upgrade to the car's infotainment system which may or may not fix the connectivity issue.
it's just frustrating that in order to get a consistent connection, i have to go into the app and "forget" the car, then it will go through the new connection prompts.
i'm hoping the next app update might fix the issue but at the moment its unclear whether its the app, or my phone or the car's problem.
Click to expand...
Click to collapse
Auto dealers tend to know almost nothing about software and smartphones. They know how to sell cars, and the mechanics tend to know how to fix them mechanically, more or less.
And they can almost always say that there is likely an update due at some point.
If you, or anyone having a problem on the car/HU side, has a USB OTG cable and a bit of time to test, you should consider trying my Headunit app; see my sig.
If you get it working you can get a better idea if your car HU is at fault.
I wonder if there are car stereo shops where you can plug your phone into a Pioneer AA unit, like 4100NEX, and see if it works OK on that.

I've had my 2015 Seat Leon (also VW group) for four months now and also having trouble with Android Auto through the SEAT 'Full Link' connection. It seems to be russian roulette whether it'll make a connection and start AA when you plug it in. Sometimes you'll get a 'Connection failed' message, other times you will see the system try AA, fail, then try MirrorLink then fail on that too (as my Nexus 5 doesn't support MirrorLink). As others have said you see the phone screen go black then crash out and goes back to the home screen.
The only solution I have is to restart my phone and try again. Its almost my routine now to restart my phone just before I know I'm about to go for a drive. It beats having to sit in the car watching my phone reboot before I set off!
I didn't know you can change the USB settings on the phone, so I'm going to go through the various settings in developer options to see if any of these help. I'm thinking 'Charge only' might be useful, unless AA needs MTP or network connection to operate?

seems like i'm not the only one! sounds to me its more and more likely to do with the vw made headunit (could be the firmware). I just tried a mate's phone with the AA app but it also went in a connection loop before finally establishing a handshake with the phone. hopefully next firmware update to the car's headunit may be able to fix but but i won't bet on that happening anytime soon.
guess everyone has to trial and error and find ways to establish a successful consistent connection. for me is to forget the car and establish a new connection to the car.
still frustrating as ever and i don't want to have to spend 2 - 3 mins each time before i drive to wait for AA to load.
anyone else having connection issues with other car makes?

rafalucas said:
anyone else having connection issues with other car makes?
Click to expand...
Click to collapse
With my Pioneer or my Headunit app, one of the biggest issues is quality of the USB cable and USB connections.
Testing with different/known high quality cables is worthwhile.

nimdy said:
'Charge only' might be useful, unless AA needs MTP or network connection to operate?
Click to expand...
Click to collapse
"Charge Only" is what I try to aim for. Despite it's name apps like Android Auto can use the USB in this state.
AA does not need or use MTP or network connections via USB. Trying to use USB for other things, like network connection, would only be possible via a USB hub, but it's a crap-shoot whether that would even work.

mikereidis said:
With my Pioneer or my Headunit app, one of the biggest issues is quality of the USB cable and USB connections.
Testing with different/known high quality cables is worthwhile.
Click to expand...
Click to collapse
i've tried various cables but i find the original samsung cable that came with the phone the most "consistent" in establishing a successful connection.

mikereidis said:
"Charge Only" is what I try to aim for. Despite it's name apps like Android Auto can use the USB in this state.
AA does not need or use MTP or network connections via USB. Trying to use USB for other things, like network connection, would only be possible via a USB hub, but it's a crap-shoot whether that would even work.
Click to expand...
Click to collapse
i'll give this a go tonight

PHEW. I thought maybe it was just me. I have just purchased a Skoda Fabia 2016 with Android Auto (I imagine this will be the same underlying system for VW/Skoda/Seat/Audi). I find that sometimes, I plug it in and then it magically works fine. Other times it can't connect to the device and tries to connect to MirrorLink instead....which also fails. I'm using a Samsung Note 3 official UK lollipop build - but rooted. When it fails, I have to go through the process of telling it that I want to connect to the device.
Incidentally when it has connected, it's rock solid every time (well with one random crash & reboot of the car's entertainment system).
It's just annoying. I want to get in my car, plug it in, AA to launch and that's it!
What's also slightly annoying is that there's no button to go right to AA on the dash. I have to go to 'Menu' and find Android Auto in that menu to launch back into it if I go to something else within the car's entertainment system. Grr! Not anything anyone can do on here, but just venting!

jonboyuk said:
PHEW. I thought maybe it was just me. I have just purchased a Skoda Fabia 2016 with Android Auto (I imagine this will be the same underlying system for VW/Skoda/Seat/Audi). I find that sometimes, I plug it in and then it magically works fine. Other times it can't connect to the device and tries to connect to MirrorLink instead....which also fails. I'm using a Samsung Note 3 official UK lollipop build - but rooted. When it fails, I have to go through the process of telling it that I want to connect to the device.
Incidentally when it has connected, it's rock solid every time (well with one random crash & reboot of the car's entertainment system).
It's just annoying. I want to get in my car, plug it in, AA to launch and that's it!
What's also slightly annoying is that there's no button to go right to AA on the dash. I have to go to 'Menu' and find Android Auto in that menu to launch back into it if I go to something else within the car's entertainment system. Grr! Not anything anyone can do on here, but just venting!
Click to expand...
Click to collapse
Galaxy s6 Stock firmware and my octavia android auto 1.4 work very well.

No luck with LG G3
Good day everyone, I just purchased a 2016 VW GTI and I have an LG G3 with Lollipop 5.01 rooted. and I can not get it to work with mirrorlink or android auto. Mirror link default or AA default. I tried different cables, plugged in car on before the car was on. MTP, PPP, charge. The head unit does see it as an LG phone but nothing works.. usb debugging on or off.. Kind of bums me out. Oh I keep getting a make sure the phone is unlocked message I turned screen lock off, and the phone is awake when I try to connect.

mikereidis said:
If you, or anyone having a problem on the car/HU side, has a USB OTG cable and a bit of time to test, you should consider trying my Headunit app; see my sig.
Click to expand...
Click to collapse
Yes! This is the best option for check if the problem is the HU/car or the phone.
From my point of view typically the most issues are related to the phone (ROM, AA app, etc.). For example, with my previous Lollipop 5.0 one month ago... the AA was inestable. With a new 5.1 phone and with the last AA app version (upgraded 1 week ago) I don't have any problem.
Please, try this before post about problems. Sometimes the problems isn't the car or the Head Unit. :angel:

Hi all. Further to my last post, I'm also sure it is a device/ROM issue. It doesn't work all the time, but most of the time the workaround for me is to open the open apps list, swipe them all off to close them, including AA app, then re-open AA. This increases the chances of my phone connecting to the car, but every so often I get a connection error and have to try again a second/third time.
I think I may have asked before, but is there anywhere we can report these bugs to? AA is technically beta (as with most Google products) so I'm sure they would welcome our bug reports.

Connection Memory ?
Hi,
I have the same experience as many others that the connection to AA is very random. I've tried:
Different phones (Nexus 5 and Nexus 6 on stock Android 6.0)
Different USB cables
AA app on and off
Screen locked and unlocked
All without being able to see a pattern. Sometimes it connects automatically in 15 seconds, sometimes automatically in 1 minute and sometimes I need to manually push the connect on the HUD (VW Passat 2106).
The only thing that is consistent is that once you are connected to AA and then disconnect, if you re-connect the phone it works flawless every time ! It seems to be working even if the re-connect happens after a few minute (e.g. not rigth away). So it seems that either the HUD or the phone has some sort of connection memory. Once it expires the connection problem reappears.
Anyone else that can confirm this ? Any ideas on where the problem can be ? I guess this rules out the USB cabel as suggested by many.
// J

Car connection

Just received this, coming from an S8+. Problem being when trying to connect to my car via USB, I've used the original cord and it recognises initially but then stops charging. Other phone is fine and I need to use android auto, don't want to take it back but it's a key feature I use. Anyone else experience this?

You are talking about Android Auto? The Huawei phones have a long history of incompatibility with that. Looks like the P20 Pro made a big enough splash to attract attention from Google though, as they are apparently looking in to making it compatible.
http://www.trustedreviews.com/news/android-auto-wireless-3452655

Highspeed123 said:
You are talking about Android Auto? The Huawei phones have a long history of incompatibility with that. Looks like the P20 Pro made a big enough splash to attract attention from Google though, as they are apparently looking in to making it compatible.
http://www.trustedreviews.com/news/android-auto-wireless-3452655
Click to expand...
Click to collapse
Not sure if it's even just an Android Auto issue as when connecting via USB it doesn't stay connected, it's weird.

Same problem for me...
Sometimes AA stop working and the P20 pro stop charging.

P30Pro and Android Auto

Hello,
i have a P30 Pro with the Firmware VOG-L29 9.1.0.178(C431E4R2P2) and a problem with Android Auto.
If i connect the P30Pro with my car, there is a connection error.
The USB Settings on the phone switch automaticly to only charging. If i switch to data transfer it changes automaticly to only charging.
On the last Firmware i have no problems with the connections to Android Auto.
Have anybody the same probleme or an idea?
Thank you
Lapidu

Sometimes, I have to select the data transfer setting two or three times before it will connect to the car. But it always works after 2 or 3 times. USB debugging might also make it work better.

I have no problems and never had. Also i never changed the connection mode, nor did i enable usb debugging. I'm using the original cable, though. Some cars/phones seem to have problems with cheap usb cables, my dad also noticed that but is fine after using the original one.
Was it working once? Did you registered the car in Android Auto or has is failed ever since? Is there a message on the phone?

Witch firmware do you have? And what for a model?

Worked on every firmware since beginning (185 atm). 128 GB Version

I have similar issue, the connection "dies" everytime I connect it to the car for the first time after being parked. Takes about 1-2 minutes, then it disconnects. I haven't investigated what the phone does, but my quickfix is usually to plug the cable in/out. After that, the connection is stable. The issue started around .162 or .165

Hi all. I have this problem as well. Just bought a carplay, but my P30 Pro (Android 10) wouldn't connect at all. I tried with different cables, including original one, still no luck. WIth any other cable it works fine from a Samsung Note 10+. Any idea?

I have the same issue with my P30 pro and civicX
After emui 10 I just can't use android auto in the car.
I have the app on my phone, and it works on the phone. But when I connect to the car it wont work.
(all the Samsungs and apple that I have home work perfectly)

I'm using emui 10 and android auto.
I have the same problem as all people here.
After usb plug, only charge (that's not important) . Some times connects at first time and some other i have to select other usb connection mode (i discovered unplug cable is not necessary)
Will try to change usb cable with the original one

Hello there! I'm trying to connect my P30 Pro with Android Auto on a Seat Leon. I always receive an error message and the connection with android auto always fails. I tried to enable Usb Debug, to install old versions of AA on my phone (for example v. 5.3 and v. 5.4). I'm using the originale data cable (actually two of them since I have two P30 pro at home). AA worked well with my old Samsung Note 8 and Mate 10 Pro. Do you have any suggestion? Thank you!

you guys need better cables, use the factory Huawei one and you'll have no issues.

I'm using two original cables (I have two P30 Pro at home). It isn't a cable problem but probably an issue with Android 10 and Android Auto. This problem affects different recent models of Huawei (P30 pro, mate 20 pro..).

Hello there! Just an update, AA doesn't work only with the Seat Leon. I tried other cars and everything is ok. I will try to update Full Link Seat.. It should solve the issue. Byee
Inviato dal mio VOG-L29 utilizzando Tapatalk

I had android 10 and 10.1 stock cable a no issues whatsoever. I just traded phones with my little bro for a s10e ??

Hello! My p30 pro can connect with Hyundai kona (2021) via usb cable. But in wireless mode, the coonection has issue: the wificonnection is over the 4g+ connection, so, I don't have mobile data on the kona's device. What can I do?

Huawei P30 Pro no longer USB Synching

I had my phone, a "Huawei P30 Pro" for about 9 months then at the beginning of the first lockdown (March 2020) I was called to Italy.
After a few days there I started to notice that I was having problems connecting my phone with my PC's & Mac's using Hisuite?
I tried revoking HDB Debugging mode, then re-enabling it, I went through all the recommendations that I found online but nothing worked.
I also uninstalled and reinstalled Hisuite, I reset all settings, I then wiped my phone completely and tried to reinstall it as a new phone hoping that would work,,,,it didn't.
Around about that time I bought a drone to do some ariel photography, I could never get the P30 Pro to recognize the drone it just kept saying that couldn't find/connect to the device, so I tried my partners P20 Pro which connected via the same USB cables I had been trying previously and they worked fine it also worked flawlessly with the drone?
I even went out of my way and bought a 'Huawei P smart Z' to test with and sure enough, it connected and worked perfectly with the drone and USB connection?
Now, even though I had called Huawei support on a few occasions within the warranty period they are now saying that it's out of time and there is nothing they can do.
I called them when I was in Italy during the lockdown where I was there for 9 months looking after my parents.
My thoughts are that it must be the synch port and perhaps tied into something on the logic board as it is not just USB synching but also when connecting 'Bluetooth?' to the drone which is strange as it connects to other Bluetooth devices, my watch, printer, TV, BPM, etc..
I love this phone especially the camera/video side to it but now I can no longer get my work off unless I send it to myself which is really cumbersome when you have 2-3 hours worth of 4K video recordings, which I do often.
The other thing is I really want to use this with my drone but how the heck can I get it to see the device and again I have tried just about everything and used other phones from other manufactures as well as Huawei and all connect/work fine with the drone and USB syncing.
I myself am a bit of a technical sleuth but this one has me hammered.
Is there anyone out there who can perhaps shed some light?
(I am looking for 3 questions answering here.)
1.what is the probable fault?
2.what is the repair solution?
3. how much could it cost?
Thank you
I will also try posting this request out on a few other boards and see what comes back.

i have the same problem

Android Auto in Norway

I have big time trouble connecting my A12 Android Auto to my brand new BMW iX3. My Oneplus Nord connects flawlessly, the A12 does not. On Samsungs website I read that Norway is not among the countries allowing Android Auto (https://www.samsung.com/ie/support/...fficulty-connecting-to-or-using-android-auto/), could that the reason?

I cannot believe that.
I live in the Netherlands and we are also not in the list and we can use AA without any problem, but, your phone AND carsystem will have to connect with each other.
It sounds more that your A12 does not have the right software for it.
Go to apkmirror site and download the AA software and install on your phone.

I have downloaded the latest version from Google Play, isn't that version as good as the apkmirror-versions? My A12 connects OK with the car when it comes to hand free phone operations over Bluetooth, but when trying to establish AA, the car says "The connection failed. Check both the Bluetooth and WLAN settings on the mobile unit". Both BT and WLAN are active on the phone, and during the process an AA logo splashes on the mobile screen.
Edit: I have downloaded and installed Android Auto 6.8.613323 which I suppose is the lastest release. Same result

Ah, now i get it.
I had a Nokia 7plus and my radio-unit worked, This summer i switched to a new Nokia X20 phone, and had the same error.
After switching the car-cable with the cable that came with the new Nokia, it suddenly worked.
So try to use the cable that came with the new phone, instead of the old cable from the previous phone.

Thanx for the tip, elot01! I switched the cable to the one that came along the A12, but nothing happens when connected to the car USB except from battery charging and the option to transfer files. I am in contact with Samsung support, and so far they have been helpful. But they have not been able to solve my problem yet.
Once they have, I will post the solution here. But any tip for the forum community is highly welcome.

Samsung has given up and redirected med to Google since "this is a 3rd party SW". I haven't managed to find any Google support center to contact, but I have figured out the problem myself.
I want to have a wireless AA, and it seems like this is only supprted with handsets capable of dual band wifi, ie. 2.4 and 5GHz. The Samsung Galaxy A12 only support single band (2.4GHz).
So there goes my A12 back in its box to be placed in some drawer and forgotten. A low-priced telephone, but still a waste of money
A tip to Google/Samsung: Why not display a message saying "Android Auto is only supported on dual band wifi mobiles" when only 2.4GHz is supported?

If you want wireless, also take a look at Carsifi (still in Kickstarter) or AAWireless (former kickstarter).
Then you don't need a new phone

elot01 said:
If you want wireless, also take a look at Carsifi (still in Kickstarter) or AAWireless (former kickstarter).
Then you don't need a new phone
Click to expand...
Click to collapse
If you want a dongle slamming aroud in you car occupying one USB-port this solution is probably OK. But it's much easier to spend the 85$ extra on a mobile with dual-band wifi.