yashsingh1/xdaforums huggingface dataset:
[Android Auto General] Snirpo:
You don't need a password. The reason this is probably happening is because we changed the password in 3.0. Please clear cache and data of AA and it will most likely start working again. If not, delete the wifi network from wifi settings (if there is any). DO NOT manually set the password. It's not nessecary and will not help in any way. AA should set it up for you.

Is this problem happening on the Note 8?
[Android Auto General] mc01319:
Today I managed to get it work with Nissan Qashqai 2019. The phone is Samsung Galaxy S20 Plus Snapdragon. I had MTP with retry enabled and disabled the Passthrough. I had also enabled the Auto Video Focus at both the Developers options of Android Auto and at the config app of AA Wireless. But, after I removed the USB cable to retry, then I couldn't do it again. I will retry tomorrow and give update. I am quite optimistic that eventually it will work. 🙂
[Android Auto General] SimonDavid:
Hi, we are enjoying aawireless a lot on a Citroen C4 Picasso 2016. We had one random reboot of the head unit but nothing like that in the last few weeks.

The only consistent issue: When music (tidal) is playing and maps does voice guidance or beeps the music stutters significantly for a few seconds. Every time. Phone is a Pixel 5. Tidal + maps has been used without issues for months with wired AA.

I tried passthrough and the audio timestamp setting but that doesn't seem to change anything.

Any other ideas?
[Android Auto General] Nudnik_de:
I can confirm that I also have the VW headunit issue. Now using a different USB cable and the issue happens less frequently.

Software: 0468

Hardware: H41

Device: 5C0035680G
[Android Auto General] Snirpo:
I can't find your name in our database, but if you give me your device name I can check if you have a Technisat unit, most probably you do.
[Android Auto General] Snirpo:
If you have a second batch device (came with 1.1.0), please update to 1.2.3.
[Android Auto General] SimonDavid:
Thank you for the swift reply. No, #3027, so I've had it for a few weeks.
[Android Auto General] Marshy33:
I've done some more testing with 475 today. And unfortunately I have had my first reboot, but it is still far far more stable than the earlier firmware I was on 253 which would have issues within the first 10 mins.

Also I'm not sure if it's AAwirelss 1.2.0 or my upgrade to 475, which has meant when I do get a headunit reboot it automatically reconnects back to android auto. Previously I had to pull the usb and replug which just made using AAwireless a pain, so much I stopped using it for a while.

So currently I can say with 475 I have had one reboot in the 2 days since I have it installed (this has been me trying to force a reboot and stress testing, by using Waze and spamming fast forward in Spotify etc), and when it did it all connected back up straight away after the headunit had booted, so just a minor annoyance.

How often does yours reboot? Is there any pattern to it, or do you have a way of recreating it?
[Android Auto General] Nudnik_de:
Had it multiple times a day, allways when changing Song in Spotify. Bought a new cable last week, the one that s.o. linked some pages before. #444

Since then only one reboot per day, none today.

Can't force the issue but I remember from last week that it occured more frequently with Spotify in fullscreen mode, when running in the background it happened less.

It always reconnected automatically, sometimed need to confirm to connect Android Auto on the MIB...
[Android Auto General] Marshy33:
That sounds very promising. I could happily live with the odd reboot every now and again. Think I'll get one if those cables too then.

Let me know if it stays good like it is now or gets worse. There are a couple of updates for your headunit, but I wouldn't suggest updating unless theres a real need.
[Android Auto General] Nudnik_de:
Its this one:

Amazon Basics, USB-Kabel mit doppelter Nylon-Schirmung, Typ C auf Typ A, USB 3.1 Gen 2 , unterstützt hohe Datenübertragungsraten bis zu 10 Gbit/s, 0,3 Meter, Dunkelgrau: Amazon.de: Computer & Zubehör

Amazon Basics, USB-Kabel mit doppelter Nylon-Schirmung, Typ C auf Typ A, USB 3.1 Gen 2 (USB-IF-zertifiziert), unterstützt hohe Datenübertragungsraten bis zu 10 Gbit/s, 0,3 Meter, Dunkelgrau - Kostenloser Versand ab 29€. Jetzt bei Amazon.de bestellen!

www.amazon.de

I will report if it is staying good...
[Android Auto General] seseattle:
Just flashed the 1.2.3 OTA on my 2nd batch device. No issue flashing (I had already done the manual flash via PC though) but then it wouldn't connect again with only the green led flashing. I'm using a Samsung S21 in a Ram 1500 with the 12" Uconnect.

I followed all steps in the FAQ for the green flashing and it then connected but only flashed blue with no AA on the head unit. I then removed the entry from the Uconnect screen mirroring list and plugged my phone into the USB cable so it could handshake with the head unit and finish setting up AA on the phone. Then I plugged the AAW device back in and everything connected quickly and works as advertised.

For some reason (maybe just on Uconnect head units?) I've twice now had to plug the phone in via cable after using app setup before AAW would work. Missing step that may help others?
[Android Auto General] FrankieG64:
I had the same issue with the 12" Uconnect in a 2020 1500 after flashing the unit and again after the update to 1.2.3. Each time I had to remove aawireless from the screen mirroring section of Uconnect and then it worked. Hopefully it continues.
[Android Auto General] dablessing:
I cannot get mine to update to 1.2.3. I’m a second batch ID. I updated the DRAM this morning for the 2nd time. My device just reboots after starting the OTA. Everytime this happens. I even pulled out of the car and onto a usb outlet and same result.
[Android Auto General] MariS9Maz:
I updated to 1.2.3 this afternoon from a wall charger. I'm looking forward to trying it out on our next trip in the car.
[Android Auto General] dablessing:
I tried the below steps from the Indiegogo comments and this allowed me to update to 1.2.3.

Please follow these steps:

Delete wifi + bluetooth AAWireless-* devices.

Reset cache + data from Android Auto and the Google Play services

Reset the AAWireless device by holding the reset button (in the pinhole) for 5 seconds, the unit should shut down, restart and go blinking green after about 10 seconds.

Reboot the phone

Manually pair to the device via bluetooth settings on the phone (without the AAWireless Config app).
[Android Auto General] charlie234:
Hello. I haven't been able to get aa wireless to work yet at all. I'm part of the second batch of aa wireless. Driving a mazda cx5 (2016.5 gt) and using an android 10 samsung s9 plus.

I've done the DRAM patch via Windows 10 with no issues, and just updated from 1.1.0 to 1.2.3 via OTA.

I've disabled blokada. Cleared storage/cache for both the AAwiteless companion app and the Android Auto. I've tried two different cables, the latter being an anker cable that has worked with AA hardwired.

Right now it flashes green and then eventually starts flashing blue. Always says android auto connected under one notification and the n second notification says searching for android auto. This all eventually crashes and starts over again for an infinite loop. I've tried MTP, direct, passthrough, 2.4ghz wifi....

I'm out of ideas, nothing ever loads and just cycles. Please help!!
[Android Auto General] Genebaby:
I'll have a look at both my headunits when I get home.
[Android Auto General] vizzze:
Device: 3Q0035846A

Hardware: H30

Software: 0359

I do have occasionally stuttering audio, frequently reboot of the headunit (on average every 5-6 songs, or earlier if i skip tracks).

I also had an episode where any notification (whatsapp or other app) caused a reboot when it was stopping the played music.

For now with the original cable in the box, will try later with a new cable.

Where do you find the VW headunit firmware files to upgrade?
[Android Auto General] Marshy33:
Its good to see someone with 3xx software. So far I'm seeing 2xx is very unstable, 4xx whilst not perfect seems best overall. But still too early to give a final verdict.

Unfortunately you cannot got from 2xx to 4xx or in your case 359 to 4xx without "hacking" your unit. All official updates should be start with the same number.

If you can hold down menu for 3-5 second it should bring up a service menu. If you then click on system update and then version. If you let me know what the installed SW train version is, we can see if there is an official update.

Does your headunit have navigation?
[Android Auto General] Snirpo:
Hmyeah we can do that as well. Then someone still has a window of 3 minutes to pair to the device though. Most cars only leave their USB port powered for 5 minutes after shutdown, so not sure if that would help that much. We probably also need to change the LED color to show if it's pairable or not.
[Android Auto General] Snirpo:
3.0 will be available from next week for everyone. The firmware itself isn't beta btw. Only the CarPlay functionality is.
[Android Auto General] Hirokiaaa:
I'll ask a question on slack. thank you.
[Android Auto General] mike.s:
Sure, but as you said "Right now it will always be possible to pair when no device is connected." I assume the inverse is true - when connected, you can't pair another phone. And, the GP's concern was based on "since my car does not turn USB off and everyone would be able to connect to my AAwireless at any time..." So, that presents a lot of opportunity.

Simply limiting it to a few minutes after power up, and before a paired phone is connected (which can shorten the window even further), greatly reduces the potential for bad actors to connect. And the opportunity would only exist after the owner took action to turn their car on, so would be likely to be noticed.

I'm not sure, though, what the real problem is. If the car is off but the USB powered, and someone connects - what can they do? It's not like they can blow the stereo speakers, that's still off. I guess it could be part of a denial of service, pair enough phones and the owner's would be fogotten, so they'd have to re-pair. Or maybe someone's driving down the highway with no phone connected, and someone in the next lane connects and starts playing Lawrence Welk with pornographic album art.
[Android Auto General] NachoB:
Vehicle: 2020 Lincoln Aviator. CarPlay up and running in under 2 minutes.

Thanks AAW team!
[Android Auto General] Snirpo:
When connected, you can't pair phones indeed. Most cars don't keep their USB port powered after shutdown, or only for a short while. There are only a few cars which keep their USB port powered for longer. Mainly pickup trucks.

So we decided to keep it simple. There's not so much you can do except for being annoying. Changing settings and / or starting up AA / CP. In the 2.5 years of AAWireless it has always been like this. And no one has really complained about it. But I do agree it might not be the most "secure" way.

I'm OK with changing the logic, but it can potentially create a storm of "I cannot pair my phone". So we need some way to make it obvious the device is pairable. Or make the functionality / timeout optional.
[Android Auto General] piri1312:
Yes on Samsung Note 8, now everything works again. Thank you.
[Android Auto General] italodance:
@Snirpo I moved to iOS, please advise me how to test beta of CarPlay. I still have my android phone and your app with me.
[Android Auto General] mmulvey01:
I've had AAW for 2 years or so. It worked perfectly until recently.

About a month ago, both AA and AAW had upgrades. Ever since then, EVERY time I start the car or if AAW crashes, it throws up multiple confirmation screens as if the car/dongle/phone have never seen each other before.

There have been a couple more updates since and each time, I hope the bug will be fixed, but it persists.

At other times, the car display screen goes solid black. It still shows the reverse camera image, so I assume the issue is in the AA interface. It stays black although music continues to play until the car is turned off, left for a while then re-started.

Anyone else having this problem and/or found a fix?

Ford Fusion 2019 Sync 3 - all updates are current.

Samsung g20 Note Ultra - fully up to date

AAW and AA with current updates.
[Android Auto General] Snirpo:
You can update through the app.

What's the name of your device?
[Android Auto General] mmulvey01:
Sorry - The name of which device? The AAW dongle?
[Android Auto General] J_E_F_F:
is that part of the 3.0 firmware update for the 2nd gen 317 devices?
[Android Auto General] hand-filer:
Ford SYNC 3 here. Lately I'm getting a "this USB device is not supported" message on the screen. I have to clear the message to get AAWireless to connect. This might have started after a recent SYNC update but not 100% certain. Either way it's pita. After 1 year of use the convenience of AAWireless isn't all that convenient any more.
[Android Auto General] Snirpo:
AndroidAutoAAW-xxxx or AAWIreless-xxxx
[Android Auto General] Snirpo:
Not yet, it's now still in dev. I can enable the dev firmware for you though.

Weird, what's the name of your device, so I can check what changed?
[Android Auto General] italodance:
So Can I test Carplay when updated to 3 or you must add the name of device first ?
[Android Auto General] Snirpo:
Firmware 3.0 has CarPlay support.
[Android Auto General] PPaniX:
Hi

I can't get carplay to connect to the car, firmware 3.0.0 installed, carplay setup completed. But the device keeps blinking green

Bluetooth says connected. but, nothing is showing up.

AA connects without any problems, GM fix enabled

Car is a Mazda 6 2018
[Android Auto General] Dangze:
Hello,

this morning I have a big issue with my dongle (AAWireless-aRiOUP0S) !

Yesterday I received the 3.0.0 firmware and I installed it, without making any test. When I start my car this morning, the dongle kept blinking green and didn't connect, so I connected my phone with cable to get AAndroid Auto working...

After returning home, I noticed that the app (3.30.0) could not connect to the dongle, whatever I do, and even if I connect the dongle to an USB charger, the dongle keep blinking green and cannot connect to the phone app. Resetting the dongle by pushing the reset switch does nothing !

What can I do, please help me !

Edit : the name of the dongle has suddenly changed : AAWa1766d0e
[Android Auto General] martynas:
HI, I have old AA wirelles version and using it on Mercedes W213. All is nice, except that Android auto does not use full screen, as mercedes did not allow it. But Carplay can use full screen. Tried buying dongle with Android Auto via Carplay, and it used full screen, but quality was low. So returned it.

If I buy gen 2 AA wireless dongle, can I use Android Auto via Carplay full screen and will it have same quality as non full screen Android Auto? When this option should move from beta to stable?
[Android Auto General] Snirpo:
Your device has been reset today at 15:01. Please unpair and re-pair your device. Afterwards reset cache and data of AA.
[Android Auto General] Dangze:
Everything seems OK now, I will tell you if any problem in the coming days...

By the way, the dongle mode is activated by default, is this normal ? Can/must I change this setting, or is this not necessary ?

Anyway, many thanks as I thought I will have to purchase another device !...
[Android Auto General] italodance:
@Snirpo

Thank you mate٫ updated to V3 and CarPlay works so good.

The connection time was about 10 to 15 sec.

Quality of music and phone is great.

There is no specific lag on map, Waze..search…

The only issue was a lag for playing first music , the rest of playlist was normal, hope to see it fixed in the next updates.
[Android Auto General] knoxjon:
@Snirpo Is there any way I could get the newest updates for AA over Carplay?

App Version: 3.29.0

Firmware: 3.0.0

Hardware revision: Gen2

Serial number: AAWfcd159dc

Car: 2021 Subaru Outback
[Android Auto General] Snirpo:
It works, and is quite smooth on the develop firmware atm. However, it's still beta and will probably stay like that for a few weeks / months. Right now the biggest thing missing is support for phonecalls. On some cars (Subaru for example) bluetooth handsfree stays enabled when using CarPlay, then phonecalls will work right now already. Other cars shut down Bluetooth handsfree when using CarPlay. Android Auto by default uses bluetooth for phone calls. So we need to proxy bluetooth handsfree to CarPlay. This is quite some work and not quite trivial, because it's realtime, so you don't want to introduce too much delay.
[Android Auto General] Saynttv:
I am having the same issue as Dangze with mine (AAWireless-cMSznINo)
[Android Auto General] asasanc:
@Snirpo Hi, I have a gen2 device and updated to v3.0 firmware. My android auto works fine no issue. I paired my iphone for apple carplay it pairs up shows apple carplay initial screen on the headunit and then nothing comes up on the screen. I tried multiple times but no luck. Aawireless has green light blinking all the time even after pairing with iphone. Bluetooth stays connected on iphone. Tried two different iphones none of them is working and its same with both.

Tried enabling AA using carplay and even AA doesnt work shows apple carplay icon on headunit and when i click on that it says connected device doesnt support apple carplay please contact apple support.

Device Id: Aawireless - abx9iqVO

Car Model: Nissan Rogue 2021
[Android Auto General] martynas:
Thanks!

To check if Mercedes w213 bluetooth handsfree stays enabled when using CarPlay (without having AAwirelss gen2), is just to connect Iphone to system and see if the bluetooh stays connected? If so, it should work with AA via Carplay too?
[Android Auto General] Snirpo:
I'm not sure if that's a 100 percent reliable way to test it. I'll ask our CarPlay dev, he already worked with Mercedes.
[Android Auto General] Snirpo:
Please unpair and re-pair your device. Afterwards reset cache and data of AA.
[Android Auto General] r0x:
I have been experiencing the following behavior for some time, as soon as i get a call or call someone, AA disconnects and the call goes through the bletooth of the car HU.

It seems like an AA issue, does someone have the same behavior?
[Android Auto General] Snirpo:
Sounds more like a car-side issue. Does AA fully disconnect? Like blinking green LED?
[Android Auto General] Saynttv:
I am unable to connect via BT to the device following the 3.0 firmware update, device seems to be constantly cycling solid green, flashing green, solid green, flashing green, yellow, repeat. The device shows up in BT device list intermittently but could not be connected to before unpairing and cannot be repaired. I have attempted to do so disconnected from all other BT devices with AAW device connected to car and alternate power source outside of car. AA data and cache have been cleared a couple times, AAW app data and cache also cleared, phone restarted a couple times and attempted to reset via reset button on device. App version is 3.29.0.
[Android Auto General] gerrya:
I am experiencing exactly the same, tried connecting it to a different device etc, all the above steps
[Android Auto General] scoobie_2:
@Snirpo I updated to 3.0 this morning but AA over CP shows up in only a small portion of the screen. This is on a 2022 Subaru Outback. Is there an additional setting to change the resolution to utilize the full screen?

S/N - AAW443ee91f

Phone - Pixel 6 Pro

Vehicle - 2022 Subaru Outback
[Android Auto General] Snirpo:
Enabled the dev firmware for you. That one does fullscreen.
[Android Auto General] Snirpo:
Hmm that's not good. Seems it's bootlooping. What's the name of your device? (AAWireless-xxxx or AndroidAutoAAW-xxxx)
[Android Auto General] Saynttv:
AAWireless-cMSznINo
[Android Auto General] Snirpo:
Are you located in the EU by any chance? I would like to have your device for investigation. We can swap it for a new one.
[Android Auto General] Saynttv:
Unfortunately in the US. Detroit, Michigan.
[Android Auto General] Snirpo:
Can you contact support@aawireless.io ? Please mention this post. They will take care of a replacement + sending the old device to ons of our devs.
[Android Auto General] Saynttv:
I will do that now, I'll include a link to this post as well. Thank you for your support.
[Android Auto General] gerrya:
mine is AAWireless-ot8ZaPIX and Im located in the US.
[Android Auto General] Saynttv:
Email sent, hope to hear back tomorrow as I see the support times are EEST. 🤞

Edit: Already have a shipping label, good support.
[Android Auto General] asasanc:
@Snirpo Reposting it just incase if you missed it. Is there anything that I should do to get carplay working?
[Android Auto General] Highway 11:
Hey @Snirpo, I'm hoping to try CP over AA if the option's still available. When I enable it on 3.0 I'm getting the same screen as @scoobie_2. Just hoping to try out the developer firmware to get full screen up and running.

Device Name: AndroidAuto-AAW070e98d0

App Version: 3.29.0

Vehicle: 2020 Subaru Outback, Denso 1.0 Head Unit

Phones: Google Pixel 7, Samsung S23 Ultra

Thanks a bunch! Out of the box it was super easy to set up and runs great so I'm excited to see what everybody's been talking about.
[Android Auto General] hand-filer:
Thank you for replying, it's GCdwGIvK
[Android Auto General] italodance:
@Snirpo

After driving about 2 hours ,I got some screen freezing while using Waze on my CarPlay 😥

It was freeze on main screen of CarPlay without any touch or use as well.
[Android Auto General] Snirpo:
Nissan might not work yet. Can you push a bug report via the app?

Bug report is located at settings --> top right icon.

Please make sure the "debug mode" toggle is enabled, then reproduce the issue and afterwards push the report.
[Android Auto General] Snirpo:
Hmm, the data is a bit confusing. Have you been trying different HU software versions? I see some switching around between HU software versions.

Please set the USB mode to default. That can potentially cause issues. On Ford changing the USB mode is not nessecary.
[Android Auto General] Snirpo:
A full freeze? It didn't restart after a while? Could've been interference related. I'm not sure if we handle wifi connection loss very well on CarPlay. Will check.
[Android Auto General] IwaseKen:
@Snirpo I'm using AAWireless ver 1 (Indiegogo) and received notification about firmware 3.0 ready to update. So is it stabe firmware or just beta? I haven't joined beta testing program.
[Android Auto General] Snirpo:
Stable. Only the CarPlay part is in beta.
[Android Auto General] italodance:
Yes it restarted after couple of minutes, Music/Audio keeps playing but touch screen and menu didn’t respond till restart or I disconnect AAwireless and connect it again. (It will restart itself eventually )
[Android Auto General] asasanc:
@Snirpo, Sure I will push that bug report. Tq
[Android Auto General] mgmCube:
Hi,

I have now updated to 3.0 but I still have the same problem with my new car. Can only connect once.

My previous car was a Seat Ibiza from 2018. I used AAwireless without any problems on this car.

I now have a Toyota Corolla from 2023. The new model. But now I can only connect with AAwireless once. When I restart my car it won't work anymore.

After the restart of my car the AAwireless keeps blinking green and I need to clear cache and data from Android Auto. After that it works again. But if I power down my car and start it up again, it start blinking green and won't connect.

Do you have any idea to what I can do?

My device name is: AAWa16ee6c2

Thanks
[Android Auto General] Highway 11:
I'm having the same issue. Gonna see if there's any settings that need to be put back to default.
[Android Auto General] hand-filer:
Nope. Any HU updates have been auto installed by SYNC. However it might be a Samsung flash drive in the second port that triggered the message and not the AAWireless module. I removed the flash drive and so far so good.