Also depends on what apps your running btw. But this is the nature of the beast unfortunately. Wifi + Bluetooth + mobile data + video rendering is a drainer. I've never seen 1 percent battery a minute before though...
AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
Might I add the type of device to the list you have mentioned above? It seems the device chipset also has a major play in the drain. Apparently, mid-range chipsets perform better than high-end ones when it comes to AA wireless. FYI, I was running Waze and Tidal on my 20 min drive home. Started the trip at 70%, and arrived home at 49%...anyways, the moral of the story is wireless aa is as good as the wireless charging capabilities of the car. I wonder how the situation is with wireless Apple carplay.
This isn't a AAwireless problem, just another observation of running a hot spot while using AAwireless. I'm on an OnePlus 8Pro running android 12, version c21.
I noticed that if I save AAwireless's password, connect to AAwireless and then try to use my phone's hot spot functionality, my phone will default to trying to share my non existant wifi internet. This shows up as "WiFi sharing" in the notification.
But if I don't save the connection, and let AAwireless connect on its own, my phone's hot spot will default to sharing my mobile data connection. This shows up as "Mobile hot spot" in the notification.
I noticed that if I save AAwireless's password, connect to AAwireless and then try to use my phone's hot spot functionality, my phone will default to trying to share my non existant wifi internet. This shows up as "WiFi sharing" in the notification.
But if I don't save the connection, and let AAwireless connect on its own, my phone's hot spot will default to sharing my mobile data connection. This shows up as "Mobile hot spot" in the notification.
I just got AAWireless and it works fine on default settings with my Samsung Galaxy A52s and Renault R-Link Evolution.
One thing is a bit annoying: When connection is established, the car unit asks if I want to start Android Auto. If I say NO, the same question comes again 10s later. This does not happen with the USB cable connection.
Any workaround for that? Thanks!
One thing is a bit annoying: When connection is established, the car unit asks if I want to start Android Auto. If I say NO, the same question comes again 10s later. This does not happen with the USB cable connection.
Any workaround for that? Thanks!
I think there is an option called "Auto Video Fokus" in the aawireless app. Try to disable that if activated, its disabled by default. ALso there is a option in the Android Auto app for starting itself when connected I think
Last edited:
I think this is because it's thinking the connection has failed, it will then restart the connection in 10 seconds. Not sure if this happens because of the phone side or AAWireless itself. Could you possibly shoot in a bug report via the app? (Help and support --> bug report). So I can check what's happening.
Might try out these settings also in AA.
Attachments
Of course, because if you USB connect your phone, that means that you intend to use AA !...
This is not enabled.
This sounds logical. I created a bug report.
This is on default (let car decide).
Of course. Still, when I connect via USB (maybe to only charge), I can deny once and then the question does not come back.
Hmm, still don't see 1.8 when I go to System Update. It just says no update available. AAWireless-aTaNRlUX
Hello, maybe I'm late to the party but I came across your post.
Lately I have tested a lot of configuration settings with my AAW and a NAC Wave 2 (Peugeot 208) and the most suitable I found is the following
-- AAW settings:
* Passthrough disabled
* Dongle disabled
-- Phone settings
* Google Driving Assistant disabled
Everything run really well, almost no lag when listening to Spotify and navigating with Maps. No disconnection either.
Hope it can help
Have a look hereHow/where do you do that ?
AAWireless - General discussion and support
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...
forum.xda-developers.com
Hi @bertsmelik,
It is known MIUI has an issue with wireless AA by cutting wifi when losess/reconnects to mobile network.
How it is with PE?
Can you test it - when connected to wireless AA try to disable/re-enable mobile data and see if AA disconnects?
Many thanks, I omitted the post...Have a look here
AAWireless - General discussion and support
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...
PE is not MIUI, IT is a custom rom baard on AOSP and Pixel. Gui is from Pixel.
WiFi works very well in PE. Trier tout suggestion, but no différence.
I can live with this phenomenon, just reboot in case of aaw connection Problem.
Thanks for the tip Marsou.Hello, maybe I'm late to the party but I came across your post.
Lately I have tested a lot of configuration settings with my AAW and a NAC Wave 2 (Peugeot 208) and the most suitable I found is the following
-- AAW settings:
* Passthrough disabled
* Dongle disabled
-- Phone settings
* Google Driving Assistant disabled
Everything run really well, almost no lag when listening to Spotify and navigating with Maps. No disconnection either.
Hope it can help
I've tried that combination in the past (actually using passthrough enabled + dongle enabled), and still had lags and hiccups.
Had tried with cable and no lags or chopping sound neither, so its not a HU hardware limitation as I previously thought.
Nevertheless, I will try it again and report back.
Cheers!
Any idea when Firmware 2.1.0 will drop into stable and get rolled out? Very much looking forward to it!
If you pass me your devices names (AAWireless-xxxx), I'll enable it.
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!
