Database Develop

[Guide] Installing Arch Linux (updated 11/4/2013) bluetooth+KDE

I've began to write up a guide for getting Arch usable on the Nexus 7. I just threw it up on google docs because I'm too lazy to try to do the wiki thing until it's more complete. Hopefully it is far enough along to get things rolling for people who are looking to experiment with arch.
Anyway, it's a work in progress, if anyone has suggestions, correction, completions, criticisms, etc then holler.
Linkies

Changelog
========
2013-07-20
--Added instructions for installing the platform tools on an arch host pc
--Added references to wicd and network manager as alternatives to netctl
2013-10-20
--Updated instructions to reflect new *-grouper.zip naming scheme for MultiROM files
--Added instructions for updating the kernel to include kexec
--Got bluetooth 90% working. Interface comes up and can find devices with scan. Can’t get it to pair yet though.
2013-10-24
--Got the bluetooth device to power up on boot by adding a udev rule. Unfortunately the bluetooth daemon seems to be failing as it starts.
2013-10-28
--My keyboard is pairing on boot now. Ugly ugly things to get it working, but it works.
2013-11-03
--Updated the guide to get X working.
2013-11-04
--Tweaked xorg.conf files to get kde and e17 working.
--Added instructions to get Touchégg working to provide more tablety experience

Todo/Bugs
Problems/Bugs/Todo
The following is a list of things that need to be addressed or that I want to address. These things will be tackled in no particular order but hopefully over time the number bugs and problems will go down relative to the number of features I want to add.
Feel free to comment with your own ideas or bug reports.
Fix slow shutdowns after enabling networking with netctl
Fix whatever extremely verbose crash shows up on shutdown after setting up bluetooth
Get bluetooth working without hacks and under bluez5
Get a graphical login working
On screen keyboard (especially at login screen)
Set up an aur and/or googlecode project to automate some of the scripting required to get things working
Automate the process with some kind of setup tool
Replace the google doc with a wiki page in a relevant place
Make a custom spin that works more out of the box
Sound
GPS
Accelerometer
Magnetometer
Hardware buttons
Any other sensors that I forgot or am unaware of
Auto screen rotation

For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).

joeG78 said:
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
Click to expand...
Click to collapse
Thanks for the feedback
I don't have arch on my pc at the moment, so it's not a given, but i think you are right that people are probably more likely to have arch if they are looking at this guide. I updated the guide with info on how to install the tools from AUR. Also added links to wicd and Network Manager in the arch wiki so people are aware of some options if they don't like netctl, and mentioned that e17 works.

Xorg with alarm on nexus 7
Okay, got ALarm installed on my nexus 7 8GB.
For Xorg, I used files from "plasma active" nexus 7 distribution.
Just take them from the plasma active and put them into your /etc/X11 and X should work.
(I can't post a link, must wait 10 posts, I'll link the files later or you can PM me)
My only problem now is to put a cross-compile toolchain on my computer to be able to compile e17 with illume modules. Tried to compile on my tablet but it's too slow and I've not enough disk free to finish. If anybody can help on this point…

What distribution are you using on your PC? Also you can pm me the link for the xorg configuration and I'll post it for you

OK so I have come as far as installing multirom and I installed the archlinux rom and got this error when I tried to boot it
"kexec-hardboot support required to boot this kernel"
How do I resolve this?

thecrimsonfukr said:
OK so I have come as far as installing multirom and I installed the archlinux rom and got this error when I tried to boot it
"kexec-hardboot support required to boot this kernel"
How do I resolve this?
Click to expand...
Click to collapse
Go back and reread the multirom thread, then install a kexec-hardboot patched kernel in your internal rom.
Sent from my SGH-T679 using xda premium

joeG78 said:
Go back and reread the multirom thread, then install a kexec-hardboot patched kernel in your internal rom.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Thank you! I didnt realize it was that simple... for some reason i find the original multirom post difficult to follow.

thecrimsonfukr said:
Thank you! I didnt realize it was that simple... for some reason i find the original multirom post difficult to follow.
Click to expand...
Click to collapse
Hello
i want install arch linux on nexus 7 , but i confuse about it . is arch linux on nexus 7 fast and stable ?
can i watch hd video in arch linux withot lag ? before days i install ubuntu desktop on N7 but when i open video HD ( not full) with vlc , it somtimes play withot sound and it have lag . unity is heavy for nexus 7 , i want install arch + lxde . is it fater ?
sorry for english .

For me Arch works without any problems but when I type startx xserver freezes after the first image of xfce or e17.
Has anybody a solution?

? How to install e17 ?
joeG78 said:
For the section on setting up fastboot and adb...it's safe to assume someone installing arch on the nex7 probably has arch on their pc too. For arch, you need to set up access to the AUR, with a package manager that has access to it, i.e. yaourt. Then you can get android-sdk-platform-tools. The rest of the guide looks good. I personally like wicd for my network manager as it is easier to add and remove networks when you go to new locations, and I installed e17(enlightenment desktop).
Click to expand...
Click to collapse
e17 is the fast
so , i want to installing to my nexus 7
thanks .

Why ? my bluetooth not work?
not find the device ????

ylixir said:
I've began to write up a guide for getting Arch usable on the Nexus 7. I just threw it up on google docs because I'm too lazy to try to do the wiki thing until it's more complete. Hopefully it is far enough along to get things rolling for people who are looking to experiment with arch.
Anyway, it's a work in progress, if anyone has suggestions, correction, completions, criticisms, etc then holler.
My bluetooth not working
cannot find the device ??
Nexus 7 32GB Wifi
Click to expand...
Click to collapse

bluetooth
I have bluetooth (almost) working. I've put instructions in the guide. They aren't really a final solution, but maybe people who are running gui's can tell me if they work. I know I have the hardware working because I can see my keyboard when I scan for it, but I can't figure out how to get bluez5 to pair from the command line. Hopefully someone has better luck with a gui?

bluetooth
I've got Bluetooth working. I even have it pairing automatically on boot with a keyboard. Its an ugly solution but it works. The guide has been updated. I'll tackle X next

My Arch Install
Hey just wanted to add my install experience to the thread hopefully to help others. First of all I want say thanks for all documentation from the previous posters. I tried to follow the instructions as close as possible for a kde install, but I ran into some trouble with lightdm, so I tried kdm instead. And I can happily report it has worked swimmingly. Instructions on how to setup kdm, navigate to /usr/share/config/kdm. First edit the kdmrc to turn off the themed greeter. Then add the xvkbd to the XSetup file as in the lightdm setup. Another thing I did was utilize the plasmaboard widget on my main kde panel for my on screen keyboard once I log in. It seems to work much better than xvkbd for me. I can also confirm flash is working great.
So this really close to totally replacing my linux laptop, especially when I am on the go, in fact I am writing this post on the device in arch. However one key piece is still missing for me is sound. I can't seem to coax any sound out the device with my arch install, and amarok crashes on startup, even though both these items were working perfectly in ubuntu. If any one has any ideas how to make audio and amarok work I would be immensely grateful. Also thanks again, I am so happy to be rid of the X11 touch race condition. I have added a screenshot of me editing this post for those interested as well.

Figured out sound!
I think i found a solution to all of my troubles from my previous post. Amarok started working after a pacman update. My general audio problems seem to be caused by the linux for tegra audio drivers lack of head phone jack detection, I found a workaround the ubuntu nexus 7 launchpad bug tracker: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068804/comments/24. For the tldr crowd basically you have to use alsamixer manually mute and unmute the int_spkr channel for speaker audio and the int_mic channel to enable headphones. Then you can use the output and and hp to channels adjust volume for speaker and headphones respectively. It also might help to do a suspend resume cycle i sound still isn't working. Thanks to everyone else, hopefully others will find this useful as well.

Many thanks for your work!!! I'm using it on a nexus 7 with glass and touch broken (unuseless) but now it lives!!! and is a very responsive lxde desktop with xrdp starting on boot which I use with amule or bittorrent all night long...
two questions:
1) for me it does not work shutdown -r now or reboot... it close immediately all network connections but I have to keep power button 10 sec to restart system...
2) using it with an hub usb I'm trying to connect a big hard disk: pcmanfm (lxde file manager) refuse to mount it saying than it is not authorized... (I've followed archlinux wiki: it work on my archlinux desktop but not in nexus 7).

[Q] xposed, VPN, ICS & Auto VPN Dialog Confirm

I read the module FAQ and the code page and tried out module & xposed code and I was not able to get around my problem. I'm not sure that it was supposed to get around my problem though, but I was hoping to get your take on things. I can't find much data, though I can find a few people asking the same questions as I.
I installed an android 4.3 ROM (http://forum.xda-developers.com/showthread.php?t=2121063) on my phone and tried to connect to an OpenVPN based VPN provider. I got an error and contacted their support. Part of that process was to try another app, so we tried the OpenVPN COnnect app, the official OpenVPN app. I got a different error with that app.
One says that "your android firmware does not support the VPNService API("
OpenVPN Connect says "Sorry, due to a known issue in this version of android, it is not possible to gain permission to open a VPN tunnel"
There seems to be a few problems popping up with OpenVPN based VPNs in various Android 4.x OSs, but none complaine about 4.3 specifically. Usually they complain about 4.4 or back when 4.0 and 4.1 were new. I found this article talking about it on OpenVPN, and they're just pointing the finger, but I can't find the actual bug referenced:
https://forums.openvpn.net/topic13772.html
I came across your code on this page:
https://code.google.com/p/ics-openvpn/wiki/FAQ
And decided to try loading xposed and your module after emailing OpenVPN Connect and receiving a response right away. The guy who replied seemed to think the error is related to the fact that the confirmation acknowledgement dialog is not able to be summoned. I figured maybe the ROM wasn't bypassing it properly or missing some part of it, so I tried your way of bypassing it.
After loading xposed and your module, and selecting the 2 VPN apps, I still get the same results.
What are your thoughts? Should I give up and find a new ROM?

What are you talking about? If you're asking about a specific module (looks to me that way,) you should do that in the appropriate thread.

After some more research and experimentation yesterday, it's looking more like those OpenVPN clients that "support" the VPNServiceAPI actually *require* it, and that annoying/nasty little dialog that google enabled to "protect" the user just serves to piss off advanced users like me. This is my hypothesis at this point, though I have not confirmed this. I suspect this because I just tested on Jelly Bomb, a 4.1 based ROM and see the same results so far.
As far as what I was talking about in my OP, I copy/pasted an email to the author of the xposed module here and tried to reformat it to fit the message board, and apparently I missed a few pronouns. By far not the most egregious use of the English language I've seen on these boards, so what's with the attitude? I don't see specific sub forums for each and every module, so I don't get what you're implying. I only saw the one xposed board, so where else was I supposed to post?

No attitude, I honestly didn't understand how your issue was related to the Xposed framework. I just searched the repo for "VPN" and now see what you're talking about.
The Auto VPN Dialog Confirm doesn't have a thread here on XDA. Reading your post again, you're trying to use Xposed to fix a bug with the app if I'm not mistaken? I'd first try checking the logcat and forwarding that to the author of the VPN app if you haven't already.
I can't answer the rest of your questions since that's up to the module's author. That being said, it looks like a module specific question/request, not a framework query.

My understanding of the issue described here is different, probably because I'm trying to solve the same problem On the other hand, I'm not on ICS anymore, but am using Sammy 4.1.2 stock with DorimanX Kernel 8.43 at the moment.
OpenVPN should be usable for establishing a connection on boot. Out of the box, this creates a dialog to trust this application. Even though I trust it and confirm, there is no way of saving that preference permanently. It seems to be kept for a while (disconnect / reconnect doesn't trigger it again at least ) Therefore, it always reappears each time I boot.
The only possible solution I could find was the Xposed Module "Auto VPN Dialog Confirm" - the same module mentioned by the OP.
I used it together with the OpenVPN Client by colucci.web.it (paid version in my case, because I also wanted TAP support and auto connect functionality as well as the option of controlling it via Tasker).
After installing "Auto VPN Dialog Confirm" it recognized the installed OpenVPN client and offered to allow VPN API connections from it without confirmation. The VPN client also has an option to automatically create connections when Wifi is up and allows to be triggered either when seeing a specific SSID or when connecting to a network which does not have a specific SSID. The latter one is the typical condition for untrusted networks.
Therefore, it achieves what I wanted - being able to route my traffic via OpenVPN in case I'm not connected to my home WiFi
Regarding the issue encountered on ICS - maybe getting in touch with the Developer of the Xposed module might be the best option, unless someone else has already found a solution for it. It could also be good to exactly specify the OpenVPN client used as clearing the Xposed logfile and having "AutoVPN Dialog confirm" run as the only Xposed app (and fail). Afterwards, the log hopefully contains useful feedback for the developer to investigate further (Support URL listed for the module)

[Android 4.0+, ROOT] AppRadio Unchained Reloaded

In addition to the well known AppRadio Unchained mod of the Pioneer AppRadio app, a completely Pioneer-less app was developed.
It's called AppRadio Unchained Reloaded and its available from the Play store here: AppRadio Unchained Reloaded
If you don't want to root your phone and have Android 7 or higher there's AppRadio Unchained Rootless
Video of AppRadio Unchained Reloaded in use by Alexei Andreyev: Pioneer AVH-X8600BT & LG G3 with ARUnchained
Another video by Alecion420: STI GR 2012 with ARUnchained+Note 3+pioneer 8000nex+Rockford Fosgate+Boyo backup Cam+SMY keyless
Video by Rubn: Appradio 3 - ARUR
AppRadio Unchained Reloaded allows full mirroring of your phone from your AppRadio. This means that any app can be controlled from the head unit screen and not just a few that are specially adapted.
For this app to work ROOT is required. Do not ignore this requirement and blame the app for not working!
V0.17 and up work with SELinux in enforcing mode.
Important
The 'Smartphone setup' on the head unit needs to be set correctly for Android as by default it's configured for Iphone. Go to Settings->System->Input/Output Settings->SmartphoneSetup and set Device to 'Others' and Connection to 'HDMI'. See this video: Smarthphone setup
Any other AppRadio related app needs to be uninstalled as this blocks the connection to AppRadio Unchained Reloaded.
AppRadio mode requires that your device is connected to the HDMI input of the head unit. Depending on the device this can be done with a MHL / Slimport / Miracast / Chromecast adapter.
Because this app may not work for your setup there's an extended trial period of 48 hours. In order to claim this simply request a refund within 48 hours after purchase by emailing the order number to the support email address.
Two versions
When your device has Android 4.3 or higher you will get version 0.31 which has support for automatic connection to wireless casting devices.
The user's manual is available here: Version 0.31 user's manual
Please read it as it contains all details about setting up a wireless screencasting connection.
When your device has Android version lower than 4.3 you will get version 0.29 without support for wireless casting devices
The user's manual is here: AppRadio Unchained Reloaded User's manual
Supported head units: any AppRadio that supports Android AppMode via HDMI.
For example: SPH-DA100, SPH-DA110, SPH-DA210, SPH-DA120, AVH-X8500BHS, AVH-4000NEX, AVH-4100NEX, AVH-4200NEX, AVIC-X850BT, AVIC-X950BH, AVIC-Z150BH, AVIC-6000NEX, AVIC-6100NEX, AVIC-6200NEX, AVIC-7000NEX, AVIC-7100NEX, AVIC-7200NEX, AVIC-8000NEX, AVIC-8100NEX, AVIC-8200NEX
Units that have AppRadio mode via USB (a.k.a. AppRadio One) are not supported.
Beta test version
The beta test version has the latest features but can also contain bugs.
You need to become a tester of the AppRadio Unchained Reloaded app to be able to get it.
Please apply here: https://play.google.com/apps/testing/mars.area51.arunchained
The following features are supported:
- Multitouch
- AppRadio buttons
- Steering wheel controls
- GPS data transfer via mock locations (only works with head units that have a GPS receiver AND do not have built-in navigation)
- Auto enables mock locations on connection (if app is converted to a system app)
- Wake lock
- Rotation locker (to put any app in landscape mode)
- Real calibration
- Start at boot (for use with Android sticks)
- Start on HDMI detection (for use with phones and HDMI adapters)
- Notifications to indicate connection state
- Widget for returning to head unit home screen
- Diagnostics
- Automatic Bluetooth toggle for improved connection
- Assign system app rights without the need to move files
For Reloaded to be able to switch Mock locations automatically, it needs to have system app rights. These can be assigned as following:
In the menu select the entry 'System app enable'. Once the rights are assigned the entry will change to 'System app disable'. When executed the system app rights will be revoked. When 'System app enable' is activated, the diagnostics will show 'Can switch mock locations' ticked. However it will not show 'Installed as system app' as technically it's not installed as a system app but nonetheless it has system app rights and the Mock locations can be switched.
When the app is still installed as a system app (by moving the files) the menu entry is disabled as it makes no sense. In order to enable the functionality remove the files that were moved to make it a system app first and then install the latest version.
AppRadio is a registered trademark of Pioneer.
Disclaimer: You are solely responsible for using this app in such a way that it does not impair your ability to drive.

Beta
Beta test release notes
0.39
- Alternate menu. Long press the background of the app to show this menu.
0.38
- Support key layout for TV boxes
- Improve screencast autoconnect support
0.37
- Fix crash at connection time when getPort not found
- Fix for LG V20 screen offset

Moved across from the other thread as it will no doubt be an FAQ.
Method for getting ARUR working on Lollipop (in this case the Nexus 5)
Update your phone to Lollipop using Wugfresh Toolkit. This allows you to flash the factory image LRX210 (which it will download for you)
Use the same toolkit to root the phone including your choice of recovery (TWRP etc).
Set SELinux to permissive with SELinux Mode Changer.
Check the phone still reports it has the right sized storage (16Gb/32Gb). If it is reporting it is half the size it should be, boot into recovery and wipe the data partition and it will get restored.
Install ARUR from the Play Store
Move the Installed application into /system/priv-app using Root Browser and set the permissions to read write execute
Alternative way to flash and root:
Install with the factory image LRX21O (not with an OTA update zip).
Root with CF Auto-Root.
If you get it installed and still have problems, Try:
Delete your Bluetooth connection on both your Nexus and your HU, perhaps a full reset on the HU, then re-add the Bluetooth connection.
Ensure the HU configuration is set to "Other" and not iPhone
Check ARUR has SU permissions in SuperSU application (or whichever app you have installed)
Check that your solution works to a standard TV (won't allow touch but will check the HDMI output)

New version released by Area51 which should mean there is no need to set SELinux mode to permissive.
Good news for those with locked boot loaders as his should now work for them with just root.

Is the nexus 6 supported, yet? If so, which cable is required?
Sent from my Nexus 6 using Tapatalk

just bought ARUR because of the newest update, but touch control still isn't working on my S5.
for my diagnostics, the only things not checked are:
no app interfernce
installed as system app
can switch mock locations.
do these need to be checked for touch controls to work? Thanks.

blackcompany said:
just bought ARUR because of the newest update, but touch control still isn't working on my S5.
for my diagnostics, the only things not checked are:
no app interfernce
installed as system app
can switch mock locations.
do these need to be checked for touch controls to work? Thanks.
Click to expand...
Click to collapse
No. The one for touch control to work would be "Event injection". I had it reported working by some people with an S5 but maybe they used a different root method. It looks like there might be still some work to do. Would it be possible for you to make a logcat dump and email it to the support email from the Play store? It can be done with an app called "Catlog". Please first start Catlog first, force close ARUR and then start it, then connect to your HU.
Edit: No app interference, do you still have ARU/Pioneer app installed? If so uninstall it first. If frozen with titanium backup it doesn't matter.

Area51© said:
No. The one for touch control to work would be "Event injection". I had it reported working by some people with an S5 but maybe they used a different root method. It looks like there might be still some work to do. Would it be possible for you to make a logcat dump and email it to the support email from the Play store? It can be done with an app called "Catlog". Please first start Catlog first, force close ARUR and then start it, then connect to your HU.
Edit: No app interference, do you still have ARU/Pioneer app installed? If so uninstall it first. If frozen with titanium backup it doesn't matter.
Click to expand...
Click to collapse
I didn't reailze it before, but because ARU was still installed, ARUR kept saying Listening for Connection. Once I uninstalled ARU it finally connected. But I still don't have touch controls. I uninstalled it and now my app interference box is checked. the other two boxes are still unchecked.
I started catlog, forced closed ARUR, and then connected to the HU. Now how do i get to the log info so I can send it to you? I've never used catlog.

blackcompany said:
I didn't reailze it before, but because ARU was still installed, ARUR kept saying Listening for Connection. Once I uninstalled ARU it finally connected. But I still don't have touch controls. I uninstalled it and now my app interference box is checked. the other two boxes are still unchecked.
I started catlog, forced closed ARUR, and then connected to the HU. Now how do i get to the log info so I can send it to you? I've never used catlog.
Click to expand...
Click to collapse
How to make a logcat using an app called Catlog
Start Catlog logcat through app menu and select record.
Select home button so you leave Catlog app running.
Go through process to start ARUR and connect to AR.
Once you know the bug was created, open the Catlog app from notification bar (this stops recording).
Select the recording, which is named by date-timestamp...from action selection pick share by email...this zips the logcat and system info txt files into one zip.
Email to self and share the zip with dev by email or any other method you want.

Area51© said:
How to make a logcat using an app called Catlog
Start Catlog logcat through app menu and select record.
Select home button so you leave Catlog app running.
Go through process to start ARUR and connect to AR.
Once you know the bug was created, open the Catlog app from notification bar (this stops recording).
Select the recording, which is named by date-timestamp...from action selection pick share by email...this zips the logcat and system info txt files into one zip.
Email to self and share the zip with dev by email or any other method you want.
Click to expand...
Click to collapse
So I didn't see any options to share the recording in the catlog app. There's only a search function, pause button, a sort button, and a refresh button and then all the log info in a long scroll. I transferred the files from my phone to my computer and sent it to the email on the play store. If there's anything else I got to do let me know. Thank you.

supernewf said:
Is the nexus 6 supported, yet? If so, which cable is required?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Nexus 6 does not support HDMI out, so there will not be a cable. You may be able to get it to work with Chromecast though, it does not support Mirrorcast either.

blackcompany said:
just bought ARUR because of the newest update, but touch control still isn't working on my S5.
for my diagnostics, the only things not checked are:
no app interfernce
installed as system app
can switch mock locations.
do these need to be checked for touch controls to work? Thanks.
Click to expand...
Click to collapse
I heard via email from blackcompany that it's working now. The thing that fixed it was to update to the latest SuperSU version.

Is Note 3 supported yet?

ixo- said:
Is Note 3 supported yet?
Click to expand...
Click to collapse
Note 3 has always been supported.
If you mean can you use a device with a locked boot loader and SELinux in enforcing mode, then the latest version is looking good so far for supporting that configuration. You still need the device rooted and the latest SuperSU application installed.

i wish i had more thumbs, so i could give this app four thumbs up
Phone: OnePlus One
ROM: Paranoid Android 4.6 (using ART instead of Dalvik)
HeadUnit: SPH-DA210
Connection: WiFi hotspot and Chromecast (tried Amazon FireStick but it was cumbersome to initiate the screen casting, it worked though)
I have the service running all the time and use NFC tags and the Trigger app to turn on/off bluetooth, wifi, hotspot, etc. I'm not sure of the battery usage so far with the service running all the time (just bought the app about 12hrs ago). This stand alone app has really sped up the time it takes to get connected and on the road. I also am not using ARUR as a system app and have mock locations on at all times. My initial impressions have been so outstanding that I have uninstalled Tasker, Secure Settings, AppRadio Unchained & AppRadio Unchained GPS Injector.
couple of quirks...
1) when i check "Do not switch Mock locations", gps injection will not work. I have mock locations on already so its my understanding there is no need to "switch" and ARUR is not a system app.
2) during my testing i stopped the app when it was already connected to my appradio and restarted. it says connected but the touches do not register. on the old unchained app you could on/off bluetooth and reconnect with the headunit to get the touches back, this method did not work.
feature request...
i'm not sure if you are familiar with the screen standby app, but if you could have such a feature as an option would be awesome! one less app to have.
question for anyone...
if anybody knows a way to automatically start casting my screen upon successful connection to my appradio, i would greatly appreciate the advice.

400ixl said:
Method for getting ARUR working on Lollipop (in this case the Nexus 5)
...
Move the Installed application into /system/priv-app using Root Browser{/URL] and set the permissions to read write execute
Click to expand...
Click to collapse
Are you sure that's all that is required for converting to a system priv-app? Last time I did it, a library file needed to be transferred as well. Also, there are multiple permissions to set (owner, group, and other), so you may want to edit it the sentence to be more explicit. Finally, was the typo using a brace intentional? The Play Store link does not work as a result.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
ddash97 said:
Phone: OnePlus One
ROM: Paranoid Android 4.6 (using ART instead of Dalvik)
HeadUnit: SPH-DA210
Connection: WiFi hotspot and Chromecast (tried Amazon FireStick but it was cumbersome to initiate the screen casting, it worked though)
I have the service running all the time and use NFC tags and the Trigger app to turn on/off bluetooth, wifi, hotspot, etc. I'm not sure of the battery usage so far with the service running all the time (just bought the app about 12hrs ago). This stand alone app has really sped up the time it takes to get connected and on the road. I also am not using ARUR as a system app and have mock locations on at all times. My initial impressions have been so outstanding that I have uninstalled Tasker, Secure Settings, AppRadio Unchained & AppRadio Unchained GPS Injector.
couple of quirks...
1) when i check "Do not switch Mock locations", gps injection will not work. I have mock locations on already so its my understanding there is no need to "switch" and ARUR is not a system app.
2) during my testing i stopped the app when it was already connected to my appradio and restarted. it says connected but the touches do not register. on the old unchained app you could on/off bluetooth and reconnect with the headunit to get the touches back, this method did not work.
feature request...
i'm not sure if you are familiar with the screen standby app, but if you could have such a feature as an option would be awesome! one less app to have.
question for anyone...
if anybody knows a way to automatically start casting my screen upon successful connection to my appradio, i would greatly appreciate the advice.
Click to expand...
Click to collapse
Are you using a 2nd phone to control the mirroring, or did you get around it by ignoring the warning in the Chromecast application? What does it do to your audio quality?

stargate125645 said:
Are you using a 2nd phone to control the mirroring, or did you get around it by ignoring the warning in the Chromecast application? What does it do to your audio quality?
Click to expand...
Click to collapse
I see no Chromecast warnings. The only warnings I do see are from the Pioneer AppRadio itself. Also, I have to use an app called "#MirrorEnabler" in order to get the "Cast screen" option in the Chromecast app as the OnePlus is not an officially supported device.
As far as the audio is concerned, I would say the quality is equal to bluetooth 2.0. I listen to sport talk about 95% of the time i'm in my car so its not enough to out weigh all the other benefits. you can stop here or...
you can read this if you want a bit more information about my opinion with regards to audio quality...
i have factory speakers with an external amp & sub connected to the appradio. Also, my vehicle is performance oriented so my cabin noise is above average. With all that said, there is still a discernible difference in the below scenarios and I would rate the "cast screen" audio as on par with bluetooth 2.0
#audio and video compression over wifi with phone as the source
appradio + chromecast cast screen + oneplus = good
#audio and/or video compression over wifi with chromecast as the source
appradio + individual app casting (ie Netflix, Play Music) = better
#potentially no compression depending on the source
appradio + directly connected media (ie dvd, cd,usb,hdmi) = best
Now, replace the appradio with my home theater system in the above scenarios and I would rate all three higher.

ddash97 said:
I see no Chromecast warnings. The only warnings I do see are from the Pioneer AppRadio itself. Also, I have to use an app called "#MirrorEnabler" in order to get the "Cast screen" option in the Chromecast app as the OnePlus is not an officially supported device.
As far as the audio is concerned, I would say the quality is equal to bluetooth 2.0. I listen to sport talk about 95% of the time i'm in my car so its not enough to out weigh all the other benefits. you can stop here or...
you can read this if you want a bit more information about my opinion with regards to audio quality...
i have factory speakers with an external amp & sub connected to the appradio. Also, my vehicle is performance oriented so my cabin noise is above average. With all that said, there is still a discernible difference in the below scenarios and I would rate the "cast screen" audio as on par with bluetooth 2.0
#audio and video compression over wifi with phone as the source
appradio + chromecast cast screen + oneplus = good
#audio and/or video compression over wifi with chromecast as the source
appradio + individual app casting (ie Netflix, Play Music) = better
#potentially no compression depending on the source
appradio + directly connected media (ie dvd, cd,usb,hdmi) = best
Now, replace the appradio with my home theater system in the above scenarios and I would rate all three higher.
Click to expand...
Click to collapse
That pretty much seals the deal for me to stick with a wired setup. As far as the warning goes, it is the one that pops up on the phone when the editing the Chromecast application options for the Chromecast device that is connected to your phone's WiFi tether. Chromecast doesn't like to cast a screen from the same device to which it is tethered, in my experience. So, I was inquiring if you found a way around this without getting such a device warning, and without having to use a 2nd phone.

DDash,
I'm very interested in your use of the AppRadio and the OnePlus.
Would you be willing to write up a short 'how to', and if any other equipment/cables, etc are necessary?
Thank you for the prededing information.

stargate125645 said:
That pretty much seals the deal for me to stick with a wired setup. As far as the warning goes, it is the one that pops up on the phone when the editing the Chromecast application options for the Chromecast device that is connected to your phone's WiFi tether. Chromecast doesn't like to cast a screen from the same device to which it is tethered, in my experience. So, I was inquiring if you found a way around this without getting such a device warning, and without having to use a 2nd phone.
Click to expand...
Click to collapse
oh yeah, without a doubt stay wired. i was perfectly happy with my previous nexus 4 hard wired setup. My original nexus 4 never had an overheating issue, it just decided not to turn on one morning so every "repaired" nexus since (4 of them now) ,overheats to the point of powering off,when connected to my appradio over hdmi. So now i have a oneplus and only kept it because it was good enough over chromecast or firetv stick.
---------- Post added at 09:31 PM ---------- Previous post was at 09:24 PM ----------
JeffDC said:
DDash,
I'm very interested in your use of the AppRadio and the OnePlus.
Would you be willing to write up a short 'how to', and if any other equipment/cables, etc are necessary?
Thank you for the prededing information.
Click to expand...
Click to collapse
Sure, i can write something up. I'll do it in the OnePlus forum and send you a link.

Zuk Z1 - Sound profile app and ability to set bedside mode (like a BlackBerry)

Hello,
I'm quite new to this forum and I've recently bought a ZUK Z1.
I had BlackBerry devices (BB10 ones) for long time and going back to Android is a sort of excitement and little disappointment as well from one side.
I've installed Cyanogenmod 13 on my ZUK Z1, but I can't find any way to proper set Sound Profiles like I was used to do with my BlackBerry.
- Normal (calls/notification... etc)
- Phone Calls only (no notifications except calls)
- Silent (no sounds in general)
Plus, I badly miss the 'Bedside mode', where the phone disables mobile network and wifi, all notifications (led/sounds etc) and shows a big black screen with only the clock.
I had a check in the forum and around the web and I found that Sound Profiles seems probably what could solve the first need.
About the second one, there are few apps that are able to display the clock... but that's it - no ability to change the sound profile settings.
So, I was trying to set a profile called "Night" in Sound Profiles to at least be able to get the same setup, using the "enable airplane mode" feature, and have this profile set to launch one of these big clocks apps afterwards.
What I've noticed is that Marshmallow doesn't seem to allow apps to set automatically 'airplane mode'. I'm a bit lost about the reasons, but it seems that I need to have this Xposed installed.
Now, my questions.
1) It seems that the current default procedure to install Xposed Installer and run the Framework install does not work and we need to use this procedure
2) On that guide, the link for Xposed arm v78 sdk 22 is broken, and in the original link I find multiple zips and I'm not sure which one is the correct one I should use.
3) Do I need Gravitybox for my specific purpose of having Sound Profiles able to set this airport mode?
4) Do I really need to do all of this to simply achieve my goals?
Sorry for the long questionnaire but I do really appreciate your help in this
Thanks!

thtieig said:
1) It seems that the current default procedure to install Xposed Installer and run the Framework install does not work and we need to use this procedure
2) On that guide, the link for Xposed arm v78 sdk 22 is broken, and in the original link I find multiple zips and I'm not sure which one is the correct one I should use.
3) Do I need Gravitybox for my specific purpose of having Sound Profiles able to set this airport mode?
4) Do I really need to do all of this to simply achieve my goals?
Click to expand...
Click to collapse
Just to help others that might face the same... here some answers to my questions
Yes, the instructions in "Sound Profiles" app need to be ignored and follow that thread.
The file to install via TWRP (or any other recovery mode) for ZUK Z1 with Marshmallow is xposed-vXX-sdk23-arm.zip. My understanding is that the architecture of this phone is ARM, and the Marshmallow sdk is the 23.
Then I've installed XposedInstaller_XXXX_.apk (latest available) and I can see that all seems installed.
Last bit, is downloading and installing the module that allows apps to access Airplane mode. Found the apk on here. I've used the most recent.
Once all is installed, I opened Xposed Installer, got into 'Modules' an ENABLED "Airplane Mode Helper". This must be enabled in the modules' list AND within its own options.
A nice reboot and all seems working
About Gravitybox, I had a look to this video and I've realised that I don't need this. This is an app for who has stock roms. Mine is the Cyanogenmod (v 13) and it's already heavily customisable.
There is still the pending question... is this the right/best app to use to achieve my goals? Until further suggestions, I believe it is

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

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