AAWireless - General discussion and support

[tallleroy]

@JohnnyCanuck has a specific problem that the developers want to investigate using the debug logs. He alone was sent the 1.1.0 firmware because the 1.0.0 firmware has a problem with sending the debug logs.

The rest of you will probably see 1.2.x as your first firmware update.

LeRoy

 

[Genebaby]

I'm looking forward to the new FW to send logs. It seems that when using AAW there a audio dropouts more often than cable. I wasn't really sure if it was the phone or the AAW connection. As per my wife's mentioning there is an area near our house, no houses around, that it gets really bad, especially for her.

This morning I was driving a VW Polo that I had moved my AAW box into while my car is in the shop and there were a few dropouts and a quite long one of about 8 seconds. So I'm keen to see what bug reports can show.

Having said that I decided that I need another so I ordered a third box. When my car comes back I'll take my wife's one and she can use a cable for now, until the third arrives and hopefully there are improvements for her experience.

 

[JohnnyCanuck]

I'm looking forward to the new FW to send logs. It seems that when using AAW there a audio dropouts more often than cable. I wasn't really sure if it was the phone or the AAW connection. As per my wife's mentioning there is an area near our house, no houses around, that it gets really bad, especially for her.

This morning I was driving a VW Polo that I had moved my AAW box into while my car is in the shop and there were a few dropouts and a quite long one of about 8 seconds. So I'm keen to see what bug reports can show.

Having said that I decided that I need another so I ordered a third box. When my car comes back I'll take my wife's one and she can use a cable for now, until the third arrives and hopefully there are improvements for her experience.

That might be caused by wifi scanning. I had a similar problem using AA Gateway and using Tasker to disable Wifi and BT scanning resolved it.

 

[JohnnyCanuck]

@JohnnyCanuck has a specific problem that the developers want to investigate using the debug logs. He alone was sent the 1.1.0 firmware because the 1.0.0 firmware has a problem with sending the debug logs.

The rest of you will probably see 1.2.x as your first firmware update.

LeRoy

That's correct. The logs didn't actually send (but they did compile) but everything is working fine now anyway.

 

[Genebaby]

That might be caused by wifi scanning. I had a similar problem using AA Gateway and using Tasker to disable Wifi and BT scanning resolved it.

That sounds interesting. We are both on Galaxy S20 series phones. On mine I have nearby devices scanning disabled. I can't find anything else that might be related to that?

 

[osm0sis]

That might be caused by wifi scanning. I had a similar problem using AA Gateway and using Tasker to disable Wifi and BT scanning resolved it.

AAWireless could probably use the "Change system settings" permission to automate this itself if it's a widespread issue.

 

[JohnnyCanuck]

Here was the Tasker task I used to disable BT and WiFI scanning:

HUR
A1: Custom Setting [ Type:Global Name:ble_scan_always_enabled Value:0 Use Root:Off Read Setting To: ]
A2: Custom Setting [ Type:Global Name:wifi_scan_always_enabled Value:0 Use Root:Off Read Setting To: ]
A3: WiFi Net [ Action:Disconnect Force:Off Report Failure:Off ]

The exit task to re-enable is pretty much the same with just the value changed:

HUR Restore
A1: Custom Setting [ Type:Global Name:ble_scan_always_enabled Value:1 Use Root:Off Read Setting To: ]
A2: Custom Setting [ Type:Global Name:wifi_scan_always_enabled Value:1 Use Root:Off Read Setting To: ]

 

[drpotts]

GMC Yukon 2017. Samsung s20
MTP mode the device never connects to the car. Car comes up with a android auto standard driving warning as if phone was plugged in hit continue on the message the. It just shows projection on the infoscreen I stead of android auto. Mtp force/retry it just keeps cycling. Direct the phone is stuck trying to find android auto.

 

[Genebaby]

Is there any info on the new modes in the new version of the App?

 

[tallleroy]

@Emil Borconi created those modes while trying to get some reluctant head units to cooperate. He will be the best one to describe the new modes.

From my standpoint, if your head unit is not working well with AAWireless, try out the other USB modes. One of them may be just what your phone / head unit needs for success.

LeRoy

 

[JohnnyCanuck]

Used the DPI setting to get split screen this morning. How cool is that? I don't think I'll stay with it because my screen is fairly small, but I'll see how I like it after a few days.

 

[mapinkerton]

Used the DPI setting to get split screen this morning. How cool is that? I don't think I'll stay with it because my screen is fairly small, but I'll see how I like it after a few days.

I like split screen on my 7" display, but it maybe a bit of an acquired taste. My wife prefers the normal screen with larger fonts in her car and may even go the opposite way to make it easier to read.

If my screen was any smaller or farther away or if my eyesight wasn't as good, it would not work for me. As it is, the split screen is just about perfect and it's nice to have options.

 

[JohnnyCanuck]

I like split screen on my 7" display, but it maybe a bit of an acquired taste. My wife prefers the normal screen with larger fonts in her car and may even go the opposite way to make it easier to read.

If my screen was any smaller or farther away or if my eyesight wasn't as good, it would not work for me. As it is, the split screen is just about perfect and it's nice to have options.

My screen is 7" as well. Out of curiousity, what DPI did you use? I have it at 103.

 

[mapinkerton]

My screen is 7" as well. Out of curiousity, what DPI did you use? I have it at 103.

I have been using 100 on my Miata, but after a little trial and error, it looks like <=103 is the magic threshold to force widescreen on mine also.

 

[limited73]

Anyone been able to get this to work on a Nissan yet? I've tried all the modes, several cables, all the little "tips" on the Indiegogo...nothing

 

[stuartrue]

Success setting this up on my 2017 e-Golf with two Pixel 4a phones. I had to enable Direct Mode and Passthrough, otherwise it took about 90 seconds for everything to connect and work. Once configured properly, it's really fast - maybe 10 seconds. Consistent too. Great job developers!

One issue I have is related to using multiple phones with the device. The connection range is too good! If my wife gets in the car in our garage, my phone will connect (since I last used it) even though I'm in the house. And it doesn't gracefully drop the connection when she drives away. The screen freezes when the car is too far from the phone, and it won't connect to the phone in the car right away. Sometimes it'll reset after a few minutes and connect to the phone in the car, but I've had it go 20+ minutes before I gave up and manually unplugged/replugged it.

My preference would be for the device to connect to the "closer" device. That is, if it can detect which phone has the stronger signal, use that one. Failing that, I would like to see it reset more quickly after going out of range. It's a real usability problem since we alternate use of the car a lot. Most of the time the device is connecting to a phone pretty far away which won't be coming with it. Not ideal. Thanks!

 

[mc01319]

Anyone been able to get this to work on a Nissan yet? I've tried all the modes, several cables, all the little "tips" on the Indiegogo...nothing

Same here with Nissan Qashqai. Lets hope that the new firmware solves this situation.

 

[Genebaby]

@Emil Borconi created those modes while trying to get some reluctant head units to cooperate. He will be the best one to describe the new modes.

From my standpoint, if your head unit is not working well with AAWireless, try out the other USB modes. One of them may be just what your phone / head unit needs for success.

LeRoy

Thanks, some idea on the scenarios he was creating them for would be interesting.

 

[Genebaby]

Success setting this up on my 2017 e-Golf with two Pixel 4a phones. I had to enable Direct Mode and Passthrough, otherwise it took about 90 seconds for everything to connect and work. Once configured properly, it's really fast - maybe 10 seconds. Consistent too. Great job developers!

One issue I have is related to using multiple phones with the device. The connection range is too good! If my wife gets in the car in our garage, my phone will connect (since I last used it) even though I'm in the house. And it doesn't gracefully drop the connection when she drives away. The screen freezes when the car is too far from the phone, and it won't connect to the phone in the car right away. Sometimes it'll reset after a few minutes and connect to the phone in the car, but I've had it go 20+ minutes before I gave up and manually unplugged/replugged it.

My preference would be for the device to connect to the "closer" device. That is, if it can detect which phone has the stronger signal, use that one. Failing that, I would like to see it reset more quickly after going out of range. It's a real usability problem since we alternate use of the car a lot. Most of the time the device is connecting to a phone pretty far away which won't be coming with it. Not ideal. Thanks!

I do wonder how OEM wireless units handle these and other scenarios, when the cable is out of the equation. With the cable the issue of car sharing didn't matter, but wireless is the way going forward with many new cars and all of those aftermarket decks.

 

[Genebaby]

Something interesting I noticed with the App. I moved my wife's AAW box from her Mitsubishi my GTI as I had moved my unit to our Polo, that is back on the road for a bit.

After a rocky start of taking a long time to bring up the AA screen it's now quite fast in the Polo. I was trying to enable the audio timestamp adjustment, which I hadn't tried yet but it wouldn't save the config.

When I setup the box from my wife's car I enabled the timestamp successfully and then I noticed that the same settings were applied when I was connecting to the other box in the Polo.

This is not a big issue, as they are both VAG cars and the same setup is probably fine, but what if you have another car that doesn't like a certain setup, like when I get my third box and put it back in the Mitsubishi?

Until I saw this I did assume that each individual box had it's own settings, but it seems the app applies the one setup to all the boxes it has in it's list. Could it be made that each box has unique settings? It would also be cool to rename the units.