AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
I noticed a change in the AAWireless (dev) app:
However, my phone reports ~30MB mobile data usage for AAWireless (dev) after a 1h drive today.
My device is AndroidAuto-AAWuU9qZkbW
Guys, how do I get Aawireless syslog file? I have been trying address 10.42.1.1:8000/syslog from my mobile when Aawireless is connected/in use in my car, with no success.
Can someone teach me how to do it?
Can someone teach me how to do it?
I intend to update my phone to either VIVO X FOLD or OPPO FIND N phone.But I see posts in xda forums of these phones and Android Auto saying Android Auto is not working in these phones either using USB Code or Wirelessly.So,can I get Android Auto working in these phones if I purchase Android Auto Wireless Dongle and without ROOTING THESE PHONES?
Anybody please advise.
Waiting with thanks....
Anybody please advise.
Waiting with thanks....
I recently switched from a Huawei P20 lite (Android 9) to a Samsung A53 (Android 12) and also could not download the syslog. With Android 12 the special WLAN configured and used by Android Auto seems to be "very special" since it is not listed in the saved WLANs and apparently does not allow a browser to connect to the AAWireless box and download the syslog.
Somehow though, I managed to do it, involving the following
- turn off headunit to prevent Android Auto from taking over (just turning off Bluetooth on the phone did not work, since AA turned it on again)
- configure the WLAN for the AAWireless box manually (I still had the WLAN password from using the Huawei P20 lite) - you may need to contact support to get your WLAN password
- turn off mobile data to prevent the browser from trying to connect to the AAW box over mobile data
- connect to the AAWireless WLAN
- open http://10.42.1.1:8000/syslog in the browser and download the syslog
Nobody seems to answer by humble question quoted below.Anyone please give me the advice whether Android Auto will work with VIVO X FOLD or OPPO N FIND FOLD Phone.
Waiting with thanks...
Waiting with thanks...
what is best settings for skoda scala with samsung s22 ultra, everymorning my connection is losting after 5-15 minutes..
Connection come back after 30-90 seconds..
Connection come back after 30-90 seconds..
Last edited:
If they don't work with Android Auto via USB cable or wirelessly then they will also not work with the AAWireless dongle.
Last edited:
Thank you martin.armstrng for your reply.But seems that you have not understood my question correctly. What I want to know is that whther Android Auto work in VIVO X FOLD or OPPO FIND N FOLD or Mi MIX FOLD phone either with USB code or wirelessly.If Android Auto does not work in these phones I have to purchase a Samsung Fold phone.So please be kind enough to clarify this.
Waiting again with thanks...
Connect through wifi (wifi password is the uppercased sha1 of the SSID). Then download from http://10.42.1.1:8000
What is default wifi password for my device?
_vNcssAPe
My phone (Samsung S21+) lost wifi connection with device sometimes every 5 min, sometimes every hour and etc sometime every 10 sec
FW: 2.1.0
S21+
VW TOUAREG 2019
Vag Fix Enabled
Ugreen Cable, Samsung cable - no effect
i have changed wifi chanles 149 153 etc no effect
_vNcssAPe
My phone (Samsung S21+) lost wifi connection with device sometimes every 5 min, sometimes every hour and etc sometime every 10 sec
FW: 2.1.0
S21+
VW TOUAREG 2019
Vag Fix Enabled
Ugreen Cable, Samsung cable - no effect
i have changed wifi chanles 149 153 etc no effect
Thanks for sharing this information!
@Phantom1275, @kostiksimb and others wondering how to do this:
- get the SSID (that is the name of the WIFI) of your AAW device, something like AndroidAuto-AAWxxxxxxxx or AAWireless-xxxxxxxx with xxxxxxxx being your AAW device id
- enter the SSID in http://www.sha1-online.com to calculate the SHA1 and copy the result
- paste the result in http://www.unit-conversion.info/texttools/uppercase/ to convert it to uppercase, the result is the WIFI password
@Snirpo This information could be put in the AAWireless FAQs, if it is not already there, to avoid users having to contact support to get the WIFI password.
We didn't do that on purpose. Because non-tech are going to set up to connection to the wifi hotspot of AAWireless manually. It will not help in any way. AA should set up the wifi connection via the bluetooth bootstrap. Manually connecting to the wifi of AAWireless will not help to get AA up and running.
Hello!
@Snirpo I have notice something, IDK if this was discussed before... But having the device with start/stop, if a disconnection (by interference) occours (It happens to me not so often, only sometimes passing under a teletag - toll - reader, but still happens) the device goes to white LED indication, but as the phone is already connected to the car's BT the AAW doesn't move forward to give AA connection again, so I have to manually force bluetooth off/on so it reconnects to the car unit and then the AAW start again the AA connection... Does this makes sense to you? - Is there any way to avoid the manual BT operation? - So if the AAW disconnects from the phone and it's in waiting for BT (white LED), but the BT is already connected, resume AA on the unit...
I hope the issue is clear enough...
Thanks!
P.D> This doesn't occur without Start/Stop, as it automatically reconnects some seconds after the disconnection. (It normally does a red blinking cycle, to green, to blue and reconnects)
@Snirpo I have notice something, IDK if this was discussed before... But having the device with start/stop, if a disconnection (by interference) occours (It happens to me not so often, only sometimes passing under a teletag - toll - reader, but still happens) the device goes to white LED indication, but as the phone is already connected to the car's BT the AAW doesn't move forward to give AA connection again, so I have to manually force bluetooth off/on so it reconnects to the car unit and then the AAW start again the AA connection... Does this makes sense to you? - Is there any way to avoid the manual BT operation? - So if the AAW disconnects from the phone and it's in waiting for BT (white LED), but the BT is already connected, resume AA on the unit...
I hope the issue is clear enough...
Thanks!
P.D> This doesn't occur without Start/Stop, as it automatically reconnects some seconds after the disconnection. (It normally does a red blinking cycle, to green, to blue and reconnects)
Similar threads
Top Liked Posts
-
1
I'll test on Xiaomi Mi 10T onMondaynow. 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):1
This is head unit dependent unfortunately, you can try to set the "Start Android Auto automatically" to "Always" in Android Auto settings, but I'm afraid it won't help. -
7
No, it is plug and play for 90+% of the users. The problem with these kinds of topic is, wherever it's located, reddit, XDA etc, it's mostly about issues.
So when reading this you might think the device sucks. And for some people, that might be true. Although in alot of cases it's not the device at fault, but Android Auto itself, or the phone or the head unit, or all things combined. And for sure AAWireless is also not perfect, we can still improve and tweak stuff.
Yes, you can update when powered through any USB port
6
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.3
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.3Snirpo is fully right.
Of course I only post in this thread when I have an issue. Nevertheless my AAWireless connects perfectly in about 99.5% of my drives.
It is stable. In my opinion the AAWireless device works more reliable than my phone. Some issues are also phone related and not AAWireless related.
I normally only post for the 0.5% of my drives.3
We have two experimental options in the app from Firebase App Distribution (private beta build).@Snirpo I would also appreciate that approach
Just a little site question: Is start/stop still companion app based? Or were your tests on device based start/stop already successful?
- Device HFP (to car) controlled. This will not work in 90 percent of the cars, because of the handsfree not being visible / connectable to non-paired device. In theory we could pair the AAW device to the handsfree of the car, but that will cause a whole lot of other issues.
- Device USB controlled: May work for some cars, AAW tries start up an AA connection to the car every x seconds, if not possible it won't connect to the phone. This might work for cars which keep USB powered, but do shut down the HU (and thus also AA).
But for example on Kia / Hyundai AA actually keeps running in the background (with screen off) after you turn off ignition. So for these cars this functionality won't help at all, because AA doesn't get killed, it's still running.
Both these options have been tested, but we found them not really usable. They are either not reliable or cause side effects. So they have never made it to production. They are still in the firmware though.
So to answer your question. We tried, but did not have success. So right now (in production) start / stop is still companion app controlled. -
42This 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.20
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.
