Hi. Version 5.2 is OK for me. But all versions 6.3 are bad for my radio. The application always crashes.
Attachments
-
PXL_20210302_134047668.jpg -
PXL_20210302_133941305.jpg
[Android 4.1+] HeadUnit Reloaded for Android Auto with Wifi
- Thread starter Emil Borconi
- Start date
I had the same issue of the app crashing. For me it seems that it was related to the gles 2.0 rendering. It stopped crashing when either changing to software decoder or changing the render surface from gles 2.0 to surface view in the graphic settings.
What's the name of the 3rd party app you used to get the native AA working on the HD 8 '20? I tried it with PDANet+ but that doesn't seem to work.
Steps I have taken:
1. Unpair phone and Fire HD 8 tablet with HUR.
2. Phone does not have AA server running for native AA mode.
3. Start HUR and get prompted to pair phone. Pair phone.
4. Click on WiFi button on tablet, select the bluetooth device "phone", and note the "Looking for Android Auto" notification on phone.
After #4 I see no progress, after "Looking for Android Auto" disappears. Restarted tablet, cleared cache/data etc. Nothing seems to work.
Also, tried setting up hotspot with PDANet+ between Step #3 and #4, with phone connected to it before #4 or not.
EDIT:
Not sure how, but I did get Android Auto is available, continue on your car screen once. I could only get it once. However, the HUR app does not respond to it, that is no sign of the AA thing on left in blue. This does mean that HUR can in fact launch a WiFI hotspot on the HD8.
Edit 2: Update to RC3 fixed it and it doesn't need any 3rd party app to do hotspot on HD8 2020 tablet.
Last edited:
Just pushed a new beta out, improved the native AA Wifi connection and fixed a few small other issues.
Works every time so far on my huawei tablet, doesn't pop up the dialog boxes asking you if you want to enable / disable Bluetooth. Brilliant work Emil
Should we uninstall RC2 before installing this RC3 or can just install to overwrite existing version?
Is this new beta still not available on the play store (where i purchased HUR)?
Looking to test it out at some point.
Looking to test it out at some point.
Agree that will be helpful if can provide the steps by steps guide in getting native AA Wireless to work. For me I am still using Wifi Launcher method as not able to get native AA Wireless to work properly, that is, sometimes it worked but most of the time it doesn't.
the version that are in playstore beta is already RC3.. I believe it is the latest one..
When you open HUR, go to settings and then graphics. It's an option in there.
Are you sure you're running the latest beta? I just got that option in the update yesterday I believe.
But the program crashes right after I start. In the new beta, I won't get into the setup.
Oh, I'm not sure. Mine is working fine, latest update from the play store on my chinese head unit. Maybe someone else has ran into this issue can can help?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3
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.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
2
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.11
Have you enabled the option to disable touch restrictions? That seems to mess up the GPS in some instances.1
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. -
66This 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
12Wifi Mode Setup - Starting with HUR 5.2
Method 1 (prefered)
Only available if phone runs Android 9 or higher
Phone Setup:
- 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)
- 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!)
- For Android 10 and above make sure you set location permissions to ALWAYS, otherwise it won't work
- Enable Listening mode in HUR -> Settings -> Connectivity
- Restart HUR
- If phone is already connected to the car's BT disconnect and reconnect
- 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:
- Open Android Auto
- go to settings, scroll down and tap the "version" 10 times you will become a developer
- Now from the 3 dotted top corner menu select, "Start headunit server"
- Exit Android Auto
- Create a Wifi hotspot
- Connect to the phone's hotspot
- Open HUR (Headunit Reloaded)
- 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.
11Hi 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
@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
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 
New posts
-
-
[OFFICIAL][ROM][PAYTON]LineageOS 18.1
- Latest: ferrazrafael
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