[Paid Software Announcement and Discussion] ScrapMaker:
Heyo, I'm curious how you got this working. I've only had VERY minor success when starting the AA headunit device manually. In this case on only get audio, but I can confirm it's going over WiFi.

aaaaahhh frustratingly the issue with video was having USB Debugging on. I just leave this enabled since I use it so much. After disabling that, I was able to get video working on both phones as master-vs-slave. Though I still could not ever get Wifi Launcher to work. Additionally, I'm getting much different behavior between the Alpha, Beta, and Stable releases for both apps.

Master: Pixel 4 XL (Rooted) currently on Android 11 Beta 3, but it's never worked on any version.

Slave: Samsung S9+, not rooted

- My goal is to have the Master provide the hotspot, but the slave app REALLY does not want you to do this. I have Tasker stuff set up to turn on a hotspot, etc, so I'm already set on that.

- When I connect the slave to the car, it turns OFF Wi-Fi (even when I have specified to not tether, and to use Master SSID.) It does turn on Bluetooth.

- When I unplug the slave, it turns OFF Bluetooth. This seems odd.

- The devices never attempt a real BT connection. I assume this is to trigger the master app to load up the AA wifi developer server. I can force this manually, but then I have to fiddle with internet sharing, etc, and it gets all wonky real quick. Feels like BT is not a good mechanism for this.

* I have the master BT selection set to the slave phone, and I also have entered the master's BT MAC properly into the slave app.

- Regardless of what settings I use, the slave does put the banner on the car screen, IE waiting for master to connect.

- I've managed to make the master pop up the AA questionnaire stuff once, using the official method where the slave has its own hotspot, but after I answer a few questions, it opens up the Assistant, then ultimately fails, because the internet offered by the Slave is not good enough, and I can't force it onto any Wi-Fi.

It just feels like there should be a few more toggles/options that are more-clearly labeled. I would imagine MOST people would want to source the hotspot from their main phone, instead of having to find a SIM/hotspot contract for an old device. Is this the default use-case, or am I missing something obvious here?

I really don't want to use the slave device to create the hotspot, but since that doesn't work either, I'll use this template:

Master is running Pie or above and slave is tethering:

Running in root mode: (Master=yes Slave=no)

If running in non-root mode, is the splashscreen visible on the car: (Yes)

If running in non-root mode, did you set the masters BT inside AAGW app?: (Yes)

Did the slave actually turned on the hotspot on the slave: (No)

On the master did you select the slaves BT in the Wifi Launcher app?: (Yes)

When the master connected to the car's BT did the Wifi launcher app started up?: (Yes)

Did the master connected to the slaves hotspot?: (No)

Did the AA icon appeared on the master at all (in the notification bar)?: (No)

Even when I start the HU server manually and get audio (no video,) the quality is much lower. I'd say the comparison is about 320kbps to 128kbps MP3. I can easily switch the cable across to the master and immediately hear the massive quality increase. Do you think this will improve with dedicated hardware, or is this simply a limitation of wireless AA? It's very noticeable.