yashsingh1/xdaforums huggingface dataset:
[Android Auto General] ShadowJP88:
An having a little connection problem.

When i start the car, AA connect directly, run for...2 seconds maybe... And than close and it may take 30 seconds to have it back.

I have a pixel 5 and a Mazda with aio
[Android Auto General] Genebaby:
Has it worked before nicely?

Have a look at the lights and what they are doing during this process. It almost sounds like the power is being cut, after it starts, then returns.

Look at the lights and see what happens once it's connected and then closes.
[Android Auto General] iTaiwan:
For long trips I don't actually mind wired AA. It has the benefit of also charging my phone (Pixel 3a XL=no wireless charging). It is on small serial trips running errands where wirelessness shines. No more grabbing the phone to disconnect, only to hook up again 5 minutes later -- this after disinfecting my hands and sometimes the phone. (Or that's how I imagine it, since my unit hasn't arrived, yet., haha)

On a related topic, there are anecdotal reports of natively wireless AA HU draining the phone rather quickly. Sometimes this is attributed to people using older phones with not-so-healthy batteries. But I do wonder how common this phenomenon is, and how built-in wirelessness compares to AAWireless in terms of battery drain. And how much room there is for optimization. (Sorry, more questions than answers...)
[Android Auto General] Saison2018:
Thanks a lot to you and @Genebaby for adding your comments.

I finally think also that Wireless AA is better for short travel as we can see from my experience and latest comments from different people that confirm there will be to much battery draining.

This solution is still great to allow us to enjoy Android Auto experience, whatever the situation (wireless or wired).

Thanks again
[Android Auto General] meiser:
I'm using AAW because I can then use the car Dash charger or QC3.0 charger for my phones instead of being limited to 0.5A via the AA USB plug.
[Android Auto General] DevAuto:
I am using AAWireless with a Qi Fast Charger and have had no problems using Waze (or Maps) while streaming from Spotify (or using Simple Radio) on long trips 8 hours or more. My charger is fast enough to charge my S10 Plus to 100% while I am using it. I think what you need is the right fast charger and you should be fine.

This is the one I am using and have had great success with: https://www.amazon.com/CEGAR-Magnet...9Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU=
[Android Auto General] jackfate:
I finally did get AAW wireless working on my c8 after following these instructions and also forgetting my home wireless network while I was doing the setup in the garage. Could being connected to a wireless network interfere with AAW setup?

In any event, I've been more than impressed with the speed and the stability of the connection. I'm able to stream audio not more than 25 seconds after opening the door and have had no further issues outside of sometimes getting auto-play even though I have it disabled in settings.
[Android Auto General] Genebaby:
Your home wifi shouldn't interfere with connecting to AAW. I'm on my home wifi everytime I step out the door and AAW connects fine.

Deleting caches and app data and forgetting BT connections and resetting your AAW device is a good start. I'm not sure if going the extra mile of Google Play Services data is needed but I did it and it wasn't the end of the world.
[Android Auto General] exge:
i finally got it working properly for MIUI.

showing my settings for other MIUI users that are stuck and going to give up

This is on a Poco F3 running MIUI Global 12.5.1 Stable on Android 11
[Android Auto General] Genebaby:
Lately I am getting random auto-play as well. Just now it auto-played the song when I got in the car, but not when I got back in after going to the shops.
[Android Auto General] Genebaby:
I did some testing this week to confirm something with the audio glitch issue.

I think it must have been after the 1.4 update but I began to notice that the spot just near my house that always glitches was no longer doing so. This was with the Motorola I had the other week and now with my restored Galaxy S20, before and after the other big reset I did.

Strangely, the audio was smooth on normal 5ghz wifi, and when I test on 2.4ghz it will glitch again.

Both settings can glitch in the other usual spot I travel a lot too, and at other random times, but I think it's less than before.

So there is hope there somewhere!
[Android Auto General] Snirpo:
There's no difference in power consumption between native AA wireless head units and AAWireless. We are doing native AA Wireless :)
[Android Auto General] osm0sis:
That's been there since the beginning. Just like focus stealing being sporadic (even with the AA developer option set), it's unclear if that's an AA bug or an AAW bug.

YT Music is even more unreliable and will lose its playlist and/or be difficult to start from AA, but this is more a YTM bug or a OnePlus bug, I've found, and locking YTM into memory using the OnePlus Launcher has improved that part greatly on my 8T.
[Android Auto General] mike.s:
If your head unit limits charging to 0.5 A, that's its problem. A properly designed head unit will provide a USB Charging Downstream Port (CDP), which can deliver 1.5 A while AA is connected.
[Android Auto General] Mips81:
Vous avez juste besoin de désactiver l' optimisation MIUI

https://xdaforums.com/t/disable-miui-optimization.4260643/
[Android Auto General] 1qazwsx4:
Anyone having an issue whole listening to music then accepting a phone call, after the phone call ends, music will be played via the PHONE speaker instead of the car speakers? Only had this issue since 1.4 OR could be AA update related.

Running android 11 and miui (never had issues when I was running 1.3 and about a month ago) please note after the phone call ends and music starts from my phone speaker that it IS connected still via Bluetooth AND has AA wireless connected. Anyone else experiencing this?
[Android Auto General] Genebaby:
I've never had it happen until recently. It always used to respect the setting. No biggie.
[Android Auto General] osm0sis:
I mean I'd like it if it (and focus) could be reliably fixed, just saying it's widespread, ongoing, and I'm not sure where the fault lies. 😛
[Android Auto General] Snirpo:
In 1.4 we kill the dummy handsfree profile (needed for AA) when AA is running, to solve calls not going through the car speakers (especially for Pixels). But it seems to do more harm then good... Causes oddness on different phones. Reverted that in 1.5, which will be released this evening.
[Android Auto General] sibesaver:
So since it's going to be reverted will there be a fix for Pixel phones for the phone call issue?
[Android Auto General] Snirpo:
It didn't really help, we got some reports it helped, but seemed placebo. But we are also completely revising the start / stop mechanism. This new way we are not using Bluetooth from AAWireless at all anymore to start up AA. This also means there will be no conflict between dummy handsfree of AAWireless and the handsfree of the car. This should solve all issues regarding to phone calls.
[Android Auto General] sibesaver:
Thanks! Switching away from Bluetooth is a good idea I believe, It's one of the wonkiest things on Android phones. I consistently have trouble with other devices as well with my pixel 2 xl.
[Android Auto General] HofaTheRipper:
@Snirpo is there any source to download older firmware files to downgrade manually for troubleshooting? It would have helped with my last issue after updating to 1.4.

It would be nice if there were an option in the companion App to choose a specific version.
[Android Auto General] Snirpo:
Yes, there is: https://drive.google.com/folderview?id=18R-KYbOSt5jBeb3dtqRs-EPrBRaGE9sX

I did think about adding a downgrade option in the app, but it's a bit tricky. If we do that, we don't only need to test updates from version x to y, but also downgrades all the way back down to 1.0.0. Normally it wouldn't break, but I don't really feel like testing from the newest version to the oldest, to be sure the board doesn't accidentally brick :) It gets a bit too easy to just switch around versions all the time if we provide it via the app. And we don't really want people to use older versions.

However what I could do is provide an option to switch back to the previous version (which is still on the board actually, cause it has an A/B partition layout).
[Android Auto General] HofaTheRipper:
ok i see 😅. a switchback to the previous version would be perfect.
[Android Auto General] HofaTheRipper:
Am i right, that the e1w1 files are for the very first batch and the other e*w* for other production batches?
[Android Auto General] tallleroy:
Yes, the chip shortage has caused a number of chip substitutions to keep the device in production. Because software for the substitute chips differs to some extent. Each unique configuration receives slightly different firmware.

LeRoy
[Android Auto General] tallleroy:
Here are the LED codes for OTA firmware 1.5.0. Solid White is now used for Start / Stop standby mode.

Solid Green, the device is booting, should complete in under 12 seconds. Both the Bluetooth and WiFi are not active until after the boot is completed.

Blinking Green, the device has activated Bluetooth and is waiting for a WiFi connection from your phone. You will only be able to pair while under blinking green.

Solid White, Start / Stop standby mode. The device has completed boot and is waiting for the Head Unit Bluetooth to connect with your phone. When your Head Unit Bluetooth disconnects from your phone, the device will return to Start / Stop standby mode for as long as it is powered. The device will not take over the Wi-Fi on your phone while it is solid white. You will be able to connect your phone to any other Wi-Fi network. Use the Start / Stop Option to enable this mode.

Blinking Blue, the device has fully connected with your phone and is attempting to connect with your head unit via USB.

Solid Blue, the device is full connected with your phone and the head unit. The first time you connect you may need to set some Android Auto permissions and some head units may also produce prompts for you to answer.

Solid Yellow, the device is loading an OTA update into memory.

Red, an error has occurred, the device will attempt recovery after a timeout.

None / Black The LED will not be active when you first apply power for a very brief time. And the LED will not be active at all when the device is ready to be flashed from your computer. It will remain inactive until the flash program completes loading the firmware and reboots the device.

RIP Blinking White

Spoiler content hidden.

LeRoy
[Android Auto General] sibesaver:
1.5 is a drastic improvement for me. From cold start to connection takes about 15 seconds. Before it was sometimes a minute plus. I barely catch the device blinking green before it's connected and Android Auto is on the head unit.

Pixel 2 XL

Kenwood DDX 9704S

Thanks so much for your hard work!
[Android Auto General] davep85:
Apologies if this has been addressed, but I started having an issue with my AAWireless recently.

When it boots up it stays in the solid green light stage and never changes to blue blinking/solid blue.

I've tried doing a reset on it using the reset pin hole, but that doesn't appear to do anything.

Any extra steps I could try would be appreciated.
[Android Auto General] DevAuto:
Please read the latest update on Indiegogo from @Emil Borconi , then check your contribution ID number. This should give you a better idea when your AAWireless device will ship to you.
[Android Auto General] MrGimpGrumble:
Has anyone who received it tried it on a honda?

I have a 2018 Honda Accord Sport

Thanks!
[Android Auto General] d_PhantoM17:
I'll try and let you know. But why doesn't the play store have the latest version? It's a Google app and should be updated first on google play store, right?
[Android Auto General] seburton:
Received mine today but can't make it works.

Seems my phone is confused with those 2 Android auto notifications:

- Connected to your car

- Looking for android auto on the second one.

Using galaxy s10 - android 11 - rooted phone - VW golf 7 - MIB2.
[Android Auto General] AndrewShahoff:
Thank you for quick respond. I hoped to get this things working , but looks like another gadget will sit on the shelf waiting potential new firmware.
[Android Auto General] DevAuto:
Sorry to hear it's going to sit on a shelf. You could send it to me, I still have at least a month to wait before my unit arrives. :D

For what it's worth, I have no doubt that @Emil Borconi will provide an OTA update in reasonably short order, he has been unbelievable with following through so far. I've been a lurker here on XDA for a long time and followed several of his projects, and I have never seen him say something that he hasn't followed through on.
[Android Auto General] TomNguyen87:
Well for AA this doesn't apply because AA update is rolling in stages, that's why not all of us can get it at the same time
[Android Auto General] gregoff82:
I've tried it on my Honda Civic 2018 Sport using a Oneplus 6T. Works flawlessly/perfectly/brilliantly/excellent! Really impressed of the product!

I'm not sure if the Accord uses the same infotainment system as the Civic though...
[Android Auto General] R7woD7wo:
Finally got it working! :) Just used the supplied USB cable, reset cache memory for Android Auto and Google Play, connect once phone to car with cable (to setup Android Auto, pass it to dvp mode to enable wireless), then connect AAWireless, set to Passtrough and got perfect connection since then.
[Android Auto General] jasalta387:
Tried other with cables?

Do you get a blinking blue light on the dongle? Have you tried switching the USB mode and enable pass-through?

I get the same: apparently this means that the dongle cannot connect with the car's headunit.
[Android Auto General] andy o:
Google Maps with Android Auto will try to use the car's GPS first, then if it can't detect that the head unit has it, will use the phone's. In fact I had to pull the GPS antenna connector from my 2016 Mazda 3 head unit in order to force Google Maps to use the phone's, cause the car's GPS is so crappy.

From what I understand Waze uses the phone's GPS always, don't know if they've fixed that or if it was even a bug, but I've seen people complain about that too.
[Android Auto General] XdaPetri:
Kia Niro 2016 and Samsung Galaxy S9 work like a charm. Thank you for a brilliant device.
[Android Auto General] morback:
Hi

I have no idea if AA is using my phone's or my car's GPS, but it seems that location is worse using AAWIRELESS (which works really well in my car, connection time is the same than the wired one, that is really impressive and convenient) than by using wired USB connection.

With Waze, I feel the app is using the wifi spot location and then, detects the phone is connected to wifi and considers the car is not moving. So the shifting on the map is weird, I mean the car is following the road but the zoom stays the same (very close, as when you are stopped) and speed is not displayed. There is also some lag is the displayed position. I tried to deactivate the Google improving location service, but result is the same (worst regarding location precision).

If my explanations are clear and someone is experiencing this as well, please share 😁

Oneplus 7T, Android 10.
[Android Auto General] andy o:
Does it do the same with Google Maps? Have you enabled background location at all times for Waze?
[Android Auto General] d_PhantoM17:
tried with the latest version of AA but still takes a long time to connect. Has anyone else experienced this issue with Huawei Mate 20 Pro?
[Android Auto General] seburton:
After looking posts here, I tried again this morning with usb in direct mode.

And it works!

It's perfect

Config : Galaxy s11 android 11 oneui 3.1

Car: VW golf 7 - MIB2
[Android Auto General] vizzze:
I disabled any kind of battery optimization for android auto and maps app, also every possible force stop for background apps.

Now seems like GPS lock is great and there's no more delay and wrong position in Maps.

Samsung is quite aggressive in disabling and closing app to save battery
[Android Auto General] franners:
19MAR now says received in distribution center @ Royal Mail. No delivery date yet.
[Android Auto General] TheUntouchable:
I have exactly the same problem. It seems like Waze doesn't really have the current location of my phone. Also, it jumps from street to street while driving and does not show the speedometer which worked when connected directly via cable :( Waze is set to always use the location and also battery optimization is disabled for it

Huawei P30 Pro Android 10
[Android Auto General] DevAuto:
It sounds like it could be related to the problem @vizzze was having with GPS positioning. Can you try this and see if it helps?
[Android Auto General] Genebaby:
While you're doing the reset, was the light solid green? Did you notice it turn off and then come back? That would signify a working reset.

Make sure the reset takes, but you may as well delete the BT profile for AAW and I would uninstall, then re-install AA Config and go through the process again.
[Android Auto General] Genebaby:
I'm looking forward to putting on 1.5 when it's available.

I am looking at the Pixel 6, depending on reviews, so it would be good if Pixels played nice. You would think out of all the phones they would be the best for AAW.
[Android Auto General] muzamil:
I am having the same issue as davep85 after updating to 1.5.0. Reset doesn't do anything. It didn't turn off even for a bit.
[Android Auto General] Genebaby:
I checked and did the 1.5 update for one of my units. Updated fine and ran fine afterwards. I will test the music playing over the next few days.
[Android Auto General] Genebaby:
You have to maybe hold down the reset switch for 5/6 seconds and let go, you'll see it reboot, then the reset is done.

I'm not sure if davep85 has the 1.5 update or not.
[Android Auto General] Snirpo:
Please contact support at https://cpeb.freshdesk.com . Most likely a defective second batch device.
[Android Auto General] Snirpo:
That's odd, cause we didn't change much in that regard :/
[Android Auto General] muzamil:
I hold down the reset switch for a good 15 secconds
[Android Auto General] sibesaver:
I'll do more testing today with an actual drive. But I completely power cycled the unit/car at least three times and it connected drastically faster each time.
[Android Auto General] Snirpo:
For resetting the device please hold the button for 5-10 seconds and let go. If you hold it for too long it will go into maskrom (flash) mode or won't do anything.
[Android Auto General] andreiav:
Hello. What's new in 1.5?

A full changelog for each release would really be appreciated :)

Thanks for all the hard work!
[Android Auto General] Snirpo:
Yes, I'll write a full changelog next week from 1.0.0 to 1.5.0 and put it on GitHub + add a link in the app.
[Android Auto General] KRGrayson:
Can anyone explain how they fixed the issue with the 2018 Chevy Mylink Infotainment system not recognizing AAWIRELESS until the 1.4.0 update?
[Android Auto General] tallleroy:
@KRGrayson

The 'new' Default USB Mode is what fixed issues with many GM infotainment systems.

Instead of presenting what should be the correct USB mode for Android Auto to the Head Unit (direct), or what most phones present as their default mode ( MTP and its variations); Default USB Mode presents a USB Mode that no Head Unit supports. When the Head Unit sees an unsupported USB Mode, USB protocol calls for it to ask the AAWireless device what modes it does support. The Head Unit then selects the correct Android Auto mode and life is good.

Prior to firmware 1.4.0, some head units (GM was not alone) would not confirm what USB Mode was being presented and begin to communicate in an inappropriate mode for Android Auto.
[Android Auto General] KRGrayson:
Thanks
[Android Auto General] skamin:
Hi @tallleroy, how can I download the 1.5.0 release to my PC? I'm having trouble updating my device directly (updates always fail). I upgraded to 1.4.0 by following the this link, downloading the file to my PC and connecting directly to the device over WiFi.

The release is not listed here.

By the way, I'm a Telluride owner with 10.25" head unit, should be similar to your Palisade. USB power stays on for while after the vehicle is turned off. The Start/Stop feature was supposed to solve related issues, but has instead created others. I'm looking forward to 1.5.0 resolving those. Any other tips you have for the 10.25" Telluride/Palisade will be welcome.
[Android Auto General] skamin:
I'm having issues with Zoom (VoIP) calls on my phone when connected to AAWireless. Calls don't get properly routed to the car audio system.

Has anyone else experienced this? Is there a solution?

I drive a 2021 Kia Telluride SX (10.25" head unit).

Thanks!
[Android Auto General] istrait:
So, AA Wireless went from something that was really awesome and worked perfectly with my 2019 Jeep Grand Cherokee with Uconnect to something that no longer works at all.

Originally I was on firmware 1.3 using the latest version of Android auto on my Jeep and had no issues except every once in awhile my phone calls for no reason would start being rooted directly through the phone or my Bluetooth watch instead of the head unit.

Support told me to upgrade to 1.4 and try it again. Once I did that, aa wireless does not work at all. Head unit never detects it, and the phone shows one Android auto notification that says connected to car and another notification that says looking for Android auto. Light on Android auto is blinking blue.

I have reset the device by holding the reset button down for 5 seconds, removed the Bluetooth and wireless profiles, reset Bluetooth cache, reset Android auto cache, reset Google Play services, uninstalled the config utility and reinstalled it and still have no luck.

Any thoughts?
[Android Auto General] tallleroy:
Hi @skamin

I don't know if direct PC updates will be available for 1.5.0. My best recommendation is to power the unit with a USB power supply and do the OTA update with it that way.

I still cannot recommend using Start / Stop as more than an experiment, that does not change with firmware 1.5.0 alone. The developers have been working on a solution for some time now, and so far there has always been some problem with one situation or another. I have been testing a new version of the app with most of the Start / Stop problems fixed, but a small number of problems still remain. I cannot promise when I can recommend using Start / Stop as your daily driver. I do think that the remaining problems can be solved. But each problem requires a unique solution. Remember, no one has ever done this before.

LeRoy
[Android Auto General] tallleroy:
Hi istrait,

The first thing you should do with firmware 1.4.0 is use the app to change the Setting for USB mode to 'Default'. That will almost always solve problems where the LED is Blinking Blue.

Some background on the new 'Default' USB mode.

LeRoy
[Android Auto General] istrait:
You probably won't believe this. The one thing I didn't do was remove the phone and aa wireless from the smartphone projection settings in Uconnect. Did that while I was trying to get hooked up and all of a sudden it worked. No idea why but that fixed it.
[Android Auto General] skamin:
Thanks very much for your quick reply, LeRoy - much appreciated.

I've of course tried powering the unit with a USB power supply, but OTA updates fail nonetheless. Not sure I understand if this is a problem that plagues a certain batch of devices, or whether it is related to my phone (Samsung Galaxy S21), but I absolutely MUST get releases for direct PC updates, or my device will become obsolete (or at least will remain with its current 1.4.0). I do hope all releases can be made available in this way, or some other solution to my OTA problem will be made available. Please relay this message to the developers. Thanks!