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

AAWireless - General discussion and support

Search This thread

IlD4nX

Senior Member
Aug 3, 2008
460
95
Bugella Civitas
You mean it doesn't start the first time, or not at all anymore?
I mean that one's updated to 1.7 it start the first time and then I have to unplug the cable from aawireless wait some minutes and the plug in it again to make it works every time. For some reason I don't really understand, if unplug the cable from the car only, it doesn't work at all.
 

kingpong

New member
May 20, 2006
4
0
We 99% percent sure found the issue now. I put your devices on a 1.7-hotfix version.
I'm running into the same issue with 1.7. often now when I start the car it does not connect until I unplug aawireless and plug it back in. around the same time I updated to 1.7, my wife paired her phone with my car and I thought that was the issue. but after removing her device, it still happens. I checked today when it happened and noticed the LEDs did not light up similar to what others have reported.

any chance I can try the hot fix as well?
Ww94Dlf0
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,857
33,602
Halifax
GT-i9250
Nexus 7 (2013)
How do I get 1.70 it shows 1.50 is the latest on my app thanks all
Rollout was stopped until failed boot issues are fixed.

I'm testing the fix right now actually, seems so far so good! Trying out Start/Stop again next for extra levels of difficulty. 🤠🤞

Edit: @Snirpo honestly all seems pretty solid again now! The new Start/Stop in 1.7.x and the internal beta app seems very consistent now as well! Great work! Ship it all! 🎉🤘

Only (apparently cosmetic) thing I notice is that sometimes with Start/Stop my phone will make a toast message "Incorrect password" presumably for WiFi, but otherwise all appears to work flawlessly now.
 
Last edited:
Only (apparently cosmetic) thing I notice is that sometimes with Start/Stop my phone will make a toast message "Incorrect password" presumably for WiFi, but otherwise all appears to work flawlessly now.
1.7 hotfix seems to have fixed the no LED issue for me. I still get what you did above about invalid password and have to connect by choosing the AAWireless Bluetooth connection. Happens more often than not, so start/stop isn't really working well for me. My vehicle is a 2020 Ram 1500 with UConnect system.
 
  • Like
Reactions: osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,857
33,602
Halifax
GT-i9250
Nexus 7 (2013)
1.7 hotfix seems to have fixed the no LED issue for me. I still get what you did above about invalid password and have to connect by choosing the AAWireless Bluetooth connection. Happens more often than not, so start/stop isn't really working well for me. My vehicle is a 2020 Ram 1500 with UConnect system.
Weirdly Start/Stop still works fine for me even when that password error toast is displayed.
 

Snirpo

Senior Member
Jan 23, 2007
160
213
Weirdly Start/Stop still works fine for me even when that password error toast is displayed.
I'm glad the no led is issue is fixed now :) This was a nasty issue. I'll give out testers a day or two to double check if it's completely solved, so I'll probably release 1.7.1 on Tuesday.
Sadly we shipped 10k devices with 1.7 now, so will have to immediately push 1.7.1 to those devices. Not going to be much fun support wise I'm afraid :(
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,857
33,602
Halifax
GT-i9250
Nexus 7 (2013)
I'm glad the no led is issue is fixed now :) This was a nasty issue. I'll give out testers a day or two to double check if it's completely solved, so I'll probably release 1.7.1 on Tuesday.
Sadly we shipped 10k devices with 1.7 now, so will have to immediately push 1.7.1 to those devices. Not going to be much fun support wise I'm afraid :(
I see another hotfix build rolled out to me this morning, need it tested again, or anything to be aware of with it?

Edit: Well I tried it anyway, and still seems good in my casual use today running errands. 👌
 
Last edited:

Patrick3000

New member
Oct 4, 2021
1
1
Samsung Galaxy S10
My device is still on FW 1.5, but I can report that the internal beta build of the App SW appears to finally have Start/Stop functionality working perfectly for me (Hyundai Kona Electric with Samsung Galaxy S10).

However, when I upgraded the app to the beta build it initially behaved as if Start/Stop functionality was disabled even though it was still set in the settings. To fix it, I had to disable and then re-enable Start/Stop in the app, which prompted the app to request screen overlay permissions. This then put it into a state where the device was perpetually showing solid white LED and would not connect to the car.

Finally, after de-selecting and re-selecting my car's Bluetooth connection in the Start/Stop menu a few times I got it to work. It has now been working reliably for a couple of days.

So, I thought I would report my experience just in case this helps make the rollout of the new app sw a bit smoother for everyone else.
 
  • Like
Reactions: osm0sis

SOFO888

Senior Member
Jan 28, 2013
77
10
Hey guys,

I have an idea for the 2 phones topic.

In my car the car chooses the phone to connect to the Bluetooth system by choosing the corresponding driver. That means if I choose my name, everything in the car gets set up for me and my phone gets connected to the Bluetooth system.
As soon as I choose another driver, the car sets up everything for the other driver, disconnects my phone and connects the other driver's phone through Bluetooth.

My idea is to use the app Tasker. We could make a profile which runs the following task a soon as the phone does not connect to the car system's Bluetooth while getting AAWireless connection through WiFi:
Turn Bluetooth off and turn WiFi off. After 2 minutes, the task turns on Bluetooth and WiFi again. During this period it is possible for the first phone to get connected to AAWireless.

If both phones have this profile, the phone that gets connected to the car's Bluetooth system should connect to AAWireless while the other phone turns off connectivity for 2 minutes.

What do you think about this idea?

I did not receive my AAWireless yet. Perhaps someone could test this for us.
 

janz25

Member
Sep 28, 2006
18
4
I also received another hotfix build pushed to my unit, downloaded and installed, so far so good, no more issue with dead system. I dont use start/stop function since my car usb will auto off after engine off.

My issue all along on v1.5 are random disconection after around 30mts of drive and spotify/music stuttering after around 20-30mts drive.

Hope this build solved those issue. Will report if encounter anything else.

Thanks for the fix @Snirpo
 
  • Like
Reactions: osm0sis

RealNBB

Senior Member
Aug 18, 2014
126
38
I'm glad the no led is issue is fixed now :) This was a nasty issue. I'll give out testers a day or two to double check if it's completely solved, so I'll probably release 1.7.1 on Tuesday.
Sadly we shipped 10k devices with 1.7 now, so will have to immediately push 1.7.1 to those devices. Not going to be much fun support wise I'm afraid :(
Hi,

are you going to release 1.7.1 this day? Because i have same problems with 1.7 like the others here. Would be great! :) Thank you!
 
  • Like
Reactions: osm0sis

Top Liked Posts

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