Related
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
Hi,
I'm using AA for about 4 weeks in my VW MY16. It's very nice! :victory:
However, I have some question: If I start the AA app, and after I connect the device to the car, then I can select the AA in the car screen. But, If I reboot the phone and I connect to the car, then the AA in the car don't connect.
So the problem is quite simple: Only if the AA app is launched in the phone, then it automatically connects to the car when you connect the USB wire to the car. You don't need to have the app in the foreground, only in the background. But when you reboot, the App don't start.
Someone knows a method for auto-launching the AA app when the phone is connected to the car?
It SHOULD be automatic. I have never heard of needing to have the AA companion app open.
What phone and Android version/ROM ?
mikereidis said:
It SHOULD be automatic. I have never heard of needing to have the AA companion app open.
What phone and Android version/ROM ?
Click to expand...
Click to collapse
Hi,
I have a Wiko Fever with stock Lollippop 5.1.
Please, try these tests:
1) Open AA, push HOME button (the App continues in background), and lock the phone. Then connect to the card and start it. Result: The AA opens in the car automatically.
2) Open AA, push HOME button (the App continues in background), select "running Apps", CLOSE AA and lock the phone. Then connect to the card and start it. Result: The AA don't start in the car automatically; you need to unlock the phone and start the AA app.
3) Reboot the phone. Don't open AA and lock the phone. Then connect to the card and start it. Result: The AA don't start in the car automatically; you need to unlock the phone and start the AA app.
It's the same in your case?
manos78 said:
Hi,
I'm using AA for about 4 weeks in my VW MY16. It's very nice! :victory:
However, I have some question: If I start the AA app, and after I connect the device to the car, then I can select the AA in the car screen. But, If I reboot the phone and I connect to the car, then the AA in the car don't connect.
So the problem is quite simple: Only if the AA app is launched in the phone, then it automatically connects to the car when you connect the USB wire to the car. You don't need to have the app in the foreground, only in the background. But when you reboot, the App don't start.
Someone knows a method for auto-launching the AA app when the phone is connected to the car?
Click to expand...
Click to collapse
In my Skoda Octavia MY16 when I connect the USB cable AA starts automatically in my phone Galaxy S6,
Then select the AA in the Infotainment menu.
I've been having to open the app before plugging my phone into my Hyundai Sonata. Unfortunately, it sometimes still doesn't launch in the car, so I have to unplug, force close android auto and then reopen. It's a pain to get it started up. I have a Note 4.
Sent from my Nexus 7 using Tapatalk
ireknole said:
I've been having to open the app before plugging my phone into my Hyundai Sonata.
Click to expand...
Click to collapse
That is! You need to open the AA app before plug the phone in the car.
war1 said:
In my Skoda Octavia MY16 when I connect the USB cable AA starts automatically in my phone Galaxy S6,
Then select the AA in the Infotainment menu.
Click to expand...
Click to collapse
That is because you first opened the AA app and it's running in the background. Try this: reboot your phone, don't start AA, plug the phone, start the car... You can select the AA in the Infotainment menu?
manos78 said:
That is! You need to open the AA app before plug the phone in the car.
That is because you first opened the AA app and it's running in the background. Try this: reboot your phone, don't start AA, plug the phone, start the car... You can select the AA in the Infotainment menu?
Click to expand...
Click to collapse
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
war1 said:
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
Click to expand...
Click to collapse
My test is:
1) Phone reboot
2) Unlock phone and connect to the car
3) Start the car
4) Try to select AA in the screen of the car
In this order, don't work with my car (VW MY16). I'll try your suggestion. :fingers-crossed:
Thank you!
war1 said:
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
Click to expand...
Click to collapse
You restart your phone everytime? That would get annoying.
I think the key is waiting until Bluetooth is connected before starting android auto. But even when I do that it sometimes still doesn't work in my Hyundai Sonata. I really haven't found anything that works consistently.
Sent from my SM-N910V using Tapatalk
ireknole said:
You restart your phone everytime? That would get annoying.
I think the key is waiting until Bluetooth is connected before starting android auto. But even when I do that it sometimes still doesn't work in my Hyundai Sonata. I really haven't found anything that works consistently.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Not every time of course, I did a reboot just to test,:laugh:
ireknole said:
I think the key is waiting until Bluetooth is connected before starting android auto.
Click to expand...
Click to collapse
Starting AA companion app or AA in the car? Of course, if I start the AA companion in the phone, then the car connects (in my case is indifferent if the car is on after/before or if AA is started after/before Bluetooth).
My concern is: plug the phone and start automatically the AA companion app, even if you don't start it after you reboot your phone. This is the request!
Hi,
This really works:
1) Reboot phone and NOT start AA companion app.
2) Start the car, wait until Bluetooth is connected to the phone.
3) Connect the phone to the USB of the car.
4) Select AA on the Infotainment menu... IT WORKS!
I'll do more tests... typically I connect first, then I start the car...
manos78 said:
Hi,
This really works:
1) Reboot phone and NOT start AA companion app.
2) Start the car, wait until Bluetooth is connected to the phone.
3) Connect the phone to the USB of the car.
4) Select AA on the Infotainment menu... IT WORKS!
I'll do more tests... typically I connect first, then I start the car...
Click to expand...
Click to collapse
The rule is first wait for the bluetooth sync and then connect the usb cable because AA need the bluetooth for make calls.
war1 said:
The rule is first wait for the bluetooth sync and then connect the usb cable because AA need the bluetooth for make calls.
Click to expand...
Click to collapse
Not completely really,
After several tests with different order and reboots, I like to confirm that the AA companion app don't need to be started before connect the phone to the car. The KEY point is the BLUETOOTH (yeah!)! If the phone isn't paired with Bluetooth, or the Bluetooth is disabled in the phone, or (and this can be the annoying trouble for some like me) if the bluetooth connection is stalled in the phone... then the AA connection don't work.
So, my recomendation: You can connect the phone to the car in any order, but check Bluetooth if you have troubles.
:good:
I'm finding that even after Bluetooth is connected, it still doesn't start up. Today I tried unplugging and replugging the USB for about 10 minutes before it finally, for no apparent reason, decided to take and launch AA.
Sent from my SM-N910V using Tapatalk
I just read something on Twitter yesterday from Android support and it seemed to help. Go into the Android Auto app in the application manager and clear the cache. Once I did that, the app seems to connect better.
I also found that if I start the app and it doesn't connect, if I go into my active apps and clear out Android Auto, it will connect the next time I plug in the USB.
Sent from my SM-N910V using Tapatalk
I think all the car radios work differently. I don't turn on any Bluetooth, or run the AA before plugging. All I do is plug in, and the Bluetooth and everything else connects automatically. So I guess it all has to do with your initial setup.
Just got the update. On the latest version, I can use AA on the phone, but it no longer goes on my car display. Anyone else have the issue?
Tried uninstalling and reinstalling AA, and rebooted the head unit.
2016 Civic, S7 Edge.
I had to go through it on my phone when it was plugged in and accept the terms again.
Sent from my SM-G930W8 using Tapatalk
I've accepted the permissions repeatedly. The home screen on the car shows "Smartphone connection" and occasionally "Connected device isn't responding."
(Everything worked on the same usb cable until 2 days ago!)
Hello, everybody
Before I did the update to Android 9 on my Huawei P20 Pro, AA worked fine in combination with the Opel Intellink. Unfortunately, this has changed to a disadvantage since the update. As soon as I connect my mobile phone with the USB cable, the system asks me which USB option I want. So far so good.
But now it comes: As soon as I activate "Android Auto" in the Intellilink 4.0 settings, my phone crashes and tries to reboot. I already tried everything possible:
- other cable
- AA de- and newly installed
- Bluetooth newly paired
- USB debugging enabled (developer mode enabled)
- USB option set to MTP
- Wipe Cache partition performed
nothing helps.
Even if I don't have AA installed it crashes.
Does anyone have this phenomenon too?
Without activation this is not a problem. Bluetooth also works here.
Many thanks in advance for any suggestions or solutions.
Greetings Finrok
Me too - solution please?
Same here. Working just fine before the update. Now whenever I connect the phone to the car via USB it crashed and reboots. Tried the same as above but I can't see a solution.. I've managed to get it working since by uninstalling and unpairing the device. Plugging it in and reconnecting. But as soon as I unplug and go again next time it crashes again and reboots as before.
Not an issue with the cable, cache or Bluetooth.
May also be worth noting, I also have a p20 pro. Brand new in November
Has anyone figured it out? Please!
Was it OTA update or one of the methods from the forum (eRocovery, OTG)?
Is factory reset an option for you?
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.