yashsingh1/xdaforums huggingface dataset:
[Android Auto General] meiser:
Hi,

I tried to make an outgoing call via BT when connected to AAWireless, but it failed. I verified that I'm connected to the car's BT, not AAWireless's BT.

How can I make it work?

Thanks for your help.

Regards,

meiser
[Android Auto General] tallleroy:
When you are not in your vehicle, power the AAWireless device with a USB power supply. Any wattage power supply will be fine.

There is nothing you can see or do with your computer, and the USB support on your computer may make the device unstable.

Using the AAWireless app to change settings works fine when connected to a USB power supply.

LeRoy
[Android Auto General] usedr:
I got it, sort of, working on my Mi Mix 3 with stock MIUI 12!

https://xdaforums.com/t/aawireless-...is-connected-wirelessly.4252187/post-84741761
[Android Auto General] Spindlewood:
When AA functions don't work as expected, try clearing the AA cache. This usually has worked for me. But, if you have never had calls working, it's a long shot. I presume you checked the BT settings to make sure both calls and audio were enabled.
[Android Auto General] Genebaby:
I'll try the cache clearing on my wife's phone. The AAW in her car is a bit sketchy. I thought I got it working fine on the weekend over two small trips when I was in the car. Then she reported it was rebooting the headunit, not repeatedly, but it was happening. So I changed her setting to direct and again it tested ok just sitting there.

Now it's still doing a reboot now and then and she just showed me how the music stutters really badly when she just got home, so I put it back to MTP for now.

I'll clear the cache and see how she goes.

How can we get logs to the AAW team if we need to?
[Android Auto General] Nexus6P:
That worked for me. Thanks for the help
[Android Auto General] TheUntouchable:
Have you ever read the FAQ and tried that..?

Support

cpeb.freshdesk.com

Also:

They said providing logs will come in the future with a firmware upgrade in one of the last updates on indigoo:
[Android Auto General] Genebaby:
When I was looking at the audio timestamp config it said it was for VW vehicles, this is a Mitsubishi, and I haven't seen a need for that in my own VW.

The Mitsubishi is either rebooting randomly, or rebooting and doing the audio thing, at the moment.

I did remember something about the logs but not where I saw it, thanks for the reminder about it being an OTA, I thought maybe they could harvest them now if need be.
[Android Auto General] TheUntouchable:
Thats right, the fix is mainly for VW but perhaps it also works on your Mitsubishi, who knows :D
[Android Auto General] Delecron:
Does anyone have optimizations for the 2020 Palisade with the 10 inch screen? Like changing the DPI to get split screen?

Also, anyone else getting constant connection requests even after the car is off?
[Android Auto General] Nudnik_de:
I have the same issue when at home and car standing in front of my door. USB doesn't seem to switch off on multiple cars, e.g. I have VW T6.

On the one hand I'm concerned about battery drain of my car. On the ogher hand it's teally annoying AA always restarting and trying to connect.

There should be a sleep function added to AAWireless!
[Android Auto General] Wimmme:
Just had a first issue, searching didn't bring me an obvious solution. When using Google assistant, the dialog comes up on the car screen, but the sound coles out of my phone. Don't have that when connected through cable.

Oneplus 7t on android 11, latest AA version, car is Skoda Superb 2018 columbus.

Anyone an idea?

Will try again tomorrow and provide more info whenever available.
[Android Auto General] ejufrhef:
jungs, das ist ein englischsprachiges forum, wie wärs wenn ihr englisch redet???
[Android Auto General] Snirpo:
What phone? Blinking green is always a phone to device side issue.
[Android Auto General] Snirpo:
Can you share your device name? I'll have a look in the logs. Please try to run the update connected to a power adapter / laptop as well.
[Android Auto General] Snirpo:
According to this message the date and time of the head unit is wrong. Does it work wired?
[Android Auto General] Dr_MaZe:
I had the same issue. If you use a VPN then turn it off for the update. That's what fixed it for me
[Android Auto General] ejufrhef:
Redmi Note 10 Pro, we were talking a couple of pages ago, i had the same problem there. had hoped the update would fix things, but nope
[Android Auto General] J_E_F_F:
Thank you, as noted below

Thank you, that fixed it. I use Blokada as a pseudo VPN for ad blocking and disabling it for the update worked. (note also have the default Android Auto App bypassed in Blokada settings.)
[Android Auto General] rajil.s:
The new 2.0.0 firmware did not make any difference in my Hyundai set. I still can only use USB in direct mode and Pass-through enabled. If i disable Pass-through the device loses connection after some time.
[Android Auto General] RealNBB:
@pacogeno

Talking spanish in an english spoken forum sucks really hard.
[Android Auto General] mbower712:
I did a factory reset and it works again
[Android Auto General] Genebaby:
So it still works, just in passthrough?
[Android Auto General] rajil.s:
Yes in passthrough mode it is quite reliable.
[Android Auto General] ToesNZ:
Here's my experience setting up AAWireless with an Atoto S8 head unit (One of the better Android head units which i see recently says it natively supports Wireless AA but not at the time i purchased).

My connection is rock solid and everything is working really well.

All settings are default.

I did hit a few speed bumps but all part of the fun, Was using an MI9T Pro that just would not connect, came on here and had a look and found they have issues so went down and purchased a new mid range Motorola Edge 20 Fusion Ph (What a good choice, better in every way and a whole lot of other stuff just works now).

In the process of setting up, Version 2 of the firmware came out and i also got a firmware upgrade for the head unit which fixed other issues with Android Auto but broke AA Wireless.

Here's the steps i took that worked first time round before upgrading and worked again, firmware 2.0 connects better than before as well

Clearing bluetooth cache on phone in settings Apps (switch show system apps on)

Clearing data on Android Auto

-one of these two or both is what stopped AAWireless being flakey in connecting

Reset Android Auto back as per AA Wireless instructions

Use the usb cable to create a wired connection to your head unit and start android auto

Then switch off, hook up the AAWireless unit

Switch on again and i now have a rock solid AA Wireless connection

Love AAWireless, it's a game changer, hope this helps others
[Android Auto General] Andres.Navas:
Hi @pacogeno

It's configured as dongle mode, No passthrough, DPI 103, WiFi region Spain, 5GHz, Channel 153. Nothing else!

BR
[Android Auto General] SteveI:
FW2.0 seems to be working a treat for me; I've not had a single disconnect of any type (Head unit reboot; or Dongle disconnect) in 24hrs, fingers crossed that continues.

Samsung Galaxy S22plus (AAW in dongle mode + VAG Crash fix + Wifi region set as UK; all other settings default)
[Android Auto General] Genebaby:
Should changing your wifi region affect your DPI?
[Android Auto General] phoinix_gr:
Is there someone with Poco F3 and/or Xiaomi Mi 11 phones, that has been able to workaround the issue with AAWireless disconnecting when receiving or making a call?

It is the same for me, even after updating to MIUI13-android12
[Android Auto General] valeri_s_k:
I am with Mi 11.

The only workarount I have found is downgrading to MIUI 12.6 21.10.22 xiaomi.eu rom version. No disconnection during calls nor when loosing mobile data.

The only issue that came with AAWireless 2.0 firmware is that if you leave the car with phone in the pocket and AA running, move a few meters away and loose WiFi connection with the dongle, AA freezes and have to unplug/replug the dongle. Same happens with dongle mode enabled/disabled

With 1.8 firmware it reconnected immediately without freezing. Seems some change from 1.8 to 2.0 causes it.

May be I am missing something in the settings - any advice will be appreciated.

Other than that, with 2.0 firmware, AA is stable and have no single disconnection for now.
[Android Auto General] pacogeno:
O gracias,muy amable
[Android Auto General] mbower712:
I'm not entirely sure what happened unless it was also connected to my home WiFi when I factory reset and had it setup in the garage. On the way to work it was offline. Connected and worked wireless AA, but no Spotify or Google maps, no data connection. Did airplane mode on and off to cycle everything, still no dice. I'll have to mess with it again.

I'm starting to wish I never updated the firmware... 😕
[Android Auto General] -Loom-:
When using the device in dongle mode, can the VAG crashfix still be enabled or is it like passthrough?

Actually, in passthrough the fix is still selectable, but for my understanding it's not getting applied?
[Android Auto General] nostraslo:
I just got an update to 2.0. I can download it, but can not update my device. My firmware version is 1.8. Every time, when I press start update, it fails.

After that I cleared cache, cleared data from app, but nothing help.

What could be wrong?
[Android Auto General] snapilica2003:
Any troubleshooting I can do to figure out why I cannot get my device to work in "dongle mode"? I have a S21 Ultra and a Mazda CX-30. The device works with "dongle mode" disabled and passthrough mode on or off.

The moment I turn on "dongle mode" the device gets stuck at blinking green LED and nothing happens. Basically my phone doesn't connect to the AndroidAuto-xxx WiFi network. I've tried resetting to factory defaults multiple times with no luck. Turning off "dongle mode" makes everything work again.

Also, running the troubleshooter doesn't work as the "factory reset" that it does in the process always turns "dongle mode" off, while manually resetting doesn't.
[Android Auto General] Greg2Lu:
Ordering mine around 17 april, got a shipment yesterday, currently on route; I'm eager to try! Good workon AAWireless @Emil Borconi ;)
[Android Auto General] Mojito85:
I had the same problem.

I solved it by connecting the device to a pc USB port
[Android Auto General] Snirpo:
Really really hard to grasp to be honest. 2.0 doesn't really has any logic changes, only new features. I'm always baffled when these things happen.

But that's the nature of the beast I guess. AA itself changes, phone updates change stuff and head units updates also change or break stuff.
[Android Auto General] Snirpo:
In troubleshooting we indeed turn dongle mode off, exactly because of the problem you're describing. The logic in Android Auto itself changes.

Android Auto waits for an active Bluetooth handsfree connection to the car. If that doesn't happen, AA will never start and the device will stay blinking green. But I've also seen this happening when AA gets in a bad state. Resetting data of AA might help + re-pairing the device via Bluetooth.

But to be honest, if you don't have any issues in "normal" mode, I'd just use normal mode.
[Android Auto General] Snirpo:
Do you have a VPN enabled by any chance?
[Android Auto General] Snirpo:
Dongle mode has no influence on the other settings. Passthrough does, VAG crash fix should not be selectable in the app when enabled. That's an oopsie probably :)
[Android Auto General] Snirpo:
No surely not, does it?
[Android Auto General] snapilica2003:
When I factory reset AAwireless I see that all the bluetooth pairing on my phone are deleted anyway (probably by the app itself). But I will try to reset data for the AA app see if it fixes it.

To double check the procedure:

- put AAwireless in "dongle mode"

- factory reset AAwireless

- after reboot, unplug AAwireless

- clear data on AA on my phone

- connect my phone to my car via cable and setup AA like it's the first time

- turn off engine (or just unplug phone?)

- connect AAwireless to car USB

- turn on engine

- wait to see what happens?

Is this correct?

Also, when in dongle mode, does "passthrough mode" still matter?

I will probably end up using normal mode, though normal mode also has the issue with the bluetooth. When the device connects to my phone, the bluetooth handsfree profile stays connected for calls on top of my car's bluetooth handsfree as well.

Then I run into the issue with making or receiving calls that are not redirected to the car's bluetooth because of this. So far I see I can circumvent this by manually disconnecting from the devices's bluetooth from my phone, but I have to do this every time the device connects. Is there a workaround for this?

I was under the impression that "dongle mode" fixes exactly this issue and there's no need to keep a handsfree connection open on the phone that will create this issue in the future. What I see when I use "dongle mode" is that the bluetooth icon on my phone is different, and the connection doesn't work as handsfree with calls redirection.

Also want to ask, when I turn off my car the USB still has power for 5-10 minutes and then shuts down. I see that because of this, when I turn off the car but still stay around the car for a bit, my phone will keep beeping that it's connected to AA. Then disconnects, then reconnects, for a few times.

Is there a way to circumvent this? I've tried using Start/Stop feature but AAwireless stopped working completely when I enabled this feature.

PS: Sorry for the long post.
[Android Auto General] Snirpo:
No problem. I forgot to tell, the normal procedure for dongle mode is actually like this:

(Copied from Motorola manual)

Setting up your adapter​

Before setting up your adapter, connect your phone to Android Auto using a wired USB connection following your vehicle manufacturer’s instructions.

While the Android Auto connection is active on your car screen, unplug your phone from the car and immediately plug your adapter into the same USB port.

I'd do this:

- Factory reset AAW (puts it in dongle mode by default)

- reset AA cache + data

- re-pair to device

- follow moto instructions above

The start / stop issue is interesting. The LED probably goes white when enabled? At that point the companion app is in control of the starting and stopping. Could you share your device name? So I can check which phone you have and possibly some error logs.
[Android Auto General] snapilica2003:
Yes, LED goes white when I turned on start / stop and there's a constant notification on my phone from AAwireless app. But there's no connection to the car. And I made sure that I've selected the proper name of my car's bluetooth connection.

My current device name is 0YNBBSER but I observed that this changes every time I factory reset the device and every time I switch on or off "dongle mode".

Also, when in "dongle mode" do the passthrough and WiFi settings still do anything? Like turning on/off passthrough or setting the proper country on WiFi menu (other than United States).
[Android Auto General] Snirpo:
I'll check. That's weird, what does the notification say when connected?

Dongle mode has no influence on the other settings. Passthrough mode does, cause we don't intercept data in passthrough mode.
[Android Auto General] Snirpo:
Ah an S21 I see, I'll try to get a hold of a newer Samsung.
[Android Auto General] Genebaby:
Yes, I tried it in my Golf with MIB 2.5 Discover Pro High, a Garmin unit.

Set to Australia wifi the display shrunk, so I put it back and the display filled the screen again.
[Android Auto General] Snirpo:
That's weird, I expected the display to be upside down...

Just kidding of course :) I'll investigate.
[Android Auto General] Genebaby:
Thank you. I can confirm that in all situations the display is the correct way up!!!
[Android Auto General] dscline:
Just to confirm, you're talking about new firmware that you were testing for this issue, not the publicly released 2.0 firmware, correct? I have a Kia EV6 that initially worked with out of the box settings, but with a few disconnects. I changed to passthrough to improve reliability. Then a week or so ago I updated the infotainment system in the car. Then shortly after I got the 2.0 update. I decided to see if non-passthrough would be more reliable since 2.0, but now it doesn't work in non-passthrough at all. I ASSUME that's because of the SSL issue some of you have reported on the latest Hyundai/Kia updates. But if the fix you're speaking of is built in to the public 2.0, I need to rethink that.
[Android Auto General] J_E_F_F:
what are all the different LED states of the AAW device?

Colors, flashes, etc and their meanings?
[Android Auto General] tomballpkrxda:
You are correct. If you scroll up, one of the developers asked me to test a Hyundai/Kia fix related to the new April 2022 update. It worked great. @Snirpo
[Android Auto General] Snirpo:
@dscline Can also enable the firmware for you if you want to test? Need the device name for that. This firmware also fixes SSL related issues for aftermarket Sony head units. So if someone has a Sony where only passthrough is working, I can also enable it for a test.
[Android Auto General] l3s:
@Snirpo I have Alpine ilx-f905d device with Pixel 6, using 2.0.0 firmware and 2.9.0 app. In my case the issue is similar, I mean it is working only passtrough enabled. If I disable passtrough, the phone connects to AAWireless successfully, I can see the notification on the mobile phone Android Auto connected, the LED changes to solid blue, but on the Alpine screen I do not see anything, over there it does not display the connection. With passtrough enabled, the connection working well.
[Android Auto General] Snirpo:
Very likely to be the same issue indeed! What's the name of the device? I'll enable the firmware.
[Android Auto General] snapilica2003:
So I have some updates on my situation and wanted to share for future refference. I managed to get it working in "dongle mode" and also made "stop/start" work. Actually it seems that the only way for "dongle mode" to work was to also have "stop/start" enabled and functioning. It seems that withtout it my phone will not connect to the WiFi created for wireless connection (which is called "AndroidAuto-xxxx" when in dongle mode, different than "AAwireless-xxxx" when in "standard" mode.

The issue was the wifi being turned off by the system. Newer Android OS (11 and above I believe) have this WiFi setting option that turns off the WiFi when you leave a "known location" and turns it back on when you get back to those "known locations" so the issue is that the bluetooth beacon that is sent by the dongle is not enough to trigger WiFi to turn on and connect to the WiFi.

Note that this issue does not manifest itself when I am using a car with proper built-in Wireless AA. I have a Skoda Karoq that has built-in wireless AA and even if my WiFi is turned off, it will turn itself on to connect to AA, just not with this dongle.

Anyway, long story short, because when "Start/Stop" is active I have a constant notification on my phone from the app indicating the status (connected/not connected/etc.) it showed me "wifi is turned off cannot connect" or something simiar. So when I manually turned it on, everything started working. My phone connects imediately to my car with "dongle mode" ON and "start/stop" ON.

What remains an issue is that it will not work with "dongle mode" ON but "Start/Stop" OFF. It seems that without the helper app "helping" the phone to connect to the wifi of the dongle, the phone will not do it on its own. This is not a big deal for me, as I want to have "start/stop" enabled anyway.

So bottom line, everything is working perfectly fine for me now.

Hope this helps others and helps @Snirpo to figure out if they might want to change some stuff for their app.
[Android Auto General] l3s:
@Snirpo many thanks!

AAWireless-DBFcpUEF
[Android Auto General] Snirpo:
Enabled it, you can update via the app. Firmware is called "Hyundai SSL fix", but don't be scared, it's not only for hyundai's ;)
[Android Auto General] albertron:
Does it work with a rcd330 radio?
[Android Auto General] x10isrooted:
I just wanted to report that after the update with firmware 2.0 i had absolutely no interferences and dropout issues anymore when playing music. It could be that also samsung did something on the firmware in the meantime because i saw in the changelog of AA that Samsung team have fixed some issues with connection related topics. I have set in AAWireless the WIFI region to Germany and made no other changes and on my route where it always happened. For me it also seems that audio quality has improved. Amazing work and thanks for the update! I have the 2nd gen hardware and a Samsung S20 with snapdragon. Car is a Opel Corsa F with headunit from Bosch (The one without navigation inside). I hope it will stay like this.

By the way i have not changed it to dongle mode. Has this any advantages over the other setting? Otherwise i do not want to mess around with that unless everything works now.
[Android Auto General] Shammy7861:
@Snirpo Will you please push the new firmware to my unit to really appreciate it for testing AndroidAuto-AAWyp6P6DPq.

Thanks Sham
[Android Auto General] Snirpo:
It's probably helpful to explain for everyone how the process works :) So here we go:

When start / stop is enabled our companion app is in control of starting up AA. So wether dongle mode is enabled or not, it doesn't matter, because the standard bluetooth bootstrap of Android Auto is not used. That's also the reason why wifi is not turned automatically on in start / stop mode. Android Auto, being a system app, can do these things. From the companion app we cannot from Android 10 and above, hence showing the notification to turn on wifi.

So basically using start / stop completely invalidates the different bootstrap logic in AA regarding dongle mode, because bluetooth (to the device) isn't used to start up the process. It doesn't really matter if you use dongle mode or not.

"Note that this issue does not manifest itself when I am using a car with proper built-in Wireless AA. I have a Skoda Karoq that has built-in wireless AA and even if my WiFi is turned off, it will turn itself on to connect to AA, just not with this dongle."

This should also happen with AAWireless, AAWireless == 100% native, except when using start / stop mode like I explained above, when the companion app controls the bootstrap. AA always turns on wifi when using the native bluetooth bootstrap.

Why dongle mode doesn't work in your case is a bit of a mystery to me though...

So summary:

AAWireless + "standard" mode == emulate native Wireless HU, does not need the companion app.

AAWireless + dongle mode == works as native dongle, like Motorola MA1, does not need companion app.

AAWireless in dongle or standard mode + start / stop == does not use the native bluetooth bootstrap, but trigger wifi connection based on handsfree connection of the car. Needs the companion app, not native.
[Android Auto General] Snirpo:
The Hyundai SSL fix firmware you mean?
[Android Auto General] Snirpo:
Thanks for the feedback! Did you also change the wifi channel?
[Android Auto General] sidofido:
I have 2020 Hyundai i30N and Pixel 6, but I am still facing some random disconnections during the ride with the fw 2.0. I tried every possible option in the settings, but nothing helped. I am not sure if it is related to the android 12 and pixel or it has someting to do with my headunit in the car. @Snirpo could you please push the new fw for me? Device: XHX3rphz
[Android Auto General] Snirpo:
I can, but for disconnection issues I'm not sure it would help. Are you sure it's random? Doesn't it happen at exactly the same location everytime? In that case changing the wifi channel could also help.
[Android Auto General] x10isrooted:
nope. Left everything on default. So far no adjustments were needed.
[Android Auto General] Shammy7861:
Yes please the firmware I have installed on the unit is 2.0.0. I am happy to be your giney pig tester for all your needs.
[Android Auto General] Snirpo:
Enabled it already :)