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

[johanalejandrosanmartin]

I paid for the full version but it doesn't work properly
The trial version works better, can I have the trial app with no time limit when using it?

La aplicación funciona correctamente, solo tiene que dejar la compatibilidad de pantalla adaptada, debe usar una versión que no tenga habilitada la opción "habilitar decodificador de software", eso te da mucho rendimiento pero menos compatibilidad de pantalla, la versión de prueba tiene esa opción deshabilitada por defecto.

Mod translation: The application works correctly, you just have to leave the adapted screen compatibility, you must use a version that does not have the option "enable software decoder" enabled, that gives you a lot of performance but less screen compatibility, the trial version has that option disabled by default.

 

[landous]

Newbie question...how to set hardware keys? I have Chinese Android headunit 4.4.4 on BMW F30 but car buttons are not working on HUR..Please advice

There is an app you can search that will display keycodes on the screen as you press the buttons. Unfortunately for me, I also have a Chinese HU (Seicane) and the steering wheel controls don't register as buttons in the HU. They work fine for volume control and bluetooth skip/hang up, but not for AA.

 

[McFlypants]

Automation
To automate starting of HUR when connected to a Wifi network you can use your preferred automation app, for example macrodoid or tasker or anything else, using intents. The intent needs to be configured like this:
- Action: "gb.xxy.hr.WIFI_START"
- Packaged: gb.xxy.hr
- Type: Broadcast
- Receiver Class: gb.xxy.hr.WifiReceiver
See below example screenshots for macrodroid and tasker.

Could you reup the example pictures? I'm stuck at making this in macrodroid.

BTW great app, it saved me from throwing away my zlink android head unit.

 

[bmelika]

Could you reup the example pictures? I'm stuck at making this in macrodroid.

BTW great app, it saved me from throwing away my zlink android head unit.

I second that. I was only successful to initiate HUR through Tasker but automatic clicking on WIFI using the above intents not working.

 

[buggyglint]

Experiencing a weird issue with HUR. It will automatically close if it tries to launch in 1080p mode. If I choose 720p it will work every time. The only workaround that I've found is that it will launch in 1080p if it first has a wifi connection or connected wot a wifi hotspot. I'm running the beta version rc3 of HUR on a Tab S4.

I have also checked the android auto developer settings on my phone to make sure the 1080p option is enabled.

 

[Cutprods]

La aplicación funciona correctamente, solo tiene que dejar la compatibilidad de pantalla adaptada, debe usar una versión que no tenga habilitada la opción "habilitar decodificador de software", eso te da mucho rendimiento pero menos compatibilidad de pantalla, la versión de prueba tiene esa opción deshabilitada por defecto.

Mod translation: The application works correctly, you just have to leave the adapted screen compatibility, you must use a version that does not have the option "enable software decoder" enabled, that gives you a lot of performance but less screen compatibility, the trial version has that option disabled by default.

View attachment 5873383

This is not necessarily true. The vast majority of Double Din Android head units have until recently a screen of around 7" and no more than 1024 x 600 resolution. Therefore the best settings are usually 800 x 480 in both AA, developer settings and HUR, with a pixel density around 130. There is very little lost in noticeable rez with this and performance will be better than for higher settings and nothing to be gained by setting any higher, like 1280 x 720. But software decoder will also help with anything funky and the performance hit is offset by the lower resolution demands. At least that's what I've found - Hardware scaling has some severe colour issues for me on a Xtrons unit, since I re-installed the normal app from the beta, which didn't work at all for me. CoolWalk displays very clear and well with these settings for me.

Somebody mentioned earlier about the mic button on the steering wheel. You will need MTCDTools (https://github.com/f1xpl/MtcdTools) , for this, since most of the Canbus decoders supplied with these units are very generic and don't extend to all functions, of a particular make of vehicle. You use a series of intents, rather like HUR to get the mic to be recognised. If you want to make calls to from this button then you will also need MtcDialer (https://github.com/f1xpl/MtcDialer) and disable the HU BT app, since this will fire up if not, each time you make a call, over AA. You need to retrain Google Assistant, from time to time too. But it has been working very well for me for over 3 years now - no need to say 'Hey Google' either, just fire off instructions - 'Navigate to', "Call..." etc. The only thing that there is no intent for is to hang up a call with the steering wheel mic button - you have to do that from the screen.

 

[StriQer]

Hi guys,
I have an Android head unit that's vertical (1024x600 10 inch).

When I used the trial version of the app everything looked good, I had coolwalk and it was great, I bought the paid app and I cant get it to look right despite using the same settings and everything.
It annoys me that a little part of the top is cut off and when I have spotify on the side its stretched.

I tried every pixel density with every resolution with 10 pixel increments.

So is there any solutions for
this?
Thanks for your help

This is the best I could get it:

 

[McFlypants]

Hi guys,
I have an Android head unit that's vertical (1024x600 10 inch).

When I used the trial version of the app everything looked good, I had coolwalk and it was great, I bought the paid app and I cant get it to look right despite using the same settings and everything.
It annoys me that a little part of the top is cut off and when I have spotify on the side its stretched.

I tried every pixel density with every resolution with 10 pixel increments.

So is there any solutions for
this?
Thanks for your help

This is the best I could get it:

Did you try the custom margin settings under graphics settings?

 

[StriQer]

Did you try the custom margin settings under graphics settings?

Yeah I did...
It basically doesn't do anything.
I add like 20 pixel at the top and it moves it,but its still cut off .

 

[[email protected]]

...

Edit: I removed and reinstalled the app and it works like a charm. 800*480 and 1280*720 ok but with 1920*1080 doesn't work. TRIAL version was working. Maybe I have to try different DPIs with 1920*1080(tablet screen is 1920*1200 by the way).

It shows me AA native, it connects automatically with BT too, I will check all of these.

Thanks for this great app that I would like to see future updates.

 

[renard69]

Hello. Thanks for your work. I've bought the payed version several days ago.
Actually I am using QF001 (ROCO K706) head unit which has the included similar f-ty Chinese application named Carletter (did not find any Github or any other resource about it). Actually it is pretty good. AA worked wirelessly almost smooth and native from the box. Under "native" I mean no client applications/deamons needed on my phone to connect to AA wireless, even the SSID (of that Carletter, hotspot on head unit) came probably over BT connection to the car head unit in general. It only problem for me was that Multitouch did not work (pretty not convenient in google maps) and there seems to be no support or github to discuss it.
So. In that key my question is how is it going with:

- Added support for native AA Wireless. This will only work on the units where the BT is accessible from the Android, as many of those android powered Chinese units, have a separate BT board. For devices which supports this, no headunit server or no WiFi Launcher is needed.

If it works in Chinese software - would love it to work in HUD.
I've installed the latest V6.3 RC3 version. And you told that this "native AA Wireless" was introduced since "Version 6.3 Beta 1".
My Phone Android 11, kernel 4.14.186
AA 9.1.631044-release
Worked "native wireless" (without third party client launcher) with some BMW, Nissan stock head units and that Carletter described above.
Thanks again for your work. If you need my effort to test or debug - let me know, I am developer myself Thanks in advance!

 

[bheremans]

I was trying HUR the last days on several different phones. I found out the native AA did not work on android 11 and above. Been trying to downgrade my samsung S10 that I use on my motorbike for HUR. But samsung blocked downgrade. WOuld really also like to use the native method. It works much better than the other alternatives. Even tried some things with tasker

 

[edwaine]

@Emil Borconi will this still be updated? The last update was at least June 21, 2020. The app is now not available on my head unit even if I joined beta. I factory reset my head unit and now I am unable to download the app from the Play Store.

 

[bheremans]

Hello. Thanks for your work. I've bought the payed version several days ago.
Actually I am using QF001 (ROCO K706) head unit which has the included similar f-ty Chinese application named Carletter (did not find any Github or any other resource about it). Actually it is pretty good. AA worked wirelessly almost smooth and native from the box. Under "native" I mean no client applications/deamons needed on my phone to connect to AA wireless, even the SSID (of that Carletter, hotspot on head unit) came probably over BT connection to the car head unit in general. It only problem for me was that Multitouch did not work (pretty not convenient in google maps) and there seems to be no support or github to discuss it.
So. In that key my question is how is it going with:

If it works in Chinese software - would love it to work in HUD.
I've installed the latest V6.3 RC3 version. And you told that this "native AA Wireless" was introduced since "Version 6.3 Beta 1".
My Phone Android 11, kernel 4.14.186
AA 9.1.631044-release
Worked "native wireless" (without third party client launcher) with some BMW, Nissan stock head units and that Carletter described above.
Thanks again for your work. If you need my effort to test or debug - let me know, I am developer myself Thanks in advance!

I decompiled part of the code.. Native wireless cannot work on android 11. Found this in the code :

if (bluetoothAdapter2 == null) {
            Log.d(TAG, "no adapter available");
            return false;
        } else if (Build.VERSION.SDK_INT >= 30) {
            return false;
        } else {
            if (bluetoothAdapter2.isEnabled()) {
                try {

SDK_INT 30 = Android 11 , So what I found out with testing is confirmed in the code of HUR 6.3 RC3

 

[renard69]

I decompiled part of the code.. Native wireless cannot work on android 11. Found this in the code :

if (bluetoothAdapter2 == null) {
            Log.d(TAG, "no adapter available");
            return false;
        } else if (Build.VERSION.SDK_INT >= 30) {
            return false;
        } else {
            if (bluetoothAdapter2.isEnabled()) {
                try {

SDK_INT 30 = Android 11 , So what I found out with testing is confirmed in the code of HUR 6.3 RC3

Thanks for your response. Actually native wireless works with this phone (in Carletter app on the same head unit or on other cars native head units), so I guess it might be pretty safe to remove that "if". Waiting for Emil Borconi to respond us on that as he probably is the source code owner...

 

[McFlypants]

I have this strange behaviour on my navigation bar: it's always bright and there is a bright border around the widgets too.
Not sure what setting is wrong, i think i tried everything in headunit app and on my phone but it doesn't change.

Tried it on my tablet too (see pictures), it's the same problem. It was okay last week.

I tried all android auto apps from 9.1 to 9.3.

EDIT: Seems to work now after i deleted the data of android auto app and reconnected everything from scratch.

 

[matrixx1]

Hi I have HUR 6.3 RC paid version. Everything is super using it with native AAW via WiFi launcher. But I have a main concern. HUR wireless AA makes my phone very very hot. Using it with carlinkit wireless AA adapter and it stays cool. Did anyone else experience it? It could be I am using it on high Res (720p and DPI 158). What are your experiences with HUR AAWireless and phone heat?

 

[arvinoids]

Having an issue where any time I play audio in headunit reloaded it immediately stops the playback. Happens in any audio app (Siriusxm, apple music, etc). I've tried rebooting all devices and ensuring there are no pending updates. Does anyone have any suggestions?

This happens to me when I am on bluetooth mode for the audio. I either switch to audio sink, or start playing from the car's bluetooth app after opening HUR.

 

[klauspassat]

This happens to me when I am on bluetooth mode for the audio. I either switch to audio sink, or start playing from the car's bluetooth app after opening HUR.

Bluetooth was definitely the culprit. I just turned off the Bluetooth on my phone and everything works as it should now.

 

[matrixx1]

This happens to me when I am on bluetooth mode for the audio. I either switch to audio sink, or start playing from the car's bluetooth app after opening HUR.

interesting