yashsingh1/xdaforums huggingface dataset:
[Android Auto General] yarik1390:
@Snirpo can you please my device Fp1EJQq6 to beta channel? Thank you in advance.

And also a question: is there a solution for disconnects on MIUI when mobile network is changed or mobile data is no available?
[Android Auto General] festor:
I’m not sure what you’re asking? Do you want AAWireless to waive the shipping fee? Or do you want them to organise a deal with your "local" Amazon?
[Android Auto General] pittrich:
Sure, if you live in the US and maybe order there. If you have it delivered to Europe, you may even pay more than $15.
[Android Auto General] Jemus:
I am experiencing problems connecting my smartphone(s) via aawireless to my cars headunit.

Car: Opel Astra from 2020 I guess, equipped with "Navi Pro"

Smartphones: Samsung Note 20 Ultra, S21

AAWireless Version: 2.21.0

Because it wasn't possible to achieve a connection, I started right from the beginning as written here in post 2204:

- Reset the device and unplug it afterwards

- Clear all app data from and uninstall the AAWireless app

- Clear all cache and data from AA and Play services

- Remove the Bluetooth connection from AAWireless

- Remove all phone mirroring/Android/AAWireless history from your car

- Restart your car

- Restart your phone

- Go to the AA settings on your phone and enable developer mode, check add wireless Projection to Settings

- Plug your phone into the car with a cable and allow it to connect and run through the initial settings

- Unplug your phone

- Plug in the AAWireless unit

- Download and install the AAWireless app again and go through its initial connection again.

Still it looks like that:

AAwireless is booting up, LED is solid green

AAwireless is trying to connect to smartphone, LED is blinking green

AAwireless connects to Smartphone, LED is solid blue

Smartphone shows two notifications:

1) Smartphone is connected to Android Auto

2) I go to the Cars headunit and continue there with taking the initial steps

Poorly the cars headunit just shows that it is searching for the connected mobile phone, so that search gets initiated, but it doesn't find the phone or AAwireless or whatever it should find in that scenario. That the searching aborts, the AAwireless dongle is rebooting and everything starts from the beginning.

Actually I was able to establish a wireless connection using an old Samsung S8 using AAgateway App. So it is possible but sadly not working with AAwireless.

Do you guys have some other hints what to try? If you need any other information, I am happy to provide you with these.
[Android Auto General] Snirpo:
Support

support.aawireless.io

2.1.0 will also have a firmware based workaround/hack coming up.

This is not a problem in AAWireless, but in Android Auto/HU. MA1 has the same issue, confirmed with @psmedley .

Kinda odd AAGateway works, have to check what's different over there. Did you ever use The AAGateway solution before on this car?

EDIT: Actually think I might know why AAGateway works. Do you by any chance have the "Non ROOT mode" option enabled in AAGateway? When "Non ROOT mode" is enabled, AAGateway does the same "hack" as AAWireless does with firmware 2.1.0.
[Android Auto General] Jemus:
Yes I had to use non root Mode on the s8 because it just wasn't rooted. In the past I used a rooted Note 4 for AAgateway but it was another Car. Also Opel Astra but different Nav.
[Android Auto General] SOFO888:
@Snirpo

I had again the case that my phone connects to AAWireless, but Android Auto does not start.

A couple of pages ago, there was a solution to open the AAWireless app and push the save button in the settings.

Afterwards you explained that in this case the bluetooth connection is disconnected and reconnected to the AAWireless device.

I made a tasker script which does the following thing:

- If Android Auto does not start within 25 seconds after establishing the Wifi connection

- Turn off bluetooth and Wifi

- Wait 20 seconds (important)

- Turn on bluetooth and Wifi

It is important to have a wait time of at least 15 seconds.

I could not get Android Auto to start with a shorter wait time than 15 seconds. I use 20 seconds as this is also the timeout time of AAWireless. I think the timeout time is perhaps the reason why a short wait time does not work.

I had the cases 3 times in the past months. In all 3 cases my tasker script worked well. It was not necessary to replug the AAWireless device.
[Android Auto General] Gerr1985:
I'm down for this 2.1 beta pls

AndroidAuto-AAWCUOZ3n4Q

@Snirpo
[Android Auto General] mrtkdl:
Hi, i have some sort of interface box connected to oem head unit that provides cabled android auto which my mercedes c253 lacks. I don't know if it was discussed on this thread but i wonder if aawireless would work this device? I have attached the picture of the interface unit.
[Android Auto General] Genebaby:
I have a Netplay unit (it gets rebranded) in another car, that has native wireless AA, but it also has a USB input, so it stands to reason that you could put an AAW there instead of plugging in your phone and it should do similar.

In my other car I installed a touchscreen overlay on my factory screen and I can switch over to AA or Carplay. I made sure to get one that was native wireless, but if you can't, then you can give it a go.
[Android Auto General] martin.armstrong:
@Snirpo

in the development version of the AAWireless app the start/stop settings have experimental settings which are greyed-out and cannot be selected. If I had the firmware 2.1.0 would they then be active?
[Android Auto General] Snirpo:
In dev app yes. Production app no. We'll start rollout of 2.1.0 this evening.
[Android Auto General] androidjel:
Through there official new webshop the delivery fee is half..
[Android Auto General] Nathan1995:
Hi, this is more a general question:

I had connected my AAwireless with a short usb a to c cable in my car. I attached my aawireless with tape to the car, so it cannot move when driving. I was driving on a freeway a few days ago. AAwireless was working fine the whole time until all of a sudden it lost connection. after a few seconds it was restored. Music was streamed and Google Maps displayed, but Google Maps stopped updating. I unplugged and replugged AAW once and it wouldn't start again. later I tried AAW again with another cable and it started right away. Now to the real question: is it normal that a cable that has worked for weeks without any problems and is not exposed to any mechanical stress can suddenly fail to work with aaw?
[Android Auto General] SOFO888:
@Nathan1995

Yes...it is possible.
[Android Auto General] Jemus:
Thanks!

Works for me now :)
[Android Auto General] Swap_File:
Is the "Experimental Client Hot Spot" option for running a hot spot on the same phone AAwireless is running on, or just for hot spots on other devices?

I tried it on the same phone, and it did not seem to work (My AAWireless would connect to my hot spot, but my phone could not find the AAWireless).
[Android Auto General] Music_Love25:
Hey @Snirpo @Emil Borconi i want to go back to stable channel. You pushed 2.1.0 on my request to my device. Pls reverse that change and provide me with stable version of the firmware since 2.1.0 has started in stable phase. I want to be on stable for my device name attached in [Screenshot](https://imgur.com/a/R0jFd6L). Thanks u/Snirpoo
[Android Auto General] Spoonoid:
Hello everyone,

Is there someone who has a OnePlus 7T working with AAWireless? If so, can you tell me (PM maybe?) your phone WiFi & network settings plz ?

Mine doesn't work anymore and support says "it is not a AAWireless problem, it is a phone one"; and I need to "allow to use mobile data while you are connected to a Wi-Fi network. Once you enable that it should work."

I doubt it a little (as when my phone tries to connect to the AAWireless WiFi there is connection error before being connected), but I prefer to be sure.

Thanks in advance
[Android Auto General] pittrich:
A quick update from me.

•Opel Mokka X Intellilink

•Google Pixel 5 A13 since two day's

•latest dev companion App

•latest dev Firmware

Everything is going great. Thank you @Snirpo and your team for your work
[Android Auto General] pnsdhrn:
Android Auto Auto version 8.012304 has already been released. Has any one installed this in their phone?Does it have the much talked about Coolwalk features? Anybody please give review of it?
[Android Auto General] pittrich:
I already have version 12.123204 and no coolwalk yet. Supposedly it's up to Samsung, since Coolwalk is causing problems there.
[Android Auto General] Desperanto86:
nothing new. new coolwalk will be activated by server side in september
[Android Auto General] pittrich:
In September? I won't believe that until I see it 🫣
[Android Auto General] Desperanto86:
What Everybody Must Know About the Android Auto Coolwalk Launch

The summer is almost over and the Coolkwalk update is still nowhere to be seen; no need to panic though, and here’s exactly why

www.autoevolution.com
[Android Auto General] pittrich:
There is also nothing about it coming in September, just maybe. If Samsung really is the main problem, you could release it for the other devices via switch.
[Android Auto General] billarf01:
? for you... On the AA Wireless Adapter for Android shipping from Amazon, what firmware # is loaded on them.. I have been told by fellow Wrangler JL owner to roll back to / to only use firmware version 1.8 . When I receive my dongle from Amazon on 8/30/22 I want to be sure it has only 1.8 firmware. Thanks for you reply.. I am Rhinebeck01 in this thread talking MA1. IF I have success with AA Wireless dongle I will be posting about it.. https://www.jlwranglerforums.com/fo...1-wireless-android-adapter.86856/post-2054720
[Android Auto General] Snirpo:
It will arrive with 1.12.0, which is equal to 1.8 (gen1 vs gen2). No dongles are shipping from factory with 2.x yet.

UConnect is still blacklisted in the backend from 2.x. However we will soon remove this blacklist, because firmware 2.1.0 should work fine with UConnect.
[Android Auto General] chrisbrunner:
Hi all,

I wannt to update my AAWireless firmware version 1.0.0.

I have connect the the device an the AAWireless android app in version 2.21.0 state, that there is a new version 2.0.2 available.

I click on "Start download" and the download ends with 100%.

But after that, instead of showing a button "start update", again the button "Start download" is shown.

Also downloading again, does not change anything.

It is the same using a Samsung Galaxy S9 or a Pixel 6a as a mobile phone and the same if I have connected the device in the care or with a laptop.

Any ideas, why this happends and why the update isn't installed?

I am a german user and are using the german localisation of the app.

Thank you very much!

Christoph
[Android Auto General] Snirpo:
Oh jeez, that's a golden oldie :) Not sure why this happens, I'll check if I can reproduce. Might be a bug.
[Android Auto General] ravijot:
@Snirpo can you please push 2.1 to AndroidAuto-AAWp4QwB7wL. lol... Can't wait,😁
[Android Auto General] Snirpo:
For everyone who wants to translate the app to their own language: https://poeditor.com/join/project/lgCJgw1aR4
[Android Auto General] Andres.Navas:
Spanish 100% 💪
[Android Auto General] pittrich:
German to 👏🏼
[Android Auto General] Experge:
I'm having issues with voice navigation on Google Maps and Waze. Most of the times the voice gets out of sync with navigation, having the instruction being cut in the middle and the other half being said during the next voice instruction.

Does anyone else also have it? It doesnt happen when using wired.

This is in Brazilian Portuguese.
[Android Auto General] Cryptage:
French is now 100% ! 👍
[Android Auto General] TomNguyen87:
Vietnamese is 100% completed now!
[Android Auto General] pittrich:
Looking at the list like this, one might assume that the Czechs don't want anything to do with AA Wireless 🤔
[Android Auto General] Gerr1985:
I'm admittedly checking for the 2.1 update every 6 hours. I have a Kia in new software (yay widescreen finally) and a Jeep on Unconnect (2 aawireless devices). Both are technically working with the known workarounds, but I do miss some of the features like DPI control on the KIA.

AndroidAuto-AAWCUOZ3n4Q

AAWireless-YdNaa4Ae

*Edit*

Update appeared evening of 8/19

Kia now actually now able to full screen one app thanks to DPI at 250 (image attached)
[Android Auto General] Mischell53:
Czech will be soon. Now I'm on vacation 😀
[Android Auto General] nopasaranof:
Someone can clearly explain how to change the language file in the application?
[Android Auto General] RealNBB:
@Snirpo

I can't wait also not longer! :D If you want:

AndroidAuto-AAWVD52fJdF

Thank you!
[Android Auto General] Jemus:
Is it possible that I have to repeat the adb command after rebooting the smartphone?

It worked perfect till I rebooted.
[Android Auto General] suburbazine:
AAWireless team- I have an issue with my unit leaking a comparatively large amount of RF noise for a 100mA device, mostly between 27.180Mhz and 27.190Mhz. I basically can hear it negotiating the connection to the head unit and then video data becomes pink noise. Similarly, any local transmission on those frequencies cuts its connection to the head unit. I have tried different USB cables in case there was a shielding issue, but it doesn't happen connected directly to the phone.

Transmitting at least 4w AM nearby between in that range breaks the AAW, even worse with SSB at 12 watts. It does not seem to be affected much if at all outside of that spectrum.

I'm not certain if the leakage/interference is within FCC tolerance, either. Normal issue?
[Android Auto General] Snirpo:
To be honest, I have no idea. While the hardware design is our IP, we did not design the hardware ourselves. I forwarded this to the factory.
[Android Auto General] Mischell53:
Czech is now 100% !
[Android Auto General] Genebaby:
I've been casually waiting for the update but how have people on 2.1 been finding it? Any better than before? No difference you can tell? A godsend?
[Android Auto General] Snirpo:
Changelog will tell for who's it going to matter: https://github.com/cpebit/aawireless-issues/blob/master/FIRMWARE-CHANGELOG.md . For the rest it makes zero difference.
[Android Auto General] krzyb:
please update for my kia - AAWireless-wDa0aa67

Thank you!
[Android Auto General] maccamania:
Hi, I'm having connection issues with my Renault Captur with EasyLink after the 2.0.2 update. Maybe the last one could solve them?
[Android Auto General] Midyr:
May I ask for an update too, because of problems with my kia?

AndroidAuto-AAWRgx1QgNb

Thanks

Frank
[Android Auto General] Gerr1985:
For those with the 12.3 widescreen in KIA running latest software updates, and after you get the 2.1 firmware and turn off pass-through mode.

Setting DPI at 248 or higher will remove the split screen android auto and allow the full screen to be used for the AA apps. However, this does make things a bit large. For example, the bottom bar is so big, that the apps are extreme widescreen. This might be ok for some.

I actually chose to go back to the android auto split-screen (not to be confused with KIA split-screen), and don't mind things to be as a small as possible (while being readable), and have adjusted my DPI to be either 190 or 200. This does put things back in the split screen, but I feel like I get to see so much of the maps for example, that I prefer it this way.
[Android Auto General] Vesaros:
I have a really annoying problem.

Firstly, AAWireless has to be commended, it's truly a pleasure to use if there wasn't a critical security vulnerability for me. Every time my smartphone (Note20Ultra, latest OS) connects to AAWireless, the screen unlocks. Despite set up facial recognition, fingerprint and PIN.

It is not even necessary that I actually use Android Auto (Peugot 3008 II). In other words, as soon as I unlock the car, my smartphone connects directly to AAWireless and unlocks itself completely. Surely it is possible to disable this somewhere, but where? This cannot be changed in the permissions for the apps, in Android Auto and in the display settings.

Because of the fact, that the smartphone is in my trouser pocket, even the setting, that there shouldn't be incorrect entries when the phone is in my trouser pocket, is ignored. So all possible incorrect entries are made happily and calls are even started. I have to put the display of the smartphone back into sleep mode before driving off. Anyone have advice on this?
[Android Auto General] bpsmicro:
Samsung has this "Smart Lock" feature, that allows you to set trusted places/devices/etc settings to bypass the normal locking stuff. In Settings search for that setting and review what's "trusted". I'm thinking maybe the AAW got added as a trusted device (you'd have to do that explicitly), or maybe one of the other settings are in play.

Then if the phone's in your pocket, anything interpreted as a swipe up from the lock screen will just unlock it.

Personally I find Smart Lock entirely unreliable, but the theory was good.
[Android Auto General] sibesaver:
Smart Lock is standard on most Android phones at least the recent versions. It works beautifully on my Pixel 5a. I pair it with most all my Bluetooth devices and have hardly ever had to unlock my phone manually.
[Android Auto General] Vesaros:
I've already had the idea of the SmartLock feature, but there are no entries.

The problem is, that my Smartphone is unlocking completely, not even a SwipeUp is necessary.
[Android Auto General] fbomke:
Hi! I encountered something strange today: After briefly leaving the car for picking up some errands, the music did not come from the head unit anymore (neither did it come from the phone) although the music player (Spotify in my case) played. I could also skip tracks without any audio coming from car or phone...

When it triggerd Google Assistent on the HU, replies came from the car speakers (but no music).

Is there already a known workaround/fix for this?

My setup: Pixel 6 (Android 13), GM/Opel head unit (Opel Adam built 2019), AAWireless configured with passthrough and dongle mode activated
[Android Auto General] hundred_miles_high:
I have a 2015 Vitara and have had my AA Wireless for about a week - So far it has worked completely as expected to be honest.

My hardware is:

Bosch SLDA on f/w 1880

AAWireless device on the original out-of-the-box firmware 1.12

OPPO Find X3 Neo phone on ColorOS 12.1

This USB cable https://www.aliexpress.com/i/32923966469.html

My software is:

Android Auto 7.8.622514

AAWireless app 2.22.0

I already had AA setup to run over cable connection, and to set up the AAWireless device I literally opened the AAWireless app and followed the five or six standard setup steps, made zero changes to config, didn't update the firmware and so far it just seems to work as it should.

It connects literally a few seconds after the phone to SLDA bluetooth connection has completed and the Android Auto option on the SLDA screen is then available to use.

I haven't used it on any very long journeys but so far it has connected as it should, and worked for Google Maps and Prime Music (my main 2 apps) just the same as the wired connection.
[Android Auto General] DeanGibson:
To those complaining about AAW unlocking their phone, it is not AAW, but Android Auto itself.
[Android Auto General] Disdaine:
I received the 2.1.0 update today (with updated app) and tried the GM Fix on a 2020 Chevy Bolt. Unfortunately, it does not work for non-passthrough. It worked before the recent June/July Android Auto updates though so it was something broke by Google.

Same as before; phone says check head unit to confirm and head unit displays nothing. Trying to force projection just gives a message that a compatible USB device is not connected.

It works perfectly in passthrough mode though. With the ADB setting recommended before, non-passthrough works but unfortunately my phone resets that setting on every reboot making it a bit aggravating.

Device Name is: AAWRfr7lhVm
[Android Auto General] chipuc:
I try to update but i keep getting this message, there is no VPN.
[Android Auto General] sibesaver:
That message is just a prompt to disable any VPN you're using. If you're not using a VPN then just hit OK.
[Android Auto General] Arismfg:
Tried FW 2.1 today (got a system update available for my device with latest aawireless app version) and looks really stable till now. Connection is fast too. Ford Sync3. Samsung S8 plus and latest Android Auto.

Did not have any special issues with previous firmware other than disconnections that surprisingly were fixed just by restarting my phone.
[Android Auto General] SteveG12543:
Hi there! I would love access to 2.1.0, as I've been stuck on 2.0.0 for what feels like a lifetime and haven't been able to use the device. Currently it only says I can "update" to 1.12.0, but that doesn't even attempt to download for me.

My device is AAWireless-7TqndzFF. Thank you!
[Android Auto General] Marsou77:
Hello @Snirpo,

Today I have been notified that an update is available for my device, but I cannot download it. The screen look like this

What can I do?

My unit is: uoBcjksX

Thank you :)
[Android Auto General] Marcinok:
Please access to update 2.1

Id:

AAWEgnQEbTT

gnQEbTT
[Android Auto General] psmedley:
Use the troubleshooting tool and work through the options, including clearing the AA data/cache - then it will work in non-passthrough.
[Android Auto General] Disdaine:
Have not attempted that; will try it out in a couple minutes! Perfect timing for commute home :)
[Android Auto General] Disdaine:
Works perfectly! Finally... No more "fat" GM default :) Thanks the help!
[Android Auto General] billarf01:
Firmware 2.1.0 that has just been made avail..... Your current thought/today .... Is it good or bad move in regard to my Wrangler JL with UConnect..... or should I just stick with the firmware that the unit (Arriving this Thur. from Amazon) has on it.. ? I have a Samsung S22 smartphone...
[Android Auto General] biglou29:
Getting the same message too. Initially when I hit start download I'd get a the download notification appear in my status but zero progress and it would just stop. After 5 or 6 attempts I now always get the VPN message.

Not on VPN. Tried wifi and mobile data, also forced stopped the app and tried again. Still VPN message and error when trying to DL. Samsung Z Flip 3. Currently on 2.0.2.

EDIT: Tried again and happened to work. Didn't do anything different. Must've been an intermittent issue.
[Android Auto General] Genebaby:
Used my Golf today and the update was available. Downloaded easy, two tries to install, then reboot.

Pretty much the same as before, works fine, only the intermittent issue where I can't hear the Assistant speak. I notice that when I try to use the Assistant and cannot hear the replies that the music I was playing does not auto re-start like normal, I have to press play again.

Is this something I should raise with tech support? I have been waiting through updates to see if it is fixed.
[Android Auto General] psmedley:
My pleasure - I was involved in testing the GM fix, so had a hunch :)
[Android Auto General] Spartoi:
I have a 2020 Mazda MX-5 which has touch screen but disables the touch screen functionality in Android Auto. I've read that Mazda made this decision because Android Auto does not allow both the touch screen and physical controls (i.e: knob selector) to work only one or the other and Mazda chose the later. Is it feasible for AAWireless to add an option to force Android Auto to use the touch screen or is that not possible from the AAWireless-level?
[Android Auto General] FlyingIceman:
Please access to update 2.1

Id: AndroidAuto-AAWjbkcglYA
[Android Auto General] mnunes:
I have a Samsung S22 and a Durango with UConnect. For me, the latest builds have been the most stable by far. Earlier builds had lots of problems with sometimes not automatically connecting. I suggest updating. If the updated build doesn't work for you, you can always request to get a downgrade to 1.12 which was fairly stable but doesn't have some of the newer improvements. (One of the improvements in 2.x is the ability to set the Wi-Fi channel - this helps avoid signal drop-outs due to interference from other sources.)