yashsingh1/xdaforums huggingface dataset:
[Android Auto General] Oversemper:
I've submitted the report (AAWvzwqPWSp) while it looked like google maps used car's GPS signal. I would much appreciate if you could check it for actual car's GPS broadcasting in the log. Thank you very much!
[Android Auto General] HofaTheRipper:
You are free to tell me what to change 👍
[Android Auto General] elbubi:
Sorry, just to be sure, did I need to make anything else to provide you with the needed debug?

Tried to replicate the issue with bug report activated, but I soon as I hit back arrow to go to update section, bug recording just stops.

Regards!
[Android Auto General] MoodZy:
Hi All,

Recently I've changed cars recently and bought a VW Passat B8 from 2016 with MIB2 (previously a VW Tiguan Allspace from 2020).

Since this car change my AAWireless doesn't want to function correctly. I have random disconnections happening (could be once every 10 minutes or once every minute). When the disconnection happens it seems that it's the AAWireless device which is crashing somehow as the little status light goes off and then starts the boot sequence again (nothing > green > blue).

In the past the VW Tiguan Allspace worked fine (even though it took more than 1 minute from start of the car to full working).

What I've tried :

1. New cables : doesn't change anything (the cables work for Android Auto if I connect my phone directly to it)

2. Reset : doesn't change anything

3. Updates from v1.8 to v2.0 to v2.0.1 : doesn't change anything

4. Several USB modes / connection modes / VAG crash fixes / Start Stop fixes etc. : doesn't change the disconnects

Additional info :

* Device : AAWireless-ezvXL6z3

* Samsung S10e on Android 12

* The USB interface on the Passat seems to stay on for a very long time despite the car being off. I happens that when I near my car in the morning I automatically connect to AAWireless even though I'm just passing next to it (not opening it, nor entering it).

Are those random disconnects something that anyone experienced before?
[Android Auto General] Dangze:
Enable Start / Stop, that's what it exists for...
[Android Auto General] MoodZy:
This doesn't solve the random disconnect issue sadly.
[Android Auto General] Dangze:
I agree, but at least it could/must solve the concerned issue...
[Android Auto General] Snirpo:
Known issue, you can track it here: https://github.com/cpebit/aawireless-issues/issues/124

If you be any chance live close to (or in) the Netherlands I'd gladly debug it in your car :)

I see you're still on 2.0.1 btw, could you update to 2.0.2?
[Android Auto General] MoodZy:
Thanks. I'll have a look at that !

I live in "central" Belgium.
[Android Auto General] Snirpo:
What's the name of your device (AAWireless-xxxx or AndroidAutoAAW-xxxx)? I'll enable the develop firmware. We made some changes to replicate the Moto MA1 more.
[Android Auto General] Marsou77:
Hello @Snirpo,

Have you seen my (long) message?

Thank you :)
[Android Auto General] Snirpo:
Now I did :) I enabled 1.8, but I don't think it will solve these issues. I see you have a NAC Wave 2 HU, which is a problematic one: https://github.com/cpebit/aawireless-issues/issues/106

"When playing music with Spotify, the AA interface is really laggy and not a joy to use. When stopping music, the UI is as smooth as when my phone is wired." <-- This is exactly what happens on these HU's. Both on the Moto MA1 and AAWireless.

However, Galaxy A7 being smooth is odd, although I'm not too surprised because I have the feeling my Pixel 6 Pro has become laggier lately as well running Wireless AA since the latest phone update.
[Android Auto General] DroidShift79:
So today I verified, that when I go to the car with BT and WLAN OFF, and then turn on the car after that turn BT and WLAN ON I get a flawless connection.

When some hours go by, and I leave BT and WLAN ON when I go to the car, connection won't happen, instead blinking LED.

@Snirpo

Maybe you already found the time to look into the logs I have sent?
[Android Auto General] Marsou77:
Ok nice to know! And thank you for your answer even if this is not what I wanted to hear lol. There is nothing you can do then?

Galaxy A7 is not a rocket in general but the music streaming doesn't impact the relative smoothess of the UI.

I see you enabled 1.8.0 but it seems I can't download it with the app, it download the 2.0.2 instead, see the video attachement.

If nothing change, how can I go back to 2.0.2? I ask you in the forum?

Thank you again!
[Android Auto General] Snirpo:
That doesn't seem right indeed. I'll check this with my collegue, cause I think something in the backend is wrong.
[Android Auto General] Snirpo:
I see you're using "direct" usb mode. That should not be used normally, 95% of the cars cannot handle that. Please use default or mtp USB mode. What color is the LED blinking?
[Android Auto General] DroidShift79:
When not doing the OFF/ON thing,

And just let it do its thing, LED goes from blinking blue to solid blue, AA icon in the HU goes away, then comes back on LED is going from blinking green to solid green, AA Icon goes away then LED goes to red.

To get it back to live and connection I have to unplug it, turn BT and WLAN OFF, plug it back in, turn BT and WLAN on again, then it finds a connection after some minutes

I sent you 3 logs the second was while the issue was on, the 3rd, after it got connected again.
[Android Auto General] MoodZy:
My device name is : AAWireless-ezvXL6z3

I should have sent some logs this evening (2x - the first time might have failed because I tried to send them too soon when the device was still rebooting).
[Android Auto General] elbubi:
Hi!

Today, after trying for 20th time, I was able to flash new version (v2.0.2).

Only odd thing is that now it keeps saying un update is available but actual version 2.0.2 / new version 2.0.2

Cheers!
[Android Auto General] Marsou77:
Hi @Snirpo

It's definitely not an issue with the AA wireless dongle... I drove to Paris ~ 1h with my phone wired to the NAC and there was a huge lag with music... I'm hundred percent sure I never had this issue before. I will test with my Pixel 3 to be sure it's a NAC issue.

Thanks for your help, you can revert my dongle to 2.0.2

Also, do you think I can mess up with AA developers settings to try to fix the issue?
[Android Auto General] Genebaby:
I went for a drive and got the notice that an upgrade was available. I did it in the garage upon returning home and unlike the previous updtates it was harder to get and apply.

I for some reason had to get it only via wifi, so lucky I was at home. I had to connect to the home wifi even though I had asked (a few times) to download now and not wait for wifi.

It wasn't quite 20 times, but it was the longest update I can remember.

I use direct mode again so I'll change that to Default. It generally runs fine in my car, the 2020 GTI with Mib 2.5, I am just hoping to be able to hear the Assistant on every drive, rather than about 50% of the time. That's mostly what I want in an update.

I'll test 2.02 over the next few sporadic drives. Maybe get 2.1 before that?
[Android Auto General] bergasha1:
Could I try 2.1 see if it fixes my issue please?

AndroidAuto-AAWPZXCRdoM
[Android Auto General] Snirpo:
Google :( Thanks for the info. I hope this will not be a great storm of Pixel issues again.

I also noticed it's not possible anymore to be connected to two wifi networks since the latest update. Before you could be connected to home network + AA wifi. But when you did that, AA got all laggy.
[Android Auto General] Snirpo:
I'll try to check your logs today, I'm a bit overloaded ATM.
[Android Auto General] MoodZy:
No rush. It's the weekend for everyone !
[Android Auto General] DroidShift79:
That is normal when using the dev version of the app. Dev version will always let you reflash actual version if there's no newer one.
[Android Auto General] Snirpo:
Yes, it's normal, but I'll remove it, because I get a comment about it almost every day :)
[Android Auto General] DroidShift79:
Okay then. I actually think this could be handy in some instances. If it could be done, maybe make it an optional choice?

Maybe you could also add a "reboot dongle" button?
[Android Auto General] Snirpo:
Had a look at the logs. Seems it's connected the correct wifi network, but somehow it can't reach the OTA endpoint of the device. I'll have a look into it when I have the time.
[Android Auto General] Marsou77:
Hey! I find out the culprit, I'm so happy!

It's the new Google Driving Assistant. You have to disable it and it is smooth as butter with music 😍

Google App > Settings > Google Assistant > Transports (with car icon) > Car mode > disable everything

Now it is like before, smoooooooth!

You can add it to the FAQ.
[Android Auto General] Snirpo:
Really?! Wow, that doesn't make any sense. This is crazy... Thanks!

I'm not that happy though because we are bassiccly a sh*tfunnel for every problem in AA itself.
[Android Auto General] Marsou77:
Yeah I understand the issue... You should mention it somewhere like an "announcement" or something if it's possible.

At least you can close the issue you sent me earlier and this explains why the Galaxy A7 wasn't laggy!

Could you also revert back the firmware to the latest available for my unit please? The updater keep telling me there is an update to 1.8.0 (it's not trivial but I would like to get the 2.1.0 later lol)

Also how can I clear the "bug report available" pop up? I don't want to sent it anymore 😁

Thank you and have a nice weekend!
[Android Auto General] DroidShift79:
I got bored today, so I thought I make a mock up how the AAWireless app could look like :D When swiping t he car picture could change if you want to connect to annother device/car :D
[Android Auto General] -Loom-:
Nice idea! With an option to upload your own picture of course ;-)
[Android Auto General] DroidShift79:
I'm sure Snirpo will surprise us down the road. I believe the app could have a lot of potential. But first all the teething troubles must be under control. I'm just a graphics dude, and cannot code.
[Android Auto General] Snirpo:
Haha nice! I'll pass it on to our UI/UX designer :) We have some UX changes in the pipeline, but it doesn't have the highest prio right now as you can imagine.

We made some changes in firmware 2.1.0 which means we don't need these dreaded USB modes anymore. The plan is to ship devices in passthrough + dongle mode, to make it work natively, like the MA1, by default.

Then we are going to hide away the settings in a sort of advanced settings menu, because all these settings are nice, but people don't read/understand what they do, stuff stops working and then our support has to handle it. Hardly anyone uses these settings, for example, dpi change, the most used feature, is only used on 1 percent of all devices.

Bassicly we are KISS'ing it, but still keep advanced settings for well... You guys :)
[Android Auto General] DroidShift79:
That sounds great and that's the way to go. KISS it for the majority but keeping the jucy stuff in there for the advanced users. Keep up the awesome work. And High 5 the whole team!
[Android Auto General] Dangze:
@Snirpo:

Start / Stop is a (very) usefull setting for me, as my HU keeps the power several minutes after contact switching off !...
[Android Auto General] Snirpo:
Sorry, I was talking about all the "hack / intercepting" stuff. Like dpi change, disable audio sink, timeout values etc. Start / stop is primary functionality and should actually be more prominent than it is now and part of the initial setup.
[Android Auto General] rayboehm:
So if I'm reading this correctly, I should be using dongle mode and passthrough, with usb set to default?

I was on dongle mode until installing the 6/24 dev firmware. Had to do a full reset, and the only way to get it working properly was direct usb, passthrough and dongle disabled. Also had to disable start/stop, and after several combinations I was able to get the phone calls through the car speakers instead of the phone.

If there's a better way, let me know.
[Android Auto General] DroidShift79:
Maybe @Emil Borconi

Could add best practice and/or first steps, dos and don'ts in the first post?

Guess that would help a lot.
[Android Auto General] rayboehm:
Just realized that since I've done a factory reset, my device number has changed. Could you add me back to the list for dev firmware? My new device number is AAWJU80j3RY.

I'm back to dongle mode enabled, default usb, passthrough enabled, and start/stop enabled.

We'll see if it sticks this time.
[Android Auto General] ForeverYoung7:
Hi

Please fix the bug with the new Version. No GPS Signal on Google Maps makes impossible, to drive. Thank you
[Android Auto General] Swap_File:
I've been happily using AAwirelsss in my Kia Stinger, but I do have a few notes on my specific installation that others might find helpful.

Instead of using the built in start / stop detection, I made a Y cable that hooks up the USB data lines and ground to my head unit, but power is pulled from a cigarette lighter USB adapter. I don't know if this is safe on all cars, but it worked on mine.

I have quite a few devices in my car I need to share internet with, and I do not want to buy an extra hotspot., so I had to make a few tweaks on my phone to make my phone's hot spot play nice with AAwireless. In the past I simply had a macrodroid script set up so that when my bluetooth connects to the car, it started my phone's hot spot.

Unfortunately, the limited wifi connection to AAwireless seems to confuse my phone's hotspot, and it won't share any internet once connected to AAwireless.

I found the trick was to to have Macrodroid enable my hotspot, then disable wifi, forcing the hot spot to share my cellular data connection, then reenable wifi, and script connecting to AAwireless manually.

The AAwireless password is the SHA-1 of the device name in upper case.

Note: AAwireless does currently support connecting through a hot spot, but only a hot spot that isn't also your AAwireless phone. Support for connecting via your phone's built in hot spot is eventually coming, but for now the method I use above has worked well for me.
[Android Auto General] Snirpo:
Sounds very complex :) I'll build this feature into the next version of the app, possibly this week. Care to test?
[Android Auto General] Snirpo:
AAWireless does not influence GPS in any way. Except when you have "remove tap restriction" turned on, please disable that.
[Android Auto General] ForeverYoung7:
No way

It happens right after the firmware update to 2.0.2 from aawireless
[Android Auto General] Snirpo:
Please enable passthrough mode to verify if it also happens in passthrough mode.
[Android Auto General] ForeverYoung7:
Thanks. I will try tomorrow.
[Android Auto General] DroidShift79:
Out of curiosity, do you use a OnePlus phone?

...as I heard a lot of this in these forums.
[Android Auto General] Swap_File:
Always ready to test. I'm already part of the google play beta group, will the test version show up there?
[Android Auto General] ForeverYoung7:
I have a oppo find x5 Phone
[Android Auto General] Snirpo:
For the latest, please download: https://appdistribution.firebase.dev/i/5196d378c8e122d7
[Android Auto General] skiptowncat:
Any help with this?
[Android Auto General] DroidShift79:
That's interesting, since OnePlus also is based on Oppo...

Did you maybe have or had a systemupdate on your phone?

You also could try these steps: https://themobilequery.com/oppo-find-x3-pro-gps-not-working/

...these also helped the oneplus users I know that have issues with GPS.
[Android Auto General] jimpoison:
I had the same problem with GPS not working (not finding position or not moving on map) after the 2.0.2 update.

Plugging out aawireless from my car's usb, waiting a minute und plugging it back in seems to have helped, at least with the one Google maps journey I had today.

My phone (even if it is a oneplus 8t ;-) ) was definitely not responsible, GPS worked there all the time and I could navigate with the phone without any problem
[Android Auto General] zengshengliu:
Can someone assist me with the client mode setup?

I have firmware 2.0.2, phone is Samsung Galaxy S10+, and Mercedes MBUX system. The regular wifi mode works for wireless AA, but when I try to setup the client mode by entering the in car hotspot information, the device is just stuck with white light. I entered and double check to make sure that the SSID and password is correct, and also has the car headunit bluetooth selected. The AAWireless notification said it is connected to the unit itself. I also see Android Auto notification (on phone) show up saying something like searching (or connecting) to Android auto, but after a few seconds, it just disappear (normally it will have a "Connected" persistence notification when connected)
[Android Auto General] ForeverYoung7:
I tried with this solution and its working well actually. 😇👌
[Android Auto General] DeanGibson:
Great work ! :(

When I fired up the AAW app, it said an update to 2.0.2 was available. When I tapped that, it asked if I wanted to download on a metered connection, & I said yes. It then started to display progress info at the top of the screen, & then almost immediately quit. Repeatable.

Why do I believe that this is a software error? Because the progress info was " % %d %", which means that someone screwed up an 'sprintf' function call.

This used to work correctly.

EDIT:

The above info was from attempting the update while AA was running on the car/AAW/phone.

When I tried again a few hours later, I did not give AA a chance to start, & the update to 2.0.2 worked perfectly, & I did not see the 'sprintf' error.
[Android Auto General] Snirpo:
I'll check. We've been having some backend issues lately, so that's probably the cause. The sprintf thingy is probably a side effect of that.
[Android Auto General] skiptowncat:
That doesn't help me at all, not playing any music has nothing to do with GPS.
[Android Auto General] osm0sis:
I've noticed that " % %d %" flashes briefly at the beginning of every update actually, so unless fixed with the last app updates is likely still an issue somewhere. 🙂
[Android Auto General] DeanGibson:
Probably vestigial, before they added the progress bar.
[Android Auto General] osm0sis:
It's in the spot where the percentage is calculated/displayed. My guess is there's an initial value of nul/100 or something that %d can't display.
[Android Auto General] DeanGibson:
"%d" will take the first 32 or 64 bits (depending upon the CPU architecture) of the parameter (fixed point, floating point, graphic data, music data, whatever), interpret it as a fixed point integer, & display it. The only reason that the "%d" is displayed, is if the parameter wasn't even provided in the call to sprintf().

That's a coding error. Perhaps a variable name for the parameter was originally provided, but when the progress bar was implemented, the variable definition was removed. This would then fail compilation, so the sprintf() call was modified to remove the variable name, with the idea that the sprintf() call would be fixed later.

This is all pure speculation, & assumes a C/C++/C#/Java source code base.
[Android Auto General] Snirpo:
It's exactly that, param was missing. Has nothing to do with progress indicator though, progress indicator has been in there since the beginning :) Param missing has also been in there since the beginning, no body noticed apparently.
[Android Auto General] Spoonoid:
I'm on 2.0.0 firmware.

I was unable to capture debug logs.

The device was connected to a charging USB, outside the car. After booting, the led was blinking green, and after some time it turns yellow (not white).

On the AAW app, when pressing on the bug report, an error message said that it was unable to communicate with the device. After like 3 or 4 attempts, it started to capture logs, the led began blinking green really fast. I tried updating, but the led turn yellow after a few seconds and when returning to the bug report, it was inactive...

I tried resetting multiple times, clearing cache left and right... Something that I can try ? It was working reaaaaally great for more than a year now, I don't know if the 2.0.0 update broke something or if I'm unlucky now.
[Android Auto General] Marsou77:
Hello @Snirpo

Usually I don't use AAWireless for short distances so I let my phone connected to it without using AA (blue blinking led) but when i enable Passthrough mode, the dongle reboot itself after a few seconds if I do not use AA (red led - green blinking led - blue blinking led cycle). Is this the expected behaviour in Passthrough mode ?

Thank you :)
[Android Auto General] Snirpo:
Really confusing. Not sure what's happening. Are you trying to update and in the meantime creating a bug report?
[Android Auto General] Snirpo:
Yup, that's because in non-passthrough mode we keep the wireless connection alive by pinging to the phone, even when the HU side is not connected.

In passthrough we cannot do this, so the phone side will disconnect after a 10 second timeout, this will restart the whole process.
[Android Auto General] ilbarba77:
Hi, every time I use the AAW, it automatically restarts after a few minutes, then reboots and goes back to work.

How can I solve this ?

Attached are my settings
[Android Auto General] DroidShift79:
Try to use the USB MTP Mode. Or MTP + Retry Mode.

Maybe firmware 2.10 rolls out for all, soon. Since at least a week I have no issues anymore with the latest 2.10 version. No more fiddling with USB Modes.

I'm running dongle Mode + Start/Stop + DPI Settings ( For my Swing Infotainment system with 6,5" Display, setting DPI to 103 is brillant)
[Android Auto General] DontKnowWhy:
I also have the UConnect issue - can you please roll me back to 1.8? jVAa3JWM
[Android Auto General] dscline:
I thought dongle mode & start/stop were redundant. On effectively nullifies the other. Am I mistaken?
[Android Auto General] DroidShift79:
Hmmm... I didn't know that, but when I not enable Start/Stop, while in dongle mode, i have connection issues when I come back to the car
[Android Auto General] rayboehm:
Probably depends on the vehicle or headunit. For what it's worth, I set mine to default USB, passthrough and dongle mode enabled, and start/stop disabled. On the 2.10 firmware it has been working flawlessly for days.
[Android Auto General] DroidShift79:
With passthrough I haven't had any issues. But I rely on that DPI Setting, and and with passthrough non of the advanced options work.
[Android Auto General] rayboehm:
Have you tried changing the dpi and then enabling passthrough? Also, in AA developer settings you can change the resolution. I currently have mine set to 1280 x 720 and get a full screen map on my 10.25 widescreen display.
[Android Auto General] DroidShift79:
No, at least not knowing. I'll try it tomorrow. Just for the kicks. (I believe that won't work, cos with passthrough no juice is injected xD)

At the moment, I don't see why I should use passthrough, when I want those juicy advanced features.

That I did try. But as I only have a much smaller HU display, + I like the smaller icons, DPI Settings are the way to go for me.

What I still have on my test list, is the AIO TWEAKER app which also have some nice bits to inject, like force widescreen, more calendar entries in AA, multi display, custom notification duration, and a lot more.

Would be awesome if @Snirpo one day add those things to the AA wireless app, too.
[Android Auto General] Snirpo:
Only reason I can think of it that the MBUX wifi has client isolation enabled, so the phone and device can't actually reach eachother.
[Android Auto General] Snirpo:
Not sure what AIO tweaker exactly does, but I guess it's hacking into the AA settings / APK. Not everything we can control from the protocol side unfortunately.
[Android Auto General] Snirpo:
What's the name of the device, so I can check the details?

EDIT: Nevermind, it's in the screenshot. I see you have an Xiaomi phone. Do these disconnects happen when the mobile data connection is lost?