[Android 4.1+]Proxy/GateWay for Android Auto

Search This thread

darkado

Senior Member
May 30, 2008
351
65
After three days and hours of trying I'm thinking of giving up. I tried all combinations listed in the first post and the closest I got was tonight when I saw AA screen on my car for a second. After that my car doesn't even register AA as connected after multiple reboots. Also it looks like aagateway app is actually turning wifi off on my slave.

Master: Poco F2 Pro (Rooted) running Android 11
Slave: Galaxy S8 (Rooted) running Android 9
Car: Peugeot 308 with a NAC head unit

Anyone had any luck with a similar combo? Is the slave too new to work?
 

TheDogg07

Senior Member
Apr 25, 2012
195
48
Craiova
Hello guys!
I have Ford Puma 2020 model with sync3 v3.4 head unit with wifi (with vodafone simcard inside)
My Puma head unit support android auto and I connect with a cable from the phone to the car's usb to use Android auto from the phone. Is there any possibility to connect to the car's wifi and use Android Auto without connecting the cable between the phone and the car head unit?
 
Last edited:
  • Haha
Reactions: e6o5

Illfatas

New member
Feb 9, 2021
1
0
So i was able to get everything running fine. The only thing is i'm trying to avoid using data when my car has unlimited wifi. USB tethering seems to automatically disable the wifi on the slave(it connects to the car.) I can manually turn it back on and have it connect and i get full connectivity. I'm just wondering is there a way to make this automated.

the slave is an unrooted pixel 3

i should add, that it straight up disables wifi when the tethering starts. Even with auto connect enabled it doesn't matter because wifi is off and wont scan for networks. i've found apps that might be a work around but their scan time is too high to matter(2hrs) on wifi automatic. This is my last step from having this completely setup. i even have the phone with velcro mounts and the wire hidden. i just want to avoid the pulling the phone out every time to hit the wifi button when it connects.

edit 3....putting in airplane mode prevents it from turning off wifi.
 
Last edited:

fcaronte

Senior Member
Nov 4, 2011
825
283
i buy the app and try to use my old wiko fever with a oreo rom as Slave device (with ROOT) and mi Mi 10 with stock android 11 MIUI rom as master. i do a lot of try but my only result is a "android auto connected" on master phone to appear and disappear continually but can't get work. i try with hotspot from slave (and so without internet) and then hotspot from Mi 10 but without success. any suggestion?

i try to log and i get this

E/CAR.SETUP.WIFI: Couldn't connect to socket, retrying 0
java.net.ConnectException: failed to connect to /192.168.43.1 (port 5288) from /192.168.43.159 (port 42923) after 10000ms: isConnected failed: ECONNREFUSED (Connection refused)
 
Last edited:
  • Like
Reactions: anirudhnyg

TheDogg07

Senior Member
Apr 25, 2012
195
48
Craiova
Hello guys.
I'm stuck on this screen. what to do next?

20210304_185531_resize.jpg
20210304_185751r.jpg
20210304_1858043.jpg
 

arl16

Senior Member
Jun 6, 2008
273
102
Eldersburg, MD
Using Rooted Samsung S5 running Lineage OS 17.1 as Slave
Using Non-Rooted Samsung S10+ running as master

Master is running Pie or above and slave is tethering:
  1. Running in root mode: YES
  2. If running in non-root mode, is the splashscreen visible on the car: Root
  3. If running in non-root mode, did you set the masters BT inside AAGW app?: Root
  4. Did the slave actually turned on the hotspot on the slave: YES
  5. On the master did you select the slaves BT in the Wifi Launcher app?: YES
  6. When the master connected to the car's BT did the Wifi launcher app started up?: YES
  7. Did the master connected to the slaves hotspot?: YES
  8. Did the AA icon appeared on the master at all (in the notification bar)?: YES
Seems like everything is working. Master says connected to Car, AA is running, but nothing shows on the Car Display. Wi-Fi Launcher says "Service is looking for car display" and vibrates twice every 3 or 4 seconds 10 or 11 times before stopping. Seems like maybe I have the wrong USB settings on the slave?

Any advice? Thanks...
 

makiavelo

Member
Jul 30, 2013
10
0
Using Rooted Samsung S5 running Lineage OS 17.1 as Slave
Using Non-Rooted Samsung S10+ running as master

Master is running Pie or above and slave is tethering:
  1. Running in root mode: YES
  2. If running in non-root mode, is the splashscreen visible on the car: Root
  3. If running in non-root mode, did you set the masters BT inside AAGW app?: Root
  4. Did the slave actually turned on the hotspot on the slave: YES
  5. On the master did you select the slaves BT in the Wifi Launcher app?: YES
  6. When the master connected to the car's BT did the Wifi launcher app started up?: YES
  7. Did the master connected to the slaves hotspot?: YES
  8. Did the AA icon appeared on the master at all (in the notification bar)?: YES
Seems like everything is working. Master says connected to Car, AA is running, but nothing shows on the Car Display. Wi-Fi Launcher says "Service is looking for car display" and vibrates twice every 3 or 4 seconds 10 or 11 times before stopping. Seems like maybe I have the wrong USB settings on the slave?

Any advice? Thanks...
I have similar problems running slave on a LG G2 with LOS 17.1.

You need to downgrade to lineageos 16 or 15 because in Android 10 the AAGateway app can't move to system/priv-app. At least this was my solution, i'm running now with LOS 15 because i have some problems with 16 that also appeared in 15 but i had solved them. Probably as I say, it works in LOS 16, but I did not want to start doing it again from scratch.
 

morpho26

Member
Apr 12, 2008
22
4
Hello,

i´ve installed AAgateway on a Huawwei P20 Lite (ANE-LX1), and it works almost perfekt.
Only Issue I have is, that if it boots up, i cant´t get it to work untill i unplug and plug in again the usb cable. Whole Device Reboot dousn´t help. Only the replug Solution seems my Car to recognize the Device.
My Slave is rooted, crdroid GSI installed and working with AAgateway 2.2.

Is there any solution e.g RESET USB PORT via shell that i can implement in Tasker or Macrodroid.

THX for some advice
 

wyt18

Senior Member
Jun 4, 2007
397
177
Hello,

i´ve installed AAgateway on a Huawwei P20 Lite (ANE-LX1), and it works almost perfekt.
Only Issue I have is, that if it boots up, i cant´t get it to work untill i unplug and plug in again the usb cable. Whole Device Reboot dousn´t help. Only the replug Solution seems my Car to recognize the Device.
My Slave is rooted, crdroid GSI installed and working with AAgateway 2.2.

Is there any solution e.g RESET USB PORT via shell that i can implement in Tasker or Macrodroid.

THX for some advice
Try toggling adb debugging via tasker. That worked for me
 

Lwyrn

Member
Mar 27, 2011
10
0
Using Rooted Samsung A8 2018 running Rooted One UI 1.0 ( Android 9 Pie ) as Slave
Using Non-Rooted Samsung Note 10+ ( Android 10 ) as master

Master is running Pie or above and slave is tethering:
  1. Running in root mode: YES
  2. If running in non-root mode, is the splashscreen visible on the car: Root ( but nothing display on car )
  3. If running in non-root mode, did you set the masters BT inside AAGW app?: Root
  4. Did the slave actually turned on the hotspot on the slave: YES
  5. On the master did you select the slaves BT in the Wifi Launcher app?: YES
  6. When the master connected to the car's BT did the Wifi launcher app started up?: YES
  7. Did the master connected to the slaves hotspot?: YES
  8. Did the AA icon appeared on the master at all (in the notification bar)?: YES
Hi all, I'm trying to run this on Sync 3.4.
When i connect the slave to the car usb, nothing happen on the slave.
The master get connected to the slave hotspot. And i get "Android auto is running" in the notification center. Also AA Wireless is locking for slave. On the master I see an app ( black screen ) that get repeatedly launched every 10-15 seconds but immediately disappear.

What can i try? Thanks
 

wyt18

Senior Member
Jun 4, 2007
397
177
Using Rooted Samsung A8 2018 running Rooted One UI 1.0 ( Android 9 Pie ) as Slave
Using Non-Rooted Samsung Note 10+ ( Android 10 ) as master

Master is running Pie or above and slave is tethering:
  1. Running in root mode: YES
  2. If running in non-root mode, is the splashscreen visible on the car: Root ( but nothing display on car )
  3. If running in non-root mode, did you set the masters BT inside AAGW app?: Root
  4. Did the slave actually turned on the hotspot on the slave: YES
  5. On the master did you select the slaves BT in the Wifi Launcher app?: YES
  6. When the master connected to the car's BT did the Wifi launcher app started up?: YES
  7. Did the master connected to the slaves hotspot?: YES
  8. Did the AA icon appeared on the master at all (in the notification bar)?: YES
Hi all, I'm trying to run this on Sync 3.4.
When i connect the slave to the car usb, nothing happen on the slave.
The master get connected to the slave hotspot. And i get "Android auto is running" in the notification center. Also AA Wireless is locking for slave. On the master I see an app ( black screen ) that get repeatedly launched every 10-15 seconds but immediately disappear.

What can i try? Thanks
Try the modified aagateway by olivluca together with his aastarter app. That worked perfectly for me

 

Lwyrn

Member
Mar 27, 2011
10
0
Try the modified aagateway by olivluca together with his aastarter app. That worked perfectly for me


Thanks, but nothing. It's the same result.
When i connect the slave to the headunit, should something appear on the headunit? Because nothing appear
 

slyyke

Senior Member
Jul 14, 2014
80
11
I have purchased the app and things. I was able to previously get everything setup with OP7pro master and OP3 slave.

However I specifically purchased the mentioned TV stick "MK809V TV stick" and the correct android version. I got to where i believe everything is setup and installed however i plug in my car and nothing happens on the head unit or the master device.

At a loss at the moment. Might try to start fresh?

Anyone have good experience setting up the TV stick?
 

mikruz

New member
Mar 19, 2021
1
0
Hello. I am having trouble with the settings in Android Auto and AAgateway. I am using Samsung GALAXY GRAND PRIME on Android 4.2 root mode and Samsung S7 on Android 8 as master not root mode. After turning on HOTSPOT on the S7, the car starts the AndroidAuto application. Then it says "AndroidAuto cannot establish a secure connection because the car is moving. Stop the car". The car is of course stopped and the engine is off. On the S7 Master Anroid Auto, the message "stop the car and restart AndroidAuto" will also appear. My car is DACIA2020. Please help. Thank you.
 
Last edited:

Pixelramp

New member
Mar 20, 2021
1
1
Hello, I just wanted to share my way, how i've managed to get it to work.
My slave is a Samung Galaxy S5 running LineageOS 17.1 (Rooted) (No Gapps).
Master is a Xiaomi mi 10 running Miui 12.2.5 Android 11 (Rooted).

First, i'm using Tasker, I Couldn't get WI-FI Launcher to work. (If you're just trying and don't want to pay for tasker, you can get a month of play pass for free. In the play pass is tasker included ;) )

I've imported the task from the first post.

1. I've installed AAGateWay 2.2 on the slave, didn't open it yet.

2. I've created the Hotspot on the slave manually and connected the Master to the slave's hotspot.

3. After confirming that the Wi-Fi Connection is working fine, I disabled the hotspot on the slave and Wi-Fi on the Master.

4. I've opened AAGateway and configured it all normally. (Selecting BT device (even the phones doesn't seem to use it anyways) activated enabled tethering, used the root mode) then exited the app via the button on the bottom right.

5. I've connected the slave via USB to the car and confirmed that the slave started the hotspot automatically.

6. Important is now, that I need to wait at least 10 seconds before activating Wi-Fi on the master and connecting to the slave.

7. If the connection is established I wait another 5 seconds before started the imported tasker task.

8. The slave should ask to use aagateway (only first time) after accepting, android auto should start.



In my case it seems like the slave just need some time in the beginning before it starts enabling the connection to the master.


I hope I could help someone to get it to work.
 
  • Like
Reactions: e6o5

tedces

New member
Mar 25, 2021
1
0
Master Android 11. SS Galaxy Fold 2 - nonrooted
Slave: Samsung Note 3, 5.0 rooted

I manage to make it work only when unlock the slave (Note 3) and with the AAGateway open.
Otherwise, the master keep trying to open Android Auto then drop right after 1s. As mentioned above, I need to open the AAGateway on Slave device, unplug then plug the usb.
Does anyone got this problem?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    when will this be available for purchase on the google play store? i refuse to support paypal and their business practices in any manner. thanks.
  • 111
    Background
    - Couple of years ago Google have launched Android Auto, but up till recently the only way to connect your device to the car/head unit was to plug in a USB cable. As of 2018 this starts to change, BUT it looks like you will need to get new hardware for this and older cars/head units won't be upgraded to support this, neither phones with older OS.

    Concept
    - Since many of us will like to have this wire free but not ready / willing or have the possibility to upgrade the units/cars/phones I have thought of a way to achieve this, by using a small auxiliary device, like for example a very cheap and basic Android TV stick, which can be plugged in/mounted in the car and which can fulfil the roll of a Wifi antenna for your car.

    This app should allow you to transform any android powered device into a Wifi receiver for your Android Auto compatible Car/Headunit. Please do not confuse Android Auto, with Android powered headunit (usually Chinese, like MTCB, MTCD, Joying, etc).

    AAGateWay Documentation.

    Beta released (04.01.2020)

    What is it?

    AAGateWay is a an app which should allow you to use an auxiliary (slave) device to connect your existing Android Auto compatible car to your phone (master) using a hotspot created on your phone.

    How to use it?

    SLAVE SETUP


    1) Install the app using XDA Labs (Only on SLAVE) : https://www.b3itlabs.com/prod.php?id=3
    2) Configure

    • FOR BOTH ROOTED AND NOT-ROOTED SLAVES
      • CASE 1: Master is running Pie or higher
        1. Pair Master and Slave over BT (do this from the normal BT settings)
        2. Open app
        3. If slave is ROOTED and ONLY if you are using a TV STICK convert the app to system app. (if app not visible after conversion, reboot device)
        4. Enable the start tethering option (If asked make sure you manually configure the hotspot, to have the name HUR and the password AndroidAutoConnect)
        5. Select the masters phone BT MAC
        6. Exit
      • CASE 2: Master is running Android 8 or lower
        1. Create a Wifi hotspot from the master
        2. Connect slave to it
        3. Reopen AAGateWay and select the masters hotspot from the "Phone Wifi SSID" list
    • Slave is ROOTED - This will give a much bigger compatibility with cars, it should work with any car/unit (but depends a lot on the slave used, read below)
    • Slave is NOT ROOTED - This mode won't work on all cars and it has caveats.


    MASTER SETUP


    • CASE 1: Master is running Pie or higher
      1. Install WiFi Launcher for HUR (https://play.google.com/store/apps/details?id=com.borconi.emil.wifilauncherforhur)
      2. Make sure WiFi Launcher is version 2.1 or higher!!!
      3. Open WiFi Launcher
      4. FOR Android 10, set permission location to ALWAYS!!!!!!
      5. Select slaves BT from the BT list and exit
      6. DO NOT ENABLE ANY OF THE OTHER OPTIONS!!!!
    • If you do not want to use WiFi Launcher you can use the following Tasker task to launch AA on any condition you want: https://drive.google.com/file/d/1UO-Z5P0oQpHEdrQjYqvSM48L1TI-K5g8/view?usp=sharing
    • CASE 2: Master is running Android 8 or lower
      1. Open Android Auto, go to Settings, scroll down tap the version 10 times, then from the 3 dotted top right corner select start headunti server.
      2. Exit Android Auto
      3. Leave the Headunit Server running
      4. When you get into the car turn on the hotspot on the master (or use Tasker, automate or anything else do that for you)



    CONNECTING
    • Go to the car, plug in the slave to the car's USB and start the car
    • Slave is ROOTED
      • Nothing should happen, car should NOT detect the phone (SLAVE) at this stage. If the car does detect the slave being connected, it means your slave doesn't allow a proper USB toggle, in which case you should try enabling non-root mode.
      • Master is Pie and above
        1. If you selected to tether from the slave, at this point you should see the slave turning on the hotspot, otherwise you might see the slave trying to connect to a Wifi network.
        2. Slave will notify master
        3. Master will automatically start WiFi Launcher
        4. Master will connect to slaves hotspot
        5. Master will start AA on the phone and notifies slave
      • Slave will enable USB
      • If you are using a phone as slave you will get a prompt if you want to use AAGW as the default app for this action, make sure you select ALWAYS ans yes. (TV stick should work automatically)
      • Projection should start
    • Slave is NOT-ROOTED (or running in non-root mode)
      • You will get a prompt to use AAGateWay for this action, make sure you select always.
      • Car should display a splah-screen saying waiting for master. (on some car's screen you might see a scrambled image)
      • After splash-screen is displayed, the slave will start tethering, or will try to connect to the masters hotspot depending on the setting.
      • Once a network connection is established between the 2 devices, you will see the AA icon turning on on the master and Android Auto should be displayed on the car's screen. It is possible that the screen will stay /turn black, if that happens, you can try to press the home button on the infotainment system, then re-open Android Auto on it.

    Troubleshoot and getting help

    As the thread has so much information it will be really nice if we can try to stick to one format of troubleshooting, by using one of this 2 templates:

    • Master is running Pie or above and slave is tethering:
      1. Running in root mode: (Yes/No)
      2. If running in non-root mode, is the splashscreen visible on the car: (Yes/No)
      3. If running in non-root mode, did you set the masters BT inside AAGW app?: (Yes/No)
      4. Did the slave actually turned on the hotspot on the slave: (Yes/No)
      5. On the master did you select the slaves BT in the Wifi Launcher app?: (Yes/No)
      6. When the master connected to the car's BT did the Wifi launcher app started up?: (Yes/No)
      7. Did the master connected to the slaves hotspot?: (Yes/No)
      8. Did the AA icon appeared on the master at all (in the notification bar)?: (Yes/No)
    • Master is running Oreo or below and master is tethering:
      1. Running in root mode: (Yes/No)
      2. If running in non-root mode, is the splashscreen visible on the car: (Yes/No)
      3. If running in non-root mode, did you set the masters BT inside AAGW app?: (Yes/No)
      4. Did you select the masters hotspot name in AAGW?: (Yes/No)
      5. Have you started the Headunit server on the master?: (Yes/No)
      6. On the master did you select the cars BT in the Wifi Launcher app?: (Yes/No)
      7. When the master connected to the car's BT did the Wifi launcher app started up (notification bar)?: (Yes/No)
      8. Did the master turned on the hotspot?: (Yes/No)
      9. Did the slave connected to the masters hotspot?: (Yes/No)

    • Getting rid of all automation and manually starting it all (regardless of Android version on master and slave):
      1. Uninstall AAGW on the master
      2. Start the headunit server from within Android Auto on the master
      3. Create a hotspot on the master
      4. Open AAGW on the slave and make sure it's not set to tether
      5. in AAGW make sure you select the masters hotspot
      6. If AAGW is set to non-root mode make sure you select the masters BT (just press the button AAGW will do a BT scan of nearby devices and you can pick it from the list)
      7. Go to the car and plug the slave in
      8. Start the car
        • If slave is running in ROOT mode, slave will first try to connect to the masters Wifi and you will see a notification on the master that AA is running, only then the car should recognise a plugged in device.
        • If the slave is running in non-root mode, first you will see a splash screen on the car, then you will see slave connects to masters Wifi (if not already connected), then you will see AA starting on the master.
    • How do I collect a bug report / logcat
      1. Open Settings > About phone.
      2. Scroll down to the Build number.
      3. Tap the Build number 7 times in quick succession until "You're now a developer" appears.
      4. Return to the Settings menu and select Developer options.
      5. At the top of the screen, make sure 'Developer options' is set to On (green).
      6. Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
      7. Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.
      8. On slave make sure you enable debugging inside AAGW, on master open Android Auto go to developer settings and make sure force logging is enabled.
      9. Reproduce the problem
      10. Hold the Power button down until the menu appears.
      11. Select Take bug report. and wait for the device to capture the bug report.
      12. Tap the 'Bug report captured' notification when it appears.
      13. Send the bug report by email to [email protected]



    Know problems, workaround:
    • - Latency & lag. This will be really down to the devices you are using. I have tested it with a MK808B Plus, it work’s ok most of the time but occasionally you will get the odd lag. I’ve also tested it with a Nexus 7 tablet, and there was no lag at all, so device does matter, as well as probably ROM.
    • - I get random disconnection. There can be 2 causes for this, one the USB connection fails between the car and the auxiliary device, or the Wifi fails between the phone and the auxiliary device. In my tests I saw a few Wifi disconnections without any reason on the MK808, but non on the Nexus. Changing the tethering option from WPA2 to Open did help with this.
    • - App is closed without error or reason. The app runs in a background process, with a minimal interaction with the foreground, some devices/OS will kill background apps. I saw this happening on Nokia and I saw this happening on OnePlus as well. Try disabling battery optimisation for AAGateWay, that might help.
    • - I just cannot get it to work… Try using a phone, that will at least give you some visual guidance. Make sure that your device connects to the phone Wifi hotspot, make sure that AA Headunit server is running on the phone (try to force stop Goolge Play Services, stop and restart the headunit server)… All fails contact me
    • - Nothing happens on the master, using Wifi Launcher for HUR app. In this case, try to manually start the headunit server on the master, and manually turn on a hotspot, then reconfigure you're slave to connect to the masters hotspot (even if the master is running Pie or higher).


    Device compatibility:
    Master:

    Any phone which normally works with Android Auto

    Slave with ROOT:
    • - Tested and know to work: - MK809V, Nexus 7 (depending on rom), Sony X Compact (depending on rom)
    • -Tested and not working as expected: Pixel 2, MK808B
    • - While root is necessary, not all phones can toggle USB port on and off by software. And there can be other problems, for example on some devices when you turn off the USB the phone loses the ability to detect the power connection as well, which is use as trigger to start the whole process. It is almost impossible to predict if a phone will be a good slave candidate or not.

    Other things
    - Xiaomi phones (MIUI makes a mess), try not to use it for Slave
    - Generally older phones (pre oreo) are more likely to work fine as a slave device.

    Any suggested slave?
    - Yes, use an MK809V TV stick, as the experience with it, is pretty slick and it should work out of the box. If you get a MK809IV try to get the one with Android 5.1.1 as the one with Android 7.1 has problems with the tethering.

    FAQ.
    Q: Can I use this with any car and phone combination?
    A: Assuming your car is already Android Auto compatible, then YES.


    Q: Can I also automate the start of the Headunit server?
    A: Only with a rooted phone, using the following shell command: am startservice -W com.google.android.projection.gearhead/com.google.android.projection.gearhead.companion.DeveloperHeadUnitNetworkService

    Q: Can I use Wifi-Direct to connect instead of WIfi?
    A: No.

    Q: Does the traffic come out from my monthly data allowance?
    A: NO, traffic between auxiliary device and phone hotspot does NOT count as internet traffic, HOWEVER if you do have other apps on the auxiliary device which download updates, etc in the background that WILL be counted as internet traffic. So I suggest double check the apps on the aux device and disable all those which aren’t needed.


    Q: Will the car/head unit provide enough power?
    A: It should provide at least 500mA that’s the standard USB current, while I cannot guarantee that will be enough in all cases, it should do, assuming you do turn off all unneeded services on the TV stick.

    Q. What about start up time?
    A. It will depend a lot on the device you are using. A low-entry TV stick boot time is about 1 minute, which can be a bit too much for an initial car setup. As mentioned earlier, these devices usually have 2 USB ports, you can for example connect the power USB port to a continues power supply in the car, in which case the boot time will be non-existent since the device is always running. If you are using a phone, the phone battery will probably hold the charge just fine for a couple of days, if you disable all apps on it and you set up a profile to go into aeroplane mode when it’s not charging. Tasker or Automate are your friends for that. If you cannot connect the TV stick to a continues power source, you might consider using a small portable power pack which powers the tv stick (should hold power for a few days) and the power pack can be charged while the car is running.

    Q. Can I decrease boot time for TV Sticks/Phones by removing all unrelated software.
    A. Yes, actually quite a lot. Once you have your configuration ready and everything is working as expected, you can uninstall/disable all packages beside this ones:
    • package:android
    • package:com.android.apkinstaller
    • package:com.android.providers.settings
    • package:com.android.packageinstaller
    • package:com.notriddle.null_launcer (or any other launcher, but NULL launcher has no memory consumption, no app drawer no nothing, perfect for headless - see: https://github.com/notriddle/null-launcher )
    • package:com.android.inputmethod.latin
    • package:com.android.settings
    • package:uk.co.borconi.emil.aagateway
    • package:com.android.shell
    • package:com.android.systemui
    Easy way to list / disable all apps will be using a computer and following commands
    Code:
     adb shell pm list packages
    This will list all installed packages
    Code:
     adb shell pm disable xxxx
    where you replace xxxx with the package name (Ex: com.android.shell )


    Q. Will using Wifi 5Ghz give me better performance?
    A. Well if both of your devices support it, SURE!

    Q. Is the source code available?
    A. Sort-of, please see: https://github.com/borconi/AAGateWay this is only for the sketch, however new version does contain code which lift restrictions on 3rd party apps in Android Auto. To prevent the abuse of this by some, further code won't be updated to GitHub, however if you want to build your own version, please do contact me for details.


    Guarantee or Warranty
    - Due to the fact that there are so many possibilities and combinations of cars, head units, slave and master devices, there is no way for me to test all of them, however if you did purchase the software and you are not able to get it to work for any reason, please email me on [email protected] and I'm more then happy to refund the purchase.


    Teaser:
    24
    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.
    22
    Updates from the Netherlands, CP & EB IT is officially opened :) next week I will start the work on the promo video then Kickstarter campaign is on....
    21
    Just got off the phone with the guys who are going to shoot the promo video, we should have that by no later then 23rd of August done, so I really hope that by that day the kick-starter will be live.
    21
    Hi guys.

    Sorry to be radio silent, indeed I was relatively busy with HUR and OBD2AA as well as other non Android Auto related work. Today I have finally managed to push out a stable release for HUR, and obd2aa is also doing pretty well, so in the next period I will continue to develop the AAGateWay, that being said my schedule looks like this:

    - This weekend, working all weekend, preparing photos from 5 different events across the UK so that will tied me up till Tuesday
    - Wednesday morning hitting the road (travelling to Romania - 3 days road trip)
    - I'm not sure how much I will be in Romania
    - October 20 I'm flying to the States for 2 weeks.

    So as you can see I will be quite a lot on the road, but I will take my Sony headunit and some dev tools with me to Romania and will carry on working, my target is to have a stable version of this app before I fly to the states.

    I will try to put together a list of most common problems I saw here and wishes tomorrow so you can all see and know what's happening as well as input new ideas if you have any.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone