yashsingh1/xdaforums huggingface dataset:
[Android Auto General] Genebaby:
Ok, got home and my AA Wireless units were there!!!

I quickly set up my 2020 Golf GTI with the Discover Pro system, not sure what MIB version that is. Using the Config app it connected up first go, no issues. This is with my Galaxy S20+, Android 11 and One UI 3.1, it's fully updated and I just checked that during the week I got the new version of AA on it.

Then I tried the other unit in our 2018 Triton Exceed, which has the OEM Mitsubishi 7 inch screen that has no knows or buttons. It also woked easily on setting up but didn't want to re-connect after restarting the car unless I woke the phone up so I will play some more with hers and check it against mine. It probably isn't updated as much, ha ha.

Then I did have to go for a little drive in my GTI and it was wonderful until I was just down the road a bit, the music stopped, the GPS was frozen and then it rebooted.

I left it like that until I got to my destination as it wasn't connecting again and when I checked my phone it was saying all these things about wi-fi!!!

I have a lot of data so I only turn wi-fi on at certain locations via a Bixby routine.

Just to test, as I'd rather not leave my wifi on needlessly all the time, I setup a new routine to connect wifi when I connected to the car and it seemed to work fine all the way home.

I wasn't sure but I though before that I needed to/had to delete previous BT connections to the car? This doesn't seem to be the case.

Internet seems to work when I'm connected wirelessly, so all seems quite good, thank you team!
[Android Auto General] Dragoshiz:
Hi,

try to:

Remove Android Auto from the "Sleeping list" in the "App power management" settings of Samsung's "Device care" battery saving settings.

Move it to the "Apps that won't be put to sleep" list.

https://www.androidpolice.com/2020/05/30/how-to-prevent-apps-sleeping-in-the-background-on-android/

(scroll to "Make sure your apps don't sleep in the background on Samsung phones")

also, some units are very very sensitive to audio timestamp (mainly VW group units), this option helps to mitigate the delay caused by WiFi vs USB. This is a delay of probably less than 100ms so in most cases, you don’t need to worry about this option at all
[Android Auto General] jasalta387:
No. It only connected 3 times after trying out a lot of times (+100 attempts). I used two phones, 3 cables, all combinations of the connection mode, factory reset of the dongle.

I cannot really reproduce the steps that got the connection working those 3 times it worked. When it worked, I tried leaving the phone in the car without touching the cables or anything. When I re-started the car, the dongle won't connect :(

I gave up for now (the car battery got discharged, had to call someone to bridge the battery to start the car). I'm hoping a firmware update would help at least to get a way to get some logs.
[Android Auto General] Dragoshiz:
Hi, did you try to :

- make sure that you have enabled the Wireless Projection in Android Auto Settings

- make sure you have no active VPN connection.
[Android Auto General] Tkodrive:
Hello, I am in the USA and see the aawireless shipment has been stuck in customs for 3 days. Has anyone else had theirs stuck in customs in the USA? Has anyone received theirs or had it clear customs in the USA? I had a different package clear customs in less than 24 hours during this same time period.
[Android Auto General] Nudnik_de:
AAWireless Battery Drain

Hi there, I have a VW T6 with Discover Media Plus. When sitting on my couch I realized that my Smartphone regularly wants to connect Android Auto. It turned out that the USB port is still powered when car is locked and AAWireless is constantly searching for connection.

Is there a way to send the dongle to sleep after a certain idle time? I don't want to come to my car in the morning and the battery is drained...
[Android Auto General] Dragoshiz:
Hi as I know the power consumption of AAWireless is between 90mA and 330mA, so unless you leave it for well over 2 weeks in the car, without starting the car, this should not be a problem.
[Android Auto General] DubelBoom:
When using this device, will my phone get automatically connected to the car's BT, as it does right now with the cable? (Subaru 2020 system)

Of course along side the wifi connection to the device.
[Android Auto General] tallleroy:
If you are having trouble, please include the model phone you are using and your best description of the vehicle's head unit. There may be some commonality with the phone or head unit that the developers can work on. Or even better, a known combination of settings to get you on the road.

It is also helpful to describe the sequence of color LEDs with the trouble report.

For instance if you only see green and red, that is a problem with the phone to device radio communication. If you see flashing blue, but no solid blue, that is a problem with device to vehicle USB communication.

LeRoy
[Android Auto General] jasalta387:
of course I did that. I'm "glad" that someone with the same head unit is experiencing the same issues.
[Android Auto General] Nudnik_de:
I really would like to share your optimism. Just doing some simple math. At 330mA an 55 Ah battery is drained in 165 hrs, which is less than a week. I'm living in Switzerland where we can have really cold nights which dramatically decrease battery capacity...

...and even if it's not cold. Coming back from vacation and trying to start your car late at night at the airport w/o success is not the preferred moment.
[Android Auto General] isRaZZe:
Are any of you having heat issues as well?

The device actually works great. However, after half an hour, the device hangs up and can no longer be restarted. The case is also relatively warm. Only after a cooling phase of 5 minutes I can use the device again until it becomes too warm again and freezes.

I have contacted emil but I must honestly say that I do not trust his statements.

He claims there are no heat problems. However, I remember a post where he himself talks about putting vents in the case. So the statements do not quite fit together.

So I opened the device and I noticed two things:

1:

The case is too thick at the point of the USB port. This is also the reason for the problems with the disconnections that many report. Without the case, the cable snaps into the USB-C port much better. I think Emil is well aware of that.

2: It simply gets too warm for the chip, which should not happen. Funnily enough, operating the device without a case does nothing to prevent my freezing. But then I hung the device in front of the cold ventilation and look... 3 hours in a row and the device no longer freezes. I have now ordered a small piece of copper and try it times with it as a cooling block.

What I also find quite interesting. The current CPU (rk3308 ) is made in 28nm process. The future CPU (RV1109) is manufactured in 14nm process. Even if you can not conclude in this context, I know from personal experience that the RV1109 produces much less heat.

My very own opinion of the product:

I think it's great. A few teething problems are there, but they still need to be fixed. But I have the feeling that here is not communicated honestly.

It was better for Emil's wallet to sell the product profitably as closed source.

But for the product itself and us as a community it would have been better to make this piece of software available as open source for everyone !
[Android Auto General] netnerd:
mine shows CLEARED CUSTOMS 2 days ago 3/24/2021, that' the latest update i have.

on another tracking website, it said Estimate delivery Apr 3-6 based on DHL sh*@%$ service for their last 30 packages.
[Android Auto General] Notor1ouS-:
question to the dev:

are there any plans to boost audio volume via the settings app?

some cars have much lower volume via android auto.
[Android Auto General] Genebaby:
Thanks, that's something I'll check on my wife's phone.
[Android Auto General] Dangze:
@antman68 :

Sorry, what do you mean by "killing the click limit" ?...
[Android Auto General] maisonmdsgreen:
I used it with a redmi note 10s without problem on miui 13
[Android Auto General] antman68:
AA imposes a limit on the number of times you can press on-screen buttons before it forces you to pause and wait for a few seconds before continuing - this is the click limit. One of the things that AAWireless is meant to allow you to do is to disable this limit.
[Android Auto General] mcgyver83:
Thanks!

Happy to hear that.

I red in this long thread that there is something weird happening with MIUI and AAWireless.
[Android Auto General] valeri_s_k:
Seems that issuess are related mostly to Mi11/pro/ultra (Snapdragon 888 devices). But it doesn't mean wireless AA is unusable with these phones. Just diconnects when mobile data is lost and reconnected.

With my previous Mi9t pro all was perfect
[Android Auto General] welshblob:
And the Poco F3 which is a Snapdragon 870.
[Android Auto General] elbubi:
Hi!

Received my device. Been struggling 5 days with random disconects, lags, reboots, etc.

Finally, after changing the provided usb cable now it works almost perfectly!

Only issue I can’t solve is audio chopping when spotify is playing music and maps voice navigation triggers.

Car is Peugeot 3008 SUV (NAC), using usb direct mode and passthrough disabled, but tried every single option with no luck.

¿Any hints on how to solve it? ¿Can we expect fw v2.0 to improve this?

Despite this little issue, overall the device is FU**ING AMAZING!!!

THANKS EMIL and CHIEL!!!
[Android Auto General] Dehumanizer77:
This is not related to hardware, but software. Some older versions of MIUI (up to 12.5) are working fine, some say that some of the latest MIUI 13 beta versions are also working, while others say that they aren't, but it's clearly related to MIUI. Plus, this is not related to AAWireless only, the same behaviour (disconnecting) appears when connecting Android Auto to the car with wireless AA built in.

This thread summarizes it up quite nicely: https://xiaomi.eu/community/threads...ork-temporarily-unavailable-aawireless.64564/

As for usable/unusable, for me it's really close to unusable. Since I 1. have an operator which uses national roaming and 2. I am in the regular roming abroad often, the disconnects happen on _constant_ basis, every time the network is switched to another operator. Which is quite often, especially outside of areas with good coverage (like outside of the city).

And also, EVERY time someone calls me, the android auto disconnects, 100% of the time. This is probably related to the fact that the network also switches from 4G to 2G or something else when receiving the call (probably also operator-related).
[Android Auto General] Dangze:
VoLTE (when available) is the solution for this issue...
[Android Auto General] Dehumanizer77:
Good catch, I might try it.
[Android Auto General] Dehumanizer77:
Nope, doesn't help. Probably my operator doesn't allow VoLTE in roaming and I am abroad now.
[Android Auto General] Dangze:
Probably, I may soon face the same problem as I will be travelling abroad. Fortunately, I will not be receiving a lot of calls... :(
[Android Auto General] znel52:
Any word on when 2.0 firmware is coming? Thought it was coming around the same time as companion app update? I understand production issues are probably their main issue but wish they would at least throw us a bone. Info on firmware updates has been lacking.
[Android Auto General] sibesaver:
Yes some sort of communication would be great. Even if technical difficulties have arisen to delay release communication would at least keep people a little bit happy. Otherwise I think this project may be doomed with competition coming out.
[Android Auto General] -Loom-:
Indeed. At the beginning there were constant updates from Emil here, which are really lacking.

I really hope the software side still gets some love from the devs.
[Android Auto General] SenorValasco:
I agree. I live in hope that the update, if and when it arrives, will fix the frequent random disconnects I have been experiencing. Because of this issue I have removed my AAWireless device from the car and reverted to wired AA.

I understand that the developers have other issues to deal with, but as each day passes my device gets ever more likely to become just an expensive paperweight.
[Android Auto General] MDicnMan:
Disabling the click limit already exists and works for me.
[Android Auto General] andy o:
Are you all with disconnections on 1.8.0? Do you remember having disconnections on previous firmware? Chiel said from 1.7.1 to 1.8.0 they switched from 80 MHz to 40 MHz bandwidth which should have been better (and he said they had fewer reports of disconnections), but for some of us it was the opposite. Fortunately my P4XL had the 1.7.1 firmware cached and I could downgrade and now it's fine on the Pixel 6 Pro.

Maybe you could try asking Chiel to let you downgrade to 1.7.1 until 2.0 is ready, the Slack invitation link should be somewhere in this thread.
[Android Auto General] Genebaby:
Disconnection seems to be an issue with many that are responding here, but it's not been an issue with for a long time and it was also never like they seem to be experiencing.

I'm looking forward to 2.0 in general and really want to give it a try.
[Android Auto General] 1qazwsx4:
It seems like the disconnection issue is related to changing from say 5g/4g/3g or losing signal altogether from what I've seen. Also coming into contact with other instances that may effect WiFi (hence why some people have had luck with physically shielding their devices with a form of tinfoil)

I'm on the bandwagon here too - give us a bone, what's happening...
[Android Auto General] AggelosGR:
I am using Aawireless for around 3 monthes daily.

It works perfect. The disconnect issue happens only if i have mobile data on and change from 4g to 3g 2g.

If i disable data there are no disconnects.

Since data signal is good most of the time in 1h of driving i may have 2 or 3 disconnects. It reconnects in under 3sec so it doesn't bother me.

Mi 10t pro with latest eu update
[Android Auto General] Rom4egT:
I've got disconnections with updating app to 2.0 beta version

plus appearing OK notification in my ZTE Axon 10 Pro after getting my car off

Now switched to previous version of an app with forced Wi-Fi 2.4 Ghz . All seem to be good.
[Android Auto General] SOFO888:
I did not have any disconnects since my last post.

I have a new phone plan with a new SIM from another provider since beginning of March. Perhaps this helped me...I don't know. I'm just guessing...
[Android Auto General] RamonTSims:
I received a new AAA Wireless device today.. prod date 3022-4-10, model cs317-e1w3. Thank you.
[Android Auto General] antman68:
Do you mean using AAWireless? That was my point: AAWireless offers this but not when using passthrough (which, as the name implies, simply passes through the signal and doesn't allow any of the additional features to be used).

I can use my AAWiresless in non-passtrough mode but there are problems , such as losing control of media volume aster a notification or the Assistant going mute after dictating a text, so I have had to use passthrough. My hope is that FW 2.0, if it is ever released, will allow me to use AAWireless as advertised, not compromised.
[Android Auto General] MidnightJava:
After driving around for over a week, I believe this took care of my disconnect problem. The data drop-outs are still happening, but switching to pass-through mode and turning off wifi scanning and Bluetooth scanning seems to have reduced them. It's not unusable now, but the drop-outs are annoying. The device is either underpowered or the firmware needs optimization, I think. Hopefully, a future update will address it.
[Android Auto General] JoePryor:
The developers are having some stability issues with the 2.0 firmware. It will not be released until all the bugs are worked out. They have enough headaches at the moment, and they don’t want to overwhelm the support team with unnecessary issues.
[Android Auto General] antman68:
I would have thought that helping people who already have units but can't use them as advertised should be a higher priority than getting more units (which have the same issues) out the door.

Your comment about "unnecessary issues" is very telling: by selling AAW through a crowdfunding platform, rather than through traditional retail channels, the AAW team can deny any warranty liabilities or performance guarantees because, using the usual disclaimers around crowdfunding, they can claim that their product is still in development. Otherwise, these issues would be very much "necessary". Of course, strictly, we never ordered our AAW units, we contributed to the project and the units tha we received were just "perks".

Of course, units out = $ in (don't have a Euro key) whereas fixing problems in units already out in the market brings in nothing and, with increasing numbers of competitors, including the MA1, perhaps they are just trying to rake in as much money as they can before closing the doors. They will try to fix niggles and even provide refunds and replacements while they are still actively selling because they don't want to scare off the potential customers but the focus on shifting more units over fixing ones already supplied is beginning to look ominous.
[Android Auto General] 1qazwsx4:
Well then maybe the developers should show some transparency and actually post about that in this thread. We were told a month ago that the latest firmware was a week or two away. People wouldn't be spamming here if they were given some details. Bit of irony there mentioning about overwhelming the support team... It's already a headache with buggy releases yet they're happy to keep pumping out devices - too hard to post an update in this thread like Emil does with Indiegogo updates relating to shipping?

Of course people are guna get annoyed watching them fire out loads of devices while theirs is left sitting on a shelf near useless until they receive some firmware updates.
[Android Auto General] JoePryor:
The issues you are referring to are not unnecessary or trivial. By “unnecessary issues” I was stating that releasing the 2.0 firmware before it is 100% ready would create those issues. I’m sure the developers want to find a solution for all user issues and I believe they are doing everything possible to make that happen.
[Android Auto General] MidnightJava:
I'll take a stable release "tomorrow" over a buggy release today any time.
[Android Auto General] 1qazwsx4:
No one is arguing the fact that a stable release is preferred. No one at all. The issue is being left in the dark without any news other than "we've shipped devices to *insert country here*" on Indiegogo.
[Android Auto General] znel52:
This. 👌
[Android Auto General] beanko:
I just got a new AA Wireless (my third) today. No issues whatsoever with the first two. This one will not connect to my phone, pixel 6. I tried both of our phones. Stayed flashing green until I switched to usb direct mode. Now it stays flashing blue. I tried the faq trouble shooting suggestions with no success. Any ideas?
[Android Auto General] nvleafs:
I'm getting a strange issue after factory resetting my phone. This was working flawlessly since I got it. I had originally connected to it with my S10e when it was on Android 11. After updating to 12 everything still worked fine.

I factory reset my phone recently to breath some new life into it and now I can't get AA wireless to work. The Android Auto icon shows up on my cars screen but clicking it just locks up the display for a few seconds and Android Auto never opens.

My car is a 2019 civic and AAWireless is on version 1.8.0.
[Android Auto General] Genebaby:
Did you reset the AAW as well, that would have been a good combo.
[Android Auto General] nvleafs:
Yes - that's via holding the button down right? Is there anything else?
[Android Auto General] Genebaby:
You hold it down, and you see it turn off, or something to make sure it's doing the reset. It has been fiddly.

With a reset AAW and phone I would be looking at the cable next.
[Android Auto General] droidDHD:
After much of ROM search - I can confirm that year old Xiaomi EU on Mi 11 Ultra plays nice with AA wireless- both sim can receive , make calls without disconnecting.

So if there are those who have given up and let AA collect dust this is worth trying.
[Android Auto General] l3s:
On Pixel 6 I also had such a similar problems. Right now mine works with the following setting:

USB mode: MTP

Passtrough: Enabled

Start/Stop: Enabled (without that never connects)

Auto video focus: Enabled

Wireless projection: Enabled (in the android auto developer settings)

App version: 2.0.0

Firmware version: 1.8.0

Android Auto Version: 7.4.620964-release

Android version: SP2A.220405.004
[Android Auto General] Genebaby:
I drove that car finally on the weekend and it again didn't want to connect via BT so I went into settings, changed it to Direct and right away it was conneting and up on the screen. Interesting that the device would affect the smooth and easy BT connection that it relies upon to work. This sort of behaviour makes it tricky to give to mainstream users.

Hopefully FW 2.0 is a game changer in reliability of the connection over time. Other than that it's a process of making sure the cable doesn't get slowly but surely unplugged a bit every time you use the car, and we're golden.
[Android Auto General] Snoogins34:
Hi everyone:

I've been lurking and reading many of these messages over the last month or so since I got my AAW. I believe that I've been seeing some of the same behavior as @Olorin2 (#2443) or @josefsch (#2510), among others. In my case, I've been able to work around the issues.

First, my setup:

Car - 2019 Jeep Gr Cherokee (UConnect head unit)

Phone - Galaxy Note20 Ultra (US version), Android 12

AA version - 7.4

AAW settings - Start/Stop enabled, no Passthrough, everything else defaulted

Issue: Everything will work fine for 2-3 weeks or so, with the exception of a failed BT connection every once in a while. Here, I can just manually connect via BT to the device on my phone or unplug/reconnect the unit and then everything fires up from there. However, eventually I will get the "Looking for Android Auto..." behavior where BT and Wi-Fi connections work fine but the projection never starts on the head unit. The AAW unit is blinking blue when this happens. Once I see this, nothing I change gets me out of it. I've tried switching to the different USB modes, enabling Passthrough, disabling Start/Stop...none of it changes the result. The only thing that did it for me was the long list of steps that someone posted earlier that they got from Support. Namely, this routine:

- 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

Once I go through this, the AAW unit works again and the cycle repeats. The second time this happened, I skipped deleting cache & data from Google Play Services, because that seemed excessive to me and I didn't know what else that affected, and it still fixed my issue. It's a pain for sure, but I wanted to at least share what's been working for me. Hopefully, firmware v2.0 will see the light of day here soon, and the product will be more stable. I've been as frustrated as others with the lack of communication in the Indiegogo updates - interesting that there were a lot of earlier updates before I got my unit that talked about ongoing issues and upcoming fixes, but once they hit v1.80 that all stopped.

Thanks to all the contributors!