AAWireless - General discussion and support

Search This thread


Apr 17, 2012
If you pass me your devices names (AAWireless-xxxx), I'll enable it.
Thanks Snirpo. I can confirm the 2.1.0 24/6/22 beta build works fine with intercept and DPI changes on my Pixel 5 and IONIQ 5 with the widescreen AA update. Will test stability of the connection but I'm expecting it to work as well as 2.0.2. I do notice my phone is warmer when on intercept than on passthrough. Probably higher battery drain too.


Senior Member
Jan 23, 2007
Thanks Snirpo. I can confirm the 2.1.0 24/6/22 beta build works fine with intercept and DPI changes on my Pixel 5 and IONIQ 5 with the widescreen AA update. Will test stability of the connection but I'm expecting it to work as well as 2.0.2. I do notice my phone is warmer when on intercept than on passthrough. Probably higher battery drain too.
Hmm passthrough vs intercept shouldn't really matter batter drain wise. Except possibly when the dpi has been changed.

Nice car btw ;)


Senior Member
Dec 29, 2008
Can I ask that is the domain name of the download server when downloading firmware updates? It seems that my NextDNS installation is blocking the download of the firmware update and I would like to know which domains should I whitelist.

Edit: checking the logs it seems that whitelisting *.contabostorage.com did the trick
Last edited:


Senior Member
Feb 27, 2011
I ran into a weird issue. Any time I use Google Nav, I can only control the voice volume and lose media volume control.. This does not happen when I unplug the dongle and use a wired connection.

I created a separate thread, but wanted to see if I might get any traction here. I realize this is not an AAWireless issue but I also ran into and issue when using YT Music in Drive mode/Android Auto it shows that it is 'offilne', and only allows me to play music that I downloaded to the device (Pixel 6 Pro) however when using the app itself it shows to be online. This only occurs in Drive Mode and Android Auto. I have 'Stream via Wi-Fi only' set to the off position. Is there something else I should check? If I bypass AA and use YT Music straight through Bluetooth it works fine.

Anyone experience this?


Mar 23, 2013
Hi! One here wanting the 2.1.0 update, if possible. Mine is:

AAWireless - AAW9xsSGJQb



New member
May 10, 2022
Also would like to get the 2.1 beta; car was updated by the dealership with the widescreen update.
My device ID is AAWireless-q1l4AaPn


New member
Jul 6, 2022
I had that long connection problem also before that update of my Kia Navi Firmware and not running in passthrough mode.. :) And I have it still with the beta firmware of the AA device.
Guess thats no good news for me then... :rolleyes: Anyway it would be nice to use AAW with Widescreen and with my own dpi settings and without the tap restrictions.

Would be more than happy to report issues and give some field reports on the beta Version.


Senior Member
Sep 11, 2012
Frankfurt am Main
OnePlus 9 Pro
Is it normal, when i visit the firebase link I do have 2 options, but when I click on DEV it goes to the all releases tab?


  • Screenshot_2022-07-06-13-00-15-69_d365b52accad0f47adbc08c16219827d.jpg
    170.1 KB · Views: 21

Top Liked Posts

  • 1
    I think you should address @Snirpo directly. He can certainly help you.

    Everything works wonderfully on my Opel with Intellilink.
    @Snirpo can I get on the latest 2.1.0 beta to see if it eliminates my permanent audio dropouts that require a reboot? My device is AAWhiR8mpGW

    I'm also happy to capture logs when this happens if that's possible/helpful! Just let me know how I can do that.
  • 9
    At this moment we have shut down all OTA updates unfortunately. The load on our backend is too high. Too long without maintenance because of other priorities. We have to optimize some stuff to make it work again.
    It's working again :)
    @[email protected]:
    Please stop spamming this thread !
    It's been 'next week' for the last 3 or 4 weeks!
    I'm sorry, that's because we are stuck on the UConnect issue: https://github.com/cpebit/aawireless-issues/issues/128 . We were hoping to fix this issue much sooner, but it's a very hard one. Therefore we decided to lock UConnect to 1.12.0 and release 2.1.0 anyway. Possibly we should've made this decision earlier, but we didn't.

    Again, for most 2.1.0 will not matter in any way. Mainly for cars with SSL related issues, so non-passthrough mode will work again.

    With about 100k devices, we cannot just release a firmware anymore. We need at least a few weeks to test it properly. If we make a mistake it will overload support and it can harm us a lot.

    I'm so stupid to say it will be released "next week" every time. From now on we will not give any ETA's anymore. It's done when it's done.

    Also, when we push an update. It will be rolled out incrementally. At this point we cannot do mass roll outs anymore (except for bug fix releases), because there are too many variables. So even when we release this week, it may take a while for you to actually get the firmware.
    We are going to revert some changes and release 2.1.0 officially next week. In the meantime we are testing some start issues on UConnect HU's and some other issues.

    a feature that has been desired for a long time is that you can easily switch between two cell phones. As far as I can remember, one of your team wrote somewhere that a good solution is being worked on. is this still the case? Is there a time horizon when this can be expected? for example a specific quarter or year? I mainly ask because if the wrong mobile phone connects, it is sometimes impossible to connect the other one without switching off the mobile phone, since Bluetooth and WLAN are activated again too quickly depending on the mobile phone.
    Kind Regards

    We want to do this, but "Dongle mode", which is how AA natively works with dongles, makes this feature a bit useless. Dongle mode makes only the phone connected to handsfree of the car start up AA. So you cannot really switch phones anymore, cause even if you switch phones from the AAW side, only the phone currently connected to handsfree of the car can start up AA. It might work for cars which support multiple handsfree connections, but that's most likely only a small part of the market.

    At this point our main objective is to squash as many bugs as we can, and make the dongle as native as possible, so we get the product as plug and play as possible. Possibly in Q3/Q4 we can play around a bit with new features.
    is there any way to get a manual update then? version 1.1.0 does not work on my headunit so did i just buy a paper weight?
    Wow, really? You may have bought a paper weight? You said that?

    Do you have ANY idea of what is going on here? And that yes, you'll be updating as soon as possible. While you wait to update your paper weight why don't you have a read of the 200+ pages of this thread and edumacate yourself.

    The AAW Team go above and beyond, they deserve better, and if you're on here you should know the complexity of what this device does, which is more than any other on the market.
  • 41
    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.
    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!
    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.
    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
    Emil Borconi-Szedressy 2 days ago
    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.

    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.
    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.