• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

AAWireless - General discussion and support

Search This thread

speedyg0nz

Senior Member
Dec 6, 2010
160
67
Sony Xperia 1 III
I have been having issues with my AAW device constantly connecting and disconnecting. It will connect for usually a few minutes at a time and then disconnect and reconnect again. It continues to do this the entire time i'm in the vehicle. I've been emailing AAW back and forth but nothing is seemingly fixing the issue. Has anybody else had these issues?
Which car/headunit model?
 

[Jaco69]

Senior Member
Dec 24, 2008
276
78
20 Jeep Gladiator Uconnect

Furthermore I had frequent AAwireless reboot problems while driving, this seems to be solved checking "Enable Audio Latency Dump" in Android Auto Developer Settings. Seems strange as I found only VW reporting this problem in this thread.

Jeep Renegade with Uconnect 8.4
I wrote this just some post before, try it and confirm if it solves the problem for you, for me no more reboots
 

psylentknight22

New member
Sep 29, 2021
4
0
No luck... Still continues to do the same thing... I'm really at a loss... Seems like nothing I've done has fixed the issue but a few things that I've been told to change have made it worse at times and makes it disconnect more frequent
 

IlD4nX

Senior Member
Aug 3, 2008
460
95
Bugella Civitas
Ok, revert back to 1.5 and it works flawlessly again. Only odd thing is related to connection method: before was set to default and working... Now I had to set it to direct to make it work!
BTW still my best purchase in the last year (early baker!
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,866
33,611
Halifax
GT-i9250
Google Nexus 4
@osm0sis @janz25 @dzeidzei

I put your devices on a version which might fix the boot (no led) issues for 1.7.0+. You can update to this version via the OTA screen. Could you check if this fixes it? I can't reproduce it, so it's a bit hard to verify myself :)

Thanks!
Thanks! Sent you a few sets of logs.

One where I thought it seemed working after the update.

One with Start/stop enabled and it got stuck in blinking green when the car was started from fully off (Elantra 2018 has 3min of USB power once turned off). Solid white standby mode seemed to work really well, so it's a shame the cold start stuff isn't working.

And one with Start/stop off again, after car start fully off, and no LED light showing so I had to unplug and replug twice again to get it to boot. So, the problem is still present it seems. 😕

Edit: Did another cold start and it worked this time?! Seems more intermittent now, at least.. sending a 4th set of logs for comparison. 🤔
 
Last edited:
Thanks! Sent you a few sets of logs.

One where I thought it seemed working after the update.

One with Start/stop enabled and it got stuck in blinking green when the car was started from fully off (Elantra 2018 has 3min of USB power once turned off). Solid white standby mode seemed to work really well, so it's a shame the cold start stuff isn't working.

And one with Start/stop off again, after car start fully off, and no LED light showing so I had to unplug and replug twice again to get it to boot. So, the problem is still present it seems. 😕

Edit: Did another cold start and it worked this time?! Seems more intermittent now, at least.. sending a 4th set of logs for comparison. 🤔
When mine doesn't automatically connect (which seems to be over 50% of the time), I just go into my phone's Bluetooth settings and click on the AAWireless device listed there and it connects right away.
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,866
33,611
Halifax
GT-i9250
Google Nexus 4
When mine doesn't automatically connect (which seems to be over 50% of the time), I just go into my phone's Bluetooth settings and click on the AAWireless device listed there and it connects right away.
No LED is the big problem here, then it connecting 0% of the time for me from a cold start with Start/Stop is another problem.
 

Snirpo

Senior Member
Jan 23, 2007
160
213
  • Like
Reactions: osm0sis
In regards to the start / stop issues, please try the internal beta app: https://appdistribution.firebase.dev/i/5196d378c8e122d7

In regards to the "no led" issues. I'm trying to reproduce it, there's nothing in the logging, all seems fine. So it probably fails very early on boot. You can also join us in Slack for some more direct communication:

Join my Slack workspace! https://join.slack.com/t/aawireless/shared_invite/zt-nu6jokgj-Y~FxA6aegEZMi98aISYEjA
I have been using the internal beta app. I have seen a message on my phone saying it cannot connect to the AAWireless Wifi. That's when I figured out I could just go to the Bluetooth settings on my phone and select the AAWireless Bluetooth device there and it would connect right away instead of unplugging/plugging back in hoping it would work. Maybe a timing issue with getting the password sent for the Wifi?
 

Snirpo

Senior Member
Jan 23, 2007
160
213
I have been using the internal beta app. I have seen a message on my phone saying it cannot connect to the AAWireless Wifi. That's when I figured out I could just go to the Bluetooth settings on my phone and select the AAWireless Bluetooth device there and it would connect right away instead of unplugging/plugging back in hoping it would work. Maybe a timing issue with getting the password sent for the Wifi?
I'll check the logs, but first need to fix these no-led issues :)
Might have figured it out, was able to reproduce by re-plugging the device 100+ times. @osm0sis (and others) can you update to the latest "boot-fix" version to check if this helps for you?
 
  • Love
Reactions: osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,866
33,611
Halifax
GT-i9250
Google Nexus 4
In regards to the start / stop issues, please try the internal beta app: https://appdistribution.firebase.dev/i/5196d378c8e122d7

In regards to the "no led" issues. I'm trying to reproduce it, there's nothing in the logging, all seems fine. So it probably fails very early on boot. You can also join us in Slack for some more direct communication:

Join my Slack workspace! https://join.slack.com/t/aawireless/shared_invite/zt-nu6jokgj-Y~FxA6aegEZMi98aISYEjA

I'll check the logs, but first need to fix these no-led issues :)
Might have figured it out, was able to reproduce by re-plugging the device 100+ times. @osm0sis (and others) can you update to the latest "boot-fix" version to check if this helps for you?

Latest boot-fix version seems to work much more consistently again from a cold start. Oddly got stuck on flashing green on 1/4 attempts. And on my 5th attempt I got the "no LED" issue again, with a quick unplug/replug getting it booting. 😔

The beta app seems a bit more convoluted with regards to bug report submissions, and appears to attempt downloading the logs twice simultaneously, with one usually failing, then the AAW Config app may or may not register the successful one for submission.

Edit: The beta app does resolve the Start/Stop issues that I was seeing, entering/exiting from standby (white) flawlessly, and cold starting much more consistently without issue.

Edit 2: I've also just discovered unlocking/locking my Elantra 2018 provides another 3min of USB power, so I bet it's some kind of timing issue with the AAW unit booting up early/partially/frequently with no connectivity and weird power conditions (since it always boots fine to green with the charger-only port, even when it would stay black when replugged in the AA port on 1.7+). The new-and-improved Start/Stop might actually be a viable workaround for the "no LED" issue until you can figure out the regression from 1.5.0 to 1.7+.

Edit 3: Spoke too soon, managed to trigger "no LED" with a cold start with Start/Stop enabled, and a quick unplug/replug getting it booting back into standby, but then it was so late it didn't register the car was started and car BT was already connected so it remained in standby (tapping the AAW device in the BT list got it moving). 😑
 
Last edited:

Snirpo

Senior Member
Jan 23, 2007
160
213
Latest boot-fix version seems to work much more consistently again from a cold start. Oddly got stuck on flashing green on 1/4 attempts. And on my 5th attempt I got the "no LED" issue again, with a quick unplug/replug getting it booting. 😔

The beta app seems a bit more convoluted with regards to bug report submissions, and appears to attempt downloading the logs twice simultaneously, with one usually failing, then the AAW Config app may or may not register the successful one for submission.

Edit: The beta app does resolve the Start/Stop issues that I was seeing, entering/exiting from standby (white) flawlessly, and cold starting much more consistently without issue.

Edit 2: I've also just discovered unlocking/locking my Elantra 2018 provides another 3min of USB power, so I bet it's some kind of timing issue with the AAW unit booting up early/partially/frequently with no connectivity and weird power conditions (since it always boots with the charger-only port). The new-and-improved Start/Stop might actually be a viable workaround for the "no LED" issue until you can figure out the regression from 1.5.0 to 1.7+.

Edit 3: Spoke too soon, managed to trigger "no LED" with a cold start with Start/Stop enabled, and a quick unplug/replug getting it booting back into standby, but then it was so late it didn't register the car was started and BT connected so it remained in standby (tapping the AAW device in the BT list got it moving). 😑
I'm honestly a bit confused, bassicly reverted all changes to the kernel / boot script now.
Need a bit of a sanity check, putting your device back on 1.5.0 right now. Can you double check if the issues are gone on 1.5.0?
 
Last edited:
  • Like
Reactions: osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,866
33,611
Halifax
GT-i9250
Google Nexus 4
I'm honestly a bit confused, bassicly reverted all changes to the kernel / boot script now.
Need a bit of a sanity check, putting your device back on 1.5.0 right now. Can you double check if the issues are gone on 1.5.0?
Turned Start/Stop off again, downgraded to 1.5.0. Just cold booted 8 times (with that 3min USB power wait in between, remember... 😅), and on only the 6th time out of 8 I had the flashing green issue and just disconnected and reconnected the AAW BT device on my phone to fix. Zero "no LED" cold boot problems whatsoever on 1.5.0 that I can tell. All seems pretty consistent again. 🤷‍♂️

One other thing I notice is that when the 3 minutes of USB power with the car off is up the device briefly flashes green, sometimes making it to blue again before turning off. Makes me wonder about timing issues and incomplete boot issues as I mentioned in Edit 2 of my last post. Perhaps 1.7.0+ just can't tolerate weird USB power mode/no connectivity reboots anymore?
 
Last edited:

Snirpo

Senior Member
Jan 23, 2007
160
213
Does anyone in the EU has a device with these "no LED" issues occurring often (on 1.7.0)? We can exchange it for a new device.
 

Top Liked Posts

  • 1
    Is there a way to find out what the aawireless devices WiFi password is? More often that not, even when connecting via Bluetooth to aawireless, it then fails to connect to aawireless WiFi. You can have the device setup and functioning then the next drive it refuses to connect. Often the only way I'm able to get it connected is to connect via USB first then disconnect and then magically aawireless decides it wants to connect.

    IMO if we could get our individual AAW WiFi password, setting up an automation in a certain sequence could fix alot of connection issues but atleast users could experiment instead of waiting for an official fix that very well may never happen for some devices/headunits.

    So once more; Is there a way to find out what the aawireless devices WiFi password is?
  • 3
    I wanted provide an update on this to see if anyone has any idea. I ended up downgrading the firmware on my cars head unit to the version that was working perfectly previously. I still have the same situation. Using a cable to my phone AA works perfectly. Using the AAwireless device, my phone connects and prompts me to open AA on my cars head unit however the icon to click on the head unit screen is not there. This behaviour only happens when using the AAWireless device. I am thinking now this is a Android 12 issue and perhaps something updated on my phone around the same time the firmware in my car was updated. Is there anything I should be doing to provide logs on this? There is not really an error I suppose on the AAwireless side but something seems to not communicating correctly. I will be testing on another car to see if the problem persists or not in the coming days.
    We have a support overload since Android 12, it ain't funny... Emil and myself have (almost) zero issues on our Pixel 6s. The only thing I experienced once or twice is Bluetooth cutting out on the Pixel, have to reboot the phone to get it to work again. Stuff is broken for sure... For some it works fine, for others with seemingly exact the same situation it does not. We're trying to find solutions, but we're already pretty overloaded with everything going on.
    2
    Wouldn't recommend downgrading your device (requires @Snirpo or another aawireless dev to do this) because then like me, you'll be stuck on firmware 1.5 with no explanation why someone people are on 1.7.1 and others are stuck on 1.5 and no option to update. I'm also a first gen aawireless AAWireless-eSs19MUQ
    Explanation: some batch 4 devices have been flashed with batch 3 firmware, and at this point we have no way to differentiate them from the backend automatically. So batch 1, 2 and 4 are save to update, batch 3 not, because it could also very well be an batch 4 device. It's causing havoc cause the backend is not really set up for this situation. For now we are only doing manual updates for batch 3 devices.
    2
    Some info that may provide some insight to others. I'm using an Xiaomi note 9s (Curtana) and while running MIUI EU 12.5 I have issues with AAW after a call ends it plays through my phone's speakers instead of the headunit speakers. This is a well known bug from MIUI. I tried flashing a few different android 11-12 ROMs and ALL had issues with AAW from aosp ROMs to official lineage os (android 11) and gave up on the idea of a bug free experience.

    However, I flashed a build of MIUI EU 12.6 and I now have a BUG FREE EXPERIENCE of AAW - no dropping out, calls work without disconnecting/sound going through incorrect sources etc.

    My point being: this is XDA - we flash different ROMs some of which are buggy to high hell. If you're having issues with your phone and connections etc please try using a stable ROM or change your ROM to check if you have any luck connecting/resolving bugs. There are plenty of aftermarket ROMs here where android auto via USB functions great but wireless is bugged (looking at you lineage os) just my two cents
    2
    Hi !

    I got my AAWireless today. Updated to 1.7.1, and used it with a Pixel 6 Pro on a Hyundai Ioniq 2020 (with the April 2020 head unit SW update).

    It's working fine for ... a few minutes. Then it disconnects. I had about 4 or 5 disconnects on a 15mn trip today while using intermittently maps, spotify or both.

    When it happens, it looks like the LED stays blue, the head unit says the phone disconnected, the phone things AA is still on, and based on feedback from my passenger fiddling with the phone, AAWireless app on the phone still thinks it's connected to the device.

    If you wait long enough (a couple of minutes) it eventually comes back. That or disconnect/reconnect.

    All settings are default.

    Any suggestion ? I couldn't figure out what to do with the "debugging" mode... that said I'm a SW engineer so given instructions I can probably dig out logs etc...
    2
    I have a Samsung s21 Ultra on the Android 12 beta. Everything works perfectly for me so far. I haven't seen the change your referring too though.
  • 30
    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
    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.
    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.