yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] CDATP:
Just found out about this project. I'm very interested in trying to make this work, but 273 pages is a lot to read through. Could anyone provide me the most up to date info to answer the following questions:

1. What slave should I buy?

- All my old phones have horrendously long boot times, and I drive infrequently enough that no phone could survive on battery power, so I'm looking for something that boots up fast

- MK809 V seems like it was the best option at one point in time, is it still? The only place I can find it for sale is aliexpress.com which has >1 month shipping time, but I can wait if it's the most reliable and fastest responding slave

- I am definitely willing to root if it will help, but instructions on how to do so would be appreciated

2. What steps do I need to take to install and get this working?

- I've seen references to HUR vs. AAGateway apps but don't understand the differences

- It seems like every combination of master/slave/vehicle is different in terms of settings one must enable

- Any special apps I need to install, possibly after rooting?

3. Is there a wiki somewhere for this project?

- It seems like there is a LOT of information on this thread, much of it possibly outdated, and perhaps an organized place to keep the latest info/instructions would be useful if it doesn't exist already

My phone (master): Moto Z4 unrooted, but I would be willing to root if necessary

My car: 2020 Hyundai Kona SEL Plus (7 inch screen without navigation)

I understand Hyundai vehicles apparently have some issues, but these may or may not have been solved?

Thanks for any and all help!
[Paid Software Announcement and Discussion] Khonji:
[MENTION=842765]Emil Borconi[/MENTION]

Ok. I did test with PC and i have scenerio like below:

1. Connecting slave to PC - Slave is recognized by PC as a phone and i can access storeage

2. Slave turning on BT and starts hotspot

3. Master runs WiFi Launcher, connecting to HUR network, starts AA

4. after few seconds Master closes AA and beack to its main screen (even from any app)

5. after few more seconds slave turning off BT and closing hotspot

What can be couse of this bechavior an how can i solve it? Runign AAGW in non root mode didn't help :confused:

P.S. Slave runs on Android 9 and Master runs on Android 10
[Paid Software Announcement and Discussion] paul1035:
I don't think you need to worry about rooting your master as most people with success didn't need to do that. AAGateway is an app that launches activities, HUR is the name of the hotspot that you'd create as part of this setup. For recommendations, I am too new to this project to know what's best, but I've had luck running Lineage OS 16 rooted on my slave device for having success. Unfortunately I've only had success once and haven't been able to reproduce it, so I'm not the best person to say much more lol.
[Paid Software Announcement and Discussion] sabaatworld:
I'm trying to do the projection launch using tasker but it stopped working recently after upgrading Android Auto recently.

A1: Send Intent

Action:com.google.android.projection.gearhead.START_WIRELESS_PROJECTION

Cat: Default Mime Type:

Extra:PARAM_HOST_ADDRESS:192.168.1.101

Extra:PARAM_SERVICE_PORT:5288

Package:com.google.android.projection.gearhead

Class:com.google.android.apps.auto.wireless.setup.service.impl.WirelessStartupActivity Target:Activity

Any ideas how to get it working with latest Android Auto?
[Paid Software Announcement and Discussion] shmykelsa:
That's not a valid IP address
[Paid Software Announcement and Discussion] pavichokche:
I have a Hyundai too (2015 Sonata) and here is what I do that works:

MASTER - No root Samsung S9, Install NOTHING. Just configure the hostpot and start the head unit server

SLAVE - Rooted Samsung S6, Install AAGW 2.0.6, do NOT make system app, do NOT set up bluetooth or anything. Just start the app, configure the wifi connection to the hotspot.

This took some attempts to get to work consistenly. Mainly, I needed to uninstall and re-install the app each time it didn't work as expected. Eventually it did, however, and it's consistent now.
[Paid Software Announcement and Discussion] sabaatworld:
Sorry. That's just in this post though. On tasker, its fine.
[Paid Software Announcement and Discussion] Starky09:
Hi there,

I'm an owner of a Ceed Sportswagon 2019 too, maybe you can help me out. I use an Oneplus 7 Pro as Master and tried a Oneplus 3T (rooted with Stock and LineageOS) and a Galaxy S6 Edge (rooted with Stock)but none of them are working for me. With the Oneplus 3T my Headunit sometimes recognizes an Android Auto device but then nothing's happening and the AA symbol in the bottom right corner disappears.

Did you install the AAGateway app on your slave as a system app? You also said that you connected without tethering. Does it mean you connect the slave to the master's hotspot?

I'm really frustrated at the moment because everything I've tried didn't work, so I'd appreciate any kind of help. Thanks in advance!
[Paid Software Announcement and Discussion] Emil Borconi:
Sorry I just realised that I've forgot an IP address hardcoded in the app :(

Going to push out a release today, this affected anyone tethering from master.
[Paid Software Announcement and Discussion] grimloktt:
Thank you for the hard work on this and continued effort. We're all excited for its use!!!
[Paid Software Announcement and Discussion] IlD4nX:
Hi there,

I think you misunderstood what he wrote:

- Slave AAGW installed as NOT system app, with no specific setting (except the selection of the hotspot from master).

- Master no installation needed, only configuration of hotspot (which the slave must connect to) and Head unit started.

I will test this setup later on and let you know if it works on my OP7 Pro (master stock OOS Android 10 not rooted) with an OP5 (slave, stock OOS Android 10 rooted) on an Alfa Romeo Giulia 2019.
[Paid Software Announcement and Discussion] Starky09:
Okay, thanks. Looking forward to it!
[Paid Software Announcement and Discussion] IlD4nX:
Ok, oneplus phones have some stability issue but after a couple of plug/unplug I made it work.

After 15 minutes sadly AA crashed and I had to reboot both phones... But I wasn't able to make it work again. It's the right path to follow, but I have to test it better.
[Paid Software Announcement and Discussion] -Loom-:
After several (about 100 different) attempts without luck I would really like to understand what is happening behind the scenes of this app.

Especially when there is everything done manually on the master.

So, on the master I actived the Android Auto headunit server and I am tethering to slave. How does the slave know that the master is ready for takeover? What role does bluetooth play in all of this?

I would be glad if Email could shine some light into the technical aspects.
[Paid Software Announcement and Discussion] mcilroym:
I've been playing with this over the last few months in my spare time and think I have found my problem. The slave IP address changes every time it is cycled on off which happens a few times during connection. I found a solution to this if you have a terminal emulator, root access and be have pre android pie installed. running wifi launcher 2.1 and aagateway 2.1. I can't post the link I found this here Google the following "How can I permanently assign a static IP address to Wi-Fi or USB tether clients?" look here for more context.

/etc/dnsmasq.conf create this file with this contents on your SLAVE I used Root Explorer.

dhcp-host = 11.22.33.44.55.66,set:S20, 192.168.43.10

dhcp-option=tag:S20,option:router

server=1.1.1.1

fill in your master mac address and a tag if you want

~# su chown 0.0 /etc/dnsmasq.conf

~# su chmod 0644 /etc/dnsmasq.conf

~# su chcon u:object_r:system_file:s0 /etc/dnsmasq.conf

~# su

~# supolicy "allow dnsmasq system_file file { read getattr open }"

~# supolicy "allow dnsmasq system_file dir { search }"

now your slave and master will always have the same IP address

also when connecting to slaves wifi HUR I had to ignore the popup to stay connected to wifi with no internet "press the back button to ignore". Otherwise I couldn't get mobile data to work while connected to wifi. Hope it helps someone.
[Paid Software Announcement and Discussion] Starky09:
Thanks for the update. I've tried it again today but no luck unfortunately.
[Paid Software Announcement and Discussion] IlD4nX:
Don't know because I can't test it in these days (Monday next week I will) but today I got an AA update... Maybe it solves AA crashes!

Also I'm trying to figure out if I can do something with tasker to start the hotspot and headunit. Path seems to be better than before (at least I was able to see AA again on my car screen)
[Paid Software Announcement and Discussion] grimloktt:
With updates, mine still isn't working
[Paid Software Announcement and Discussion] NaVeElan:
Hi, I was excited to see this project and decided to give it a shot. However, I am stuck at "Waiting for master to connect screen"

Here is a summary what I have done:

Master is Pixel 4 XL and Slave is Pixel 2 XL. Running both the devices in non-root mode.

The splashscreen is visible on the car, soon after which I see the slave turns on the hotspot. Master connects to the slave's hotspot and I see the WiFi Launcher notification on the master. However, the android auto does not start in the master. The car screen is stuck in "Waiting for the master to connect" screen. Is there anything I could do to fix this issue? I tried manual tethering from the Master with the head unit server started. That did not help either.
[Paid Software Announcement and Discussion] Emil Borconi:
Updated the app, removed the burned in IP and fixed a few more crashes, bugs.

I've also moved the app to the stable channel as I feel confident enough that it's about the best I can pull out of the app.

On the device, connection is still not stable yet, we are going to refacto the whole code as it was based on OpenAuto and AASDK and the code is really difficult to debug, so it was decided to scrap that and use a code similar to the Android version I'm using now in the app. The good part is that BT, USB ACCESSORY and WiFI all works which is good. I've been also doing a lot of legwork on how global shipping can be achieved what hoops&hooks have to be completed etc. Currently in negotiation with 3 warehouse and dropshipping companies about the possibilities and prices.
[Paid Software Announcement and Discussion] grimloktt:
Which application did you update? Guessing the AA Gateway?
[Paid Software Announcement and Discussion] Emil Borconi:
Yes AAGW
[Paid Software Announcement and Discussion] saspo59:
Did wifi launcher will be updated accordingly or to use the new aag with wifi launcher 2.1
[Paid Software Announcement and Discussion] Emil Borconi:
Use the new aagw with the same WiFi Launcher.
[Paid Software Announcement and Discussion] shmykelsa:
I've just updated AAGW from 2.0 to 2.2.

Hopefully it will work (can't test right now). I had many problems with 2.0.8, and found out that 2.0 was basically the only one working properly.

I see with 2.2 the change of DPI is possible even with root, which is amazing news for me.

Now I have only one request: could it be possible to add more than one master BT?

Because with 2.0 basically every phone I installed WiFi Launcher on would connect to HUR and everything was good, but now if I want to let more than one phone connect to Android Auto Wirellesly I have to set the master BT every time.
[Paid Software Announcement and Discussion] Emil Borconi:
Bit more complicated....
[Paid Software Announcement and Discussion] saspo59:
Sorry but there is no wifi launcher 2.2 at xda lab are u going to push ver 2.2
[Paid Software Announcement and Discussion] Emil Borconi:
No use the same version like before.... no update of WiFi Launcher is needed.
[Paid Software Announcement and Discussion] shmykelsa:
Could it be that AAGateway can create a whitelist of BT Mac addresses? Cause in the worst scenario that more than one phone gets in car just one of them gets connected to car head unit so just one of them launches WiFi Launcher, right?
[Paid Software Announcement and Discussion] WilcoSnel:
Anyone else getting the notification to "park the car first. If already parked, put on parking brake"??? I did but still the same Android auto error. After some googling found it might be the car's infotainment, but when using the cable everything works normally. Could there be some flag the app is not setting correctly?
[Paid Software Announcement and Discussion] Humaid.r:
Master is running Pie or above and slave is tethering:

Running in root mode: (No)

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

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: (Yes)

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

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

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

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

I plugged the slave to the car, and I get the notification to choose either AAGateway or Android Auto, I chose AAGateway and set it to always.

However, nothing after that happens.
[Paid Software Announcement and Discussion] GingeyBook:
AAGateway setup help

Master is running Pie or above and slave is tethering:

Running in root mode: Yes, slave only

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

On the master did you select the cars BT in the Wifi Launcher app?: Yes, also tried with only slave bt connected

When the master connected to the car's BT did the Wifi launcher app started up?: Yes, connected to slave hotspot

Did the master connected to the slaves hotspot?: Yes

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

Master is Pixel 4xl, Slave is Pixel 2xl both on April security patch
[Paid Software Announcement and Discussion] krlosmt:
Master is running Pie or above and slave is tethering:

Running in root mode: No

If running in non-root mode, is the splashscreen visible on the car: Yes (It says: "AAwifiGateway - Waiting for master to connect")

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: Yes

On the master did you select the cars BT in the Wifi Launcher app?: Yes (But, do it has to be the Car BT or Slave BT?)

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

The master ask more than three times if give it permission for using wifi launcher.

Master : Xiaomi Redmi Note 8 Pro (Non rooted)

Slave: huawei Tag-l13 (Non rooted)
[Paid Software Announcement and Discussion] IlD4nX:
Wow, it's a couple of days that I installed both latest AAGW and Wifi Launcher and as soon as I turn on my car, it connects automatically, meaning that it seems to work properly ! Honestly the apps (and [MENTION=842765]Emil Borconi[/MENTION] terrific work) did huge steps ahead !

Sadly, after a while, sometimes few minutes sometimes more, something crash and I'm loosing AA: I'm not sure and I'm not able to check it, but I believe it's the launcher on the master because it drops the bluetooth connection on my car.

Anyone has any suggestion on it ?
[Paid Software Announcement and Discussion] pavichokche:
Try not using the WiFi launcher at all. Just install AAGW on your slave and manually turn on the hotspot on the master then see if it's more stable.
[Paid Software Announcement and Discussion] IlD4nX:
Yeah I did it, but there also, for some reason it crash (but I don't understand if it's a matter of AA or AAGW); in addition it work once every 4 or 5 times !

Anyway, I would prefer to make it work using slave as hotspot...
[Paid Software Announcement and Discussion] propi62:
Same for me. 2.2 connects much faster and everytime. But i also have this aa crashes, sometimes after 5 minutes and sometimes it works for 1.5 hours. If i play a long podcast i think its more stable thene with short spotify tracks.

However, Version 2.2 is very good!

Im using rooted mode with thethering on slave and thenwifi launcher on the master.
[Paid Software Announcement and Discussion] -Loom-:
After a lot of trial and error and much help from Emil I finally got it running.

Headunit: VAG MIB 2.5 (Discover Media - Volkswagen Golf 7 - Build 2019)

Slave:

1. MK809V_4K Android 5.1 (comes rooted out of the box)

2. OnePlus One - LineageOS 16 (rooted)

Master:

OnePlus 5T (rooted)

So here are some things I learned down the road:

Using the MK809V: Make sure you get the right one, as there are several MK809 models out there. Some of them have the wrong description, some of them have wrong pictures. I got the one with the green android robot. Absolutely make sure you have one with Android 5.1 and Rockchip RK3229. Don't get the one with the red antenna slider.

I had some problems with switching USB mode, but it might be a loose USB OTG port. With a fine plyer I narrowed it down a litle, also use some electronic component cleaner. Hope it lasts. For the settings: Nothing special, set up bluetooth, Super SU to always grant root rights, set storage to PTP. Installed AAGW as a system app, checked TV stick, enabled tethering. Finally I used L Speed to beef up the performance a little. Don't know if it's neccesary, but for some other users it helped with audio drop-outs.

Using the OnePlus One: This was more complicated. Since it runs Android Pie, you will have to set up the hotspot manually. I initially chose 5Ghz hotspot, but it switched back to 2,4Mhz. Seems there is a regional restriction using a 5 Ghz hotspot. Found several discussions about this. So, 2,4Ghz then.

Then, you need 'developer settings' to be able to set the USB mode. I chose 'storage mode' here. When used 'charging', I never got any connection to the headunit.

I think it's a good idea to start the slave fresh every time. So I used Macrodroid to power down the slave 1 minute after charging power drops. To power it on when charging starts was a little more complicated. Here is a great how-to: https://h4des.org/blog/index.php?/archives/358-Android-LineageOS-15.1-and-16-Auto-Boot-on-Charging.html. This works great, but booting takes about 1 minute this way, but you get a fresh device every start and don't consume battery when not in use.

Using the master: I decided not to use WifiLauncher as it gave me some headaches. Instead I used Macrodroid to have more control. Here, the crucial part was that I got a different Wifi Gateway IP adress every time the slaves hotspot start. This is a security thing in later android versions. So, I found a nice Macrodroid macro, that starts AA headunit server with the correct IP adress. I set up a 30 seconds pause until this macro starts to adjust to the MK809V getting ready after the hotspot starts.

Good luck with your setup!
[Paid Software Announcement and Discussion] IlD4nX:
For testing purpose tomorrow I will try to remove battery optimization on both Master and Slave...

Edit "the day after": nope, battery optimization doesn't impact at all: still after some minutes it crash (no idea if master or slave). I still have doubts on some apps, such as VNC and TuneIn: I will try after to freeze those apps.

Edit 2: it's not a matter of app... I'm starting to think about usb issue which is disconnecting.
[Paid Software Announcement and Discussion] shmykelsa:
So maybe I am unfortunate but so far AAGW 2.2 is not functional at all.

My master is OnePlus 6T running an AOSP based ROM (Android 10)

My slave is LG V10 running stock Android 7.0

The one and only configuration that works without any hassle is with slave running AAGW 2.0, start tethering option OFF, and I programmed the master so that upon Bluetooth connection with car, it starts AA headunit server and tethering.

The other way around does not work. If I start tethering on slave and use WiFi launcher, nothing happens and the phone is not recognized as a USB device from the car.

AAGW 2.2 will not start tethering on the slave under any circumstance even if start tethering option is active. If I try to recreate the "2.0" setup, so tethering on master and wifi connection on slave, my slave will just not act as an USB device and car won't recognize it at all. Same goes with start tethering and WiFi launcher on master.
[Paid Software Announcement and Discussion] Emil Borconi:
Sorry guys, today as setting up my new phone (OP8 PRO :D) I realised the WiFi Launcher which I published was the wrong one, so I've updated the app now, might help with some of the disconnections you are facing.

If you do get a disconnect after 4-5 minutes (or any other interval at random stages) please do email me on borconie@gmail.com for support and with a bug report from both devices, I will like to see what's causing this, can be plenty of reasons.

AA 5.3 poses some major changes (nothing AAGW related) but it seems that they broke my other apps notification system, where I was using showing users heads up notifications.

I don't have any more news to share with you about the Linux version of the board yet, as soon as I do I will update you.
[Paid Software Announcement and Discussion] IlD4nX:
Good to know [MENTION=842765]Emil Borconi[/MENTION], I updated the Launcher and removed CarNotifier: I will test tomorrow morning the system with these small changes. In case I will try to grab a logcat and let you know.

Thank you for your work !

Edit: it seems that the new version break something... The previous one at least gave some life signals. With this update nothing.

Edit2: stupid me I was blocking it because of VPN

Edit2: it's driving me nuts... It's not the VPN the issue. It does not connect like the "wrong launcher"...
[Paid Software Announcement and Discussion] LLStarks:
I need to go back to master hotspot and try a few things.
[Paid Software Announcement and Discussion] Humaid.r:
I updated the WiFi launcher. However, still not able to get it working.

I guess the Slave device needs to be rooted, and I don't want to do that.
[Paid Software Announcement and Discussion] LLStarks:
If I had previous versions of the launcher, I could try bisecting what I consider to be a regression in functionality. I only have the older slave apps to play with and swapping them out hasn't mattered.
[Paid Software Announcement and Discussion] singcheng:
If I get MK809V, I still have to get a HDMI to USB converter, right? Since the car comes with a USB port rather than HDMI port like the TV.
[Paid Software Announcement and Discussion] Anonym.tsk:
Hi. I have Kia with headset based on Android 4 with builtin Android Auto support (only wired). Is it possible to install AAGateway immediately on headset and not to use slave device?
[Paid Software Announcement and Discussion] -Loom-:
No, you need the HDMI only to set it up using your Monitor / TV.

Just be aware that the device has actually three USB ports. 1. DC: just for powering, 2. USB OTG: for powering and data connection and 3. HOST: for connecting other USB peripherals like a keyboard.

Inside the car you just need the USB OTG port, nothing more. That's the simple beauty of this solution.