2016 VW Golf Android Auto won't work with LG G4

[rdlkgliders]

Please keep me posted I have the same problem with a 2016 Jetta With LG G4
I can get the android auto to take on my infotainment center but without any long term success.
AA will connect and operate fine, I connect by trial and error none of the workarounds seem to have any consistent positive effect or solution.
I have tried the seat belt,, brake Etc Etc combo and have been no more successful than un pairing, bluetooth, repairing bluetooth, clearing AA cache and or Data, uninstalling AA, forgetting cars in AA, setting and every possible combo of above that I am aware of. I have had the car 2 weeks had it into tech twice and had the latest update installed but still no help. Many phones have issues it seems but the update I am told helped some but not our LG G4. A flagship phone and 2015 phone of the year finalist.
For me it is a deal killer I will get out of car unless some workable solution comes soon.....Very Soon.
The one thing I have had some success with and I have many hours invested is once you are blessed with connection to AA shut off car and THEN UNPLUG PHONE INTO USB and before you turn back on car PLUG PHONE INTO USB. this seem to sustain connection until I forget to do this. Also once you turn ignition off or before do not power off stereo. keep trying to connect it will happen you may need to reset or uninstall AA and also disconnect and reconnect usb but it will take eventually. I just did a factory reset and may disable lookout and try again. I will get back once that happens tomorrow. I am determined to find a temporary work around but Google VW or carrier need to start chiming in with acknowledgement of problem and info on a solution. AA is in Automotive brochures and on Automotive websites front and center as a key selling point and if it doesn't work and no one other than the consumer and tech's at the dealer are talking this will get, well lets hope someone with the ability to rectify this is listening.

 

[dgiaffe]

I saw this post in a VWVortex forum. Unfortunately, I can't post links yet due to me being new around here (Need 10 posts count)

Guys. I got android auto to work with my LG G4.
Here is how I did it.
First thing is I ordered this short cable. (Amazon Link to short sync and charge usb cable)
That got it so the phone would actually show the USB options once it was plugged in; my old cord did not.
From there, I chose the 'USB Charging Only' option and went through the manual connection to Android Auto.
From there, everything worked, miraculously!

I will try it tomorrow as it is quite late here, but thought I'd sharing my findings, if anyone has the chance to try it out before me!

 

[Katmeat]

Just for edification, I have exhausted efforts to connect my rooted Verizon LG G4 to AA on my 2016 Golf. I still have my old G2, and I recently loaded CM13 on it which is based on Android 6.0 (Marshmallow), and as an experiment I connected it to the car and AA works perfectly on it. So, it does look like that whenever Verizon gets around to pushing out the upgrade to the G4, our problems with AA may disappear.

 

[dgiaffe]

Just for edification, I have exhausted efforts to connect my rooted Verizon LG G4 to AA on my 2016 Golf. I still have my old G2, and I recently loaded CM13 on it which is based on Android 6.0 (Marshmallow), and as an experiment I connected it to the car and AA works perfectly on it. So, it does look like that whenever Verizon gets around to pushing out the upgrade to the G4, our problems with AA may disappear.

Yea I unfortunately have that feeling too.

 

[rdlkgliders]

Okay so to follow up I did a factory restore on my Tmobile H811 (LG G4) and installed only AA. I did update the 5 or 6 apps requesting an update.
The phone connected to AA on first try after entring into and accepting all the disclaimers for speech to text, navigation location etc along with the normal AA disclaimers that need to be accepted.
[/COLOR]I drove around starting and stopping many times using my past workaround of shutting the car off and then disconnecting the phone from the micro usb leaving the cord plugged into the cars usb. Then when I get back into car to start driving again I connect the phone back into the micro usb and turn on ignition ( I never push the off button on the radio as this has caused problems) at this time with me in car and car in park I accept the connection terms when asked and connect to AA and it will work without issue as long as I follow this procedure.
do not turn off stereo by pushing button on it this has caused me to start all over.
Next I decided to perform some of the troublesome steps of just disconnecting while car was running, leaving phone plugged in while car was off and then re starting and turning off and on radio between connections. All of these actions are trouble and create stability issues.
I got the phone to reconnect out of sheer persistence trying my uninstall and reinstall method and connecting and disconnecting and it is working again.
sorry it this is wordy but I want to translate my successes and failures to save others the abundance of time I have spent.
When connected please follow the part in red and let me know if this works for you.

NOTE
The Apps I updated after restore LG bloatware Health app etc... I also only signed in with my email address at the play store not when I started up the phine for the first time after the restore when it prompts for the google account to sync email etc...

 

[Windfrenzy]

2016 Golf with VZW G3, Android 5.1.1 and stock phone software. Not rooted. Did factory reset on phone with no effect. Still very temperamental and inconsistent. If anyone has it working well, what version is your VW software? Mine says 0241. Forget where I saw that, but noted it.

 

[dgiaffe]

Okay so to follow up I did a factory restore on my Tmobile H811 (LG G4) and installed only AA. I did update the 5 or 6 apps requesting an update.
The phone connected to AA on first try after entring into and accepting all the disclaimers for speech to text, navigation location etc along with the normal AA disclaimers that need to be accepted.
[/COLOR]I drove around starting and stopping many times using my past workaround of shutting the car off and then disconnecting the phone from the micro usb leaving the cord plugged into the cars usb. Then when I get back into car to start driving again I connect the phone back into the micro usb and turn on ignition ( I never push the off button on the radio as this has caused problems) at this time with me in car and car in park I accept the connection terms when asked and connect to AA and it will work without issue as long as I follow this procedure.

Hmm I guess I'll try plugging before starting the car and see if that helps. Now that you say you made a factory reset, I wonder if it wouldn't be a common installed app or a Google Play Services update that causes the issue.

 

[dgiaffe]

2016 Golf with VZW G3, Android 5.1.1 and stock phone software. Not rooted. Did factory reset on phone with no effect. Still very temperamental and inconsistent. If anyone has it working well, what version is your VW software? Mine says 0241. Forget where I saw that, but noted it.

Mine is 0613, but definitely not working either.

 

[dgiaffe]

from a VWVortex.com thread:
My primary phone is a Verizon LG G4 running Android 5.1, rooted but with a locked bootloader. I never have been able to get Android Auto working with it on my 2-week old R. I have tried numerous different cables to connect it, with no luck.

My backup phone is an old LG G2, and I just installed CM13 on it which is Android 6.0 Marshmallow, and Android Auto works perfectly on it when plugged into my new R! For the time being, I am just tethering that phone off of my G4 while in the car so that Android Auto works, until such time as Verizon pushes out Android 6.0 to the G4.

I have a feeling we can't do much, but I hate giving up as well lol. So I'll keep testing and update this thread.

 

[rdlkgliders]

The hard part is establishing the initial connection. I am not sure nor would I be comfortable endorsing any of the initial connection steps that have been discussed. In fact tonight after playing with it and disconnecting from AA I tried my usual steps to reconnect, No luck put the car in D and drove.
To my surprise after deciding to try and connect one more time while in drive whola it worked......Go Figure. I will say I have had great success keeping it reconnecting once I establish an initial connection by doing the steps in red upon every disconnect and reconnect. Let me know if this helps anyone else. PS I have the latest update available per VW. I will try and look up the exact version tomorrow. GL

 

[dgiaffe]

All right, well I think that was my last try until software updates of any sort. I tried using the original USB cable that came with the phone and resetting to factory default. I didn't restore the Google backup of my account, simply reset to factory default and installed Android Auto right away. That's the only thing I did and yet no luck. I even tried sideloading Android Auto on my Nexus 7 2012 (Play store tells AA is not compatible with the device so I downloaded it from apkmirror) and the wizard starts like a charm, no problem at all. I really think it's specifically the Verizon LG G4 that is affected. Unless anyone has one working (from Verizon)? I mean, not just intermittent connections, but at least being able to set it up.

I will try to stop by a Hyundai or Honda dealership this weekend to see if I can start AA from a different car maker. Then that would tell us if it looks more like a phone or car issue. For now, I really just want to use AA for Google Maps and I have no trips planned soon so I'll try to focus in enjoying my new car instead of thinking too much about this lol.

 

[dgiaffe]

OK well I didn't give up yet LOL! Had to try one last thing because (might be due to my IT profession) I can't let a problem unsolved. During lunch break, I went to Hyundai and asked to try out Android Auto with my phone. There was a Sonata with AA enabled in the showroom. I used the same cable from my GTI, same LG G4. AND BAM! It started right away.

I then went to my VW cardealer and of course, they didn't know what to do. I was asked to contact VW support to see if they can help. I sent them an email as well as a tweet. I discovered also the knowyourvw.com website, which is honestly really well done. Paid attention to the Android Auto video @ http://knowyourvw.com/?page=video&id=53&autoplay=5278 but found nothing I was doing wrong there.

As a summary:

GTI 2016
Nexus 7 starts wizard
VZW Samsung Galaxy S5 starts wizard (had to originally try a factory reset to make it work)
VZW LG G4 doesn't start wizard at all (including factory reset)

Sonata 2016
VZW LG G4 starts wizard without a problem. Literal plug and play.

So looks like something that needs to be updated (LG or VW, i am not really sure, but looks more of a VW thing) on the software side to make it work properly. I know that the latest software version of the MIB II firmware is 0613 and it had some AppConnect fixes --> http://www.goapr.com/support/tsb/91n9mibbulletinver2.pdf . However, this is the one I have unfortunately and it didn't fix mine. Might be worth a try if your MIB II firmware version is lower than that though. Dealer should be able to do the upgrade.

I'm following closely this thread. Will update if I run into any more information.

 

[rdlkgliders]

dgiaffe we are cut from the same cloth. I also have an IT degree and even though no longer in that field I can not leave these sort of issues alone as long as a new potential solution enters my thoughts. Today I called VW of America customer service and told them of our situations mentioning that there are many documented cases of Android phones (specifically LG G4's) having erratic connection issues. VW USA was very pleasant and said they will contact the dealer an area rep and escalate the case to their tech department and that I should hear back by end of day tomorrow.
Presently I am still connected using my work around and not doing any further testing for now.

 

[dgiaffe]

Nice! Good to hear. They actually got back to me on Twitter as well. Asked me for my VIN and email address and said they would reach out to me. I tried to call as well, but was stuck on hold for over 45 minutes so I gave up. Glad you reached them. Keep us posted!

 

[iamholam]

Also in IT (though with kids and family I don't get to play with my car as much!) currently waiting on Skoda UK to get back to me on what they can do to help with system. Good to know from you that it seems to be the MIB2 VAG system that is likely the issue rather than my phone.

 

[gmiterek]

Back in middle of December 2015 I got my brand new Tiguan R Line 2016. Been waiting 6 weeks of it. Beautiful. Love it. The first thing I tried was install my rooted Nexus 6 with CM13 on it. I wanted so badly to play with Android Auto. I did the whole install thingy. When it got to accept the android auto, my phone would reboot. No matter what I did, it always rebooted, downloaded the latest nightly, same thing. I was so pissed, I started regretting getting the Tiguan as the car I wanted was the RAV4 because it was a little bigger, but it didn't have Android Auto, so forget the bigger, getting a VW. After 3 or 4 days of trying all kind of fixes from the internet I gave up. I didn't want to put the original ROM, I love Cyanogenmod.

So, on the next weekend, I decided to try with my wife's phone, it's a LG G4 I think H813 is the model, but not sure. It worked on the first try, everything went smoothly, we played with all of the options (nice to tell google maps a name of a place to go and it guides you there, no more entering addresses or city's). Everything was working superbly. Her phone is with Bell Canada and it's running Lollipop 5.0.1. We've had a few hiccups reconnecting, but it would be just disconnecting the USB cable (love the fast charge on the VW) and reconnecting it and it would be back. The only thing I did, that could make a difference. I have good quality USB 3.0 cables and I installed all the software through the Wi-Fi and not the cell data network. I don't know if that could make a difference. Also, your USB settings need to be MTP (transfer files settings) and not charge only. My phone still didn't work.

At the end to get my phone to work, I had to change my ROM, I'm running Pure Nexus right now and it's working superbly great. The only thing I get is that if I leave my phone connected through the USB for android auto when I turn off the car and then turn it back on I lose the connection to my Bluetooth connection and Android Auto. For the AA to work, I just unplug replug the USB cable, but for the bluetooth to work, I need to resync them. If it's unplugged when I leave the car. Everything works great.

Loving AA, it's awesome, I don't use the NAV from VW. I only use Google Maps now.

 

[dgiaffe]

Cool, great input! Glad to see it works in Canada. I wonder if it has to do with 5.0.1 vs 5.1, or if the VW media unit is different in Canada vs US. I have a feeling the VWs are more finicky because they are trying to handle AA, CarPlay and MirrorLink, whereas I believe most manufacturer are choosing one and sticking to it.

 

[CPrice TX]

Well. I was about to give up, but finally got Android Auto (AA) to work on my 2016 GTI with the latest 0613 update for MIB II.

HTC One M8 with Android 5.0.1. I was having ALL the problems described in this thread. I switched the default connection back and forth from AA to MirrorLink -- it finally worked on AA. I tried every USB setting in my phone -- it finally worked on USB Network Setting "None". I uninstalled AA and re-installed -- it did not immediately work but then...

I read somebody say something about starting the car. I had been sitting without car running trying to connect. So, I started car, put into reverse, backed up about 2 feet and BAM -- AA seemed to reset and took me through all the acceptances and confirmations you must do to make it work.

After all that, my best advice -- uninstall and reinstall AA -- plug in phone BEFORE starting car -- START car -- and make sure you are in a place with excellent data coverage.

I was about to give-up, but it works! (now we will see if it continues over the coming days)

Good Luck everyone!

Chris in Dallas, Texas
2016 MK7 GTI - Carbon Steel - Bone-stock at this point

 

[dgiaffe]

I read somebody say something about starting the car. I had been sitting without car running trying to connect. So, I started car, put into reverse, backed up about 2 feet and BAM -- AA seemed to reset and took me through all the acceptances and confirmations you must do to make it work.

After all that, my best advice -- uninstall and reinstall AA -- plug in phone BEFORE starting car -- START car -- and make sure you are in a place with excellent data coverage.

I was about to give-up, but it works! (now we will see if it continues over the coming days)

Good Luck everyone!

Chris in Dallas, Texas
2016 MK7 GTI - Carbon Steel - Bone-stock at this point

Hmm when you backed up, was your phone simply unlocked, plugged USB? Might be worth giving it a try, even though I really tried a bunch of stuff. I never paid attention into which step I took before the other, but I know I had good coverage wherever I tried. Also, is your M8 with Verizon or another company?

Finally, good car choice, just got the same but in white

 

[dgiaffe]

Well I'm back, but no luck. I tried: Uninstall AA, Install AA, plug phone, start car, go to App Connect, select my device one, back up at the same time, stopped, retried, but same behavior. My phone shows AA half a sec and goes back to the home launcher. I do have the 0613 update as well. I do have a feeling somethings not properly set on the VW headunit for the G4 5.1. Who knows at that point anyway.