yashsingh1/xdaforums huggingface dataset:
[Android Auto General] Msan2000:
Well, seems Android 13 broke something.. I updated to the 2.0.0 FW while still on Android 12 and it was working fine.

Installed Android 13 Beta 1 and can't get it working anymore.. Tried all different modes and options, reset, nothing.. AA works fine connected with the USB cable straight to the phone though.
[Android Auto General] Snirpo:
We already played a with changing the signal strength, but it didn't really seem to change anything. We could give the option to do it.

This whole interference stuff is just a bit ****ty, because a setting for one, does not necessarily work for the other. And also like you're saying, a shield may or may not help. We spent over a month with the Chinese + some testers trying different antenna configurations and also software tweaking and the results were just too inconclusive to make any (risky) changes to the hardware :(

The MA1 + Carsifi (tested myself), and also some native AA Wireless head units for example from BMW (according to the internet) also don't seem to be completely insensitive to interference. So can we ever fix this 100%? I'm not sure...
[Android Auto General] Genebaby:
I haven't played with the app too much but I do like the look and features of 2.6, we've come a long way and no other dongle has anything like it. The big test will be when I get my wife's car running 2.0 FW and see if both our phones can easily use AA.
[Android Auto General] mlord:
Updated firmware to 2.0 here today. Total non-event. AAW just continued working as it always has here. OnePlus9Pro LE2125 in a 2018 Subaru Crosstrek.

I would like to find a description of each of the settable features though. Does this exist somewhere? Eg. "Dongle mode" means this.. etc.
[Android Auto General] Andres.Navas:
Hello!

2nd day testing on channel 153, no disconnections at all, not at the known places, not random ones yet... So far, so good and happy to see the positive impact of having the capability of changing the channel! Big kudos to the AAW team for this!

However if anything changes I will try to report it here :)

BR
[Android Auto General] Genebaby:
There is still some voodoo here to get things working. The biggest issue I have with AAW and the Ottocast device is more than one phone on the device.

AAW has been working for a while in the GTI but no in the wife's Mitsubishi, but I got her phone working, she uses it the most, I hardly do. She virtually never drives my car.

Today I checked and she didn't get the update yet and I still couldn't get mine to work, it was telling me to go use AA on the carscreen but no projection, light is blue.

I gave up and tested her phone before I go. Same thing now, she isn't getting projection, ahhhh!!!!

I reset the APP cache and storage, deleted and re-added the device, no good. Went and started deleting storage and cache in AA and AA for Car Screens and after I did the second one projection began all by itself.

Tested after a car reset and she should be good to go.

I guess I could do the same for my phone but mabye another day. Will FW 2.0 and dongle mode fix these storage and cache resetting requirements out of the blue?
[Android Auto General] :
Update:

Firmware 2.0

Channel 165

Car:

Audi 2021 MIB3

Everything works fine now. No reconnects. Like before.

Drove the same way twice now.

It finally works flawless for me.

Im happy.
[Android Auto General] valeri_s_k:
Hi, does anyone have freezing AA after upgrade to firmware 2.0?

Some details here:

Xiaomi Mi 11 phone and VW MIB 2 with enabled VW fix.

I know xiaomi phones have issues (with AAWireless and native wireless AA)- AA restarts when mobile network is lost/reconnected.

HU unit is OK, does not reboot, only AA freezes on the screen. May be AAWireless device freezes too, but not sure.

It happens in both Dongle and standard modes.

Already tried all possible workarounds - cleared/reinstalled all needed data/apps
[Android Auto General] sibesaver:
I had the same issue with it connecting but not being on the car screen. I've been talking with Chiel in the slack beta channel for support. Just curious what head unit do you have? I have a Kenwood DDX9704s. He mentioned there were changes to the SSL handshake. When I know more I'll post here.
[Android Auto General] Genebaby:
Mine are OEM headunits, this one is a 2018 Mitsubishi in the wife's car.
[Android Auto General] Genebaby:
You have MIB 3 but no OEM wireless AA? I know MIB 3 can do it.
[Android Auto General] SOFO888:
@Snirpo

I wrote a couple of weeks ago that I had disconnects. After doing the AAWireless setup again, everything was fine.

I don't have disconnects for some weeks now.

My question is therefore: is the update only necessary for people with problems?

Honestly speaking I don't want to update as it is running now...
[Android Auto General] znel52:
Try this. I have same headunit and had same issue. This got me up and running.
[Android Auto General] sibesaver:
I think I've tried that already but I tried so many things I don't remember for sure so I will give it another attempt. I kind of suspected the issue was AAwireless not being able to add the car to Android auto properly.
[Android Auto General] sibesaver:
No Love. When it connects I get this but nothing on the head unit.
[Android Auto General] Jimbob65:
Huawei p30 pro.

For anyone having problems with AAwireless and Spotify, maps etc not running correctly with AAwireless, it is likely the apps do not have permission to run in the background.

I was having problems to the point where I was giving up on the unit.

Finally, I found the solution and I hope this helps anyone else having the same issue I was.

Go to the 'phone settings', 'apps' then 'app launch', find the relevant app and click on 'manage manually' and allow 'permission to run in the background'.

Since I enabled this, I've had no problems.
[Android Auto General] Snirpo:
If everything works fine, and you don't need the extra features of 2.0. Then you never need to update. Actually we still have some people still on 1.0, because it just works for them :)

This is actually quite good information, I'll try to reproduce this as well. In general, if AA fails to start up (blinking green), resetting cache and data helps.
[Android Auto General] sibesaver:
I resolved my issue but not sure exactly what fixed it. I did three things all at once which is my bad. I made sure pass through was not enabled within AA wireless. I uninstalled updates from Android auto and reinstall. I set driving mode to start Android auto instead of do not disturb. Rebooted my phone. I didn't turn my head unit and AA wireless on until I was away from any known Wi-Fi. I did get the confirmation screen on my head unit to continue with Android auto once everything connected. Now I'm good to go without pass through.
[Android Auto General] xatornet:
Hi there. Please, I seek help, I've tried everything during almost a whole year, but it keeps failling:

I have a VW Golf MK7, 2017, with MIB2 platform from Technisat Preh. I know the drill: you have to select "VAG Crash Fix" in order for it to not reboot from time to time. But the thing is, it doesn't work. I've already tried these steps:

-Select VAG Crash Fix Enabled + USB Mode Default. It keeps rebooting.

-Select VAG Crash Fix Enabled + USB Mode MTP. Same, it keeps rebooting.

-Select VAG Crash Fix Enabled + Passthrough Enabled. Same, it keeps rebooting.

Also, I've tried upgrading my headunit's Firmware from verson MTS2_EU_VW_ZR_P0363T to MTS2_EU_VW_ZR_P0369T (The last official one). It keeps doing the same.

I've tried twice using the support button, but I only get a mail telling me to use VAG Crash Fix Enabled, which I do, and another mail telling me to enable "Force 2.4Ghz", which I've done, and it increases lag, without fixing anything. Also, I've used several USBC cables, with the same luck.

Please, is there anything I could do to fix this? Please? Anyone?

Thank for your time
[Android Auto General] -Loom-:
I have a Golf 7 with MIB 2.5 (also Technisat) and since VGA crashfix was rolled out, no more reboots for me.

However, I noticed that the USB cconnection is quite sensitive to movement. Just a light push and you get a reboot. Might be the USB port or the USB cable itself. Hard to tell . And maybe the connection degrades after some time because of roadbumps and general vibrations...

So, you might want to try different cables, or fix the cable to the AAWirless device with some sort of stick-tape.
[Android Auto General] xatornet:
Thanks for answering. In my case, and since the issue has been happening from the very beggining and for almost a year now, belive me when I say, that i've tried any usb cable possible. In my case, it's not the connection itself. I can use the same cable to plug my phone, and it works wonderfully. It's not a drop connection, it's a full freeze for about 1/2 seconds, followed by a full reset of the headunit. It surely happens fast if I change songs using the wheel buttons, but it will also do it on its own, taking some more time.

Eitherway, thanks for your answer.
[Android Auto General] -Loom-:
I feel sorry for you. I can only image the amount of time you put into this ...

Well, this really looks like the freeze followed by a reboot I used to get before the VAG crashfix.

I assume you already did all the possible cleanup actions like resetting the headunit, remove all bluetooth and wifi related AA stuf, clear data from Android Auto, putting some aluminum foil around the AAwireless device to get some shielding from interferences..etc

.And just out of curiousity: what firmware are you running?

But regarding the cable: just because it works wired does absolutely not mean it works wireless with the same cable. Android Auto is incredibly picky about the cable.
[Android Auto General] xatornet:
Yeah, I've even tried different phones, and roms. Same luck with all of them. I'm right know at FW 1.8.0, waiting for the 2.0 (i've applied this afternoon for it).

In regards of the cable, I've tried about 10 cables, with very different lengh and different vendors. I can understand that the USB could be picky... but this would be madness 🤩

In fact, I'm pretty sure this has to be something wrong between AAWireless and my headunit, because I've tried this very same AAWireless on my partner's Golf MK5, with a RCD360 Pro (an RCD330 knock off) and it works wonderfully, first try. No reboots. No drama.

So there's gotta be something else here...
[Android Auto General] -Loom-:
If this would be a general incompatibility of the MIB2, then there would be plenty of other users complaining.

So, as you said, it could be something special on your side. Maybe your car's USB port is broken, or worn out. Enough stability for running wired, but not enough contact when running with AAWireless.

Just a wild guess, as I'm running out of other ideas - except replacing the headunit of course.
[Android Auto General] xatornet:
Well,

The only thing that I'd like is to get a little "official" support. I've even bought a VCDS cable unit, to check for fail tests on my end... I'm that desperate. Eitherway, I'll wait for some response and FW 2.0. If there's no fix... then I guess I have to give it away or something, I don't know.
[Android Auto General] Snirpo:
There's very little chance 2.0 will fix this. There are some head units where it's just a bit of a mystery why it doesn't work properly. Our support is not really helpful in these cases unfortunately because they also don't really have the solution. I will tell them that these "try 2.4Ghz" responses are not helpful though...
[Android Auto General] xatornet:
Thanks for your answer.

Welp, that's a bummer. I'll wait to update it, and if it still does not work, i'll upload a bug report again, and I guess I'll use this on my partner's RCD360. What a pitty, not being able to use Wireless Android Auto on my end... :-(
[Android Auto General] Limpperi:
Fw 2.0 with dongle mode on, takes a LOT longer time to connect to the cars head unit when starting the car. If i disconnect and reconnet during the drive, or when car has been on, its as fast as it should be.

I reseted everything and did as instructed when going to dongle mode. It blinks green fast and while bluetooth connects/disconnects/connects/disconnects many times until it properly connects. This is not the case with dongle mode disabled, but then there is so much more latency when pausing music etc.

So initial startup connect time in dongle mode is maybe around 1-2 minute mark now as opposed being right away ready earlier in 15 seconds or so with dummy bt. AAwireless was one of the 100 engraved so i suppose its the first gen unit if that matters.

Any ideas? Peugeot 208 2020
[Android Auto General] Istarish:
Dang it, I really counted on client mode allowing me to use my car's wifi hotspot to be a golden config for the wireless AA experience with some battery saving due to lack of need of LTE comms... But it turned out that my MIB2.5 high (in MY2019 Škoda Superb) only supports 2.4 GHz wifi and even though AA works, it's very laggy and rather unusable. I suppose there's no sense in attempting the client mode without 5 GHz network?

Thanks for great support and for making this great product happen!
[Android Auto General] marecek65:
Snirpo:

Hello, I send reguest by form which you have published 3 times and I havent received firmware 2.0 yet. Please, can you solved it?
[Android Auto General] josefsch:
Hi, I just want to report after upgrading to firmware 2.0.0 on Monday. Had only short drives during the week, but 2 drives each 2 hours today, most of the time listening to podcasts:

No problems so far with my Renault R-LINK2 and Huawei P20 lite configuration1

Thanks to Chiel, Eric & team!
[Android Auto General] Genebaby:
That's what I was getting and then I cleared storage and caches.
[Android Auto General] mlord:
So.. what is "dongle mode"? Must I purchase a Motorola Dongle to find out? :)
[Android Auto General] Genebaby:
Are there updates to your headunit available from VW. I think your brand is the most prone to issues unfortunately, at least in the early days when we were figuring out the different brands of MIB units.
[Android Auto General] Genebaby:
It's part of the 2.0 FW, everyone will get it eventually.
[Android Auto General] civictd04:
I have a 2019 Subaru Outback. I have batch 1 (version 1.8 firmware) of AAWireless and was having issues connecting to my LG V60 (Android 12) even following the steps quoted above. What finally worked for me was doing this:

1. Complete steps 1 thru 8 quoted above

2. Connect AAwireless to car after reset

3. Make sure AA wireless projection setting is on on your phone in AA settings (you may need to enable developer mode to do this)

4. Attempt to pair you phone to AAwireless as usual thru the AAWireless app (if it doesn't work at this point continue with the following steps)

5. In AA settings on phone, make sure to forget all cars

6. Click + Connect Car in AA settings

7. Pick AAWireless-abcxyz from list of Android devices. Do NOT pick your car if listed (your phone should not need to be connected by a wire to the car at all)

8. Your phone should now wirelessly connect to the car (I did NOT have to turn on passthrough nor change USB mode from anything but Default)

Hope that helps someone,

Charley
[Android Auto General] kb_79:
Hello in dongle mode is it possible to be in direct wifi on the aa wireless without having the bluetooth active?
[Android Auto General] mlord:
I know that, and have it here. But I have no idea what it does. The only description is effectively "what Motorola does".
[Android Auto General] hand-filer:
Wireless or wired you still need bluetooth on for AA to work and to receive/make phone calls.
[Android Auto General] dc300m01:
2018 Mazda 6. I was having trouble connecting after upgrading to the Samsung s22 ultra. Finally got it working without having to use pass-through. Here's my steps:

1. Ensure pass-through is disabled in the aaw app.

2. Force stop Android auto, then clear cache and data

3. Factory reset the Mazda infotainment system. Wait for it to reboot, then turn car off.

5. Wait for the light on the aaw module to go out. Then restart the car

6. Android auto should go through the normal setup process.

7. Once Android auto is loaded, turn off car. Wait for light on aaw module to go out.

8. Turn car on, everything should work. I'm able to change dpi and everything again!
[Android Auto General] xatornet:
As far as I've seen, i've updated my headunit to the latest FW version, which is P0369T in my case.
[Android Auto General] Genebaby:
At least you have checked that avenue and if you get it working an update won't upset it. I'm not sure if mine have update available.
[Android Auto General] osm0sis:
@Snirpo Direct control over channel width (and upper/lower sideband choice for 2.4GHz) is a pretty basic wifi feature, so hopefully that can be added. No reason not to give that ability to power users who want to dig into resolving any interference issues they encounter.
[Android Auto General] Snirpo:
From our testing it doesn't really help for interference related issues. It's possible, but not as easy as changing channels. Possibly we can add it to 2.1.0. 2.4Ghz wifi is very limited on these chips, for example we cannot enable 40mhz bandwidth on 2.4ghz at all.
[Android Auto General] Snirpo:
This is interesting. You're saying dongle mode reduces lag? That bassiccly proves what I suspected, Google added specific logic in AA for the Motorola dongle. One of out testers with a Chevy has hiccups in audio every 20 seconds, with Dongle mode it's gone.

One big change in dongle mode is it waits for the HU handsfree connection before starting up AA. This is something built in to AA. Is it possible your car takes a long time to connect handsfree?

Can I have your device name? To check what HU you have.
[Android Auto General] kb_79:
@Snirpo Hi its possible to have a wifi code for my dongle AndroidAuto-AAWfR8ar1TO ? Thx
[Android Auto General] Limpperi:
Yes it definitely does reduce it, especially noticeable when audio ducks a bit for navigation voice to give instructions. Before they overlapped a bit, now its gone. And music pauses instantly now. And my experience is that it does not take long to hu connect to the hands free, its usually done by the time i get seatbelt in

Device is AAW6ABzM5pC
[Android Auto General] Snirpo:
NAC Wave 4 I see. Expected Wave 2. But very interesting nevertheless.

About the long time to connect. I'll have a look into it, possibly we can tweak it a little.
[Android Auto General] Dangze:
@Snirpo

I have NAC Wave 3 (Citroen C5AC), should I use Dongle mode ? I'm not sure to have understood everything in your above discussion...

Thanks.
[Android Auto General] Snirpo:
You can try :) According to @Limpperi it reduced lag in his car.

BTW if it reduces lag this is purely because of logic in AA itself. The only change on the device side is disabling the dummy handsfree and changing the device name.

Device bluetooth name == "AndroidAuto-xxxx" -> dongle mode. That's what controls it on the AA side. It's actually called dongle mode in AA (in the code).
[Android Auto General] Genebaby:
Drove my car yesterday and it's running great. It was good on 1.8 and it's good on 2.0. I haven't done a few runabout trips where I turn the car on and off but so far I can hear the assistant every time, I hope that continues as that was my only issue before in that car. I'll try and update the wife's car and add my phone to it.

Before I used the new app and FW 2.0 I thought Dongle Mode was one of the connection choices, so instead of Default or Direct etc. I didn't realise it was a separate thing. So I think it's a good thing to tick as Google did work with the company that produced the MA1, so gave them a bit of a boost compared to the little guys.
[Android Auto General] Snirpo:
It probably is yes, dongle mode makes it "native" instead of sort of a hack. We were thinking about making it default, but it may need some resetting on some phones. For tech guys, that's fine. But other people, even if you try to explain it the best you can, will immediately contact support, and we really didn't want that with 50k+ devices around.
[Android Auto General] Falconpunch01:
Tried to search for this answer, sorry if it's already answered.

Can I play music with a different phone via Bluetooth through the head unit normal BT feature while my phone is connected through AAwireless dongle and running AndroidAuto?

I know currently when I use AA wired, it disables the headunits Bluetooth. I had a previous car with Wireless android auto and I could play music through another device via BT while my phone was using wireless AndroidAuto.
[Android Auto General] SOFO888:
This depends on the car. There are cars which allow 2 bluetooth connections at the same time.
[Android Auto General] Limpperi:
In my car atleast, after AA is initially connected, you can take the bluetooth just off from phone and then connect another phone to the BT.
[Android Auto General] Genebaby:
I did the 2.0 install in the wife's car and only enabled Dongle Mode to see if that would get my phone connected. No dice.

I started deleting data and cashes and I could get to see the first AA screen for new setups, but then it would crash with a communication error. Restart phone etc, same deal. See the AA start screen, comms error crash.

Very glad the wife's phone kept connecting ok through all this and did again before I gave up.

Went into the GTI and had to redo all my AA settings/shortcuts etc but it's working ok there on my phone. My phone is the only one connected to that AAW.
[Android Auto General] andreaslev:
Got the firmware update to 2.0 today and I'm thrilled. I can finally use my existing WiFi connection in the car and connect both devices over it. The connection is very fast as usual. Thank you for the many work and keep it up .... Thank you
[Android Auto General] Dangze:
@andreaslev

which phone ?...
[Android Auto General] fese:
I had the same issues as you and I also tried so many different things. My MIB2 Technisat was always rebooting after some minutes, if played music through Android Auto. It was very frustrating.

For me this problem was definitively not related to AAWireless as it also occurred with direct USB connection to different smartphones.

My last hope was a FW Update to a different HW train (from 245 to 478). This was quite tricky, but after that I didn't had any reboots anymore. Everything is now working flawlessly.

Such a update to a different HW train was not intended by the manufacturer! For me everything is still working fine, but it could break things.

I'm not sure if the "VAG Crash Fix" option was already there, before I did my HU FW update. .
[Android Auto General] dscline:
Then I would expect the answer to be no. Your car sees AAwireless as a wired connection, so if it disables Bluetooth with wired AA, it should using AAwireless too.
[Android Auto General] dscline:
For those who want to try dongle mode but have issues, is there someplace you've already explained what needs to be reset?
[Android Auto General] Snirpo:
Simple, just turn it off again :)
[Android Auto General] 1enry1:
thanks , sorry where i found this in my samsung phone ?

PS but... my problem is that the anfroid auto ASSISTENT request the "permission" NOT

in the phone , but in the car !

in the new MIB 3 in the VW GOLF 8 .....

HELP ME ?
[Android Auto General] jeremyt561:
For the app permissions, long press on the app shortcut and click info. Then go to permissions. Can you post a screenshot of this permissions request your seeing?
[Android Auto General] lanege:
Hi, i am on 2.0 fw, where i configure client mode on my aawireless dongle ? I need solve my onlyone problem, possibility use car wifi for my internet in phone... Thanks..
[Android Auto General] martin.armstrong:
settings->wifi settings
[Android Auto General] MdX MaxX:
Just wanted to share my AAWireless experience with my Kia EV6 and Galaxy S21. For the first few weeks I would frequently get random disconnects and had to unplug and plug back in the dongle to connect again. But since I've switched the device to Passthrough mode, I've had zero issues after several hours of driving. Thanks for a great product!