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...
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...
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.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...
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 thinkI 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!
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.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!
Might try out these settings also in AA.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!
Of course, because if you USB connect your phone, that means that you intend to use AA !...
This is not enabled.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
This sounds logical. I created a bug report.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.
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.Of course, because if you USB connect your phone, that means that you intend to use AA !...
Hmm, still don't see 1.8 when I go to System Update. It just says no update available. AAWireless-aTaNRlUXSorry, accidentally enabled develop instead of 1.8, 1.8 should be enabled now.
Hello, maybe I'm late to the party but I came across your post.Thanks for the input Snirpo, just for the sake of curiosity I will swap to default mode.
I have lags and audio chopping also (when two apps collides) but afaik that is a HU hardware limitation.
I've got used to them so they don't bother me thaaat much, but solving random disconnects would be fantastic.
Happy to help with logs or anything else that helps this wonderfull project.
How/where do you do that ?
Have a look here
Hi @bertsmelik,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
Many thanks, I omitted the post...
PE is not MIUI, IT is a custom rom baard on AOSP and Pixel. Gui is from Pixel.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?
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
Any idea when Firmware 2.1.0 will drop into stable and get rolled out? Very much looking forward to it!Yup, this is fixed on 2.1.0, which is in beta. You can use passthrough mode in the meantime.
How do I get the 2.1.0 beta?Yup, this is fixed on 2.1.0, which is in beta. You can use passthrough mode in the meantime.
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.
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.
We hopefully have the final version now. Prototypes will soon be sent out to testers for real life testing. With no major issues I expect end of Q2/Q3 for mass production.btw, any updates on AAW 2? Kinda wanna offer one to my sys but at the same time want the new shiny toy for myself xD
Agreed, is implemented in latest internal beta version of the app. I'll release it to public beta tomorrow.I agree text box or even arrows left and right that you can adjust the numbers
This is the app version. But yes, CarPlay (BETA) has also been released a while ago in firmware version 3.0. We are now at 3.3.2.
Yeah is a change in AA, nothing we can do about it, same happens on TeslAA.I've been using DPI 135 for months for my 8.4-inch screen on a GM MyLink2 system. Since the last Android Auto update, the icon bar has returned to horizontal and only goes vertical if I set the DPI to 103, but then everything becomes too small. Anyone else experiencing this issue?
for me, horizontal bar takes up too much spaceI'd been using 133 on mine, but I'm trying to live with the horizonal bar at 115 now.
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.I used to get the same thing. I believe it is an issue with AA/Google rather than AAW. In any event, I have had to give up on AAW as I can't connect to it/won't update, just sits there with a constant light-blue light. It is a (very expensive) paper weight on my desk now. It is just "too Beta" for my requirements.
I have now got a Carlink 2022 Android box which works flawlessly for me.
MG ZS EV 2022
Galaxy S21 Ultra (not rooted)