yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] camoto:
2018 Jeep Grand Cherokee with Uconnect

Master: Google Pixel 2 XL (noroot)

Slave: Google Pixel 1 (noroot)

Configuration: using reverse tether hotspot on slave

Everything works fine but if I turn off the vehicle and turn it back on before everything had shut down completely, something on the vehicle's headunit gets in a locked up state where it can no longer see the slave is connected. Strangely this also causes bluetooth on the headunit to stop working too and I have to disconnect everything, shut down the vehicle and start all over again to get it working.

This complication threw me for a huge loop and I sunk a ton of time into troubleshooting so I never collected debug information, sorry. This is a great app and I am really excited to see what comes of it but seeing how much I rely on AA, I am going to keep watching on the sidelines for now. I really appreciate all of the hard work that is going into this as it's really what google should have been working on a long time ago. This project would be earth-shattering if the following could be implemented:

1.) In app connection status for the slave and master so that the user can see what connection is not working or status of headunit server.

2.) Avoid using developer headunit server so that it didn't need to be started, restarted, etc from a separate app.

3.) Full automation of needed connections unless there is an error so that required user input is minimized.

I know it's still early and this will progress but wanted to just say thanks and provide what little feedback I have. Great job, Emil!
[Paid Software Announcement and Discussion] rpgreentree:
Hi Emil. The app is working great but I still have 2 problems with it and 1 new one.

First is that the slave will not self connect if the USB cable is left plugged in. Although it's not a great imposition I have to wait for the hot spot to connect then unplug the USB and plug it back in again. I believe it is because the power comes to the slave very early on in the car startup process. Then Bluetooth connects to the master and starts up aagateway and the hotspot. Then I have a wait of about 30 seconds for the slave to connect and I believe the wifi toggle has timed out as I don't see any activity when wifi connects.

The other one is that aagateway persists on the master well after I leave the car, which isn't that much of a problem, except that if I forget to exit and the phone rings it thinks it is still connected to AA in the car and won't let me answer or use the phone to talk.

The last, and certainly the least, is that with release 3 if I chose not to manually connect to USB the master chimes every 20 seconds or so while looking for activity from the slave. Once I manually connect to USB the chime goes away.

This is a great app Emil and a real game changer. I hope you do well with it.

Edit

I noticed that the wifi toggle needs a rooted phone. Should I have allowed root access to the app on setup?
[Paid Software Announcement and Discussion] journey42:
I have the same issue. Workaround is primarily just to turn off the car, then back on and wait. To connect faster after this, force kill the slave, then start up, then plug in, then turn on WiFi, then turn on car. That'll be nearly instant.

My setup is AVH-3250NEX (original firmware, not the update from mid-2018), in a 2012 Ford Focus with steering wheel control integration (can't remember the name), with a rooted G930T running Project L (Oreo) in the middle, and a T-Mo S9, stock, patched to current.

RC3 has been really nice, especially since I rooted. Only need to be absolutely CERTAIN to turn off hotspot right after the head unit goes off.
[Paid Software Announcement and Discussion] alexo95:
Android auto released an update today, it will be interesting to see if this solves/creates any issues
[Paid Software Announcement and Discussion] bggold:
No issues
[Paid Software Announcement and Discussion] Jaihoidundso:
My last Android Auto release is 3.9.585064 (Wednesday) . I don't have a new release. Oo
[Paid Software Announcement and Discussion] Emil Borconi:
3.9 is the latest but some people get it with a few days / weeks delay.
[Paid Software Announcement and Discussion] bbobbity5:
Thanks Emil, tried it but no good. Still the original issue of Bluetooth not connecting to car. I think it's just one of those things - hopefully a future update will fix it. Thanks heaps for your help though and great work with the app!

---------- Post added at 05:15 AM ---------- Previous post was at 05:11 AM ----------

Didn't work but a great app - thanks for putting me into it!
[Paid Software Announcement and Discussion] toband_se:
I have the same issue as previously reported by another user (with the same slave). The problem is on the slave.

Slave is a Nexus 5 (rooted) - running Android 6.0

When I start AAGateway it asks about "Allow AAGateway to use device location".

If I press Yes - then it asks again. Ending in an infinite loop asking for the same location access.

If I click "No - don't ask again" I get to the screen of AAGateway but no buttons are clickable.

The initial Alpha version worked - except for the other known problems.

Link to same problem here.
[Paid Software Announcement and Discussion] epsonix:
A few days of using AAGateWay 1.0Beta RC3 and aside of some issues I have, I found reliable way of making it to work.

FIrst, all the checkboxes on master/slave are unticked (mean automatic start of tethering or Wifi). WiFi on slave is always on. When I go to car, in advance I turn on hotpot. When I have slave connected to hotspot, then when I start car, all works well first time. When I leave the car, I have to disable hotspot manually, otherwise master AAGateway is keep annoying me with notifications every say 30 second.

If I go for automatics, then I rarely success, very often need to manually.

Looking forward for polished version - maybe something could be done about these notifications (so they do not keep popping up, just update text)

I experience sometimes significant slowdowns, cuts on music etc, but usually it happens within first say 10seconds after conenction to headunit, later is fast enough - probably part of reason is that my slave is rather slow (Samsung Galaxy A3 2016) and master is rather average performance phone (LG Q6). For completness, my car is Alfa Romeo Giulia 2018 and using stock headunit.
[Paid Software Announcement and Discussion] kalua1985:
I have the exact same issue with my VAG car. No way to automate the setup.due to this. Using unrooted galaxy s7 as slave and unrooted note9 as master.
[Paid Software Announcement and Discussion] UnReal':
[MENTION=842765]Emil Borconi[/MENTION] Hello, and thank for your amazing work.

I was asking myself if there was a possibility to export to canbus informations from Android Auto.

Let's take the exemple of VAG, there is a small display (called MFD) who output informations from Head Unit. It can be song informations, direction, or even calls.

Here is an exemple with navigation :

Youtube

Here is an exemple with audio:

Youtube

I searched a little about it and found some datasheet of CAN messages : Google Sheet

Do you think it could work ?
[Paid Software Announcement and Discussion] *justintime*:
Why do you also ask in this thread? I saw this question also in an another developer thread...

This app has nothing to do with VAG information.
[Paid Software Announcement and Discussion] UnReal':
I ask this thread too because I don't know at which level we can retrieve the informations to send to CAN. If this can work using an app over Android Auto or if it need to be at the level of android auto app..?
[Paid Software Announcement and Discussion] mobileman88:
This app is just a proxy to aa.
[Paid Software Announcement and Discussion] bbobbity5:
Hey Fezster, it works!! Great suggestion - turns out I just had to be patient. If I get in the car and then activate that app, after about 3 attempts by aagateway (approx 1 minute) it then connects! Consistently worked for a couple of days now. Fantastic, very happy with that workaround, thanks mate!

---------- Post added at 07:59 AM ---------- Previous post was at 07:47 AM ----------

Hey mate, check out the solution suggested to me by the legend Fezster:

Just download the app https://play.google.com/store/apps/details?id=org.myklos.btautoconnect

And stick a widget on your home page. Then when you get in the car, hit that widget. It takes about a minute to work (3 or so attempts by aagateway to reconnect) but then it does it!

Btw I have aagateway set up to start and tether automatically when it detects the car Bluetooth. This app starts that process and then connects the phone after a few attempts. I just leave the head unit server running on the slave.

The settings on Bluetooth auto connect are as follows:

Set last device - ticked

Profiles - media and calls ticked

Devices - only have your car ticked, and moved to the top of your Bluetooth devices

Settings screen action - enable Bluetooth ticked

Events - all unticked

Good luck!
[Paid Software Announcement and Discussion] fezster:
No worries! I found that app really useful too.
[Paid Software Announcement and Discussion] denisehilton:
I've been waiting a log time for this Proxy/gateway. Thanks a lot for sharing it with us. Kudos.
[Paid Software Announcement and Discussion] airic37:
I updated my Nexus 5 with the lineage os rom in order to work around this issue. Things are working relatively well now.
[Paid Software Announcement and Discussion] imurdel:
A question could I serve as a slave the X96 MINI? Thank you
[Paid Software Announcement and Discussion] franco853:
hi everyone, just bought the app yesterday, went to try it, but cant seem to bypass one thing, i configured eveything and android auto pops up on my op6 when i plug the slave in the car, but it's stuck on a screen asking me to pull the parking brake, the problem is that is already pulled, i tried to toogle it off and back on but nothing, he won't let me configure AA.

Any suggestions?
[Paid Software Announcement and Discussion] kt0516:
Looking at the specs it might be possible, but you have to try it.. Of course I am curious about the results.. :)
[Paid Software Announcement and Discussion] Emil Borconi:
Just a quick update guys. Sorry I'm really busy this days and I haven't touched any Android Auto related development in the last 2 weeks, but my H96 Pro stick have arrived, bad news DO NOT BUY IT!!!!!!!!!!!!!!!!!!!! It does have 5Ghz Wifi but the micro USB port is for power only, there is no data port so you cannot connect it to the PC, neither to the car/headunit.
[Paid Software Announcement and Discussion] imurdel:
Hello, could you tell me if MK808B, is configured from the TV or from the computer, thanks
[Paid Software Announcement and Discussion] SLAB_8002:
Whew, thanks for the heads up. I was just thinking I need to order one this week.
[Paid Software Announcement and Discussion] moJinn:
Followed instructions and it works well, great work! although with my combination of hardware on the alpha works. but so far works great! although I lost my viper4android functionality, is there anyway to force audio through bluetooth? I have a ford sync 3 for the receiver and they also updated their firmware so audio goes through the usb port, and viper doesn't work for some reason (even though there's a usb profile) not sure what to do.
[Paid Software Announcement and Discussion] ksngrjn:
ordered MK809 IV Android 5.1 TV Dongle

I have ordered MK809 IV Android 5.1 TV Dongle from Aliexpress (productId=32909427834) for slave to work with Pixel 3 (Master) . Hope everything works well. will update here once i try it after receiving the shipment.
[Paid Software Announcement and Discussion] Duzao662:
Guys, I have a galaxy s8 exynos with the pie beta and I can't install the aagateway on it, any help? It just says download failed
[Paid Software Announcement and Discussion] moJinn:
i remember i had a tough time paying for it. but was able to download it eventually. im on pie also so you should be able to get it and use it. and try the alpha version if the beta doesn't work. only the alpha version worked for me.
[Paid Software Announcement and Discussion] pppeterrr:
Got my android stick ready, rooted and usb assigned to the app.

Assigned in the Developer settings, in debug mode use AAgateway.

But it doesnt work. Can someone explain me how to do it ?

What i did

1 factory reset the stick and root it (rk31sdk 4.2.2 stick)

2 connect it to the hotspot from the master

3 download the AAgateway, and set it as slave with all 3 options selected.

4 in the android settings i enable debug mode, and select aagateway as app

now it says "nothing to do here AAgateway is the default app...."

in the car, i connect the stick "host" to USB from the car,

and the DC into a charging USB.

The stick connects to the hotspot, and Aagateway is waiting for connection.

Nothing else happens, not even the notification on the car "usb connected"

I tried it before with a phone, and it worked pretty well.

I could need some help!

Do i need to enable in the USB settings "connect to pc" ? (normal settings)
[Paid Software Announcement and Discussion] NYZack:
Does the current version allow us to run the headunit server on the slave if the slave is providing the hotspot? Any trick to getting that to work? This would be great, so that the master phone wouldn't always have to be running the headunit.
[Paid Software Announcement and Discussion] pppeterrr:
This makes me totally crazy :cyclops:

So i found out that my tv stick got another usb port! Yes, this one should be the

port to connect with my car. Kinda stupid, at first i used the "host" usb port that

is also there. Well whateffer.

So, i get my laptop - 4G enabled (to see the headless android tv stick)

Installed the Host APK teamviewer on the tv stick.

Open teamviewer on the TV stick tethered to my phone.

Yes this works! I now can see realtime the tv stick (sorta, big lag thoug) on the laptop.

I go outside, to the car - plugin the usb

And 1 time i see the option to select AAgateway for the usb!!! GREAT

But then nothing.......ahhhhrghhhhhhh...................

Oke this is a great idea, the best! And the first thing that came to my mind

when i used AndroidAuto - No cable's !!!!!

[MENTION=842765]Emil Borconi[/MENTION] I hope you will go steps further with this project, i will support and

try out everything that is needed. But for now - with a android stick, you will

get crazy users :silly::eek::cool:
[Paid Software Announcement and Discussion] Habibmustafa:
If this is a success, I hope it makes Android-based infotainment units (with WiFi/BT) a capable slave unit. If there is a beta test program, sign me up, Emil. Honda '16+ guys, how is your experience? Just thought I ask again here since there's 101 pages worth of old and outdated comments.
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=9576945]imurdel[/MENTION] - From where it's easier for you can be both. [MENTION=4702181]moJinn[/MENTION] - Not quite, I'm not sure about Ford Sync3 but my Sony disables the BT Media source on the headunit when AA is running, so phone is unable to output over BT. [MENTION=1655232]pppeterrr[/MENTION] - If you do have an option called "connect to PC" that does need to be enabled (if it's a Rockchip AAGateWay should enable it automatically). On the slave you won't see anything else (2 notifications) but nothing more. After that prompt the slave will try to connect to the master. Was AAGateWay running on the master? [MENTION=3770040]NYZack[/MENTION] - Headunit Server must always run on the master, you cannot run it on the slave. I will add the changes for those who have Pie on the master to be able to connect without running the Headunit Server.
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=9576945]imurdel[/MENTION] - From where it's easier for you can be both.
[MENTION=4702181]moJinn[/MENTION] - Not quite, I'm not sure about Ford Sync3 but my Sony disables the BT Media source on the headunit when AA is running, so phone is unable to output over BT.
[MENTION=1655232]pppeterrr[/MENTION] - If you do have an option called "connect to PC" that does need to be enabled (if it's a Rockchip AAGateWay should enable it automatically). On the slave you won't see anything else (2 notifications) but nothing more. After that prompt the slave will try to connect to the master. Was AAGateWay running on the master?
[MENTION=3770040]NYZack[/MENTION] - Headunit Server must always run on the master, you cannot run it on the slave. I will add the changes for those who have Pie on the master to be able to connect without running the Headunit Server.
[Paid Software Announcement and Discussion] imurdel:
Thank you very much for the answers
[Paid Software Announcement and Discussion] franco853:
Guys anyone can help me with my parking brake issue? Everything is working and connecting on my setup(op6 master / lg g4 slave) but AA on master won't let me setup saying parking brake isn't pulled... But it is, and the headunit(alpine halo 9) detecting it correctly in his own settings.
[Paid Software Announcement and Discussion] moJinn:
Thanks for the update Emil, I've been asking around in the v4a thread and they've been trying to help me out getting v4a to work over usb but no luck yet.
[Paid Software Announcement and Discussion] Frinky:
I followed the instructions in the OP for my phone and for the MK808B and things seemed to go okay. However, when connecting to my car, my head unit recognizes the MK808B as an Android Auto device (I get the icon and it boots into AA mode) but then I get a black screen on my head unit saying to stop the car and follow the instructions on my phone and my phone keeps giving me the "waiting for slave..." notification. Any ideas? Head unit's an XAV-AX5000.
[Paid Software Announcement and Discussion] pppeterrr:
[MENTION=842765]Emil Borconi[/MENTION]

Thanks a lot for your reply, i am a little further now.

It seems that the alpha version gives me a working situation.

Or at least, that is with a phone. With the beta on the android stick, for

now it gives me a "android auto error". So switching back to alpha.

But selecting AAgateway as default with the alpha, seems a big problem.

I cant get it to work. If only i could get the auto default for the usb in

the alpha situation or something like that. It will work here.

For now i will wait for your next release.

BIG thanks for all your work!!
[Paid Software Announcement and Discussion] Gunde:
Anyone else experiencing the slave asking for AAgateway as default every single time it's plugged in? Why won't it remember I wonder?
[Paid Software Announcement and Discussion] Emil Borconi:
Send me a bug report please. The beta version does twinkle around with the Parking Brake sensor data. I only need the bug report from the master.
[Paid Software Announcement and Discussion] Emil Borconi:
If you expand the notification on the master does it still only say "waiting for slave" or do you see more info there?
[Paid Software Announcement and Discussion] Emil Borconi:
Android Auto error on the car can be acceptable, it might give you similar message till the slave connects to the master.
[Paid Software Announcement and Discussion] Emil Borconi:
I heard of something like this on a couple of times, but I'm not aware of the fix. Are you using some custom ROM? Try to disable Google Play Services on the slave.
[Paid Software Announcement and Discussion] Gunde:
No custom ROM. Non-rooted LG G3s factory fresh.
[Paid Software Announcement and Discussion] sibesaver:
I have yet to get it to work on my Verizon LG G3. I had the same issue. Yesterday I got further than I ever had by rooting and disabling Google Play services. Rooting bypassed the constant default dialog. However, the USB connects as installer instead of accessory (which I think is what's required). I've yet to get AA to appear on the head unit (Kenwood DDX9704s) even though I get the slave and master are connected. I might try a custom ROM as Verizon's stock on the LG G3 is just all sorts of a mess.
[Paid Software Announcement and Discussion] Gunde:
Thanks, I'll try rooting and disabling Google Play Services.

Besides this annoying prompt, it all works great for me, as long as I plug in the slave last. Master BT and hotspot needs to come first, or it won't work at all . Next step is to find out how to fix this.
[Paid Software Announcement and Discussion] sibesaver:
Let me know your setup if you ever get it working consistently and I'll do the same. The G3 is still a great phone and I think would work good for this but frustrating to get it to work.
[Paid Software Announcement and Discussion] Emil Borconi:
You should be able to do it without root:

Plug in to a PC and run this adb command:

adb shell pm disable com.google.android.gms
[Paid Software Announcement and Discussion] Frinky:
I'll check the exact wording next time I'm in the car, but when I expanded the notification it said connection successful which I thought was odd.
[Paid Software Announcement and Discussion] sibesaver:
Master LG V20 Verizon stock

Slave LG G3 Verizon rooted running 6.0 stock rom

I can consistently get what appears everything connected between slave and master upon starting the car with RC3.

Slave has 2 notifications.

1. Listening for state changes

2. Car connection established

Master has 1 notification.

1) waiting on slave

The head unit (Kenwood DDX9704s) displays the message.

You must agree to the terms and continues to use Android Auto. I can close the message both nothing happens, no Android Auto interface appears and I have no dialogs on slave or master where I can agree to the TaC.

Any ideas???
[Paid Software Announcement and Discussion] valhallen.282:
Issue - Jitter while music playback

What happens-

While I haven't been able to pull a bug report on it just yet since I'm not using my car. The last time I had music streaming issues I realised it was because the app was force reconnecting I guess.... I would have jitter while playing Spotify/Poweramp and see the notification popup of AAGateway.

Possible causes I looked at-

Since notifications of AAGateway are set to silent it's not the notification audio causing ducking. Notification ducking is audibly different from jitter.

The Master is an S9+ and has been set to allow AAGateway to run in the background. So it can't be that the app is being killed seeing as I'm a fairly light app user.

I'll check over the next day or two if the slave device(Rooted Xperia L running aoscp) has some battery optimisations killing the app in screen off mode that is causing the reconnects... Just thought I would put it here.
[Paid Software Announcement and Discussion] pppeterrr:
[MENTION=842765]Emil Borconi[/MENTION]

Got it working with my android stick! Not sure anymore what makes it work, did so much

things, it can be anything :) Anyway got some stutter in the audio, but that could be the

fact that it had droid vnc running. Pretty handy to get the stick screen on your phone.

Anyone else got some good results with a android stick ?
[Paid Software Announcement and Discussion] odl:
for me stutter in the audio is always caused by poor wi-fi connection (I tried with multiple configurations), meaning long pings and some packets lost from time to time. you can check it running ping command with terminal emulator on android device. The thing looks like there is missing some buffer for audio on slave side even for short network interruptions.
[Paid Software Announcement and Discussion] sibesaver:
User error. Somehow the allow new cars was unchecked. Once i checked and rebooted both devices I got the screen where i could agree to TaC. Everything has worked fine connection wise since (only 2 connection trials today).

Question on custom DPI. My head unit is 6.95" and a resolution of 800x400. The interface is narrowed by half with at 160 dpi. Anyone with a similar size head unit and resolution have a good dpi setting?