Was so looking forward to this. I have some books in Archive that simply fail to download to the HT7, others can take ages to download. Tried removing the app, de-registering on Amazon and re-installing, same issue. Anyone else seeing this ?
Ian
So far my books haved synced fine over Wi-fi. Are you using Wi-Fi or 3G? Do you get any error message?
I'm only attempting this over the WiFi network, it eventually gives up and says failed to download, try again.
The only real possible causes for failed downloads would be loosing wireless connection or Closing the application before the download has completed.
Well I thought this but the iPhone beside me downloads fine over wifi as do my various laptops with the Kindle app installed.
Maybe try de-registering and uninstalling/Reinstalling one more time? Don't know what else to suggest fella.
This is off the amazon website hence why i've quoted it.
Amazon Website said:
Book appears in Kindle Library and Archived Items but download failed.
Possible causes:
Lost wireless connection.
Application closed before download completed.
Confirm wireless connection and retry download
Check wireless data service or Wi-Fi is enabled on the device and that status indicators show an active connection. A wireless connection must be active.
Launch Kindle for Android.
Tap the Menu button, then select "Archived Items."
Select the desired title from the "Archived Items" list.
Leave your wireless connection and Kindle for Android app running until the download completes--do not leave the application.
If your wireless connection is interrupted and the download fails, attempt the steps above again when your wireless connection is re-established and active long enough to complete the download.
Confirm disk space is available
If you see the error message: "There is not enough space available on the media card," free up disk space by deleting videos, pictures, applications, and/or other files you no longer need.
Book is missing or does not appear in Archived Items list.
Possible causes:
Lost wireless connection.
Kindle for Android registered to wrong account.
Confirm wireless connection and relaunch application
Close the Kindle for Windows Phone application.
Check wireless data service or Wi-Fi is enabled on the device and that status indicators show an active connection. A wireless connection must be active.
Launch Kindle for Windows Phone and log in to the Amazon account you used to purchase the book you wish to download if prompted.
Scroll to the menu section in the panorama view and select "Sync" and wait for the sync to complete.
Scroll back to the home section in the panorama view and select “Archived Items.”
If the title still does not appear, follow the steps below to re-register.
Re-register the application
Launch Kindle for Windows Phone on your device.
Scroll to the menu section of the panorama view.
Tap settings.
(If already signed in)
Tap the “deregister this device” button.
Tap “deregister” button.
Enter the same e-mail address and password for your Amazon.com account and select "Register."
Click to expand...
Click to collapse
Edit: Lol just noticed it says Android when talking about books not being in archived items even though its the WP rouble page.
http://www.amazon.com/gp/help/customer/display.html?ie=UTF8&nodeId=200590160
I appreciate the response, thanks. Will try a few things and report back here
konnexion said:
I appreciate the response, thanks. Will try a few things and report back here
Click to expand...
Click to collapse
No problem, Maybe try the Feedback and Support feature which is within the app to send an e-mail.
Case opened with Amazon Kindle Support
Please keep us apprised of the situation.
konnexion said:
I'm only attempting this over the WiFi network, it eventually gives up and says failed to download, try again.
Click to expand...
Click to collapse
Hate to cross post, but I'm having a similar issue on my android device (nook color), as well as two windows pc's. I don't think this issue is isolated to one platform.
Thanks for info. Amazon are still investigating this issue
solved the same problem
I had the same problem. I accessed my app manager and changed the kindle app location from phone to sd card. After that all my queued books downloaded. I think the problem was not enough memory on my phone, or reserved memory on the phone and kindle auto DLs to location the app is installs. (could be wrong, but solved the problem anyway) hope this helps
Hi All,
I know this is a fairly new device, but I was super keen to get it specifically to put cyanogenmod 11 on. After having some trouble with the current version of TWRP posted in another thread here on XDA (which only worked when the phone was in an "out of the box" state, requiring me to do a factory reset due to a mini android update that was automatically applied between reboots - resolved), I got the stable channel release of CM11 which is listed as not having any issues, flashed it, and am having some issues.
The main problem I am experiencing is that regardless of which player I am using, if I open "Settings" from the status bar, whatever media I am playing goes silent. The player appears to still be playing, changing tracks, removing and reinserting headphones, clearing the playlist, re-opening the player...nothing fixes it. And then randomly some time later it will start making sound again if I leave the player running. Is there anyone else that can provide insight into this one? I have heard the problem is addressed for some in CM12, but that is not yet stable for our device.
Cheers.
I can confirm that you also lose system sounds, and that it applies even if you have no headphones plugged in and instead use the phone speaker. Total silence after accessing the settings from the statusbar. I have of course posted this on the Cyanogenmod system, but they have closed it pending a report dump which I cant produce till i am back at my android modding PC.
You have to remove the equaliser from quick settings. You can also use cm 12
snorglamp said:
Hi All,
I know this is a fairly new device, but I was super keen to get it specifically to put cyanogenmod 11 on. After having some trouble with the current version of TWRP posted in another thread here on XDA (which only worked when the phone was in an "out of the box" state, requiring me to do a factory reset due to a mini android update that was automatically applied between reboots - resolved), I got the stable channel release of CM11 which is listed as not having any issues, flashed it, and am having some issues.
The main problem I am experiencing is that regardless of which player I am using, if I open "Settings" from the status bar, whatever media I am playing goes silent. The player appears to still be playing, changing tracks, removing and reinserting headphones, clearing the playlist, re-opening the player...nothing fixes it. And then randomly some time later it will start making sound again if I leave the player running. Is there anyone else that can provide insight into this one? I have heard the problem is addressed for some in CM12, but that is not yet stable for our device.
Cheers.
Click to expand...
Click to collapse
As much as I understand you requiring help, you should post questions in the Q&A section and not in the development section.
csoulr666 said:
As much as I understand you requiring help, you should post questions in the Q&A section and not in the development section.
Click to expand...
Click to collapse
Is this not a cyanogenmod 11 development issue? Happy for someone to shift it to Q&A if its not a development issue (I dont think I have that ability). Or are development threads only for posting finished products?
CONFIRMED: Problem is caused by equaliser quick settings tile
OK, so I can confirm that the problem is indeed the equaliser quicksettings tile/animation. So as described above there is a work around, and for anyone that needs to know the actual steps to disable the equaliser quicksettings tile please see below (it took me a while to work out as you cant just remove it with a drag/long press the way you can other tiles):
Go to settings>Notification Drawer>Quick Settings Panel>Dynamic Tiles
This is a list of the quicksettings tiles that pop up when triggered by a system event, disable the "Equalizer" (Sic) by unticking the checkbox and the bug goes away.
The equaliser continues to work, you just dont get the quicktile popping up and causing the bug.
Cyanogen Mod developers appear to have picked up the bug so maybe a fix coming to stable release soon?
Resolution of audio issue
snorglamp said:
OK, so I can confirm that the problem is indeed the equaliser quicksettings tile/animation. So as described above there is a work around, and for anyone that needs to know the actual steps to disable the equaliser quicksettings tile please see below (it took me a while to work out as you cant just remove it with a drag/long press the way you can other tiles):
Go to settings>Notification Drawer>Quick Settings Panel>Dynamic Tiles
This is a list of the quicksettings tiles that pop up when triggered by a system event, disable the "Equalizer" (Sic) by unticking the checkbox and the bug goes away.
The equaliser continues to work, you just dont get the quicktile popping up and causing the bug.
Cyanogen Mod developers appear to have picked up the bug so maybe a fix coming to stable release soon?
Click to expand...
Click to collapse
The latest nightly release of CM11 now includes a fix for this bug. Official release channel still contains the bug, although it does not list it as a known issue for some reason. The next release M channel version should include the fix.
Calendar Not Working CM11
Next problem: trying to add anything to the calendar results in a user prompt that an account must be added first. I only have the cyanogenmod account linked to the phone, and that works fine for contacts. But in the calendar, if you select the cyanogenmod account, it tells you you can only have one account per phone. If instead you add an email address and set up say, work email, when you go back to the calendar it gives you the same prompt again. Does anyone know exactly what kind of account it requires to add, as nothing seems to work. Someone suggested to me to install the Google Calendar Sync component fro G-apps, however this would presumably share my calendar with google, which is precisely what I am trying to avoid by having cyanogenmod. Any help would be sincerely appreciated.
SOLVED CALENDAR PROBLEM CM11 and CM12
snorglamp said:
Next problem: trying to add anything to the calendar results in a user prompt that an account must be added first. I only have the cyanogenmod account linked to the phone, and that works fine for contacts. But in the calendar, if you select the cyanogenmod account, it tells you you can only have one account per phone. If instead you add an email address and set up say, work email, when you go back to the calendar it gives you the same prompt again. Does anyone know exactly what kind of account it requires to add, as nothing seems to work. Someone suggested to me to install the Google Calendar Sync component fro G-apps, however this would presumably share my calendar with google, which is precisely what I am trying to avoid by having cyanogenmod. Any help would be sincerely appreciated.
Click to expand...
Click to collapse
SOLVED: Thanks to Andy see below, i can also confirm it works with USB PC Sync software! Hoorah!
View PostAndyH, on 05 March 2015 - 05:08 AM, said:
Download and Install the Offline Calendar App:
https://f-droid.org/...e.localcalendar
After that create an offline calendar in the Offline Calendar App
Then you can use the standard calendar app with the created offline calendar database.
No more need to sync anything with google...
snorglamp said:
Hi All,
I know this is a fairly new device, but I was super keen to get it specifically to put cyanogenmod 11 on. After having some trouble with the current version of TWRP posted in another thread here on XDA (which only worked when the phone was in an "out of the box" state, requiring me to do a factory reset due to a mini android update that was automatically applied between reboots - resolved), I got the stable channel release of CM11 which is listed as not having any issues, flashed it, and am having some issues.
The main problem I am experiencing is that regardless of which player I am using, if I open "Settings" from the status bar, whatever media I am playing goes silent. The player appears to still be playing, changing tracks, removing and reinserting headphones, clearing the playlist, re-opening the player...nothing fixes it. And then randomly some time later it will start making sound again if I leave the player running. Is there anyone else that can provide insight into this one? I have heard the problem is addressed for some in CM12, but that is not yet stable for our device.
Cheers.
Click to expand...
Click to collapse
The CM12 nightly release for our device appears to be stable and does not include this bug.
Fix Found, Request inclusion
snorglamp said:
Next problem: trying to add anything to the calendar results in a user prompt that an account must be added first. I only have the cyanogenmod account linked to the phone, and that works fine for contacts. But in the calendar, if you select the cyanogenmod account, it tells you you can only have one account per phone. If instead you add an email address and set up say, work email, when you go back to the calendar it gives you the same prompt again. Does anyone know exactly what kind of account it requires to add, as nothing seems to work. Someone suggested to me to install the Google Calendar Sync component fro G-apps, however this would presumably share my calendar with google, which is precisely what I am trying to avoid by having cyanogenmod. Any help would be sincerely appreciated.
Click to expand...
Click to collapse
Please vote for the F-droid (secure local calendar database) type solution to be integrated into Cyanogenmod at https://jira.cyanogenmod.org/browse/CYAN-481
I am only just getting used to CM on my Fire. I have set up a restricted profile for my child. The problem that I have is the home screen is black (the lock and open apps screens aren't). If I switch to the open apps screen it says "Your recent screens appear here". If I go back to the home screen then I get "Unfortunately, System UI has stopped", so I have no way to launch apps in the restricted app.
I have enabled apps in the restricted profile settings.
I've tried a "normal" additional user and a guest and both of these appear to work.
Just wondering if I've done something wrong, or if restricted users don't work ?
I forgot that I posted this as I never got any answer at the time, I probably posted to the wrong place
Anyway, to close this out, I discovered that the "HPROF" app needs to be enabled (in the owner's "App&Content Access" settings screen for the restricted user) for the restricted profile to work properly. With this app enabled for the restricted user everything works fine.
Sorry to dig this out again.
How have you been able to setup a restricted profile at all? I'm on 12.1 with my Kindle Fire (Thor) and I'm only able to setup new profiles without having the chance to chose between regular and restricted. Any hint?
Hi, yes. I have set up one for my daughter and used a restricted profile. Here's what I did...
As your main (owner) user, bring up settings and then users. You need to go that way - don't swipe down and tap the user icon on the right hand side because that lacks the restricted user option.
Anyway, from the settings->Users screen, select "add user or profile" and choose "Restricted Profile". After you've added the profile it will appear on the same settings->users screen. It will have a little cog next to it - tap that and then enable the apps you want to allow the profile to access. By trial and error I discovered that you must enable HPROF. I think that everything else is optional. Good luck
Thanks for the quick response. Unfortunately CM 12 and 13 builds for the Kindle seem to be "smartphone" rather than "tablet" builds. As Google has removed the feature of restricted profiles for smartphones, on the Kindle the option of setting up restricted profiles is missing :crying:
Ah! I just noticed that your device is different to mine - this is the forum for the Amazon Fire 7" - 5th Gen 2015. I have CM 12.1 and it works on my device (Kindle Fire 7" 2015, codename KFFOWI). Sorry it didn't work out for you
True, Fire HDX is different to Fire. Nevertheless I would have expected, that at least classification of the devices (smartphone vs. tables) is equal. Thanks anyway!
thomas.magnum said:
True, Fire HDX is different to Fire. Nevertheless I would have expected, that at least classification of the devices (smartphone vs. tables) is equal. Thanks anyway!
Click to expand...
Click to collapse
As you are discovering custom ROMs for HDX sometimes identify the device as a phone vs tablet. Some HDX models do come with a LTE radio which may be a contributing factor. Fuller response provided in the HDX forum.
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: 20/04/2023
Version 7.X Released
- It has braking changes for WiFi, this is mainly due to recent Android SDK limits, like toggling WiFi, BT, getting Mac address and others. Therefore WiFi connection now does need a helper app on the phone.
- Dropped GLES20 as too many issues reported by different bad implementations
- Resolution is now automatically detected based on the cars screen.
- SelfMode (running on phone screen) works without the need of activating developer options in Android Auto.
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
Self Mode (when Android Auto and HUR are running on the same device)
Open HUR and press the self mode button. (you need to make sure Android Auto, Google Play Service, Google maps, Google Text To Speech is also installed on the device and it's up to date)
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
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.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]
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:
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
D key - Changes to Day theme
N Key - Changes to Night theme
M Key - Mic
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:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
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:
Start HU app
Select Self mode
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:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
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.
Well done! Thanks so much for your hard work Emil.
*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.
Syphe said:
*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.
Click to expand...
Click to collapse
What version of Android is your unit running? I haven't heard of any with less than lollipop being able to run this so far, h.264 decoding is absent or poorly implemented.
Edit....see the bottom of this post
http://forum.xda-developers.com/showpost.php?p=68010519&postcount=1449
Wifi Mode - Starting with HUR 7.X
Braking changes with version 7.X
Only for phones running Android 9 or higher, if you still use Android 8 phone, you won't be able to connect over WiFi. Device running HUR, can have any version of Android.
Phone Setup:
Install Wifi Launcher for HUR on the phone ( https://play.google.com/store/apps/details?id=com.borconi.emil.wifilauncherforhur&hl=en_US )
Make sure you give the app all the permissions, including draw over other apps, otherwise it cannot start Android Auto from the background!
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!)
If you want your phone to create the hotspot, turn on the option to Enable hotspot (this will probably not work if you are on Version in the USA due to carrier limitations!), likewise if you want your car to create the hotspot or you want to use an incar wifi module, leave this option turned off.
Only turn on the legacy option if HUR specifically instruct you so.
Car/Headunit setup:
Connect to the phones hotspot or if you are using an incar WiFi connect to that network. Alternatively if you want HUR to create the hotspot and connect your phone to it, enable the option in HUR settings.
Open HUR
As soon as the 2 devices are on the same network, HUR will fire up on your car screen.
Emil Borconi said:
Hi Syphe.
The core of the app is the same as the original, and the app does require a hardware H264 decoding supported by the OS. Till now we are not aware of any chinese HU which support this. Please contact me by email and I'll refund your purchase.
Click to expand...
Click to collapse
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"
Christopher Price said:
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"
Click to expand...
Click to collapse
Yeah I thought about that myself.... will probably create a small check app in the near future (just need to catch up with all my other work now, which has been pushed behind to get this done)
bugger, thought it was quite promising when everything started to connect itself
I've been building my own app to do simple notification mirroring over a wifi tether, but this would have been much easier haha.
Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!
kevster0522 said:
Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!
Click to expand...
Click to collapse
Hi.
Yeah the XDA labs app can sometimes play funny, if your having any kind of issues feel free to contact me directly be email, on [email protected]
Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later
fmark said:
Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later
Click to expand...
Click to collapse
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..
Emil Borconi said:
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..
Click to expand...
Click to collapse
Yes, my phone has 4G connection while tethering.
Lets try the debug output. Could you please send me the .apk with debug messaging? I'm curious to see what is going on when it fails to connect.
Thank you!
Im interested too because isnt working on my s4 and nexus7 2012
wpostma said:
Im interested too because isnt working on my s4 and nexus7 2012
Click to expand...
Click to collapse
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?
Christopher Price said:
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?
Click to expand...
Click to collapse
It might be about the Wifi connection, I had some connectivity issues over Wifi myself the last day, but they were fully random, at a first look they point to the TCP socket.... I'm investigating this.
I got some Wifi disconnected myself but it is very random, it can occur after 1-2 minutes or after 3-4 hours... so testing potential FIX for the issue isn't going to be easily. At the first investigation it looks to be something related with the pooling/keeping connection alive. I have tweaked this and made a new build, currently running for about 20 mins and looks OK, but as said the disconnect can occur randomly at any point.
The worst part is that the logs do not give any hint on what could be the cause of this, neither on the HU part, neither on the AA side, they only mention a broken PIPE bu no hint on what can be the cause...
I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?
Christopher Price said:
I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?
Click to expand...
Click to collapse
setting socket to keppalive looks to sort the problem, I'm trying to figure out failing handshake at the moment. On TCP sometimes the handshake fails, trying a few more times passes..., handshake over usb always passes....
Looking at the code and notes Mike seems to struggle with it as well in the past...
When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?
skitty said:
When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?
Click to expand...
Click to collapse
Emil Helped me with this problem. You don't actually connect through your wifi networks menu, use Wi-Fi Direct instead. Found here: wifi networks menu > 3-dot menu > Advanced > Wi-Fi Direct