yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] tommy_riley:
I did some further testing with the RC1 candidate. Regardless if I used my non-root Samsung s8+ pie 9.0 as slave, or if I use my rooted LGv30 Oreo 8.0 as slave, as soon as I hook up the device as a slave device to my Uconnect 4c headunit in my Jeep, I get a garbled Android Auto screen.

It makes no difference if the master is available too connect to or not. I can verify the the connection was successful if I do hook up master as the Android Auto app when launched, acts as though it's in full AA mode and I can route music to my headunit via USB. I can tap on the screen and see that it's attempng to dial numbers or give "I can't help with that just yet" type Android assistent messages.bifni click on too many options on the garbled screen.

So for me at least for now the new AAgateway rc1 is functioning, just not visually UI ready due to slave pass through of UI. I tried various screen resolutions on both of the phones as well as turning on and off different settings on the phone to see if I can get anything to trigger the screen garbled to go away and I could not. Once I switch back to the latest beta release build and the XDA location I have both devices working to display Android auto properly over wireless.

also with the RC2 candidate if I tap away from the Android auto screen and come back it just goes to a black screen.

I've attached some camera grabs of the headunit initial display after slave AA gateway is connected via USB and then again when I switch away from Android auto and come back you see the black screen.

there's one more screenshot which isn't much different but that's after the master connex and I can see things starting to move around but it's still very garbled.

it looks to me like the switching slave and master tethering (when master qualified due to it running on 9.0 pie) was also A working scenario regarding functionality from what I could tell but not being able to see the UI on the headunit.

RC1 on master and latest beta on slave was a working scenario for me.

Note: Not sure why XDA labs app has decided to flip my image attachments upside down. Ha.
[Paid Software Announcement and Discussion] fold93:
Hi Tommy, thanks for the reply but the problem is definitely on the master side. I'm still trying to figure out if it has something to do with Huawei's power saving settings.

I have tried a little more today and got it to work nearly everytime. Sometimes only for 2-3 seconds sometimes even for 30+ seconds. But still after sometime the AAGateway app gets closed or crashes without any notification.

I will dig trough the logs in the evening, maybe I can find something.
[Paid Software Announcement and Discussion] Sandlife3680:
I have been trying to get the aagateway app but it keeps telling me to to download it in the xda labs app which I am!
[Paid Software Announcement and Discussion] lukindaSS:
Aa gateway
[Paid Software Announcement and Discussion] NYZack:
"App/Xposed updates" in the hamburger menu, then select "Apps" on top.
[Paid Software Announcement and Discussion] Emil Borconi:
Hi guys.

Ok so I have identified a few main categories of issues and I will try to tackle them one by one:

1) Some cars/units do reset the connection even after the Splashscreen is displayed

2) Some cars/units have messed up video (green coding/decoding errors)

3) Some reported disconnection after a few seconds

4) Reverse tethering doesn't seems to work / connect

Now there is no specific order on fixes (probably point 1 and 2 are the most difficult because they are car/head unit specific issues and I will need to somehow get my hands on a unit like that)

I've made changes and I think I've got point 4 sorted now so I will like to have some testers please. If you've tested RC1 and your car screen never showed up "Waiting for master to connect" or it kept resenting the connection, this updated won't help you, however if the connection seems to be enabled but nothing happened, this might be for you. Please do email me on borconie@gmail.com for the APK. Only email if you're master device is running Pie as I'm interested to know if I have fixed this particular problem for now.

While fixing this I've discovered that some Slave devices won't turn on the hotspot automatically, I think it's due to no sim card in them.

Example: MK809V and ZenPad (running stock 5) did not turned on the Wifi automatically not even with Tasker, however my Pixel 2, OnePlus 6T and Huawei 30 Pro all did without root.

Setup instructions for reveres tethering:

1) Master, only option which should be enabled is "Connect to Slave's hotspot" and the headunit server should not be running.

2) Slave only option which should be enabled is "Tether from this device" and if you are trying on a tv stick enable the "Hacky workaround to grant USB Accessory permissions" as well.

3) Make sure the master can connect to the slaves hotspot.
[Paid Software Announcement and Discussion] martin.armstrong:
I would suggest that when you want to turn on the wifi hotspot on a phone/tv stick with tasker or automate or manually for that matter, it is better to switch off the wifi before switching on the wifi hotspot as just turning on the hotspot can on some devices cause it not to switch on properly.
[Paid Software Announcement and Discussion] Emil Borconi:
Thanks. That actually did work!
[Paid Software Announcement and Discussion] TheCondorITA:
Just tried with rc2 and still got waiting for master.

Slave (making hotspot)

Galaxy S5 with lineage 14.1 clean rom, Just installed AAgateway

Master:

Oneplus 5 stock rom

Connect fine to slave but AAgateway seems that cannot reach the slave (no notification on slave "connect to master").

If i let the master build the hotspot AAgateway display "connected to master" but seems that There Is a problem on USB side. Headunit keep resetting USb connection?

It was Just a test, i understant that Emil won't focus on this setup.
[Paid Software Announcement and Discussion] Emil Borconi:
Try one thing please on the master disable mobile data, and try again, just for curiosity and see if then the master connects to the slave.
[Paid Software Announcement and Discussion] xXIgorXx:
I tried the RC2 version on my devices. My setup:

Master:

Galaxy note 9 running Android Pie

Slave:

Moto Z Style running Android Nougat

First I tried to setup the hotspot on slave side. My master connects just fine and Android auto starts on the master, but the headunit display turns black.

Same with hotpot on master and slave connecting to it, connection is fine I get all the notifications on the master that I'm connected, but headunit display black.

The beta works fine for me, only problem is that the connection is lost from time to time or the headunit server gets stuck.
[Paid Software Announcement and Discussion] Emil Borconi:
Ok, that might be a different issue... Again something to do with the video decoder. When the screen goes black try to press the home key or similar basically leave as running and switch to radio or something else on the headunit, then switch back to Android Auto and see if the screen comes up.
[Paid Software Announcement and Discussion] xXIgorXx:
Sorry Emil, that didn't work. After the screen turned black I went straight to the headunit's home screen, then to the radio and back to the home screen. When I press the Android auto icon, nothing happens it even seems to me that I get a little delay / lag on the unit afterwards.
[Paid Software Announcement and Discussion] Emil Borconi:
Ok, thanks for the info.

Yes delay / lag is possible, if I don't get everything 100% right headunit can enter stupid loops.... or unknown states...

Any chance you grab me a bug report from the slave when you get to the black screen?

Thanks.
[Paid Software Announcement and Discussion] pearsco7:
RC2 with Slave hotspot is working much better for me. Occasionally I have to exit AAgatewey from the master notification panel and manually relaunch in Master AAGateway app.

Voice commands however dont work at all and navigating the menus in Android Auto GUI in SYNC is very slow / choppy / laggy.

Slave: non-SIM'ed Pixel 2

Master: Pixel 3 XL
[Paid Software Announcement and Discussion] TheCondorITA:
Just tried but without any effect (tried also to Total clean and reinstall AAgateway on both master and slave).

Still get waiting... On the headunit (fiat Uconnect).

The First Time After reinstall and config something happened: master refreshed two times its screen, seems it's tried to start android auto but fail.
[Paid Software Announcement and Discussion] lockstra:
First of al: Emil Borconi thanks for helping us with your app. Appreciated when somebody helping us with this Google sh#t.

My question:

Is there anyone who has it working on a Mitsubishi Outlander PHEV 2019?

I have tried it with a slave stick (5.1) and a slave phone Gakaxy S7 Edge (7.0) with a resetted Galaxy Note 8 as master running on 8.0 but can't have a connection.
[Paid Software Announcement and Discussion] metin5013:
I feel a project such as this with such high interest from the community should be spun out as an open source project via github for a larger crowd of developers to contribute to. As much as the developer should be congratulated for the great work he has contributed, the lack of input or updates has left this lagging. Food for thought
[Paid Software Announcement and Discussion] rpgreentree:
Lockstra, I have it working fairly stable using the latest beta on a Mitsy Pajero Sport. I believe it has a very similar head unit to the Outlander. I have a Galaxy s7 unrooted as master, gs5 rooted as slave with usb and wifi boxes ticked.
[Paid Software Announcement and Discussion] lockstra:
Thanks for your tip. It is a Kenwood set.

I am going to give it a shot soon.

Many thanks!!
[Paid Software Announcement and Discussion] saspo59:
Hi friends

I have a problem to eastablich a connection,

OnePlus 3t running pie as master, lgg2 as slave,

both as rooted. First AA normally with cable works,when I try to make the wireless connection on master side all proceeds ok providing the wifi signal and slave detect it all ok when plug-in the USB cable to usb unit the unit detect and even gives the AA sign on unit like normal but I can't select AA mode when pressing the sign nothing happened,

Thanks for any help
[Paid Software Announcement and Discussion] monkey3ddd:
Got this working today. Slave - Moto E(2015) running carbon os, Master - S10+. Vehicle 2019 Expedition with Sync 3.

My only issues is notifications, no email or texts, although I suspect that is my issue, but if anyone has some insight that would be appreciated.

Issue 2 is voice control, as noted before by others, assistant seems to be listening as the 4 dots come up, but nothing happens.

Other than that it works and is very cool, thanks for your work, looking fwd to the next release.

*edit*

I got notified of a text message and was able to reply via voice, so that did work.
[Paid Software Announcement and Discussion] pearsco7:
Sounds like your experience mirrors mine. Question for you. Is it really slow for you when you try to navigate things on the Sync 3 head unit like the drop down for music apps or navigating within apps like playlist in Spotify?
[Paid Software Announcement and Discussion] monkey3ddd:
Navigate in android auto? No. I hit the headphone icon to change music "sources" and it seems to be pretty normal. I play music via rocket player, other times Sirius xm plays "underneath" android auto. Mostly have the live map displaying.
[Paid Software Announcement and Discussion] saspo59:
Hi all

Still no connection, all is set up well in master and slave, head unit server is running,wifi between them is ok ,AA icon in head unit is there, but still master saying waiting for slave connection, don't know i think I miss something any help ?.
[Paid Software Announcement and Discussion] fold93:
Hi monkey.

What Versions of AAGateway are you using on master/slave?
[Paid Software Announcement and Discussion] monkey3ddd:
Beta
[Paid Software Announcement and Discussion] saspo59:
Hi all

After traying many combo nothing work for me,I was using beta in master and slave.until I seen this u tube video and all working but only in the alfha apk, installing the AAg only in slave side.

https://m.youtube.com/watch?v=J3a-wKIww-w
[Paid Software Announcement and Discussion] epsonix:
6 weeks ago I got Mitsubishi Outlander PHEV (it was a 2-3 month old car with a few kkm mileage only) as rent car for a week while I was in France for snowboarding. I had millions of issues getting just Android Auto to work OK via USB (needed it for navigation as car did not have this). Usually I needed around 10-30 or maybe even 50 attempts to get the link with AA (just to have Google Maps to get around France), and in most of cases voice was not working (Spotify and navigation). I tried various AA versions, played with various settitngs or ways of connecting etc. Nightmare, I coudl not figured out one working way to get AA to work. I imagine these cars have something odd in its infotainment firmware that it is so problematic to use even over USB, so over AAGateway there may be also issues.

BTW. My phone works perfectly in in my Alfa Romeo Giulia both over USB and AAGateway Beta, however I have replaced radio for newer type/firmare - the one I got when I collected the car year ago had also problems with establishing AA link with phones I used to have in the time (usually 1-2 extra attempts needed) - after replace to newer my issues were gone.

Is your phone working OK over USB with the car? Maybe with stick it doesn't?

Maybe ask dealer if there is any firmware update for your infotainment or if they know any tricks to ease establishig connecitons?
[Paid Software Announcement and Discussion] lockstra:
Thanks for your message!

Yes, usb is working 90/100 times. I bought two different tv sticks but no luck on both. One time I saw the message return to Mitsubishi...... and the message aagateway but I didn't got it working.

Soon I try again!!

Thanks!!
[Paid Software Announcement and Discussion] epsonix:
if USB works in only 90% of times, it prooves your car has not perfected this link establishing. maybe you can check easily firmware you have in your radio/infotainment somewhere (e.g. in Alfa Romeo it is in some Settings menu) and ask on Mitsubishi forum - somebody with brand new car may check it for you - at least you will know if there is point to visit dealer and complain AA not working well, and try to get update which may help.

With sticks a lot of guys have problems as far as I read, even Emil could not get things fully working on some sticks as far as I recollect discussions from this year.

Maybe try with other phone. I got it 99% perfect on Beta RC3 with Automate running on both phones, slave provides hotspot, enables it on USB power (using Hotspot workaround for newer androids to avoid rooting), disables a few minutes after power is gone (and puts slave into power saving) - all to save slave power - its running fine nonetheless I do not commute a lot. On Master Automate forces Wifi connection with slave when BT of master connects to the car, and opens Spotify and start playing music. Master WiFi is setup to static IP, and slave AAGW has this IP fixed as master address. Both phones Android 8, stock Android (no rooting etc).
[Paid Software Announcement and Discussion] sibesaver:
I thought you had to run android pie on the master in order for the slave to initiate the hotspot, at least that was what Emil stated previously.
[Paid Software Announcement and Discussion] epsonix:
just works for me. and the best is slave does not need sim card. at least with my phones it works.
[Paid Software Announcement and Discussion] mkanet:
Are we there yet?

I've been waiting for a build that's completely dependable without having to add any extra software like Tasker. Are we there yet? Or, is it better to wait a little longer for more mature build

I haven't bought my slave device yet. Ill buy whatever slave device is necessary as soon as I get the word that this solution works reliably on its own.
[Paid Software Announcement and Discussion] najera23:
lag

Hello Emil,

I am using a galaxy s8 as a slave (it is the only device i have available at the moment) and an s10+ as the master.

I am getting a lot of lag when i hear music, sometimes it stops for a bit but it always comes back, i don´t know if im missing something in the configuration or ending proceses on the slave (almost all apps are disabled)

By the way, i use deezer as a music source with high quality(about 1400 kbps).

In the meantime i´ll try to use lower quality tracks.

thanks!
[Paid Software Announcement and Discussion] LLStarks:
It looks like Android Q Beta 3 is now enforcing the blocking of background services like AAGateway.
[Paid Software Announcement and Discussion] skip416:
I'm finding more consistent AAgateway connectivity with Q beta 3 than the previous Q betas, plus the audio issues have been resolved (ok google, sketchy Bluetooth, etc. all seemingly working).

For reference, I'm using the alpha AAgateway with pixel xl and Samsung s4 on lineage 14.1.
[Paid Software Announcement and Discussion] saspo59:
I think it's about time to get a new update that will be more stable
[Paid Software Announcement and Discussion] darling40:
Hello I trying to do android auto wireless and there are some step that I know understand, can please explain me step by step how to do it !!!
[Paid Software Announcement and Discussion] aemankocher:
Galaxy Note8 AAGateWay aemanduhok2322@gmail.com
[Paid Software Announcement and Discussion] bggold:
What steps don't you understand? The OP has it written out pretty well.

If you give us a little more info I'm sure someone will help you out.

Start with devices and headunit type. Then where you are getting stuck.

---------- Post added at 12:45 AM ---------- Previous post was at 12:45 AM ----------

? Cannot we get a little more info please?
[Paid Software Announcement and Discussion] Hckymstr19:
In my Audi with Galaxy s9 master and Droid turbo rooted slave, on beta rc3, it connects but shortly after it disconnects and I get the "AAgateway has stopped working" usually on the slave but sometimes on the master.
[Paid Software Announcement and Discussion] Wimmme:
I cannot get this to work anymore.

Tried 1.0 Beta RC3 on both master and slave, in all combinations of root or not. Tried 1.0 Alpha too, but it has no real interface is that correct ?

With the beta i get connection on both master & slave, but a notification on my car display:

Android auto gateway: connected to master; car connection established

Car display: Check mobile device to see if confirmation is necessary please.

Master: Oneplus 5 Pie rooted (or not)

Slave: Nexus 6P Oreo rooted (or not)

The strange thing is got this working somewhere in october/november, so it must have been the Alpha version

Is the setup different for beta and alpha ?

The USB connection to my Oneplus5 is unstable, for the nexus it is ok. Wireless AA would be so great.
[Paid Software Announcement and Discussion] fold93:
I think you should have a look at the unstable USB connection with the OP5. Cables tend to be very stable at connecting something :)

Maybe OxygenOs's power saving is the problem?
[Paid Software Announcement and Discussion] martin.armstrong:
As you are the only person on this forum who have mentioned that they were trying it on an audi I would suggest as a long shot to send an email to Emil Borconi asking

specifically for the test version RC1. My setup is a motorola one master and a Mk809V tv stick with an audi A4 B9 and neither the alpha or the Beta versions worked but the first test version RC1 did, albeit only with option 1, but reliably, and with an initial funny blank green screen when it had connected which reverted to the normal AA screen after pressing the menu button on the car and then reselecting the smartphone interface, but none of the subsequent versions RC2 and 3 worked.
[Paid Software Announcement and Discussion] Wimmme:
Maybe that 's a solution for me too, I drive a Skoda Superb, also VAG...
[Paid Software Announcement and Discussion] Hckymstr19:
What do you mean when you say "albeit only with option 1"?
[Paid Software Announcement and Discussion] martin.armstrong:
[MENTION=9290725]Hckymstr19[/MENTION]

see page 127 from forum, post from Emil Borconi, by option 1 I meant Setup 1, wifi tethering from master as opposed to reverse tethering from slave (setup 2)
[Paid Software Announcement and Discussion] hasanity:
Great idea and amazing work Emil.

Both alpha and beta versions work for me. However with beta version the connection lasts a few minutes before aagateway shuts off on my master phone. Using Google voice also crashes the app. Both of which are issues I'm guessing are pretty common and you're already working on. Looking forward to a stable version!

Master phone: Lenovo p2

Slave phone: Nexus 5

Running Android auto on VW headunit.
[Paid Software Announcement and Discussion] Hckymstr19:
Oh ok so the normal setup then where the slave connects to Masters hotspot right?
[Paid Software Announcement and Discussion] martin.armstrong:
[MENTION=9290725]Hckymstr19[/MENTION]

Yes
[Paid Software Announcement and Discussion] juajar:
I second this. The app just closes after a few minutes on my Motorola G7 Power. Should I try the Alpha? On either or both?
[Paid Software Announcement and Discussion] mat2802:
Anybody Tried to install it directly on the car infotainment?

On my hyundai ioniq I am able to access Android, and install apps, and car has WiFi...
[Paid Software Announcement and Discussion] sibesaver:
Hoping for a stable and compatible release with WiFi direct option. Seems like like this project is so complex though that wthout additional developer input it may never get there.
[Paid Software Announcement and Discussion] saspo59:
I don't see any response from dev. for long period even that it's paid app.
[Paid Software Announcement and Discussion] bggold:
Hey guys [MENTION=224120]Emil[/MENTION] has been very busy lately and has not abandoned his apps. I have said this before that most devs do this part time and have lives beyond Android app development.

Give him sometime and I'm sure he will give us all an update.

I have been in communication with him. He is still around.

Please be patient. He usually comes back from these "long" absences with great breakthroughs.

Thanks
[Paid Software Announcement and Discussion] Pedroenf:
Amen to that :good:
[Paid Software Announcement and Discussion] valerikolev65:
Hi,

It works goot with the following setup:

HU: VW Passat m/y 17, Discover media

Slave: Xiaomi Redmi Note 3, LineageOS 16.0, rooted

Master: Xiaomi mi5s, LINEAGEOS 16.0,rooted

Aagateway works under following conditions only:

Slave always connected to usb, WiFi always On

Master: Head unit server always running, Hotspot must be turned on before getting into the car.

If I use Aagateway options to togle usb/wifi on Slave and start tether /HU server on master, it doesn't connect properly.

So, maybe I am doing something wrong, or it is rom specific , or devices.

If someone has same or similar setup, pls share experience.

Cheers.
[Paid Software Announcement and Discussion] TheCondorITA:
At the biginning of the month Emil sent me and someone esel another revision to test. So it's not definitely death this app.
[Paid Software Announcement and Discussion] monkey3ddd:
Anyway to disable the "waiting for slave" pop-up? I have it working well, but that constant pop up. Yikes..
[Paid Software Announcement and Discussion] Marcozizou:
I have the galaxy s10 and the volksvagen T-roc I do the procedure but when I go to connect the smartphone to the radio with the cable it writes me on the car display that I have to check if on the smartphone there is need to grant an authorization but in reality I don't have none of it. Solutions?