yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] suku_patel_22:
Superb news. A small hardware that will work with most cars would be awesome. All the AA manufacturers will be after you !! Hope the performance can be must better (I suppose a 5ghz wifi radio won the slave would help)
[Paid Software Announcement and Discussion] jimsey:
HI Emil,

My backing too.

many of the PI's can run linux and android, and if you managed to get a deal with a PI device manufacturer using same architecture for a consumer device, you'd have a real head start because you could get much of your r and d testing via xda

:good:
[Paid Software Announcement and Discussion] LLStarks:
Is the other project/developer name being kept anonymous for the moment? I'd be very interested in contributing to a kickstarter.
[Paid Software Announcement and Discussion] skatermike21988:
So I think I found something interesting about my situation and why it wasn't working before. I tried my automated task today and it didn't want to work. So I tried my manual way that worked yesterday, same result. Aa notification shows for a few seconds and goes away. So i thought, well i factory reset my master yesterday and didn't pair the bt with my car. Aa did it on connect. Well it automatically reconnected my bt now that its paired and didn't work. So I turned of bt and went to tasker to run the task and send the intent and boom instantly aa appears on my head unit and it connects the bt. Now I need to figure out how I can automate this process as it seems to be the problem.

Edit: I have been able to replicate this as well. After connected, I unplug slave leave bt on and try again and it fails. But slave switches to accessory so unplug slave try again with bt off and it works right away.
[Paid Software Announcement and Discussion] Emil Borconi:
Updated the AAGATEWAY as well as the Wifi Launcher app.

On the Launcher app I did fix a bug so really hope that now it will work as expected for all of you.

On the AAGW app I also made some small changed.
[Paid Software Announcement and Discussion] Emil Borconi:
For those curious who is the mystery person working on this it's an XDA member as well known as [MENTION=407678]Snirpo[/MENTION]
[Paid Software Announcement and Discussion] LLStarks:
Ah. OpenAuto. Nice.
[Paid Software Announcement and Discussion] pflarini:
..

---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------

Did it work with the TV Stick Mk809IV?
[Paid Software Announcement and Discussion] Emil Borconi:
Yes but not with Android 7.1 stick.
[Paid Software Announcement and Discussion] morpho26:
Pls can you explain how you realized the AA Start or how you say "the intent" via Tasker......
[Paid Software Announcement and Discussion] skatermike21988:
I'll try to explain my process that I have set up now that seems to be working 100%.

I'm sure it's my headunit that requires aa to setup the bluetooth which is why I have issues with using bluetooth to trigger the process so I had to do some hackery in tasker to make it work.

Slave:

(STATE) On Power Any: Start wifi tether

(STATE) On Not Power Any: Stop Wifi Tether

Master:

I have 2 variables:

-wificonnect

-btconnect

I then have 3 profiles:

(STATE) BT Connected - car bluetooth address: (This disables bluetooth on connection to car only if btconnect variable is 0 and establishes a connection to slave hotspot. Have to use a variable because once AA connects, it will turn on bluetooth and connect to the car. Without the variable this task would be stuck in a loop)
-Set Bluetooth off if btconnect eq 0
-Variable Set btconnect to 1
-Wifi Set On
-Wifi connect configuration "HUR" (Uses tasker plugin wifi connect)
-Wait 15 seconds
-Variable set wificonnect to 1

(EVENT) Variable Set: wificonnect, 1 (This sends the intent to AA to establish connection)
- Send Intent
-Action: com.google.android.projection.gearhead.START_WIRELESS_PROJECTION
-Cat: Default
-Extra: PARAM_HOST_ADDRESS:192.168.43.1 (Replace ip with address of slave)
-Extra: PARAM_SERVICE_PORT:5288
-Package: com.google.android.projection.gearhead
-Class: com.google.android.apps.auto.wireless.setup.service.impl.WirelessStartupActivity
-Target: Activity

(State) Not BT Near car bluetooth (Sets variables back to 0 so process can be automated next time getting in car)
-Variable Set: wificonnect to 0
-Variable Set: btconnect to 0

I'm sure there is an easier way to do this but this is what works for me with my Bluetooth issue.
[Paid Software Announcement and Discussion] lexiperplexi91:
Edit: I see it
[Paid Software Announcement and Discussion] propi62:
What is the intent to stop/kill the wireless projection?
[Paid Software Announcement and Discussion] Emil Borconi:
Simply exit car mode, this can be achieved by tasker as well I think it's a variable called uimode in tasker
[Paid Software Announcement and Discussion] propi62:
My slaves hotspot changes ip adress everytime, so i give up.
[Paid Software Announcement and Discussion] epsonix:
[MENTION=842765]Emil Borconi[/MENTION] Are you aware that there are all the time issues with downloading WiFi Launcher for HUR on any phone I try on XDALabs apk. No issues with AA Gateway. There are funny messages, it either waits infinitelly for Paypal, or often it does not show the app as installed or when I get to its page finally, often pressing to download and accepting all ending up with infinite download icon spinning. Why there is this paypal for 0zł USD (lists 2 currencies, polish and $). Wonder if anybody else is experiencing similar odds with this apk.

It happened always since November when I tried first time.

EDIT

I rebooted my phone, and it went smoothly even without Paypal popping up. Will try both now.
[Paid Software Announcement and Discussion] pflarini:
My slave does not show ip address: "ip address unavailable"
[Paid Software Announcement and Discussion] skatermike21988:
The slave that is running the hotspot will not show it's ip. You can get that from the master under the connection properties for that wifi connection. You may need to change from dhcp to static briefly to see it but it will be under "gateway" or "router"
[Paid Software Announcement and Discussion] epsonix:
Tried to test new Launcher 1.6 on And9 and AAGW 2.0.8 on And8. Tried case 1 as I should, I see screen short blinks on all steps like connecting to USB (but slave does not start hotpost, phone without SIM card) then on master when I get BT connection with car. I enabled hotspot manually (I think I also had some blink on master? God I get lost looking at 2 phones and trying a few setups each time) I have all notifications on HU attemt to connect and then goes back to radio screen, master shows notification that it is running and slave that it is connected to car.

When I try case 3 (not default for my adroid versions), selected master hotspot from slave AAGW, also on master hotspot does not start. I think I had to enable WiFi on slave by hand soon after connection was comming up with car as it slave was disabling WiFi (or maybe it happened when I had option to start tethering off, getting lost). Anyway, behaviour is consistent with other slave phone And7, and all previous versions of Launcher and new 2.0+ AAGW (all works with AAGW 1.0beta RC3). The only improvements I see that with this version I no longer see that apk not responding or stopped working, what was common with versions like Nov - mid January.

I tried also uninstalling WiFi Launcher for HUR and started the AA server by hand and enabled hotspot, but again, no luck, what again is consistent with my last 2.5 month experience.

Certainly I have issues with disablin WiFi automatically on slave, enabling hotpot automatically on both, and I do not knwo if HU server is started automatically in case 1 (should there be notification? if not maybe you list in notification or apk UI itself more complete status?)

I'm waiting for my MK809V_4K from China, long wait - they advise early March. I wonder if my case give you Emil any idea what is wrong. I can work without Launcher and start all on master (HU server and connection of WiFi) and slave (hotspot) via Automate like I did with AAGW 1.0RC3 - as this works with my phones, I just think your new AAGW intereres with that. Maybe you can add more options to your AAGW to leave all to user? I really sniff you taken me away the option which works forcing some automation but failing on no priviledges (for some reason Automate handles this when I enabled some workaround setting for hotspot enabling on And7+).

Can you add such option?
[Paid Software Announcement and Discussion] NYZack:
It's not hard to write a Tasker task to get the hotspot ip. I think someone may have posted one. Otherwise, pm me, and I can send you my version.
[Paid Software Announcement and Discussion] Marshy33:
This is the Shell script I was using....

ip route list match 0 table all scope global | awk 'NR==1{print $3}'
[Paid Software Announcement and Discussion] Buckers1313:
Just purchased a TV stick for use in the future. Does anyone have a place for instructions on how to setup or if there is a video demonstrating the setup and config steps? I saw they are rooted already so hoping that helps with the Hyundai issue. How does the stick go eith boot up times? How quickly do they boot?
[Paid Software Announcement and Discussion] charles8814:
On my phone, tasker app do not provide 'wificonnection' event but only available 'wificonnection' on the State.

Is that right the 'wificonnection' profile should use 'event' not a 'state'?
[Paid Software Announcement and Discussion] skatermike21988:
The event is variable set with variable being wificonnect. This gets triggered when the bluetooth connect state task sets the wificonnect variable to 1
[Paid Software Announcement and Discussion] pflarini:
My MK809IV boots in 45 seconds.
[Paid Software Announcement and Discussion] Emil Borconi:
- I have updated the launcher app again, just a small change compared to yesterdays release, but I have also renamed it (to avoid confusion as some users confused it with HUR).

From now on it's simply called Wifi Launcher.

In case anyone want's to play around with the Launcher app the source can be found here: https://github.com/borconi/WifiLauncherforHUR
[Paid Software Announcement and Discussion] smoki3:
On the new AAGateway I had to set the Hotspot password manually on the slave ( running android 6). Otherwise the master doesnt connect
[Paid Software Announcement and Discussion] jimsey:
Hi Emil,

Unfortunately 've not been able to get any setup working on any of my slaves since version 2 :(

Peugeot 5008

S10+master

Mk809v slave

Moto g3 slave

Samsung s3 slave

When I roll back to 1.3, i can get it to work most of the time but the audio is jittery.

I think the last version which worked well was the one you pushed out just after new year
[Paid Software Announcement and Discussion] pflarini:
Got working almost all times with this configuration:

- Slave: Moto G5, oreo

- Master: Galaxy S9, pie

- Using case 2.

The remaining problem is when I turn radio off for a few seconds. So, after turning on again, it does not connect. I need to go away for 2 or more minutes, time enough to car cut energy from slave.
[Paid Software Announcement and Discussion] Emil Borconi:
Hmm... odd as I do have the same tv stick for test.

- Is any of the slaves rooted?

- Did you enable the tethering on the slave?
[Paid Software Announcement and Discussion] jimsey:
all 3 slaves are rooted.

I've tried wifi tethering, when i enabled this on the MK809v it starts the HUR hotspot and my master connects to the hotspot, then when I launch AA on the car screen, i get the attached message on the screen.

when i use the g3 slave, AAgateway seems to crash/close when i launch AA on the car.

definitely puzzling... i'll take some bug reports and email them over if you have time to look into it?

when i uninstall wifi launcher from the master and AAgateway 2+ from the slave, then install 1.3 on the slave, i can connect by connecting the slave to the masters hotspot and manually starting AA head unit server
[Paid Software Announcement and Discussion] Emil Borconi:
It is normal for it to show no device (at least till the device actually connects).

Using the stick, install latest AAGW on it, and latest Wifi Launcher on the master.

- On the master open the Wifi Launcher app and select the car's BT (don't change anything else)

- On the slave (STICK), convert AAGW to system app, reboot the device, and make sure start tethering is enabled.

- Go to the car plug in the slave to the car and start the car. Once the car starts open the screen which you just share and wait. On the master keep checking that Wifi Launcher is actually running, then that the master actually connects to the slaves hotspot, then once it's connected you should see AA flashing up on the master and only then the car will recognise the slave.
[Paid Software Announcement and Discussion] Rc_086:
Latest AA Launcher and 2.0.8 version. Second day, no success...

Pixel 4 master (rooted)

BQ Fast plus slave. 8.1 Oreo

Master - app is starting when connected to car bluetooth, got an ikon and message of AA on master screen (AA is available, connect phone to the car), after few seconds it disappear.

Slave - connection to the car established, but hot spot does not starting auromatically, have to do it manual (HUR and the password to AndroidAutoConnect).

First version of new AAgateway app 1.03 connection fast and stable, but black screen on car after i click AA icon on car screen.:(
[Paid Software Announcement and Discussion] Emil Borconi:
That icon on the master is AA generated, NOT the WiFi Launcher app. The Wifi Launcher app will say Wifi Launcher and will have an exit button. Make sure you did selected the car from the BT list inside the Wifi Launcher app.

If the app can't turn on the hotspot on the slave you are in quite an un-lucky position as it won't work.

You can try to set things up manually the other way:

1) Create a hotspot from the master and start the headunit server on the master

2) Set the slave to connect to masters hotspot instead of creating a hotspot.
[Paid Software Announcement and Discussion] pflarini:
Try:

In master, settings, applications, android auto, clear all data and cache and restart your testes.

I suggest that you restart both phones, connect slave to the car, turn off car, go away, wait 2 minutes and start car normally.
[Paid Software Announcement and Discussion] smoki3:
The new version of AAGateway break rootmode on 7.0 and older slave devices.

Switching back to 2.05 make it working again.

The Problem is the creation of the hotspot. Looks like the hotspot is not encrypted on the slave and the wifilauncher could not connect to this unsecured wifi.
[Paid Software Announcement and Discussion] jimsey:
Hi Emil, followed your instructions precisely, and just to be sure I cleared all data from both apps before starting again following your instructions.

Using mk809v set to tether and newest wifi launcher on my master.

Once the master connects to my slaves hotspot (HUR) the android auto icon becomes available on my cars screen(shown in the picture)

When I select android auto on my cars screen I get the second message on my cars screen Saying no compatible device detected.

This is odd because the android auto option on my cars screen does not become available until it recognises an android device is plugged in ?
[Paid Software Announcement and Discussion] Oversemper:
Oh! This is a supercool thread I've found!

So, I've got Mercedes GLC 2019 (non-restyle) with standard "audio 20" head unit. Pixel 2 XL works seamlessly with the unit both for android auto and simple BT integration. All I wish for is to replace the USB cable with a WiFi connection.

Before I buy your app, what device should I get for a slave? Money is not an issue... well, I'm not going to buy a new pixel 4 xl 128Gb, of course, but I can get, for example, a used Pixel 2 (non-xl). It will be buried in the compartment between the front seats, and I want a stable WiFi, low power usage, low heating... so, a phone with a good SoC is best, I guess.

Or may be any other particular models of smartphone are preferable? For master I'll use pixel 2 xl.
[Paid Software Announcement and Discussion] jimsey:
Hi,

The glitches are still being worked on but the first post lists the slave devices confirmed to work:)
[Paid Software Announcement and Discussion] Emil Borconi:
Are you sure? As I did tested on older and it created them correctly. Indeed I've changed the hotspot creation for rooted devices running 7.0 (but only 7) as there is a bug in 7 which causes hotspot creation failure.
[Paid Software Announcement and Discussion] Emil Borconi:
That actually might be timing... As the slave will only turn on the USB when it gets a connection from the master, but master will exit AA (this is aa design) if it doesn't receive an answer from the car in a few seconds (I haven't looked at the exact value but it's about 2-5 seconds).

Don't you have a setting on the car to automatically launch AA when a phone is connected rather then relying on a user input?

The big issue is if you set the tv stick to run in non-root mode, it won't be able to switch on the USB (those sticks have that option to in the setting to connect to PC which needs to be enabled). Maybe try with a phone and enable the non-root mode, make sure you select the masters BT from the list and give it a try and see if you can get it working that way (if you can't set your car to autostart when the usb is connected)
[Paid Software Announcement and Discussion] Emil Borconi:
Today's update contains no changes of code, just edited some strings as some of the options did created confusions.
[Paid Software Announcement and Discussion] jimsey:
Yes the car can auto start android auto, but only if AA is available as soon as usb is plugged in. I've had about 50 attempts this week with versions 2.0.6 and 2.0.8 and I cant get either version to work In any configuration on any of my slaves :confused:

Could it be something about the handshake with PSA cars ?

At the moment the only way I can get it to work is with older versions of aagateway(prior to version 2) and using the master to create a hotspot.

---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------

Thanks, I gave it a try but it didnt help. I think my car doesn't like something about v2+ of aagateway
[Paid Software Announcement and Discussion] Emil Borconi:
Non-root mode should be almost equal to older versions 1.3 so if on older version it worked it should with non-root mode as well.
[Paid Software Announcement and Discussion] shmykelsa:
I have 7.0 and this is working just fine
[Paid Software Announcement and Discussion] pflarini:
Could you explain better the options you chosen in this profile? It's not getting triggered.

In State BT Near there are some options to choose:

standard devices

low energy

unpaired

toggle bluetooth

invert
[Paid Software Announcement and Discussion] smoki3:
I just can tell you my expirence. With 2.08 my master can not connect to HUR hotspot. If I look in settings the Hotspot is created without encryption. If I then add encryption manually while the hotspot was activated it works one time.

With 2.06 it works out of the box.
[Paid Software Announcement and Discussion] Emil Borconi:
I feel I'm in a no win situation... I change code make it work on one device it breaks the other.... :(
[Paid Software Announcement and Discussion] skatermike21988:
For those that get the notification on master that says aa is connected to car and then goes away after a few seconds I'd suggest trying my method of turning off bluetooth and sending the intent via tasker. I think some head units require aa to establish a bluetooth connection. I know on my head unit if I plug in to run aa via cord I get a popup that says switching to aa will disconnect my bluetooth and I think that may be causing the problem I was having. Using my tasker profile and not wifi launcher I have had a 100% success rate with connecting wirelessly.
[Paid Software Announcement and Discussion] sibesaver:
Yes!!! I'm using tasker in place of Wifi Launcher with AAGW 2.04 and it works almost 100% of the time. No later version of AAGW even connects to my Kenwood headunit.
[Paid Software Announcement and Discussion] mellda:
I am confused about what TV stick to buy. There is MK809IV and MK809V. Android version 4.4, 5.1 and 7.1 (not recommended). There is chipset RK3229. What exactly should I buy? Is there anybody using the TV stick with samsung S10+ flawlessly? No lagging, reconnecting all the time? If so, what version have you bought? Do you have the link? What version of aagateway/wifi launcher are you using?
[Paid Software Announcement and Discussion] jimsey:
That's android for you, so fragmented and so many possibilities.

:silly:

I think perhaps when you commercialise this, you may end up with slightly different code for different cars with a selection of car in the configuration options.

The good thing is you've already got test data for most car manufacturers
[Paid Software Announcement and Discussion] propi62:
please share a step by step tutorial for master tasker profile.
[Paid Software Announcement and Discussion] skatermike21988:
From my previous post:

---------- Post added at 10:46 PM ---------- Previous post was at 10:44 PM ----------

I chose standard devices
[Paid Software Announcement and Discussion] martin.armstrong:
[MENTION=842765]Emil Borconi[/MENTION]

I have got AAGateway V2.0.8 and WIFI Launcher V2 to work with my slave phone (but not with my MK809V stick with Android 5.1.1, as the slave, although at least the installation problem with the stick is now cured).

It works with both the master and the slave providing the hotspot.

As reported previously, with the slave providing the hotspot, the master seems to only have mobile internet, once it has a connection to the slave hotspot, when the WIFI Launcher has NOT initiated the connection.

It seems as if the only time that the WIFI Launcher initiates the connection is if:

the master connects via Bluetooth with the car AFTER the master has connected via WIFI with the slave, and this happens only if:

1. The car has previously been locked and the slave is already connected to the usb but with no power.

2. The ignition of the car is IMMEDIATELY turned on after unlocking the car and opening and shutting the drivers door, as the Bluetooth takes a bit of time before it powers up (this power-up process however, is already started after the car is unlocked and the drivers door is opened and shut, even if the ignition of the car is NOT switched on) and in the meantime the slave has activated the hotspot, which happens very quickly once it has power (which only happens once the ignition is turned on), and the master has connected to the slave hotspot, but for this to happen quickly one must be out of range of the home WiFi or have forgotten it.

So to sum up, mostly I have to do some sort of manual operation on the master phone to get an AA connection, eg. toggle Bluetooth, and ALSO have mobile data available on the master, so I cannot just keep it in my pocket, which is what I would prefer to do.

A curious thing with this mobile data problem is that the 4G symbol on the Google maps display in top rh. corner is only displayed when there is NO mobile data on the master!
[Paid Software Announcement and Discussion] LLStarks:
2.0.8 broke things for me. Master won't connect. Is there any way to get back to 2.0.6?