AAWireless - General discussion and support

Search This thread

amirage

Senior Member
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.
 

Swap_File

Member
Apr 12, 2016
37
28
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.
 

sidamos77

Senior Member
Nov 8, 2012
667
149
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!
 

TheUntouchable

Senior Member
Jul 14, 2010
1,198
286
Germany
Huawei P30 Pro
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!
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:

Snirpo

Senior Member
Jan 23, 2007
431
526
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!
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.
 

sibesaver

Senior Member
Sep 30, 2010
129
46
Moore, OK
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.
 

Attachments

  • Screenshot_20220702-120624.png
    Screenshot_20220702-120624.png
    184.5 KB · Views: 37

sidamos77

Senior Member
Nov 8, 2012
667
149
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 is not enabled.
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 sounds logical. I created a bug report.
Might try out these settings also in AA.
This is on default (let car decide).
Of course, because if you USB connect your phone, that means that you intend to use AA !...
Of course. Still, when I connect via USB (maybe to only charge), I can deny once and then the question does not come back.
 

Marsou77

Senior Member
Feb 2, 2011
1,468
350
Earth
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.
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 :)
 
  • Like
Reactions: elbubi

valeri_s_k

Senior Member
Aug 24, 2020
51
15
Bourgas
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
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?
 

bertsmelik

Senior Member
Jan 12, 2014
124
45
Ridderkerk
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?
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.
 

elbubi

Member
May 12, 2013
33
6
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 :)
Thanks for the tip Marsou.
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!
 

Top Liked Posts

  • 6
    I 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 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)
    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.
    12
    Very close to release of 2.1.0 now. We fixed the UConnect issue, except for some cases where you still have to re-plug the device, but this is also the case on the MA1.
    9
    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 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.
    8
    @[email protected]:
    Please stop spamming this thread !
    6
    It's been 'next week' for the last 3 or 4 weeks!
    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.
  • 41
    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 should be expected as well as support from the developers of the product: @Snirpo and myself.
    18
    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)
    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.
    16
    I 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!
    15
    We 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
    Hello. What's new in 1.5?
    A full changelog for each release would really be appreciated :)
    Thanks for all the hard work!
    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.