AAWireless - General discussion and support

[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)

 

[ForeverYoung7]

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.

Any help with this?

I tried with this solution and its working well actually.

 

[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.

 

[Snirpo]

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.

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.

 

[skiptowncat]

I tried with this solution and its working well actually.

That doesn't help me at all, not playing any music has nothing to do with GPS.

 

[osm0sis]

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.

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.

 

[DeanGibson]

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.

Probably vestigial, before they added the progress bar.

 

[osm0sis]

Probably vestigial, before they added the progress bar.

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.

 

[DeanGibson]

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.

"%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.

 

[Snirpo]

"%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.

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.

 

[Spoonoid]

Can you possibly download the Alpha app from: https://appdistribution.firebase.dev/i/5196d378c8e122d7 . This version has debug logs enabled you I can see what's happening (or not happening in this case ).

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.

 

[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

 

[Snirpo]

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.

Really confusing. Not sure what's happening. Are you trying to update and in the meantime creating a bug report?

 

[Snirpo]

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

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.

 

[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

 

[DroidShift79]

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

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)

 

[DontKnowWhy]

I also have the UConnect issue - can you please roll me back to 1.8? jVAa3JWM

 

[dscline]

I'm running dongle Mode + Start/Stop

I thought dongle mode & start/stop were redundant. On effectively nullifies the other. Am I mistaken?

 

[DroidShift79]

I thought dongle mode & start/stop were redundant. On effectively nullifies the other. Am I mistaken?

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

 

[rayboehm]

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 ca

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

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.