AAWireless - General discussion and support

[alexalex1989]

I had problems with disconnects when the mobile signal changed. It is a known issue with Xiaomi / Poco phones. I can now confirm that it works after flashing the PixelExperience custom ROM.

 

[SOFO888]

@Snirpo
Just (perhaps) a stupid question: is it also possible to add another device to AAWireless Wifi?

For explanation: I ordered a dashcam. I did not receive the dash cam yet.
The dashcam provides the possibility to get connected to a WiFi router so that I can download the files and live view the dash cam. But it's not possible to be connected to AAWireless Wifi and have another hotspot or Wifi connection at the same time with my phone. Therefore my idea was to connect the dash cam to the same Wifi like my phone (in this case the AAWireless Wifi).

 

[Snirpo]

@Snirpo
Just (perhaps) a stupid question: is it also possible to add another device to AAWireless Wifi?

For explanation: I ordered a dashcam. I did not receive the dash cam yet.
The dashcam provides the possibility to get connected to a WiFi router so that I can download the files and live view the dash cam. But it's not possible to be connected to AAWireless Wifi and have another hotspot or Wifi connection at the same time with my phone. Therefore my idea was to connect the dash cam to the same Wifi like my phone (in this case the AAWireless Wifi).

Yes you can, AAWireless hosts a hotspot. Password of the hotspot is uppercased sha1 of the full SSID. I don't know what performance impact this has though. But I expect none, cause the wifi has more than enough bandwidth.

 

[SOFO888]

Thank you Snirpo for the fast response.
I will try it out as soon as I have the dashcam.

 

[JaGuR]

Have you tried a different cable ?
A decent quality cable

 

[elbubi]

Glad at least results are consistent among us. Tried it again today with 01181615, tried dongle on/off and passthrough on/off.
Same as yestarday, much worse audio performance and sluggish interface response.

I know its not AAW to blame for this, its the shi*ty NAC 2 HU, I truly hate it.

Do you want me to roll back to 2.1.0 or do you prefer me to stay in beta channel to try new approaches?

Regards!

@Snirpo

Sorry to bother you, do you think you can drag me back to v2.1.0 or do you prefer me to stay on beta chanel to try any other firmware?

 

[bloodhound42]

@Snirpo was the firmware 2.2.0 released ? My AA wireless is showing 2.1.0 only

 

[Snirpo]

@Snirpo

Sorry to bother you, do you think you can drag me back to v2.1.0 or do you prefer me to stay on beta chanel to try any other firmware?

I enabled the normal beta version for you know. Can also put your back on production.

 

[Snirpo]

@Snirpo was the firmware 2.2.0 released ? My AA wireless is showing 2.1.0 only

2.2.0 only adds compatibility for European production devices. It's functionally same as 2.1.0. Hence not enabling it for everyone.

 

[elbubi]

I enabled the normal beta version for you know. Can also put your back on production.

Ok @Snirpo thanks! I will stay on develop fw by now, will let you kwow if I need to go back to production chanel.

Regards and thanks!

 

[italodance]

There is a bug with new AAWireless app update, its Wi-Fi channel is 149 now and if you try to set it as auto it never connects anymore until reset it manually.

Edit: I could set it to higher range but Auto is impossible.

 

[italodance]

By the way, is there any manual instructions for the App companion?!
I don't know what kind of settings these are.

 

[Snirpo]

There is a bug with new AAWireless app update, its Wi-Fi channel is 149 now and if you try to set it as auto it never connects anymore until reset it manually.

Edit: I could set it to higher range but Auto is impossible.

This is not a bug, but a feature. From extensive testing we decided to make channel 149 the default for countries where it's supported. Interference is less on the upper channels (that's probably also why it's the default on the MA1). We probably should remove "Auto" though, because the app will indeed automatically move the channel back to 149. In the previous app version "Auto" actually used to be hardcoded channel 40. It was never really "Auto" before. Should've been called "Default" or something. So it's now actually more "Auto" then it was before

However, not working on 149 is not correct. Can you give me the name of your device (AAWireless-xxx or AndroidAuto-AAWxxx)?

EDIT: We removed this functionality for now in app version 3.12.0. Apparently it causes issues for some phones. Surprising, because this functionality has been in open beta (8000+ users) for over a month with no reports of issues.

 

[italodance]

This is not a bug, but a feature. From extensive testing we decided to make channel 149 the default for countries where it's supported. Interference is less on the upper channels (that's probably also why it's the default on the MA1). We probably should remove "Auto" though, because the app will indeed automatically move the channel back to 149. In the previous app version "Auto" actually used to be hardcoded channel 40. It was never really "Auto" before. Should've been called "Default" or something. So it's now actually more "Auto" then it was before

However, not working on 149 is not correct. Can you give me the name of your device (AAWireless-xxx or AndroidAuto-AAWxxx)?

EDIT: We removed this functionality for now in app version 3.12.0. Apparently it causes issues for some phones. Surprising, because this functionality has been in open beta (8000+ users) for over a month with no reports of issues.

Tnx for the update, I just saw it in Play Store.
But the bane of my device changed after resetting. (?!?!)
It was AAwireless-xxx , now changed to AndroidAuto-AAWxxx?!

It doesn't supposed to change?! And what's the difference?

 

[SOFO888]

Just for correction: bane should be name.
It's the name of the WiFi network of AAWireless.

 

[Snirpo]

Tnx for the update, I just saw it in Play Store.
But the bane of my device changed after resetting. (?!?!)
It was AAwireless-xxx , now changed to AndroidAuto-AAWxxx?!

It doesn't supposed to change?! And what's the difference?

AndroidAuto-AAWxxx means your device is in dongle mode, that's how it's triggered, by the AndroidAuto-xxx. That's what you normally want, and is default on new devices. The reason why we still have "normal" (native wireless HU emulation) mode as well has multiple reasons.

1. Device priority from AAWireless itself won't work in dongle mode, because how Android Auto is designed to work in dongle mode.
2. Because dongle mode didn't exist before the MA1 was released, so we kept it as an option to turn it off. This is to avoid potentially breaking people's setups when updating their device. When it's off, it will stay off on firmware update, until you reset the device or switch it off manually.
3. For some phones / cars, for some reason, in dongle mode it will just never start up AA. We have no idea why, it doesn't make any sense, we have yet to see a pattern. Turn it off and it will work fine. These kinds of issues come and go, so is probably just brokeness in Android Auto itself.

 

[Diesel80]

Hello @Snirpo I'm from Italy, and having some issue.

The scenario information are:
Veycle Toyota RAV 4 2022
Device Xiaomi Mi 11T 5G - Android 12, latest official global miui 13 (No rooted)
Google android auto 8.6, trough playstore no beta channel
Device AAW51381c93

1) One time on 3/4 time the AA don't start and need to delete from car and phone the BT and Wifi network, cycle restart of phone, dongle or car

2) Sometime that's happens to while running AAwireless after 30min and have a start-stop AA every 5minutes or need to do the correction on step 1

I have read this forum these days ant find that the best combo is
- USB mode standard
- Dongle mode Off
- Passtrught off
- Start/stop off ( my car don't stop usb power when engine stop becouse hybrid engine)
- Wifi 5Ghz, put ch 149 and region "italy"

Last test i have done yesterday:
Clean data\cache for compaion app and Google AA
remove any reference for wifi-bt from car and phone
Put no battery restriction on Google AA and companion APP (also auto start)
Reset dongle to factory default (UPDATED, sorry i have forgot it first time i post)
Follow wizzard from companion app for first setup for dongle and Google AA.
Unit working flawless

Today morning AA didn't start in any way. Need to put phone on cable, AA started immediatly and after disconnect phone by cable and re-connect the dongle to same cable AA wireless start

I have notice during the falling start of AAWireless there usually one of two by BT or Wireless don't connect, and if l try manually ask for password (mostly of time wifi).

Can i try the new firmware fer EU region?
Is there a way i can provide some debug information?

PS: Cable connection is rock solid, and have used the cable provided by unit to test if was a cable problem.
With previus car (ford ecosport 2019) i have used same unit with another phone (Mi 10T) and the actual phone.
The behavior was the same. cable connection rock solid. AAW sometimes dont start until reset veycle too. I was thinking was a ford problem (very poor infotaiment). Now i think the problem is unit itself, but im pretty sure the unit is fully functional, and is something related to software.

Thank you in advance

 

[italodance]

I noticed if I set Dongle Mode, it has delay in connection like 3 or more minutes, so I forget it.
And if I disable it, it connects in seconds but sometimes my phone recognize it as a Bluetooth headset which results in low volume (but like as I said sometimes).

Really confused. Any fix possible for this behavior?!

I moved to "Disabled Dongle Mode" anyway.

 

[Snirpo]

I noticed if I set Dongle Mode, it has delay in connection like 3 or more minutes, so I forget it.
And if I disable it, it connects in seconds but sometimes my phone recognize it as a Bluetooth headset which results in low volume (but like as I said sometimes).

Really confused. Any fix possible for this behavior?!

I moved to "Disabled Dongle Mode" anyway.

I'll test on Xiaomi Mi 10T on Monday now. It used to work fine, but I haven't tested for a while on Xiaomi. Delay of more than 3 minutes is not normal. But yeah in general, Xiaomi and Huawei phones are problematic with Android Auto Wireless.

EDIT: OK, I got the Xiaomi Mi 10T from the office. It still had MIUI 12.5 installed. Tested a few times, works perfectly fine. Upgraded to MIUI 13, it was a bit wonky at first, but tried multiple times from cold boot (with dongle mode enabled) and it seems fine. So I have no real explanation for these issues. We could replace the device, but I'm not sure it would help to be honest. Anyway, if you want to try, please contact [email protected] for a replacement.

A video of how it should work (on AA version 8.6.625054):

 

[urmanio23]

Maybe @Snirpo can help me with a question. My phone that the bug that makes AAw disconnect when cellular data fails or changes (roaming switching, etc)

Could there be an option to make AA start automatically after reconnecting to the phone? Right now I have to click/touch the AA icon on the infotainment screen.

I have a Peugeot 208, recent model and a POCO F4 with MIUI 13.

Thanks in advance.