yashsingh1/xdaforums huggingface dataset:
[Paid Software Announcement and Discussion] grimloktt:
I was able to get this working in my garage but then received the error when trying to use it in real life that: "There was a connection error with your Android Auto Device."

I'm using Pixel 4 and a MK809V.

Master is running Pie or above and slave is tethering:

Running in root mode: (Yes/No) yes

Did the slave actually turned on the hotspot on the slave: (Yes/No) How do I know?

On the master did you select the cars BT in the Wifi Launcher app?: (Yes/No) Yes

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

Did the master connected to the slaves hotspot?: (Yes/No) How do I know?

Did the AA icon appeared on the master at all (in the notification bar)?: (Yes/No) Yes. It sometimes initially shows as connected but then disappears.
[Paid Software Announcement and Discussion] mrniceguy1437:
AA is having regular connectivity issues with Pixel and some Samsung phones...I wonder if that could be related at all. Have you tried clearing cache for the apps and force close Play Services and try again.

I'm also on a Pixel 4 and can get this working, but not yet reliably...trying many slave devices: OnePlus One, Nexus 5 and S9.
[Paid Software Announcement and Discussion] grimloktt:
TY for your reply. I added WiFi manager to do the battery do not optimize list. We'll see if that does anything...
[Paid Software Announcement and Discussion] LazyWizard:
I've been messing with this for a couple of weekends, on and off. I haven't gotten anything to work consistently. I know it can work because once in my messing around it all came together and my splash screen and AA all startup I'm just not sure how it happened exactly one time. I have version 2.0.4 installed now but I still can't get anything to work. I've tried both the tasker profile and the macrodroid options. I'm willing to try anything at this point. Does anyone have any idea what I am doing wrong. I think the only progress I have ever made was with the slave (Nexus 7) starting the tether and my master (Pixel XL 2) connecting to it. Any advice would be appreciated I would love to get this working.
[Paid Software Announcement and Discussion] reaper1983:
Hi I've bought a android tv stick it has hdmi connection a micro USB on side with so slot then micro USB and standard USB on end.

No matter how I connect it to my laptop I can't access it to root it anyone help please.
[Paid Software Announcement and Discussion] skatermike21988:
Check master's wifi connection to know if it connected to the hotspot But since you say the Android auto notification appears I'm going to assume that it is connected since wifi launcher is sending the intent.

I had the same issue with the notification disappearing and to get it to work I had to disable Bluetooth profiles on the master's connection to the car. Had to only leave calls/handsfree and disable the others. It then started working.
[Paid Software Announcement and Discussion] Emil Borconi:
Updates.

Hi sorry hours turned to days and days to weeks since I've updated you. What happened in the meantime.

[MENTION=407678]Snirpo[/MENTION] continued working on the Linux build, there where some issues related to Qt, D-Bus and BT and I have build the a new app for configuring the device (as the device is going to be embedded we need some way to configure it properly). I'm ready with the config app and waiting now for the test build myself to see how the config app works.

Today we also managed to figure out a small piece of puzzle which was related to the Accessory init bit, this is being tested as I'm writing the update.

On the app bit, I did carry out some work, but I always come back to one thing, TIMING of events. Till recently making the master wait for long periods was pretty easy as all you needed to do is to send a PING request to it from the slave and the phone would wait. Sadly this isn't the case any more and if the master doesn't get an answer from the slave in about 10 seconds (I need to time it exactly) it will terminate the connection. On the other hand most cars will wait for about 20 seconds before they reset the USB connection, making it pretty difficult to automate everything in the right way.

I did find some mistakes in the code as well in both WiFi Launcher and AAGW, but I need to come up with a different way to sort the timing before I can push out the fix, most probably I will need to use a BT on slave and master to make sure everything is ready to start the WiFI connection as that few seconds time frame is really small.

If you do have any question please email me directly.
[Paid Software Announcement and Discussion] grimloktt:
How do you disable the Bluetooth profiles?
[Paid Software Announcement and Discussion] skatermike21988:
Bluetooth settings, then select your cars bluetooth from the list. Accessing the profiles will be device specific but are pretty similar. Either a long press on the device, or a settings cog next to it or even just tapping on the device in the list are typically how it's accessed. Then uncheck all but handsfree/calls
[Paid Software Announcement and Discussion] grimloktt:
Is this what you're talking about? What settings do you have and which one should I keep?
[Paid Software Announcement and Discussion] skatermike21988:
Yes leave only calls enabled
[Paid Software Announcement and Discussion] grimloktt:
I tried it and it didn't work but look at this now. I went back into settings to turn them back on and now look at the options...
[Paid Software Announcement and Discussion] skatermike21988:
Did you Try again with the new options disabled. The most notable one would be Media Audio, wouldn't hurt to see if that's the reason.
[Paid Software Announcement and Discussion] Emil Borconi:
Some updates.

We got the linux image booting on the Orange Pi Zero 2 with both chips the H3 and the H5 (64 bit). We also got the USB accessorry working and we had the first connection, however it disconnects in a couple of seconds, but we are seeing progress on the Linux side.

I've spent quite a lot of time trying to come up with a new version of AAGW, but I'm also facing sudden disconnects. Currently splitting my time between the linux build and working on the app update.

Sadly the H5 chips which where more powerful will be discontinued, however for the current build even the H3 chip is an overkill as the device will have one task only.

I'll keep you posted and hopefully I'll be able to update the AAGW app with a better one. I've fixed the WiFi Launcher but I can't push out the update till I don't finish the AAGW as well, connection and init is done now over BT between slave and master, so both apps need to be updated at the same time.
[Paid Software Announcement and Discussion] Mayki07:
Raspberry Pi

Is there any reason to use Orange Pi instead of the more widespread Raspberry Pi?
[Paid Software Announcement and Discussion] Emil Borconi:
A few actually.

- Form factor

- EMMC available on Orange Pi (this is a deal breaker for the Raspberry Pi)

- Factory willing to customise the board (all additional connector & stuff removed, image pre-flashed, making it a perfect plug&play device)
[Paid Software Announcement and Discussion] Mayki07:
Sure, I understand, thank you for the explanation... ;)
[Paid Software Announcement and Discussion] pavichokche:
That's really cool! Do you have any idea of how much the finished product would cost? Even just approximately, like $50?, $100?, $200?
[Paid Software Announcement and Discussion] Emil Borconi:
No not yet, I'm waiting for quotes from the manufacturer, also need to do some extensive research on TAX, DUTY, import, Amazon warehouse fees, shipping, etc... Sadly when you add all to the mix raw material price is only a bit of the mix.... also trying to negotiate with the manufacturer some figures based on potential turnaround and so on...

However my aim is to have it comfortably below $100. Once I have quote from manufacturer (which is ongoing negotiation) and discuss all the details with [MENTION=407678]Snirpo[/MENTION] as well will let all of you know.

On a different note I realised I've spent 3 days trying to figure out the disconnection for the Android version of the app looking in the bloody wrong place.... :mad::mad::mad::silly::silly::silly::silly::eek::eek::eek::eek::eek:
[Paid Software Announcement and Discussion] reaper1983:
I have downloaded the gateway app on TV stick but when running it it says it needs to be installed in system files to run USB when I except it to move the app disappears.

What am I doing wrong.
[Paid Software Announcement and Discussion] grimloktt:
That happened to me too. I think I just did the steps again and it worked properly the second or third attempt.
[Paid Software Announcement and Discussion] morpho26:
When the message appears every time after reboot and AAGateway Start, it means that your Stick is not rooted.
[Paid Software Announcement and Discussion] reaper1983:
I've checked root and that's fine only get message once but after excepting app disappeared
[Paid Software Announcement and Discussion] Emil Borconi:
Updated AAGW and the WiFi launcher as well. Also I've updated the how-to in the OP, please read it for instructions.

Some key points:

1) If you had a nice (at least 95% reliably working setup) don't update. No seriously, there is no new feature to it, no performance gain, etc, so apply the rule if ain't broke don't fix it :)

2) Most of the work was focused on the rooted slave and master running Pie and above

3) If your master is with Pie or above and you used tethering from master you should consider updating and using tether from slave, but again see point 1.

Since I'm under lockdown (like probably most of you) I had limited testing possibility, also I've been working on it now for quite a while so while I hope I did check all possible things, bugs can still be expected.
[Paid Software Announcement and Discussion] lonsdaleite:
I've tried the latest versions today. No success.

Master: Samsung Galaxy S9+, Android 10

Slave: HTC M8, Android 9 (LineageOS 16), rooted

Running in root mode: Yes

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 cars BT in the Wifi Launcher app?: No (I selected slave's BT)

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, but only for a few seconds

Case 1: Root/non mode (same behavior), slave is tethering

Master connects to slave, I see AA on master, but there is a red screen with an error and AA closes after 1-2 seconds

Case 2: Root/non mode (same behavior), master is tethering, HeadUnit server loaded

Nothing happens on master

The only way I can make it work is using AAGW v1.0
[Paid Software Announcement and Discussion] IlD4nX:
Exactely the same behaviours here with:

- OP7 Pro (not rooted) as master,

- OP5 (rooted) as Slave

- on a Alfa Romeo Giulia.

But in addition, the can also say: the car does detect the slave being connected both in "Root" and "not Root" mode.

Here also: The only way I can make it work is using AAGW RC3 (1.0 ?)
[Paid Software Announcement and Discussion] bethencsoft:
No luck

Not working for me.

Paired Master and Slave by bluetooth ok.

Tethering from rooted Slave (Galaxy S6). Connection OK.

Connection between devices starts ok, Gateway icon and message apperas in car Head Unit OK (Waiting), but when Android Auto starts in Master, it show a "Android Auto have stop working" and closes.
[Paid Software Announcement and Discussion] pavichokche:
Awesome. Hey, have you thought if it would be possible to set up the new device to connect to the master over WiFi direct? Could that offer a more stable and stutter-free connection?
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=6833357]lonsdaleite[/MENTION], [MENTION=1122855]IlD4nX[/MENTION] - sounds like the slave is not able to turn off the USB. [MENTION=9706543]bethencsoft[/MENTION] - That might be a different issue, could you produce a bug report from the master please? [MENTION=9360880]pavichokche[/MENTION] - no, device will follow AA wireless protocol exactly, so in the "eyes" of the phone it connects to a Wireless AA unit. This means that the device will need to create the hotspot and it also means it will support phones (masters) running Pie or higher only. This should not be a problem as Pie is now a 2 years old OS, so by the time device hits the market most phone should be running at least Pie. (I know there will be exceptions, but sadly I'm not sure we will be able to support those).

Also I did have the very first quote, and had a super brief chat with [MENTION=6197810]Sniro[/MENTION]p about the price. Please do not hold me to it as a lot more of research needs to be done on many parts, but there is a good chance that device will end up costing about $60-$70

Currently [MENTION=6197810]Sniro[/MENTION]p is working on the code (actually his is pulling the heavy bit on the coding) and I've started doing research on how can this product be made available worldwide. This actually is pretty massive task, and it does influence the pirce a lot. Just some quick examples, if project is run over Kickstarter and its successful (funds are raised), kickstarter takes a 5% cut of the money, if you list the product on Amazon, for every sale conduct there Amazon will take %12 listing fee, plus final value fee, plus it will charge you for storage, plus it will charge for handling the product (no easy formula to work out exactly how much). If you want to sell in certain part of the words it means you need up to register company in those countries, also need to work out and follow different rules for different market, pay taxes to different local authorities. Working out logistics from China (manufacturer) to the world is a different nightmare. While all this has nothing to do with coding, all this needs to be prepared before we put the project to kickstarter, I do not want to launch a project having no clue what we are doing and what we are expecting and ultimately how much funds we need to raise for this to happen.
[Paid Software Announcement and Discussion] Emil Borconi:
[MENTION=6833357]lonsdaleite[/MENTION], [MENTION=1122855]IlD4nX[/MENTION] - sounds like the slave is not able to turn off the USB.

[MENTION=9706543]bethencsoft[/MENTION] - That might be a different issue, could you produce a bug report from the master please?

[MENTION=9360880]pavichokche[/MENTION] - no, device will follow AA wireless protocol exactly, so in the "eyes" of the phone it connects to a Wireless AA unit. This means that the device will need to create the hotspot and it also means it will support phones (masters) running Pie or higher only. This should not be a problem as Pie is now a 2 years old OS, so by the time device hits the market most phone should be running at least Pie. (I know there will be exceptions, but sadly I'm not sure we will be able to support those).

Also I did have the very first quote, and had a super brief chat with [MENTION=407678]Snirpo[/MENTION] about the price. Please do not hold me to it as a lot more of research needs to be done on many parts, but there is a good chance that device will end up costing about $60-$70

Currently [MENTION=407678]Snirpo[/MENTION] is working on the code (actually his is pulling the heavy bit on the coding) and I've started doing research on how can this product be made available worldwide. This actually is pretty massive task, and it does influence the pirce a lot. Just some quick examples, if project is run over Kickstarter and its successful (funds are raised), kickstarter takes a 5% cut of the money, if you list the product on Amazon, for every sale conduct there Amazon will take %12 listing fee, plus final value fee, plus it will charge you for storage, plus it will charge for handling the product (no easy formula to work out exactly how much). If you want to sell in certain part of the words it means you need up to register company in those countries, also need to work out and follow different rules for different market, pay taxes to different local authorities. Working out logistics from China (manufacturer) to the world is a different nightmare. While all this has nothing to do with coding, all this needs to be prepared before we put the project to kickstarter, I do not want to launch a project having no clue what we are doing and what we are expecting and ultimately how much funds we need to raise for this to happen.
[Paid Software Announcement and Discussion] pavichokche:
Alright, I thought that Wireless AA used WiFi direct, that's actually why I mentioned it. By the way, will this new device require the master to be running the headunit server? Or is it literally going to emulate a wireless AA-capable headunit, with the master phone being completely unaware?

I think it won't be worth it to even consider such "big-scale" sales options as Amazon for now. Honestly, I don't think this will be a super popular project, at least in the beginning, so something like kickstarter or indiegogo would be the PERFECT place to get funded, measure interest, and manage shipments of the first units. If it ends up being a huge success and you get way more funding/interest than you expected, you can look into bigger alternatives. I'd be focusing on finding shipment options/pricing so that you can make the first shipments yourself.
[Paid Software Announcement and Discussion] -Loom-:
During the last few days, I've been struggling to get this to work an a Volkswagen Golf 7 (Disover Media) and a OnePlus 5T as master (rooted) and a OnePlus One as slave (also rooted).

1. On Master I started Wifi Launcher, entered BT MAC of the slave.

2. On Slave I configured AAGW with BT MAC of the master, selected root mode and tethering.

3. Then for testing purposes I connected the slave with my PC via USB.

4. The hotspot on the slave was created instantly.

5. On the master the Headunit Reloaded Wifi Service appeared

6. The master is unable to connect to the slaves hotspot.

In fact, Wifi on the master in constantly turned on and off as long as Headunit Reloaded Wifi Service is active.

Then I tried tethering from the master. When I opened a hotspot on the master, the slave is never connecting to it. On the master the HUR service is switching on and off every few minutes, but nothing more happens.

Either way, I could never get a connection between the two phones.

Is this expected behaviour?
[Paid Software Announcement and Discussion] paul1035:
So I finally had some luck running this. I did a bunch

of scenarios, and what worked for me was running LineageOS 16.0 rooted on my Droid Turbo as a slave running AAGateway 1.0 with a locked S10+ as my master running the latest 2.1 Wireless Launcher.
[Paid Software Announcement and Discussion] Khonji:
It seems that i have same problem. How can i check if my slave (rooted Xperia xz premium) properly managing the USB connections and in case it is not how can i get it right?
[Paid Software Announcement and Discussion] Emil Borconi:
Point 6 - It is correct. WiFi Launcher will constantly try to reconnect the WiFi unit it recognise that it's connected to the WiFi called HUR. Try to manually turn on the hotspot on the slave and manually connect the master to the HUR WiFi, then run the test again (like you did with your PC it's fine). You know everything is running well if:

1) When you plug in the slave to the PC, the PC does NOT recognise the slave.

2) You pass point 6

3) After passing point 6 from above list the PC suddenly detects the slave being connected.

[MENTION=6239345]Khonji[/MENTION] - Probably this is the easiest way to check.
[Paid Software Announcement and Discussion] -Loom-:
The last time I used LineageOS 17 on slave, let's check out with LineageOS 16 now:

Master: OnePlus 5T, latest OOS, rooted. No Wifi Launcher installed for testing purposes.

Slave: OnePlus 1, Lineage OS 16, rooted.

1. Slave running AAGW 2.1. Manually created a hotspot with HUR/AndroidAutoConnect.

2. AAGW on slave is set to root mode, BT MAC of master is entered, tethering mode enabled

3. Manually connected master to the slaves hotspot.

4. USB connection of the slave to PC

5. BOOM! As soon as I plug in the USB adapter, the hotspot on the slave gets disabled..

6. For about 10 seconds, I'm unable to manually turn on the hotspot again. It gets switched off immediatly. After 10 seconds or so I can turn on the hotspot again.

So, no chance of a connection. What could this be? At least, the slave is not recognized by the PC as long as AAGW is running. But something else must be seriously wrong here.

I even tried this scenario with Android Auto Emulator. But only thing I got was "Waiting for phone". Is this supposed to work at all? Could really ease my testing, since my neighbours must already think I'm nuts by constantly sitting in my car (and emptying the battery). ;)
[Paid Software Announcement and Discussion] reaper1983:
Quick question.

If I use a phone as slave will it automatically turn on when I turn car on or am I going to have to manually turn it on every time. Ie if not use for few days and phone goes flat.

Also what budget android phones work as slave will a Alcatel onetouch pixi work or a alcatel one
[Paid Software Announcement and Discussion] -Loom-:
There are very vew phones that turns on (you meant: boot) when charged. So, most phones you would have start manually once there are flat.

For choice of phones: after about 5 days of trial and error with a Oneplus One and three different OS's and a MK809V Android Stick I finally gave up. Never got it to work. Only one time I was able to see a running wireless Android Auto. But couldn't reproduce it. There are far two many variables to control to get it working perfectly. Right phone, right android version, right car headunit.

Personally I'll wait with what hardware solution Emil comes up ;)
[Paid Software Announcement and Discussion] reaper1983:
Ok cheers just fed up of having to connect it tempted to get the wireless car play adaptor and change to apple
[Paid Software Announcement and Discussion] rpgreentree:
I use an Alcatel GoPlay rooted, stock ROM and it works fine.
[Paid Software Announcement and Discussion] Deluxe50:
Hey, unfortunately it doesn't work. Slave smartphone Nexus 6P with Pixelexperience ROM (Android 10) and rooted. Master smartphone Pixel 3 (Android 10) and not rooted. Is it normal that the Bluetooth connection between the two smartphones is disconnected after about 5 seconds? Does the slave smartphone have to have a SIM card in it? Without it, the smartphone will not start a hotspot.