Yes. Got my device with 1.7.0, but upgraded to 1.7.1. hoping it may solve the issue
AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
I have 2 AAWireless devices, and I had them both working flawlessly in a Hyundai Palisade for months. I upgraded the vehicle to a Genesis GV80, which some may know is a Hyundai "upgrade" product, and runs a very similar/same head unit as the Palisade. The software is a little different, but appears to have a very similar baseline and structure.
In the Palisade, the AAWireless devices were very stable, with a vary rare disconnect. In the Genesis, the devices seem to connect for maybe 10 seconds, bring up AA, then disconnect. It cycles through that cycle every 10 to 15 seconds. I tried changing available settings like USB etc in the app, with no change. I've tried multiple cables, including the one that worked in the Palisade, with no luck. I should note, if I plug the phone in using the same cables it works flawlessly, so tells me cable is good. I updated both to the newest firmware and that did not change anything. I note that I may have updated to newest firmware BEFORE trying in the Genesis, and mention because I see discussions on the newest version (1.7.1) having bugs)
The phone is a Samsung S20 Ultra, and is the same phone and settings I had with the Palisade. I did try to delete and reinstall the AAWireless devices, then the app itself, and once again no change.
Anyone have any thoughts on what to try? Really surprised me when it did not work in the Genesis given the headunits are both Hyundai and so similar to the Palisades
In the Palisade, the AAWireless devices were very stable, with a vary rare disconnect. In the Genesis, the devices seem to connect for maybe 10 seconds, bring up AA, then disconnect. It cycles through that cycle every 10 to 15 seconds. I tried changing available settings like USB etc in the app, with no change. I've tried multiple cables, including the one that worked in the Palisade, with no luck. I should note, if I plug the phone in using the same cables it works flawlessly, so tells me cable is good. I updated both to the newest firmware and that did not change anything. I note that I may have updated to newest firmware BEFORE trying in the Genesis, and mention because I see discussions on the newest version (1.7.1) having bugs)
The phone is a Samsung S20 Ultra, and is the same phone and settings I had with the Palisade. I did try to delete and reinstall the AAWireless devices, then the app itself, and once again no change.
Anyone have any thoughts on what to try? Really surprised me when it did not work in the Genesis given the headunits are both Hyundai and so similar to the Palisades
Last edited:
I have received the unit and was very satisfied with its operation, but I was very disappointed when I discovered that my phone has stopped recording calls when connected to the aawirelless, this for me is very important to have this recording function the calls, before putting the aawirelless if it had the function of recording calls having connected by bluetooth to the car radio.
My phone is a xiaomi Mi 10T Pro, with android 11 system, room xiaomi.eu, with native dialer and active call recording.
Please, it is very important for me to be able to record the calls for my work, I need to know if this bug has any solution, thank you very much for the help.
My phone is a xiaomi Mi 10T Pro, with android 11 system, room xiaomi.eu, with native dialer and active call recording.
Please, it is very important for me to be able to record the calls for my work, I need to know if this bug has any solution, thank you very much for the help.
Last edited:
Upgraded firmware to 1.7.1, started having constant connection issues, and now AAW no longer works at all. (cannot connect to AAW device, AA no longer starts) Please revert device tPCsvA0Oto 1.50, thank you
It helps a lot: No more interrupts, drop-outs.....
Thanks a lot again!
Is there a reason for the problems with 1.7.1 and the first GEN of AAW? The board?
To be honest, I don't know at this point. We have over 3800 boards now on 1.7.1 and very few tickets of issues with 1.7.1. Anyway, we're stopping updates for the old boards for now to investigate.
Last edited:
That did it, thank you.
Guessing mine is first gen, last batch of that run I recall correctly. Rarely having issues, initial connection issues usually only happen due to automated timing issues on my device. I'll stick to 1.50 for now, thanks again.
I have a 1st gen unit currently running on firmware 1.7.0. I get the disconnect issue at one specific location every time without fail.
I keep a Faraday pouch in the car for my key fob for when I'm at the self serve car wash. Today I decided to place my AA module in it to see what would happen. Long story short, no more dropouts and much easier than lining the housing with foil tape.
I keep a Faraday pouch in the car for my key fob for when I'm at the self serve car wash. Today I decided to place my AA module in it to see what would happen. Long story short, no more dropouts and much easier than lining the housing with foil tape.
Hi festor,
My PC unfortunately does not have Wi-Fi, after borrowing a laptop and struggling with transferring the web link to no avail, I searched for the Wi-Fi AA wireless radio network.
When I print the mail to PDF, the web link no longer works.
The AA-Wireless* network does not show up.
As soon as there is power on the device the green LED goes on permanently and then flashes 3 times each.
A Bluetooth connection is present and I can change the settings.
Neither with or without Force 2.4 Ghz I see the network on the laptop.
The phone is permanently searching for Android Auto.
Best regards
Roland
Translated with www.DeepL.com/Translator (free version)
Is there going to be a way for us to choose when to downgrade/upgrade etc coming? Cause it really does seem like some cars just run better on "insert X version here" would be great being able to experiment.
hi, i received the device yesterday and had a big problem. after connecting to the usb the green led flashes but no bluetooth connection is possible and therefore no wifi either. no change in a connection even after several resets. bluetooth has been tested with various devices, none of which has been successful.
maybe someone has a solution to this problem.
Thanks in advance
maybe someone has a solution to this problem.
Thanks in advance
+1 connection problem. AAWireless never connects to Wifi. There is no AAWireless-XXXXXX wifi network visible. Bluetooth connection works fine, settings can be adjusted. LED is flashing green after booting (constant green).
After plugging AAWireless in for the first time, first thing I did was to update. Worked fine from 1.3.0? to 1.7.1
But afterwords, I did never get a blue light. Never saw a AAWireless Wifi network. Resetting, un-pairing-pairing, deleting cache and data etc. does not solve the problem. Downgrading to 1.5.0 is not possible, because the App won't connect to the device.
After plugging AAWireless in for the first time, first thing I did was to update. Worked fine from 1.3.0? to 1.7.1
But afterwords, I did never get a blue light. Never saw a AAWireless Wifi network. Resetting, un-pairing-pairing, deleting cache and data etc. does not solve the problem. Downgrading to 1.5.0 is not possible, because the App won't connect to the device.
I think the problem ist not only at a "few" boards of the first batch. Do you see how many customers of this GEN updated to 1.7.0/1.7.1? How much percent of them use this? I think there could be many more with this problem but the most of them have not used this FW, or dont update to any new version or are not interested for searching for the issue and dont report them to you. Not all of this users trying to keep in contact in this board to you or your App.
Yes, we can see exactly how much boards of each model are updated to a certain version.
If people are having issues after an update we should see that back in the tickets in our support system / XDA / Reddit, we monitor all these sources.
If that's not the case, it means we can never push any update anymore. We do test updates internally, but there will always be cases where a certain update breaks for some and not for others.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4
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.
