AAWireless - General discussion and support

[Snirpo]

These steps worked when connecting for first time in my case, unfortunately. Every subsequent connection it got stuck.
With 1.8 firmware AAW used to work fine without passthrough. Since 2.0.0 the only way to make it work with my headunit is using passthrough.

Do you have a Hyundai / Kia by any chance?

 

[Aberk]

That sounds very odd. Does the device actually not boot anymore in these cases? I mean does the LED stay solid green? If so, it's most likely defective. If not, there's something else going on.

I think the device boots. I can make settings changes using the companion app. My phone appears to think it is connected to AA, but I get device not supported on my truck's screen.

The LEDs vary. I sometimes see it solid green, but usually it blinks blue with 2 quick blue flashes then a delay and 2 more quick blue flashes. This blue flashing sequence just keeps repeating itself.

 

[LKnzw]

Do you have a Hyundai / Kia by any chance?

Peugeot 208 - Device ID JTF9GGyz

 

[Snirpo]

I think the device boots. I can make settings changes using the companion app. My phone appears to think it is connected to AA, but I get device not supported on my truck's screen.

The LEDs vary. I sometimes see it solid green, but usually it blinks blue with 2 quick blue flashes then a delay and 2 more quick blue flashes. This blue flashing sequence just keeps repeating itself.

Aah blue flashing is the HU side not sending the start command. Can you try to switch to MTP usb mode? that will atleast make the "USB device not supported" go away.

 

[worldonfire]

Checked it, definitly seems like the device is fully rebooting. Like in fully going back to solid green, blinking green, blue. Can you confirm this?

Yes, at first led goes off. Then solid green, blinking green. Then blinking blue and solid blue. Sometimes it does not even reach to solid blue and starts over...

Tomorrow i'll check what the leds do with passthrough disabled. If I remember correctly, then it does the same, but I will confirm it just to be sure.

 

[Aberk]

Aah blue flashing is the HU side not sending the start command. Can you try to switch to MTP usb mode? that will atleast make the "USB device not supported" go away.

When I switched to MTP, I didnt get the not supported message. I got no device connected instead. I tried all 3 flavors of MTP with the same results. MTP with force start made the LED green, but the other 2 did the double blue blink I keep seeing.

 

[Marsou77]

Hello!

I have been using AAWireless for almost a year and I am very happy with it, everything working as intended with a Google Pixel 6 & Samsung Galaxy A7 and with a Peugeot 208 I.

Since the introduction of AAWireless 2.0 it is advertised that we can easily switch between many smartphone. But in my experience it is not working for me. I have set the AAWireless to firstly connect to the Pixel, and if not found, connect to the Samsung. But it connects only to the last connected phone and obviously I have unchecked the box "connect to the last connected phone".

Did I miss something?

Thanks for your help

 

[mnunes]

I'm in the same situation. Dodge Durango with Uconnect (2018 model). It's very hit or miss, and nearly never reconnects if I'm getting back in during the 1 hour power delay.

My settings:
Dongle mode = on
Passthrough mode = on
Start/Stop = on
Firmware = 2.0.0
App = 2.12.0
Phone = Samsung Galaxy S22

The USB cable I'm using works 100% of the time when I plug my phone in directly to it.

I have an update for my Dodge Durango Uconnect (2018). It seems that once I get AAWireless to work, it only works for 1-2 trips/connections. After that, the next time it tries to connect I see the unit boot, then the LED flashes blue for a little while like it's trying to connect, then the LED goes solid white. If the USB port was still powered (1 hour delay after the ignition turns off), the LED starts solid white, then flashes blue, then goes solid white again. In either case, AAWireless doesn't work.

I did identify a work-around so I don't have to completely setup from scratch each time. In the UConnect screen, I go to paired devices and make it forget the AAWireless device that's been discovered for Android Auto. Then (also on the UConnect unit) I disconnect my phone, wait a few seconds, then reconnect the phone. After about 15-20 seconds AAWireless comes up just fine.

If it matters, I do also regularly see the message "device not supported" on the UConnect screen like others have mentioned. Changing USB mode to the various MTP modes did not help (never connects this way).

My current settings:
Dongle mode = on
Passthrough mode = enabled
Start/Stop = enabled <<< because the USB port stays powered for 1 hour
Firmware = 2.0.1
App = 2.14.0
Phone = Samsung Galaxy S22

 

[Snirpo]

Hello!

I have been using AAWireless for almost a year and I am very happy with it, everything working as intended with a Google Pixel 6 & Samsung Galaxy A7 and with a Peugeot 208 I.

Since the introduction of AAWireless 2.0 it is advertised that we can easily switch between many smartphone. But in my experience it is not working for me. I have set the AAWireless to firstly connect to the Pixel, and if not found, connect to the Samsung. But it connects only to the last connected phone and obviously I have unchecked the box "connect to the last connected phone".

Did I miss something?

Thanks for your help

Do you have dongle mode enabled?

 

[Snirpo]

I have an update for my Dodge Durango Uconnect (2018). It seems that once I get AAWireless to work, it only works for 1-2 trips/connections. After that, the next time it tries to connect I see the unit boot, then the LED flashes blue for a little while like it's trying to connect, then the LED goes solid white. If the USB port was still powered (1 hour delay after the ignition turns off), the LED starts solid white, then flashes blue, then goes solid white again. In either case, AAWireless doesn't work.

I did identify a work-around so I don't have to completely setup from scratch each time. In the UConnect screen, I go to paired devices and make it forget the AAWireless device that's been discovered for Android Auto. Then (also on the UConnect unit) I disconnect my phone, wait a few seconds, then reconnect the phone. After about 15-20 seconds AAWireless comes up just fine.

If it matters, I do also regularly see the message "device not supported" on the UConnect screen like others have mentioned. Changing USB mode to the various MTP modes did not help (never connects this way).

My current settings:
Dongle mode = on
Passthrough mode = enabled
Start/Stop = enabled <<< because the USB port stays powered for 1 hour
Firmware = 2.0.1
App = 2.14.0
Phone = Samsung Galaxy S22

When this happens, this device going back to solid white. Can you try to disconnect handsfree to the car on the phone side, and then reconnect handsfree? That should make it start up.

 

[worldonfire]

Yes, at first led goes off. Then solid green, blinking green. Then blinking blue and solid blue. Sometimes it does not even reach to solid blue and starts over...

Tomorrow i'll check what the leds do with passthrough disabled. If I remember correctly, then it does the same, but I will confirm it just to be sure.

@Snirpo looks like when passtrough is disabled, then it acts the same. Only difference is that then it is able to show aa for some time again.

 

[Marsou77]

Do you have dongle mode enabled?

Nope, I'm running AAWireless without customizing anything. It's factory settings.

 

[Snirpo]

Nope, I'm running AAWireless without customizing anything. It's factory settings.

Can you send in a bug report via the app? Help and support --> bug report

 

[Roy47]

Is it possible for me to have the Hyundai ssl fix. My device is AAWw1PUnHoF

Thanks Roy

 

[Aberk]

I have an update for my Dodge Durango Uconnect (2018). It seems that once I get AAWireless to work, it only works for 1-2 trips/connections. After that, the next time it tries to connect I see the unit boot, then the LED flashes blue for a little while like it's trying to connect, then the LED goes solid white. If the USB port was still powered (1 hour delay after the ignition turns off), the LED starts solid white, then flashes blue, then goes solid white again. In either case, AAWireless doesn't work.

I did identify a work-around so I don't have to completely setup from scratch each time. In the UConnect screen, I go to paired devices and make it forget the AAWireless device that's been discovered for Android Auto. Then (also on the UConnect unit) I disconnect my phone, wait a few seconds, then reconnect the phone. After about 15-20 seconds AAWireless comes up just fine.

If it matters, I do also regularly see the message "device not supported" on the UConnect screen like others have mentioned. Changing USB mode to the various MTP modes did not help (never connects this way).

My current settings:
Dongle mode = on
Passthrough mode = enabled
Start/Stop = enabled <<< because the USB port stays powered for 1 hour
Firmware = 2.0.1
App = 2.14.0
Phone = Samsung Galaxy S22

So far this has been the easiest fastest work around for me, but still irritating to have to do it.

 

[bagadj]

I have an update for my Dodge Durango Uconnect (2018). It seems that once I get AAWireless to work, it only works for 1-2 trips/connections. After that, the next time it tries to connect I see the unit boot, then the LED flashes blue for a little while like it's trying to connect, then the LED goes solid white. If the USB port was still powered (1 hour delay after the ignition turns off), the LED starts solid white, then flashes blue, then goes solid white again. In either case, AAWireless doesn't work.

I did identify a work-around so I don't have to completely setup from scratch each time. In the UConnect screen, I go to paired devices and make it forget the AAWireless device that's been discovered for Android Auto. Then (also on the UConnect unit) I disconnect my phone, wait a few seconds, then reconnect the phone. After about 15-20 seconds AAWireless comes up just fine.

If it matters, I do also regularly see the message "device not supported" on the UConnect screen like others have mentioned. Changing USB mode to the various MTP modes did not help (never connects this way).

My current settings:
Dongle mode = on
Passthrough mode = enabled
Start/Stop = enabled <<< because the USB port stays powered for 1 hour
Firmware = 2.0.1
App = 2.14.0
Phone = Samsung Galaxy S22

this is exactly the same problem i had... now back to 1.8.0 solve this problem, even if the message: "device not supported" shows in my uconnect for a while then disappear.. but AA starts regular with no problems.
maybe it could be an uconnect problem?

 

[Flame Red]

I have used the AAWireless on a GM and Mazda, it works perfectly.

On the Volvo I have, the voice directions from Waze are cut off at the end of whatever is said. It does not do this on the other cars I have it installed on. Phone is a Samsung Fold on all.

Might there be an setting I need to tweak for the Volvo to have it not cut off the end of the spoken Waze directions on the Volvo? Everything else works perfectly.

I have th 2.0 software installed.

Thank you.

 

[FrankieG64]

this is exactly the same problem i had... now back to 1.8.0 solve this problem, even if the message: "device not supported" shows in my uconnect for a while then disappear.. but AA starts regular with no problems.
maybe it could be an uconnect problem?

+1 experiencing the same issue with a 2020 Ram 1500, 12" Uconnect, Samsung S10. It happened occasionally prior to firmware 2.0, but now occurs on a regular basis especially during short trips. I can usually solve it by removing AAWireless from the "projection" settings in Uconnect and then restarting AAWireless. Tried dongle mode but it made no difference. Also tried with start/stop enabled and disabled, again no difference.

 

[Mezil]

Hello
I am writing to you for a small problem.
I have for three weeks AA Wireless on Opel Astra with Intellilink and OnePlus 8T.
It often happens that android auto starts up correctly, but the phone doesn't work. I can manage phone calls from Android Auto but you can't hear the voice from the speakerphone but I have to switch to putting the phone to my ear, selecting call, phone in the menu. Not the best thing since I'm driving!
How can I do? I have updated to the latest firmware. Thank you

 

[mnunes]

When this happens, this device going back to solid white. Can you try to disconnect handsfree to the car on the phone side, and then reconnect handsfree? That should make it start up.

@Snirpo
When I disconnect and reconnect from the phone, the AAW blinks blue for about 10 seconds then goes back to solid white. Similarly, when I just disconnect and reconnect from the headunit it will blink blue then go back to solid white. The only way I've been able to get it to work is to have the headunit forget AAW, then disconnect and reconnect from either the headujit or the phone.