yashsingh1/xdaforums huggingface dataset:
[Android Auto General] Snirpo:
Surprising! Could you check with WiFiman (great app btw) https://play.google.com/store/apps/details?id=com.ubnt.usurvey&hl=nl&gl=US what the actual channel is the device is using now?
[Android Auto General] Shammy7861:
You are a legend dude will keep t

you in the loop once I have applied it. I have alot of respect for you and thank you for putting in all the hard work and effor you have done.
[Android Auto General] x10isrooted:
sure. let u know later today when i drive back home on the same crossing where it always happened.
[Android Auto General] l3s:
@Snirpo I have updated the device with Hyundai SSL fix version. Unfortunately that does not change anything for me. After a firmware update, I disabled passtrough in the app, I have reset the Android Auto data and cache, then connected my phone with cable. Then connected the AAWireless and the same thing happens, on the mobile looks connected, led solid blue, but on the Alpine device nothing happens. (Tried all USB modes too)

By enabling passtrough it works again.

But thanks for the update!
[Android Auto General] snapilica2003:
That explains a lot then :) Thanks for clarifying.

But using dongle mode and start/stop doesn't that at least make it so that there's not a secondary bluetooth handsfree connection for calls on my phone? That's the main issue for not wanting to use standard mode for me as there is the "AAwireless-xxx" bluetooth connection as well as my car's bluetooth connection, both enabled for calls. So when this happens any calls I initiate or receive the audio will be randomly passed to one of those two devices.

That's basically my main issue with standard mode and why I wanted to try dongle mode.
[Android Auto General] diehof:
Hallo, the same with me....but when I quit the app only by selecting radiobutton it works with update to 2.0 in handyapp....
[Android Auto General] Snirpo:
Yes, but in start / stop mode the device will not use the bluetooth connection of the device at all, so it shouldn't make a difference. Except when you open the companion app for changing settings, then it will connect to bluetooth.
[Android Auto General] Snirpo:
Unfortunate, must be another issue. It's funny actually, because I have an Alpine ILX-903D myself for testing, and it works fine without passthrough. Almost the same head unit you'd expect, apparently not.

Could you shoot in a bug report via the app? I'll have a look.
[Android Auto General] huppejue:
Hello, everyone, I use the device in a car with my wife. With this setting, shouldn't mine (JH) always be used first when we're both in the car? However, the last connected device is always connected. Is it the same for you or am I doing something wrong? Best regards
[Android Auto General] l3s:
@Snirpo

Yes I had iLX-F903F before, and it was working well with no passtrough enabled. Actually if I remember correctly with that device everything worked well out of the box with default USB mode. With the iLX-F905D if I leave the USB mode on default, I get an "USB device not supported"message no matter is the passtrough enabled or not. But with direct or MTP mode passtrough enabled, it is connects after around 40seconds the power applied.

I'll send you a bug report very soon.

Many thanks for your time!
[Android Auto General] dscline:
@Snirpo that'd be great, thanks!

qYyGHOFB
[Android Auto General] sibesaver:
I had this issue with my Kenwood head unit. Working prior without pass through but the new firmware wouldn't connect without it. I solved the problem by actually uninstalling Android auto updates rebooting the phone and reinstalling. Clearing cache and data and resetting the device didn't help by itself.

Make sure AA wireless is configured without pass through before first connect
[Android Auto General] Snirpo:
Definitely different hardware (/ firmware) then.
[Android Auto General] Snirpo:
No, you are correct, thats how it should work. I'll check.
[Android Auto General] Snirpo:
Are you sure this device name is correct? I can't find it in the backend for some reason.
[Android Auto General] dscline:
@Snirpo hmm, well that's odd. The other day when I was in my car playing with this, I took a screen cap so I'd have the ID if needed. So I just went back out to my car and did it again, and it's completely different. 🤷‍♂️ See below.
[Android Auto General] rodak:
I have the same issue with my Sony system.

Pixel 6 Pro

Sony XAV-AX5550D

Firmware 2.0.0 but also all past firmwares.

Solid blue light, says connected but nothing shows on my screen. With passthrough enabled it works as normal.

Will the Hyundai SSL firmware fix it as well?

AndroidAuto-AAWx20ZG7ZB
[Android Auto General] Snirpo:
Yes pretty sure it will. I enabled it.
[Android Auto General] Snirpo:
Did you factory reset the device possibly?
[Android Auto General] dscline:
Yes, I did. I thought I had taken that screen cap afterwards, but maybe not. After I first upgraded ot 2.0, I tried out dongle mode, and switching back to non-passthrough. I then had some difficulties getting it to connect regardless of what I changed, so I decided to reset and start over. I didn't realize the device ID would change with a factory reset. Sorry for the confusion.
[Android Auto General] rodak:
Does the device id change with every factory reset? Or just this time after 2.0 update?
[Android Auto General] l3s:
@sibesaver

Many thanks, I'm going to try this, however once I tried to uninstall android auto updates, but I did not reboot the phone also true.

Could you please confirm the steps?

1. Make sure passtrough disabled

2. Disconnect AAWireless

3. Turn off head unit

4. Remove Android Auto updates

5. Reboot the phone

6. Install Android Auto updates

7. Connect the phone with wired connection

8. Disconnect the phone

9. Connect AAWireless

Is this correct?
[Android Auto General] sibesaver:
I did not perform step 7 and 8. Also of note I did this away from any known Wi-Fi connections but not sure that that's relevant.
[Android Auto General] Snirpo:
No problem, a factory reset on firmware < 2.0.0 did not reset the name, so I get the confusion.

We changed the factory reset to be a bit more aggressive to be sure no data is leftover. The device name change is intended.

We decided we don't really care about the device name, the mac address will stay the same so we can still uniquely identify devices.

Also some phones are very persistent with caching the device bluetooth name (especially Pixels). So it could've shown the old name for a while.
[Android Auto General] rodak:
Thanks, still solid blue but not working without passthrough, anything I can provide to investigate?

Best regards
[Android Auto General] l3s:
Thanks for confirming.

I did everything as is written above skipped step 7-8, but unfortunately it does not provide me a solution.

Passtrough turned off, by first start it does show in the phone notification bar the Android Auto connected, however I don't see the popup message what you need to confirm by the first start of Android Auto. The head unit does not display any connection, but the led is solid blue.

When I am enable passtrough I get the first start pop up message immediately.
[Android Auto General] sibesaver:
Well sorry that didn't work for you. You may be facing the SSL issue @snipro mentioned in previous threads which affects some head units.
[Android Auto General] dscline:
Ok, got the update. Unfortunately it doesn't seem to have changed anything. I still require passthrough for it to connect to the car. Non-passthrough originally worked, but I had changed it to passthrough to see if it would help with some disconnections I was seeing. When 2.0 came out I decided to try non-passthrough again, but it hasn't worked. Unfortunately around the same time there was an infotainment update for my car, so I'm not sure if the inability to connect w/o passthrough is due to that update, or something to do with 2.0. It's not a huge deal, it works, I'm just unable to take advantage of the click limit bypass. I may tinker with it more later, or wait and see what further updates bring.
[Android Auto General] Shammy7861:
It only changes the 1st time then sticks with that I would advice reseting it and then configuring it starts with a clean slate and nothing in the back ground then.
[Android Auto General] osm0sis:
Can this be represented in the app UI?
[Android Auto General] Snirpo:
Yes, I already updated the text for dongle mode. But the problem with the app is, for same people it might get even more confusing if you try to explain it. Explaining what something does and trying to keep it understandable for less techie people is pretty hard.
[Android Auto General] osm0sis:
Nice! I also mean shouldn't that be visually represented by enabling start/stop causing dongle mode to be grayed out or something?
[Android Auto General] milanxx:
Ahoj. U CE&EB IT je popis Start / stop hodně skrytý a teprve s popisem se čeká na odezvu v telefonu. Až v aplikaci po přečtení tohoto fóra jsem našel co jsem potřeboval a teď to mám aktivované na BT svého auta. Protože moje Škoda Fabia s Swing + zapíná USB hned po odemčení. A tak krabička svítí modře a jednotka ještě není plná. A to pak způsobuje, že nemusím vždy klikat na displej jednotky s novým připojením. Teď se zdá, že je to ono.
[Android Auto General] SchwarzAugen:
Hello to everyone! I drive a Hyundai bayon 22. my phone is one plus 9 Pro android 11. when i press the command key from the car it says oops something went wrong please try again later. but when I unlock the phone and press the command key again, it executes the command and it works perfectly. I have this problem only when the phone screen is locked. Does anyone know about the solution?
[Android Auto General] milanxx:
V telefonu najdete v nastavení Android Auto, zda funguje funkce AA, když je telefon zamčený?
[Android Auto General] SOFO888:
I also had issues with my screen locked.

I made a Tasker task to unlock the phone as soon as Android Auto is running because the trusted devices function of Android was not reliable on my phone.

You could try out the trusted devices function in the settings.

If this does not work, Google for the Tasker and make a script.
[Android Auto General] Boosky:
Don't you have an opinion in AA app's settings called "run Android Auto without phone unlocking"?

Not sure how it is in English, I use Polish version. And not sure how it is in Android 11, I use Android 9.
[Android Auto General] -Loom-:
Might I suggest that you add a brief description to the app about what the different led colors mean? Might make troubleshooting easier.
[Android Auto General] x10isrooted:
Here are the promised info about the channel. Not a single issue since fw 2.0 for me still.
[Android Auto General] SchwarzAugen:
There is no opinion like that? Do you have?
[Android Auto General] sibesaver:
I think you're referring to this, but it's only applicable to running Android auto on the phone screen I believe
[Android Auto General] Boosky:
It works for me and it's in mine settings.

Phone screen settings are below.
[Android Auto General] martin.armstrong:
it is an option for AA for car screen, not for phone screen.
[Android Auto General] Boosky:
That's what I meant :)
[Android Auto General] SchwarzAugen:
Yes this is working normally automaticly. O think ım gonna use smart lock for my car that way phone always ve unlocked in car.
[Android Auto General] GoLuftwaffewar:
Hi, in my Kia Niro PHEV 2021 the aawireless FW 2.0.0 is working great with my Samsung Note20 Ultra 5G, but with my wife Samsung Galaxy S22 Ultra, the calls seem to go to the AAwireless dongle instead of the car BT.

When I go in the BT Settings and disconnect AAWireless, the call is now on the car BT.

Any Idea how to fix this?

Thanks
[Android Auto General] morrislee:
I can confirm this process works!! Back to no need for passthrough!
[Android Auto General] Snirpo:
Yeah I think this is some kind of security feature, to have AA not start when your phone is locked. Might be useful for wireless connections

Please try to enable "Dongle mode" from the settings. You may need to re-pair afterwards.
[Android Auto General] mobileman88:
Splendid. I will try this today
[Android Auto General] mondogarp:
Hi everybody. I have received my AAwireless a few days ago. My phone is a Poco X3 pro (MIUI 13) and the car is a Dacia Duster 2021 with original Mediadisplay.

The phone immediately connect to AAW and android auto starts without problems each time, but then I have a lot of disconnections. Sometimes they are very short and the system reconnect immediately, otherwise it takes a lot of time and I have the message on my phone that Android Auto is searching to connect. It happens with both 1.8 and 2.0 firmware.

I have tried different solutions searching on the thread, but nothing works (it seems to me that the main issue for other users is the initial connection to AAW).

After some tests, my guess is that the issue happens when the phone mobile network or the GPS position has some problem and is disconnected/reconnected, but i am not sure of it. My mobile phone has two sims from diffferent networks but I use only one at time. When I switch them, Android Auto immediately crash
[Android Auto General] rodak:
I tried all different solutions proposed here like uninstalling Android auto updates etc but still solid blue with nothing on the screen. As soon as I enable passthrough it works.

I sent a bug report through the app earlier today, can you see some issue?

Current device name AndroidAuto-AAW0eGZNMRG but it might have changed a couple of times due to multiple resets.

Best regards
[Android Auto General] llaugerm:
I have updated Android Auto on my Pixel 13 running Android 13 beta 1 and after I did the Android Auto update the AA wireless keeps disconnecting with an error message on my Pioneer Head Unit android auto has stopped, stop the car and check your connection. It was working fine prior to me updating to the newest Android Auto. I'll uninstall the updates and try it one more time. This is just to let you know.
[Android Auto General] Kermit83:
I have aawireless for several days (Mazda CX-5 '17 and Galaxy S20).

After the first connection, there was firmware 1.x. I have updated to 2.0.

At the moment, it looks to be working, but I'm having a few minor issues:

1. When someone calls me on my phone it is ok. But if I want to call, I hear the voice from the phone, not from the car. I read that firmware 2.0 has improved the dummy Bluetooth hands-free profile.

2. I would also like my phone to be a hotspot in the car. From what I have understood so far, the Wifi Client mode should be used with an external hotspot. Do I understand correctly?
[Android Auto General] Snirpo:
1. Please try dongle mode from the settings in the app, this will disable the handsfree profile of the dongle.

2. Yes for now it's only external hotspot. But i can change this quite easily to be able to use the hotspot of the phone. It's on my list. Unfortunately because of limitations in Android, you will probably have to fill in the credentials yourself, but that's a minor issue I guess.
[Android Auto General] Kermit83:
Do I have to connect phone by cable first, before I use dongle mode? that's what it said in the popup in the app. At least that's what I understood ;)
[Android Auto General] mobileman88:
That's what I did. Seems to work well now
[Android Auto General] darekb:
Try AA developer mode you should select:

- save the sound

- record microphone input
[Android Auto General] Kermit83:
Dongle mode works fine. Thanks.

Unfortunately, sometimes disconnects and reconnects after few seconds. At the moment I am in pass through mode.
[Android Auto General] Snirpo:
Yes correct!
[Android Auto General] CAT1210:
I am having some serious issues with this thing. I drive a 2021 CX-5 and have a Z Fold3. I, finally, got the AAWireless to work reliably and I was directed to update the firmware (yesterday) to 2.0....now, when I get in the car and start going down the road AAWireless fires up just great every time but there is no audio (Waze, Spotify, etc) whatsoever. I need to either unplug AAWireless and plug it back in or go into the AAWireless app and go into settings and click save to "reboot" AAWireless while driving down the road and the audio will work after that. To troubleshoot, I restarted the Z Fold3 to see if that would work, it did not. I restarted the Mazda Connect to see if it would work, it did not. Only restarting the AAWireless fixes the issue....

Anybody have any ideas? I am using MTP, no passthrough, and Start/Stop for my vehicle but no other options enabled, which worked fine prior to the update.

Thanks!
[Android Auto General] DeanGibson:
If I move the AAW to a different model car, is it necessary to reset it, or do anything special?
[Android Auto General] anz17n:
I'm getting the same issues as others are getting after updating my Hyundai navigation. AAW was working great before, but now I have to use passthrough.

Is there any timeline for when the SSL cert fix will be deployed? I'm also interested in getting the fix but don't want to keep cluttering this thread with posts requesting devices to be added to the list. Maybe a separate form to request the fixed firmware?

On a separate note, I'm curious about how this ended up breaking. Any idea if Hyundai is specifically targeting AAW? Or, is AAW just caught in the crossfire for some other change? Does this fix prevent these sorts of breaking changes from happening again? Or could Hyundai, or other manufacturers, just block new SSL certs again?
[Android Auto General] Msan2000:
Could I also try the SSL fix firmware please?

AndroidAuto-AAWjnNspavj
[Android Auto General] GoLuftwaffewar:
Thank you for the Dongle solution, it worked.
[Android Auto General] Snirpo:
Not sure why Hyundai did this. Hard to say. Hyundai / Kia (atleast on my e-Niro) runs Android. So it's quite possible they just updated the AA receiver side (possibly from Google themselves) and the "security" was tightened.

I do want to give more information on how we want to fix this properly, but I'm pretty sure carsifi is following this thread as well and they are bassiccly copying all things we do, so if you don't mind I'm going to keep it quiet :)

I think we can release this in a week or two. It's a bit more intrusive than only replacing the certificate. That's what I did now, but it's only a temporary fix.
[Android Auto General] steveone77:
Hi, only a question. When I make a call, my voice goes directly from the phone to the car's bluetooth or to AAwireless device?
[Android Auto General] huppejue:
Hello,

I have now noticed a new phenomenon. I use the device in a car that I share with my wife. When my wife starts the car in our garage, it's possible that my cell phone (which is in the office, for example) is the first to connect to the AAWireless. Before the FW update to 2.0, as soon as my wife drove away and my connection was broken, her cell phone connected to the AAwireless. Unfortunately, that doesn't work anymore. The device glows blue and the image is frozen on the navigation screen in the car. She then have to switch off the ignition briefly so that the device restarts. Then the AAWireless connects to her cell phone. Unfortunately this is a bit annoying. Will there be a solution for this?

Bets regards
[Android Auto General] smirle:
I just factory reset my AAwireless after upgrading to 2.0 a week or so ago.

When I went through the setup after factory reset I noticed that dongle mode was on without me doing anything. Is dongle mode turned on by default when you factory reset on 2.0?
[Android Auto General] guitarz:
Just got AAwireless unit today for March contribution.

LED was steady white with no blink or color change at all, even after reset.

Is this normal?

Oh I cannot connect too.
[Android Auto General] DeanGibson:
Support

cpeb.freshdesk.com
[Android Auto General] Snirpo:
Yes just found out about this a day ago through one of our testers. Already have a fix. Care to test?
[Android Auto General] Snirpo:
No wifi or Bluetooth visible either? Then it's unfortunately defective :( Sometimes these devices (somehow) slip through QC. Should never happen of course... Please contact support@cpeb.it for a replacement.
[Android Auto General] Snirpo:
Correct, it's defaulted to dongle mode. Eventually we want everyone on dongle mode, but we didn't want to "break" people's current setup after update.

Dongle mode is how it should work, but It's Android Auto so things will break for some and that means support load for us.
[Android Auto General] SOFO888:
I'm still on the old firmware.

I had only one disconnect 2 days ago since my last post.

Today Android Auto forced me to update to 7.5. I was on 7.2 before.

Hopefully it will stay as reliable as it was during the past few months ;)

Thanks to the team.
[Android Auto General] zengshengliu:
I recently updated to 2.0 firmware, and ran into some issue.

My car is 2020 Mercedes GLE with MBUX system. With an hour commute, AAWireless would disconnect 7 or 8 times, and each time after it disconnect, it will automaticaly reconnect after a few minutes. (I can't connect manually since Android Auto button is grey out during the disconnect)

I also see it a few times where after I started the car, AAWireless will remain "off" (no light) until I disconnect and reconnect the USB cable.

I did perform a reset of the unit itself, have USB mode set to MTP with forced start, and with dongle mode enabled.
[Android Auto General] guitarz:
Thanks. Mine doesn't behave like this at all.

Thanks. Obviously, it's a faulty unit. Will do.
[Android Auto General] 1qazwsx4:
@Snirpo

Is there any plans to bring obd2aa support through AAW considering emil/his team seems to be trying to make this app work again? I thoroughly miss having a way to have android auto display my gauges
[Android Auto General] andreaslev:
Good to know, I have a Kia PHEV, but haven't installed an update from April yet. Better to wait a bit then. Thank you

I've never had AAwireless run as smoothly as it does now. Latest beta app and firmware 2.0 on Samsung S20 Plus
[Android Auto General] Snirpo:
If you enable "developer mode" from AAWireless settings it should work wireless.
[Android Auto General] 1qazwsx4:
Hmmm did not realise there was an option for that inside aawireless app. I had tried the updated obd2aa app after mblok and Emil did the revised version but it didn't work for me because patching it for android auto made aawireless no longer work (on 1.8 firmware) I just downloaded the latest version from the purchase website and it wouldn't appear in android auto (even with enabled unknown sources) so I patched it using AA AIO and it worked perfectly tonight but apparently it will eventually say "there are no new messages" when opening the app due to Google changing stuff.

Will be interesting to see of it sticks or not.

The way I used above, it did function wirelessly thought I would add. Will update if it stops working anyways
[Android Auto General] huppejue:
How can I Test? Do you give me a new FW? My device is AAW5slVSV7W
[Android Auto General] Snirpo:
I enabled the firmware, it's called Hyundai SSL fix, but the the issue you were talking about is also fixed in this version. You can update via the app.
[Android Auto General] Snirpo:
The "developer mode" is intentionally a bit undocumented ;)
[Android Auto General] 1qazwsx4:
Thanks for your response, will have to have a look through! Happy my device is working perfectly at this stage so didn't want to fiddle too much haha thanks for all your work
[Android Auto General] huppejue:
Hello, I just tested it with the SSL FW. Sadly it still does not work. The device stays blue and the navigation screen is frozen. I think with the old FW the device started flashing red and then restarted... which then led to my wife's cell phone connecting. best regards
[Android Auto General] huppejue:
Or do I have to reset the device after the FW update?
[Android Auto General] Snirpo:
No, it can freeze up for up to 15 seconds, then it should restart. If not, I'll look into it.
[Android Auto General] huppejue:
I think you should look into it ;-)
[Android Auto General] Snirpo:
Will have a look this evening!
[Android Auto General] fcaronte:
Hi all, what's exactly do the "dongle mode" what the difference from other connection way?