yashsingh1/xdaforums huggingface dataset:
[Android Auto General] Snirpo:
Can you share your device name? I can't find you by name in our database. It's an oddball situation, might be some specific hardware revision which has this issue.
[Android Auto General] Snirpo:
Can you share your device name? (AAWireless-xxxxx)?

I checked three devices with this issue and they all seem to be batch 2 devices (aka the batch from hell). I'll try to reproduce what's happening, although it's a bit tricky because it could be happening on only a small amount of boards from a specific batch of SoC's.
[Android Auto General] bjevers:
This is happening on my device also on 1.7. I "think" I'm from the first batch. AAWireless-BXWYmJU2
[Android Auto General] dzeidzei:
name ends with b05JW0kL. Not sure about the batch, contribution id was 4678.
[Android Auto General] osm0sis:
AAWireless-2WuK74t7 here. #7004. Thanks for your efforts and looking into it!
[Android Auto General] Snirpo:
Boot limit is set to 5 failed boots before reverting to the previous version, so I think you experienced this. I'm glad we built in this failsafe... Didn't think we ever needed it... Thanks for the info guys!
[Android Auto General] vetol:
Problem is inside device or only with USB cable? In other car this AAWireless is working and I did try 3-4 for cables in my car and it's the same. If problem is with the cable, tell me what cable to buy and I will buy it as soon as possible. :)
[Android Auto General] janz25:
I did the firmware update back to 1.5 today morning and my AAW worked as usual before the 1.7 upgrade.

@Snirpo mine is from second batch, i didnt send any log but my device id is AAWireless-NOTJiaqt, not sure if this could help.
[Android Auto General] psylentknight22:
I have been having issues with my AAW device constantly connecting and disconnecting. It will connect for usually a few minutes at a time and then disconnect and reconnect again. It continues to do this the entire time i'm in the vehicle. I've been emailing AAW back and forth but nothing is seemingly fixing the issue. Has anybody else had these issues?
[Android Auto General] speedyg0nz:
Which car/headunit model?
[Android Auto General] psylentknight22:
20 Jeep Gladiator Uconnect
[Android Auto General] [Jaco69]:
I wrote this just some post before, try it and confirm if it solves the problem for you, for me no more reboots
[Android Auto General] psylentknight22:
Ok...I will give this a try... Are there anymore settings changes I should check?
[Android Auto General] psylentknight22:
No luck... Still continues to do the same thing... I'm really at a loss... Seems like nothing I've done has fixed the issue but a few things that I've been told to change have made it worse at times and makes it disconnect more frequent
[Android Auto General] Snirpo:
@osm0sis @janz25 @dzeidzei

I put your devices on a version which might fix the boot (no led) issues for 1.7.0+. You can update to this version via the OTA screen. Could you check if this fixes it? I can't reproduce it, so it's a bit hard to verify myself :)

Thanks!
[Android Auto General] IlD4nX:
Ok, revert back to 1.5 and it works flawlessly again. Only odd thing is related to connection method: before was set to default and working... Now I had to set it to direct to make it work!

BTW still my best purchase in the last year (early baker!
[Android Auto General] osm0sis:
Thanks! Sent you a few sets of logs.

One where I thought it seemed working after the update.

One with Start/stop enabled and it got stuck in blinking green when the car was started from fully off (Elantra 2018 has 3min of USB power once turned off). Solid white standby mode seemed to work really well, so it's a shame the cold start stuff isn't working.

And one with Start/stop off again, after car start fully off, and no LED light showing so I had to unplug and replug twice again to get it to boot. So, the problem is still present it seems. 😕

Edit: Did another cold start and it worked this time?! Seems more intermittent now, at least.. sending a 4th set of logs for comparison. 🤔
[Android Auto General] bjevers:
When mine doesn't automatically connect (which seems to be over 50% of the time), I just go into my phone's Bluetooth settings and click on the AAWireless device listed there and it connects right away.
[Android Auto General] osm0sis:
No LED is the big problem here, then it connecting 0% of the time for me from a cold start with Start/Stop is another problem.
[Android Auto General] hand-filer:
Running 1.7.0 on SYNC 3 for 2 days now. No issues so far.
[Android Auto General] Snirpo:
In regards to the start / stop issues, please try the internal beta app: https://appdistribution.firebase.dev/i/5196d378c8e122d7

In regards to the "no led" issues. I'm trying to reproduce it, there's nothing in the logging, all seems fine. So it probably fails very early on boot. You can also join us in Slack for some more direct communication:

Join my Slack workspace! https://join.slack.com/t/aawireless/shared_invite/zt-nu6jokgj-Y~FxA6aegEZMi98aISYEjA
[Android Auto General] bjevers:
I have been using the internal beta app. I have seen a message on my phone saying it cannot connect to the AAWireless Wifi. That's when I figured out I could just go to the Bluetooth settings on my phone and select the AAWireless Bluetooth device there and it would connect right away instead of unplugging/plugging back in hoping it would work. Maybe a timing issue with getting the password sent for the Wifi?
[Android Auto General] Snirpo:
I'll check the logs, but first need to fix these no-led issues :)

Might have figured it out, was able to reproduce by re-plugging the device 100+ times. @osm0sis (and others) can you update to the latest "boot-fix" version to check if this helps for you?
[Android Auto General] osm0sis:
Latest boot-fix version seems to work much more consistently again from a cold start. Oddly got stuck on flashing green on 1/4 attempts. And on my 5th attempt I got the "no LED" issue again, with a quick unplug/replug getting it booting. 😔

The beta app seems a bit more convoluted with regards to bug report submissions, and appears to attempt downloading the logs twice simultaneously, with one usually failing, then the AAW Config app may or may not register the successful one for submission.

Edit: The beta app does resolve the Start/Stop issues that I was seeing, entering/exiting from standby (white) flawlessly, and cold starting much more consistently without issue.

Edit 2: I've also just discovered unlocking/locking my Elantra 2018 provides another 3min of USB power, so I bet it's some kind of timing issue with the AAW unit booting up early/partially/frequently with no connectivity and weird power conditions (since it always boots fine to green with the charger-only port, even when it would stay black when replugged in the AA port on 1.7+). The new-and-improved Start/Stop might actually be a viable workaround for the "no LED" issue until you can figure out the regression from 1.5.0 to 1.7+.

Edit 3: Spoke too soon, managed to trigger "no LED" with a cold start with Start/Stop enabled, and a quick unplug/replug getting it booting back into standby, but then it was so late it didn't register the car was started and car BT was already connected so it remained in standby (tapping the AAW device in the BT list got it moving). 😑
[Android Auto General] Snirpo:
I'm honestly a bit confused, bassicly reverted all changes to the kernel / boot script now.

Need a bit of a sanity check, putting your device back on 1.5.0 right now. Can you double check if the issues are gone on 1.5.0?
[Android Auto General] osm0sis:
Turned Start/Stop off again, downgraded to 1.5.0. Just cold booted 8 times (with that 3min USB power wait in between, remember... 😅), and on only the 6th time out of 8 I had the flashing green issue and just disconnected and reconnected the AAW BT device on my phone to fix. Zero "no LED" cold boot problems whatsoever on 1.5.0 that I can tell. All seems pretty consistent again. 🤷‍♂️

One other thing I notice is that when the 3 minutes of USB power with the car off is up the device briefly flashes green, sometimes making it to blue again before turning off. Makes me wonder about timing issues and incomplete boot issues as I mentioned in Edit 2 of my last post. Perhaps 1.7.0+ just can't tolerate weird USB power mode/no connectivity reboots anymore?
[Android Auto General] Snirpo:
Does anyone in the EU has a device with these "no LED" issues occurring often (on 1.7.0)? We can exchange it for a new device.
[Android Auto General] IlD4nX:
On 1.7 mine always doesn't start... It's a first batch 9KzFD2sS. Do you believe I have to change it? (Italy)

On 1.5 is perfect!
[Android Auto General] Snirpo:
You mean it doesn't start the first time, or not at all anymore?
[Android Auto General] IlD4nX:
I mean that one's updated to 1.7 it start the first time and then I have to unplug the cable from aawireless wait some minutes and the plug in it again to make it works every time. For some reason I don't really understand, if unplug the cable from the car only, it doesn't work at all.
[Android Auto General] Snirpo:
We 99% percent sure found the issue now. I put your devices on a 1.7-hotfix version.
[Android Auto General] osm0sis:
Not seeing the OTA here.
[Android Auto General] kingpong:
I'm running into the same issue with 1.7. often now when I start the car it does not connect until I unplug aawireless and plug it back in. around the same time I updated to 1.7, my wife paired her phone with my car and I thought that was the issue. but after removing her device, it still happens. I checked today when it happened and noticed the LEDs did not light up similar to what others have reported.

any chance I can try the hot fix as well?

Ww94Dlf0
[Android Auto General] IlD4nX:
Tomorrow I will try it!
[Android Auto General] osm0sis:
Got it now! Midnight here so will also try tomorrow. 👍🤞
[Android Auto General] dallasnights:
How do I get 1.70 it shows 1.50 is the latest on my app thanks all
[Android Auto General] osm0sis:
Rollout was stopped until failed boot issues are fixed.

I'm testing the fix right now actually, seems so far so good! Trying out Start/Stop again next for extra levels of difficulty. 🤠🤞

Edit: @Snirpo honestly all seems pretty solid again now! The new Start/Stop in 1.7.x and the internal beta app seems very consistent now as well! Great work! Ship it all! 🎉🤘

Only (apparently cosmetic) thing I notice is that sometimes with Start/Stop my phone will make a toast message "Incorrect password" presumably for WiFi, but otherwise all appears to work flawlessly now.
[Android Auto General] bjevers:
1.7 hotfix seems to have fixed the no LED issue for me. I still get what you did above about invalid password and have to connect by choosing the AAWireless Bluetooth connection. Happens more often than not, so start/stop isn't really working well for me. My vehicle is a 2020 Ram 1500 with UConnect system.
[Android Auto General] osm0sis:
Weirdly Start/Stop still works fine for me even when that password error toast is displayed.
[Android Auto General] Snirpo:
I'm glad the no led is issue is fixed now :) This was a nasty issue. I'll give out testers a day or two to double check if it's completely solved, so I'll probably release 1.7.1 on Tuesday.

Sadly we shipped 10k devices with 1.7 now, so will have to immediately push 1.7.1 to those devices. Not going to be much fun support wise I'm afraid :(
[Android Auto General] osm0sis:
I see another hotfix build rolled out to me this morning, need it tested again, or anything to be aware of with it?

Edit: Well I tried it anyway, and still seems good in my casual use today running errands. 👌
[Android Auto General] Patrick3000:
My device is still on FW 1.5, but I can report that the internal beta build of the App SW appears to finally have Start/Stop functionality working perfectly for me (Hyundai Kona Electric with Samsung Galaxy S10).

However, when I upgraded the app to the beta build it initially behaved as if Start/Stop functionality was disabled even though it was still set in the settings. To fix it, I had to disable and then re-enable Start/Stop in the app, which prompted the app to request screen overlay permissions. This then put it into a state where the device was perpetually showing solid white LED and would not connect to the car.

Finally, after de-selecting and re-selecting my car's Bluetooth connection in the Start/Stop menu a few times I got it to work. It has now been working reliably for a couple of days.

So, I thought I would report my experience just in case this helps make the rollout of the new app sw a bit smoother for everyone else.
[Android Auto General] SOFO888:
Hey guys,

I have an idea for the 2 phones topic.

In my car the car chooses the phone to connect to the Bluetooth system by choosing the corresponding driver. That means if I choose my name, everything in the car gets set up for me and my phone gets connected to the Bluetooth system.

As soon as I choose another driver, the car sets up everything for the other driver, disconnects my phone and connects the other driver's phone through Bluetooth.

My idea is to use the app Tasker. We could make a profile which runs the following task a soon as the phone does not connect to the car system's Bluetooth while getting AAWireless connection through WiFi:

Turn Bluetooth off and turn WiFi off. After 2 minutes, the task turns on Bluetooth and WiFi again. During this period it is possible for the first phone to get connected to AAWireless.

If both phones have this profile, the phone that gets connected to the car's Bluetooth system should connect to AAWireless while the other phone turns off connectivity for 2 minutes.

What do you think about this idea?

I did not receive my AAWireless yet. Perhaps someone could test this for us.
[Android Auto General] janz25:
I also received another hotfix build pushed to my unit, downloaded and installed, so far so good, no more issue with dead system. I dont use start/stop function since my car usb will auto off after engine off.

My issue all along on v1.5 are random disconection after around 30mts of drive and spotify/music stuttering after around 20-30mts drive.

Hope this build solved those issue. Will report if encounter anything else.

Thanks for the fix @Snirpo
[Android Auto General] RealNBB:
Hi,

are you going to release 1.7.1 this day? Because i have same problems with 1.7 like the others here. Would be great! :) Thank you!
[Android Auto General] Snirpo:
1.7.1 has just been released :)
[Android Auto General] maisonmdsgreen:
What new?
[Android Auto General] [Jaco69]:
Maybe bug fixing?
[Android Auto General] Snirpo:
Correct:

aawireless-issues/FIRMWARE-CHANGELOG.md at master · cpebit/aawireless-issues

Contribute to cpebit/aawireless-issues development by creating an account on GitHub.

github.com
[Android Auto General] osm0sis:
Nice! Can you put me back on the stable track? Thanks for all your work! Also, what was the issue in the end?
[Android Auto General] Snirpo:
Done. It was some wonkyness in the boot script. There was some device tree fixup stuff in there, which oddly has been there from the beginning, but suddenly became a problem after some refactoring...

I'm not 100 percent sure why this became a problem now, but removed it, because we don't need it anyway. It was a leftover from the original Rock Pi S boot script.
[Android Auto General] mc01319:
Great update,

With version 1.5 and 1.7 with beta AAConfig I had random disconnects from my CAR screen.

With 1.7.1 no disconnect so far.

Thank you !
[Android Auto General] 1qazwsx4:
Latest update has not fixed the calling issues with Xiaomi. When streaming music via Bluetooth, if you take a call then end it, the music is routed through phone speakers instead of Bluetooth but the phone/AA is still connected via Bluetooth. Have to remove AA wireless from USB to regain music through cars speakers... Anyone else facing this issue? Tried running AA wireless using passthrough with same results.

Edit: version 1.3-1.4 I didn't have the above issue.
[Android Auto General] valeri_s_k:
Did you update the rom in the meantime?

As per my experiance, there are some issues with MIUI, not related to AAW device/firmware. I have also tested AA on another car with factory equiped wireless unit and MIUI behavior is the same.

I had the problem you described above with MIUI 12.5 on Mi 11 - could not find solution, that's why unlocked bootloader and flashed xiaomi.eu rom. Tested both - stable and weekly MIUI 12.5 - always the same.

For me this issue was solved with MIUI 12.6 weekly release, but then another one appeared - MIUI somehow shortly disconnects/reconnects wifi when mobile data is lost. Not found a sollution yet too.

I can live with it for now - it is OK for short everyday trips where mobile data coverage is good. For long trips I use wired connection that works just fine.

Xiaomi.eu announced that A12 rom will be released soon and hope it will work ok.
[Android Auto General] 1qazwsx4:
I appreciate your response. I've always used miui eu roms and the 12.04 roms worked fine and I had no issues but as soon as my AA wireless updated to 1.5 firmware thats when my issues started. I reformatted and updated to miui eu 12.5 also and the problem persists but I'm unable to downgrade my AA wireless to firmware 1.3/1.4 so I can confirm that miui isn't the sole problem. Any other aftermarket AOSP ROM etc ALL have issues with AA/other problems so changing to them isn't an option...

Also MIUI 12.5 seems to have a bug that turns wifi off when you go out of range and can't be disabled lol

To clarify to those curious:

Play music via Bluetooth and wirelessly casting android auto = working great. Recieve a call during this = working great. Hang up at the end of the call = music is now streamed through car speakers instead of the cars, Bluetooth connection is still saying connected (can still make calls too but any audio is routed through phones speakers instead of the cars) and android auto remains connected.
[Android Auto General] valeri_s_k:
Yes, for me that was exactly the issue with MIUI 12.5, no diference in global/EEA or xiaomi.eu, stable or weekly.

The wifi disconnect/reconnect issue appeared to me with 12.6.

I am quite sure both are MIUI issues because I've tested it with factory fitted Android auto wireless head unit on 2021 Skoda Karoq (no AAW device used, phone connected directly to HU wifi) and issues are completely the same.

Can't say anyting about MIUI 12.4 and earlier as first MIUI version for Mi11(venus) is 12.5

IMO, there is a small chance that these issues are caused by AAW device firmware. Anyway it worths to try, if Snirpo can downgrade your device to 1.3 and I would appreciate your feedback.
[Android Auto General] 1qazwsx4:
I do agree that its likely to be miui causes but my device was working normally until I updated AA wireless while running my previous miui ROM.

I would be more than happy to downgrade my device to 1.3 to verify if this fixes my issues while running miui 12.5 and have requested to be able to downgrade for some time but my messages haven't been seen.

Will definitely update my results once I find out - the current 1.7 update does work well for me other than the BT issue@Snirpo please make it possible to downgrade/offer a guide on how - AAWireless-eSs19MUQ
[Android Auto General] Snirpo:
Done, you can updowngrade to 1.3 now :) I'm sorry I haven't seen your messages. I don't always read all messages here.
[Android Auto General] 1qazwsx4:
No worries mate, wouldn't expect that as there's far too much to read haha thanks I appreciate that. 1.3 worked fine with the previous MIUi eu ROM so I will check to see if it works with miui eu 12.5 ROM and report back tonight
[Android Auto General] DanJKroll:
Like others here, my unit started acting wonky after the 1.7 update. I see the 1.7.1 OTA update, but it is requiring me to connect to Android Auto to install it... and I have not been able to connect since the 1.7 update. I've followed all of the steps to delete the various caches and connections, but nothing gets me connected. Any suggestions on how to do the update so I can get back to normal? I appreciate your help.
[Android Auto General] osm0sis:
Connecting to a power-only USB port always got the "no LED" state booting for me, even when it wouldn't at all in the car's Android Auto USB port. Then I could firmware update.
[Android Auto General] irv67440:
My aaw is running ver 1.5 on a samsung note 10+ on a 2021 mbux.

Lately i notice that whilei am using the phone the aaw reboots every 5 or 8 minutes.

It used to that it would reboor when not on the phone and i read that should click an audio setting in aa developer and that helped.

Is there a setting i can check to resolve the reboot on the phone.

Thanks
[Android Auto General] SOFO888:
@Snirpo

See my post 1654

Post in thread 'AAWireless - General discussion and support' https://xdaforums.com/t/aawireless-general-discussion-and-support.4247677/post-85729859

Would this be worth testing?
[Android Auto General] 1qazwsx4:
Abit of an update on my findings

Hi @Snirpo, I downgraded my AA wireless device to test my issues with after call disconnected all audio routed through phone speakers instead of car speakers. After multiple tests using MIUI eu 12.5 I can report that even with 1.3 firmware on AA wireless, the issue still happens. HOWEVER, when streaming using Bluetooth (not using android auto/AA wireless) after ending a call the audio remains normal and music streaming works as it should. I guess that's why I assumed everything worked as normal on firmware 1.3... either way it's still an issue that I can't pin down - can any other Xiaomi users confirm they are having this issue?

Thanks for allowing me to downgrade and test - can you please enable me to update to the latest OTA again :)
[Android Auto General] Limpperi:
After 1.7.1 update just now im not able to establish a data connection at all. Could i have a rollback to 1.5?

EDIT: fixed. This can be deleted. I just had to forget the wifi once

Oneplus 7 pro android 10
[Android Auto General] tpagel:
Hi... What is the expected behavior when I press the reset button on the device? I tried holding it for 10 seconds but the device still was in the green-blinking mode... Why did I try to reset it? I had some issues connecting to my Mazda MX30 (worked fine for months but it stopped working), I thought it might be an issue with the device but at the end it turned out that deleting all information from my car (Bluetooth connection from AAWireless and my Phone plus removing my phone from the car's setting) and then reconnecting via the app worked... Or is there no reaction from the reset operation on the device and resetting it did the trick already?
[Android Auto General] LaKriz83:
I received my unit this week and am struggeling with building up a connection with my Skoda Superb and my Pixel 5. I get a stable connection (LED on AAW is blue) and my car display shows AAW as available device. When I touch Android Auto on the screen then, it is trying to connect but then it says "Connection failed" --> LED on AAW remains blue --> Trying again by touching Android Auto --> "Connection failed" --> AAW is rebooting

Once I had Android Auto on the screen, but only for seconds. Then it says "Connection failed" again and my smartphone says "Communication with 48:FO:7B:B5:17:52 not possible"

My Setup is the following:

Car: Skoda Superb III, 2017, HU Software Version MST2_EU_SK_ZR_P0363T (0363) (mybe this helps?)

Smartphone: Pixel 5, Android 12 beta (

AAW Config: USB Mode: Direct, nothing else. With this I get a stable blue LED (Passthrough did not work). Newest OTA on AAW. Followed the FAQ by setting up everything (cleared cache and storage of AA and Google Play Services, Enabled Wireless Projection and Video focus in developer settings, manually connected via Bluetooth)

I tried different cables: The supplied one, an Anker USB 3.0 and an original one from Motorola

I have no more ideas. Do you have any, which can help me?

Thanks a lot.
[Android Auto General] canadoc01:
How do I know which batch I have?

My main issue is that I have it freeze on the same parts of the highway likely due to radio interference. Was hoping and told they were working in a fix.

Does 1.7.1 fix this? Do I need to foil tape this?...