• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Android 4.1+]Proxy/GateWay for Android Auto

Search This thread

deslash14

New member
Dec 14, 2013
3
0
Master: Pixel 4 - No Root
Slave: S7 - Root and no root

tested with a rooted and non rooted slave.
whatever i do.. everything goes perfect till AA launches on Car Display. it makes connection and then breaks down.
Only thing i see is that Usb connection mode changes itself... it gets toggled to "file transfer" but looks like AA? changes it back to "charging phone"
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,208
2,944
Tg. Secuiesc / Kezdivasarhely
So the longer post I have promised.

The app seems to be working now on Orange Pi, which is great and performance it's good as well.

Both @Snirpo and myself received our Rock Pi S boards and we are testing them now, while some adaption is needed, it does look like this board will be a much better choice. They have a smaller factor size compared to the Orange Pi Zero 2 and they seems to be a better build quality. One of the issues was that my Orange Pi Zero 2 I used in test was running super hot sometimes at 85 C which is NOT OK and NOT normal. The Rock Pi S seems to be much cooler running at about 40 C without any heat sink or so. Also I've exchanged a few emails with Radaxa the manufacturer of Rock Pi S and it looks they can give better service compared to Orange Pi. Also Rock Pi S power draw is really low, which is good as some cars / units have a limited power output of 500mA. Sadly it's not all perfect yet, for example we could not get a Sony headunit to recognise the board, but we halted further investigation since it was an Orange Pi Zero board and it really looks like we are going to go with the Rock Pi S, so after spending 2 days trying to work out the reason why the Sony unit does not detect the Orange Pi board with decide to rest it and re-visit the issue when we have modified the Rock Pi S to fit our needs. The good news is that you won't need any WiFi Launcher or similar app to get it working over WiFi, the experience will be seamless. Another good thing is that the Rock Pi S board have a promising boot time, even from SD card it takes about 15 seconds to boot up which probably will be further reduced a bit when we start using the NAND on the board.

What is happening next?
- If everything goes well I hope next week I can travel to the Netherlands and set up a company between @Snirpo and myself. As this was a joint effort from both of us we will like to do this as equal partners.
- This/next week I will be looking for someone who can shoot a professional demo video (need some good PR for it)
- In parallel we will also build a simple website for the product.
- Once all above steps are completed we are going to launch the campaign (need to decide if we are going to use Kick-starter or Indiegogo)

While we have the app running now, there are still a few things we need to iron out, like the configuration, stripping the image to make it as small as possible, implementing OTA for future updates and so on.

What I can tell you already is that the campaign will need to raise enough funds for at least 3000 pcs, that is a given. While the price not set in stone we are hoping to be able to offer the product for about $65, but please do not hold me to it yet as I'm waiting for more input from the factory regarding USB cable costs, packing and other small bits and bobs which can influence this.

This week I hopefully I should know exactly when I will travel to NL to set up the company and I will update you with dates, from there everything should start to pick up in peace.
 

pavichokche

Member
Aug 10, 2018
23
2
What I can tell you already is that the campaign will need to raise enough funds for at least 3000 pcs, that is a given. While the price not set in stone we are hoping to be able to offer the product for about $65, but please do not hold me to it yet as I'm waiting for more input from the factory regarding USB cable costs, packing and other small bits and bobs which can influence this.

Wow, all amazing news. Fantastic work, guys!
The only thing I was thinking is this mention of USB cables. I'm sure it won't affect the cost of the final product much, especially when doing a bulk order, but it would be nice if you can offer people a cheaper version without "bells and whistles" like cables or extra packaging or anything like that (maybe even no box for the board or anything). I think many people wouldn't mind a partially or fully DIY assembly process to make the product more affordable in the end.

What I mean is maybe you can have the full product for $65, and optionally just the board for $50 or $55 (for example), you know?
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,208
2,944
Tg. Secuiesc / Kezdivasarhely
Wow, all amazing news. Fantastic work, guys!
The only thing I was thinking is this mention of USB cables. I'm sure it won't affect the cost of the final product much, especially when doing a bulk order, but it would be nice if you can offer people a cheaper version without "bells and whistles" like cables or extra packaging or anything like that (maybe even no box for the board or anything). I think many people wouldn't mind a partially or fully DIY assembly process to make the product more affordable in the end.

What I mean is maybe you can have the full product for $65, and optionally just the board for $50 or $55 (for example), you know?
Ish a USB cable with USB-IF certificate which has smaller chance of causing can cost easily $10+

Yes I did consider both options and will take input from you guys as well.
 

LLStarks

Senior Member
Jun 1, 2012
1,534
580
Ish a USB cable with USB-IF certificate which has smaller chance of causing can cost easily $10+

Yes I did consider both options and will take input from you guys as well.
Awesome. Will there be a case? Only half-decent one I could find was this one. The acrylic one floating around provides very little protection aside from the top and bottom to prevent shorts.

Something more purpose-built may be needed since the buttons are extremely exposed unless carefully recessed.
 
Last edited:

Emil Borconi

Recognized Developer
Feb 18, 2008
3,208
2,944
Tg. Secuiesc / Kezdivasarhely
Awesome. Will there be a case? Only half-decent one I could find was this one. The acrylic one floating around provides very little protection aside from the top and bottom to prevent shorts.
Yes, custom design, probably high quality plastic, as metal case will be a bit odd. We are dropping the Ethernet port as well as there is no need for that. If it does not affect the price I will like to turn the USB port as well to reduce the size even more.
 

pdanders11

Senior Member
Aug 13, 2012
108
2
Just curious why you aren't sticking with the Rock PI S for hardware if it works? Are there hardware mods required to make this work better along with the desire to make smaller? Any plans to provide development versions of SW for the Rock Pi until your custom board is done?

Very cool project. Huge advantage having common hardware and not supporting multiple phones and OSs.
 

nogardeht

New member
Apr 15, 2011
2
0
So the longer post I have promised.

The app seems to be working now on Orange Pi, which is great and performance it's good as well.

Both @Snirpo and myself received our Rock Pi S boards and we are testing them now, while some adaption is needed, it does look like this board will be a much better choice. They have a smaller factor size compared to the Orange Pi Zero 2 and they seems to be a better build quality. One of the issues was that my Orange Pi Zero 2 I used in test was running super hot sometimes at 85 C which is NOT OK and NOT normal. The Rock Pi S seems to be much cooler running at about 40 C without any heat sink or so. Also I've exchanged a few emails with Radaxa the manufacturer of Rock Pi S and it looks they can give better service compared to Orange Pi. Also Rock Pi S power draw is really low, which is good as some cars / units have a limited power output of 500mA. Sadly it's not all perfect yet, for example we could not get a Sony headunit to recognise the board, but we halted further investigation since it was an Orange Pi Zero board and it really looks like we are going to go with the Rock Pi S, so after spending 2 days trying to work out the reason why the Sony unit does not detect the Orange Pi board with decide to rest it and re-visit the issue when we have modified the Rock Pi S to fit our needs. The good news is that you won't need any WiFi Launcher or similar app to get it working over WiFi, the experience will be seamless. Another good thing is that the Rock Pi S board have a promising boot time, even from SD card it takes about 15 seconds to boot up which probably will be further reduced a bit when we start using the NAND on the board.

What is happening next?
- If everything goes well I hope next week I can travel to the Netherlands and set up a company between @Snirpo and myself. As this was a joint effort from both of us we will like to do this as equal partners.
- This/next week I will be looking for someone who can shoot a professional demo video (need some good PR for it)
- In parallel we will also build a simple website for the product.
- Once all above steps are completed we are going to launch the campaign (need to decide if we are going to use Kick-starter or Indiegogo)

While we have the app running now, there are still a few things we need to iron out, like the configuration, stripping the image to make it as small as possible, implementing OTA for future updates and so on.

What I can tell you already is that the campaign will need to raise enough funds for at least 3000 pcs, that is a given. While the price not set in stone we are hoping to be able to offer the product for about $65, but please do not hold me to it yet as I'm waiting for more input from the factory regarding USB cable costs, packing and other small bits and bobs which can influence this.

This week I hopefully I should know exactly when I will travel to NL to set up the company and I will update you with dates, from there everything should start to pick up in peace.

I would totally back this project on kick starter or indiegogo, I have odroids and raspberrys around, and I was looking for a setup that would make my life so much easier with this kind of setup for my car. Hope you can do it.
 

Emba7a

New member
Jun 25, 2017
2
0
Duster and Dacia Duster and [Android 4.1+]Proxy/GateWay for Android Auto

I am very interested in the solution you provide. For several weeks I have been looking for an option for wireless connectivity and re-reading the option you provided.
I have Dacia Duster and since I noticed that you are from the country she is from.
"I can't handle not to ask you before i start beating my head in the wall "
Did you ever test this solution with Dacia Media NAV v2 and is it compatible (i can use it with USB)
------------
Duster
Phone slave LG g2 ( will change it soon with some Android stick in stock hear in BG )
Main phone One Plus 7 Pro

Best regards Emil
------
Ooo I just saw the latest topics,
I can't wait to get ready

Good Luck
 
Last edited:

shmykelsa

Senior Member
Nov 21, 2013
941
615
25
Lecce
OnePlus 6T
Samsung Galaxy Z Fold3
So the longer post I have promised.

The app seems to be working now on Orange Pi, which is great and performance it's good as well.

Both @Snirpo and myself received our Rock Pi S boards and we are testing them now, while some adaption is needed, it does look like this board will be a much better choice. They have a smaller factor size compared to the Orange Pi Zero 2 and they seems to be a better build quality. One of the issues was that my Orange Pi Zero 2 I used in test was running super hot sometimes at 85 C which is NOT OK and NOT normal. The Rock Pi S seems to be much cooler running at about 40 C without any heat sink or so. Also I've exchanged a few emails with Radaxa the manufacturer of Rock Pi S and it looks they can give better service compared to Orange Pi. Also Rock Pi S power draw is really low, which is good as some cars / units have a limited power output of 500mA. Sadly it's not all perfect yet, for example we could not get a Sony headunit to recognise the board, but we halted further investigation since it was an Orange Pi Zero board and it really looks like we are going to go with the Rock Pi S, so after spending 2 days trying to work out the reason why the Sony unit does not detect the Orange Pi board with decide to rest it and re-visit the issue when we have modified the Rock Pi S to fit our needs. The good news is that you won't need any WiFi Launcher or similar app to get it working over WiFi, the experience will be seamless. Another good thing is that the Rock Pi S board have a promising boot time, even from SD card it takes about 15 seconds to boot up which probably will be further reduced a bit when we start using the NAND on the board.

What is happening next?
- If everything goes well I hope next week I can travel to the Netherlands and set up a company between @Snirpo and myself. As this was a joint effort from both of us we will like to do this as equal partners.
- This/next week I will be looking for someone who can shoot a professional demo video (need some good PR for it)
- In parallel we will also build a simple website for the product.
- Once all above steps are completed we are going to launch the campaign (need to decide if we are going to use Kick-starter or Indiegogo)

While we have the app running now, there are still a few things we need to iron out, like the configuration, stripping the image to make it as small as possible, implementing OTA for future updates and so on.

What I can tell you already is that the campaign will need to raise enough funds for at least 3000 pcs, that is a given. While the price not set in stone we are hoping to be able to offer the product for about $65, but please do not hold me to it yet as I'm waiting for more input from the factory regarding USB cable costs, packing and other small bits and bobs which can influence this.

This week I hopefully I should know exactly when I will travel to NL to set up the company and I will update you with dates, from there everything should start to pick up in peace.

This looks very promising and I so hope this gets all the way through, although I have three (let's say two and a half) concerns:

-What about Android version? Will there be a minimum Android version to make this all work? Or will it be pie and above?
-In a case scenario where Google will change Android Auto Wireless connection logic, will the board be ready to have firmware/software updates? If the answer is yes, how hard will it be, giving that the board will probably not have some physical buttons to get into recovery/BIOS/UEFI mode or something
-Probably the answer will be no, but will this solution require to have a rooted master?
 

Raendy

New member
Apr 23, 2013
1
0
Internet connection

Great work Emil! Really looking forward for the Rock Pi Dongle since I can't make it work via Master/Slave Phone.

One question regarding Internet connection - official Android Auto Wireless uses the car's internet connection since it needs to be connected to car's wifi if I understand correctly. How will this work with your dongle?

Best regards and keep up the good work
Randy
 

Zeooo

Member
Dec 3, 2007
10
1
Great work @Emil Borconi!

I've been setting up AAGateway and it seems to work even though the screen looks distorted. I've been reading posts and searching all afternoon but I can't find the solution. Can anybody help me?
My devices are:
Samsung S9 not rooted (master)
Samsung S7 not rooted (slave)
Car group Vag
 

ScrapMaker

Senior Member
Jan 23, 2008
973
84
Great work @Emil Borconi!

I've been setting up AAGateway and it seems to work even though the screen looks distorted. I've been reading posts and searching all afternoon but I can't find the solution. Can anybody help me?
My devices are:
Samsung S9 not rooted (master)
Samsung S7 not rooted (slave)
Car group Vag

Heyo, I'm curious how you got this working. I've only had VERY minor success when starting the AA headunit device manually. In this case on only get audio, but I can confirm it's going over WiFi.


aaaaahhh frustratingly the issue with video was having USB Debugging on. I just leave this enabled since I use it so much. After disabling that, I was able to get video working on both phones as master-vs-slave. Though I still could not ever get Wifi Launcher to work. Additionally, I'm getting much different behavior between the Alpha, Beta, and Stable releases for both apps.

Master: Pixel 4 XL (Rooted) currently on Android 11 Beta 3, but it's never worked on any version.
Slave: Samsung S9+, not rooted

- My goal is to have the Master provide the hotspot, but the slave app REALLY does not want you to do this. I have Tasker stuff set up to turn on a hotspot, etc, so I'm already set on that.
- When I connect the slave to the car, it turns OFF Wi-Fi (even when I have specified to not tether, and to use Master SSID.) It does turn on Bluetooth.
- When I unplug the slave, it turns OFF Bluetooth. This seems odd.
- The devices never attempt a real BT connection. I assume this is to trigger the master app to load up the AA wifi developer server. I can force this manually, but then I have to fiddle with internet sharing, etc, and it gets all wonky real quick. Feels like BT is not a good mechanism for this.
* I have the master BT selection set to the slave phone, and I also have entered the master's BT MAC properly into the slave app.
- Regardless of what settings I use, the slave does put the banner on the car screen, IE waiting for master to connect.
- I've managed to make the master pop up the AA questionnaire stuff once, using the official method where the slave has its own hotspot, but after I answer a few questions, it opens up the Assistant, then ultimately fails, because the internet offered by the Slave is not good enough, and I can't force it onto any Wi-Fi.

It just feels like there should be a few more toggles/options that are more-clearly labeled. I would imagine MOST people would want to source the hotspot from their main phone, instead of having to find a SIM/hotspot contract for an old device. Is this the default use-case, or am I missing something obvious here?

I really don't want to use the slave device to create the hotspot, but since that doesn't work either, I'll use this template:

Master is running Pie or above and slave is tethering:
Running in root mode: (Master=yes Slave=no)
If running in non-root mode, is the splashscreen visible on the car: (Yes)
If running in non-root mode, did you set the masters BT inside AAGW app?: (Yes)
Did the slave actually turned on the hotspot on the slave: (No)
On the master did you select the slaves 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?: (No)
Did the AA icon appeared on the master at all (in the notification bar)?: (No)

Even when I start the HU server manually and get audio (no video,) the quality is much lower. I'd say the comparison is about 320kbps to 128kbps MP3. I can easily switch the cable across to the master and immediately hear the massive quality increase. Do you think this will improve with dedicated hardware, or is this simply a limitation of wireless AA? It's very noticeable.
 
Last edited:

lorilucille9

Senior Member
Apr 15, 2013
101
12
@Emil Just received my MK809V TV stick today and I'm struggling with getting AAGateway installed on it thru XDA labs. I paid for the app previously and tried it on my other phone with no success. Now I'm trying to log into XDA labs to download the app on the TV stick and it keeps saying invalid username/password but I know it's correct. Any one else have this issue or advice/trick to try to get this to install? Thanks in advance for any help!
 
Last edited:

Rag3

Member
Sep 5, 2008
27
5
@Emil Just received my MK809V TV stick today and I'm struggling with getting AAGateway installed on it thru XDA labs. I paid for the app previously and tried it on my other phone with no success. Now I'm trying to log into XDA labs to download the app on the TV stick and it keeps saying invalid username/password but I know it's correct. Any one else have this issue or advice/trick to try to get this to install? Thanks in advance for any help!

This is known behavior of the xda app on older android versions. Same here.
I install aagw on my master, copy the apk and uninstall it again.
 
  • Like
Reactions: lorilucille9

Top Liked Posts

  • There are no posts matching your filters.
  • 112
    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.