Hi, I just recently got a new Golf with the app connect system that has Android Auto functionality built in. However, I just can't get it to work with my G4. I've downloaded the Android Auto app, I've tried using different cables but every time I plug it in the AA app seems to just crash. It also won't connect manually when I try to connect it in the car. I live in Australia. Is there anything else I can do/download to make this work? Thanks.
Don't know if this will help, but try to set the Android Auto on a headunit. Mine was set to Mirrorlink by default.
Maybe in the settings you should define it to choose Android Auto instead ?
Make sure the phone is unlocked when its plugged in. Also, try plugging in the phone before you turn on the car. My Nexus 5 is able to connect 90% of time on my 2016 GTI.
I just picked up my GTI last night. The salesman couldn't get Android Auto to connect to my AT&T G4. Android Auto was set as the preferred connection. I've tried connecting with my phone locked, unlocked, plugged in before/after the car is on, plugged in after/before the phone is unlocked, USB debugging on and off, MTP, charging only, PTP.
monkadelicd said:
I just picked up my GTI last night. The salesman couldn't get Android Auto to connect to my AT&T G4. Android Auto was set as the preferred connection. I've tried connecting with my phone locked, unlocked, plugged in before/after the car is on, plugged in after/before the phone is unlocked, USB debugging on and off, MTP, charging only, PTP.
Click to expand...
Click to collapse
Did you ever get connected?
Robbie Doo said:
Did you ever get connected?
Click to expand...
Click to collapse
tt
I work at a vw/Skoda dealership. I am tech savvy. I have tried I phones and various Androids with Mirrorlink/Android Auto and to be honest the results are pretty Mixed. I phones mostly pair OK but with so many iterations of Android topped with manufactures bloatware its impossible. I have failed to pair phones that are compatible and tried every app every cable and every configuration even the Manufacturers are clueless. Some models I managed to pair took me 40 or 50 attemps. Android Auto is in its infancy and stability will take time. I managed an S5 with ease and S6 with great difficulty a HTC one A9 which is very unstable. A HTC one M8, but didn't manage the Huawei P8 yet but I'm working on it. I failed with a galaxy S4 and succeeded with another one. I have an LG G4 on the way so that will be interesting. I have had 100% success pairing I iPhones but customers tell us the connection drops out. However I do think Android Auto offers more in terms of functionality if you can live with the fact that you may not ever get it working.
Anything new with G4
Did you manage to make the LG G4 working?
Hello
I had the same problem with my VW Passat GTE 2016 + LG G4. Solved it by going into the settings in the car (under App Connect) and chose Android Auto as default instead of MirrorLink which was the default before.
(although it doesn't work very well anyway, sometimes it does, sometimes it doesn't)
I have Android Auto 1.6.2400
Konstigt said:
Hello
I had the same problem with my VW Passat GTE 2016 + LG G4. Solved it by going into the settings in the car (under App Connect) and chose Android Auto as default instead of MirrorLink which was the default before.
(although it doesn't work very well anyway, sometimes it does, sometimes it doesn't)
I have Android Auto 1.6.2400
Click to expand...
Click to collapse
Just to confuse the issue even more, my vw connects to android auto pretty much perfectly every time & yet I only discovered by accident that the default setting on the head unit was set to mirror link so maybe that's not the cause for you after all. It's pretty basic software so far it seems.
Sent from my Nexus 6P using XDA-Developers mobile app
I picked up my new Golf today, but it doesn't have the App Connect. My phone is an Oneplus One with MM Cos 13, do you think Android Auto can work with it?
Just my experience : I own a 2016 Jetta with App Connect and a Nexus 4. I had similar issues with AA connections first. The phone was running Android L 5.1..1. 2 weeks ago I went ahead and installed CM13 and now AA works way better : I never had a connection failure since... Really a plug and forget experience now. So I think Android M is better for Android Auto. Moreover I read that latest AA update includes fixes for connection stability.
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
I've given up on the Google Forums, looking for some relief here. Last September we bought a new 2017 Honda CRV. Great car, except...
It worked for several months, now I can't get AA to remain connected at all. I think I have been through everything. I just tried the recommended high quality Belikin 3.1 USB cord, it didn't make any difference. Tried other cords as well. This is so frustrating. One of the main reasons we went with the Honda over the Toyota was the availability of Android Auto. Unfortunately, this has been a real excercise in frustration.
When I start the car (USB not connected at this point), Bluetooth connects and AA automatically starts up on my phone. After a few moments, I plug in the USB cord. On the CRV's home screen the blue Android Auto logo shows in the smartphone field. I tap it and my phone connects to the head. So far so good. However, within a minute Android Auto vanished from my phone's screen and on the car's display I get "Device Not Connected".
Has anyone else had/solved this problem? Any of you using an HTC phone? It's not like the phone disconnects, it seems more like AA on the phone just shuts itself off/crashes within a minute or two of starting, but what do I know? Here is the kicker, the system seems to work fine with my wife's Samsung Galaxy S7 phone, SM-G930V. I just went out for a little drive. The HTC refuses to remain connected, the Samsung did just fine.
Error message: On head, "Device Not Connected". AA on my phone just stops. It's like AA on the phone stops working causing a disconnect from the car. Here is more info about my system.
Car/Head Unit make & Model
2017 Honda CRV
Head model: MY16DA
Android Auto version 4.2.2
Kernel Version 3.1.10+
Build number 1.F195.80
HTC 10, model HTC6545LVW USB C cable
Verizon
Android 8.0.0
Android Auto version 3.4.582534-release
Google play services: ver. 12.8.72 (040400-202717283)
Developer Options >USB debugging enabled. USB set to MTP and also tried other settings.
Tried changing out HTC cords to no avail. Just purchased new Belikin USB 3.1 cord. It didn't make any difference.
I have done a factory reset on my phone and on the Honda's display unit as well. I uninstalled HTC's Boost+, reset my phone's Bluetooth. I changed the battery settings on my phone to not optimize AA, Waze and Google Maps.
How can I fix this? Is there anyway out of this rabbit hole?
Switch USB debugging off change Bluetooth from 1.4 to 1.6 in the developers settings
Running into the same problem with an after-market Sony head unit (XAV-AX5000) and a Samsung Galaxy S7 (Oreo 8.0). I'll have to give the BT setting a try.
dq0 said:
Switch USB debugging off change Bluetooth from 1.4 to 1.6 in the developers settings
Click to expand...
Click to collapse
Nope, didn't work. It seems to connect to the phone fine, but then it quickly disconnects, within seconds, or a minute or two. Posting on Honda thread, it doesn't seem to be an across the board problem, I think it's limited to my phone. Having said that on the AA forums there are plenty of complaints about connecting problems. I was hoping against hope that this forum might have a deeper understanding or possible resolutions.
SammyQ2 said:
Nope, didn't work. It seems to connect to the phone fine, but then it quickly disconnects, within seconds, or a minute or two. Posting on Honda thread, it doesn't seem to be an across the board problem, I think it's limited to my phone. Having said that on the AA forums there are plenty of complaints about connecting problems. I was hoping against hope that this forum might have a deeper understanding or possible resolutions.
Click to expand...
Click to collapse
Try turning Dev mode in AA. OPEN app go to About. Click on the title several times.
dq0 said:
Try turning Dev mode in AA. OPEN app go to About. Click on the title several times.
Click to expand...
Click to collapse
I'm willing to try anything, I had no idea that setting existed. Sorry to say that it didn't work. Ugh.
I hope someone recognizes this problem.
I have an Opel Astra K (2016) with an Opel Intellilink Radio 4.0 system. By connecting the phone with USB to the system, Android Auto should start on the car's system.
I've tried connecting 3 different phones, a Samsung Galaxy S8+ with Android 9, Galaxy S9+ with Android 10 and Galaxy S20+ with android 10.
The Android Auto on the S9 and S20 are preinstalled, the phones are updated. The S8+ doesnt have it pre-installed so ive downloaded the APK,
Android Auto - Google Maps, Media & Messaging 5.3.5016 (28th may 2020).
Ive used 3 different cables. Original samsung cables and a unbranded cable. None of the attempts worked. Android Auto wont show up on the car display, but it starts on the 3 phones.
After almost giving up, i made a call with one of the phones while being connected with the USB. After the call, android auto started to show up on the car screen. It looks likes it got triggered by something. When i turn of the car, but keeping the cable connected, Android auto keeps working after starting the car again. The connection goes away after disconnecting the phone (pulling out the cable). After making a call again, it starts to work again. I have no idea how this happens and what the reason could be.
The "trick" by making a phone call works on all phones and with all cables.
Anyone got an idea?
I switched from Pixel 2 to Pixel 6
Reset the cached data in Android Auto
Deleted the bluetooth connection
Reset the AAwireless device with a paper clip.
Tried to connect both with the app and/or the bluetooth from the phone.
It discovers the device
It kind of connects but the Android Auto in the car does not start so the step of choosing AA in the car's headset cannot be done.
the car with Android Auto does work with directly connected to the port.
Just cannot use the AAwirelesss anymore which is upsetting.
carthorisJ said:
I switched from Pixel 2 to Pixel 6
Reset the cached data in Android Auto
Deleted the bluetooth connection
Reset the AAwireless device with a paper clip.
Tried to connect both with the app and/or the bluetooth from the phone.
It discovers the device
It kind of connects but the Android Auto in the car does not start so the step of choosing AA in the car's headset cannot be done.
the car with Android Auto does work with directly connected to the port.
Just cannot use the AAwirelesss anymore which is upsetting.
Click to expand...
Click to collapse
Use the AAwireless app to send a tech support request by tapping the box labeled "Help and Support." Describe your problem exactly and briefly.
carthorisJ said:
I switched from Pixel 2 to Pixel 6
Reset the cached data in Android Auto
Deleted the bluetooth connection
Reset the AAwireless device with a paper clip.
Tried to connect both with the app and/or the bluetooth from the phone.
It discovers the device
It kind of connects but the Android Auto in the car does not start so the step of choosing AA in the car's headset cannot be done.
the car with Android Auto does work with directly connected to the port.
Just cannot use the AAwirelesss anymore which is upsetting.
Click to expand...
Click to collapse
I recently updated my phone, and with that update came Android 12. I had to turn on the passthrough options in AAW app settings and that worked for me. You should give that a try.
I am having the same problem. Car is a 2020 Corvette and I switched from S20+ to S22+. After a few tries a while back it connected and worked fine on S20+. I go through the connection process on S22+ and everything goes smoothly but after process, the dongle is connected to WiFi of phone. and LED's on AAWireless cycle between blinking green and blinking blue. I have also cleared cache, uninstalled Android Auto and reinstalled, changed cables. and nothing works to get the car connected. I have sent a support question to AAWireless but does anyone here have any thoughts. I have done the passthrough think but it didnt work. I will try again from a clean start.