AAWireless - General discussion and support

Search This thread

seseattle

Member
Jul 6, 2006
25
0
Houston, TX
Some USB mode feedback.

I'm on 1.7.1 and it's working well on my '19 Ram 1500 with the 12" UConnect screen - except that it pops up a "device not supported" on every 2nd or so reconnect. This was fixed by putting it in MTP mode and now it is working perfectly.
 

dzeidzei

Member
Sep 27, 2014
6
1
I'm also quite happy with 1.7.1 on my passat gte. Only flaw seems to be the one i've had for quite a long time. I think pre-1.5.0:

Sometimes, maybe one out of 5 times AA just doesn't launch. Workaround for this is has been for me to open app, got to start/stop setting, disable and enable it back and then save settings. After this AA will launch in about 10 seconds, everytime.
 

ekraus50

Member
Sep 11, 2021
6
1
I have a Ford with Sync 3. The AAwirless module works as stated but when I shut the vehicle down and exit
the phone stays connected until I am pretty far away. If I am on a call it stays connected but with no voice.
The USB port stays active for some time. And if I exit the car am close enough the AAmodule connects to the phone.
My only cure it to unplug the module. Any idea how to fix this?
 

Lenster45

Senior Member
Oct 2, 2010
209
26
Naples
I've had my unit for about a week now. Its running 1.6 and says no update available with is fine by me since its been operating flawlessly. The only quirk is. I listen to audio music stored on my phone using VLC media player. The player no longer resumes from where is left off when I turn the vehicle on. I have to enter the app on the HU and select the playlist. It always resumed correctly when attached by cable.
2017 Honda CRV USA

Len
 

yahoo666

Member
Oct 15, 2021
17
3
Adding up to what I've already wrote here. What I've noticed is that when the AAW is in "blinky blue" status (which means it's available to be enabled on the HU, but not enabled) - it could stay in this state forever. But after it turns to solid blue (which means the AAW has been enabled on the HU) - it crashes as described.

Also noticed, that after last update to beta 1.8 I get red light when booting.

cheers
y.
 

Lenster45

Senior Member
Oct 2, 2010
209
26
Naples
Problem started showing up. Device stays at blinking green. I followed the instructions to reset everything. Still doing it. A message says "Internet Unavailable cannot Auto Connect" and it never disconnects from the home WIFI.
If I power it from a outlet. It works fine and goes to blinking blue. It disconnects my home network and connects to the AAWireless WIFI. It I reconnect it to the car again, back to blinking green.

2017 Honda CRV USA. Stock HU

Len

Edit: Works fine in the car when connected on a cable. On firmware 1.6 but it says no update available. Also tried 2.4G wifi.
 
Last edited:

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
16,773
40,453
Halifax
GT-i9250
Google Nexus 4
Even though I don't have any problems on 1.7.1 (actually working the best it's ever worked), a bit more of an official statement on the apparent global rollback to 1.5.0 would be nice. 🤔
 

Snirpo

Senior Member
Jan 23, 2007
978
896
Even though I don't have any problems on 1.7.1 (actually working the best it's ever worked), a bit more of an official statement on the apparent global rollback to 1.5.0 would be nice. 🤔
Yes, sorry we probably should've communicated that. All older batch devices are now back to 1.5. We had some issues coming in of devices having connection issues on 1.7 and also cases where WiFi stopped working. It might be a bit confusing, but to prevent a lot of tickets coming in with "can you downgrade my device" we decided to provide 1.5 as latest firmware again. I'm now waiting for some returns to come in where the Wifi stopped working (mostly batch 3 devices), so I can analyze what's happening and restart the rollout.
Next time we will probably do a phased rollout, cause rolling out an update sucks with the amount of hardware variance we have at the moment.
 

diehof

New member
Oct 23, 2021
2
0
I have Seat Ateca built 2018, Samsung 9+, Android 10,...updated ota last week on 1.7.1 and it's working well with original cable.
 

Selo68

New member
Oct 23, 2021
3
1
I have problems with reconnecting since version 1.7.1. But only if i leave car and come back after a short time. (unplug and replugging solved the problem). When conneced aa is running rocking solid (without any disconnects). Phone mi9 with crdroid and nikgapps stock
I have the same problem. I don't know if this is caused by vehicle infotainment or AAW
 

*****_***

New member
Oct 23, 2021
1
0
I got my AAwireless two weeks ago. As far as I know it is from last batch. Firstly I updated it to 1.7.1.
I've noticed it crashes randomly... After crash a light in the AAW device is still solid blue. In order to make it working again I need to unplug AAW device from car and connect again. I tried to use other cables but it does not help.

I use it with samsung galaxy s20+.
My car is KIA Proceed MY21 with widescreen.

Do you have any idea how to fix it? Maybe should I change something in settings?
 

Ludeape

Senior Member
Jul 2, 2015
525
124
Hi,
Have anyone come across the issue with a Samsung phone having the issue of AA wireless ask for secure folder password every time it connects?
Thank you
 

Zece-88

Member
Dec 25, 2016
14
0
Yes, sort of. But it's too technical at this point. It means fully re-flashing the device. We don't want another "DRAM fix" adventure again, that was an horrible experience. We first need to understand this issue and check the numbers, if it's worth the hassle of explaining how to re-flash the device. But for sure in the future we will provide some easier USB update mechanism. It's possible with the update tooling we're using.
Hi @Snirpo,

Im stuck at the v. 1.7.1 with no working wifi after the upgrade. Emil says he rolled med back to v. 1.5.0, but no update to be seen in companion app.

I downloaded the v. 1.5.0 firmware om pc. Please explain how to re-flash the unit.
 

mars1300

Member
Oct 5, 2021
6
0
Hi. Just wanted to give some info about my experience. I have one from the batch that needed the DRAM fix, and am using with a Mazda infotainment. After the DRAM fix the device was rock solid, it probably crashed/rebooted twice over a few months.

This was being used on Mazda vehicle with firmware 70.00.367A.
After updating to Mazda firmware 74.00.230A it started crashing constantly, multiple times on a 15 minute drive. I contacted support and got told to send it in for a replacement, but I decided to wait a little and see if the 1.7.1 update fixes those crashes.

The 1.7.1 update made things a lot better, but it still crashes occasionally, maybe once every 3 or 4 drives, which is usable, but not as good as it was on the older Mazda firmware. I'm hoping that this gives you something to track down with Mazda's update. Since I don't drive too much, I think I will wait and hope for a software fix before I send it in for a replacement.
@Snirpo @Emil Borconi Just wondering if you think these crashes will be solvable through software updates or if I should send it back for a replacement as was instructed by support. If you think it's solvable I don't mind waiting.
 

EGOiST1991

Senior Member
Jul 3, 2015
530
116
Cologne
My device works greeat so far. It just looses the connection 2-3 times a drive. it will connect after a few seconds back. but it still is a problem i guess. is there a fix?

Since there are so many cases with reconnecting i wanna specify.
It connects perfectly fine! After 15-20mins the connection is lost for 5-10-15seconds. and then i can reconnect via my carscreen.
Some time into the drive the same happens again. The disconnects seems at the same gps position...
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    I should have come to this thread to begin with, but I, too, am having this issue as well. Also in a Polestar 2.

    I submitted a support ticket on January 17 this year, and after providing plenty of information and submitting bug reports, it seems I have been forgotten about. I was even told that "no other Polestar owners have reported this" - rubbish, it seems!

    I recently got the 4.0 Beta notification and today updated that in the hope that something had been done, but nada!
    I note there are several compatibility options for other manufacturers that exist, including a new one in 4.0 that I haven't noticed before that addresses a Mercedes Benz issue, so surely two people with the exact some car is enough to acknowledge there is an issue for Volvo/Polestar AAOS compatibility?

    I'm grateful I didn't buy my AAWireless to use in my Polestar, because I'd be bloody annoyed at having paid the money I did for it and having a shiny, new paperweight as a result.
    AA over CP is NOT a core feature. In fact even CarPlay is NOT a core feature (yet). Its beta... We dont advertise it anywhere. Its a nice extra, but that's it. Sorry but these "paperweight" comments annoy the heck out of me. Some people expect their issues to be fixed right away. That's just not how it works.
    2
    That sounds good.

    While I have your attention, where do I find documentation for the app's multitude of device settings?

    Also what color should the device's light be when it is connected and properly working? My device is blue and everything seems OK.
    Blue means working correctly, so you're ok.
    Hey Snirpo,

    Thank you very much for the quick response.
    I don't like to have Google Maps as start app.

    I tried everything to have another app as start app, but did not find a way to change it.

    My last hope is to emulate touch inputs on the head unit.

    Can you please give me some support how to emulate touch inputs?

    Thank you very much.
    It's not possible right now, we have to implement it. But it's quite some work and it will be pretty wonky with all the screen sizes and stuff.
    Hi all, I have a 2020 Corolla Sedan (USA). This car only supports CarPlay, not Android Android Auto.

    We purchased the latest version of AAWireless and enrolled in the beta program to enable AA over CP and it actually loads in the car and looks and works like native AA, which is amazing.

    We have 2 problems though which is why I am posting.

    1. It takes 1 to 4 "reboots" of the dongle to finally load AA (the light goes through the flashing green and flashing blue before resetting and trying again on its own).

    2. Once loaded phone calls through AA are in fast forward and sound like a chipmunk. Occasionally GPS also lags, I'm not using the infinite touch setting.

    I've spent hours tweaking the various settings and modes but haven't found a combo that fixes these issues.

    Appreciate any guidance!
    AA over CP is still very much beta quality. We'll add these issues to our backlog, but right now AA over CP has low prio.
    2
    Core feature or not, everyone knows it's capable of it.
    Nobody is asking for it to be fixed right away, simply acknowledged. @leroy_sunset had no replies to the post back in October and had a support experience that mirrored mine. I was even told "no other Polestar owner has reported this", which was quite clearly not true.

    I'm a developer Monday to Friday too, and if I brushed off paying customers with niche requirements, I'd not have a job.
    Hell, right now I and about a dozen other developers are working on a feature to be used by 1 customer.

    All I'm asking is that this issue, which clearly does exist, is treated correctly.
    It is treated correctly. It's on our backlog and does not have priority right now unfortunately. I do agree our support may have given false info though... So in that sense you have been brushed off. I'm sorry for that.
    1
    I never criticized the developers, once. I never communicated that my expectations were not met. I bought a product, tried it, found it didn't work for my very niche use case. It's beta, I get it. I'm not mad - a tad disappointed, but I am loading the beta updates literally every time they come through hoping it will work. I didn't return the product because I want it to work, I want to support the company, I want to help the developers get this working on my car!

    I will say - wireless CarPlay with an iPhone works perfectly on the Polestar! It's a cool product. I am just hoping that AA over CarPlay will come through some day. In no way do I want to discourage the devs - please, please keep trying to get AA over CarPlay to work on my Polestar! I'd pay 2x for it :D

    You guys don't even remotely put out a paperweight. You got me in the beta super quick, you're updating all the time. I definitely have a good impression of Snirpo and I know you'll sell plenty more of these once AA starts working on Polestars. The Polestar forums are dying to get something that works!
    1
    Well that did not work, because the phone, a Pixel 7A, turned both Bluetooth and Wifi back on :eek: Tried it numerous times in the car with same results, away from the car both settings remained off as expected. I also want to keep Bluetooth on for hands free phone calls.
    We can add a feature to disable AAW temporarily. Will probably add it as an "app shortcut" so you can place it on your homescreen.
  • 49
    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.
    21
    I used to get the same thing. I believe it is an issue with AA/Google rather than AAW. In any event, I have had to give up on AAW as I can't connect to it/won't update, just sits there with a constant light-blue light. It is a (very expensive) paper weight on my desk now. It is just "too Beta" for my requirements.

    I have now got a Carlink 2022 Android box which works flawlessly for me.
    MG ZS EV 2022
    Galaxy S21 Ultra (not rooted)
    I know I should ignore these posts, but these are the comments why I'm honestly considering completely dropping out any forum / reddit / social media. What's the point? We have support, we have warranty, we have a refund policy. It might be "beta" for you, but we shipped over 100k devices and believe me or not, for most, it just works. It's the same thing for all of these dongles. They will not work perfectly for all, there are just too many variables.
    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
    Very close to release of 2.1.0 now. We fixed the UConnect issue, except for some cases where you still have to re-plug the device, but this is also the case on the MA1.
    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.