yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] epsonix:
OK, thanks for information. My master runs Oreo, and based on first post instructions from Emil, reversed tethering only works if master runs on Android Pie (like your Pixel 3 has).

I wonder if Emil would find work around this to allow older Androids to support such as well.

Also, is it required that slave phone (which runs hotspot in such reversed config) has access to mobile data - currently I do not have any SIM card in my Slave, and would prefer to keep the one I have for some other use (unless it is really needed, but better would be without).

re newer beta, I well undestand, lets wait for Emil to release newer version.
[Paid Software Announcement and Discussion] NYZack:
Slave does not need to have data. That's the reason for needing a recent version of Android on the master, which lets the master stay connected to a hotspot that doesn't have internet while simultaneously getting data from the cell network.
[Paid Software Announcement and Discussion] epsonix:
but since both my slave and master runs on Oreo, would it be solution if I put SIM card into slave end enable mobile data? I guess I still need static IP for master with current version AAG, don't I?
[Paid Software Announcement and Discussion] sibesaver:
Maybe I'm missing something but it seems like wifi direct would work more seamless as it does away with the pseudo master/slave relationship of a wifi hotspot. Plus like I mentioned earlier "hotspots" can be carrier controlled/ restricted.
[Paid Software Announcement and Discussion] NYZack:
That would work I think, but I would assume you need the SIM card for the master. You need to be able to provide the master IP to AAGateway, and ideally you'd have a static IP (which you can set up under wifi settings on the master). My slave phone keeps changing the IP address of itself (the gateway), so I couldn't set up static IP settings for the master (which require that you enter a static gateway address). This wasn't a problem for me, because the hotspot gives the same IP address to the master each time (luckily).

I don't know if AAGateway will work with wifi direct at present, but I agree it sounds like a good idea. And I don't know if your hotspot (on the slave) will be carrier-restricted if there's no SIM card (in the slave) phone. Probably phone-specific.
[Paid Software Announcement and Discussion] epsonix:
On master of course I have SIM, on slave I just tried, and it works nonetheless I have no SIM there. On master there were some warnings, WiFi icon is with ! symbol, and it uses its own mobile data anyway, but connection is being established all right. I tried with DHCP, and set first such IP on slave AAGW, then disconnected all, tried again, I was assigned with the same IP. Then I forced this IP, played a bit, all works fine.

I also started testing with WiFi Direct. I also get luck with working through this channel (I got assigned with different IP, so needed to change it in AAGW on slave). I will test it more, but battery in my master was discharged and I didn't have USB C cable in my car (slave is running on micro USB), so need to return home. I will do more tests soon, and will see which way works better.

Just to remind, my master is LG G7 Fit Android 8.1 unrooted, slave is LG Q6 Android 8.1 unrooted, AAGW is last beta from 13 Jan, AA apk is 4.1 arm64 and car is Alfa Romeo Giulia manufactured in 4.2018 with replaced radio (newer firmware 080.000.047 than I used to have (since on older there were in general some issues with AA over USB))

BTW.Typing IP into AAGW slave needs small trick- I get only numeric keyboard, no . symbol, so needed to type it in other app text field and copy whole to AAGW.
[Paid Software Announcement and Discussion] martin.armstrong:
MK809V as slave, Motorola one android 9 as master

I have received an MK809V stick. This has android 5 and also has the ability to create a wi-fi hotspot although it has no provision for inserting a sim-card but I can connect to it with my android 9 master which notices that it has no internet but nevertheless can maintain a connection. with it.

This stick also has the MBOX launcher which on the MK809IV, in any case, seems impossible to replace with standard android one. I have the feeling that AAGateway might work better if I could do that, any ideas from anyone how to do it?

I have tried the alpha and the beta versions of AAGateway on the slave (I forgot to swap also the version on the master but I don't know whether that is important, I was always using the beta version on the master) , with the beta version trying it with superuser access and also not.

I have tried the reverse hotspot method also.

I got, I think only the first time of trying, the message on Audi A4 screen asking to activate android and also whether to always do it and telling me to follow non-existent instructions on phone but then that time and all subsequent times the slave always crashes. I have tried it with the AAA,BB and C flows in the automate app and also without, but without fail the stick always crashes upon connecting!
[Paid Software Announcement and Discussion] martin.armstrong:
MK808, MK809IV and MK809V as slave, audi A4 B9, motorola one as master

All 3 of my tv sticks crash as soon as they try connecting to my car, regardless of whether I allow root access or not, regardless of what options I select in AAGateway on them. and also in alpha version and beta versions..

I have replaced the mediabox launcher on the 809IV and MK809V with the GOOGLE NOW LAUNCHER but it had no effect on the behaviour with AAGateway.

If anybody is interested I managed it by doing the following:

installed/updated to latest version the GOOGLE app.

installed GOOGLE HOME

installed GOOGLE NOW LAUNCHER (afterwards do not attempt to run as an app, as it will just say that the mediabox launcher is the default launcher)

Restarted the sticks and a choice of launchers was displayed and selected GOOGLE NOW (JUST ONCE initially)

I hope that an update of AAGateway will be soon available as so far I have had no success whatsoever.

Anybody out there got it working with a tv stick on an Audi A4 B9?
[Paid Software Announcement and Discussion] epsonix:
Over last couple of days I've been testing config with hotspot on slave without SIM card/mobile data on this and fixed IP of master in slave app (and on master wifi connection). All works grand quite well.

I had to add Automate flow on slave to control my slave's hotspot, as otherwise it was draining battery too quickly - now I enable on power from USB (which i get for the moment when I open the car, and then later when ignition is on) and disable it after 10 mintes of no power. That way my slave phone keeps well charged, nonetheless I use my car usually 0.5h a day only to commute 8km to the office and back.

It happened once that AA server has crashed over this time, but all works much better then in times when I had hotspot on master.

There is still some glitch when my master looses network coverage - Spotify freezes. I have no clue why, since I have all playlist downloaded to my master and slave's hotspot looks like does not need it. I reckon it is some odd of Spotify or AA rather than anything related to AAGateway.

from future version of AAGateWay I would wish to see automatic control of AA server, check its status (crash handling/restart).

In terms of custom DPI. If I do not tick the box on master, I not that much fits to my car screen (maybe it is because it is pretty low resolution 800x480)? When I select any other custome DPI in other hand (no matter if it will be 50,80,120,160,250, 1000), I always get some other scaling across - things then become like say twice compressed and text bit small. I though still prefer it over no custom DPI, as on Google Maps various permanent elements do not steel that much of the map.

Very often with voice commands I have problem when using AAGateway - it often tells back that This internet connection is too poor or not stable. I'm not sure if newer AAGateway may do anything about this, or it is purely matter of addtional WiFi bridge, delays and AA Server.

Looking forward for newer version with some fixes/improvements.
[Paid Software Announcement and Discussion] Emil Borconi:
Hi guys.

Not gone, working hard to make this fully usable, finally some progress, but still cannot make this work on real cars / headunits yet.

https://youtu.be/RkNseIiWPg0
[Paid Software Announcement and Discussion] Thofkes:
Very excited for your next release!! I use AAGateWay on my daily commute, but lately it has been crashing a lot which is always a bummer :( do you have a timeline for the next release by chance? Thanks! ?
[Paid Software Announcement and Discussion] bggold:
Remember is not polite to ask for etas.

He has to work out some issues that might take a few hours or could be weeks let's hope not the latter.
[Paid Software Announcement and Discussion] Thofkes:
I'm very sorry! I'm not on forums very often so I'm still learning the ropes. Let's just say I'm a huge fan of this app so I'm quite excited about it's development. I do not mean to offend. I'm happy to do whatever I can to help! I've only taken a couple application development classes in college a few years ago so I'm quite rusty on code, but I'm a fast learner if there is any particular subject I could help focus on. Otherwise I'm happy to send bug reports and patiently wait for any news!
[Paid Software Announcement and Discussion] bggold:
Don't worry about it. It is kind of an unspoken rule. No offense take.

I'm sure once he gets the bugs out it will be a great improvement.
[Paid Software Announcement and Discussion] Thofkes:
I completely agree! Best of luck to Emil!
[Paid Software Announcement and Discussion] gregoff82:
Just tried it out!

Been lurking on this thread for quite some time and now I finally have a AA enabled car so I could try this out!

Car: Honda Civic 2018

Master: Oneplus 6T, Android 9.0

Slave: Nexus 5X, Android 8.1.0

After a little hazzle back and forth (the nexus has a badly cracked screen so I had to combine my efforts with a remote tool and a mouse over OTG). For the first few rounds it worked qutie well but after a few minutes it froze. To the best of my abilities, I have come to the conclusion that the issue was that the Nexus disconnected the wifi to the master for some reason. This seems to be a common issue on the Nexus 5X so I don't think it's related to AAGateway.

Great work Emil! Once you hit a stable version I would suggest that you actually increase the price (because you are worth it). I would easily pay 10 times as much for this solution!

Just a random thought: In the meantime, I use the nexus as a stand alone AA device in my Honda which works. However, I cannot make calls on AA since my SIM is in my master phone. That made me thinking... Instead of routing the Android Auto GUI through the slave, why not have the slave doing all the AA stuff, but use the slave as a Bluetooth slave somehow. I'm not an expert on the subject, just a random thought.
[Paid Software Announcement and Discussion] sibesaver:
Maybe because I have an old slave (G3) running 4.4 but how is this possible? I thought AA required a SIM to expose things like maps, notifications, and streaming music, didn't realize it could work standalone.
[Paid Software Announcement and Discussion] gregoff82:
There wont be many notifications since I won't receive SMS text messages or such (since the sim card is in my main phone, not the one connected to AA). For music I use Spotify which supports offline playlists (which are kept up to date when reaching my home wifi when on the driveway). For maps I can easily make a hotspot on my regular phone.

But no, for Spotify it doesn't need a SIM or any connection at all for that matter for daily use (other than on the driveway). AA starts with no problem.
[Paid Software Announcement and Discussion] Sage:
my two cents.

VW Golf 2016

Slave S7 Edge Oreo (Touchwiz)

Master S9 Edge Pie (Touchwiz)

Took me quite awhile to get it working. Lots of reboots and disconnects and reconnects. Finally got it up and running though had really bad lag on the GPS. I was consistantly 150m behind where i actually was.

All that aside it looks great and once i got it working i loved it!

The only real problem other than the GPS lag is that i had to disconnect and reconnect the USB to the slave everytime i turned off the car. Is there a way around this? I did try the 'echo 0 > /sys/devices/virtual/android_usb/android0/enable though this didnt work either.. i didnt have the problem with an old Nexus though it seems Samsungs have to physically disconnect and reconnect to start Android Auto.

Anyone else have a fix or experience with this?
[Paid Software Announcement and Discussion] itsmewajid:
Hi guys

sorry if its posted in the wrong thread

I have an android head unit running 8.0 in my civic which has a carlinkkit dongle connected.

I connect my OnePlus 6T over usb to the dongle for android auto. Can i make this wireless with AAGateway like running the slave in the head unit?

Sorry if am wrong
[Paid Software Announcement and Discussion] pearsco7:
I am using the same setup as you in my truck, Pixel 2 (slave) providing the hotspot to Pixel 3 XL (master). Am I correct in assuming the only thing I have to do on the master is enable the server in Android Auto developer options and manually start the Master in AAGateWay? How about on the slave? Just assign the master's static IP?

Also is the beta version you were emailed newer than the posted beta for download? (Version 1.0 Beta RC3 on 01.13.2019). It seems for me the voice commands are real hit or miss.

I agree, once we can run the server on the slave and we dont have to have anything special running on the "master" and that would be amazingly awesome!
[Paid Software Announcement and Discussion] NYZack:
You don't have to do anything manually on the master (assuming things are working normally) if you set AAGateway to start on the master whenever it hooks up to the car's Bluetooth, and have the headunit server running in the background. I disabled battery optimization on the master for AAGateway and Android Auto; not sure if that was necessary. And I minimized the notification for the headunit server so it's not taking up unnecessary space on my notification shade or constantly showing me the notification on the top of my screen. You have to enter the master's IP address if the slave is making the hotspot; otherwise it's not necessary.

The beta version I'm running hasn't been released on this thread, to my knowledge.
[Paid Software Announcement and Discussion] ShadowSociety:
For those running the MK809 IV with Salkod's flows, what is your boot time like? From initial power to enabling USB connection takes my unit exactly 1 minute. I did disable the boot animation and from reports my time to start should be closer to 30 seconds. Any additional settings I should enable or things I should disable?
[Paid Software Announcement and Discussion] Emil Borconi:
Good news, I've made the breakthrough I needed on the slave side, waiting for more confirmations but looks very promising.

If all goes well I should be able to update the app on the next week or so, possibly to RC or stable state.
[Paid Software Announcement and Discussion] TheCondorITA:
Great news! I look forward for that
[Paid Software Announcement and Discussion] Emil Borconi:
SO STUPID!!!!!

I've spent over 8 hours trying to figure out why my connection gets dropped almost instantly after it's been established, just to realise that I've had the limit wifi option enabled in AA, so every time it connected it killed the Wifi.

GGGGRRRRRRR!!!!!

Anyway more progress made, so next version around the corner...
[Paid Software Announcement and Discussion] Emil Borconi:
Ok, can I have some testers please?

If you will like to test please do email me on borconie@gmail.com, at first I will like to ask users who have 2 phones and who are fairly tech savvy preferably. Also since I made loads of changes I'm not sure if I broke or not the "OK Google" problem so it will be nice if I can have a tester from those who suffered of the "Ok Google" issue.

Setup 1)

Tether from Master and connect Slave to Master:

- Everything stays the same as it was with the beta version, and all the settings and steps are the same. However the Slave should pull up a video instantly on the car's screen so there should be no need to toggle USB and WIFI on the salve.

Setup 2)

Tether from Slave and connect to Master to Slave (will only work if MASTER is running Pie)

- On the master make sure you enable the option "Connect to Slave's hotspot", as well as selecting the car's BT adapter.

- On the slave, enable the Tether from this device option.

- Make sure the Master have the Slave's hotspot saved so it can connect automatically

- Make sure the Headunit Server is NOT running on the master.

- Plug in the slave to the car and start the car

- Slave should connect to the car instantly displaying a waiting message on the car's screen and also it should turn on the hotspot

- Master should start AAGateWayWifi as soon as it connects to the car's BT and when it connects to the Slaves hotspot it will start AA as well.

Once I have some feedback on how it is working I'm looking to clean up the code, remove the logs, make a bit of cosmetics on it and push it to release stage.
[Paid Software Announcement and Discussion] sibesaver:
Just curious if the slave will always need pie for setup 2? Setup 1 isn't an option for me as my wireless carrier restricts my hotspot on my master which is non rooted.
[Paid Software Announcement and Discussion] Emil Borconi:
Oh, thanks for spotting that, master needs to run Pie, Slave can be on anything!
[Paid Software Announcement and Discussion] pearsco7:
Email sent. I would love to test setup 2 for you.
[Paid Software Announcement and Discussion] alexo95:
Dang, my phone is android 6 with no updates available. I may have to get a new phone soon :/
[Paid Software Announcement and Discussion] jimsey:
Hi Emil,

Email sent, happy to test either setup, have a few old phones I've setup as slaves.
[Paid Software Announcement and Discussion] pppeterrr:
[MENTION=842765]Emil Borconi[/MENTION]

Present to help you out with some testing - i send you an e-mail
[Paid Software Announcement and Discussion] sibesaver:
I think devices with Pie are still far in the minority. New phones are just costing way too much these days. I could buy a WiFi headcount fast cheaper than a flagship phone running pie.
[Paid Software Announcement and Discussion] scott47:
I just learned about this effort and I'm really excited to try it!

I recently installed a Pioneer 4400 NEX unit which is supposed to have wireless Android Auto...only it doesn't seem to work at all. I am using an LG V30 running Android Pie (Lineage OS 16 unofficial anyway). It works great when I use the hardwired USB connection, but wireless won't work with AA at all. I've read online that this isn't that uncommon so I'm hoping I can get this to work.

Since I don't really have a spare phone to use, I purchased what I hope is a compatible MK809V unit: https://www.ebay.com/itm/371975885995 (it shows MK809V in the picture but MK809IV in the description).

Emil, thanks for working on this!
[Paid Software Announcement and Discussion] TheCondorITA:
Email sent, i can try setup n.2
[Paid Software Announcement and Discussion] imurdel:
Hello, those of us who have MK809 as a slave, how do we do it? Thank you
[Paid Software Announcement and Discussion] Thofkes:
Anyone else running the new apk (and trying either option 1 or 2) and just getting a black screen when you plug your slave in? Or are people getting it to work? I've only been getting a black screen so far... My phone just updated to Pie yesterday and I installed the new apk after that so I'm not sure what the cause of the issue might be. Going to send Emil logs when I get a chance.
[Paid Software Announcement and Discussion] jimsey:
Hi I've tried 2 different slaves and get the black screen with both. I've sent logs to Emil , he initially thought it might be related to sleep/doze settings on the slave, but not so sure now you have the same result.
[Paid Software Announcement and Discussion] pearsco7:
I have tried "setup 2" with multiple slaves (S8/Pixel 2) and masters (Pixel 3, S8+, Pixel 3 XL). Only once was I able to get it working but it would never work again after that first time. All I get is the screen where it says waiting for master.
[Paid Software Announcement and Discussion] HofaTheRipper:
Same here. Option 1 doesnt work either.
[Paid Software Announcement and Discussion] Emil Borconi:
Looking into the logs.
[Paid Software Announcement and Discussion] jimsey:
No worries, just let me know if theres anything else I can do to help with testing ;)
[Paid Software Announcement and Discussion] rpgreentree:
Sorry Emil, I have had to reinstall the beta version. I have had the new version working on 2 occasions but each time it crashed with a "communication error". Unfortunately I'm going on aroad trip so I need reliability working satnav hence reverting to the older version. Once I'm back I'll try again.
[Paid Software Announcement and Discussion] Zece-88:
Hi Emil.

I'm done testing setup 1.

Master: Pixel 2 Xl, android pie, rooted

Slaves: Huawei P9, non rooted and Samsung Galaxy Alpha, non rooted.

Headunit: Pioneer F88DAB

Like the rest I was only able to get the headunit to show the message "waiting for master" a couple of seconds before it tells me "check your phone, when its safe to".

I've checked all permissions and still unable to get any futher. If I check master Phone, it tells that connection has been establised. If I go to android auto it tells me to those android auto on my headunit. Can't figure this out.

I had better luck with the beta, but it was behind with navigation (nothing wrong/lag duing music). Hope this helps you in your development.
[Paid Software Announcement and Discussion] jimsey:
Hi Emil,

After testing the new version I unplugged my slave and tried plugging my master directly into the cars USB and got the same black screen with a message saying waiting for connection. I Tried closing the aagateway app, restarting phone, restarting car and reconnecting USB multiple time with same result, then i uninstalled the new version of aagateway and the phone connected to the car first time. Wonder if the issue is with the app running on the master?
[Paid Software Announcement and Discussion] tommy_riley:
On the RC1 candidate, using S8+ as master and rooted LG v30 as slave (just to verify normal working scenario) I got to the point where everything connected, however the Android Auto display on my Uconnect headunit was garbled - you could tell it was Android auto but that was about it. Touch screen was unresponsive. Will try through some other scenarios, but if an RC2 is coming soon(?) Maybe I'll wait until that is available.
[Paid Software Announcement and Discussion] fold93:
Hi everyone.

I have tried this a few times half a year or so(with a Xiaomi phone) and had no luck. Now I'm running a p30 pro as master and a oneplus 3 as slave. Sometimes AA starts up and is displayed fine on screen, audio is working too. But after maybe 3-5 seconds the AAGateway app closes on the master.

The other times it closes when I push the Android Auto button on my car's head unit.

Is this something huawei specific? Any way I can troubleshoot this?

I will collect a bug report tomorrow maybe this will give me a hint..

Battery optimisations are off, the app runs forever even when connected to the master. The problem occurs once AA gets started.

I am running the latest beta of AAGateway downloaded from xda labs on both devices.

Best regards,

Fold
[Paid Software Announcement and Discussion] tommy_riley:
Not sure If related, but symptom sounds similar. I was having a problem with my slave phone where it kept disconnecting from the hotspot after aa auto started on master. My slave was rooted so I used magisk to hide aagateway from being detected as root so play services stopped freaking out and then made sure to have toggle USB with WiFi checked, and toggle WiFi on power unchecked on slave on the gateway app, then things stabilized for me. Make sure you reboot your slave after this config is set for the settings to stick.