[Android 4.1+] HeadUnit Reloaded for Android Auto with Wifi

[Emil Borconi]

@Emil Borconi
Restart HU after changing connection method doesn't help.
No way for me start working 7.2 and 3.9
Also tried with no luck
7.2 and 3.8.2
7.1.4 and 3.9

Only 7.1.4 and 3.8.2 keep working

And if I choose Manually connect to HU server I see - Couldn't connect to AA HU server, are you in the same network? (Attach)
I use one network - wi fi hotspot on phone!

And one more - wi fi launcher 3.9 crashed sporadically (attach). 3.8.2 doesn't have these crashes

HU: Mobis Hyundai Kona
Phone: Oneplus 7, OOS 12

If you select manual method, you do not need WiFi Launcher, you need to starrt the the headunit server from within Android Auto, please read the instructions.

FC of WiFi Launcher is something else, will need to check that, but as the updated instructions say, when using the manual method, you do not need WiFi launcher:

Manually connect to Android Auto Headunit Server

• In this mode you do not need to install WiFi Launcher on your phone.
• You will need to manually create a hotspot from the phone and connect the device running HUR to the phone
• You will need to make sure you enable the developer settings in Android Auto and starting the headunit server from there. You can do this on your phone, by opening the phone settings, going to connected devices -> Connection preferences -> Android Auto. If you haven't enable the developer mode yet, scroll down and tap the Version 10 times quickly. Once you enabled the Developer mode, you can start the headunit server from the 3 dotted top right corner menu. The Headunit Server can be left running all the time as it doesn't have any negative effect, except the constant notification on the phone.
• When headunit server is running and the device running HUR is connected to the phones hotspot press the WiFi button in HUR.

 

[Emil Borconi]

I apologize if this has been said already but ...

My Setup
HUR: Galaxy Tab A (2017)
Android Auto: Pixel 7 w/Evolution Rom

I was getting a lot of these same issues with the black screen on head unit reloaded force closing on startup etc.

I was able to track down the root of the problem being the video resolution under developer setting in the Android Auto. It would seem as if I had it too high and it was causing a crash on HUR no matter what my connection method was. Once I set it to auto everything worked perfectly, consistently.

Hope this helps someone.

Yes that is indeed pretty important!

 

[Emil Borconi]

@Emil Borconi

I just updated both apps to 3.9 and 7.2 and I'm using wifi direct to connect my phone to my Samsung Galaxy Tab E. Previously, it was working fine but after the update, HU keeps crashing. Not usable anymore...

Does it crash with all the WiFi methods? As you need to explicitly set and configure it on both devices.

 

[Mexca]

Does it crash with all the WiFi methods? As you need to explicitly set and configure it on both devices.

Thank for the reply.
No, all other methods are working. Only the wifi direct method is crashing.

 

[AdvenceeD]

Edit: On updated beta version everything works perfect! Thanks

Hey, i have problem with connection via usb, i need to connect and disconnect the device multiple times to run Android Auto, otherwise nothing happend or application HUR just crash.
I tried to connect with enabled debbuging or disabled but it doesnt change anything. Im using Xiaomi Note 10 pro.

 

[profeet2]

If you select manual method, you do not need WiFi Launcher, you need to starrt the the headunit server from within Android Auto, please read the instructions.

FC of WiFi Launcher is something else, will need to check that, but as the updated instructions say, when using the manual method, you do not need WiFi launcher:

Manually connect to Android Auto Headunit Server

• In this mode you do not need to install WiFi Launcher on your phone.
• You will need to manually create a hotspot from the phone and connect the device running HUR to the phone
• You will need to make sure you enable the developer settings in Android Auto and starting the headunit server from there. You can do this on your phone, by opening the phone settings, going to connected devices -> Connection preferences -> Android Auto. If you haven't enable the developer mode yet, scroll down and tap the Version 10 times quickly. Once you enabled the Developer mode, you can start the headunit server from the 3 dotted top right corner menu. The Headunit Server can be left running all the time as it doesn't have any negative effect, except the constant notification on the phone.
• When headunit server is running and the device running HUR is connected to the phones hotspot press the WiFi button in HUR.

Still the same...
Server is run, manual mod is chosen
Hot spot is created. Connection is up as well.
Could not connect to Android auto Headunit server. Are you on the same network, is the Headunit server running?

Looks like HUR doesn't have connection to hotspot. But all other app works as well

I enabled debugging on HUR, @Emil Borconi could you please let me know where I can find log file?

 

[ElIT3ShOOT3R]

How can I force the Android Auto to use my Headunit's GPS instead of the phone? The GPS of HU is working fine, I also disabled Android Auto's location permission on my phone but it still uses phone's GPS.

 

[dekefake]

Hi Emil, thanks for the AAC toogle, appreciate it.

The app is now working perfectly with my PX5 headunit, and sound is not stuttering anymore even in wireless mode with 7.2. Real game changer.

 

[Lystercol]

Hi guys, could some charitable soul tell me where I can find all the versions of WiFi launcher? With the last update it stopped working for me

 

[mksahin]

Hi guys, could some charitable soul tell me where I can find all the versions of WiFi launcher? With the last update it stopped working for me

Here....

https://apkpure.com/wifi-launcher/com.borconi.emil.wifilauncherforhur

 

[mksahin]

How can I force the Android Auto to use my Headunit's GPS instead of the phone? The GPS of HU is working fine, I also disabled Android Auto's location permission on my phone but it still uses phone's GPS.

The ability to use headunit's own GPS (instead of phone's GPS) depends on 2 things:
1) Relevant HUR setting should be enabled (under Settings->GPS). This is already enabled by default. If disabled for some reason, should be re-enabled.
2) The app that you are using should support the ability to use headunit's own GPS. Google Maps supports this (if provided by the headunit) and that's how I use it. However, not every app that uses GPS can utilize headunit's own GPS. For example, as far as I know, Waze (never used it) apparently don't (can't) use headunit's GPS and can only use phone's GPS regardless of the setting at the headunit (or HUR in our case).

So, basically it depends on the app. I suggest you re-enable Android Auto location permission anyway.

 

[ElIT3ShOOT3R]

The ability to use headunit's own GPS (instead of phone's GPS) depends on 2 things:
1) Relevant HUR setting should be enabled (under Settings->GPS). This is already enabled by default. If disabled for some reason, should be re-enabled.
2) The app that you are using should support the ability to use headunit's own GPS. Google Maps supports this (if provided by the headunit) and that's how I use it. However, not every app that uses GPS can utilize headunit's own GPS. For example, as far as I know, Waze (never used it) apparently don't (can't) use headunit's GPS and can only use phone's GPS regardless of the setting at the headunit (or HUR in our case).

So, basically it depends on the app. I suggest you re-enable Android Auto location permission anyway.

After enabling share gps in HUR settings, I tested it out with lockito app and on my HU and it does work. I was confused a bit because my phone still shows the GPS indicator on status bar. Anyways, I hope now it saves some juice on my phone while I'm using AA wirelessly.

 

[Penguin66]

Because connecting with WiFi over phone's hotspot keeps crashing HUR whenever WiFi disconnects, I'm using it over USB.

But here's the thing, those couple of minutes when it's working over WiFi, HUR/Android Auto is very fast, snappy and responsive (like 60+fps). Over USB, although it's working flawlessly, it's lagging like it's 20-30fps compared to that over WiFi.

Is it because cable is not good (getting some new ones today/tomorrow to try), or that's the maximum data speed it can get from the cable and it's still not enough data transfer like there is over WiFi? Or am I missing some settings? Guess it's not the hardware issue, otherwise it would lag over WiFi aswell.

 

[mksahin]

Because connecting with WiFi over phone's hotspot keeps crashing HUR whenever WiFi disconnects, I'm using it over USB.

But here's the thing, those couple of minutes when it's working over WiFi, HUR/Android Auto is very fast, snappy and responsive (like 60+fps). Over USB, although it's working flawlessly, it's lagging like it's 20-30fps compared to that over WiFi.

Is it because cable is not good (getting some new ones today/tomorrow to try), or that's the maximum data speed it can get from the cable and it's still not enough data transfer like there is over WiFi? Or am I missing some settings? Guess it's not the hardware issue, otherwise it would lag over WiFi aswell.

Theoretically, USB 2.0 data transfer speed is 480 Mbps. Wifi (assuming your HU has 2.4GHz Wifi like most headunits) transfer speed is much lower than that (I usually get 65 Mbps connection). So, I assume it's your cable (or maybe USB port on the HU).

Also, I suggest that you enable the AAC audio option in HUR settings (latest beta version) to ease the bandwidth usage (wired or wireless).

 

[daxtor]

@Emil Borconi I run the latest version of HUR and there is a problem that didn't happen with the previous version. I used to be able to start Android Auto just by plugging my phone to the USB cable. However with the current version I need to click the "USB" button and then choose my phone to start AA. I have a Chinese head unit and a Samsung Galaxy Note 9. Can you think of a reason of this behaviour change?

 

[omaralwardian]

@Emil Borconi so today I attempted to give version 3.9 of the Wi-Fi launcher a try again, completely wiping it and reinstalling it from scratch. I'm on the S21 Ultra Snapdragon processor North American device. When I attempt to open it, all permissions I give, and everything looks ready to go, and then I get a big pop-up saying app not responding.

Subject: Input dispatching timed out (4cdbb0d com.borconi.emil.wifilauncherforhur/com.borconi.emil.wifilauncherforhur.activities.MainActivity (server) is not responding. Waited 10000ms for MotionEvent)

--- CriticalEventLog ---
capacity: 20
events <
  timestamp_ms: 1695128990307
  anr <
    pid: 14677
    process: "com.borconi.emil.wifilauncherforhur"
    process_class: 1
    subject: "Input dispatching timed out (f7e033c com.borconi.emil.wifilauncherforhur/com.borconi.emil.wifilauncherforhur.activities.MainActivity (server) is not responding. Waited 10001ms for MotionEvent)"
    uid: 10434
  >
>
events <

 

[ElIT3ShOOT3R]

Sometimes the HUR does not calculate day/night time correctly for some reason even though the car's GPS is working fine but the HU's time is incorrect when I use my car after a few days maybe because of weak car battery. Is there any way to work around it? Like, use the phone to calculate the correct time for the AA?

 

[mksahin]

Sometimes the HUR does not calculate day/night time correctly for some reason even though the car's GPS is working fine but the HU's time is incorrect when I use my car after a few days maybe because of weak car battery. Is there any way to work around it? Like, use the phone to calculate the correct time for the AA?

If your HU does not have internet connection, its time may be incorrect as in your case. Then, it's normal that HUR will switch day/night theme incorrectly. One way to fix this is to use "WiFi client mode (phone will create hotspot)" method for wireless connection. This way, HU will have internet (from the phone) and its time will be correct.

Or you can try other options in HUR's day/night setting and see if they work for you.

 

[Emil Borconi]

@Emil Borconi so today I attempted to give version 3.9 of the Wi-Fi launcher a try again, completely wiping it and reinstalling it from scratch. I'm on the S21 Ultra Snapdragon processor North American device. When I attempt to open it, all permissions I give, and everything looks ready to go, and then I get a big pop-up saying app not responding.

Subject: Input dispatching timed out (4cdbb0d com.borconi.emil.wifilauncherforhur/com.borconi.emil.wifilauncherforhur.activities.MainActivity (server) is not responding. Waited 10000ms for MotionEvent)

--- CriticalEventLog ---
capacity: 20
events <
  timestamp_ms: 1695128990307
  anr <
    pid: 14677
    process: "com.borconi.emil.wifilauncherforhur"
    process_class: 1
    subject: "Input dispatching timed out (f7e033c com.borconi.emil.wifilauncherforhur/com.borconi.emil.wifilauncherforhur.activities.MainActivity (server) is not responding. Waited 10001ms for MotionEvent)"
    uid: 10434
  >
>
events <

I'll check on an S20 Ultra, that's the closest I have to your phone.

 

[Emil Borconi]

@Emil Borconi so today I attempted to give version 3.9 of the Wi-Fi launcher a try again, completely wiping it and reinstalling it from scratch. I'm on the S21 Ultra Snapdragon processor North American device. When I attempt to open it, all permissions I give, and everything looks ready to go, and then I get a big pop-up saying app not responding.

Subject: Input dispatching timed out (4cdbb0d com.borconi.emil.wifilauncherforhur/com.borconi.emil.wifilauncherforhur.activities.MainActivity (server) is not responding. Waited 10000ms for MotionEvent)

--- CriticalEventLog ---
capacity: 20
events <
  timestamp_ms: 1695128990307
  anr <
    pid: 14677
    process: "com.borconi.emil.wifilauncherforhur"
    process_class: 1
    subject: "Input dispatching timed out (f7e033c com.borconi.emil.wifilauncherforhur/com.borconi.emil.wifilauncherforhur.activities.MainActivity (server) is not responding. Waited 10001ms for MotionEvent)"
    uid: 10434
  >
>
events <

Not able to reproduce.... Also Javascript error is very strange as normally there is no Javascript used in Android.... do you have some accessibility / input injection / tasker stuff which could cause this?