[Android 4.1+]Proxy/GateWay for Android Auto

Search This thread

Emil Borconi

Recognized Developer
Feb 18, 2008
3,278
3,137
Tg. Secuiesc / Kezdivasarhely
As promised more updates (albeit I haven't done any work today). @Snirpo had some really god progress on Linux so much so that it makes the idea of custom building Android for this boards almost totally pointless. I'll have a chat with him on how see things, but since running this app on Linux will be preferred over Android (way less overhead and much lighter OS) I might stop in building a custom Android ROM and focus more on improving the current app. Don't get me wrong the board and kickstarter idea is going ahead, but as it looks now it makes much more sense to stick with the Linux build over Android.
I'll keep you all posted.
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,278
3,137
Tg. Secuiesc / Kezdivasarhely
As promised more updates (albeit I haven't done any work today). @Snirpo had some really god progress on Linux so much so that it makes the idea of custom building Android for this boards almost totally pointless. I'll have a chat with him on how see things, but since running this app on Linux will be preferred over Android (way less overhead and much lighter OS) I might stop in building a custom Android ROM and focus more on improving the current app. Don't get me wrong the board and kickstarter idea is going ahead, but as it looks now it makes much more sense to stick with the Linux build over Android.
I'll keep you all posted.
 

xjust

Senior Member
Apr 5, 2014
73
14
so a little update. beta 2.0.8 crashes on android galaxy a5 2014
alpha 1.0 works great.. strange
 

Reli4nth

Senior Member
May 7, 2013
443
207
Madrid
I managed to make it work, a bit "laggy" but stable.

SLAVE:
LG G6 (Android 9) Rooted with Magisk
Tethering from Slave
App version 2.0.8

MASTER:
Oneplus 6T (Android 10) Rooted with Magisk
Connecting to slave hotspot
Using tasker profile to start AA

The only problem is that AAGateway doesn't reliably start the hotspot on the slave, so I use tasker for that aswell. The connection is stable, but a bit choppy, and the Google assistant doesn't seem to work (partially, as some commands work sometimes).
Keep it up!, looking for that kickstarter project to be a thing :D
 

pavichokche

Member
Aug 10, 2018
38
3
I managed to make it work, a bit "laggy" but stable.

SLAVE:
LG G6 (Android 9) Rooted with Magisk
Tethering from Slave
App version 2.0.8

MASTER:
Oneplus 6T (Android 10) Rooted with Magisk
Connecting to slave hotspot
Using tasker profile to start AA

The only problem is that AAGateway doesn't reliably start the hotspot on the slave, so I use tasker for that aswell. The connection is stable, but a bit choppy, and the Google assistant doesn't seem to work (partially, as some commands work sometimes).
Keep it up!, looking for that kickstarter project to be a thing :D

Try running the hotspot in 5Ghz mode instead of 2.4GHz, I found that smoother on one device.
 

lonsdaleite

Member
Jul 18, 2015
19
0
Slave: HTC M8, Lineage OS 16.0 (I also tried 14.1), rooted
Master: Samsung Galaxy S9+, Android 10, NOT rooted
Car: Ford Focus 3 with Sync 3 3.0
AAGateWay 2.0.8

Root mode: the app restarts every few seconds, so it doesn't work at all.
Non root mode: I entered BT MAC address and connected slave to the car. Ford's screen shows "Waiting for device"; Slave's notification shows "Connection established"; master connects to slave (I tried both master's tethering and slave's tethering), but there is no reaction on master. If I install WiFi Launcher on master, it makes master connect to slave and Android Auto pops up for a 0.5 sec, but nothing else.

What's wrong? I spent ~4 hours in my car and I really tired.
I've even tried to switch phones (samsung as slave and htc as master), exactly the same behaviour.
 
Last edited:

jimsey

Senior Member
Oct 14, 2007
362
72
Lancashire
Hello JIMSEY
I think we have the same car : peugeot 5008 . I succeeded in making AA Gateway 2.08 to work. My configuration :...

thanks.. i've got it working tonight but using wifi launcher rather than tasker, scenario 1 ( slave as hotspot)

i could not get the tasker script from page263 to work

hopefully it won't stop working in a few days :)
 
Last edited:

lonsdaleite

Member
Jul 18, 2015
19
0
Slave: HTC M8, Lineage OS 16.0 (I also tried 14.1), rooted
Master: Samsung Galaxy S9+, Android 10, NOT rooted
Car: Ford Focus 3 with Sync 3 3.0
AAGateWay 2.0.8

Root mode: the app restarts every few seconds, so it doesn't work at all.
Non root mode: I entered BT MAC address and connected slave to the car. Ford's screen shows "Waiting for device"; Slave's notification shows "Connection established"; master connects to slave (I tried both master's tethering and slave's tethering), but there is no reaction on master. If I install WiFi Launcher on master, it makes master connect to slave and Android Auto pops up for a 0.5 sec, but nothing else.

What's wrong? I spent ~4 hours in my car and I really tired.
I've even tried to switch phones (samsung as slave and htc as master), exactly the same behaviour.

I tried AAGW 1.0 alpha and it works! So I'd like to try 2.0.4, does somebody has .apk?
 

krlosmt

New member
Feb 19, 2018
4
0
Master : Redmi Note 8 pro (no root)
Salve: Samsung note 9 ( no root)
And vice versa

Whenever I connect the salve tô the Head unit (2017 VW Golf mib2) the screen says the following .
"Please check If confirmation is required on the mobile device..."
Even when the Master is turned off.

Slave says conection stablished
Master says running...
 

Lucas_Skyline

Senior Member
May 11, 2011
153
15
Fortaleza - CE
Slave: Galaxy S2 (I9100) with custom room (Resurrection Remix, Android 7.1.2, rooted)
Master: Samsung Galaxy S10+ (G975F Android 10)
Car: VW Polo 2020 with Composition Touch and App Conect
AAGateWay 2.0.8

I tried both ways:
slave is tethering: my Galaxy S10+ does not connect to the wifi on the Galaxy S2, because the IMEI is broken and it does not have a SIM card. The S2 is not solving IP addresses and the S10 refuses to connect, even if I turn mobile data off.

Then I tried master tethering:
Running in root mode: slave yes, master no
Did you select the masters hotspot name in AAGW?: (Yes)
Have you started the Headunit server on the master?: (Yes)
On the master did you select the cars BT in the Wifi Launcher app?: (Yes)
When the master connected to the car's BT did the Wifi launcher app started up (notification bar)?: (I think so, not entirely sure)
Did the master turned on the hotspot?: My master (S10+) does not have the "Enable start tethering" option, so I turned the hotspot myself and connected the slave to it manually.
Did the slave connected to the masters hotspot?: Yes, manually.

When I connect the USB cable on the slave, Master blinks, but the slave force closes the AAGateWay app and disconnect from the hotspot on Master, then my HeadUnit says there's a connection problem.

Is there any reason for this force close/disconnection? Am I doing something wrong?

Thank you!
 

Hyce83

New member
Mar 20, 2020
1
0
Hi Everyone, appreciate a little help here too.

Running in root mode: Yes

* Did the slave actually turned on the hotspot on the slave: Yes

* On the master did you select the cars BT in the Wifi Launcher app?: Yes

* When the master connected to the car's BT did the Wifi launcher app started up?: Yes

* Did the master connected to the slaves hotspot?: Yes

* Did the AA icon appeared on the master at all (in the notification bar)?: No

Slave: Samsung Galaxy S4-I9505 (rooted with Lineage OS16)
Master: Samsung Galaxy Note 10+ (Not Rooted)

Car: Honda Civic X

I have been tinkering over the past few days but doesnt seem like slave and master is talking to each other apart from being connected via slave hotspot or master hotspot.

I have tried manually setting up the hotspot on slave and connecting master to the tether. Then connecting the usb cable onto my car unit. Nothing happens except that theres an message on my car unit saying the connected phone is not android auto compatible. Unsure if any same car users can share their advice.

Thanks in advance!

Sent from my SM-N975F using Tapatalk
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,278
3,137
Tg. Secuiesc / Kezdivasarhely
Hi guys.
As promised more updates will follow. The embedded board will run on Linux (this is now 95% sure) I will be making a small config app for the phone as we want the board to be simple plug and play, however some config should be achievable using a small app on the phone. This means I won't be working too much on the board side and I will be focusing on improving / fixing the app as much as possible. I also want to check if I can implement the remote connection from the slave without modifying the slaves BT stack (that will mean no more WiFi Launcher on the master will be needed).

I need to tidy up a few loose ends this morning, but do expect more activity from me during the day / week.
 

morpho26

Member
Apr 12, 2008
22
4
Hi guys.
As promised more updates will follow. The embedded board will run on Linux (this is now 95% sure) I will be making a small config app for the phone as we want the board to be simple plug and play, however some config should be achievable using a small app on the phone. This means I won't be working too much on the board side and I will be focusing on improving / fixing the app as much as possible. I also want to check if I can implement the remote connection from the slave without modifying the slaves BT stack (that will mean no more WiFi Launcher on the master will be needed).

I need to tidy up a few loose ends this morning, but do expect more activity from me during the day / week.

Hi Emil,

for me it works much reliable a MK809 4k Stick well.
But of course i‘m also interested in a linux version.

I have here a Orange Pi Zero Plus (H5) Board.

If you need somebody for testing, i would be pleased to help out.
 

LLStarks

Senior Member
Jun 1, 2012
2,258
1,676
I'll probably pick up the Orange Pi Zero Plus2 H5 and see what I can do with it. Just messing around. Should be susceptible to every rooting attack. Kingo, King, Pingpong, etc.

Just wish there was a slim case and not the double-height to accommodate a daughterboard I don't need.
 
Last edited:

lancer1991

Member
May 21, 2011
45
4
Anyone care to share with me an older beta as I'm having crap luck with 2.0.8. I posted a few weeks back my experiences and while I had a couple successes it's just not wanting to work at all anymore whatever I try. I sent a PM to Emil but no response to try and get another version.
 

pavichokche

Member
Aug 10, 2018
38
3
Anyone care to share with me an older beta as I'm having crap luck with 2.0.8. I posted a few weeks back my experiences and while I had a couple successes it's just not wanting to work at all anymore whatever I try. I sent a PM to Emil but no response to try and get another version.
You should send Emil an email, he shares it on one of these forum pages, and he'll send you all the previous versions.
 
  • Like
Reactions: lancer1991

pacpac56

New member
Mar 24, 2020
2
0
hello
i tried but i have this message on my headunit

"the connected device does not support USB functions"

sorry for my english, im french
 

popy2006

Senior Member
Mar 22, 2007
1,440
240
Hi guys.
As promised more updates will follow. The embedded board will run on Linux (this is now 95% sure) I will be making a small config app for the phone as we want the board to be simple plug and play, however some config should be achievable using a small app on the phone. This means I won't be working too much on the board side and I will be focusing on improving / fixing the app as much as possible. I also want to check if I can implement the remote connection from the slave without modifying the slaves BT stack (that will mean no more WiFi Launcher on the master will be needed).

I need to tidy up a few loose ends this morning, but do expect more activity from me during the day / week.
Hi Emil,

Following this for months now and had little success on my 2016 VW polo and an old lg g4.

android auto wireless is launched in 33 additional country's. Does this have any positive impact on aagateway development?

Looking forward to an Linux based client.
Are there any news on this?

Thank you

Gesendet von meinem ONEPLUS A6013 mit Tapatalk
 
  • Like
Reactions: krlosmt

mac5079

New member
Apr 1, 2020
2
0
I got it working on a rooted S8 with an S10 master and an AUDI MMI2 Navigation Plus head unit. I had previously configured the S8 as a permanent in car phone. I made it so that it powers on when it receives USB power and shuts down when it loses USB power. Unfortunately it appears that the slave has to be ready before the master connects to the car Bluetooth or it will not establish the AA over wifi connection. Is there a workaround for this? I also noticed that when playing music through the connection it occasionally cuts the sound for a fraction of a second.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 114
    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 borconie@gmail.com



    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 borconie@gmail.com 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.