AAWireless - General discussion and support

Search This thread

Genebaby

Senior Member
Dec 11, 2013
649
78
I got the email update so I spent some time in the Polo and did the 1.30 update, taking me off the experimental VAG FW, which my headunit didn't like too much but I was getting by.

I re-enabled Direct mode but left Force 2.4ghz on, and the Google Assistant didn't take over the audio controls anymore and seemed more responsive again. I will test it further.

I had a look at the start/stop feature as the VAG cars don't power it up constantly, but at least for a few minutes and when I make a call after parking the audio is routed strangely, so I'd like to try this feature.

However, when I turn it on I can't get AA to display. After a while, and unplugging etc I got the settings to show and turned it off and was able to get AA running. Checked again when I got to my destination, same thing. I sent a bug report through.
 

tallleroy

Senior Member
  • Nov 20, 2015
    65
    80
    Atlanta, Georgia
    When you enable the Start / Stop feature, be certain to also select the name of your vehicle Bluetooth. The paired Bluetooth devices will be displayed with the Start / Stop enable slider. Your phone will wait for the vehicle Bluetooth to connect before activating Android Auto on the AAWireless device.

    The waiting is done using events on the phone, your phone battery is conserved in this way.

    LeRoy
     
    • Like
    Reactions: osm0sis

    Genebaby

    Senior Member
    Dec 11, 2013
    649
    78
    When you enable the Start / Stop feature, be certain to also select the name of your vehicle Bluetooth. The paired Bluetooth devices will be displayed with the Start / Stop enable slider. Your phone will wait for the vehicle Bluetooth to connect before activating Android Auto on the AAWireless device.

    The waiting is done using events on the phone, your phone battery is conserved in this way.

    LeRoy
    So it might be a little slower than without this feature enabled? First time using it today and it really only needs to be an auto stop feature, unless it's there also for cars having trouble starting? If so it would be handy to split the functions so you can have only auto stop.

    That said, I was testing again and with it enabled my Delphi VAG headunit would not show AA, then after seeing your post I went into the BT settings and touched the AAW unit I was using, I think, and AA began to be displayed.

    I tried a power cycle and waited for the light to turn off and it seemed to work automatically the next time but a bit slower.

    Next I left the car for at least a half hour and it was no longer working, red light all the time, needed to kill USB power to quickly get into settings to disable start/stop and all is pretty good otherwise on the stable 1.30.

    Music playback seems to be better in terms of skipping so far.

    I'll test out the Harmin headunit in the GTI when I can.
     
    • Like
    Reactions: Cavin8

    Snirpo

    Senior Member
    Jan 23, 2007
    69
    60
    Any timeline on a fix for Nissan? I've been in contact with support for over a month now, sent logs, tried different cables, all the settings...nothing.
    It's next on my list. We have a tester which also has issues with his Nissan, so we can reproduce. This is a very low level issue, we don't know yet how to fix it. I bought an USB debugger to check what is happening. I can't really give a timeline. Can take a week, can take a month, or maybe we can't fix it with software at all and have to look on the hardware side.
     
    • Like
    Reactions: osm0sis

    vizzze

    Senior Member
    Jan 16, 2011
    112
    26
    I had a look at the start/stop feature as the VAG cars don't power it up constantly, but at least for a few minutes and when I make a call after parking the audio is routed strangely, so I'd like to try this feature.
    I can confirm this, had the same experience. When making a phone call in the car, when you keep the conversation and remove the car key, the audio goes from BT of the headunit to the BT of aawireless and you loose the communication (not the call itself but the audio), but i was able to select the phone speaker on the Phone and keep talking on the phone.
     
    • Like
    Reactions: TheUntouchable

    andreiav

    Senior Member
  • Jun 4, 2014
    219
    115
    Brasov
    Do owners of VAG cars with Technisat headunits that reboot need to activate any setting in the new FW version? I didn't get a change to test it yet. Do we need to activate "Adjust audio timestamp"? Or is this no longer necessary?
     

    Marshy33

    Senior Member
    Nov 28, 2015
    133
    36
    Do owners of VAG cars with Technisat headunits that reboot need to activate any setting in the new FW version? I didn't get a change to test it yet. Do we need to activate "Adjust audio timestamp"? Or is this no longer necessary?

    It needs to be activated yes. But it will be automatically turned on if the AAwireless unit recognises you have technisat mib2 after updating to 1.3.0.

    I believe the wording of adjust audio timestamp will also be updated to something more specific in a later release, like VW crash fix.
     

    wainy54

    Member
    Dec 11, 2010
    5
    3
    The start/stop feature is a welcome improvement with my A5. Whilst it doesn't leave the USB port powered on permanently, it leaves it on for a couple of minutes.

    With the feature enabled AA stops when I turn off the ignition and open the door. This is good because it allows me to open things like Google maps on the phone.

    However, the phone still remains attached to the AA wi-fi and doesn't rejoin my home WiFi until the AAwireless unit loses power (a couple of minutes).

    I'm not sure if this is intentional/expected behaviour?

    For my use case, it would be nice if AAwireless sent a wi-fi deauth or something after AA stops (if that didn't introduce some other issue).

    It's a really minor inconvenience, I'm more than happy with the product and the continued development.
     
    • Like
    Reactions: osm0sis

    Marcolino974

    New member
    May 19, 2021
    1
    0
    Ciao, ieri è arrivato il dispositivo, ho scaricato l'app e sul display dell'auto si accende Android Auto (peugeot 5008). Ora ho solo un problema, wifi connesso, ma internet non disponibile. Come posso risolvere? Grazie
     

    twingo_man

    Senior Member
    Jan 13, 2007
    277
    17
    Toulouse
    Hello,
    I received mine today
    It's working fine in my Renault clio 4 with rlink

    But in my Renault clio 5 (my main car) with easylink, it doesn't work
    The led blinks sometimes in blue, sometimes in green. And I have this on the phone: Screenshot_2021-05-19-11-53-00-441_com.miui.home.jpg
    I tried all the usb mode with or without passthroug activated, but nothing changes...
     

    Limpperi

    Senior Member
  • Feb 4, 2011
    135
    26
    Vantaa
    OnePlus 3T
    OnePlus 7 Pro
    I just recieved my unit, i had some troubles connection to the car. It is a Citroen C3 from 2020.
    I just found that i have to delete known connections in android auto.
    If i leave car known in android auto, it will connect phone and sound is transmitted from phone to car, but there is no picture.
    If i delete car from android auto, and accept connection again, i get display and sound.

    Anybody know what to do ?

    I tried the stop/start function, but i dont know how to use it, how to active handsfree in citroen c3 ??
    You have to enable "request video focus on startup" from android auto developer settings. My C3 works best with direct usb mode. Returning back to android auto via the soft buttons and steering wheel controls a are known bug
     

    rd-Target

    Senior Member
    Mar 17, 2008
    123
    30
    Næstved
    I received my unit today. First setup went smooth and it connects just fine, even when leaving and coming back to the car.
    Went for a short drive (20 minutes), and the head unit rebooted a couple of times. After coming home I did an OTA (from 1.2.0 to 1.3.0), and that hopefully fixed the problem.
    Phone: Xiaomi Mi 10 w. Android 11 (Xiaomi.eu)
    Car: 2020 Skoda Superb 3V
    SW Train: MST2_EU_SK_ZR_P0478T

    I recon it's the latest SW train for my car, but I'm not sure?

    In the companion app I've configured the following; USB Mode = Direct, DPI = 110. Everything else is standard.
     

    tallleroy

    Senior Member
  • Nov 20, 2015
    65
    80
    Atlanta, Georgia
    The start/stop feature is a welcome improvement with my A5. Whilst it doesn't leave the USB port powered on permanently, it leaves it on for a couple of minutes.

    With the feature enabled AA stops when I turn off the ignition and open the door. This is good because it allows me to open things like Google maps on the phone.

    However, the phone still remains attached to the AA wi-fi and doesn't rejoin my home WiFi until the AAwireless unit loses power (a couple of minutes).

    I'm not sure if this is intentional/expected behaviour?

    For my use case, it would be nice if AAwireless sent a wi-fi deauth or something after AA stops (if that didn't introduce some other issue).

    It's a really minor inconvenience, I'm more than happy with the product and the continued development.
    You may have entered a password for the AAWireless WiFi network at one time. Check your WiFi settings and forget the AAWireless network. It should return to your home network after removing the AAWireless entry from the list of normal networks.
     
    • Like
    Reactions: osm0sis

    Top Liked Posts

    • There are no posts matching your filters.
    • 6
      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.
      3
      Long time lurker here as well. It seems like the Chevy/GM guys are having a lot of problems still? My 2017 Corvette is doing the thing where at best it'll flash blue, my phone will claim it connected to my car, the dongle will show up in the car's AA device list, but won't connect to it or project from it. This happens regardless of settings unfortunately.

      I'm running on 1.3.0 for reference. Phone connects perfectly via USB. Any hints or tips from fellow Chevy people that got it working?
      The developers tell me that version 1.9.1 of the app and firmware version 1.4.0 are working their way out to all users now.

      When the play store updates your app, update the firmware to 1.4.0 with the OTA. Once both are updated, unplug and then plug in the device.

      Using the app, set the USB mode to 'Default'. Your GM, Nissan or Peugeot vehicle should connect to the head unit and display AA just like it did with your phone on a cable.

      The 'Default' mode is set up in a way where the head unit asks specifically for the interfaces provided by the AAWireless device before making a faulty assumption about which modes the device supports.

      It has been predicted that the 'Default' USB mode will work with any head unit in any vehicle that supports cabled Android Auto. If you care to try it once you have the app and the firmware; let us know if it does not work in your car. You may, of course continue to use any USB mode that works for you. The old modes have not changed.

      LeRoy
      3
      Firmware 1.4 was supposed to fix the Nissan problem. USB Mode has to be set to 'Default' in the Settings with the app. Then disconnect and reconnect the device. This method has cured several Nissan models when we were testing it.

      Avoid Start / Stop for now.

      LeRoy
      2
      Geez Louise that timing! I went to work with 1.3.0 being the latest update, read this thread, and updated to 1.4.0 just before leaving work. It hooked up perfectly with default settings.

      Anybody else having trouble on their Chevy (I think I read one guy freaking out in his Camaro a month ago) try it again, I bet it'll work now.
      2
      Hi,

      Is there a changelog somewhere for the AAW updates, by chance?

      Thanks,
      Patrick
    • 26
      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