yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] techied:
Here's what I was missing:

Intent in Tasker needs to be set to Target "Activity"

Everything else worked perfectly!

Fixed link: https://taskernet.com/shares/?user=...lKsL6tk=&id=Profile:Wifi+Launcher+Replacement
[Paid Software Announcement and Discussion] josan1990:
Tested and it doesn't work, my slave doesn't do anything in the car, he doesn't even activate the AP or anything, maybe without root it doesn't work? The car doesn't detect anything when I connect the slave, I activate the AP manually, the master connects to the AP, tries to launch AA when it connects to the car's BT, but it doesn't do anything else.

On the other hand, Tasker works perfectly (with the new version of AAGateway, but keeps closing automatically).

I think I'll have to enable the debugger and see if I get the trace that stops the service.

Has anyone debugged AAGateway?
[Paid Software Announcement and Discussion] sibesaver:
That's awesome! Sorry about that oversitght in my post. I will edit it in case someone comes across it later.
[Paid Software Announcement and Discussion] techied:
Now that I can get the devices to connect reliably, the only issue I have left is keeping them connected... They sometimes disconnect at random.

But I think that may be related to Pournelle's Law
[Paid Software Announcement and Discussion] brooc:
I now am able to get the splash screen to show up with 2.0.4 and the master connects to the slave. It even starts Android Auto, but then the splash turns to a black screen and that's it. I don't actually see anything on the head unit.

Making progress, but very slowly.

Still not working...
[Paid Software Announcement and Discussion] sibesaver:
I have the issue of the splash screen never closing. I have to hit the home/apps button on my head unit and then click Android Auto to get into the AA interface. I set my music to auto-resume inside AA in order to know when to click the home button (after a full connection was established).
[Paid Software Announcement and Discussion] brooc:
I think I tried restarting AA on the head unit, but I'll try again.

I wish this whole thing would be more reliable...
[Paid Software Announcement and Discussion] sibesaver:
I think that's why the dev is taking a hardware approach now. Too many differences in devices and software in play to make it 100%. Even with dedicated hardware, I think the variety of head units/cars is still going to be an issue.
[Paid Software Announcement and Discussion] badsmoke:
[MENTION=1946425]josan1990[/MENTION]

can you please me send also the version to me, unfortunately I have no luck with version 2.0.8 and tasker
[Paid Software Announcement and Discussion] Reli4nth:
If someone can PM me version 2.0.4 I'd appreciate it. No luck with 2.0.8, the car doesn't recognize the connected phone. I tried my Galaxy S2 with Android 4.1, 4.4, 5.1 and 7.1
[Paid Software Announcement and Discussion] brooc:
Good news. Tonight after getting the black screen again I did try to exit AA on the head unit and go back and it finally worked.

My setup is a Pixel 3 (master), Nexus 5X (slave) and I think that either WiFi Launcher or Tasker works (I have them both installed). I think I got to the black screen with both of them. This works with version 2.0.4.
[Paid Software Announcement and Discussion] josan1990:
No ROOT?
[Paid Software Announcement and Discussion] brooc:
No root
[Paid Software Announcement and Discussion] josan1990:
In my headunit impossible, If I'm not root the car unit doesn't do anything when I connect the master to the slave
[Paid Software Announcement and Discussion] LLStarks:
I've been able to get 2.0.2 working but only in non-root mode. Root mode in general seems to have trouble starting the hotspot on my slave and getting the Honda to recognize the USB connection at the right moment.

Master: OnePlus 7T Pro

Slave: Pixel 2 XL

Headunit: Honda
[Paid Software Announcement and Discussion] sythelthra:
I am also having trouble. After reading this thread, it seems you need 2.0.4 to make it work.

Where do I get this version?
[Paid Software Announcement and Discussion] josan1990:
Umm, can you upload a screenshot of the app?

I think I have the 2.0.4 version but I don't have any non-root option, I think it's older
[Paid Software Announcement and Discussion] epsonix:
For me (LG G7 fit A9 master, MK809IV TVStick A5.1.1 rooted, AR Giulia) 2.0.4 does not work in any case. 2.0.8 at least setup and start hotspot from slave/conncetcion from master, though often freezes slave totally - probably gets stuck on next step. Looking forward for future versions, for now giving up.
[Paid Software Announcement and Discussion] larsaeaeae:
I'd like to have a pm/mail/link for version 2.0.4 too, just bought this but got no luck with a rooted android 8.1 nexus 5x and a stock android 10 pixel 3.. :(
[Paid Software Announcement and Discussion] rewen:
This is great. I was struggling to find out what's up with this project.. it almost needs its own forum, or at least add this to the main post.

I'm all for a dedicated device tailored towards this functionality. Happy to pay for it.
[Paid Software Announcement and Discussion] apoorvchandra:
I just downloaded 2.0.8 and I get Car connection succesful on the slave but nothing happens on the master, even when I try to manually connect to the master's hotspot (or the slave hotspot) and manually start the head unit server.

(Pixel 4 master, 10, non rooted, Pixel 3a slave, 10, non rooted.)

Can someone also PM me the 2.0.4 link APK?
[Paid Software Announcement and Discussion] lorilucille9:
Can someone send me the link also please?
[Paid Software Announcement and Discussion] smoki3:
Maybe emil can push it to xda again?

Gesendet von meinem GM1913 mit Tapatalk
[Paid Software Announcement and Discussion] Golubev:
How to find out MAC address of the car BT?
[Paid Software Announcement and Discussion] Shafeey:
Edit: Worked few times with reboot. But not consistently.

I could connect to android auto successfully with the latest version (2.0.8) from XDA Labs with Tasker on Master.

Master: Galaxy S9+ on Android 10 with Tasker.

Slave: Pixel 5x on Pie with 2.0.8 running hotspot.

I set up the Wifi setting in the Master to connect to hotspot network (HUR) with a static IP. My slave always uses the same subnet range when creating hotspot (192.168.43.1 in my case).

Then I modified the tasker profile that was mentioned here to set %hotspotipaddr to 192.168.43.1.
[Paid Software Announcement and Discussion] Emil Borconi:
Hi guys.

Sorry for being radio silent, last few weeks I was working 10-12 hours per day, 7 days a week to finish my other project, but sadly I'm still not done, but not that far off either.

However since I got really tired of doing the same work for such a long period of time I've decided I will dedicate the weekend to this project.

My current focus is to build a plug&play device, way to many possibilities to try to make it work for all case scenarios.

As I have mentioned it earlier I've teamed up with [MENTION=407678]Snirpo[/MENTION] so we can bring this product to you, he is working on Linux angle and I'm suppose to work on Android one.

I have received my Orange Pi Zero Plus2 from China as well as one which was landed to me 2 weeks ago. It turns out the same board has 2 different CPU's some boards are coming with a H3 and others are coming with a H5 CPU, they both do come with an EMMC.

Wihile Android is available for this devices, booting them up is not as simple as it sounds :) well not always. The H3 device can be booted more easily with H3Droid image, which is a nice small image based on Android 4.4, it can even be flash to the EMMC, so the boot time of the device is about 20-25 seconds. This will be ideal to work with, but sadly the hotspot is not working in this build so I can't use it. The H5 needs to be booted with the original Android 5.1 image, which works, but it has no root and currently I wasn't able to figure out how to activate the OTG function on the board, but on this one tethering is working. The original Android 4.4 images is damaged on Orange Pi website so I can't test that one, which leads me with no other choice but to build the Android OS myself. I have never done this before, so I still need to follow loads of tutorials and to learn how to do it, I spent most of my day trying to set up a Linux build machine for this task.

[MENTION=407678]Snirpo[/MENTION] also hit a bit of stumbling block with porting UsbAccessory to Linux which is a crucial bit for this to work.

While I might not be active on the forum, in case anyone has any question or needs support please email me on borconie@gmail.com I usually get back to all emails in less then 24 hours.
[Paid Software Announcement and Discussion] LLStarks:
One day we'll find a board that doesn't suck and has good support.

Rooting a 5.1 board shouldn't be too hard. Ancient crap like Kingoroot should work until you get Magisk on there and clean up.
[Paid Software Announcement and Discussion] NYZack:
I wonder if the app would be less complicated to develop if it were directed toward one ROM that could be used on multiple devices - a particular version of LineageOS, for instance, which can be installed on most unlocked phones. Or is the actual hardware important as well?
[Paid Software Announcement and Discussion] pavichokche:
Wow, this sounds very interesting. I really appreciate all your hard work and time that you've put into this.

That said, as a person who just bought a phone to dedicate as a slave to this, does this development mean that you're no longer going to be working on improving the AAGateWay app?
[Paid Software Announcement and Discussion] Emil Borconi:
After 3 days of wrestle, and some help I have finally managed to compile and build the rom for the board (with H5 cpu).

Currently this is just the stock image, compiled from source, so now I will start to tweak it and adapt it for this project.

Due to the global crisis caused by the coronavirus, my workload got reduced significantly overnight, which means I will have time to dedicate to this project (and other Android Auto related ones).

I'll keep posting on this app tread about progress I made on the board. I won't be making changes on the app for now, till I don't see the board project completed, if anyone needs help or older version of the APK please do email me and I will answer you as soon as possible. Once I have the board in a nice stage ready to be presented as a kickstarter project I will try to make the app work on more devices.
[Paid Software Announcement and Discussion] xjust:
Just purchased the mirror app and installed it on a slave samsung a5 2014 (rooted now). Specially got from olx for this single purpose ;)

Master phone is mate20pro. Not rooted since bootloader is locked on those..

Will test tomorrow how it all goes on a porsche macan which just had android auto function enabled.

Normally they just allow carplay as an option.

In this setup the phone calls are also routed via this application wirelessly right ? The car kills the bt connections when the android auto is connected

Also in this setup is possible to run 3rd party apps like youtube or netflix while in motion? I saw that the current version bypasses 3rd party apps and this is the reason code is not public.. the display in the car is very low quality and small but just to have it working would be nice.

Ps. Felicitari pentru idee :)
[Paid Software Announcement and Discussion] NYZack:
If you can get it to work, this app works exactly as if you had your (master) phone plugged directly into the car and running Android Auto. Bluetooth connects to the master, as it does when the phone is plugged in directly. There is not much more to say.
[Paid Software Announcement and Discussion] brooc:
Thanks Emil for all the hard work. Can you revert the version on the market place to 1.0.2 as none of the other versions seem to work.

Additionally, I couldn't get the WiFi Launcher to work. I would like to debug that and get it working. Is there any information I can give to try to resolve that?
[Paid Software Announcement and Discussion] mdoussiere:
Hello JIMSEY

I think we have the same car : peugeot 5008 . I succeded in making AA Gateway 2.08 to work. My configuration :

Using Case one, (Slave tethering which is better for battery usage), Tested with two slaves devices, both are working :

-	Slave 1: Samsung A3 2017 rooted, Custom ROM Lineage OS 16, no google apps installed, AA Gateway installed as système app ;Checked « wifi tethering » and wifi tethering manually configured with HUR and password AndroidAutoConnect

-	Slave 2 : MK 809 V android 5.1.1 ; AA Gateway installed as system App, cheked « i’m a Tv stick » and « wifi tethering » ; wifi tethering configured automaticaly by AA Gateway

Master : Samsung S8, android 9, Non rooted

-	No wifi launcher installed (tried it but not working), but tasker task given previously in this forum by Marschy 33 (Thank’s to him), started on event « bluetooth connected » with the car

-	« mobile Data always on» checked in developper settings

Points to check before connection :

-	Phone bluetooth connection with car configured with calls, messages and contacts, no audio streaming

-	HUR network in Master configured with no automatic connexion

-	Android Auto configured in master with no automatic connexion

Importants points for connection :

-	Do not tap the Android Auto icon on your car headunit when it appears, but wait and tap the icon just after the notification of android Auto is send by the master, ( you have about 10 seconds to do that , When the phone is in my pocket y refer to the sound of the notification)

-	The USB ignition in this car is given as soon as the door is open (no problem, accelerate the boot of the slave) and desappears some time after the engine and headunit are stopped : after stopping the car , note that you have to wait for the end of ignition before starting if you want AA Gateway to work. (I Think the slave must be plugged in the car before ignition for AA Gateway to work).

With this configuration Wireless Android Auto works perfectly with AA Gateway : all apps included google assistant, « OK google » , whats’app read messages,….

Thank’s to the dev for this app
[Paid Software Announcement and Discussion] Emil Borconi:
As promised more updates (albeit I haven't done any work today). [MENTION=407678]Snirpo[/MENTION] 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.
[Paid Software Announcement and Discussion] xjust:
so a little update. beta 2.0.8 crashes on android galaxy a5 2014

alpha 1.0 works great.. strange
[Paid Software Announcement and Discussion] Reli4nth:
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
[Paid Software Announcement and Discussion] pavichokche:
Try running the hotspot in 5Ghz mode instead of 2.4GHz, I found that smoother on one device.
[Paid Software Announcement and Discussion] lonsdaleite:
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.
[Paid Software Announcement and Discussion] lonsdaleite:
I tried AAGW 1.0 alpha and it works! So I'd like to try 2.0.4, does somebody has .apk?
[Paid Software Announcement and Discussion] lonsdaleite:
Tried 2.0 - 2.0.4. All versions don't work in slave-tether mode.
[Paid Software Announcement and Discussion] krlosmt:
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...
[Paid Software Announcement and Discussion] Lucas_Skyline:
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!
[Paid Software Announcement and Discussion] Hyce83:
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!
[Paid Software Announcement and Discussion] Emil Borconi:
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.
[Paid Software Announcement and Discussion] morpho26:
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.
[Paid Software Announcement and Discussion] LLStarks:
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.
[Paid Software Announcement and Discussion] lancer1991:
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.
[Paid Software Announcement and Discussion] pavichokche:
You should send Emil an email, he shares it on one of these forum pages, and he'll send you all the previous versions.
[Paid Software Announcement and Discussion] pacpac56:
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
[Paid Software Announcement and Discussion] popy2006:
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
[Paid Software Announcement and Discussion] mac5079:
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.
[Paid Software Announcement and Discussion] morpho26:
Can you explain how you realize the power on with usb power? on my devices, several samsung galxy A models i didn‘t found the feature.
[Paid Software Announcement and Discussion] mac5079:
To do this you will need a rooted phone. To turn it off I used Tasker. I don't have enough posts here to give you a link to the guide to get it to power on. Try to google for "AutoBoot Android When Charger Connected Instructables".