[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

Oceloti

Member
Dec 4, 2014
12
3
I have trial version, USB Connection working, but I connect my phone to hotspot from my head unit ( I have working Huawei E3372h modem usb), but when I try connect HUR via wifi I have connection refused error.

I have enabled wireless AA connect and wireless debuging

Can someone help me
For me, the Trial version and the fully paid version worked completely differently. The trial is super old version and very antiquated.

The only way to know if it will work for you with your setup is pay for the real version and try it.
 
Last edited:
  • Like
Reactions: lew26

iHusky

Senior Member
Mar 5, 2012
557
49
32
Mikołów
For me, the Trial version and the fully paid version worked completely differently. The trial is super old version and very antiquated.

The only way to know if it will work for you with your setup is pay for the real version and try it.
I bought a full version app ( installed on headunit) still can't connect via wi-fi, Hotspot running on headunit and phone is connect to this hotspot. BT wireless is disabled, and I can install wifi launcher on HUR only in headunit.


Do something with this, why I must make hotspot on phone site? And why BT is disabled?

I have eunavi on PX5
 

drummerclave

Member
Jan 17, 2020
20
2
Is there something else I need to do to get wireless working? I updated hur to the beta version in playstore and after launching it says my Bluetooth adapter is capable of native android auto. So I unpaired and paired again like it says to do and nothing. When I press the wifi/Bluetooth button it has my phone listed and when I press it nothing happens. USB connection works flawlessly
 
Jul 10, 2017
6
0
Ok, i got it working with regards to scaling.

Can someone please answer this question. My headunit is a vertical unit with 768x1024 resolution (not 1024x768)

I have set the following settings and it looks great:

Overscan: ON
Pixel Density: 170
Resolution: 1920x1080

Can someone please confirm that setting pixel density and resolution here does NOT actually adjust the REAL pixel density and resolution of the display - this is only virtual settings within headunit reloaded android auto emulator, right?

In other words, I will not damage my display by changing the pixel density and resolution within this app?

Thank you.
 

gljones2001

Member
Aug 10, 2016
30
14
Bourbonnais IL
Ok, i got it working with regards to scaling.

Can someone please answer this question. My headunit is a vertical unit with 768x1024 resolution (not 1024x768)

I have set the following settings and it looks great:

Overscan: ON
Pixel Density: 170
Resolution: 1920x1080

Can someone please confirm that setting pixel density and resolution here does NOT actually adjust the REAL pixel density and resolution of the display - this is only virtual settings within headunit reloaded android auto emulator, right?

In other words, I will not damage my display by changing the pixel density and resolution within this app?

Thank you.

It's not setting the pixel density of the display. If you press the home button, it goes straight back to the home screen without blanking out. This shows that it is not resetting the display settings.

Also it would not damage the display by changing the pixel density at all. That is fully a software thing, not a hardware thing. It just changes how the board displays to the screen, not what the screen actually does.
 
  • Like
Reactions: rey_1178

mattboy9921

Senior Member
Jul 1, 2012
66
17
Newtown
Has anyone found a surefire way on Android 11 to get the phone to connect to the head unit's hotspot? For myself, sometimes it will connect but most times not because it knows the connection has no internet. I tried AutoTools but I think the latest API prevents it from working.
 
  • Like
Reactions: iHusky

iHusky

Senior Member
Mar 5, 2012
557
49
32
Mikołów
I have this issue too, but on Android 10 in my phone, this is stupid, that I can`t connect AA to headunit using hotspot from headunit site. Yes I know that if I have USB modem, without Wi-Fi function, I can`t connect headunit to Wi-Fi network, but if developer could add server to connect this two apps, I mean AA and HUR, using wire or wireless ethernet connection.
 

dada56

Member
Sep 4, 2013
19
6
On latest version 6.3 rc3 have to choose between the lesser of two evils: 1. pixlelated (not sharp) gles 2.0 image or, 2. Surface view that is not streched out all the way (sideways, 2 black lines on either side) thus giving up expensive real estate. Can you fix please?
 

cybertech

Senior Member
Sep 16, 2006
196
8
That's a difference we have then, i have full voice functionality in 5.2 stable. Hey google, responding to msgs etc all works flawlessly in 5.2 and 6.3 RC.
.
.

Just tried switch back to 5.2 stable and confirmed that voice command does not work for my case. I say out "hey google ... read message" I can see the blue red orange green dot appear and moving but never read out my message. For 6.3 RC2 or 3 it will read out my message and even I say "Make a Call" and it will ask "Who do you want to call".
 

lew26

Senior Member
Nov 1, 2019
105
12
On latest version 6.3 rc3 have to choose between the lesser of two evils: 1. pixlelated (not sharp) gles 2.0 image or, 2. Surface view that is not streched out all the way (sideways, 2 black lines on either side) thus giving up expensive real estate. Can you fix please?
My HU falsely failed hardware acceleration test. I solved the issue you described by enabling hw decoding, even though ny unit failed the test
 

Oceloti

Member
Dec 4, 2014
12
3
Just tried switch back to 5.2 stable and confirmed that voice command does not work for my case. I say out "hey google ... read message" I can see the blue red orange green dot appear and moving but never read out my message. For 6.3 RC2 or 3 it will read out my message and even I say "Make a Call" and it will ask "Who do you want to call".
Its a hard one alright. We all have such different systems. For me the Hey Google recognition has always been fine, beta or stable. Does the google assistant work for you if its triggered by pressing on the microphone or via a steering wheel control?

The main thing that's hurting me now is my steering wheel controls aren't mappable and don't work in the beta but work perfectly on stable and I'm sure that's not the case for anyone else. It would be nice to have the 5.2 pre-set button mappings in the beta as an option.
 

moba77

Member
Nov 8, 2013
22
4
Hi) I have a question regarding internet connection : I've installed on my mobile phone WiFi launcher and when I start the headunit it discover Bluetooth, it connects successful. I have changed options on headunit reloaded to start hotpspot and finally android auto starts. The problem is that it seems offline , no connection available. Have I done some mistakes? Thanks for support
 
Last edited:

lew26

Senior Member
Nov 1, 2019
105
12
RC3 is working reasonably well. I'm using a Klyde PX5 HU running Android 10. This might help others.

  1. I connect with USB. Plugging in the USB cable, after HU fully boots, only brings up the HUR menu. Unplugging and replugging brings up AA. Not an issue with 5.2
  2. HU fails video hardware acceleration test. 5.2 passed. Hardware acceleration works.
  3. USB cable. Google AA suggests USB cable choice is important. Google suggests short and high quality. The selling point of many cables is low price and the longer the better. I've had good luck with Cable Creations. Braided cable. Available .5 foot .80 foot. Longer is also available. Available on amazon.
Edited to add google voice works using mic icon on screen or by saying hey Google. Voice command to summon Google didn't work with 5.2

No matter what I do the steering wheel voice button summons Google on the HU and not from my phone
 
Last edited:

nandroidint

Senior Member
Apr 2, 2018
56
23
For people wondering how to get AA via wireless this is the steps to take:

1. Rename the hotspot of your headunit to the hotspot settings that HUR requires:
a. Name: HUR
b. Password: AndroidAutoConnect
2. Make sure your HUR is in the latest version, as of now its v5.2 from the playstore
3. On HUR, make sure you have wireless incoming enabled, its in the connectivity settings of the app
4. Go to your phone's playstore and download the app "WiFi Launcher", its from the same developer that created HUR, once it downloads, open it and it will ask you for a few permissions, make sure you allow those permissions since it won't work without them
5. Now, connect your phone to your android headunit's wifi hotspot you created in step one, make sure your phone connects successfully, after it does, open the HUR app and you should see "listening for incoming connections", at this point your phone should connect to your HUR app, it it doesn't, go to the "Wifi Launcher" on your phone and go to advance settings and click on "Start WiFi service manually", at this point it should connect.

Mine was working fine but than for whatever reason it's failing now, i open the HUR app and it seems like my phone will automatically connect but the HUR app flashes and it auto closes, not sure if someone has had this issue on their systems
 
Last edited:
  • Like
Reactions: Nickinatorz

cybertech

Senior Member
Sep 16, 2006
196
8
RC3 is working reasonably well. I'm using a Klyde PX5 HU running Android 10. This might help others.

  1. I connect with USB. Plugging in the USB cable, after HU fully boots, only brings up the HUR menu. Unplugging and replugging brings up AA. Not an issue with 5.2
  2. HU fails video hardware acceleration test. 5.2 passed. Hardware acceleration works.
  3. USB cable. Google AA suggests USB cable choice is important. Google suggests short and high quality. The selling point of many cables is low price and the longer the better. I've had good luck with Cable Creations. Braided cable. Available .5 foot .80 foot. Longer is also available. Available on amazon.
Edited to add google voice works using mic icon on screen or by saying hey Google. Voice command to summon Google didn't work with 5.2

No matter what I do the steering wheel voice button summons Google on the HU and not from my phone

On your point 1. , I also need to plug in and unplug then re-plug the USB cable and only then it will bring up AA. I have found out for my case was because HUR already running when I plug in my phone USB cable. #If I close/quit the running app HUR and after that plug in the USB cable, it will brings up AA after showing the HUR menu for 2 to 3 seconds without the need to plug unplug and re-plug USB cable. Now I am finding ways to close/quit the running HUR after I have turned off car engine because whenever I starts the car and the Car HU starts up, I can see the HUR is already running in the background. Trying to minimize steps #.
 

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.
    1
    Covid restictions have had me home bound for a while and I haven't had a chance to test HUR on a longer drive. I had a problem today.
    I used Google Maps to guide me to a location 1.5 hours away. About 2/3 of the way there I noticed that the vocal instructions and map location on the screen weren't in sync. The vocal instructions were up to date with where I was, but Maps on the car display was behind, around 5 minutes. On the way back I used Garmin on the car deck and had no issues.
    I don't know if anyone else has had this happen, or if it has happened if they figured out what it was and a fix.
    Not a big problem, as I knew where I was going. But on a trip where directions are needed, this would have been a problem.
    Have you enabled the option to disable touch restrictions? That seems to mess up the GPS in some instances.
    1
    NO, I hadn't read anything about that. I'll check HUR next time I get in the vehicle. Thanks.
    You know what, I thought I was in the AA wireless thread. But this may also apply to HUR. The option is called fake speed reporting or something like that in the GPS section. Play with that and the other option called GPS sharing, which I believe means Android auto will use the GPS of the tablet which sometimes is not that good.
    1
    Mine is a Honda stock head unit running 4.2.2. HUR I'm running 6.3 B4. The headunit bluetooth card was compatible with native wireless when I installed 6.3, but never did connect. I have tried both types, wireless and via hotspot.
    When I get a chance I will try your instructions today. My previous phone, a Pixel 2 stock worked fine when plugged into USB .
    The only issue I have with USB, is that the phone will not go through HUR. So in other words, if I ask assistant to call someone the call goes through the phone speaker, with or without audio synced. I have selected and deselected the phone in bluetooth settings. The car deck is awful to make calls through. The bluetooth assistant is terrible and it forces me through several menues before i can connect and make a call.
    So the head unit is rooted as well, and you installed HUR... What year is it? Are you sure it has WiFi? When you go to settings-> connection in HUR, is the first option you see "use native wireless AA method", or "listen for incoming connection"?
    1
    Yes, its rooted and that's how I got HUR installed.The first option is for native wireless AA. Its a 2016 Honda Pilot Limited. When I installed HUR 6.3 the phone confirmed that the bluetooth card was suitable for native wireless.
    It definitely does have wifi. I have connected to the hotspot on the phone.
    The deck must have been archaic in 2016. It is slow, the ui is poorly designed and in general it is subpar to other OEM's. But it did work on USB with 5.2 and a Pixel 2, no problem. The Pixel is gone and I have a Poco X3 NFC, running A11 and ArrowOS.
    Native AA works on 5GHz, which that head unit probably doesn't have, and I don't know if there's a fall back for 2.4GHz. What do you see on the screen I mentioned above?
  • 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