yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] Emil Borconi:
You are mainly right and this is why it's being ported to Linux and this is why we try to make an embedded device to eliminate many of the variables. Master phones are a problem as well but that is the smaller one, and to eliminate most of master phones potential problems we are going to stick with Android 9+ on the master, but even that is not as simple as it should be. Android Auto Wireless has many problems, because some phones (Samsung) disable data usage when Wifi is active, or better said it forces the user to answer the question about the WiFi every time and much much more.

The bigger problem of the project was car & slave combination, with limits imposed by Android, which are being eliminated with the move to Linux and tweaking the OS on the device to make is compatible across the board.

All that being said, you are still right this project have dragged its feet way longer then it should have, and it will probably need maintenance for long period of time, if Google does decide to change something, things will need to be tweaked.
[Paid Software Announcement and Discussion] Emil Borconi:
Thats not a mistake, you should select the slaves BT.
[Paid Software Announcement and Discussion] bethencsoft:
In my humble opinion, would not be better focus in another way? Raspberry Pi has android stable rom, for example. Could not be used like slave one of them and focus the app on this device and rom?

Another point would be interesting is using slave to install AA on it and try make comunication between master and slave only for internet connection and calls. I think that would be possible, like Android Chinese Radio Stereos works. This connects android phone to android radio for calls by bluetooth and you can connect android phone to android radio by wifi for data transfer at the same time
[Paid Software Announcement and Discussion] WilcoSnel:
In that case can the troubleshooting guide be changed?

Because the step On the master did you select the cars BT in the Wifi Launcher app?: (Yes/No) seems to contradict this.

Maybe change that to On the master, did you only select the slave's BT in the Wifi Launcher app?

That confirms the step instead of contradicting it. And since all the other troubleshooting questions are answered "yes" if you did it right it. It feels like you did something wrong if you have to answer it with "no".

The next step seems to contradict this as well.

When the master connected to the car's BT did the Wifi launcher app started up?: (Yes/No)

It should only start up the Wifi Launcher based on the BT signal you selected right? So the Wifi Launcher should start on connecting to the slave's BT as you said, not the car's BT. Or am I missing something here?

Just a thought :)
[Paid Software Announcement and Discussion] Lucas_Skyline:
Hi Emil,

For Samsung phones, I think you can force data to remain on on developer settings (networks, mobile data always on). Does that solves the problem? I don't know, just trying to help :)

Thank you for all the updates!
[Paid Software Announcement and Discussion] Emil Borconi:
I'll order a Pi3 and play around with it making sure Android app works fine on it.
[Paid Software Announcement and Discussion] LLStarks:
Only downsides to the Pi 3 would be size and uncertainty regarding its USB modes. Everything else? It's perfect.

Cases

Throw any OS or version on it until things work (Android Things as a lightweight option!)

Well-understood hardware

Is there anything the Pi 4 adds on top of that other than even more unused ports?
[Paid Software Announcement and Discussion] Rag3:
I think major downside is power consumption. The pi3 is way oversized in term of performance I guess. Not sure if all radio usb ports will provide sufficient power. Unfortunately bt and wifi are not on board on the older pi versions. Maybe the nano version would work?

Anyway, ordered a mk809v hoping it will run smooth.
[Paid Software Announcement and Discussion] Emil Borconi:
That is my worry point with the Pi3, the power consumption, many cars have 500mA max current which is too low for the Pi board.

The size is quite big as well, Android performance is so-so, lack of EMMC made it a really unfit candidate for the job. A Raspberry Pi Zero W with EMMC would be a much nicer candidate for the Linux version as well, but sadly they don't exist.
[Paid Software Announcement and Discussion] SOFO888:
For the Pi3 the solution could be a wire which connects the power contacts to the cigarette lighter plug and the data contacts to the USB port.
[Paid Software Announcement and Discussion] reitso:
"playstore availability"

When will the stable version be ported to google playstore?
[Paid Software Announcement and Discussion] LLStarks:
My MK809V came in. Can't get the car to detect it at all. And yes, it's plugged into the right USB on both ends.

Is there a setting I'm missing to set the USB port a certain way?
[Paid Software Announcement and Discussion] ScrapMaker:
Has anyone run into a situation where they have audio working, but the vehicle headunit remains dark? This seems to happen regardless of using Launcher, or just the HU server, and despite swapping between master/slave for tethering.

Pixel 4 XL Master (rooted)

Galaxy S8 *and* Galaxy S9+ Slaves (both unrooted)
[Paid Software Announcement and Discussion] Emil Borconi:
Reason the app is not on playstore as despite all the attempts it is not something easy to configure and use. People who use XDA generally are slightly more advance users and even they find it difficult at times to get it all running. Adding it to PlayStore will mean much more support needed from my side, which I'm not sure I can offer without a hit in the quality level of support I try to give to everyone.

[MENTION=800534]ScrapMaker[/MENTION] - Press the home button on the unit and then go back to AA

[MENTION=4670039]LLStarks[/MENTION] - Car should only detect the unit after it established the connection with the master. Email me for help.

This is the last update from [MENTION=407678]Snirpo[/MENTION] I've got today: "I completed the refactoring. Aasdk is completely gone now except for the protobuf stuff. Now i'm squashing bugs I introduced because of the refactoring. I have a lot more confidence in the code right now. Probably will have it working very soon :)"
[Paid Software Announcement and Discussion] legendarycom:
hi to all,

I am a new user and I am staring with stable release. I follow the instruction but I how no luck for succesfull connection and need some help.

Slave = OnePlus One non-rooted (Andorid 6.1):

- AAWifiGateway installed

- connected to master BT phone

Master = Huawei P30pro non-rooted (Android 10)

- Wifi launcher installed

- start app when slave BT is detected

What happens:

- Connect slave to the car unit (VW radio unit). The connection is succesfull second time and it says connect master on car unit and on slave I see Headunit Reloaded Wifi Service connected to car unit.

- on master I get a notification Wifi direct enabled,m then disabled and I see HUR wifi connection with no internet. AA is starting but before the screen is shown on car unit everything disconnects (on slave Headunit Reloaded restarts and I need to connect again with car unit and on Master AA crashes and also the phone automatically unlocks and goes to app drawer)

any help and tips apriciated :)
[Paid Software Announcement and Discussion] Emil Borconi:
Just pushed a beta version out for WiFi Launcher.

Some user might have experienced Master connecting to slave for a second then sudden disconnect (only when slave was tethering), the update on WiFi Launcher will probably help fix this issue.
[Paid Software Announcement and Discussion] Emil Borconi:
Just pushed a beta version out for WiFi Launcher.

Some user might have experienced Master connecting to slave for a second then sudden disconnect (only when slave was tethering), the update on WiFi Launcher will probably help fix this issue.

Edit: - The beta was pushed to XDA Labs only: https://labs.xda-developers.com/store/app/com.borconi.emil.wifilauncherforhur
[Paid Software Announcement and Discussion] Emil Borconi:
You don't need macrodroid WiFi launcher will eventually disconnect your from your home WiFi and connect you to the HUR Wifi.

With the second problem its a bit of catch 22...

I can terminate the connection when the BT is dropped, but this is not reliable method, sometimes its dropped earlier. Sometimes the BT reconnects several times (this was the problem actually every new connection forced WiFi Launcher to restart the whole process, hence the problems). Now WiFI Launcher stays on and it's waiting for a CARMODE EXIT to terminate (this should be triggered when AA close itself). I will try to improve the logic a bit but it's almost always ending up in some race/edge condition... That being said I'm happy to read that it's connecting as it's supposed too.
[Paid Software Announcement and Discussion] lottjam11:
After further experimenting, I can confirm that WiFi Launcher 2.3 does in fact enable the HUR connection (without using the MacroDroid macro I made), but only when it's a fresh install of the app. With a fresh install, everything works as designed for creating the connection to HUR and starting AA. However, upon ending the HUR hotspot, the Wifi Service does not exit automatically, and I cannot reconnect to my home WiFi. If I exit the WiFi Service via the notification, my home WiFi reconnects immediately. But if I restart HUR, WiFi Launcher doesn't restart (no notification for WiFi Service) and reinitiate the connection to HUR. If I uninstall/reinstall WiFi Launcher it works as expected for the initial connection, but again won't exit cleanly.
[Paid Software Announcement and Discussion] Rag3:
Maybe store the BT connection state with a timeout, i.e. only when the connection is gone for e.g. 10 consecutive seconds, launcher will exit? (In addition to aa exit as a second way to detect)
[Paid Software Announcement and Discussion] Anonym.tsk:
Hi. I have problem and idea.

Master: Oneplus 6T, Android 10, non-rooted

Slave: LG Nexus 5x, Android 10, rooted

Car: Kia Sorento Prime

First problem: the latest beta WifiLauncher sometimes doesn't start after BT connection. Only restart BT on master helps.

Second problem: when i start my car usb power looks like on picture

AAGateway starts hotspot and bluetooth on ignition phase, then in a second it stops hotspot and bluetooth (starter phase) and in second tries to start again. And 50/50 when engine starts, hotspot and bluetooth on slave are disabled.

I think, it's good idea to add debounce 1-3s (mb configurable) to start/stop hotspot handlers to skip ignition and starter phases and start hotspot only when engine already started.
[Paid Software Announcement and Discussion] LLStarks:
I went back to my OnePlus One slave and got it working after factory resetting my master. I ran into Android Auto red screens at first, but then it finally connected to the head unit properly.

Master: OnePlus 7T Pro 5G McLaren (Android 10)

Slave: OnePlus One (Oxygen 2.1.6 - Android 5.1.1 - Rooted mode)

I need to try the MK809V again. I was able to get the AA icon to appear in both laptop and head unit tests, but wifi issue lottjam11 mentioned is quite noticeable. Furthest I got was the red screen and I think it would work now if I ever got that far again.
[Paid Software Announcement and Discussion] Kaitlyn2004:
I just came across this thread as I realllly want wireless android auto!

MY primary phone is a Pixel 4. I also have a Pixel XL, and would be willing to pick up a separate (cheap+small) slave device if it made sense. I have a 2020 Toyota 4Runner with android auto built in. USB works just fine.

Will my setup work for wireless android auto?
[Paid Software Announcement and Discussion] lottjam11:
For what it's worth, if I just reboot my phone after HUR connection is stopped (car is turned off) instead of exiting the WiFi Service, my phone will connect to my home WiFi and will also reconnect to HUR without having to reinstall the WiFi Launcher app... Since I'm rarely driving these days, it's not a big deal to reboot my phone...
[Paid Software Announcement and Discussion] Emil Borconi:
- Updated WiFi Launcher from Beta to stable, made sure it does a clean nice exit after disconnecting from the slaves hotspot.

[MENTION=8305479]Anonym.tsk[/MENTION] - I think I already have a 3 second delay burned into the AAGW app but I will double check.
[Paid Software Announcement and Discussion] Emil Borconi:
- Updated WiFi Launcher from Beta to stable, made sure it does a clean nice exit after disconnecting from the slaves hotspot.

[MENTION=8305479]Anonym.tsk[/MENTION] - I think I already have a 3 second delay burned into the AAGW app but I will double check.

On a different note, sadly I don't have any more updates about the Linux version :(

However I got my hands on a Raspberry Pi 3 (I specially wanted 3 not 4 because on 3 it is possible to run Android Things as well). I will be doing some playing around with this, Android Things does allow you to set up different BT profiles and I want to test that as well...
[Paid Software Announcement and Discussion] Issa souri:
I have problem that how to connect to my car screen ,,, waiting aagateway wifi master to connect,,,,
[Paid Software Announcement and Discussion] lottjam11:
I've only briefly tried this new version. It does seem to exit cleanly when the disconnecting from the HUR hotspot. I'll have to see next time I'm in my car if it reconnects and starts AA as expected. Appreciate the update!
[Paid Software Announcement and Discussion] Issa souri:
during wire connection SSD
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=1555354]misiekm73[/MENTION] - Please use email as notifications from posts/PM's are not always coming trough.

From the post I'm not sure which steps are you taking can you please try to be slightly more precise?

- Are you using root or non-root mode?

- Does it actually connect but you get a black screen as it's not obvious.

Please do email me directly on borconie@gmail.com
[Paid Software Announcement and Discussion] Emil Borconi:
I have played around with the RPI3 board this days. The micro USB port doesn't seem to be usable as an OTG port (at least not in the Android versions available) and without a functional OTG port it is a non-starter, so RPI3 boards can't be used for this project.
[Paid Software Announcement and Discussion] cabbie_fin:
I have MK809V_4K rooted stick. In order to install AAGW on it I need to login to xda labs. This the stick will not do. Does anyone have any tips on how to get the stick to co-operate?
[Paid Software Announcement and Discussion] Emil Borconi:
Email me and I can send you a copy of the APK.
[Paid Software Announcement and Discussion] jimsey:
Thats a shame, does that put an end to hopes of a plug and play device as presumably you were going to build on a suppliers existing hardware?
[Paid Software Announcement and Discussion] Emil Borconi:
No, but I need to wait for [MENTION=407678]Snirpo[/MENTION] to do the rest of the work.... That will be Linux based and it will be plug&play I only looked at the raspberry as an alternative.

In the last few weeks I did got quite a few emails from different users and most of them are able to get it working but ROM and slave hardware does make a big difference. I had multiple users who tried 4-5 ROMs till they got it working (slave only)
[Paid Software Announcement and Discussion] lottjam11:
I had same issue. I ended up installing xda labs on my tablet, downloading AAGW apk and emailing it to myself. I then opened my email in the web browser on the MK809V and downloaded/installed the app...
[Paid Software Announcement and Discussion] Rag3:
Can you make ROM recommendations for the devices you tested yourself? Such as the MK809V - mine should arrive in a few days and it would be helpful.

Thanks!
[Paid Software Announcement and Discussion] Emil Borconi:
Just the stock 5.1 one which comes installed on the unit.
[Paid Software Announcement and Discussion] Rag3:
Thanks! That sounds easy :) Just hope the device matches the specs I ordered...
[Paid Software Announcement and Discussion] Emil Borconi:
Quick update about the Linux development (this is a copy & paste of the email I've got) from [MENTION=407678]Snirpo[/MENTION]

Hi Emil,

Small status update: Like you may already have seen, I did quite a lot of work the last few days. There were quite a few bugs, well... really alot.

I squashed most of them. Mainly in the sending/receiving of messages. But the SSL stuff is giving me some issues. Handshaking and sending plain messages is working fine (again). But the sending of encrypted messages is not working yet. That's also where I kind of got stuck when still using AASDK. Fortunately it's now a bit easier to debug.[/B]

The good part is that my my C++ skills are non-existent I do know the AA SSL protocol by heart by now, so I'm almost sure I've already located the problem and suggested the fix. Will keep you all posted as soon as we have more info on this.
[Paid Software Announcement and Discussion] LLStarks:
I've found the MK sticks nearly impossible to troubleshoot on the fly. If there's some kind of wireless ADB or Vysor that can do screen mirroring, I'd like to know.

More generally though, I'd like to see a root mode for the Wifi Launcher or something that more confidently tells me that it won't die in the background, runs on boot, or is even listening for a connection in the first place.
[Paid Software Announcement and Discussion] szo1:
That's strange, I've been using a MK809III stick from the start of this thread, and it has also stopped letting me logon to XDA Labs. I just thought my stick was starting to die.
[Paid Software Announcement and Discussion] Emil Borconi:
I could create a tasker task.... Then you won't need the WiFi launcher....
[Paid Software Announcement and Discussion] cabbie_fin:
The next obstacle in the course

I did get AAGW working, thanks Emil. Still, it does not work correctly. The problem is now between the car and the TV stick. The master - slave connection appears to work without a hitch. The car unit is VAG Bolero MIB 1, which may be too old for all of this to work. The car unit recognizes the TV stick (HX_2299, or something to that effect) and it then decides to end communication with it. I am running the stick as rooted, otherwise there is no operation at all. Has anyone got things working with MIB 2/2.5 platform?

Through USB things work.
[Paid Software Announcement and Discussion] naqand:
This would be awesome!!
[Paid Software Announcement and Discussion] Emil Borconi:
I have create a tasker task to launch Android Auto (link available in OP as well): https://drive.google.com/file/d/1UO-Z5P0oQpHEdrQjYqvSM48L1TI-K5g8/view?usp=sharing

If you want to use Tasker to fire up AA over WiFi please feel free to use it (make sure you set the conditions right :D )
[Paid Software Announcement and Discussion] -Loom-:
You you specify what conditions must be set? Like "Connected to HUR" ?
[Paid Software Announcement and Discussion] apoorvchandra:
Hey [MENTION=842765]Emil Borconi[/MENTION]

Master is running Pie or above (Android 10) and slave is tethering:

Running in root mode: Yes (Slave rooted, master not.)

If running in non-root mode, is the splashscreen visible on the car: n/a

If running in non-root mode, did you set the masters BT inside AAGW app?: n/a

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

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?: Yes

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

The slave (rooted) starts a Hotspot, and master connects to it. (Master BT set in Slave AAGateway settings.)

Master connects to the Wifi hotspot from Slave, and BT connects to the car headunit.

Wifi Launcher kicks in, but AA headunit server on the master

DOES NOT

start.

Add : On the master, why am I selecting the Slave's BT? Shouldn't it be the headunit BT?
[Paid Software Announcement and Discussion] globnexus5X:
AAGateway on new Peugeot 5008 (2017)

Hello [MENTION=842765]Emil Borconi[/MENTION]

I have some issues with AAGateway and Wifi Launcher. i try lot of tests but i can't launch android auto wireless.

My car is last generation of Peugeot 5008. i read some post in this thread and it appears that there are some problems with this car / headunit.

it seems that [MENTION=646399]jimsey[/MENTION] succeeded : https://xdaforums.com/general/paid-...droid-auto-t3813163/post82062477#post82062477 with AAGateway 2.08.

How can i download AAGateway 2.08 plz ?

My equipments :

- Slave : MK809 V rooted / Android 5.1

- Master : OnePlus 5 / Android 10 non-rooted

AAGateway version : 2.2

Wifi launcher : 2.3 and 2.4

Master is running Pie or above and slave is tethering:

Running in root mode: YES

If running in non-root mode, is the splashscreen visible on the car: N/A

If running in non-root mode, did you set the masters BT inside AAGW app?: N/A

Did the slave actually turned on the hotspot on the slave: YES

On the master did you select the slaves BT in the Wifi Launcher app?: NO (BT CAR)

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)?: YES

Thanks a lot for your work. Have a good day

Mat
[Paid Software Announcement and Discussion] Emil Borconi:
Selecting slaves BT is fine, did you allow WiFi Launcher to draw over other apps? Sounds like the permission is missing and WiFi Launcher can't start the activity.
[Paid Software Announcement and Discussion] Emil Borconi:
- Did the car made any sign that it detected the presence of a phone after the AA icon appeared on the master?

- Did the AA icon remain visible on the master for a longer time or was it only for a couple of seconds?
[Paid Software Announcement and Discussion] globnexus5X:
Thx for your Reply

- Did the car made any sign that it detected the presence of a phone after the AA icon appeared on the master?

Yes AA icon on screen car is available many times during 0.5 sec but its impossible to click on it

- Did the AA icon remain visible on the master for a longer time or was it only for a couple of seconds?

AA icon on master is always visible after master is connected to slave
[Paid Software Announcement and Discussion] matts18ss:
I'm so close!

Master is running Pie or above and slave is tethering:

Running in root mode: 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: Yes

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?: Yes

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

Master: Galaxy s20 ultra factory, non-rooted.

Slave: LGv20 rooted running rr_h918 rom on Android 9

Issue: I get the splash screen, slave launches hot spot, master connects, screen goes dark. I hit home button, then Android auto on car, and it acknowledges the press but does nothing. Music I had streaming prior to testing did begin to play. If I launch Android auto for phone screen, it shows it's connected and shows swipe up to unlock. If I do that the app disappears. The music continues streaming though.

Car: 2018 Chevrolet Camaro SS

I do IT for a living and enjoy this project. Any ideas, no matter how difficult or unorthodox I'm willing to try.

My next thought is flash an older Android rom on the slave.

Any help is appreciated!
[Paid Software Announcement and Discussion] Tabs78:
Hi, i follow guide but i have not splash screen on My car.

I have Tucson 2018

Slave s6edge no root

Master p30pro no root

Inviato dal mio VOG-L29 utilizzando Tapatalk
[Paid Software Announcement and Discussion] IlD4nX:
Try to root your slave, it should increase compatibility.