AAWireless - General discussion and support

Search This thread

Virnik0

Senior Member
Sep 14, 2010
1,902
421
Prague
blog.nutcracker.cz
I received my own yesterday. It is even smaller than i thought. Connection works, but so far, it didn't start automatically. I had to run AAWireless APP and select to check connected device, then it connects. I suspect BT connection conflict between BT of my car, watches, camera and AAWireless. Will give it more testing, it is very early to judge.
 

mack0a

New member
May 11, 2021
2
1
I used the search and didn't really find anything that sounded like the issue I have. Since I received my AAW, it does nothing but sit in "boot". The green light comes on as soon as I plug it in and never cycles. I have tried to put the device in flash mode to update the firmware, but same results.

The same for me, solid green light, it never goes beyond booting.
I have already tried rebooting the device with a 5-second press, flashing it with DRAM fix - no effect so far.
Is it bricked? It still can be flashed, so maybe there's hope. Is there any alternative firmware that I can "unbrick" it with?
 
  • Like
Reactions: GeekyHusband

Snirpo

Senior Member
Jan 23, 2007
66
60
We fixed the "VW Headunit crashing on skipping tracks" issue now completely. Confirmed it's a bug on the HU side, latency makes it worse. We will probably push a new firmware by the end of this week.
I will also submit a bug report to Google, cause they can fix/workaround this issue as well for cabled users.
 

Genebaby

Senior Member
Dec 11, 2013
647
78
I was just trying to do something other than music streaming in the Polo and the AAW box rebooted. Last time I was trying to hear a message using AA, this time I was in the phone section of the headunit, and this time I have the VAG specific FW, so for me nothing has changed.

Hopefully I just submitted a bug report just afterwards from Fql2KAtB
 

Snirpo

Senior Member
Jan 23, 2007
66
60
I was just trying to do something other than music streaming in the Polo and the AAW box rebooted. Last time I was trying to hear a message using AA, this time I was in the phone section of the headunit, and this time I have the VAG specific FW, so for me nothing has changed.

Hopefully I just submitted a bug report just afterwards from Fql2KAtB
I'll put your device on the new version so you can check. However I see you have a Harman and Delphi headunit, so these are probably unrelated. Your headunit doesn't reboot, but AAW itself restarts?
 

Snirpo

Senior Member
Jan 23, 2007
66
60
Thanks, I'll check in the car soon, and yes, this is a Delphi unit in this car. Did my logs come through?
Sadly the logs haven't arrived. The log sending functionality is utter sh*t right now. We really have to improve it, but so much other stuff to do :( Could you try again?
 

Genebaby

Senior Member
Dec 11, 2013
647
78
Ok, I applied the update on the way home and can report some strange behaviour afterwards. I just submitted (hopefully) logs again just now.

So I applied the update and decided to ask Google for a song, which I can't recall being a reboot issue, just wanted to hear a song. I did notice that the Assistant's voice was choppy, but the music was fine. Then I realised that I could no longer change the volume of the music. The volume button only affected the Assistant volume, like you can do when the Assistant is talking.

So I asked some questions and always got the choppy Assistant voice.

When I got home I did another log submission and the AAW rebooted. Put the music back on and the volume works for the music. Asked a question, choppy Assistant and the volume again is stuck for the Assistant.
 

Snirpo

Senior Member
Jan 23, 2007
66
60
Ok, I applied the update on the way home and can report some strange behaviour afterwards. I just submitted (hopefully) logs again just now.

So I applied the update and decided to ask Google for a song, which I can't recall being a reboot issue, just wanted to hear a song. I did notice that the Assistant's voice was choppy, but the music was fine. Then I realised that I could no longer change the volume of the music. The volume button only affected the Assistant volume, like you can do when the Assistant is talking.

So I asked some questions and always got the choppy Assistant voice.

When I got home I did another log submission and the AAW rebooted. Put the music back on and the volume works for the music. Asked a question, choppy Assistant and the volume again is stuck for the Assistant.
Got your logs, will check them later. These issues seem completely unrelated. I suppose you did try multiple cables and tried passthrough mode? Also please try 2.4ghz WiFi and make sure debug logging is off (cause this hurts performance alot, and might cause very odd issues).
 

Genebaby

Senior Member
Dec 11, 2013
647
78
Ok, I'm using a known good cable, I don't think the car likes passthrough but I'll try that and the wifi too.

Just went for a quick drive and same thing happens when I get a notification to listen to, buggy voice and volume issue. Strangely the music volume decreases afterwards, it goes quieter than it was set to.
 

Marshy33

Senior Member
Nov 28, 2015
133
36
Ok, I'm using a known good cable, I don't think the car likes passthrough but I'll try that and the wifi too.

Just went for a quick drive and same thing happens when I get a notification to listen to, buggy voice and volume issue. Strangely the music volume decreases afterwards, it goes quieter than it was set to.

My good cable gets lots of disconnections with AAwireless. The only cable that has been solid for me is the one that came with AAwireless.
 

Genebaby

Senior Member
Dec 11, 2013
647
78
My good cable gets lots of disconnections with AAwireless. The only cable that has been solid for me is the one that came with AAwireless.
I'll switch to that one, it's what I'm using in the other car, that doesn't get as much use at the moment. Need to go for a decent drive so I'll try all this later
 

Nudnik_de

Senior Member
Feb 22, 2011
98
18
Zurich
I'm on the AAWireless VAG software version (1.3?) provided by Snirpo and my VW MIB2 Technisat PQ is on SW 475. Today I had the first headunit reboot since I updates both.
Interesting observation: it's the first time it rebooted during playing a song on spotify and not when changing songs...
 

valeri_s_k

Member
Aug 24, 2020
13
0
Bourgas
Got my unit yestarday, setup was easy and for minute or two.
Just after setup, updated to newest version.

Car/HU - VW passat 2017/MIB2 - ZR Technisat/Preh
Phone - Xiaomi Mi 9T pro with custom AOSP Rom

Before receiving AAW unit I have used TV stick which was slow ( more than 2 minutes total time for AA to appear). Otherwise good for most of the time, but not always - tv stick crashed from time to time.

First observations after few short drives, total abt 30 minutes:
- Faster than expected - abt.20 seconds - AA appears on the HU display only few seconds after phone connected to car BT.
- stable connection, no HU or AAWireles unit crashes/reboots so far. By the way never had HU crashes when on wired connection or when used tv stick as well.
- play music (Spotify) with no interruptions.
- steering wheel buttons operating as usual.

In general could not notice difference between wired and wireless connection.

Hope it will stay stable on longer drives too.
 
Last edited:

Genebaby

Senior Member
Dec 11, 2013
647
78
Doing a lot more driving than usual this evening, got one more trip to go.

Just now I went for a drive, swapped to 2.4ghz and used the AAW cable. Same new issues with Assistant and volume.

On the way back I enabled passthrough, and those issues are gone. I thought that passthrough was a stop-gap type of thing and it was best to try and use MTP or Direct (I was using Direct), but I"m happy with passthrough as l just want a wireless experience, not to change DPI or anything.

So I'll keep it on Passthrough and 2.4ghz for the first half of my next trip, which is going into the area it loves to sktip the song, and then let it go onto 5ghz for the way home and see how it goes.

Just to be clear I've never had the Assistant volume issue until I got the experimental FW this afternoon.
 

Top Liked Posts

  • 1
    My PIxel 4XL connects fine in my 2020 Hyndai Kona but never connects to my 2020 Corvette.

    AAWireless is flashing a blue light this whole time but Android Auto never comes up.

    Direct mode by itself made things worse (red light = rebooting I think) and Passthrough Mode didn't work either.

    Anything else to try?
    Try 1.4 fw on aaw if you are not already running with it. As you are on GM car, best bet afaik is on "default" usb mode. Full reset AAW, forget it on bt settings, and wipe data+cache on aawireless + wipe also all in original aa app

    Edit: made it more cohesive and understandable
  • 7
    Some edited thoughts on my settings with AAWireless Config 1.8.2 that may help someone. This version of the app works best with OTA firmware version 1.3.0. Which should be available soon for all versions of the AAWireless device. It may also be used with OTA firmware 1.2.x, but we have identified some problems that are fixed in OTA firmware 1.3.0. Update when you get the chance.

    The 1.8.x version of the app introduces the Start / Stop option.

    I have a 10.25 Hyundai head unit. I think that the Wireless Projection function of this unit is the same for KIA and Genesis 10.25 inch head units. This head unit first appeared in 2019 Korean model years and is very flexible when used with with AAWireless.

    Here are the settings in the AAWireless Connect app version 1.8.2 that I use and what also works with my head unit.

    USB Mode I use MTP, but Direct works as well. The head unit responds a bit faster with MTP.

    Passthrough I have it turned off. The head unit works with Passthrough turned on, but DPI, Remove tap restriction, Disable Audio Sink, AutoVideo Focus and Developer mode cannot be processed by AAWireless when on. When on the exact encrypted data conversation is transmitted between your phone and the head unit. When off, AAWireless joins the conversation to inject those Experimental Features.

    Force 2.4Ghz I have it turned off. The 5Ghz channel used is 40. This feature will turn off 5Ghz Wi-Fi in favor of 2.4Ghz Wi-Fi on channel 1.

    Start / Stop I have this turned on. What it is designed for is those vehicles that keep the USB port powered on while the ignition is off. My Hyundai keeps the USB port powered for several minutes after I turn off the car and leave vehicle. With this turned off, my phone won't connect to my home network.

    WiFi connect timeout I now leave this at the default 20 seconds. For a couple of months after the initial conversion to Android 11, my Samsung Galaxy S20 FE 5G phone would not connect to AAWireless on the first try. It would always connect on the second try. Samsung fixed their problem with a subsequent update. But while this was a problem, reducing the WiFi connect timeout to 5 seconds really helped.

    Adjust audio timestamp I have it turned off. The head unit also works with it turned on. Turn this on if you notice things out of sync. With OTA firmware 1.3.0, enabling this option will help with certain Volkswagen Auto Group (VAG) head units that crash when playing audio.

    Change DPI I use 130 to see more of the map. Lower numbers make the area of the map shown larger but the text will be smaller. The number 0 will restore the default used by your phone, head unit combination.

    On my head unit, using the number 103 will put Android Auto into wide mode with map and media side by side. But it is still only displayed in the left portion of the screen, and much of the text is too small for me to read.

    Remove tap restriction I turn this on, it helps me with my on phone music collection. The head unit works with this off. Some other head units will not update your GPS map position properly with this option on.

    Disable Audio Sink I have this turned off. Turning this on will make your phone use something else for audio. In my case it is the phone's speaker.

    Auto video focus I have this turned on. This option tells my Infotainment system to switch to Android Auto when AAWireless connects. I don't have to navigate through the screens to get Android Auto up where I can see it.

    Developer Mode I have this turned off. The head unit works with this turned on. An app update will be needed to correct the text. Frankly, I am not sure what is enabled by setting this on, but Emil is sure some of you will know.

    I often use the app with the AAWireless device plugged into a USB A power source, like a power supply or a charging port in your vehicle. The Android Auto traffic going through the device can make app less responsive.

    When an OTA is available, it is better to download the OTA with the AAWireless device powered off and your phone on WiFi. Once the download has completed, turn on AAWireless, link to it again and upload the OTA to the device.

    I use a large microSD card in my phone (Samsung Galaxy S20 FE 5G) to store my music collection. I play the music with Rocket Music Player. Works very well under Android Auto.

    LeRoy
    5
    I think it would be really helpful for a dedicated forum structure for AAW. It should/could be organized by head unit type and cell phone type and then people can see what settings are working and not waste a bunch of time trying random configurations and then eventually getting lost because their troubleshooting skills are not great. It would also be great if the software came with preconfigured templates you can use by telling it what type of vehicle you have and what cellphone you have, I am sure that would be a ton of work but it would make for a vastly improved user experience for the masses.
    5
    New version of the AAWireless config app in the Beta channel. 1.8.1

    Fixes a problem found with the new Start / Stop feature. There is still a problem when you turn the Start / Stop setting off. You will need to cycle the USB power on the device for it to take effect. Future firmware for the AAWireless device will be needed to address that problem.

    So if you have a vehicle that leaves the USB power on after you turn off the ignition, give the 1.8.1 Beta a try.

    LeRoy
    4
    For those of you using the AAWireless Config app Beta 1.8.0. The new Start / Stop option will trigger a white led when the device is waiting for the vehicle bluetooth to connect to your phone.

    Right now with firmware 1.2.x the white LED is solid, in the near future firmware 1.3.0 and onward it will be flashing white.

    When you see the white LED, the device is powered, but the Wireless Android Auto protocol is disabled. When your phone connects to the vehicle bluetooth, the Wireless Android Auto protocol is enabled. The effect is to allow normal connection to other Wi-Fi networks whenever the Wireless Android Auto protocol is disabled.

    Whenever your USB port is powered, the AAWireless device will be powered up. So if your USB port is powered all the time, you should probably unplug the AAWireless device when get on the ship for your world cruise. Although the battery drain of the powered AAWireless device will be very small, extended periods of time may drain your battery enough that you will notice. ( My KILL A WATT EZ cannot measure the combination of a USB charger with the AAWireless device in Start / Stop standby. The combined wattage is too low to register for that instrument. )

    The Beta testers have identified a problem with Start / Stop. There will be another version coming.

    LeRoy
    4
    Here are the LED codes for OTA firmware 1.3.0. Added Blinking White to the list

    Solid Green, the device is booting, should complete in under 12 seconds. Both the Bluetooth and WiFi are not active until after the boot is completed.

    Blinking Green, the device has activated Bluetooth and is waiting for a WiFi connection from your phone. You will only be able to pair while under blinking green.

    Blinking White, the device has completed boot and is waiting for the Head Unit Bluetooth to connect with your phone. The device will not take over the Wi-Fi on your phone while it is blinking white. You will be able to connect your phone to any other Wi-Fi network. Use the Start / Stop Option to enable this mode.

    Blinking Blue, the device has fully connected with your phone and is attempting to connect with your head unit via USB.

    Solid Blue, the device is full connected with your phone and the head unit. The first time you connect you may need to set some Android Auto permissions and some head units may also produce prompts for you to answer.

    Solid Yellow, the device is loading an OTA update into memory.

    Red, an error has occurred, the device will attempt recovery after a timeout.

    None / Black The LED will not be active when you first apply power for a very brief time. And the LED will not be active at all when the device is ready to be flashed from your computer. It will remain inactive until the flash program completes loading the firmware and reboots the device.

    The general rule is that blinking means the device is waiting for something to happen. Solid means the device is engaged in some type of work.

    LeRoy
  • 25
    This thread is dedicated for AAWireless users.

    AAWireless is a device which allows you to transform your existing wired Android Auto compatible unit into a Wireless Android Auto unit.

    General chat, experience sharing and community support should be expected as well as support from the developers of the product: @Snirpo and myself.
    15
    We fixed the "VW Headunit crashing on skipping tracks" issue now completely. Confirmed it's a bug on the HU side, latency makes it worse. We will probably push a new firmware by the end of this week.
    I will also submit a bug report to Google, cause they can fix/workaround this issue as well for cabled users.
    9
    @jahandy

    Here are the LED codes.

    Solid Green, the device is booting, should complete in under 12 seconds. Both the Bluetooth and WiFi are not active until after the boot is completed.

    Blinking Green, the device has activated Bluetooth and is waiting for a WiFi connection from your phone. You will only be able to pair while under blinking green.

    Blinking Blue, the device has fully connected with your phone and is attempting to connect with your head unit via USB.

    Solid Blue, the device is full connected with your phone and the head unit. The first time you connect you may need to set some Android Auto permissions and some head units may also produce prompts for you to answer.

    Red, an error has occurred, the device will attempt recovery after a timeout.

    LeRoy
    7
    Hey all, and thanks so much to the developers for bringing this great product to life!

    I just wanted to share my experience with the setup process because I had a rocky start and maybe someone with similar issues finds it useful. Please don't yell at me if most of it has already been posted! ;-)

    Car: Nissan Leaf MY19 / Phone: Samsung Galaxy S9 (One UI 2.5, Android 10)

    Open Android Auto for phones and activate wireless mode:
    The basic prerequisite is to enable wireless projection in the Android Auto for phones app. So if there's no Android Auto app in your app drawer, first download the app, and enable wireless projection in its settings. If that setting isn't there, activate developer mode by tapping the version number at the bottom of the settings several times. In the menu on the upper right enter developer settings and activate the setting for enabling wireless projection. Return to the main settings, find the new wireless setting and activate it, too.

    Connect to AAWireless via Bluetooth and starting of Android Auto:
    First of, I would have liked a little more insight on how to connect to what exactly.

    The AAWireless config app is actually not necessary but provides some troubleshooting options in case the setup is unsuccessful and offers some tweaks for advanced users.

    The regular process as I understand is the following:
    1) Turn ignition on and connect AAWireless via cable to the car's USB port. Nothing happens on the car's head unit just yet.
    2) Connect the phone to AAWireless via Bluetooth.
    3) The phone should receive WiFi-Settings from AAWireless via Bluetooth and then connect to AAWireless' WiFi without any user input.
    4) Android Auto starts automatically on the phone and becomes available on the car's head unit.
    Now the phone stays connected via both Bluetooth and WiFi.
    From now on whenever the phone is near the AAWireless device it will connect to it automatically and thus activate Android Auto on the phone and the car's head unit.

    Throughout my whole setup process I encountered all kinds of LED states: green, red, blue, blinking steadily, constantly lit and whatnot. Frankly I just ignored the LED because without an official legend I find if futile to try and decipher the meanings.

    No Android Auto after successful Bluetooth connection:
    My first problem arose right after initiating the Bluetooth connection to AAWireless on my phone. Nothing would happen afterwards.
    So I followed the steps outlined in the FAQ:
    When connected via Bluetooth to AAWireless I opened the AAWireless config app which would take a while to read the settings from the device and sometimes nothing would happen. I unplugged, replugged, disconnected, unpaired and re-paired A LOT.

    Finally, I got a working connection by selecting Direct for USB mode and enabling Passthrough mode. After saving and re-plugging the device Android Auto would magically appear on my phone and car.
    But - just once.

    Stops working:

    Now, after having had one successful connection I wanted to test if it works reliably. Thus I unplugged AAWireless for a minute and plugged it back in. The result: again my phone connected via Bluetooth and nothing else happened.
    I tried all kinds of stuff, like deleting the app caches, uninstalling Android Auto, unpairing etc. I got it working again from time to time but not reliably.
    To add insult to injury my husband's OnePlus 3T started Android Auto effortlessly right. away. without. any. hassles. whatsoever. over. and. over.

    So I factory reset my phone!
    I know, no one wants to hear this but it actually helped. I've never done a reset in the 2.5 years I've had my phone and I dreaded it. But after all this time, 200 apps, 2 major Android updates and a lot of general tinkering I didn't have to coerce myself too hard. After resetting the S9 I could easily initiate the connection via Bluetooth, it would connect to WiFi and start Android Auto. Over and over.

    No internet

    Then I ran into the next major problem: the dreaded no internet because WiFi problem. My phone is set to connect to the internet via the cell network in case WiFi is unstable. I also tried the setting in the phone's developer options which keeps the phone connected to mobile data all the time. Both settings didn't change the fact that even though the status bar showed a 4G icon, Google couldn't be reached in Android Auto.

    The solution is another brain melter for me. When the phone informed me that WiFi data was unstable I must instinctively have tapped 'Keep WiFi'. This actually kills mobile data and forces all data requests through the non working WiFi connection! As stupid as it sounds: just ignoring the popup keeps both mobile data and WiFi active while choosing an option will sabotage wireless Android Auto. This is clearly Google's fault because they obviously forgot to code an exception for Android Auto to keep it from throwing this error.

    Now AAWireless seems to work as it should.

    One more thing I had to learn even before going wireless: Samsung's power saving settings can mess up your phone's GPS in Android Auto. It took me a while to figure out that one thing power saver does is it stops the GPS when the phone screen is off. It makes no exception for Android Auto. Thus I could use Maps and Waze on the phone but as soon as I was on Android Auto it would just show me an approximate location and 'jump' from street to street as it only used cell tower data for positioning.

    So, good luck to those who face issues, enjoy your wireless Android Auto to those who got it and got it working and a huge thanks to the team who made AAWireless!
    7
    Some edited thoughts on my settings with AAWireless Config 1.8.2 that may help someone. This version of the app works best with OTA firmware version 1.3.0. Which should be available soon for all versions of the AAWireless device. It may also be used with OTA firmware 1.2.x, but we have identified some problems that are fixed in OTA firmware 1.3.0. Update when you get the chance.

    The 1.8.x version of the app introduces the Start / Stop option.

    I have a 10.25 Hyundai head unit. I think that the Wireless Projection function of this unit is the same for KIA and Genesis 10.25 inch head units. This head unit first appeared in 2019 Korean model years and is very flexible when used with with AAWireless.

    Here are the settings in the AAWireless Connect app version 1.8.2 that I use and what also works with my head unit.

    USB Mode I use MTP, but Direct works as well. The head unit responds a bit faster with MTP.

    Passthrough I have it turned off. The head unit works with Passthrough turned on, but DPI, Remove tap restriction, Disable Audio Sink, AutoVideo Focus and Developer mode cannot be processed by AAWireless when on. When on the exact encrypted data conversation is transmitted between your phone and the head unit. When off, AAWireless joins the conversation to inject those Experimental Features.

    Force 2.4Ghz I have it turned off. The 5Ghz channel used is 40. This feature will turn off 5Ghz Wi-Fi in favor of 2.4Ghz Wi-Fi on channel 1.

    Start / Stop I have this turned on. What it is designed for is those vehicles that keep the USB port powered on while the ignition is off. My Hyundai keeps the USB port powered for several minutes after I turn off the car and leave vehicle. With this turned off, my phone won't connect to my home network.

    WiFi connect timeout I now leave this at the default 20 seconds. For a couple of months after the initial conversion to Android 11, my Samsung Galaxy S20 FE 5G phone would not connect to AAWireless on the first try. It would always connect on the second try. Samsung fixed their problem with a subsequent update. But while this was a problem, reducing the WiFi connect timeout to 5 seconds really helped.

    Adjust audio timestamp I have it turned off. The head unit also works with it turned on. Turn this on if you notice things out of sync. With OTA firmware 1.3.0, enabling this option will help with certain Volkswagen Auto Group (VAG) head units that crash when playing audio.

    Change DPI I use 130 to see more of the map. Lower numbers make the area of the map shown larger but the text will be smaller. The number 0 will restore the default used by your phone, head unit combination.

    On my head unit, using the number 103 will put Android Auto into wide mode with map and media side by side. But it is still only displayed in the left portion of the screen, and much of the text is too small for me to read.

    Remove tap restriction I turn this on, it helps me with my on phone music collection. The head unit works with this off. Some other head units will not update your GPS map position properly with this option on.

    Disable Audio Sink I have this turned off. Turning this on will make your phone use something else for audio. In my case it is the phone's speaker.

    Auto video focus I have this turned on. This option tells my Infotainment system to switch to Android Auto when AAWireless connects. I don't have to navigate through the screens to get Android Auto up where I can see it.

    Developer Mode I have this turned off. The head unit works with this turned on. An app update will be needed to correct the text. Frankly, I am not sure what is enabled by setting this on, but Emil is sure some of you will know.

    I often use the app with the AAWireless device plugged into a USB A power source, like a power supply or a charging port in your vehicle. The Android Auto traffic going through the device can make app less responsive.

    When an OTA is available, it is better to download the OTA with the AAWireless device powered off and your phone on WiFi. Once the download has completed, turn on AAWireless, link to it again and upload the OTA to the device.

    I use a large microSD card in my phone (Samsung Galaxy S20 FE 5G) to store my music collection. I play the music with Rocket Music Player. Works very well under Android Auto.

    LeRoy
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone