AAWireless - General discussion and support

Search This thread

Synman

Recognized Developer
We are working as fast as possible to fix all issues. I just pushed a new app (1.8.0) with the functionality you are describing: Start / stop AA based on the BT handsfree of the car is connected. I'm not terribly convinced yet this is going to work correctly on all phones though, so I pushed it to the beta channel first for some feedback.
Also the initial setup bug you are describing should've been fixed. This happened because the list of devices was based on the bluetooth devices of the phone. However if bluetooth is off, the list of devices is empty. And if the device list is empty, it starts the setup. We are now saving a copy of the device list in our own local database.

Ah, that'll do it! As I have been running my phone primarily with BT disabled the past couple weeks, particularly when I forget to unplug the AAW from my car. Funny thing (as I know there were initial Wi-Fi signal strength issues pre-production) I can be sitting in my living room and my phone will spontaneously start trying to connect to my car, hours, heck even a day, after getting out of my car. There is certainly no lack of signal strength in the production version of AAW :)

Is there a an open beta link / invitation you can share? I just checked the play store and it doesn't appear a public beta group is configured for the app.
 

psmedley

Senior Member
May 5, 2011
110
24
Adelaide
Just an update on status on my Holden vehicles:
Holden MY18 ZB Commodore - device id sKKQxr0e - I'm not quite sure how, but I got the AAWireless connected today a couple of times (same cable as I've used previously). The one thing I tried today was to force 2.4 GHz wireless - and this seemed to help. I was able to play audio and see the Android Auto on the car screen wirelessly.

Holden MY20 BK Astra - device id rT77pJHT - I was able to get solid blue on this yesterday after disconnecting my work iPhone from the car bluetooth (the car supports multiple BT connections) - when connecting the AAWireless - the car kept asking if I wanted to disconnect the iphone to allow AAWireless to connect. Unfortunately, with solid blue, the car doesn't 'see' the phone but in the media section of the car infotainment, AAWireless is an option, and I'm able to play audio via Android Auto, just not see the car projection. A couple of photos of this are at https://photos.app.goo.gl/jEQRBF8RUkv3pr9N8 and https://photos.app.goo.gl/sdkifqDPYasobUXE9
 

psmedley

Senior Member
May 5, 2011
110
24
Adelaide
Just an update on status on my Holden vehicles:
Holden MY18 ZB Commodore - device id sKKQxr0e - I'm not quite sure how, but I got the AAWireless connected today a couple of times (same cable as I've used previously). The one thing I tried today was to force 2.4 GHz wireless - and this seemed to help. I was able to play audio and see the Android Auto on the car screen wirelessly.

Holden MY20 BK Astra - device id rT77pJHT - I was able to get solid blue on this yesterday after disconnecting my work iPhone from the car bluetooth (the car supports multiple BT connections) - when connecting the AAWireless - the car kept asking if I wanted to disconnect the iphone to allow AAWireless to connect. Unfortunately, with solid blue, the car doesn't 'see' the phone but in the media section of the car infotainment, AAWireless is an option, and I'm able to play audio via Android Auto, just not see the car projection. A couple of photos of this are at https://photos.app.goo.gl/jEQRBF8RUkv3pr9N8 and https://photos.app.goo.gl/sdkifqDPYasobUXE9
Interestingly, I find it hard to reconnect on the Commodore - it's certainly not connecting first time every time....
 

cronosmachine

Senior Member
Sep 16, 2010
414
419
I have weird issue with the cable.

Here the condition:
1. Two cars, Hyundai IONIQ Hybrid and Hyundai Elantra Sport.
2. One AA Wireless dongle of course.
3. Magnetic Wireless Type C Plug cable.
(https://shopee.com.my/product/303363956/5252992664)
4. Short Type C cable or Type C cable provided are same.
5. USB Pendrive, contain video and song.

- Hyundai IONIQ Hybrid head unit it's MOBIS part.
- Hyundai Elantra Sport head unit it's Motrex (http://www.motrex.co.kr/en)

Here the scenario:
1. Short Type C cable and Magnetic Wireless Type C Plug cable work on IONIQ with AA Wireless, USB Pendrive.
2. Short Type C cable and Magnetic Wireless Type C Plug cable work on Elantra Sport with USB Pendrive, not AA Wireless.
3. Magnetic Wireless Type C plug cable working on Elantra sport direct wired connect with my phone and android auto launched and working.

I not sure why the Magnetic Wireless Type C Plug not working with my Elantra Sport while it's working on My IONIQ, but if I changed the cable to original or shorten one it's working and same cable also working on my IONIQ.

I used method this video for xiaomi phone, but always need to set mobile data every time connected to AA Wireless.
 
Last edited:

Snirpo

Senior Member
Jan 23, 2007
69
60
Ah, that'll do it! As I have been running my phone primarily with BT disabled the past couple weeks, particularly when I forget to unplug the AAW from my car. Funny thing (as I know there were initial Wi-Fi signal strength issues pre-production) I can be sitting in my living room and my phone will spontaneously start trying to connect to my car, hours, heck even a day, after getting out of my car. There is certainly no lack of signal strength in the production version of AAW :)

Is there a an open beta link / invitation you can share? I just checked the play store and it doesn't appear a public beta group is configured for the app.
It's in open beta, you should be able to switch to the beta channel. Rollout always takes a while.
 

Snirpo

Senior Member
Jan 23, 2007
69
60
I have weird issue with the cable.

Here the condition:
1. Two cars, Hyundai IONIQ Hybrid and Hyundai Elantra Sport.
2. One AA Wireless dongle of course.
3. Magnetic Wireless Type C Plug cable.
(https://shopee.com.my/product/303363956/5252992664)
4. Short Type C cable or Type C cable provided are same.
5. USB Pendrive, contain video and song.

- Hyundai IONIQ Hybrid head unit it's MOBIS part.
- Hyundai Elantra Sport head unit it's Motrex (http://www.motrex.co.kr/en)

Here the scenario:
1. Short Type C cable and Magnetic Wireless Type C Plug cable work on IONIQ with AA Wireless, USB Pendrive.
2. Short Type C cable and Magnetic Wireless Type C Plug cable work on Elantra Sport with USB Pendrive, not AA Wireless.

I not sure why the Magnetic Wireless Type C Plug not working with my Elantra Sport while it's working on My IONIQ, but if I changed the cable to original or shorten one it's working and same cable also working on my IONIQ.

I used method this video for xiaomi phone, but always need to set mobile data every time connected to AA Wireless.
Yeah these cable issues... It's driving me insane really. I really like to fix that somehow. However since this has always been a problem with AA, I don't see it happening we can ever fix it completely.
 

cronosmachine

Senior Member
Sep 16, 2010
414
419
Yeah these cable issues... It's driving me insane really. I really like to fix that somehow. However since this has always been a problem with AA, I don't see it happening we can ever fix it completely.
The same cable magnetic Wireless Type C cable working if I use my phone directly. Android auto launch and working. But with aa wireless can not. Even just now i cut the magnetic Wireless Type C cable and make it short, still same.
 

HansWursT619

Senior Member
Jan 11, 2011
101
16
How can I access the Settings in the Companion App?
My AA connection works fine, but the Settings are always greyed out.

Edit: Ok I used a powerbank to power the AAWireless and change the USB Mode to "Direct".
Now the settings work when powered through the car.

Is there a "best" USB Mode or should I just stick with Direct"?
 
Last edited:

Snirpo

Senior Member
Jan 23, 2007
69
60
How can I access the Settings in the Companion App?
My AA connection works fine, but the Settings are always greyed out.

Edit: Ok I used a powerbank to power the AAWireless and change the USB Mode to "Direct".
Now the settings work when powered through the car.

Is there a "best" USB Mode or should I just stick with Direct"?
If it works, then you don't have to change it. Default (MTP) works on 90 percent of the head units.
 
Last edited:
May 15, 2021
7
1
Hello guys!

My Configuration:
Seat Ibiza 2019
Samsung Galaxy S20 5G (Android 11)
Playstore AAWireless Config App 1.7.1
AA Wirelesss (updated to 1.2.3. from 1.1.0 after receiving 2 weeks ago) and a another, short IF-certified USB cable

pic01.jpg



Everything works as far as "perfect" after activate "Passthrough".

Before i had the problem, that i can't hear every half of an hour/hour in Spotify the next track in a playlist/album (never at the END or IN a track!!!) and after pressing a button on my car display the headunit crashed. After crashing (takes 20 Seconds for reboot and so on) it works fine for the next few hours. I readed this error so many times ago in this thread for this headunit.
After changing it to "passthrough," this error seems to be gone. BUT as far as I use another BT-connection outside of my car (i erased every BT connection before 2 weeks after installing AAW) this error comes again and very often as long as i don't erasing every other BTs in my Android!

Do you have an actually FW for my car for testing if it is better after updating?
 

Attachments

  • pic01.jpg
    pic01.jpg
    253.3 KB · Views: 21
Last edited:

tallleroy

Senior Member
  • Nov 20, 2015
    65
    80
    Atlanta, Georgia
    Interestingly, I find it hard to reconnect on the Commodore - it's certainly not connecting first time every time....
    You might try shortening the Wifi connect timeout in the AAWireless config app. At one time, my Samsung phone benefited from a shortened timeout of 500ms. It shortened the connect time when the connection failed the first time.

    Samsung has since updated my phone and it always connects first time now, so the default of 2000ms is fine for me.

    LeRoy
     
    • Like
    Reactions: osm0sis

    Genebaby

    Senior Member
    Dec 11, 2013
    649
    78
    Update on driving the Polo with the beta VAG FW. So running in Passthrough with 2.4ghz Force mode makes the map work well and stopped the audio issue I was having with my old settings.

    The audio can still skip, randomly a little, but maybe not as much, but here are two areas that I drive near my house and it WILL skip just about all the time. One is a street very near me, and another an open area near me that I don't visit every trip, but the street near me is on my way home and every time in a certain spot it will glitch, sometimes less than others.

    Phone calls I have realised seem to be an issue. I got one and it failed, they never heard a ring, the phone said I was not available. My daughter was in the car so I asked her to call me and it worked fine.

    Yesterday again, first call, it died. I tried to call back using the headunit phone software, no good, then this friend called back and we could talk, so it seems the first call has problems?

    I've never used Passthrough in my cars until this FW but I do have to take the GTI to VW tomorrow so I'll use Passthrough on that with stable 1.2 FW on the way there, in 2.4ghz mode and observe, but I probably won't get a phone call.

    The Polo headunit is a Delphi and the GTI a Harmin.

    I'm driving the Polo soon so I'll send a bug report, maybe that will help?
     

    bigcid10

    Senior Member
    Dec 17, 2011
    508
    73
    West Palm Beach
    I posted this in the AA reddit and the google AA forum as I lost all my brains on this
    and it used to work fine

    when I start a voice dial on my pioneer HU(Pioneer AVH-4200nex) ,it will dial the other phone

    but I can't hear the person pick up or the HU in my car dial

    but if I change the audio source from the dialing app in AA on my radio

    to say 'speakerphone(note 20) or phone speaker " it works

    I remember when I installed AA on my phone ,it asked for bluetooth permissions

    but it went past the screen without giving me a chance to allow it

    Is the a way to manually enable it as it doesn't give me the option in AA app properties ?

    Thank you

    oh,I have AA wireless box ,but it was happening with a cable also
    Thanks again

    @Emil Borconi
    could you please take a look at this and give me some ideas ?\Thank you
     

    Synman

    Recognized Developer
    It's in open beta, you should be able to switch to the beta channel. Rollout always takes a while.

    figured it out and had the beta version loaded in no time at all.

    Selected SONATA from the list and tried it out. A couple minutes after turning off the ignition in my car (and exiting it) my Wi-Fi connection fell back to home Wi-Fi and it's sticking to it without issue so far.

    Nice!
     

    muckdawg

    New member
    Jul 9, 2007
    1
    1
    I posted this in the AA reddit and the google AA forum as I lost all my brains on this
    and it used to work fine

    when I start a voice dial on my pioneer HU(Pioneer AVH-4200nex) ,it will dial the other phone

    but I can't hear the person pick up or the HU in my car dial

    but if I change the audio source from the dialing app in AA on my radio

    to say 'speakerphone(note 20) or phone speaker " it works

    I remember when I installed AA on my phone ,it asked for bluetooth permissions

    but it went past the screen without giving me a chance to allow it

    Is the a way to manually enable it as it doesn't give me the option in AA app properties ?

    Thank you

    oh,I have AA wireless box ,but it was happening with a cable also
    Thanks again

    @Emil Borconi
    could you please take a look at this and give me some ideas ?\Thank you
    I had a similar disconnects when using the AAW box when making or receiving calls. The cause was my phone had wifi calling enabled and the phone was trying to use the AAW wifi for the call. Disabling wifi calling fixed the problem for me.
     
    • Like
    Reactions: bigcid10

    psmedley

    Senior Member
    May 5, 2011
    110
    24
    Adelaide
    You might try shortening the Wifi connect timeout in the AAWireless config app. At one time, my Samsung phone benefited from a shortened timeout of 500ms. It shortened the connect time when the connection failed the first time.

    Samsung has since updated my phone and it always connects first time now, so the default of 2000ms is fine for me.

    LeRoy
    I'll try this - I had a 50% strike rate today. When we left the house this morning, it connected straight away - when we left to come home there was no connection (flashing blue light).

    Cheers,

    Paul
     

    FrankieG64

    New member
    Mar 26, 2020
    4
    0
    Loaded the Beta app yesterday and went out to run some errands. App worked perfectly. Each time I stopped and left my truck the AAWireless wifi disconnected and then reconnected when I returned. When I went to a friend's house it connected to their wifi immediately. Same occurred when I returned home. Phone no connects and disconnects for the 2 hours or so that the USB remains powered. Great solution, Thank You.
    Phone: Samsung S10
    Vehicle: 2020 Ram 1500 12" Uconnect
     

    tallleroy

    Senior Member
  • Nov 20, 2015
    65
    80
    Atlanta, Georgia
    I'll try this - I had a 50% strike rate today. When we left the house this morning, it connected straight away - when we left to come home there was no connection (flashing blue light).

    Cheers,

    Paul
    Sorry, I did not understand your first post correctly @psmedley. Flashing blue LED indicates a completed connection between the phone and the device, and no connection from the device to the head unit over USB.

    The only solution with that condition is to try the four different USB mode options in the AAWireless config app and the Passthrough option.

    There may be one of those settings that will work for you.

    I did not have much luck with my friend's high end Buick SUV. The head unit saw and registered the device as Android Auto, but would not fully connect and display Android Auto.

    I found it interesting that my friend also had a base model Chevrolet mid size pickup with the most basic GM radio and it worked with AAWireless immediately.

    The developers are aware of the problem and will be working toward a better solution. They have overcome many problems with software refinement so far. I think they will be able to solve this one too.

    LeRoy
     

    bigcid10

    Senior Member
    Dec 17, 2011
    508
    73
    West Palm Beach
    I had a similar disconnects when using the AAW box when making or receiving calls. The cause was my phone had wifi calling enabled and the phone was trying to use the AAW wifi for the call. Disabling wifi calling fixed the problem for me.
    I just looked at my phone and the wifi calling was disabled ,thank you though
    funny thing is once out of about 25 times it will work but no any consecutive 2 times,lol
     

    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
      Well bad news, I tried whole morning fixing the WiFi not disconnecting issue on the phone side for the start / stop feature. Something has changed on the Android Auto side which makes AA keep a very tight hold on the WiFi network, it's impossible to disconnect it.
      There is one hack I can apply, which is like we do with OTA, take over the network, and then immediately disconnect it. But I'm pretty sure this won't work correctly on some phones. @tallleroy tested it and it wouldn't work correctly on his Samsung. On my OnePlus it did work fine, but to be honest everything you throw at the OnePlus just works.
      2
      So at least problem is not with my phone :)
      And seems that unit itself is not faulty..or we both have faulty ones...
      So seems like some sw issue or total incompatibility with our car ((
      Damn, i hoped so much that i would get rid of those cables
      If passthrough mode also gives the same issue it has most probably something to to with latency introduced / jitter by WiFi and the car not being able to handle this.
      These things are solved by trial and erroring until the source of the issue is found.
      The VW bug was the same thing. Its litterally a bug in the HU. We have one tester who also had the HU crash with the phone connected wired. Latency apparently worsened the problem. Now with our workaround, the HU does not crash anymore.
      I'm pretty sure we can fix (or work around) these issues, but we have to find out why these things happen. It costs time sadly :(
      Luckily we have a great community of people who can help us fix it :)
      if you want to help more directly you can always join us in Slack: https://join.slack.com/t/aawireless/shared_invite/zt-nu6jokgj-Y~FxA6aegEZMi98aISYEjA
    • 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