yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] fma965:
So i think i have a bit of an issue if it's a short trip, I don't know what exactly causes it but...

Ford cars keep power to the USB port and lighter socket for about 20 minutes which i think might be related to my issue.

When i go to say the local shop and am less than 15 minutes when i get back in the car the AA connection doesn't seem to come back until i unplug and plug the slave phone, is this issue already known? i read the previous posts but i'm not sure thats about the same issue.

It seems if i am gone for say ~40 minutes (my lunch break for example) the issue doesn't happen which would make sense as the USB power would be killed after ~30 by the car computer to save power when the car ignition is not on.

Is there a solution to this?
[Paid Software Announcement and Discussion] JKLIMES1:
my 2 cent

just wanted to chime in here in case it helps with troubleshooting and let you know my experience. So far not having much success getting either scenario to work, at least with the newly updated AAGW/ Launcher for HUR.

S10+ - master (not rooted)

LG V30 - slave (not rooted)

2018 Honda Accord

case 1- Has been a no-go for me. Have followed the step as instructed in the OP and i cant get past the splash screen on the car radio saying "waiting for master to connect". Master is connected to slaves hotspot but still only splash screen shows. i notice that Launcher for HUR will only sometimes get activated and show in the notification panel when the master connects to the radio BT. Also notice that if i toggle the BT off on the master, the splash screen will disappear on the car radio. if toggled back on the splash screen will re-appear. Cant get passed the splash screen even tho the master does connect with the slave as well as head-units BT. I have tried also manually starting the Head Unit Server in AA, But still no luck with case-1. This might have something to do with the fact that my slave device not rooted, not sure??

case 3- using the updated AAGW / Launcher for HUR, i can maybe get it to work once, on the first try only. otherwise i have to either restart both devices or most usually do a fresh reinstall of the apps. Most times however still all i get is the splash screen. However with the previous builds of the apps, i was able to get it to work all the time, with one caveat; Head-unit server MUST be manually activated with-in AA on the master, and the slave MUST be connected to the masters hotspot prior to the car radio trying to load the AA app which is usually within about 5-10 sec of the car being started. If the radio tries to load AA before the connection between the devices is met, I will not be able to use AA until I do a re-boot of both devices and first make sure that the slave is connected to the masters hotspot. As long as the slave and master are connected before the car attempts to fire up AA, this method always works. However its not very convenient at the moment since my slave does not always connect to the masters hotspot right away once i'm in the car, sometimes it can take a minute or two. So its either sit in the car and dont turn it on until the devices connect, or not have the slave plugged into the usb when i turn the car on. That way the car is not trying to fire up AA right away. once the devices connect to each other i can then plug in the usb from the slave and AA will load right away....but as i mentioned neither is a good option as i want to just keep the slave plugged in to the usb all the time and be able to just get in the car and turn it on right away without any issues with AA loading.

seems like there has been some success with users out there lately so things are looking promising

Emil, just wanted to give you props on your customer support as well. I wish other devs were as helpful as you have been.
[Paid Software Announcement and Discussion] Emil Borconi:
That will be a problem as the trigger mechanism on the slave is the power source so it your car keeps the power not sure what you can do... I'm not even sure on what can I build in to make it reset...
[Paid Software Announcement and Discussion] Emil Borconi:
Something is not right, if it worked with previous beta it should with this one as well. If you are using non-root mode make sure that the master BT is selected on the slave. Set the slave to tethering. When you plug in the slave the hotspot will only be turned on on the slave after the Splash screen appears on the car. Now on the phone make sure you have the launcher app installed and the car's BT selected. Watch that it actually start the launcher app on the master when the master connects to the car's BT. If it doesn't start look for any battery optimization and turn it off for the launcher app.when the launcher app starts wait and see that it actually connects to HUR WiFi. Make sure that the launcher app has location permission set to always.
[Paid Software Announcement and Discussion] JKLIMES1:
Actually all of what you mentioned was done already. It all connects just as you mentioned and still cant get past the splash screen. Also the AAGW app does not give me a root or noon root option anywhere in the app. Optimization turned off and the launcher app does fire up when connected to the cars BT. Master also connects to the HUR hotspot on the slave. But again a no go getting past the splash screen
[Paid Software Announcement and Discussion] martin.armstrong:
[MENTION=842765]Emil Borconi[/MENTION]

in further testing this morning I found the following:

1. with using hotspot on slave, when I unplug and plug in the slave from the car after I have already had AA running, even if I make sure that wifi launcher is running either before I unplug the slave or before I plug in the slave again, the AA connection is still not restored once the master is connected to the slave wifi. Only toggling the master BT results in an AA connection again.

2. with using hotspot on the master, when I unplug and plug in the slave from the car after I have already had AA running, AA restarts every time.

3. the triggering in Automate on a wifi connection is indeed also dependant on mobile data being off.
[Paid Software Announcement and Discussion] propi62:
I have another problem. My android auto crashes whene i skip some spotify songs. (Buffer problem?)
[Paid Software Announcement and Discussion] Marshy33:
I've also has had this happen.

I have found if I let Spotify play without fast forwarding or only a few fast forwards its fine, but as soon as fast forward several tracks, all sorts of weird things start happening from sound cutting out to the wrong song playing.

Emil said he was going to check some settings in the app, but has said hes busy this weekend.
[Paid Software Announcement and Discussion] IlD4nX:
I tried but if hotspot starts after Bluetooth, AA doesn't start... I moved the hotspot in the quick toggles and it's ok by now.
[Paid Software Announcement and Discussion] Matt_black_90:
Ok that's weird, for me it have worked every time so far.
[Paid Software Announcement and Discussion] JohnnyCanuck:
For those with audio dropout issues, I think I may have found a solution. This assumes a rooted slave, but I edited the build.prop file to include:

I spent about 20 minutes in the car listening to Spotify with only a couple of very minor dropouts so I think I maybe onto something (the connection itself is plenty fast ... 5GHz with a link speed of 866MHz). I am not enough of an expert to figure out how to tweak these settings even more to increase the buffer, but if anyone has an idea ... happy to play with it.

I could be that the phone is just not ever going to be ideal as a slave, but I am hesitant to buy another cheap phone until Emil has a chance to let us know about his latest efforts with different TV sticks or Pi. But, I am close to a well functioning solution so if I can resolve the wifi issues through build.prop tweaks, that would be ideal.
[Paid Software Announcement and Discussion] JohnnyCanuck:
Still working down the road of build.prop type tweaks to resolve audio dropouts, but I am out of my element a bit. Found another well respected XDA app (L Speed) that seems to have a number of additional network performance tweaks beyond just buffer size. I will see if those fully resolve the wifi issues tomorrow and provide an update.
[Paid Software Announcement and Discussion] xanderharris86:
I'm trying to attempt Case 1 but the issue I'm having is that when I attempt to manually configure the hotspot on slave, it tells me I don't have a sim and can't activate a tether because of it. When I tried doing it through FoxFi, it gives me an error that "HUR" is too short of a ssid and it expects at least 8 characters. I tried Case 3 and it was just stuck at the waiting for master screen for a few minutes and I gave up on that. I would much prefer to do case 1 but I need a way to enable a wifi hotspot on my slave (s8+) without a sim card in it. Any suggestions?
[Paid Software Announcement and Discussion] martin.armstrong:
if your slave phone is rooted and if on the slave you did not select non ROOT mode and you select tethering, AAGateway will create the hotspot for you, even if manually on your phone you cannot create a hotspot because there is no sim. Edit: However, having read Emil's instructions again this may only be true if slave phone is older than android 8. You could always put in a sim temporarily in order to be able to create the hotspot manually and the AAGateway might be able to activate the hotspot without a simcard in it, even it is not routed.
[Paid Software Announcement and Discussion] Rag3:
[MENTION=224120]Emil[/MENTION]:

Just setting up everything (s3 mini as slave and s9 as master) to try tomorrow.

One point came up regarding the hotspot: I guess it would make sense to allow setting a custom password here. Using the same pw for all users might cause conflicts between users and certainly concerns me security wise.

Currently the only way I see to achieve this (without changes to both apps) would be tasker on slave to start tethering + not use the wifi launcher on the master but also tasker to initiate the connection.
[Paid Software Announcement and Discussion] martin.armstrong:
Quote: ust setting up everything (s3 mini as slave and s9 as master) to try tomorrow.

[MENTION=1192017]Rag3[/MENTION]

please post a message on this forum if you succeed with AA wireless with your S3 mini as slave. I could not get it to work with a rooted S3 mini as slave, only with a rooted motorola one did it work (Edit: and with an MK809V stick)
[Paid Software Announcement and Discussion] JohnnyCanuck:
Audio Dropouts - Potential Fix

Further to my posts yesterday looking at network settings to try and resolve the audio dropouts, I may have found the solution. I got a much improved result tweaking build.prop to increase the tcp buffers, but I was still getting enough dropouts to be annoying. I then went and looked at L Speed and used it to optimize all the network settings within the app. That got me more improvement, but not completely free of dropouts. I then went and optimized I/O and CPU settings for performance within L Speed and I think I might have solved the problem. 15 minutes of listening without a dropout. I will test on my commute tomorrow but this might be a solution worth exploring for others with dropout issues.

Because every case scenario is different, I am not making any guarantee this will solve anyone else's issues with dropouts, but it is worth exploring. Your slave has to be rooted for L Speed to work. My setup for reference:

Slave - Rooted Moto Z running Lineage 16.0 with GApps pico

Master - Samsung Note 10

Car - 2018 Audi RS3

AA Gateway Setup - latest beta installed as a system app on the slave but not set to start tethering. Using Tasker to start Hotspot and Head Unit Server on the Master (I cannot get WiFi Launcher to start Android Auto under any scenario).

L Speed main thread here: https://xdaforums.com/apps/l-speed/tweak-l-speed-v1-0-02-02-2015-t3020138

Note that I used the apk version of L Speed and did not install through Magisk (although I did root through Magisk). It is also no longer on the Play Store. I downloaded it from the links in this thread: https://xdaforums.com/apps/l-speed/l-speed-removed-play-store-t3966837
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=1192017]Rag3[/MENTION] - The reason for the same password is that the WifiLauncherForHUR needs to be able to set up the connection automatically on the phone, normally that should be a dummy netwrok no internet, and well (I would not leave personal information on the slave which stays in the car all the time anyway). That should be nothing more then an empty phone with one app on it.

[MENTION=2637038]JohnnyCanuck[/MENTION] - Thanks.

I though I will come into the office today for 1-2 hours to do some small tweaks, well it's almost midnight and I'm still in... Anyway I've pushed a new build, mainly focused on performance improvement for TCP, however during the testing I came across a bug(ish) on the connection side, where the connection was initialised, better said where the handshake was taking place between the slave and the master (non-root mode) so for those trying non-root mode and having no joy, should give this new version a go.

Also made a horrible video (excuse the quality and the mess in the office) it's mainly to see what performance should be expected, especially skipping songs in spottily since this had the most complains.

In the video the slave is a Pixel 2 XL and the master is my OnePlus 7 and it's using the 2.4Ghz Wifi (not the 5Ghz).

https://photos.app.goo.gl/6V8y38UWCRumknPp8
[Paid Software Announcement and Discussion] Marshy33:
Thanks for the update Emil! :) will be testing this out tomorrow.

I have downloaded, but every time I move it to a system app and then reboot it removes the app from my phone.
[Paid Software Announcement and Discussion] Emil Borconi:
If it's a phone leave it as it is no need to make it system (you can easily select use aagateway and always)
[Paid Software Announcement and Discussion] epsonix:
[MENTION=842765]Emil Borconi[/MENTION]

I've installed newer AAGW 2.0.5 (on LG Q6 not rooted Android 8), and tried today with newer AA (5.0) on my unrooteed LG G7 fit Android 9, car Alfa Romeo Giulia 2018 with last year infotainment firmware MV085...Still no luck, though it seemed to me that at least some crazy things like disabling WiFi did not took place this time.

On slave in case 1 way I had to enable Hotspot by hand (for some reason AAGW can't do it, where Automate can - but I have some special option added there some workaround for Android 7+ enabled in AUtomate to make it work (I used it with old 1.0Beta RC3 for whole last year) ), car connection was established, master blinked and connected to HUR hotspot (but it was saying Running... only), but no luck in getting AA on car screen. I also tried manually enable AA server just in case, but no help.

I tried also case 3, but similar, no luck.

I have a question, as there are some confusions. In instructions in post 1 you say to set to enable tethering if slave is A8.0+ and master is A9.0+, however in AAGW apk beside the setting it says enable only if phone is Pie (A9) - it is slave phone, do you mean slave phone or master phone for this setting. Another confusion is in master setup instrucitons:

"Master is running Android 8.0 or older

Enable start tethering (should work on most devices)"

no such setting in WiFi launcher for HUR, did you mean on AAGW on slave for this? please get instructions free of any confusions/bugs, it is not smooth to get it working as far, so we surelly do not need misunderstandings/wrong configs/guesses etc.

Also, could you clarify how to go without WiFi Launcher for HUR on master - I want to at least try by hand or use Automate - want to exclude possibility that the master apk is a problem. Without WiFi Launcher for HUR can I try case 1 and case 3 or it is only restricted to one of these?

What is Enable debugging option on AAGW?

I'll email you now with new debug report.

In 2-3 days I should receive MK809IV stick, so will try with it. can you maybe do bit more clear description on how to set it on stick from beginning - e.g. that I need to root it or install something first, or set some system settings specific way etc.
[Paid Software Announcement and Discussion] NYZack:
Very stupid little point, but I was having trouble with Case 1 and found that I had neglected to enable the "Start tethering" option on the slave. This setting was neatly off my AAGateway settings screen (no indication it was there), and I had to scroll the screen up to see it. I wonder if some people's tethering issues result from this.
[Paid Software Announcement and Discussion] JohnnyCanuck:
Is xase 1 working for you now? I simply cannot get it to work. WiFi Launcher detects BT connection and starts its service, it then starts the hotspot on the slave, and starts AA on the Master but .... nothing connects to my car. No Android Auto.
[Paid Software Announcement and Discussion] NYZack:
Yes, it works for me. But previous versions have as well.
[Paid Software Announcement and Discussion] JohnnyCanuck:
[MENTION=842765]Emil Borconi[/MENTION], the latest version of the app is completely broken for me. My case 3 scenario of starting a hotspot and Head Unit Server on my master and not triggering tether from the slave is also completely broken. I get a head's up notification on my phone that AA is connected to my car, but I get nothing on my car. Is there any way to download the previous beta? It's no longer on XDA Labs.

Trying it the way it's supposed to work with WiFi Launcher, my Master connects to HUR hotspot on BT connect but it does not start AA on my phone.
[Paid Software Announcement and Discussion] shmykelsa:
I wonder if the GitHub repo is updated at all since I'm interested in seeing the code & building it myself
[Paid Software Announcement and Discussion] smoki3:
I also wanted to upgrade to the new version (2.05).

But after installing it and converted to system app, the app was also gone after reboot. I tried to installed it again but now I can't get it running again when I just set it as default app.
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=2637038]JohnnyCanuck[/MENTION] - Email me please for the older version. [MENTION=5562025]shmykelsa[/MENTION] - No only the alpha version code is available as I have stated this in the beginning. [MENTION=3115338]smoki3[/MENTION] - When you say you can't get running, what happens exactly?
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=2637038]JohnnyCanuck[/MENTION] - Email me please for the older version.
[MENTION=5562025]shmykelsa[/MENTION] - No only the alpha version code is available as I have stated this in the beginning.
[MENTION=3115338]smoki3[/MENTION] - When you say you can't get running, what happens exactly?
[Paid Software Announcement and Discussion] smoki3:
The slave turns on the hotspot, my master connects to it, on the car it appears as connected but I can not switch to Android auto
[Paid Software Announcement and Discussion] Emil Borconi:
root or non-root mode?
[Paid Software Announcement and Discussion] smoki3:
root mode. Before I had the older version running as system app and it was working fine.
[Paid Software Announcement and Discussion] Emil Borconi:
Let me check, it was quite late last night maybe I accidentally broke something.
[Paid Software Announcement and Discussion] propi62:
I tried the 2.0.5 this morning for about 40 minutes and came late to work. Could not make it work.

The wifi optimization changelog is very interesting. Cant wait for new version to test it out.
[Paid Software Announcement and Discussion] Marshy33:
Same as others, couldn't get it working this morning with the new version.

Can grab any logs you may need lunchtime.
[Paid Software Announcement and Discussion] sibesaver:
Version 2.0.5 totally broke for me where previous was working in non-root mode. Head unit puts up a message saying I have to agree to terms and conditions but no screen on either master or slave to do this. It sort of acts like the head unit doesn't recognize the slave anymore. I used to at least get the AA icon to appear or the AAGateway splash screen.
[Paid Software Announcement and Discussion] smoki3:
Is there a way to download the old build?
[Paid Software Announcement and Discussion] Emil Borconi:
Can confirm I managed to brake to root mode in 2.0.5, fix expected today.
[Paid Software Announcement and Discussion] Emil Borconi:
2.0.6 should fix the root mode, sorry (out now)

By the way I did some benchmark (non scientific) and there is significant difference between hardware. For example using a Xperia X Compact as the slave I did had significant shutter of the music when I was dragging the map, however using the pixel 2 xl, it was smooth. Both slaves where set to 2.4Ghz network, 5Ghz is better.
[Paid Software Announcement and Discussion] fma965:
Thanks, it doesn't seem to happen always though, like today i went in the shop for less than 5 minutes and it worked when i got back in the car but other times it hasn't

I haven't tried the new version yet so will try that shortly.

Side note: If you guys have older phones on bloated firmwares you should really see if you have a Treble project for that device like project spaghet for a load of samsung devices, this allows a almost full AOSP experience and it was much faster that the samsung firmware.
[Paid Software Announcement and Discussion] Matt_black_90:
I have made my slave reboot every time it gets disconnected from my masters hotspot(case3)

This is done through Macrodroid.

Don't know if it makes sense but I feel like I give the app the best possible scenario by always connecting trough a freshly booted phone.

Since I got this working about a week ago i have not had a single problem.
[Paid Software Announcement and Discussion] Emil Borconi:
That is not a bad idea...
[Paid Software Announcement and Discussion] pflarini:
One problem that happens frequently is that, after master identifies BT connection, slave stops to tether...

What slave is trying to do?
[Paid Software Announcement and Discussion] Emil Borconi:
Root or non-root mode? And does the master actually connects to the slaves hotspot?
[Paid Software Announcement and Discussion] pflarini:
Slave is rooted.

Master connects correctly, but after that situation, it looses connection. So I need to wait slave to enable tether again, but a this point, android auto is gone in master, so I need to force BT disconnect and reconnect, that causes slave to loose tether again.. It´s a loop..
[Paid Software Announcement and Discussion] Emil Borconi:
Even with today's version?

If yes enable the debugging option and capture me a bug report from the slave. Thanks.
[Paid Software Announcement and Discussion] NYZack:
Here's an interesting experience. I had an old Android TV box lying around and decided to try that as a slave (running Android 7, Nougat). Everything seems to work fine, except that whenever the device reboots, the HUR hotspot wifi security gets reset to "None," so the master can't connect. I know it's AAGateway that is doing this, because the hotspot settings are preserved between reboots when I uninstall AAGateway.

Moreover, it's even weirder - the master shows that the slave wifi has security on it (it's not an open network), but though it seems to connect, it can't get an IP address. It will only get an IP address if I manually set the wifi password on the slave (which shows itself as having no password). Again, once I set this password, it gets wiped with the next reboot.
[Paid Software Announcement and Discussion] DAVIZINHO:
Hello Emil!,

I received this today and comes with android 7.

I will install xdalabs antes test it in the next days. My idea is the master create the hotspot and the stick connect to it.
[Paid Software Announcement and Discussion] Emil Borconi:
Something is needed up on that TV stick. Not your fault but this Chinese ROMs should be treated with a pinch of salt. Hence preferring the older ones because they have way less security so it's easier to get what you want from them.