yashsingh1/xdaforums huggingface dataset:
[Android Auto General] Draygon:
@Snirpo

I would also like to downgrade vom 3.1 to 3.0.

Is it possible to downgrade or is a fix planned? My AAwireless is unuseable now, sadly.

Issue description:

With 3.0 Carplay worked fine with my car (Seat Leon), but since updating to 3.1 it's constantly missing the USB connection to my dongle. My car loses the connection to the dongle and it's crashing in a loop. The car only shows "Searching for USB", like when a data storage is added.

I did not have these issues with 3.0 for months.
[Android Auto General] josefsch:
The link for firebase dev versions changed around version 3.35 - now you have to use https://appdistribution.firebase.google.com/testerapps/1:45720266093:android:e1a237ee480d807c42a664
[Android Auto General] DroidShift79:
Even with this, I always land here:

guess I need a new invitation link or something. even when I log out of firebase, I can't get to the latest builds
[Android Auto General] josefsch:
Try https://appdistribution.firebase.google.com/testerapps - for me this shows 2 apps for testing, the old "app.aawireless.staging" and the new "app.aawireless"
[Android Auto General] DroidShift79:
Thanks for you help. Unfortunately I only see app.aawireless.staging
[Android Auto General] Snirpo:
We've moved back to the the app.aawireless package, so no separate package (app icon) for staging. The main reason being we are publishing now to internal beta in Play Store as well. Then the package name needs to be the same as production. Here's the link: https://appdistribution.firebase.dev/i/21242479a3e0995d
[Android Auto General] Snirpo:
HI guys, I need some testers to verify if the long connection times have been fixed. Are there any volunteers for a test firmware?

@osm0sis @diego1810 @grac ?
[Android Auto General] Snirpo:
Dongle mode has no effect on the other settings. We don't have any official technical documentation. It's all reverse engineered. But if you want to have a look at how the protocol works, you can check https://github.com/f1xpl/aasdk for example.
[Android Auto General] osm0sis:
I'm down to clown! 🙌

AAWIf49c96b
[Android Auto General] Boosky:
Hi, was that successful?

How to get WiFi password and IP of connected device (the dashcam)?
[Android Auto General] diego1810:
yes for sure AAW544d1d2c
[Android Auto General] Draygon:
Hi @Snirpo

does it fix the permanent connection issues happening since 3.1? With my car (Seat Leon) my car had no issues with 3.0, but 3.1 is unusable.

If so please add me: AAW8ba8e292
[Android Auto General] osm0sis:
Hard to tell because the start time for the UI to launch on 3.x varied a lot for me, but so far I'm cautiously optimistic? After a few starts in a half hour while running errands I think they overall seemed faster again.
[Android Auto General] Snirpo:
It seems you are talking about CarPlay? Anyway this is unrelated because you have gen2 device.
[Android Auto General] Snirpo:
Can you send in a log? So I can verify if this issue does not occur anymore? To make the starts faster overall you can also disable dongle mode, so you're not dependent on the handsfree connection from phone to car. We are actually thinking of making dongle mode disabled by default from factory. Lately it has become a pain in the ass, and seeing all the "my dongle suddenly doesn't work anymore" reviews of the MA1 on Amazon, we're not the only one.
[Android Auto General] SOFO888:
No, it was not successful. I tried it with a IP cam I had at home. But the cam only works with Wifi with Internet available.

As the Wifi on AAWireless does not provide Internet, the cam didn't want to stay connected.

I need another cam for testing.
[Android Auto General] milanxx:
@Snirpo

After a week of testing, 2.2 is stable and has no PCD problem. It starts without a problem with the reverse gear engaged, and the radio starts playing music from the AA even with the camera on the screen. So this is how it should work.

Now we can try 3.0.

Thank you very much for your willingness

AndroidAuto-AAWd9474072
[Android Auto General] Robarg:
is there any separate source of information for the apple carplay beta testing?
[Android Auto General] bigcid10:
Aaw6189e073

I would love to test the firmware as well

Thank you

Edit:

One more thing ever since the 17.1.2 came out on the iOS firmware. This box doesn’t work at all anymore. It will flash it’s typical green go to flashing blue, then go to solid green

But the way that they handle the CarPlay set up is a little bit different now as it picks it up as a Bluetooth device and add it to the list, but when you click on it, it sends you to CarPlay

Sometimes, if you default it, it will work one time but the next time you turn the car off and back on it doesn’t work anymore
[Android Auto General] osm0sis:
Will as soon as I can. Big power outage in my area right now after last night's snow storm, and we haven't dug out yet. 😬
[Android Auto General] mike1986.:
I will be happy to help. AAW5836c28e
[Android Auto General] Draygon:
Yes Carplay.

Is there any fix planned or a downgrade to 3.0 possible? Thanks!
[Android Auto General] Snirpo:
Sure, if you give me your device's name,I'll revert to 3.0
[Android Auto General] diego1810:
3.3.0-202312031800-cs307-fix-44ea96dd138

d5f50 for me it's not fixed, 20 seconds to connect
[Android Auto General] Snirpo:
20 seconds sounds kinda normal though? Can you send in a bug report?
[Android Auto General] diego1810:
before on 2.x it was a lot faster, anyway tomorrow I will send bug report
[Android Auto General] osm0sis:
Finally finished shoveling! Sent! 😋
[Android Auto General] mike1986.:
For me it is actually noticible faster with 3.3.0.
[Android Auto General] KNAPPO:
Hi.

I picked up a AAW unit last week for my new Toyota Corolla and have been having major issues getting it setup over the last few days. Ive had a few tickets open with AAW support but nothing worked. Out of all the time ive tried ive only been sucsessful twice :(

Device: AndroidAuto-AAWd1ccb7f1

Car: Australian Toyota Corolla 2023 (Denso HU I belive)

AAW: 3.1.0

Phone: Google Pixel 7A - Android 14

Yesterday I found a post by @Snirpo (Post #5,748) from the 7th of September and the penny dropped why i was having so many issues... https://xdaforums.com/t/aawireless-general-discussion-and-support.4247677/page-288#post-88976575

Last night I tried again and followed the Denso HU connection and it eventually worked! But upon re starting the car it never connected again and I didn't want to remove all the BT connections and start all over again IF the connection wouldn't be retained so I decided to poke my head in here and see if I can provide any Beta testing help and try and get this AAW HU combo up and running.
[Android Auto General] IwaseKen:
@Snirpo my first gen device (name hSRIZO3c) is very stable at 2.1.0. I was right when not upgrade to 3.1.0. But I want to buy more device for my friend, how can I do it? I'm living in Asia and cannot see option for shipping. I could buy the first gen because it was on Indiegogo at that time.
[Android Auto General] Snirpo:
Please check my reply below:
[Android Auto General] diego1810:
today 75 seconds to start, sended bug report
[Android Auto General] osm0sis:
Does disabling Dongle mode still fix it?
[Android Auto General] diego1810:
later I will try and report
[Android Auto General] diego1810:
so do you think that disabling dongle mode will help?
[Android Auto General] Snirpo:
Most likely, because it removed the need for a handsfree connection to the car. Based on @osm0sis logs I'm pretty sure it's fixed. So I'll push this fix to production. Thanks for testing!
[Android Auto General] diego1810:
ok will try, thanks
[Android Auto General] osm0sis:
Interestingly that's what mine looked like it was doing during the wait time too; I could see the status icon on my Hyundai's UI showing that contacts/calls, etc. were being downloaded from the phone and it appeared to just take way way longer on this step.
[Android Auto General] rusinov:
Hello,

My setup is following:

Toyota Corolla MY21, Panasonic HU with latest firmware 1045 (released 04.2023)

Google Pixel 7 , Android 14, latest stabile security patches AA - 10.8.634424

I have the same issue which is described above. Initial pairing successful, when I switch off the car and power it again, AAWireless started blinking green, no way to connect it back.

I've reset everything - AAWireless device to factory defaults, Phone removed from Toyota HU, on the phone cache and stored files removed for AAWireless App and also AA. All bluetooth pairing removed also.

So next I've paired my phone to Toyota HU only like a handsfree and run over the AAWireless setup, without connecting my phone wired. What I found that pairing was successful, but my phone profile in the Toyota HU was switched again to AAMode instead of handsfree. Power off/on the car and connection dropped again. So, finally I've removed again everything and disable the Dongle Mode on the device, this trigger another AAWireless reboot, now the device is renamed to AAWireless-XXXXXX (Instead of AndroidAuto-AAWireless--XXXX), but it is working fine. I've switch the car off/on a few times, and it is still working. My phone apears as AA on the Toyota HU unit (instead of handsfree), but still works. Hope this is permament workaround until you/Toyota find a way to fix it.
[Android Auto General] Snirpo:
You're in luck because Panasonic HU's seem better than Denso. Unfortunately this is not something we can fix. The fix is disabling dongle mode. Toyota made a weird design decision to have either AA OR hands free enabled. Without hands free AA will simply not start up in dongle mode. So disabling dongle mode is the only way to fix it.

For Denso HU's you have the problem above + an extra issue, quoting myself:

"We've been investigating. It is possible, but cumbersome.

First, you need to disable dongle mode, because the car from some unknown (dumb) reason disables normal handsfree (without AA running) when AA is enabled. Same thing happens wired. Use AA once and next time you get into the car, hands free will not automatically connect.

Next, if you don't want to manually start it up everytime through the car's settings, you need an Y cable to make the dongle keep power and enable "auto video focus". The car kills USB power once when starting AA. Then the dongle reboots, and the car side times out and will not get video or audio focus.

Every AA dongle will have these issues."
[Android Auto General] Snirpo:
Yeah the effect is kinda the same. But the cause is different. Basically what was happening is the Wi-Fi authentication failing, this made the phone throw an error, and eventually stuff timed out on the device side and it restarted the whole process. This could happen up to 2 or 3 times.

And for the techies:

We use rngd to populate the entropy pool. This is needed for Wi-Fi encryption. On the gen2 devices it uses a hardware rng, on the gen1 devices it was software based. We had some changes our software which accidentally disabled the software rng, so rngd wasn't running at all. I enabled the hardware rng for the gen1 devices now as well (Why it wasn't enabled I don't know, has been like this since 1.0). We should've caught this error. I think the main problem being we are not really developing on these gen1 devices anymore and hardly any of our testers are using gen1's anymore. So next time we have to test them more thorough.
[Android Auto General] rusinov:
How we can report that to Toyota? Even we found the way (their end user support is awful) they will reply "We do not support AA in wireless mode", even the same Corolla cars in USA support AA wireless natively. :-(

Seems like all of us have to switch from Android to iPhone. :-(
[Android Auto General] diego1810:
disabled dongle mode and now connection is very fast: only 2 seconds!! many thanks
[Android Auto General] Snirpo:
Yup, probably because the USB port is powered when near the car. So the wireless side of the AA connection is already started in the background (blinking blue). When starting the car, the wired side will also connect.

Maybe we should start a petition to urge Google to drop this annoying "hands free has to be connected" restriction. In fact there is a setting in AA to disable this restriction. Its just not visible...
[Android Auto General] diego1810:
hi, how can we disable this restriction in AA?
[Android Auto General] RealNBB:
I have a gen1 device.

if i can help/test something let me know. :)

AAW03c1e63b
[Android Auto General] adoz12:
Hey, wondering if I could get some help with my AA Wireless issue.

Car is a 2021 MG 3 that only supports wired USB CarPlay via OEM touchscreen.

Just purchased a Gen 2 device, have the latest firmware and settings on (Carplay, AA over CP etc) however the car doesn’t see the AA wireless unit as a Carplay unit and hence nothing happens. LED blinking green. Phone is a Galaxy S23 Ultra.

I tested with the same phone on another car with an Alpine Halo AA/CP (wired) head unit and it sees AA Wireless as Carplay – all works well.

Any suggestions to get it working in the MG 3? It should work yes?
[Android Auto General] osm0sis:
Ah the joys of being one of the original Indiegogo backers... 😛😉

Happy to stay in the beta channel if you like!
[Android Auto General] grac:
Not true. I have gen2 and this same problem with connect AA over CP protocol
[Android Auto General] Snirpo:
Unrelated. AA over CP is in beta, it won't be perfect. Please post your device name and push a bug report through the app.
[Android Auto General] adoz12:
Just wanted to update - AA over CP in the MG 3 is working. Needed a full reset of the AAW dongle and AA (clear data) on the phone then to start it as a new install while connected to the car.

Issue now is the onscreen buttons don't work at all after the first initial boot until I activate Google Assistant from the steering wheel button twice. While this is occurring Spotify / maps / steering wheel buttons work fine.

I am also getting screen flickers every 30 secs to 1 min or so like the map is loading back in.

Any suggestions?
[Android Auto General] grac:
I reported it a few times 😎👍
[Android Auto General] Simon105:
I have been supporting version 1 since the beginning of the project. Then I bought gen2 as soon as I read that there would be carplay. I currently have ip15pro max and damn it doesn't want cp to work with my kia sportage. I understand that it is in the beta phase, but I wonder if it will work at all? My syslog in file. I also sent it to support
[Android Auto General] jhwbg:
Hi, I just received my AAWireless G2 and I got it running on my MB E200 2019 with NTG 5.5.

There is a issue when making or receiving phone calls, it sends me out from AA interface to MB phone interface and AAWireless reboots itself, after call is made it sends me back to AA Interface.

I'm on latest beta 3.2.1 and I hope that this will be solved in the future.

AA over CP is a great feeling when using full screen with native resolution.

Great work it will be amazing when ready.

Thanks

Jan
[Android Auto General] DMac1900:
Yes please!

My AAW is now connecting to my MY23 Toyota Corolla again!!! (wonder if this has anything to do with AA updating to 10.9.634624 - release?)

BUT it is much slower now, about 68-70 seconds from turning the power on (used to be more like 20).

AAWireless-31df1b7c

App version 3.37-1121
[Android Auto General] Snirpo:
It's already released in beta, I moved your device to beta.
[Android Auto General] Snirpo:
Correct, phone calls is WIP.
[Android Auto General] adoz12:
Also finding calls show on the screen in AA (AAW with AA over CP) but I have to use the phone to take the call. The actual sound from the phone call does not output from the car speakers.

I have submitted a bug report from the companion app regarding the onscreen button issue also.
[Android Auto General] kbwang75:
@Snirpo

Like to confirm what's the production firmware for gen2 ? The AAW site changelog is showing 3.2, beta 3.2.1 but my gen2 is 3.1 and showing up to date.
[Android Auto General] DMac1900:
It isn't updating from 3.1.

Is there something I need to do to force an update?
[Android Auto General] Snirpo:
Is the beta toggle enabled in the app?
[Android Auto General] Snirpo:
Hmm no, it's not showing up the update? Is the beta toggle enabled?
[Android Auto General] DMac1900:
Yes, it is. I've tried clearing the cache - but not a full data wipe/reinstall (yet).
[Android Auto General] Snirpo:
Hm odd, will look into it.
[Android Auto General] Snirpo:
I think I really know why this is happening... Will be fixed asap.
[Android Auto General] Snirpo:
Should be fixed now, can you verify?
[Android Auto General] DMac1900:
Still no update I'm afraid.
[Android Auto General] DMac1900:
Wait! 3.2.1 has just appeared - success!

Thanks Snirpo, I'll report back when I've had a chance to see what the start time is like with this.
[Android Auto General] mike1986.:
I'm currently on 3.3.0 beta. Is official 3.2.1 the same? It's written in the changelog that long connection time has been fixed but only for gen1. I thought we were testing a fix for gen2 devices?
[Android Auto General] Snirpo:
Only gen1 was affected by this bug. I see you have a gen2. 3.2.1 is pretty similar to 3.3 at this moment.
[Android Auto General] kbwang75:
My beta toggle is off.
[Android Auto General] kgeissler:
I am having an issue. When connected to aawireless, all phone calls go to the phone speaker and not thru the car speakers. Any way to fix this?
[Android Auto General] Snirpo:
Enable dongle mode
[Android Auto General] kgeissler:
It's already enabled
[Android Auto General] Snirpo:
What's the name of your device? (AAWireless-xxx or AndroidAutoAAW-xxxx)
[Android Auto General] DMac1900:
20 seconds from pressing the car's power button to AA displaying on the screen, no other action required.

Thanks again Snirpo, I was missing my AAW.
[Android Auto General] adoz12:
Same for me - calls only through the phone.

In the AA call screen it shows a message "Bluetooth not enabled" but Bluetooth is enabled. This is AA over CP in the MG 3.
[Android Auto General] J_E_F_F:
2020 Volvo XC60 & AAW v2 has always (since 6/2022) suffered from stuttering.

Installed the latest 3.2.1 beta and the latest beta app.

Phones are Galaxy S21+ and Pixel 6

Stutter fix - LOW is much worst than off

Stutter fix - HIGH is much better than low or off

I still need to test with my 2020 GM which also suffers from stuttering. (2nd AAW v2 device)

Please explain the different Stutter Fix settings of LOW, HIGH and UNLIMITED, is it seconds, KB, MB etc? (I realize those are related)

Is there is a negative to using either High or Unlimited.

Might voice commands be delayed in the buffer, higher battery use, or anything?

Should you use the lowest acceptable setting, or go right to unlimited? Why or why not?
[Android Auto General] Snirpo:
In AA over CP mode this is expected behavior. That's because we haven't implemented hands free audio proxying yet. ETA 3.3.0.
[Android Auto General] Snirpo:
What it does is set the max unacked audio packets to a higher value. The default value is too low on some cars for a wireless connection (we think). We can set a value from 0 to 4096. To make stuff easier for end users we decided to provide three values.

Right now it's:

Low = 50

High = 100

Unlimited = 4096

4096 has a special meaning in AA. We are not exactly sure how it works or what it does.

Some head unit / phone combinations need the audio stutter fix. Some brands seem to be most affected, like Volvo. But it's all a bit random. Some have audio stuttering, some don't. I was very reluctant to add this feature to the firmware, because it's bassiccly a hack, and hard to explain why this happens for some and not others. Personally I have never experienced it on all the head units I've tested so far, which is quite a lot by now. But in the end, if it works it works I guess...
[Android Auto General] muttleytm:
One of the messages states:

Remove all phone mirroring/Android/AAWireless history from your car

It seems to be saying to clear the history on the receiver. I've looked through the manual, looked through the setup screens and just searched online. I can find no mention of it or any place where I can do it.

Can someone clarify this?

Thanks
[Android Auto General] Snirpo:
On most cars this means to clear the bluetooth pairing with the phone on the car side. But is there a reason you want to clear this?
[Android Auto General] muttleytm:
That was simply the advice I was given. I did try just unpaiiring/forgetting. It didn't solve my problem at the time. I got sidetracked with other things though. So I'm going to try again. I also found out the radio also was a few firmware releases behind. So I've done the firmware update on the radio.

Just making sure I understand all the steps involved. I'll try again later.

I noticed the problem started after the Android 14 update. So I'm basically clearing the AA Wrreless data& cache, the AAWireless appon the phone, etc. Starting over from scratch.
[Android Auto General] adoz12:
@Snirpo

Thanks for the reply, shall keep an eye out for the upgrade on this.

Any ETA on 3.3.0 / can you make this available for my device if I send the unit ID?

Also are you aware of the 'frozen touch input' issue with AA over CP? Unable to use the car touchscreen to select onscreen AA buttons etc besides a red touch area at the top left corner which does nothing but then it will randomly start working if left for a while or you double activate Google Assistant from the car’s ‘voice’ steering wheel button.
[Android Auto General] kgeissler:
AndroidAuto-AAW20d462la
[Android Auto General] Snirpo:
Does this happen always or only when getting out of the car (turning off ignition) and getting into the car again?
[Android Auto General] kbwang75:
@Snirpo

My beta is off.

What is the gen2 production firmware ? My gen2 is currently 3.1 now.

The AAW companion app is show up to date.

The AAW website is showing 3.2 and beta is 3.2.1.
[Android Auto General] kgeissler:
While driving. If I make a call via the contacts app on Android Auto or I receive a call while driving, I have to pick up the phone and talk to the person. However, if I am at the main screen in my Kia and not AA, speaker phone works fine. It's only when android auto is actively running
[Android Auto General] Snirpo:
3.2.1 is fully available in beta and rolled out to 2 percent in production. 3.2.0 has never been in production because a bug was found (Long connection times on old devices).
[Android Auto General] kbwang75:
I was asking because 3.2.0 is listed in the firmware changelog site and kept wondering why my device kept missing that version.

[3.2.0]

Features:

Add audio stutter fix to work around audio stuttering on some GM/Mercedes/Volvo models.

‍

Fixes

AA over CP initial connection stability improvement.

AA over CP - Mercedes knob/touchpad fix.

AAWireless | Firmware changelog

AAWireless is the world’s first and leading wireless Android Auto™ dongle. ✓ Works out of the box. ✓ Comes with free companion app. ✓ Connects automatically after setup.

www.aawireless.io
[Android Auto General] Selo68:
Why does the app show me version 2.1.0 as current?Nothing new besides the beta version?
[Android Auto General] milanxx:
@Snirpo

Again, after a week of testing 3.2.0, it is running backwards without any problems. I still use start/stop.

It is strange that there is no switch to betaSW in the application now 3.38-1115-develop-1118e2f and previous ones last week

AndroidAuto-AAWd9474072
[Android Auto General] Snirpo:
Now there is.
[Android Auto General] kbwang75:
My beta is off but showing the beta upgrade firmware available