Any thoughts on GA for 2.1.0? (another Hyundai / Kia owner that has just upgraded to get widescreen Android Auto on the headunit)
AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
I can tell that switching to pass through is currently a good workaround
But I have the problem that the connection sometimes takes longer then my driving time.. sometimes it connects instantly.. The WiFi timeout is already set to 5 seconds Have the feeling this started after upgrading to one of the 2.X firmwares.
Last edited:
Thx. I'll go on pass through. Long drive planned today so let's see how that goesI can tell that switching to pass through is currently a good workaround
I'm on a Hyundai. So far passthough is a workaround since I upgraded the infotainment for AA widescreen but it does take a variable amount of time to connect. I'm also keen to get the DPI higher (I set it at 180 on an ioniq 5). Makes the AA interface look so much smarter rather than a kids toy! Hope we can get an update soon to fix it.
Hi all, I just get the phone to download 2.0.2 firmware. My device firmware is 1.8.0 and app won't download the update whatsoever. I click download and then nothing...again the start download comes up...I hit it again..still nada...any suggestions? I deleted the data and cache in the app and even forced stopped it..still no use...
Reboot phone to connect
I would like to share my experience. Just found this morning that AA does not connect to my phone. Restarted AAW a few times: no joy.
Only after I rebooted my phone, it connected without a problem.
Inspecting the phone revealed that Maps had been updated last night (to version 11.36.2). I recall that I had to reboot the phone a few weeks earlier in order to connect.
Would the update of Maps cause this?
Anyone else saw this on his/her phone?
My AAwireless: 2.0.2
My phone: Poco X3 NFC (rom: Pixel Experience Android 12.1)
My car: MG EHS PHEV 2021
I would like to share my experience. Just found this morning that AA does not connect to my phone. Restarted AAW a few times: no joy.
Only after I rebooted my phone, it connected without a problem.
Inspecting the phone revealed that Maps had been updated last night (to version 11.36.2). I recall that I had to reboot the phone a few weeks earlier in order to connect.
Would the update of Maps cause this?
Anyone else saw this on his/her phone?
My AAwireless: 2.0.2
My phone: Poco X3 NFC (rom: Pixel Experience Android 12.1)
My car: MG EHS PHEV 2021
Last edited:
Maybe I'm not doing it right, but I don't see 1.8 as an available option when I go to System Update.
On the dev app, it says the same thing for current and latest: 2.1.0-202206240850-develop-516470d-develop-6803c38f.
In the regular app, it just says no update available. What is the correct way to rollback to 1.8? Thanks.
What is actually the difference with or without the passthrough mode ?
I've been using it since the beginning because I had some diconnections problems in normal mode, and never tried again without it.
Is it better without it ? and, if yes, why ?
When using passthrough mode most settings in the app like DPI, the sink stuff and co will not work as everything is directly routed to the phone.
Does anyone know if on 2.0.2 the SSL fix was applied? I'm still on the dev aawireless app + firmware update "channel" where everything works fine but I do not need daily updates and if it's on the stable I would revert back to stable "channel"
Passthrough mode will send all data unmodified to the dongle. This should work all the time, everywhere. Using it in combination with dongle mode should be fine for everyone. Downside is, you can't use any advanced features like DPI settings with it
Without passthrough mode, you could use the extra features in the app. And for me connection without passthrough, is much faster.
Ok, thanks for your answers. I'll try it when 2.1 firmware will be available (I'm KIA user, and apparently version 2.02 doesn't work properly with last unit update)
AFAIK the SSL fix is only in 2.1.0, but I also understand that using Passthrough on 2.0.2 works as well.
Unless there's a wireless charger in the car, AA wireless is a failed cause due to the obscene battery drain. 1%/ min is just ridiculous.
Sorry, accidentally enabled develop instead of 1.8, 1.8 should be enabled now.
Similar threads
Top Liked Posts
-
5@Snirpo
I just want to say thank you to you and your team for your hard work and the device.
I have it now since end of October 2021. I use it nearly every day.
The successful connection rate is at around 98-99% in my case. For the other 1-2% there is always support from your side. Thanks for this.
Don't listen to inpatient people. Everybody wants to have everything right away. Waiting is something people don't know any more today in the globalised world. Don't listen to these guys.3
There. I've fixed it for you!
Mine works perfectly 99% of the time, & when it doesn't seem to work, rebooting the HU or phone fixes it. That tells me where the problem is.
Too many people have unrealistic expectations of wireless communications (that includes Bluetooth). As a Amateur Radio licensee for fifty years, I understand the frustration. However, it's the nature of radio communications. -
16
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.9
I remember a post from a guy with the classic “I've been in the industry for years” claim. He said that because he had a weekly internal briefing at his workplace, you should be doing the same for us here. If you give an inch, they want a mile.
Then you have all the narcissistic Karens with zero patience that say whatever they think will get your attention so they can jump the queue. Even when you (quite rightly) post that firmware will now be staggered with no release announcement, you have an immediate request from someone with “faulty” units asking you to announce when the release will start!?!
It must be incredibly frustrating and every rational user will understand. Even if you decide against stepping back permanently, please take a lengthy break.98 -
41This 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.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!16
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.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.14
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.Hello. What's new in 1.5?
A full changelog for each release would really be appreciated
Thanks for all the hard work!
