yashsingh1/xdaforums huggingface dataset:
[Android Auto General] belarmito:
Thanks!

I have used it for 2 minutes and right, I can navigate through all screen options. When I need to switch from left or right area or to left column of icons, I can do it pressing wheel to the left while I turn it.

Only issue I've found is that previous/next song does not work if spotify screen is not maximized. If I have google maps in full screen or in left side with spotify in the right side of the screen, neither steering wheel buttons or audio volume wheel left/right press work. The only way is if I have spotify in the main area of the screen. I guess this does not happen in official giulia carplay with iphone device connected.

Is there some way to fix it or is it planned to be fixed in next upgrades?

thanks a lot for you good support!
[Android Auto General] joeyberkovitz:
I assume you're using AA over CP, not an iPhone?

Either way, if a button only works depending on what app is open on the screen, that's almost certainly an issue with the phone (whether it's Android or iPhone) because we have no idea what content is on the screen at any given time.

If you're using AA over CP, just note that the gesture mode turns next/previous track into up/down controls. To turn gesture mode off, either just push the knob to the left once, or wait 10 seconds without pressing any buttons.
[Android Auto General] belarmito:
I am using AA over CP. That's why I ask if this is the same behaviour as with an iPhone or if is different (in this case, It would be a bug).

I guess next/previous track buttons in steering wheel or in audio volume wheel in the console should work in any case with spotify, no matter what appears in the screen. With AA there is no problem with this.

Thanks
[Android Auto General] belarmito:
@joeyberkovitz , I have used the car again in a 10 minute trip and previous/next song functionality has worked perfectly in any place of the screen, both with steering wheel buttons and previous/next clic in the audio volume wheel!

But surprisingly, when I arrived at my destination, I started moving though spotify, maps, maximize one, the other, navigate through all icons.... and when I tried again to skip a song, it did not work, even when the icon selector was positioned in spotify screen. In fact, in some cases, when I pressed next/previous track in steering wheel or audio volumen wheel, icon selection in spotify moved, as if I was turning the selection wheel.

There must be some bug. I will keep on using it to check if I can find out in which conditions works and not. If you need some picture or video or any kind of test, please let me know.

thanks
[Android Auto General] grac:
I can't connect with AA over CP protocol.

After pairing dongle have bootloop.

When i connect with AA without CP protocol ev. work fine.

My phone is Samsung Galaxy S23 Ultra with new AA, my car AR GIULIA 2018y
[Android Auto General] J_E_F_F:
Dumb question, why would one choose to use AA over CP in the first place?
[Android Auto General] grac:
Because i want full screen in my AR GIULIA 2018y audio system
[Android Auto General] joeyberkovitz:
This isn't a bug, you're just misunderstanding how the gesture functionality works

I described it here: https://xdaforums.com/t/aawireless-general-discussion-and-support.4247677/post-89173865

If you have any other questions about it, let me know
[Android Auto General] l3s:
Right now with the current appcenter version and 3.1 fw I have only one minute of operation...

Alpine iLX-905d, Pixel 8 pro

0:00 start the car

0:36 android auto connection happens,

1:35 android auto connection interrupted. Never recover from this state

Sent you the logs from the app
[Android Auto General] belarmito:
I have read it more calmly and now I understand how to operate it. I have played a little bit with the system in my way back home and it does work perfectly. Turn knob to navigate through app icons and press knob to the left and turn wheel to move through apps in the screen. Now I see it is 100% functional.

Regarding voice commands: is it supposed to work without any problem? I have tried to make a command pressing command button in the sterring wheel and I see that the microphone and colour line command appear on the screen as it is waiting for me to make a command, but it did not work. After some seconds, android auto voice told me that there might be some connection error. I am not sure if this is a occasional problem, as once every some time it happens in android auto. I tried commands as "play XX artist in spotify" or "navigate home", and neither worked.
[Android Auto General] Snirpo:
I'll test next week. Have the exact same HU on my desk in the office. Didn't have time to unpack the Pixel 8 though.
[Android Auto General] l3s:
Thanks that's great! Please make sure to update your alpine device to v5 firmware. There's a lot changed since the last v2 firmware
[Android Auto General] Snirpo:
Never updated the firmware, so probably lots has changed indeed :)
[Android Auto General] AMAMSNL:
Hi there I am a Noob, but dont hate myself.

I have not red all 311 pages of this subject :sneaky: did take me a considerable time to find it....

Despite my lazynes hope there is someone that can tell me how to get AA wireless going on a NBT EVO 6 unit (lastest firmware update).

Perhaps there is manual somewhere, seen some posts, chatting about a firmware but have no idea where to find it and on what to install it.

I am a fanatic fan of AA ever since released but am unable to use it in my Mini Countryman F60 2019., only Carplay is supported, I keep a dedicated Iphone ios 17, in my car to run google maps app in Carplay (runs without a hitch) (full screen btw) but AA has more finesse. Would like to run AA from my Samsung Galaxy S20+ don't care if its wireless or not. Now I am wrestling with 2 phones which i dont like..

So have the following devices to get AA going on a Carplay only unit.

NBT EVO 6 latest firmware, UI and new Monitor, released on 2021 Mini's only.

Galaxy S20+

Android 13,

AA ver. 10.8.634424,

Kernel 4.19.87-27102101,

One UI 5.1

Thanks in advance for your help.

André
[Android Auto General] belarmito:
I have used it once more today. The problem with voice commands was due to AA service. Now it works perfectly.

Finally, I can have AA in my giulia with fullscreen even when its AA system does not support it.

@Snirpo @joeyberkovitz , I have to say that you guys make an amazing job. This AA through CP is going to be very useful for many people, including Alfa Giulia/Stelvio owners. There is a Giulia/Stelvio community that is going to buy AAwireless from now for sure. Right now this is the only AA though CP dongle in the market that works 100% in this car.
[Android Auto General] grac:
@Snirpo Can you add me to the 3.2 Beta Firmware?

Device ID: AAWf71e6c79

Device ID: AAW7526e215

Thx
[Android Auto General] Snirpo:
We will release 3.2 in beta soon. You can enable beta firmwares with the toggle in the firmware update screen. The plan is to provide updates in beta every month or so. We're not enabling develop anymore for the general public because it's inherently unstable and can potentially brick your device (although that's pretty hard to do). You can join us as internal tester ofcourse though, then you will get develop/nightly firmwares.
[Android Auto General] grac:
So, v.3.1 is the last beta ?
[Android Auto General] bigcid10:
I don’t have the beta option on my app.aawireless page

Is there a way to enable it so that I can receive the 3.2 beta when it comes out? Thank you.
[Android Auto General] b0thunt3r:
For me it's not possible because i'm on the stuttering fix from march. Can you help me out?
[Android Auto General] bigcid10:
I’m having an issue where I would be in a phone call with somebody and then all of a sudden they can’t hear me anymore and I have to basically reboot the radio and the AA wireless box and then it’ll come back for a little while

Audio and other things are fine, but it just seems to be related to phone calls the person that I’m talking to loses my voice. They can’t hear me anymore.

I’m on firmware version 3.17 and

AAwireless

aaw6189e073

3.17

thank you

Edit: this doesn’t happen when it’s wire connected
[Android Auto General] Snirpo:
Is this on AA or CP?
[Android Auto General] bigcid10:
Cp

I don’t have any problems with audio. It’s just a phone issue.

iOS 17.1.1
[Android Auto General] piumach:
Hi, I've got the latest beta firmware today (3.1.0) and I tried to connect my iphone, but under carplay settings it's not able to find the aawireless dongle.

Any chance to understand if my AA is gen.1 or gen.2? No stickers in the backside since the beginning, the only info I have comes from the companion app, device name: DOBFkwRn.

Thanks!
[Android Auto General] Snirpo:
Gen 1. Next version of the app will have device info functionality.
[Android Auto General] piumach:
Thanks for the prompt feedback!

I have a couple of questions:

1. Any chance to get carplay working on gen.1 devices?

2. Sometimes Android Auto is not able to connect to the car infotainment, only way to restore the connection is to soft reset the infotainment. It happened on my 2017 VW Golf (mk 7.5 with discover media mib2) and with current Octavia 2020 mk3 FL with Columbus infotainment. Any solution? It's pretty annoying

Regards,

Nicola
[Android Auto General] Snirpo:
Unfortunately little chance we can get CarPlay working on the gen1 devices. Not nessecairly because of the hardware, but more because of the low level software support. There's quite some kernel hacking needed to get it working.

For the VW issue, that depends on what the LED color is at that point. If it's blinking green it's a phone side issue. If it's blue or blinking blue it's something on the car side.
[Android Auto General] Simon105:
Hi. I bought a gen2 device specifically. and I can't connect to my car. I'm in contact with support. a regular china cp adapter works every time without any problems. please do something with cp in aaw
[Android Auto General] l3s:
It would be not fair to set up an error report like that

I installed 3 or 2 updates before version from firebase and for whatever reason the start stop mode got enabled that made the problem.

By disabling it no more disconnect happens.

I'm sure that I never enabled manually as I never used and experimented whith this mode

The long time connection problem is still present true
[Android Auto General] Snirpo:
It's beta functionality for a reason. We're working on car compatibility. We are not advertising CarPlay functionality on or sales page because it is beta, and not primary functionality (yet). May or may not work.
[Android Auto General] Snirpo:
I'm not sure what you mean by "it would not be fair to set up an error report like that". But start/stop can indeed be problematic on some phones. It will not turn on by itself though. So not sure how that happened.
[Android Auto General] Simon105:
I understand that and I've been with AAW since the first series. android auto works great on my car. I have sent the logs to support and I hope it will work because I want to continue using your device. the symptoms are strange, because aaw connects to the iPhone and the radio signals that it will detect USB, unfortunately it gets stuck and cannot connect. I'm waiting for good news! Regards
[Android Auto General] l3s:
Originally I reported this problem to you, and my error report it wasn't valid that's why I said it would be not fair to say I have this problem permanently.

The fact is I am not playing around with different settings etc in the app since a while ago, the only thing that I did to update the play store beta with a firebase app version (hopping to have any improvement on my connection problem) and I noticed it after each start I have problem with the connection (as I described originally)

During the weekend I spent some time to figure out what can make the problem, and when I opened the AAWireless setting I noticed it the start stop mode is enabled in the settings and I know that I never used this option, so I disabled it and everything started to work again. To me also strange because to enable start stop mode needs more then one step son have no idea how it got enabled.

Anyway as you asked me before to experiment with disabled connection to smart watch (watch in airplane mode), my experience is the following.

If my phone is in my pocket or bag, 50/50 I got proper connection or huge delay (more then a minute) to get connected.

If I have the phone locked but out of my pocket (AOD visible on the display) the connection almost every time time happens within 30 seconds.
[Android Auto General] unq80:
Hello my friend. I was in the same situation and already replaced my xiaomi with S23+ and AA works as expected now.
[Android Auto General] ijuzwa:
Thanks a lot for your feedback. Really appreciate it!
[Android Auto General] kbwang75:
@Snirpo

Probably better for AAW to have statement or banner somewhere to say Apple Carplay is only beta stage. Production support still uncertain.

If not all rush in to buy and have unrealistic expectations.
[Android Auto General] milanxx:
@Snirpo

New insights from operation. Suddenly, when the reverse gear is engaged, when the PDC function is in the camera, the connection was not established. It kind of disappeared after some update (DEV). And an active call when arriving in the car will not allow AAW to start either, the call will only be switched to the car.
[Android Auto General] Snirpo:
Yeah, maybe we should make it more clear indeed. I'll discuss with our marketing guys.
[Android Auto General] Snirpo:
On CarPlay, AA over CP or native AA?
[Android Auto General] pdxcire:
The Changelog link is on the System Update page, near the bottom, between' Latest' version x.x.x and the 'Start Update' button
[Android Auto General] milanxx:
I only have S23U so native AA. And are there any findings about the conflict with the watch?
[Android Auto General] mike1986.:
Sure, now it is. For for many days there was none.
[Android Auto General] pdxcire:
That's unfortunate, I'm glad you see it now though. I seem to remember seeing it for quite awhile, not sure if it was an option in the last 2.5 years.

I do agree with your original sentiment by the way!
[Android Auto General] Cipcino81:
Hello,

is there a way to download and save the current firmware of my aaw device in my phone and then the possibility to install this firmware again in the future directly from the saved firmware image ?

Or even better would be the ability to select from the aaw app which version of the firmware to install (included older versions) I'm still on 1.8 and it works ok for me, but if I could chose to install any firmware and not only the last, I could safely experiment newer firmwares and eventually go back to 1.8 whenever I like. That would be cool.
[Android Auto General] Snirpo:
Not yet, but it's in our backlog.
[Android Auto General] Snirpo:
Ok, I can put your device back on the previous firmware to check it out?
[Android Auto General] Snirpo:
Correct, this was a mistake. We simply forgot to update the changelog.
[Android Auto General] Snirpo:
Question: Does anyone have longer connection times on 3.x vs 2.x? If so, can you provide your device's name and push a bug report via the companion app (settings -> top right icon).
[Android Auto General] milanxx:
Yes, we can try. But I have a feeling that it was already with 3.0. Now I waited for AA and when it started I backed up and the connection dropped. Somehow it doesn't like it with PDC. And I didn't have time to look at the LED, my eyes were on the camera and mirrors, I just heard the annotations on the mobile phone in my pocket.

I think those calls were already at the beginning when I bought it, it's just a marginal problem.

AndroidAuto-AAWd9474072
[Android Auto General] mike1986.:
I do, but it might be very subjective. My device is Samsung Galaxy S23 Ultra. I'll try to provide a log soon.
[Android Auto General] marias77:
Noticed if you have a garmin watch with audio playback/ microphone aawireless won't connect unless you turn the watch off before entering in the car.. is there an easier workaround?
[Android Auto General] Snirpo:
Please try turning off dongle mode. Unpair, and then re-pair.
[Android Auto General] osm0sis:
Yep! Just sent you a couple of reports. Sometimes it's longer than others. AAWIf49c96b
[Android Auto General] grac:
Yes
[Android Auto General] bigcid10:
Does dongle mode apply to CarPlay as well ?

I was thinking, maybe this has something to do with the reason why I lose my outbound voice on phone calls after a certain amount of time

I have it enabled maybe I should disable it

I’m using CarPlay on my pioneer nex radio
[Android Auto General] Naplm:
On November 28, 2023, I received a notification in the application on my Samsung Note 10 about the new firmware version 3.2.0. After the update was completed, the device rebooted, but the application indicated that the installed firmware version is still 3.1.0. There is no notification about the new version 3.2.0. What is the problem?
[Android Auto General] alexxutzu:
I need to update my device to last version (after last downgrade to 2.2.0). I got a lot of Youtube Music crashes and many disconnecting problems. All of these after updated my S24 Ultra to Android 14. My car is Skoda Octavia 2022.
[Android Auto General] diego1810:
hi reported log long time connection AAW544d1d2c
[Android Auto General] Snirpo:
Problem has been found. It only effects gen1 devices. Working on a solution.
[Android Auto General] thatdude:
Thank you, @Snirpo, and everyone who assisted on AA over CP development. The continued development is very appreciated.
[Android Auto General] TS_:
After upgrading to 3.1.0 it's noticeably slower to connect. Will you please downgrade me to 2.2.0? AAW8cObecOf
[Android Auto General] lraulet:
@Snirpo ,

Hi I'm a new user of AAwireless switching from MA1.

I'm happy so far with AAwireless.

However, I do not find any documentation (wiki or any webpage will be fine) explaining each option available in the companion app.

In settings part there are plenty of settings : USB mode, Passthrough, Dongle Mode, .... Same story with the "paired phone" where there is a toggle to choose by preference the last connect phone ; it does not explain what is the behavior when this toggle is off.

Bottom line is where can I find technical information for all settings of AAWireless ?

Thx a lot in advance.
[Android Auto General] Snirpo:
The settings all have explanations in the app. However they might be too technical indeed. We are actually thinking of hiding them away. For most users there's no point in changing them.

I do agree with you regarding the "last connected phone". Maybe we should have an info button next to that setting. If you have that disabled it will always use the priority list for connecting.

Just curious: Why did you switch from the MA1?
[Android Auto General] lraulet:
Thx @Snirpofor your quick answer.

Regarding the documentation that is too technical, I do not think it is the case. I'm embedded SW developer so I should be (I hope :) ) able to understand technical explanation.

But, It appears that you need to click on settings before getting any information. It's not obvious because at the first stage you can think it will change/toggle the setting just by clicking on the initial feature icon; for example "Passthrough Disabled" ; you can think that clicking on it will directly enable it.

Note that I'm French so the UI is in French ; so, may be, part of the confusion is due to translation in the app. Explanation for each feature is really not really clear is all cases.

Is there a way to define the app langage to English ?

For the "last connected phone" there is, you are right, a popup that looks like a warning saying that if "start/stop or dongle mode is enable prioritization will not work". From UX standpoint I think you should remove the "toggle" in this screen as well as the ordering feature if start/top or dongle mode are enabled. Because those control are useless (confusing) when start/stop or dongle mode are enabled.

I have 2 more questions :

- If I understand well, the "dongle mode" is now the mode by default but with this mode some settings are not working ; is it impacting only the "connected phone preference" ? I'm asking because it is a feature important to me.

What do I risk by disabling "dongle mode" ?

- Am I correct if I say AAWireless does not use WiFi Direct and only use WiFi STA mode ? MA1 is using WiFi direct when possible.

Now regarding your question about why do I switch from MA1 to AAWireless.

The answer is pretty simple : with the MA1 I had audio glitch every 20s. So, to see if it comes from MA1 I ordered the AAWireless. You Setup wizzard is really perfect and there is a special screen for Samsung phone where the app asked for disabling Battery optimization for AA. With that setting AAWireless is working well ..... and ... MA1 as well :)

So now, which one will I keep ? Probably (95% sure) AAWireless for 2 reasons :

1) I like the ability to update the device (I wrote I'm tech) and ability to play with settings

2) For me MA1 is nearly a copy (reverse engineering) of the AAWireless, so I prefer giving my money to the original author.
[Android Auto General] Snirpo:
Switching to English is unfortunately now only possible when switching phone language. We will probably add the new per-app language support from Android 13 in the future.

Dongle mode is the native way how Android Auto should work with dongles, according to Google. That means only the phone which is connected to the handsfree of the car will start up AA. This is how the MA1 works as well. This is also means phone prioritization or switching will not work from the dongle side. Or well... it will work, if you make sure the correct phone is also connected to the hands free of the car. Otherwise AA will simply not start up.

If you disable dongle mode, AAW will work in a "emulated native AA wireless HU" mode. This means AAW (unfortunately) has to host a dummy HFP Bluetooth profile, because that's what AA demands. A native wireless AA HU has to has the AA Bluetooth profile + HFP profile. After the initial bootstrap, we disconnect this dummy HFP profile. On most phones this is fine. However on some phones (mostly Chinese brands), the handsfree audio routing goes completely funky. This mostly means phone calls go through phone speaker instead of the car.

Didn't realize the MA1 works in Wi-Fi direct mode, but in the end it doesn't really matter, because I'm pretty sure the MA1 will always be the AP (hotspot). AAWireless works in AP mode, but it can also be switched to client mode from the Wi-Fi settings. However I would not suggest to use client mode because we have to run our own foreground service on the phone to make it work. Some phones are pretty aggressive with power saving (Samsung for example) and they will just kill the foreground service randomly, this will kill the AA connection. Hence client mode being tagged "EXPERIMENTAL", and it will probably stay experimental forever. Last time I tested client mode it worked fine on Pixel phones though.

The MA1 isn't a copy perse I think. But it is quite interesting they use the same SoC as gen1 AAWireless. They also use a very similar Wi-Fi chip. Potentially the AAWireless firmware will work on the MA1 without any issues. Never tried, but I'm pretty sure it will work with few changes.
[Android Auto General] lraulet:
Thx @Snirpo for all those details.

In addition to the Phone prioritization that does not work with Dongle mode, what is the list of settings/features that do not work either?

And by the way, can you point me a technical document (may be from Google) that explain how AA dongle (protocols, messages sequences,...) is working? I'm interested on understanding more deeply this part.
[Android Auto General] DroidShift79:
@Snirpo

I'm registered, at least I was, for the firebase dev releases of the app. Lately I do get the emails that a new version is available but when I click on it, it says version is not available. Any Idea how I can fix this? Latest version I see is 3.35, and mails informed me up to 3.38.
[Android Auto General] mr.shme:
Is there anyway to downgrade my unit (fa88bcde)? I installed the 3.1 update last week and dongle mode no longer seems to work with my truck.