• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

AAWireless - General discussion and support

Search This thread

janz25

Member
Sep 28, 2006
13
0
Did you enable "Remove tap restriction" ? If so, try disabling it again. You should also try "Force 2.4Ghz" if that has no effect. Enabling "Passthrough" would rule out some things too if both of those don't work.
Thanks. I never enabled the remove tap restriction and oh yes, i set my usb at default. Whilst i did tried the options to enable passthru and also 2.4ghz on fw 1.3, i still experiencing stuttering audio. But, i will try those options again on this firmware.
 
Last edited:

valeri_s_k

Member
Aug 24, 2020
20
1
Bourgas
Hi there,

Noticed several device disconnections when passed same place. Seems something interfere with 5 gHz WIFI.
Fortunately it wasn't a place on my regular driving routes.

So, I am thinking it would be safer when traveling to unknown places, especially if it is a large city and you rely on navi, to force 2.4 gHz for more stable connection.

My question is to those of you, who use 2.4 ghz - is there any interuption/delays in music or navi voice guidance or anythin else that you have noticed.
 

exge

Senior Member
Apr 25, 2010
119
24
unfortunately with the latest versions and updates, now it is very hard to connect to the AAWireless. I need to plug it in and out before i can connect to the BT of the dongle.

Is there a possible way i can revert to 1.2 firmware and corresponding app? That was the last version where everything worked flawlessly. Or perhaps show the debug text so i can try to see whats wrong when reproducing the issue
 
  • Like
Reactions: iTaiwan

tallleroy

Senior Member
Nov 20, 2015
73
101
Atlanta, Georgia
Hi there,

Noticed several device disconnections when passed same place. Seems something interfere with 5 gHz WIFI.
Fortunately it wasn't a place on my regular driving routes.

So, I am thinking it would be safer when traveling to unknown places, especially if it is a large city and you rely on navi, to force 2.4 gHz for more stable connection.

My question is to those of you, who use 2.4 ghz - is there any interuption/delays in music or navi voice guidance or anythin else that you have noticed.
I am using 2.4 ghz all of the time now. A place that I regularly pass has started to interfere with 5 ghz wifi. No downsides that I have noticed.
 
  • Like
Reactions: iTaiwan

tallleroy

Senior Member
Nov 20, 2015
73
101
Atlanta, Georgia
unfortunately with the latest versions and updates, now it is very hard to connect to the AAWireless. I need to plug it in and out before i can connect to the BT of the dongle.

Is there a possible way i can revert to 1.2 firmware and corresponding app? That was the last version where everything worked flawlessly. Or perhaps show the debug text so i can try to see whats wrong when reproducing the issue
If you have Start / Stop enabled, disable it until the next firmware.
 

Rusmash

Member
Feb 8, 2020
6
1
Peugeot 3008 Google pixel 3a. Connection works without any problems. But Google maps announcements and Spotify don't work together. It freezes and autodisplay becomes very slow. I have version 1.4 and have tried all the settings. Got to go back to the cable.
 

Limpperi

Senior Member
Feb 4, 2011
138
27
Vantaa
OnePlus 3T
OnePlus 7 Pro
Peugeot 3008 Google pixel 3a. Connection works without any problems. But Google maps announcements and Spotify don't work together. It freezes and autodisplay becomes very slow. I have version 1.4 and have tried all the settings. Got to go back to the cable.
Do you have integrated navigation in your 3008? If not, you could try to delete all android auto data and resetting the AAW unit. Bosch RCC had problems before but all should be good now in 1.4 along with positive results (me included).

That said, I have not enough knowledge to say anything about the NAC (with integrated navigation) unit, but full reset everywhere could not make any harm.

Edit: tried with my rcc right now, all works as they should. Doublecheck that the usb mode is on "Default". Above mentioned fixes have worked with others running with 3008. If those wont work, im out of ammo. Hope you get it sorted out tho!
 
Last edited:

jackfate

New member
Jun 14, 2021
2
0
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?
 

Limpperi

Senior Member
Feb 4, 2011
138
27
Vantaa
OnePlus 3T
OnePlus 7 Pro
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 data and cache in original android auto app

Edit: made it more cohesive and understandable
 
Last edited:
  • Like
Reactions: jackfate

Rusmash

Member
Feb 8, 2020
6
1
Haben Sie in Ihrem 3008 eine integrierte Navigation? Wenn nicht, können Sie versuchen, alle automatischen Android-Daten zu löschen und die AAW-Einheit zurückzusetzen. Bosch RCC hatte vorher Probleme, aber jetzt sollte in 1.4 alles gut sein, zusammen mit positiven Ergebnissen (mich eingeschlossen).

Über die NAC-Einheit (mit integrierter Navigation) habe ich allerdings nicht genügend Kenntnisse, aber ein kompletter Reset überall kann nicht schaden.

Edit: Habe es gerade mit meinem rcc versucht, alles funktioniert wie es soll. Überprüfen Sie, ob der USB-Modus auf "Standard" steht. Die oben genannten Fixes haben bei anderen mit 3008 funktioniert. Wenn diese nicht funktionieren, habe ich keine Munition mehr. Hoffe du bekommst es in Ordnung gebracht!
Ich habe tatsächlich NAC. Ich habe auch schon zurückgesetzt und USB auf Standard. Wie gesagt, es funktioniert nicht. Aber danke für die Tipps. Ich werde dann warten. Vielleicht gibt es ja irgendwann mal ein Update
 

Genebaby

Senior Member
Dec 11, 2013
680
82
Testing over the weekend for the Assistant voice level seems to point to an issue in the Polo. It happened using the cable and didn't happen in the GTI when I went out in it. Strange.

In a few weeks the Polo will be off the road so I'll be experiencing AAW in the GTI and returning the other unit to my wife's Mitsubishi, we'll see how the newer FW etc goes in that vehicle. It wasn't as good as the VAG cars at the start.

In regards to audio skipping, I have gotten it on 2.4 and 5Ghz, but it does seem less prominent on this Motorola. I will see how things go when I get my Samsung back.
 

mnim85

Member
May 31, 2021
5
1
Anyone else experience non working steering wheel buttons in his/her PSA 2020/2021 (Peugeot, Citroen, Opel/Vauxhall) car?
I'm on firmware 1.4 and using a Google Pixel 4XL. Got the problem since 1.3, passthrough activated. USB Mode "Direct" and "Default" on Firmware 1.4. When I use the "next track" button on my steering wheel, the list of radio stations appear.

Car: Opel Corsa F 2020 without Navigation.
 

Genebaby

Senior Member
Dec 11, 2013
680
82
Testing over the weekend for the Assistant voice level seems to point to an issue in the Polo. It happened using the cable and didn't happen in the GTI when I went out in it. Strange.

In a few weeks the Polo will be off the road so I'll be experiencing AAW in the GTI and returning the other unit to my wife's Mitsubishi, we'll see how the newer FW etc goes in that vehicle. It wasn't as good as the VAG cars at the start.

In regards to audio skipping, I have gotten it on 2.4 and 5Ghz, but it does seem less prominent on this Motorola. I will see how things go when I get my Samsung back.
This morning on the cable the Assistant worked perfectly with the audio, so not sure what's going on with these cars.
 

Limpperi

Senior Member
Feb 4, 2011
138
27
Vantaa
OnePlus 3T
OnePlus 7 Pro
Anyone else experience non working steering wheel buttons in his/her PSA 2020/2021 (Peugeot, Citroen, Opel/Vauxhall) car?
I'm on firmware 1.4 and using a Google Pixel 4XL. Got the problem since 1.3, passthrough activated. USB Mode "Direct" and "Default" on Firmware 1.4. When I use the "next track" button on my steering wheel, the list of radio stations appear.

Car: Opel Corsa F 2020 without Navigation.
1.4 fixed all this for me (citroen 2020) after resetting the aaw and aa app. Usb on default.
 
  • Like
Reactions: mnim85

Top Liked Posts

  • 1
    Yes, I'm running firmware 1.5.0 and companion app 1.9.3

    I've tried passthrough, 2.4Ghz WiFi mode and various USB modes
    USB mode 'Default' is the recommended - and works for my with a MY20 Holden Astra..
  • 14
    Hello. What's new in 1.5?
    A full changelog for each release would really be appreciated :)
    Thanks for all the hard work!
    Yes, I'll write a full changelog next week from 1.0.0 to 1.5.0 and put it on GitHub + add a link in the app.
    8
    @KRGrayson

    The 'new' Default USB Mode is what fixed issues with many GM infotainment systems.

    Instead of presenting what should be the correct USB mode for Android Auto to the Head Unit (direct), or what most phones present as their default mode ( MTP and its variations); Default USB Mode presents a USB Mode that no Head Unit supports. When the Head Unit sees an unsupported USB Mode, USB protocol calls for it to ask the AAWireless device what modes it does support. The Head Unit then selects the correct Android Auto mode and life is good.

    Prior to firmware 1.4.0, some head units (GM was not alone) would not confirm what USB Mode was being presented and begin to communicate in an inappropriate mode for Android Auto.
    7
    @Snirpo is there any source to download older firmware files to downgrade manually for troubleshooting? It would have helped with my last issue after updating to 1.4.

    It would be nice if there were an option in the companion App to choose a specific version.
    Yes, there is: https://drive.google.com/folderview?id=18R-KYbOSt5jBeb3dtqRs-EPrBRaGE9sX

    I did think about adding a downgrade option in the app, but it's a bit tricky. If we do that, we don't only need to test updates from version x to y, but also downgrades all the way back down to 1.0.0. Normally it wouldn't break, but I don't really feel like testing from the newest version to the oldest, to be sure the board doesn't accidentally brick :) It gets a bit too easy to just switch around versions all the time if we provide it via the app. And we don't really want people to use older versions.
    However what I could do is provide an option to switch back to the previous version (which is still on the board actually, cause it has an A/B partition layout).
    6
    Here are the LED codes for OTA firmware 1.5.0. Solid White is now used for Start / Stop standby mode.

    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.

    Solid White, Start / Stop standby mode. The device has completed boot and is waiting for the Head Unit Bluetooth to connect with your phone. When your Head Unit Bluetooth disconnects from your phone, the device will return to Start / Stop standby mode for as long as it is powered. The device will not take over the Wi-Fi on your phone while it is solid 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.

    RIP Blinking White
    The change from Blinking White to Solid White was based on feedback from this forum. Users saw the Blinking White drift to other colors over time. It turns out that the drivers for the RED, GREEN and BLUE LEDs on the device are not coordinated for the blinking feature. Blinking the primary colors is fine, but blinking Yellow, Cyan, Magenta and White will cause drift to other colors.

    LeRoy
  • 27
    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.
    14
    Hello. What's new in 1.5?
    A full changelog for each release would really be appreciated :)
    Thanks for all the hard work!
    Yes, I'll write a full changelog next week from 1.0.0 to 1.5.0 and put it on GitHub + add a link in the app.
    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