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

P.S dgiaffe V.W USA has been very good to me and has gotten back to me every time they said they would. I am getting a new Head unit (radio) It will be appx 30 days and I am not convinced it will help unless there are a bunch of people out there with working G4's and other problem phones and we are the minority, who knows. Stay with it VW gave me a pretty fair offer so follow through.
Good to hear they are helpful. My Feb 3rd appointment was confirmed today so hopefully they'll figure something out.

I guess I'll retry a few things tomorrow as I am driving out of my town and would LOVE to use maps through AA instead of using my phone separately. This is really the one thing I want from AA. Also like I said earlier, I'll try my cousin's G4 from Canada on Friday, see if that makes any difference.

Besides that, I have a feeling I exhausted everything i read in this thread and nothing brings me even to the setup. Is there anyone specifically with a G4 on Verizon who's able to get passed through the setup wizard? I'll be retrying all of the tricks here just to make sure i didn't forget something... Just doesn't make sense it is so complicated when it simply starts in the Hyundai.

In theory, you should even be prompted to download AA when you connect if it is not installed. Regardless, AA installed or not, Bluetooth on or off, Bluetooth paired or not, I always get that short black screen and back to home launcher.
 
Continuing to work the problem, I:
  • Disabled HTC Sync on my phone
  • Disabled the standard "Car" app on my phone
  • Uninstalled and reinstalled Android Auto (AA)
  • Turned off Bluetooth
  • Plugged phone into USB before starting Car

And today for the first time I was able to connect, and then quite easily re-connect a 2nd and 3rd time. By only plugging and unplugging phone when the car is OFF.

VW may not be as simple to connect as Hyundai, but I have the feeling more of the problem is related to the extremely fractured software images on our wide variety of Android phones, along with the various apps added by our various phone vendors and carriers.

My latest advice -- keep disabling EVERYTHING that wants to start up naturally when you plug your phone into a USB port.

Good Luck,
Chris

2016 VW GTI SE -- Carbon Steel Gray
HTC One M8 - Android 5.1 (should be Marshmallow by this time next week -- come on T-Mobile)
2016-01-07 14.07.07.jpg
 
Hi there everyone. I'm experiencing exactly the same issues here. I bought a 2016 Golf GTI (Pure White BTW :), and can't use AA with my Samsung Galaxy S6. When I plug the phone, the infotaiment shows "reading usb device" for a while, then it goes away, and then shows it again, goes away, etc. I've tested a Nexus5, a Motorola Moto X Force and a Xiaomi Mi4c and all of them worked like a charm with AA. But there is no way to get my S6 working, I've already tried everything I've read here. Hopefully updating to marshmallow will fix the issue.
 
Continuing to work the problem, I:
  • Disabled HTC Sync on my phone
  • Disabled the standard "Car" app on my phone
  • Uninstalled and reinstalled Android Auto (AA)
  • Turned off Bluetooth
  • Plugged phone into USB before starting Car

Unfortunately that didn't work for me either. I have nothing autostarting with USB anymore, but still not luck *sigh*.
 
Continuing to work the problem, I:
  • Disabled HTC Sync on my phone
  • Disabled the standard "Car" app on my phone
  • Uninstalled and reinstalled Android Auto (AA)
  • Turned off Bluetooth
  • Plugged phone into USB before starting Car

And today for the first time I was able to connect, and then quite easily re-connect a 2nd and 3rd time. By only plugging and unplugging phone when the car is OFF.

VW may not be as simple to connect as Hyundai, but I have the feeling more of the problem is related to the extremely fractured software images on our wide variety of Android phones, along with the various apps added by our various phone vendors and carriers.

My latest advice -- keep disabling EVERYTHING that wants to start up naturally when you plug your phone into a USB port.

Good Luck,
Chris

2016 VW GTI SE -- Carbon Steel Gray
HTC One M8 - Android 5.1 (should be Marshmallow by this time next week -- come on T-Mobile)
View attachment 214043
Bizarrely I found that if I could get AA working once when plugged in, even if I unplugged and replugged back in it would have a better chance of working again. However it would just fail again the next day for no reason when using the car every time.
 
I have found that I can connect every time if I close all apps except Android Auto. Other apps shouldn't be open at all.

If I have another app open, even if it is minimized, I probably won't connect.

It works reliably this way. I'm hoping that an update will make it work better.

Posted via the Android Central App
 
I went to the Detroit Auto Show this weekend and figured I'd ask the crew of the VW booth about it. Tried my phone in a different GTI, it had a different software version (0245 if I remember, instead of my 0613) and it had the exact same behavior. I am doubtful that rdlkgliders' head unit replacement will work now. The lady was nice enough to take my email and information and she said she would relay this to her superiors. Told them the same phone was working right away in a Hyundai Sonata, which I don't think they liked hearing lol. All I want is awareness and it looks like it is working.

Also, my cousin's LG G4 from Canada had the same problem when plugged in. Granted, we didn't test thoroughly (only tried once), but to me, it should be working right away, we shouldn't have to troubleshoot it for minutes everytime you want to go somewhere.

lawguyman, I'll try closing all my apps to see if this'll help. Can't wait to get that rolling with my appointment on Feb 3, even though I know it'll be still a long process.
 
Drove a few hours total yesterday and today, and used Android Auto (AA) quite a bit. Here are some of my observations.

-- Definitely helps to close all other apps. With all other apps closed, it will keep trying to connect until it is finally successful.
-- MUST turn off Bluetooth -- for me it will NOT connect if Bluetooth is on (AND it automatically turns Bluetooth back on anyway once connected to AA).
-- Doesn't like to switch data connections. I was visiting my mother, and the phone was on house WiFi. I think AA connected while on WiFi, and I pulled away from house, losing WiFi connection. Not only did AA freeze, the whole headunit froze for a couple minutes. Note to self, make sure I am not on a WiFi connection that I am going to drive away from while AA is connected.
-- I like the AA interface, although I wish for even more functionality (which of course would probably negate the goal of reducing distractions). I plugged in an iPhone in this evening, and was of course amazed by the quick connection. But, I was disappointed in the interface -- not nearly as elegant at AA.

2016 GTI SE
HTC One M8 - Android 5.1
 
I plugged in an iPhone in this evening, and was of course amazed by the quick connection. But, I was disappointed in the interface -- not nearly as elegant at AA.
I've used CarPlay for 5 months, and have now been on Android Auto about 6 weeks (OEM vehicles - I work in the industry). I DO NOT want to be an iPhone user - but there's something to be said about just plugging your phone in and having it work. Based on all the issues/quirks I'm reading about for various handsets, I fear AA adoption will be a longer (and more painful) process than CarPlay.

My G2 was a total failure (slow/laggy in AA), while my Moto X 2013 is good probably 90% of the time - but getting the connection is never a one-step process.
 
Another update on my end (no good news): My friend just got a 2016 Honda Accord and I tried my phone with AA in it. The phone worked on first try! It really is VW's implementation of AA that is not working properly, at least for the LG G4, and, throughout the thread, I'm assuming some other phones as well. It shouldn't be as finicky to make it work.

My appointment with my local dealer and a Regional Case Manager is Wednesday. I'll definitely add these details to the conversation with them. The fact that my phone reacted the same in a VW GTI at the Detroit Auto Show also leans to the fact that VW is wrong somewhere in its AA implementation.
 
I can add to your friend's success...my Note 5 connects 100% of the time on my 2016 Accord. After connecting the cable to the phone 15-20 seconds passes and the connection is established.

I've been following this thread with curiosity because I have no issues and am wondering how your issue is resolved. It appears to be a VW issue or maybe Honda has just nailed the thing down.
 
I am now connecting consistently and fairly quickly, after major challenges in the beginning, by ensuring these steps:

Bluetooth off (AA has never connected with it on before the plug-in).
All apps closed except for alarm clock and business mileage tracker (this includes AA itself and I'm guessing any apps that work with AA like Messages, Music apps, etc).
I've found that it connects quicker by having AA closed and not starting it on the phone. Just let it do the work.
I've gotten used to just pulling up the radio for a couple moments while it works through its connection dance. It seems to be connecting quicker and quicker each time. Still slower than the Hyundai and Honda systems though I'm guessing.

And EVERY time, my phone asks me to approve the data transfer request from the vehicle, even though EVERY time I say Yes and Don't Ask Me Again.

Sigh. I'd love to ignore it but my phone insists that the request be answered, although I don't see it making any difference in functionality.

Chris - Dallas Texas
2016 GTI SE - HTC One M8 Android 5.1
 
I've had my 2016 GTI for w few weeks and I have not been able to get my Verizon G4 to connect- not even once. At least I'm not the only one?

I got this answer from the "Android Auto Team" in response to a comment/email through the Play store:
"We're working with VW to identify and confirm the issue and resolution. Once that happens we will post to our help site with more information on when this will be resolved. Thanks for writing us..."
 
I've had my 2016 GTI for w few weeks and I have not been able to get my Verizon G4 to connect- not even once. At least I'm not the only one?

I got this answer from the "Android Auto Team" in response to a comment/email through the Play store:
"We're working with VW to identify and confirm the issue and resolution. Once that happens we will post to our help site with more information on when this will be resolved. Thanks for writing us..."

Glad to hear! The more who report, the faster they'll get it fixed or take it seriously. Peace!
 
I have had a 2016 VW for two months, and I also have frequent Android Auto connection problems. My phone is a Nexus 5x (which Google still sells directly as a showcase for Android M).

I intermittently get the same connection problem, where it presents looping error messages on the display (describing a connection problem), while I am driving.

I also just went to the Google play store, selected "Android Auto", and reported the connection issue to the email address that they listed.

Thanks to everyone on here, who is helping to get this solved.
 
I have independently been doing the same thing as you, but my phone is a Nexus 5X and still requires it.

Just as you said, once I have a connection, I can usually re-connect. But if anything happens out of order, then it is often a difficult crapshoot to re-connect with Android Auto and App Connect.
 
Been following this closely (thanks everyone!) because my new Golf purchased in Australia in Nov does not work with my new LG G4 (of course my LG works fine with other car, I tried everything about this).

I've been to VW garage yesterday for another reason and asked them about AppConnect - so the official answer from VW is that they are aware of this issue and working on it and expected to push an update to clients later this year.
So you need to register your interest in this update and they will then contact you when the update is available.
(This also relevant for the back camera bug they have..)

I suppose you never really know if they are actually working on it and when (and if) the update is really pushed but it sounded like they are taking responsibility on this.

T.
 
I see we have more and more people reporting their connection issues to both VW and AA which I hope helps to create a quick resolve.
My connection has gotten a lot more stable since we all started sharing info. I still use my workaround of disconnecting and reconnecting and am connected 90% plus. The problem always lies in the reconnect when I forget to take the right steps. I can connect with BT on and also never open AA on the phone allowing it to happen on it's own. I don't seem to increase or decrease my chances by closing apps but can't swear to it since I am mostly connected. I was one that threw a pretty big stink with the dealer and VWOA letting them know I cannot accept this. VWOA has been great and today I took my car in to have the MIBii replaced per their tech and the dealers tech's recommendation. I had previously had my car in to be serviced a couple times and started my case with VWOA appx 2 weeks or so ago. I do not expect the new radio to solve the problems but am willing to try as there are other issues that may or may not relate to the AA problem.
On occasion I lose all volume in all sources even though the source is playing and the volume is up. Also I have had the radio shut off completely on me while driving. Yesterday I had a first with AA working I could get no audio again so I started playing with it and found when I shut off BT the audio would come back. I am real curious to hear what the problem is but not confident I ever will although I do believe that the issues will be corrected for all of us soon. With Marshmallow around the corner I hope that things get resolved sooner than later. You guys on Verizon seem to be getting the worst of it as My Tmobile G4 at least connects albeit only after a prayer, a sacrifice and a note from my mother.
GL to all and I will update my findings after I get the new unit installed.
 
I see we have more and more people reporting their connection issues to both VW and AA which I hope helps to create a quick resolve.
My connection has gotten a lot more stable since we all started sharing info. I still use my workaround of disconnecting and reconnecting and am connected 90% plus. The problem always lies in the reconnect when I forget to take the right steps. I can connect with BT on and also never open AA on the phone allowing it to happen on it's own. I don't seem to increase or decrease my chances by closing apps but can't swear to it since I am mostly connected. I was one that threw a pretty big stink with the dealer and VWOA letting them know I cannot accept this. VWOA has been great and today I took my car in to have the MIBii replaced per their tech and the dealers tech's recommendation. I had previously had my car in to be serviced a couple times and started my case with VWOA appx 2 weeks or so ago. I do not expect the new radio to solve the problems but am willing to try as there are other issues that may or may not relate to the AA problem.
On occasion I lose all volume in all sources even though the source is playing and the volume is up. Also I have had the radio shut off completely on me while driving. Yesterday I had a first with AA working I could get no audio again so I started playing with it and found when I shut off BT the audio would come back. I am real curious to hear what the problem is but not confident I ever will although I do believe that the issues will be corrected for all of us soon. With Marshmallow around the corner I hope that things get resolved sooner than later. You guys on Verizon seem to be getting the worst of it as My Tmobile G4 at least connects albeit only after a prayer, a sacrifice and a note from my mother.
GL to all and I will update my findings after I get the new unit installed.

Do you know which software version you have in your MIB? I believe the latest is 0613, but I could be wrong. This bulletin describes exactly what you are saying with the screen going blank or restarting: http://www.goapr.com/support/tsb/91n9mibbulletinver2.pdf I am already on 0613 and didn't face your issues, so maybe they can try the update on your car. I don't think it'll help AA, but at least it should fix your issues.. even though your MIB is being replaced.

My appointment is tomorrow. I hope I'll hear something new. I'll probably decline the head unit change if they offer it, since my phone did the same thing at the Detroit auto show, in another GTI. Maybe they will confirm what Tomerhd said earlier instead. I'll report back tomorrow night with the results of my appointment. I'll also report to Android Auto's support in the Google Play Store.
 

Trending Posts

Forum statistics

Threads
956,893
Messages
6,970,483
Members
3,163,641
Latest member
RichardDixon