AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
I went for a few trips in the GTI this morning and everything was great again in terms of AAW starting up on the screen, responsiveness and dropout free. I did think stop/start was fixed at the 2.0 FW but will see again maybe in 2.1.
The one issue that has been there for a long time is the Assistant being mute, and it happened again. First drive all good. Go into a store for a few minutes and second drive the Assistant can't be heard.
That's my only issue at the moment.
The one issue that has been there for a long time is the Assistant being mute, and it happened again. First drive all good. Go into a store for a few minutes and second drive the Assistant can't be heard.
That's my only issue at the moment.
One again to everyone with passthrough issues or in general having connection issues... Do the following and it will fix majority of issues.
Step zero: update your AAW to the latest firmware - if you've got issues connecting, there may be bug fixes that help.
Step one: DISABLE passthrough mode in your AAW app settings. Now
reset your AAW device using the small pinhole on the side of the device (hold for approx 5 seconds and you'll see the LED change/stop flashing etc so you'll know when it's reset)
Step two: WIPE YOUR ANDROID AUTO DATA on your device (in settings, search for android auto)
Step three: Clear your headunits Bluetooth connection to your phone.
Step four: Plug in your device to headunit and setup android auto.
Step five: Disconnect your phone and alter the android auto device settings to enable wireless AA (and other desired changes)
Step six: Now plug in your AAW device and set it up and connect (if it doesn't connect, simply open your Bluetooth connections and do it manually)
Step seven: Congrats, you're running AAW without passthrough mode and can now alter the settings within the AAW app.
Step zero: update your AAW to the latest firmware - if you've got issues connecting, there may be bug fixes that help.
Step one: DISABLE passthrough mode in your AAW app settings. Now
reset your AAW device using the small pinhole on the side of the device (hold for approx 5 seconds and you'll see the LED change/stop flashing etc so you'll know when it's reset)
Step two: WIPE YOUR ANDROID AUTO DATA on your device (in settings, search for android auto)
Step three: Clear your headunits Bluetooth connection to your phone.
Step four: Plug in your device to headunit and setup android auto.
Step five: Disconnect your phone and alter the android auto device settings to enable wireless AA (and other desired changes)
Step six: Now plug in your AAW device and set it up and connect (if it doesn't connect, simply open your Bluetooth connections and do it manually)
Step seven: Congrats, you're running AAW without passthrough mode and can now alter the settings within the AAW app.
Yesterday noticed very weird behavior.
Connection worked ~5-10 minutes and then dropped. And then aawireless started "bootlooping". Headunit showed to choose Android Auto or Mirrorlink (it did not restore previously chosen android auto like usual). Stayd ~10-20 sec like so and then lost again the connection. And it did not manage to show android auto even when I clicked to "android auto" on headunit. And this loop remained to the end of my drive. After few hours started another drive. At first it worked some time and after first drop, it started same "bootloop" again.
I don't know if it may be connected with enabling passthrough mode day before (because regular dongle mode still very unstable and trying different settings still...)
Connection worked ~5-10 minutes and then dropped. And then aawireless started "bootlooping". Headunit showed to choose Android Auto or Mirrorlink (it did not restore previously chosen android auto like usual). Stayd ~10-20 sec like so and then lost again the connection. And it did not manage to show android auto even when I clicked to "android auto" on headunit. And this loop remained to the end of my drive. After few hours started another drive. At first it worked some time and after first drop, it started same "bootloop" again.
I don't know if it may be connected with enabling passthrough mode day before (because regular dongle mode still very unstable and trying different settings still...)
Strange indeed, can you send in a bug report via help and support --> bug report? Please inform me if you did, then I can see what's happening
This failure sounds like the boot looping I am seeing. I uploaded a log to support ticket https://cpeb.freshdesk.com/support/tickets/28709 yesterday...maybe of some use.Strange indeed, can you send in a bug report via help and support --> bug report? Please inform me if you did, then I can see what's happening
You can try to update via another power source (laptop/power adapter). Some cars actively repower the device when AA is killed (which we do when starting OTA). In firmware 2.1.0 we removed the killing of AA, which will solve these issues.
I checked. For some reason your phone is disconnecting from wifi 10 seconds after the wifi connection has been setup. Do you have any apps running which may cause this? Like tasker?
Last edited:
no not tht i know of. Pretty much stock android an very little other stuff on top.
As I can understand "bug report" has to be initiated manually, like start driving, then enable bug report, if problem appears, then stop and send right?Strange indeed, can you send in a bug report via help and support --> bug report? Please inform me if you did, then I can see what's happening
Does bug report work when passtrough is enabled (as this problem I described, was when passtrough was enabled).
Today morning disabled passtrough, but still constant connection drops. Should I try to send bug report with passtrough enabled or disabled or both?
Just been back out and tried anything I could find to see if it made a difference.
So far nothing, just same connect then almost instant disconnect.
Tried:
1.Disabling Adaptive Battery
2.Turned off mobile network
3.Forgot my home wifi network incase it was trying to relog into that
4.Turned off "Turn on Wifi automatically" option in wifi preferences.
5.uninstalled the Wifi analyser i did have installed
Happy to try anything anyone else can throw at me.
So far nothing, just same connect then almost instant disconnect.
Tried:
1.Disabling Adaptive Battery
2.Turned off mobile network
3.Forgot my home wifi network incase it was trying to relog into that
4.Turned off "Turn on Wifi automatically" option in wifi preferences.
5.uninstalled the Wifi analyser i did have installed
Happy to try anything anyone else can throw at me.
Yes, passthrough is also fine, but the logging is less detailed. In this case it's probably fine though.
Can you possibly send a phone side log? I'll PM you my email address.
You can generate a log via developer settings of the phone: https://support.wizyemm.com/hc/en-us/articles/360059933253-How-to-generate-an-Android-bug-report
I am having basically the same issue with my 2020 Gladiator and the 8.4 screen, but with an S22. Mine had been working flawlessly since I got it and one morning it just stopped connecting. I am able to get it to connect after factory resets like you, but if I like the truck sit for a few hours and the USB power off, I am back to square one.
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.
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?
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.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5
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
Blue means working correctly, so you're ok.
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.
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
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.1I 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
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
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.Well that did not work, because the phone, a Pixel 7A, turned both Bluetooth and Wifi back on 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.
-
49This 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 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.16I 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!15We 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.
