AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
Thanks Snirpo. I can confirm the 2.1.0 24/6/22 beta build works fine with intercept and DPI changes on my Pixel 5 and IONIQ 5 with the widescreen AA update. Will test stability of the connection but I'm expecting it to work as well as 2.0.2. I do notice my phone is warmer when on intercept than on passthrough. Probably higher battery drain too.
Hmm passthrough vs intercept shouldn't really matter batter drain wise. Except possibly when the dpi has been changed.
Nice car btw
Can I ask that is the domain name of the download server when downloading firmware updates? It seems that my NextDNS installation is blocking the download of the firmware update and I would like to know which domains should I whitelist.
Edit: checking the logs it seems that whitelisting *.contabostorage.com did the trick
Edit: checking the logs it seems that whitelisting *.contabostorage.com did the trick
Last edited:
Just to leave it here, 2.1.0 is working like a charm for me since 3 weeks or so. Not a single issue. I love it 
Same here. No issues, no complaints.Just to leave it here, 2.1.0 is working like a charm for me since 3 weeks or so. Not a single issue. I love it
I ran into a weird issue. Any time I use Google Nav, I can only control the voice volume and lose media volume control.. This does not happen when I unplug the dongle and use a wired connection.
I created a separate thread, but wanted to see if I might get any traction here. I realize this is not an AAWireless issue but I also ran into and issue when using YT Music in Drive mode/Android Auto it shows that it is 'offilne', and only allows me to play music that I downloaded to the device (Pixel 6 Pro) however when using the app itself it shows to be online. This only occurs in Drive Mode and Android Auto. I have 'Stream via Wi-Fi only' set to the off position. Is there something else I should check? If I bypass AA and use YT Music straight through Bluetooth it works fine.
Anyone experience this?
I created a separate thread, but wanted to see if I might get any traction here. I realize this is not an AAWireless issue but I also ran into and issue when using YT Music in Drive mode/Android Auto it shows that it is 'offilne', and only allows me to play music that I downloaded to the device (Pixel 6 Pro) however when using the app itself it shows to be online. This only occurs in Drive Mode and Android Auto. I have 'Stream via Wi-Fi only' set to the off position. Is there something else I should check? If I bypass AA and use YT Music straight through Bluetooth it works fine.
Anyone experience this?
I'd love to be on 2.1.0 Beta too. Stuck on Kia/Hyundai Widescreen Update.
Device: AAWireless-ka7FPOIF
Device: AAWireless-ka7FPOIF
Guys with Kia/Hyundai Cars and Widescreen: Just activate the passthrough options in AA Wireless App if you don't use options like DPI or sink changing, this will fix the problem.
Yeah it fixes the connectivity issue. But it takes a whole lot longer to connect to AAW - at least in my case.
I had that long connection problem also before that update of my Kia Navi Firmware and not running in passthrough mode..
And I have it still with the beta firmware of the AA device.Guess thats no good news for me then...I had that long connection problem also before that update of my Kia Navi Firmware and not running in passthrough mode..
Anyway it would be nice to use AAW with Widescreen and with my own dpi settings and without the tap restrictions.Would be more than happy to report issues and give some field reports on the beta Version.
Similar threads
Top Liked Posts
-
6I wanted to add my thanks to @Snirpo and his team. They've been working tirelessly to get everything working for everyone. When you think about all of the combinations of phones, Android versions (including non-standard ROMs), Android Auto updates, head units (not just an auto manufacturer but the changes those manufacturers make to their own systems year after year, and updates) plus aftermarket systems - it's staggering how many different things have to all "just work."
I know forums are often the place people come to report their problems and ask for help, and having been on the receiving side of it myself it can sometimes be overwhelming and disheartening.
So kudos to the AAW team for everything they've done! -
18
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.86
I'm sorry, that's because we are stuck on the UConnect issue: https://github.com/cpebit/aawireless-issues/issues/128 . We were hoping to fix this issue much sooner, but it's a very hard one. Therefore we decided to lock UConnect to 1.12.0 and release 2.1.0 anyway. Possibly we should've made this decision earlier, but we didn't.
Again, for most 2.1.0 will not matter in any way. Mainly for cars with SSL related issues, so non-passthrough mode will work again.
With about 100k devices, we cannot just release a firmware anymore. We need at least a few weeks to test it properly. If we make a mistake it will overload support and it can harm us a lot.
I'm so stupid to say it will be released "next week" every time. From now on we will not give any ETA's anymore. It's done when it's done.
Also, when we push an update. It will be rolled out incrementally. At this point we cannot do mass roll outs anymore (except for bug fix releases), because there are too many variables. So even when we release this week, it may take a while for you to actually get the firmware. -
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.18
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.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!
New posts
-
-
-
Development [ROM][OFFICIAL][OnePlus 9 Pro][12.1.0_r22]Nameless AOSP[2022/08/14]- Latest: chandu dyavanapelli