AAWireless - General discussion and support

Search This thread

Snirpo

Senior Member
Jan 23, 2007
376
441
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

Member
Nov 21, 2007
11
1
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.
 

Snirpo

Senior Member
Jan 23, 2007
376
441
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

Member
May 19, 2022
16
0
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

Member
Nov 21, 2007
11
1
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

Senior Member
Feb 2, 2011
1,465
349
Earth
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 :)
 
Last edited:

mnunes

Member
Feb 24, 2007
17
1
Verizon Samsung Galaxy S8
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

Senior Member
Jan 23, 2007
376
441
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

Senior Member
Jan 23, 2007
376
441
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

Member
May 19, 2022
16
0
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.
 

Aberk

Member
Nov 21, 2007
11
1
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.
 
  • Like
Reactions: mnunes

bagadj

Senior Member
Jan 24, 2010
353
32
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?
 
  • Like
Reactions: mnunes

Flame Red

Senior Member
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.
 
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.
 
Last edited:
  • Like
Reactions: mnunes

Mezil

New member
May 27, 2022
1
0
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

Member
Feb 24, 2007
17
1
Verizon Samsung Galaxy S8
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.
 

Top Liked Posts

  • 2
    Always ready to test. I'm already part of the google play beta group, will the test version show up there?
    For the latest, please download: https://appdistribution.firebase.dev/i/5196d378c8e122d7
  • 7
    I got bored today, so I thought I make a mock up how the AAWireless app could look like :D When swiping t he car picture could change if you want to connect to annother device/car :D

    View attachment 5645393 View attachment 5645397
    Haha nice! I'll pass it on to our UI/UX designer :) We have some UX changes in the pipeline, but it doesn't have the highest prio right now as you can imagine.
    We made some changes in firmware 2.1.0 which means we don't need these dreaded USB modes anymore. The plan is to ship devices in passthrough + dongle mode, to make it work natively, like the MA1, by default.
    Then we are going to hide away the settings in a sort of advanced settings menu, because all these settings are nice, but people don't read/understand what they do, stuff stops working and then our support has to handle it. Hardly anyone uses these settings, for example, dpi change, the most used feature, is only used on 1 percent of all devices.
    Bassicly we are KISS'ing it, but still keep advanced settings for well... You guys :)
    5
    @everyone

    For feature requests or issues, please use: https://github.com/cpebit/aawireless-issues/issues/new/choose

    I getting really hard to follow this thread. Possibly I already forgot some requests of some people. Need a bit of structure. We will try to fix issues one by one from GitHub.
    4
    Regarding the broken day / nightmode cycle:

    I also have this problem, and I read a few days ago that it was due to a combination of updated Google Maps and Android Auto.

    The combination which should work:

    Android Auto: 7.5.621344
    Google Maps: 11.31.1

    You finde all these old versions on apkmirror.com, or similar sites.

    Didn't have the time to check this out myself.

    I had this same problem. Found out it woud be caused to 11.31.1 and upwards. Found the solution on Google Maps Help.

    I installed Maps 11.35.0 beta (from apk mirror) and all seems to work well again. My AA is level 7.7.622134 (from play store).​

    Tried a lot of different variations, but my conclusion is that Maps from 11.33.1 is the culprit.
    3
    That is normal when using the dev version of the app. Dev version will always let you reflash actual version if there's no newer one.
    Yes, it's normal, but I'll remove it, because I get a comment about it almost every day :)
    3
    @Snirpo

    Why don't you use a Y-cable? Data plugs into the USB and electric power from the cigarette lighter plug.
    By this you can check the voltage on the cigarette lighter plug. Is it 12.x Volts, you know the engine is off. Then you wait for a timeout of 2 minutes after the phone disconnected and turn off AAWireless. As soon as the voltage is 14.x Volts, you know that the engine is running and turn AAWireless on. You could sell this as an addon cable for people who need this.

    Another solution is to make it based on vibrations/accelerations. The early bluetooth handsfree sets used a similar way to check if the door was opened. I don't know if there is a sensor on the board.

    Another idea is to carefully check how stable the 5V from USB is during engine start as the ICs have to control the output voltage based on the input voltage (input voltage should drop during engine cranking). I guess you will see a voltage control behavior. I think it will drop for a short time and then go over 5V until the controller sets the 5V stable. And here you can start AAWireless. As soon as the phone disconnects keep a long enough timeout of 5 minutes or so to make sure that noone tries to reconnect. Then you can turn off AAWireless. You could sell this as an addon cable for people who need this.

    These are just some ideas...
    While I do like these ideas technically. From an UX perspective I don't know.

    Right now already we get complaints AAWireless is difficult to setup (while in reality it really isn't), compared to for example the MA1, this would complicate it more. I have seen a lot of support tickets, and for non-tech these things are just very hard to understand. "Why do I need an extra cable?!"

    I think for the car's which have an always on USB port (Dodge RAM/Jeep) we seem to have a proper device controlled solution now (in beta).
    For other cars which keep their USB port powered for just a while after turn off its trickier, but even then the phone controlled way works for most. What's left is the edge cases, where we have to think about how to handle those.
  • 40
    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.
    16
    I just want to leave a big THANK YOU for the developers! You invented a great product and do a great job here.

    Anyone who has ordered the product knows that it is a crowdfunding project, which may also have teething problems. I find it cheeky to get upset about problems, even though they are dealt with promptly here. What more should the distributors do than react to the problems here and offer solutions?

    I also have problems with the device, but I was helped quickly. Even if it takes a few days.

    Dear team: Keep up the good work!
    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.
    14
    I've already waited patiently for delivery 3 months more than expected - I ordered In April and was coming in June but now that's looking like October. Now I read on the indiegogo forum that people in the UK are being charged an additional €27 by the Royal mail as the UK is now not in the EU.

    Hi Emil!
    Just received my AAWireless, and will plug in and test tonight. Love the packaging, looks great! However… Since it was shipped from Hong Kong I was forced to pay a rather substantial import fee and duties on this bad boy. I was under the impression that they would be shipped from within the EU? Is it stands now I’m EUR 27,00 poorer :(
    2 2
    https://www.indiegogo.com/individuals/24534862
    Emil Borconi-Szedressy 2 days ago
    PROJECT OWNER
    Looks like you are in the UK which is outside EU and also there is no way to pre-pay taxes with shipping company any more either....


    This is a crazy. An additional $10 was already taken for delivery and it was meant to ship from the EU. I suspect the units have been shipped by Royal Mail / Dutch post. The Royal Mail rips off people in the UK because they add another £11 in admin fees on top of the 20% VAT even though goods up to £135 should be exempt.
    See https://www.gov.uk/government/publi...s-goods-sold-to-customers-from-1-january-2021

    So not only has VAT been charged coming into the EU from China, it has also been charged coming into the UK ON TOP of the VAT already paid in the EU.

    This is just rubbish. What the guys need to do is either ship it from Hong Kong which can cost £0.20 (there are hundreds of chinese ebay and aliexpress sellers doing this already
    See http://www.vatfraud.org/blog/stop-s...ons-universal-postal-union-upu-terminal-dues/
    The $10 postage already taken should then be refunded.

    The other way round it is send the item from Hong Kong and to mark the item as a gift and providing it is below £39 there is NO VAT to pay and NO Royal mail admin fee. Actually as the original product was $57 - roughly £41.25 This wouldn't be a crime seeing as we have had to wait soo long. This could also mean the $10 delivery could be refunded

    The other way is to ship it via fedex and state the ex-vat cost coming from china and then add 20% vat that the developer should be paying to the UK HMRC.

    Sadly if that doesn't take place, EVERYONE IN THE UK will feel ripped off because of the poor delivery and poor choices made by the developers.

    Cheers
    Disgruntled in the UK

    First of all, your item wasn't shipped yet since in the June batch, so you could have not payed anything for shipping. Secondly, UK is outside the EU, there was a vote about this in 2016, so it doesn't matter if the package comes from EU or from HK or from US, it is treated the same, it's an import. If we import it from HK to EU, we will pay import VAT on the product, then when we send it to UK, we claim back that VAT and we should pay VAT in UK, since there is no more free trading between EU and UK.

    Up till recently there was a nice option, to pay VAT and Import duty up-front, when you ship to the UK, but this has been changed and now they requires business outside UK to register with HMRC and do HMRC feeling even if they are residing outside UK, a lot of red tape. Since crowdfunding is not a sale, we can still ship the units to UK, but not sure if we will be able to after the IndieGoGo campaign.

    We are also a EU registered company so we cannot (and will not take advantage) of any loop-holes in systems to sell at ridiculously / unrealistically cheap prices.

    About the user who paid 27 euros, it turned out that user is living in DK, but provided the address as UK so his package traveled the wrong way, hence the extra duties and surcharges.

    Not aware of other users from UK having to pay anything additional when they received the package.