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

What should be my next focus?

  • Try to work out how to integrate ODB2/CAN data?

    Votes: 18 94.7%
  • Build a HUD app to work with HUR(HUDWAY style)?

    Votes: 1 5.3%
  • Something else?

    Votes: 0 0.0%

  • Total voters
    19
  • Poll closed .
Search This thread

67jeffh

Senior Member
Feb 16, 2013
67
13
Samsung Galaxy S20 FE
That's honestly the one feature that I am missing. I'd love to either have HUR set night mode based off my phone being in light or dark mode or if I could manually set up sunrise and sunset times it would be perfect
Yeah mine doesn't work either. It works correctly in native AA (our Malibu and Buick encore) but not with HUR for some reason. Tried every possible combination in developer settings and AA etc... no luck.
 

barnesk9

Senior Member
Sep 23, 2008
109
7
Thank you. I didn't find the app on the first post but I found it in the playstore luckily.
The app actually works if I connect via Wifi (I had to use the second method first before I could use the first).

I have 2 questions.
1. Is it possible to set the resolution to a custom resolution? My HU supports a resolution of 1024x600 pixels, so setting it to 800x600 makes the layout appear oversized while going for 720p makes it too small, partly too small to read. I know Android Auto supports the resolution since I had it with another method (I used a USB dongle with the app AutoPlay before - had bad experience though).
2. I can't seem to make USB mode work. The screen stays black when I connect my phone via USB. I tried both methods mentioned in the first post (meaning active software rendering and allowing video playback while driving). I can send you my hur.log file.
Thank you for making this possible.

Edt:
My HU had an app called EasyConnection installed which pops up a message on my smartphone whenever I plug it in.


2. Is this interfering in any way? It seems I can't uninstall the app. I disabled it and took away all rights I can but since I'm not su I can't delete it.


1. You're better off setting the resolution to 720p then changing the DPI so that it fits to your liking

2. Yes, easyConnect does interfere with HUR. Disable it in the app settings
 

omerbagi10

Senior Member
Nov 21, 2016
323
114
Is there a way for the media the be played from the phone's bluetooth to a different multimedia system while connected the HUR with usb?
My car has both original multimedia and an android headunit and I want the sound to come out from the original multimedia.
 

steslatt

Senior Member
Oct 22, 2010
421
70
Is anyone else still having the crash upon wireless connection issue with the latest beta? Sometimes it works fine, but sometimes when it connects via WiFi the app will crash a few times before wireless connection works. USB seems unaffected. Wondering if I'm the only one or if it's still an issue with the program.
Yeah I've been having this problem for a while now tried both stable and beta versions but it does the same thing.
 

hgaaditya

Senior Member
Sep 23, 2013
78
7
Bangalore
I just bought the paid version. And can't seem to get it to work. Just keeps crashing on launch.

The trial version worked well for 5 mins and asked me to buy and so I did.

But I tried the stable and Beta versions.. it just goes black with a notification ring. And then crashes right after. Anyone has any solution/advice?
 

zoltanandras

Member
Jan 26, 2021
11
1
I just bought the paid version. And can't seem to get it to work. Just keeps crashing on launch.

The trial version worked well for 5 mins and asked me to buy and so I did.

But I tried the stable and Beta versions.. it just goes black with a notification ring. And then crashes right after. Anyone has any solution/advice?

Hi,

Black screen can have multiple causes:
  1. - Make sure your device does allow video playback while driving. This setting is is different on each unit.
  2. - Try changing the video settings. Go to Settings -> Graphics and enable the software decoding
  3. - Try lowering the resolution. Go to Settings -> Graphics -> Resolution
  4. - Try resetting the pixel density to 160 DPI Go to Settings -> Graphics -> Pixel Density
  5. - If you are using a USB connection try to uninstall/disable EasyConnection app, usually it's preinstalled on the units.
  6. - Try different connection method (Wi-Fi or USB)
  7. - Try another USB cable (If you using with USB method)
 
  • Like
Reactions: hgaaditya

hgaaditya

Senior Member
Sep 23, 2013
78
7
Bangalore
Hi,

Black screen can have multiple causes:
  1. - Make sure your device does allow video playback while driving. This setting is is different on each unit.
  2. - Try changing the video settings. Go to Settings -> Graphics and enable the software decoding
  3. - Try lowering the resolution. Go to Settings -> Graphics -> Resolution
  4. - Try resetting the pixel density to 160 DPI Go to Settings -> Graphics -> Pixel Density
  5. - If you are using a USB connection try to uninstall/disable EasyConnection app, usually it's preinstalled on the units.
  6. - Try different connection method (Wi-Fi or USB)
  7. - Try another USB cable (If you using with USB method)
So, I played around with the settings. And it looks like it works well till 720p. As soon as I set 1080 it breaks.
Enabling/Disabling Software encoding has no effect. Even DPI doesn't have much effect anything from 140 to 210 works..

But 1080p breaks.

PS: I don't have a android HU. I am running it on a tablet in Sea mode.
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,206
2,902
Tg. Secuiesc / Kezdivasarhely
Hi guys.
On the run as usual, Sunday afternoon and trying to finish the work for the week as I can't recall when was the last day without work...

Anyway I've released a new Beta, bumped the version since there are again massive changes:

Version 6.3 Beta 1 released
- Re-wrote whole rendering process to use GLES20, in simple terms video render should use GPU
- Much better scaling approach
- 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.
- Changed key mapping, user can now define their own buttons as they wish.


If you update the app, please make sure you check the key bindings in settings to match your need. Also if you do get a dialog saying your unit supports native AA wireless, you will need to un-pair and re-pair the phone with the unit, after HUR have been started. In this case you should probably remove WiFi Launcher from the phone in case you have it installed.

On the video render bit, I've changed that completely, tested in 5 different units I have and it works nicely, now I hope it won't cause problems.... GLES20 is different, basically it's low-level graphic API. This should help a lot with performance and device support.

Beta is available on my website and should shortly be available on PlayStore as well https://play.google.com/apps/testing/gb.xxy.hr
 

Klamathy

Member
Oct 5, 2019
35
17
Hi guys.
On the run as usual, Sunday afternoon and trying to finish the work for the week as I can't recall when was the last day without work...

Anyway I've released a new Beta, bumped the version since there are again massive changes:

Version 6.3 Beta 1 released
- Re-wrote whole rendering process to use GLES20, in simple terms video render should use GPU
- Much better scaling approach
- 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.
- Changed key mapping, user can now define their own buttons as they wish.


If you update the app, please make sure you check the key bindings in settings to match your need. Also if you do get a dialog saying your unit supports native AA wireless, you will need to un-pair and re-pair the phone with the unit, after HUR have been started. In this case you should probably remove WiFi Launcher from the phone in case you have it installed.

On the video render bit, I've changed that completely, tested in 5 different units I have and it works nicely, now I hope it won't cause problems.... GLES20 is different, basically it's low-level graphic API. This should help a lot with performance and device support.

Beta is available on my website and should shortly be available on PlayStore as well https://play.google.com/apps/testing/gb.xxy.hr
Hi emil.. thanks for your constant efforts.. So I installed latest beta on an atoto a6 pro

1) HUR tell me that is can support native AA wireless (atoto has 2 bt adapters and when i click on wifi in hur it shows list of devices connectd to bt2) however it will not connect phone shows searchig for android auto screen but it then closes - so for now i reverted to use wifi launcher
2) Screen is 1024x600 and i used to use 720p with 185 dpi.. this still works but now i have a 1 cm black margin on right side of screen and graphics do not look smooth but rough like there is a lot of aliasing..
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,206
2,902
Tg. Secuiesc / Kezdivasarhely
Hi emil.. thanks for your constant efforts.. So I installed latest beta on an atoto a6 pro

1) HUR tell me that is can support native AA wireless (atoto has 2 bt adapters and when i click on wifi in hur it shows list of devices connectd to bt2) however it will not connect phone shows searchig for android auto screen but it then closes - so for now i reverted to use wifi launcher
2) Screen is 1024x600 and i used to use 720p with 185 dpi.. this still works but now i have a 1 cm black margin on right side of screen and graphics do not look smooth but rough like there is a lot of aliasing..
Yeah second user who reports this :( why this is not showing up on any on my test units.... :(
 
  • Like
Reactions: svandasek

vj4

Senior Member
Apr 10, 2007
360
11
I just bought this and for some reason once I've run it on KonstaT pi 4 build my Wi-Fi wont work after. Just lists it as limited.

Worked fine before I ran headunit Reloaded. as i used the wifi to download from the app store.

Used USB to connect to my phone.
 

Clarkie49

Senior Member
Jan 15, 2018
94
9
Hi guys.
On the run as usual, Sunday afternoon and trying to finish the work for the week as I can't recall when was the last day without work...

Anyway I've released a new Beta, bumped the version since there are again massive changes:

Version 6.3 Beta 1 released
- Re-wrote whole rendering process to use GLES20, in simple terms video render should use GPU
- Much better scaling approach
- 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.
- Changed key mapping, user can now define their own buttons as they wish.


If you update the app, please make sure you check the key bindings in settings to match your need. Also if you do get a dialog saying your unit supports native AA wireless, you will need to un-pair and re-pair the phone with the unit, after HUR have been started. In this case you should probably remove WiFi Launcher from the phone in case you have it installed.

On the video render bit, I've changed that completely, tested in 5 different units I have and it works nicely, now I hope it won't cause problems.... GLES20 is different, basically it's low-level graphic API. This should help a lot with performance and device support.

Beta is available on my website and should shortly be available on PlayStore as well https://play.google.com/apps/testing/gb.xxy.hr
Hi Emil is there a tablet that the native WiFi connection works, I have a Huawei which keeps popping up a dialog box asking whether you want to enable Bluetooth
 

omerbagi10

Senior Member
Nov 21, 2016
323
114
Was using stable 5.2, decided to try beta 6.3 then spotify stopped working.
Reverted back to stable 5.2 but spotify still does not work, uninstalled and installed again but the problem still exists.
 

Attachments

  • IMG_20210208_014525.jpg
    IMG_20210208_014525.jpg
    1.2 MB · Views: 58

Klamathy

Member
Oct 5, 2019
35
17
Yeah second user who reports this :( why this is not showing up on any on my test units.... :(
Can i help in some way? do you wish some logs?
re 1cm margin on right hand size this only happens if i enable full screen in hur settings.. If i disable fullscreen mode.. screen is filled correctly but then i have bar with android buttons at bottom of screen..
 
Last edited:

shoman94

Recognized Contributor
Mar 27, 2009
8,915
12,312
Maine
I installed the trial version on my Dell Venue running Android 5.1. I tried to connect my phone running Android 11 using Wi-Fi Direct which seems to connect to my phone but yet nothing happens with the app after I'm connected to my phone. I've also tried connecting my phone directly to my tablet using a USB cable and nothing happens. What I'm trying to accomplish is to run Android auto server on my tablet which will be connected to my vehicle via Bluetooth or auxiliary plug. So then I could connect my phone to it and use the tablet as if it was an Android auto receiver.
 

macgreg04

New member
Feb 8, 2021
2
2
Hi Devs,
Bought version 4.6 new UI.
Tried multiple times on latest beta and latest stable versions unable to make it work as smoothly as 4.6
Just black screen or glitchy graphics on initial test.

Samsung Note 10+ and Android 11user here
 

shoman94

Recognized Contributor
Mar 27, 2009
8,915
12,312
Maine
So I figured out that I must run the server from my phone and I can connect to it using my hotspot. So it the tablet pulling from my hotspot bucket for all the data being used?

I couldn't get wifi direct to work, not sure what I'm doing wrong.

I don't have a USB-micro OTG which my tablet is.


On google maps I don't see a current speed or speed limit..... Is that not shown with AA?
 

mbonus

Senior Member
Aug 18, 2010
942
532
i get crash as soon as i press WiFi , latest working version for me is 6 beta 6
Yeah this 6.3 beta 1 doesn't work for me. Is there anyway to revert to 6 beta 6?

(Chinese car screen) I was connecting via wifi by using my own phone hotspot and headunit server. I don't use the screens builtin bluetooth. The new beta tried to get me to use it, but thats not how my setup works. (I connect BT to my actual car)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Hi anyone using the native WiFi method, mine is working great accept when I go past a local car showroom AA disconnects and then hur closes down. Its the only place that this happens really strange 🤔
    Car salesmen will do anything to get you in the showroom to unload a new vehicle on you. That said, this is a pretty clever ploy.
    2
    .One question about wifi...do I have to enable the hotspot in the phone settings when wifi launcher is installed, or do I just leave it off and wifi launcher sets up the wifi?
    Thanks for your patience.
    Just to expand on what Clarkie49 said, because this is getting tiresome.
    Disclaimer: my head unit's display is currently busted and I haven't been able to use it since these beta updates have been released with "native" AA wireless, however I doubt my head unit is compatible with it.

    Using the WiFi Launcher method, the WiFi hotspot should be broadcast from the car deck/head unit, to which your phone connects. The SSID of this hotspot should be set to HUR and password AndroidAutoConnect unless you change these in the WiFi Launcher app on your phone, in which case you're phone will look for and connect to whatever unique SSID you specify.
    You may need to confirm via a prompt on your phone to stay connected to this WiFi, which has no internet connection, and use mobile data.
    Your head unit will not be connected to the internet this way so apps installed on the head unit will not update, etc. Your phone is connected to the internet, it just sends the Android Auto feed to Headunit Reloaded.

    I don't use this method because I want my head unit apps to be up-to-date and YouTube Music to download Smart Playlists, etc. So, in case HUR craps out and I've no reception or my phone battery dies, I can still use native apps on the head unit.
    My head unit has a crappy Bluetooth module and Bluetooth tethering from the phone isn't reliable so I connect my head unit to my phone's WiFi hotspot, which can be named whatever you want.

    To automate things, I use Macrodroid on the head unit to launch HUR when connected to this hotspot. I used to use HUR in Self Mode and it was set up to launch directly into Self Mode so I never had to touch anything when getting in the car. However, Self Mode was laggy which was unsafe while driving so I've switched to using AA from the phone, which is much smoother and more responsive.
    My phone is rooted so I'm able to use Macrodroid to start the AA head unit server on the phone (may not be necessary with native AA wireless, I'm not sure) with the following shell script, triggered when the phone connects to the head unit's Bluetooth after switching on the car:
    am start-foreground-service -W com.google.android.projection.gearhead/com.google.android.projection.gearhead.companion.DeveloperHeadUnitNetworkService
    ...and stop the server with this one, triggered when disconnected from the car's Bluetooth:
    am stopservice -W com.google.android.projection.gearhead/com.google.android.projection.gearhead.companion.DeveloperHeadUnitNetworkService
    Macrodroid is also used to enable/disable the phone's hotspot when connected to/disconnected from the car's Bluetooth.

    On the head unit, once it connects to the phone's hotspot, I have Macrodroid launch HUR. All I need to do is tap the big WiFi button and HUR connects to my phone's Android Auto.

    As for your head unit not handling calls over Bluetooth, I'm not really sure. Maybe WiFi Launcher is starting when the phone connects to the car's Bluetooth, as it should, but screwing things up for you when you try to connect over USB. If you use your phone's hotspot, you don't need WiFi Launcher. If you use WiFi Launcher, you use your head unit's hotspot. Neither should affect the Bluetooth connection to your car's Bluetooth audio receiver (bar some 2.4GHz interference between WiFi and Bluetooth)

    Sorry for the long-winded reply; I was just getting frustrated seeing the same things said over and over again. Poor explanations plague this thread; hopefully mine isn't one of them!

    Please pull me up on any errors I've made here.
    1
    Im running the latest beta and Im having the delay issues with waze where it updates the car location on the map every couple of seconds and doesnt show the speed.
    Somehow google maps works fine.
    The only way i can get waze to show my real location and speed is turn off all the GPS setting options within HUR. Means you have to rely on your phones internal GPS for all the location data but it works flawless for me that way.

    Only impacts waze running HUR for me, perfectly fine leaving them enabled for google maps or in other android auto emulators.
    1
    It seems different for almost every head unit. 5.2 worked fine for me on a Pixel 2 Android 11. Phone calls worked properly, Google maps was working great, Assistant was fine.

    I got a new phone (Poco X3 NFC) which I rooted and installed Arrow OS and AA. 5.2 worked fine, but I can't be sure that I checked the phone. I installed beta 4 and it worked fine, except for the phone issue. Went back to 5.2 and the phone calls were now on the phone speaker. Everything else through the head unit, no problem. RC3 has the phone issue, but everything else runs as expected.

    I have not been able to resolve this yet. I'll go at the bluetooth again today, but I think I did that right the first time.

    I'm curious as to why Waze is used in place of Google Maps. I don't use Waze, as GM works perfectly in my case. Waze seems to be problematic.
    In your car without hur can you play music from your phone via Bluetooth, if you can then that's the way to go. Then with hur running don't sink the music. As for waze problem you can pick maps from the app screen and from then maps will be the default GPS.
    1
    Are your phone calls going through the head unit or the phone?

    Through headunit when BT is connected
  • 66
    This Threader is a Spin-off of the original: [Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p by the late :crying: @mikereidis.

    App links: https://www.b3itlabs.com/prod.php?id=1
    PlayStore: https://play.google.com/store/apps/details?id=gb.xxy.hr

    Previous XDA Lab purchases can be downloaded using: https://www.b3itlabs.com/download.php

    Last edited: 07/02/2021
    Version 6.3 Beta 1 released
    - Re-wrote whole rendering process to use GLES20, in simple terms video render should use GPU
    - Much better scaling approach
    - 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.
    - Changed key mapping, user can now define their own buttons as they wish.

    Last edited: 21/06/2020

    Version 5.2 released
    - Removed WiFi Direct
    - Improved menu UI CREDIT and THANKS TO @sebaw
    - Updated margin setting
    - Added option to record audio using BT mic (motorcycle helmets)
    - Added button to reconnect WiFi connection ( phone and unit depended won't work on all units, please read app forum for how to connect)
    - Option to disable touchscreen
    - Removed brightness adjustment (some users experienced problems adjusting brightness after using previous version, sadly they need to do a factory reset of the unit, and update to current version)

    Version 5 released
    - New UI CREDIT and THANKS TO @sebaw
    - New over-scan approach allowing any resolution units to work properly (including portrait mode)
    - New mic source (should help with speech recognition)
    - Added option to keep status bar (user request)
    - Added welcome setup
    - Added possibility to use old USB driver (android built in one) in case you cannot get it connected with the new version
    - Added option for Gain control on mic
    - Added option to keep Wifi off (for USB use)
    - Changed Wifi Direct implementation (you will need to install the Wifi Launcher for HUR on the phone to use Wifi Direct)
    - Removed option to stretch full screen as this is not needed any more (it will always be full screen)
    - Fixed Incoming mode not setting password for some devices
    - Fixed app crash when Wifi toggled during app running
    - Fixed night icon colors for devices running 4.x
    - Fixed app freeze if permissions denied
    - Fixed app crash after device unplugged when using native android USB driver.
    - Fixed day/night calculation if share GPS turned off
    - Code cleanup
    - Other bug fixes.

    Also a big THANK YOU to @ppietak for helping with code cleanup and bug fixes!



    Version 4.5 released
    - Fixes for USB shuttering
    - New USB driver
    - Fixes for reverse camera not resuming on some units
    - Added support for incoming connection listener (automating Wifi) - Experimental, read below how to connect


    Version 4.4 Released
    Change log

    • Fixed broken touchscreen
    • Changes on WideScreen mode and HD
    • Fixes for Rotary
    • Potential fix for black screen for second connection over Wifi
    • Left/Right hand driving position option (for widescreen)
    • Buffer setting for mic (could help when Assistant does not hear what you're saying)
      Enjoy XDA Ad Free and check out:

    Version 4.3 Released
    Change log

    • Fixed double skip on Spotify when using SWC
    • No more decoder workaround needed (updated code for video playback)
    • Added support for rotary (arrow keys can be used for non-touch input)
    • Enhanced mic input (mic sampling rate can be adjusted in settings for better compatibility)
    • Added intent: "gb.xxy.hr.WifiP2P" for Wifi-Direct start
    • Added app color scheme (dark menu for night)
    • Mapped Key N to open Maps (N=Navigation)
    • Mapped Key L to open Multimedia (L = Listen)
    • Changed USB code, hoping to help those who suffered for USB disconnection problems
    • Fixed a serious bug in share GPS code
    • For some rooted android headunits the app can now disable the default call screen being overlayed when HUR is running (only if HUR is set as the navigation app!) This will require ROOT


    Version 4.1 Released
    Change log

    • Removed Google Play Services dependencies
    • Honda compatibility fixes
    • Some other small bug fixes

    Version 4.0 Released

    How to use the app?
    USB Mode

    • Plug in the USB to your device (in case of tablet use an OTG cable), when prompted make sure you allow HUR to be the default app for the action and you check the always box.
    • If you are running the app on a device with Android 7.0 or higher, you might need to pull down the notification bar and select the connected USB device before the app starts (this is device dependent)
    • If the app does not start automatically when you plug in your phone, you can always open HUR, tap the USB button and select the phone from the list.

    Wifi Mode
    READ SECOND POST

    Incoming connection Mode
    READ SECOND POST

    Self Mode (when Android Auto and HUR are running on the same device)
    • Open Android Auto on the phone, go to Settings and tap the Version 10 times to become a developer
    • Once you are a developer from the 3 dotted right corner select Start Headunit Server
    • Close Android Auto
    • Start HUR
    • Select SelfMode

    FAQ / Troubleshoot

    All I get is a black screen

    - If you are using an Android powered headunit (Joying, Xtrons, etc) look for a setting on your device which allows Video Playback during drive
    - Try changing HUR settings and enable Software decoding

    HUR crashes after start
    - Try changing HUR setting and disable "Media Workaround"

    Wifi Autostart doesn't work
    - Option will be removed as it's not deprecated. See intents below on how to achieve this.

    What does the "Share GPS" do?
    - Share GPS actually forwards the GPS data of your device to the phone, so phone will need to do less work, comes really handy if you have an Android powered headunit, with external GPS antenna, however, if you using a tablet which is built into the dashboard, it's possible that you want to turn off this feature, because your phone will have a more accurate GPS fix.

    What is the Sink Audio
    - This option enabled HUR to work as a speaker for your phone. If you disable this option, all the sounds will be outputted on your phone speaker (or if your phone is connected to a Bluetooth device, then they will be played back on that)

    My carrier doesn't provide data allowance for Wifi, what can I do?
    Wifi data used between phone and tablet is classed as intranet not internet so it won't count against your data usage, but do be careful if you have auto-updates enabled on the device running HUR those updates will be downloaded over the phone's Wifi hotspot and that will incur data costs.

    I have audio-sink enabled but phone calls are coming from the phone speaker. Why?
    Android Auto is designed to sink all the audio over USB (Wifi) except phone calls where it will ALWAYS use a Bluetooth headset, if none is connected it will just flip the phone to speaker mode.

    Are any hardware keys supported?
    • Volume Up
    • Volume Down
    • Media Next
    • Media Prev
    • Media Play
    • Media Stop
    • Media Rewind
    • Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
    • F key - Same as Phone Key
    • M Key - Mic
    • H Key - Takes you to home screen

    What about intents?
    • gb.xxy.hr.WIFI_START Can be used to start HUR and try to connect using Wifi.
    • gb.xxy.hr.playpause Same as pressing the Play/Pause media button.
    • gb.xxy.hr.next Same as pressing the Next media button.
    • gb.xxy.hr.prev Same as pressing the Prev media button.
    • gb.xxy.hr.mic Triggers microphone input.
    • gb.xxy.hr.phone Same as pressing the dial key (answer phone call when ringing, takes you to dialer screen otherwise).
    • gb.xxy.hr.day Enables day theme.
    • gb.xxy.hr.night Enables night theme.
    • gb.xxy.hr.togglenight Switches between day and night theme.



    I need more help.
    - Feel free to ask a question on this thread, or you can always drop me an email to [email protected]

    How do I collect a bug report / logcat

    1. Enabling Developer Mode

    • 1. Open Settings > About phone.
    • 2. Scroll down to the Build number.
    • 3. Tap the Build number 7 times in quick succession until "You're now a developer" appears.
    • 4. Return to the Settings menu and select Developer options.
    • 5. At the top of the screen, make sure 'Developer options' is set to On (green).
    • 6. Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
    • 7. Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.


    2. Capturing a Bug Report
    It's very important to do this right after you experience the issue again, so your device can log at least one occurrence of the issue.
    • 1. Hold the Power button down until the menu appears.
    • 2. Select Take bug report. and wait for the device to capture the bug report.
    • 3. Tap the 'Bug report captured' notification when it appears.
    • 4. Share the bug report. (I recommend to email it to yourself.)
    • 5. Download the bug report to your computer.
    • 6. Send the bug report by email to [email protected]


    Setup demo


    IF YOU UPGRADED TO ANDROID AUTO 2.X

    Dial Pad is broken - Workaround available:
    - Open AA -> About -> 3 dot menu -> Developer settings -> Application mode -> change to developer. This will bring back the Dial screen.

    Version 3.0 Released
    Changelog:
    • - Move USB functions from C to Java
    • - USB popup numbers limited to 2 and they should remain saved
    • - App will only start on a phone manufacturer vendor
    • - App is now running in multi-thread for better performance
    • - Much enhanced Wifi speed
    • - Better USB stability
    • - Should work on RK3188 units as well
    • - App runs as service so can be run in the background as well
    • - While running in background supports notification control for media
    • - While running in background on units running 5.0+ and above you will enjoy Heads-Up notifications for navigation
    • - Ability to rename the "Headunit" to your own prefered string.
    • - Fixed Wifi-Direct so can connect over Wifi-Direct as well, but not all devices seems to work
    • - Moved string to XML so translation to other languages should be implemented in the future
    • - Fixes some memory leaks
    • - Supports custom hardware keys

    Version 2.5a Released
    - Fix for USB close bug in 2.5

    Version 2.5 Released - Attention contain BUG
    - Left/Right button goes into endless loop
    - Added support for ARM64
    - Changed car name from Emil to Headunit
    - Added mirror output support for HUD display.


    Version 2.4 Released
    - Improved performance (Wifi should be on par with USB now, even with Audio transport enabled)
    - Improved touch sync (no accidental long touches and other strange occasional bugs)
    - Option to share the GPS with the phone (reduce battery usage footprint on phone)
    - Final fixes for Day/Night calculation and theme switching
    - Auto volume adjust fixes (on supported ROM, the volume adjuster is hidden from the user)
    - Software decoding works with Audio as well.


    Version 2.3 Released
    - Improvements and fixes for auto volume adjust
    - Improvements and fixes for hardware key input
    - Wifi speed improvements (should be able to run smoothly even with transport sound enabled)
    - Tweaks for SelfMode (home and recent app button can be used to gracefully exit the app)
    And the biggest change:
    - Unlimited Browsing support - This is experimental and hacky it's possible that Google will close the loophole at some point but for the time being it works.




    Version 2.2 Released - With some major changes
    - Fixes for Communication Error 2 received with Play Service 10.X
    - New Self mode
    - Corrected channels order
    - Unlimited browsing working when car is parked (only for Android Auto 1.6)
    - Totally changed the Day/Night toggle logic, now the calculations are done inside the headunit app and updated each 10 minutes, so if you're driving all day the sunset/sunrise should be correct. even if you are 500 miles more to the north or west or whatever.
    - Added Auto adjust volume option (works for bluetooth audio as well).
    - Changed all the key mapping, and using real keys instead of simulated touches:

    Supported hardware keys:
    1. Volume Up
    2. Volume Down
    3. Media Next
    4. Media Prev
    5. Media Play
    6. Media Stop
    7. Media Rewind
    8. Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
    9. F key - Same as Phone Key
    10. D key - Changes to Day theme
    11. N Key - Changes to Night theme
    12. M Key - Mic
    13. H Key - Takes you to home screen

    The following keys are still usable but they are based on simulated touches:
    • Up Arrow = Scroll Up
    • Down Arrow = Scroll Down
    • Left Arrow = Moves to next Left tab
    • Right Arrow - Moves to next right tab



    Version 2.0 Released
    Changelog:
    - Fixed calculated night mode
    - Added support for Software decoding (should work now with any device) - If you have problems running HUR, go to settings and enable Software decoding. Do not use software decoding with audio transport, the audio playback will suffer a lot, consider streaming the audio from the phone to a A2DP directly or using a cable to connect the phone Jack to the stereo AUX, or if your phone is rooted you might want to consider Wifi Audio streaming app, it's too much to ask from the Software decoder to do both Audio and Video, unless you have a very strong CPU, but if that is the case I'm pretty confident that the Hardware decoding will work on the device.
    - Added option for letterbox display (prevent distortion of stretch)
    - Added option to start the app when connected to Wifi

    Software Decoding
    - Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.


    Version 1.5 Released - Key features
    - Stable Wifi connection
    - Added support for Android 7.0 (Self mode as well)
    - Self mode running in stable and usable way
    - Connecting USB cable will start app automatically (even if phone is running Android 6.0 or 7.0)
    - Supports keyboard shortcuts:
    1. M = Start the Mic
    2. N = Navigation Tab
    3. P = Phone Tab
    4. H = Home Tab
    5. E = Entertainment Tab
    6. UP Arrow = Scroll Up
    7. Down Arrow = Scroll Down
    8. Left Arrow = Moves to next Left tab
    9. Right Arrow - Moves to next right tab
    10. S = Play/Pause button (only works in Entertainment tab)
    11. F = Next track (only works in Entertainment tab)
    12. R = Prev Track (only works in Entertainment tab)
    - Uses light sensor (if available) for toggling Day/Night theme.


    If you are updating from version older than 1.2 please read:
    You won't be able to install it over the old one (Key signature changed!), so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
    1) On XDA Labs, click the download Stable
    2) When prompted to install select Cancel
    3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
    4) Locate the newly download APK and copy it somewhere else.
    5) Uninstall the old version
    6) Install the APK which you just copied.
    If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.

    App requirements:
    - Android 4.1 or higher
    - H264 Hardware decoding!

    How to use the app: (Please read this steps before asking for help)
    1) USB OTG
    - Plug in the OTG cable to your tablet, connect your phone, done!

    2) Self mode (for AA 2.0) - See Video
    - Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
    - Exit Android Auto
    - Start HUR and select Self

    3) Wifi
    - From the phone create a Wifi hotspot
    - Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
    - Connect your tablet to the newly created Wifi hotspot
    - Start the Headunit Reloaded app
    - HTC ATTENTION! If your phone is a HTC, please change the default IP address to: 192.168.1.1
    - Select Wifi

    4) Wifi Direct (not supported by all phones/tables)
    - Start Headunit Reloaded on the tablet
    - Select Wifi Direct
    - On the phone go to Settings -> Wifi -> Advanced -> Wifi Direct, join the group. (Do not try to connect as to a normal Wifi it will not work!)
    - On the phone start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"

    Other important notes:
    Software Decoding
    - Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.

    To exit the app
    If you are connected with USB, just unplug the USB cable, DO NOT use the exit from the menu. If you are running Wifi, Wifi Direct or Self mode, ALWAYS use the exit button from the left drawer menu!

    Audio transport option
    Will forward (sink) all the audio from the phone to the tablet if enabled, EXCEPT phone call audio, that will go trough the phone speakers or Bluetooth Handsfree if connected. If you wish to stream all the audio from the phone directly to your A2DP bluetooth, then simply disable the Transport Audio option.

    Day/Night toggle
    The device running the Headunit Reloaded app will be responsible for changing the theme. You can chose between using the light sensor of the device to toggle between day and night mode, or you can use calculated sunset sunrise mode, or even force it to one theme only. If you have previously installed AA Helper to your phone, please uninstall it!

    Auto Start on Wifi
    This option will launch HUR whenever you are connected to a Wifi (specific Wifi can be named)

    Auto increase volume on speed
    The logic behind is a very simple approach, every time the speed increases it will send a vol + key to the phone and every time the speed decrease it will send a vol - to the phone. This requires the device running HUR to have a GPS receiver.



    OLD STUFF:

    Version 1.3 (Wishlist version) - Released
    - Added option for easy car mode toggling. (Car mode can be disabled if not using Self mode - avoid conflict with other Car apps)
    - Auto Hide status + action bar while running the app no need to use the Hide option from menu
    - App will automatically close when Wifi connection is lost


    Version 1.2b - Released
    - Buffer overflow protection - Special Thanks to invis-zz from GitHub (https://github.com/invisi-zz) - This should random crashes while using the app.
    - Removed Send Log feature (it was classed as backdoor/trojan and Google was blocking the app on playstore)
    - Updated OpenSSL library to 1.0.1t (used OpenSSL contained vulnerabilities and Play store blocked the app)
    - Managed to get the app on PlayStore (wonder if it will stay...) - https://play.google.com/store/apps/details?id=gb.xxy.hr
    Signature Key changed!!!!
    I had to update the APK signature key (I'm trying my luck with Play Store), this means if you try to install the new version you won't be able to install it over the old one, so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
    1) On XDA Labs, click the download Stable
    2) When prompted to install select Cancel
    3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
    4) Locate the newly download APK and copy it somewhere else.
    5) Uninstall the old version
    6) Install the APK which you just copied.
    If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.



    Version 1.1 Stable - Released
    Jumping the version number due to significant amount of changes:

    • Removed Day/Night/Auto mode (see bottom of this post for a better solution.)
    • Added new setting for 720p Video - Fully working now (even on Wifi)
    • Changed Self mode start sequence (if the phone is rooted it will start automatically and then go back to HU), if your device is not rooted, please use the following sequence to start Self mode:

      1. Start HU app
      2. Select Self mode
      3. When AA opens select Start Developer Server
    • Added support for hardware keys (simulating touches), so if your tablet is integrated with the car remote you can control AA from the remote.
      Hardware keys as follow:
      1. M = Start the Mic
      2. N = Navigation Tab
      3. P = Phone Tab
      4. H = Home Tab
      5. E = Entertainment Tab
      6. UP Arrow = Scroll Up
      7. Down Arrow = Scroll Down
      8. Left Arrow = Moves to next Left tab
      9. Right Arrow - Moves to next right tab
      10. S = Play/Pause button (only works in Entertainment tab)
      11. F = Next track (only works in Entertainment tab)
      12. R = Prev Track (only works in Entertainment tab)
    • Some other minor tweaks, to improve stability and make Self mode connect 9 out of 10 times.
    • Fully integrated x86 native binaries
    • Declared app as CAR HOME, for those using SelfMode it is crucial, that when you get prompted which should be the default CAR HOME app (Android Auto or HU) you select HU!!! - This is needed to be able to bring back the HU on top after a successful connection is established. AA is trying to override everything..... and to block the user out of his phone as soon as it's connected to the car.
    • Transport Audio option will affect USB connections as well (You can keep the audio on your phone/bluetooth, when connected with the OTG cable)



    Version 1.03b released - Beta

    - You will find it in XDA Labs (under the Beta version)
    - Fixes Wifi/Self mode for some devices which didn't connect before
    - Increased stream buffer size to match the DesktopHeadUnit app (128Kb vs 64Kb)


    Version 1.02 release
    - Fixed wifi not connecting on some device only after numerous attempts (see explanation below if interested)

    The issue looks to be related to the timing, on some occasions and on some devices the phone either sends the SSL data too soon, either too late, either to slow :) and because the TCP socket is set to non-blocking mode, it can end up in a missed packet in the initial Handshake. I have tweaked this now, so the TCP socket will connect in non-blocking mode, but will switch to blocking mode and wait for full message after a successful connection and once the SSL Handshake is out of the way it will revert back to non-blocking mode, uhhh event reading this makes me dizzy :)
    This however could make the initial startup slightly slower than it was.

    - Corrected AutoStart option (Working properly now)
    - Fixed USB device overlapping Settings text on the drawer menu
    - Added "Send Log" function to be used if there are problems for easier debugging.


    Version 1.01 released

    - Potential Wifi disconnect fix (see: http://forum.xda-developers.com/showpost.php?p=68078605&postcount=16 for details)
    - AutoStart option added to the menu


    Very sadly Mike passed away this year and his software stopped working after a Google Update, he left us a slightly outdated GPLv3 version of the software at: https://github.com/mikereidis/headunit which I have used to rebuild (or ty to) rebuild up to his latest build with some additional small modifications as well as fixing the issue caused by Google.

    The forked version can be found on: https://github.com/borconi/headunit if anybody is intersted.

    Since the app released by him isn't working any longer I have created the new version of it and slightly re-name it just to avoid any confusion.

    I take almost no credit in this app, except for some minor changes, and finding the fix for what Google have broke (changed), which was a painful task.

    I'm not a developer as such, and this app would never have existed if it wasn't for @mikereidis, however I have spent now several weeks studying the app and understanding how it's working and I plan to continue with the maintenance/development of the app.


    I have published the app on XDA Labs under the new name: "Headunit Reloaded Android Auto" and it is now available for purchase. As I have stated previously I'm intending to support all of Mike's customers, so if you have purchased Mike's application before, please email me a proof of purchase to [email protected] and you can have a free copy of the spin-off app.

    How to use (Self / Wifi ) ?
    1) Self mode.
    See instructions in version 1.1

    2) Wifi Mode
    Start AA on your phone, tap the header 20 times till you become a developer, once that is completed from the menu select Start Head Unit server. Now start tethering on the phone, connect the tablet to the newly created wifi hotspot, start HU on your tablet and select Wifi. This will make the HU app try to connect to the default Android gateway (192.168.43.1), if you need to change this, use the Settings menu from the HU option list. If HU doesn't start on first, do try a few more times, first setup sometimes proves tricky. If this is the first time you connect your phone to the a HU, please make sure you answer all the questions on the phone.

    3) Wifi p2p
    This is not supported by all devices and might not work for your device, plus sometimes it can be slightly buggy. Start WifiP2p on the tablet from the HU. On the phone go to Wifi Direct (this is usually found in Advanced Wifi settings settings - DON'T TRY TO CONNECT LIKE TO A NORMAL WIFI and look for a new available connection. If you can see one tap to join. Once you joined the network, give it about 30 seconds or so, then open the AA on the phone and start the head unit developer server (same as describe it above). If you're lucky it will work instantly, if not you might need to play around with it.


    Other Options:
    Possibility to toggle the Audio mirroring when using a Wifi connection. By disabling the Audio mirroring, you will keep all the audio on your phone rather than on the tablet (or on the handsfree) if the phone is connected to the handsfree. This will improve the performance greatly, since audio will use up a significant quantity of Wifi bandwidth when communicating between the 2 device.


    USB OTG connection.
    Have remained unchanged and it will work same way it did till now, see original threader for details.

    I will monitor both Threads and will do my best to help and support everybody.




    12
    Wifi Mode Setup - Starting with HUR 5.2

    Method 1 (prefered)
    Only available if phone runs Android 9 or higher
    Phone Setup:
    1. Install Wifi Launcher for HUR on the phone ( https://labs.xda-developers.com/store/app/com.borconi.emil.wifilauncherforhur thanks to @gvillo89 for rewriting the app)
    2. Open the app and select the car's BT adaptor from the list (make sure phone is NOT connected to the car's BT, but BT is enabled!)
    3. For Android 10 and above make sure you set location permissions to ALWAYS, otherwise it won't work
    Car/Headunit setup:
    1. Enable Listening mode in HUR -> Settings -> Connectivity
    2. Restart HUR
    3. If phone is already connected to the car's BT disconnect and reconnect
    Using the WiFi&BT button
    - This won't work on all units. It needs to know the phones BT address (you can set it up in HUR -> Settings -> Connectivity).
    - Phone setup is identical as above, but it becomes mandatory to give WiFi Launcher access to notifications!
    - When you press the button on the car screen it will turn on the hotspot and send a message over BT to the WiFi Launcher app which will try to initiate the connection

    Potential problems & solutions:
    • HUR can't turn on WiFi:
      - you can try to use other ways to turn on the hotspot, for example manually or using tools with root access
    • HUR can't automatically configure the hotspot:
      -This will happen if the unit running is based on Android 8 and above. Make sure you manually set the hotspot name to: HUR and the password to: AndroidAutoConnect
    • Phone connects but has no internet access:
      - Each phone is different, but usually there is some setting under the phones WiFi settings which suggest to allow mobile data while connects to WiFi. In some cases you have to forget the HUR network on the phone, then when you re-connect to it make sure you don't tap the notification which says the WiFi has no network. Hard to give exact advice because of so many different implementation on phone side.


    Method 2
    Available on all phones including those running Oreo and below

    Phone:
    1. Open Android Auto
    2. go to settings, scroll down and tap the "version" 10 times you will become a developer
    3. Now from the 3 dotted top corner menu select, "Start headunit server"
    4. Exit Android Auto
    5. Create a Wifi hotspot
    Car/Headunit:
    1. Connect to the phone's hotspot
    2. Open HUR (Headunit Reloaded)
    3. Press the Wifi button.

    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.
    C1at7OvC3vWppAW_DEEcw4PQKqdV1QY28I1qO1FE5r8qIzmrb7NMreaoEuN0DJxCnFTk4kMEiHdDNw=w1920-h902-rw


    S0Ylty7QO023gJUkqAdw34yryW8AE2oQXjTwGDpYY_0aqFnwDf3SwlG_Vsu9S9SLL0s371iPFWeaIn3pW42UWfFy68Gb0g=w1920-h432-rw
    11
    Hi guys.
    As you probably know I'm pretty busy with a major project which means way less time for XDA. Sadly as we know XDA Labs went down for a while, and there are many of you who have purchased the app on XDA Labs and not able to access it any longer.

    For all those, you can now used the following link: https://www.b3itlabs.com/download.php you will need to fill in the paypal email address you used to make the purchase, the page will then generate a one time unique link which will be emailed to you.

    Link will allow you to download to pick and download the APK.

    As I've said all links are one time use only, so you won't be able to share those links, if you need to re-download the app, you will need to request a new link.

    I will be adding checkout option to the website as well hopefully in the near future so new users can get a copy of the apps if needed.

    If you need any support, please contact me directly by email.

    P.S. I'm working on a new version, of HUR, still need to fix some bugs, but should be a pretty big step forward compared to previous version.
    10
    Isn't that exactly what you just joined up to do?
    You didn't join to ask a question. You could have started with telling us what device and Android version you are trying to connect with/to, and perhaps someone could help you constructively.

    Sent from my ELE-L29 using Tapatalk

    @googlebox:

    Normally I try to take criticism in a positive and constructive way and I try to improve my service I'm providing.
    Also when you bought the app you did bought support with it as well, indeed the app help button brings you to this thread as 99% of the issues/problems/solutions have been discussed in here, but in case you are still lost or not sure, you can at any given time shoot me an email and normally I reply in max 24 hours. If there is one thing I pride myself with is that I really do my best and try to go the extra mile to give support to all users, which is sometimes an extensive and exhausting thing to do, and this will be reflected in the reviews as well.

    Now to echo the above quote, without actually saying what is the problem, where are you stuck, what have you done, it's really hard to give you any guidance.
    Judging from your comment, I'm guessing that you try to connect the 2 devices over WiFi but maybe I'm wrong and you try to connect them over a USB cable, while I don't like to be arrogant, I will make an exception this time. The LAYMAN, will understand to have Android Auto wireless in a car it will cost him $500+ if he/she goes to buy a Kenwood/Pioneer receiver and then pay another $100+ for fitting. The layman won't try to cut the corner and have some tablet fitted into the dashboard trying to mirror the screen, that is not a layman any more. So if you do consider yourself a layman, please feel free to go and pick up a unit which can offer you the desired solution, I will refund you the app price no problem so you can spend it on that solution.

    I have never ever refused a refund from anyone even if they used the app, if they weren't happy with it, I even send copies away for free, when some users contacted me that they can't afford it, I've spent sometimes hours with users on different issues and support, in some rear cases I drove down to personally help out the users so your comment, really made it personal and I think this is the very first time I took a comment personal. So to answer you in a question, RTFM if you can't manage tough luck shoot me an email and I'll refund you.
    Once again I do apologise for the harsh language.
    9
    Next beta will have a bonus surprise.... one more service is now decoded... :D
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone