DIY Wireless Android Auto

I will post up pics or a video in a bit, but I have completed a DIY install of wireless android auto in my 2018 RS3. This should work on any FL 8V and probably a number of other models as well.

You need three things: an old android phone you don't mind rooting and using as a "slave"; a $1 app from XDA labs (https://labs.xda-developers.com/store/app/uk.co.borconi.emil.aagateway; and a "master" android phone that supports wireless AA (eg. S10, Note 10, Pixel). My actual phone is a Pixel 3 which supports AA wireless.

Optional: Tasker, AutoInput, Secure Settings.

Once you have the app, you need to contact the developer by email for his latest test version (1.1) and he'll provide you with the .apk.

Steps:

1. Root your "slave" phone. I am using a first gen Moto Z and running AEX as my ROM (Oreo). You need only one app installed on the slave: AA Gateway.
   
2. Install the AA Gateway app on the Master as well.
3. Start a hotspot on your master and connect the slave to the hotspot.
4. Start AA on the master in Head Unit Server mode.
5. Start the AA Gateway app on the Slave and in its settings set the "Phone WiFi SSID" to the hotspot SSID.
6. Start the AA Gateway app on the Master.
7. Connect the Slave to your USB port in your car. When the Slave pops with a prompt as to what app to run select AA Gateway "Always".
8. You will then get the prompts on your Master for AA permissions.
9. Once done, you have wireless Android Auto ... fully functioning.

In real life, I find a couple of things. The first is that I have to exit to the MMI menu and go back into Android Auto when I start up the car (I get a warning about checking my phone ... backing out and back clears it). And, the Slave requires reboots every few times.

To automate a fair bit of the process, I use Tasker and AutoInput. I have used Tasker with AutoInput to create a one touch app on the master to start a hotspot and put my phone into Head Unit Server mode. I have a one touch app to stop both. I prefer to use one touch apps than leave Tasker active and waiting for a state change, but the tasks would be identical. I can post the project files for these if anyone is interested.

To automate the reboot process on the slave (as well as make sure that it always connects to the master) I use Tasker and Secure Settings. Tasker is set to automatically connect to the hotspot on USB power up. Tasker is also set to reboot the slave 5 minutes after USB power down. This required Secure Settings and root.

If a dongle worked, I would definitely go that way, but I have not seen any that convert wired AA to wireless AA on a non-Android HU. That CPLAY2air dongle that's picture claims to work for wireless CP but their website doesn't say a word about wireless AA.

I kind of missed one point in my write-up. The whole idea is that I leave the slave phone pretty much permanently hidden in my car (I have it stashed under the front seat with the wire to the front USB port hidden under the centre console trim). It means I can leave my phone in my pocket or throw it on a wireless charger when I'm in the car. Once set up it's intended to be more (not less) convenient than a cable.



I've also rigged up a wireless charger in the armrest cubby under the mat so I can just drop my phone in there to charge (sorry about the bad pics).

It is a bit technical, fair enough. I will note that I am not really that technical ... just good at following instructions from XDA.

calw123 said:

Can you give us more info on this as I have the same or a very very similar dongle and I can't get it to work at all for android auto

Click to expand...

I have shifted to the one of the newer wireless AA dongles as well. I am using the AAWireless (https://www.cpeb.it/) or you can still get it from Indiegogo as well. It works pretty much flawlessly 98% of the time. Once in a very rare while I have to power cycle it (just by unplugging the USB connector for a couple of seconds).