yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] wacko37:
Woah was just about to embark on setting this up based on your previous comments, luckily i read this post. I am familiar with Tasker(i think) so i will look forward for your next reply so we can make this happen :D

Anyhow i think its time to give XDAuto a go,(now that a few things have been amended) have been waiting for this release for a while since "Zaph" had first mentioned he was working on it.

Thankyou all for your hard work in making this happen
[Android Head-Units] jpapadami:
I updated to 1.1.6b2 from Tuatara's 1.1.4.3 rom and when I reboot into recovery it's stil CWM and not TWRP. Is there any way to fix this? Can I just install a TWRP zip update through CWM?

Also, for the next update it would be nice to be able to see the Apply button for changing hardware button colors. I can't dim the buttons and would like to :).

Nice job BTW. The zip updates and TWRP are very useful and such a big plus for this unit.
[Android Head-Units] topcatbv:
Everything went smooth from v39 to v40 with 1.1.5
[Android Head-Units] toologic:
To [MENTION=4173803]Bokomaru[/MENTION] Can I change (delete or add) applications in /preinstall directory into Recovery flashable zip by simple way (copy to zip, delete from zip)?
[Android Head-Units] Duck Dodgers:
Whoop Whoop

Just ordered NU5261S-H-H0 through Summer :D:good:

Now just need to wait for it! :rolleyes:
[Android Head-Units] Black6spdZ:
we need to get recovery ZIPs for all of the misc flashable options, TWRP/CMW recoveries, kernels, etc. To be honest unless anyone really wants a factory ROM I would take a new unit, RKBatch tool flash the TWRP recovery.img and then flash everything else from then on through recovery. If there was only a way to enter recovery from a cold boot it would be perfect.
[Android Head-Units] Duck Dodgers:
Wiki note

Was just going over a few bits on the Wiki in preparation (I'm sooooooo excited :D) and I noticed that there was a link for a Kia head unit (NU5241S-H-H0). I had a look at this as my wife has a 2010 Kia Sorento and I know she'll want what I am getting!!!!! Reading the link though mentions Wince unit so I don't think this is the same setup.....

I could be wrong so shoot me down in flames if need be, but this should be mentioned so not to mislead

I'm struggling to find a pure android unit that will go in the Kia so I guess she'll have to wait!
[Android Head-Units] zanix:
I just added this link to the wiki today, I **think** it's the same as the other units. Could you contact Summer and confirm if this is true?
[Android Head-Units] Duck Dodgers:
I've mailed her and will let you know.....
[Android Head-Units] amigo74:
Is it possible to integrate the native support of 4g lte surf sticks such as huawei e3372s in new releases, so that apps like ppp widget 2 must not be installed ??
[Android Head-Units] bockywocky:
Sorry type something wrong
[Android Head-Units] wacko37:
Just installed XdAuto b2 last night.

Ran into a problem when updating from Tuatara Rom via CWM.

The rom installed ok via update zip but first bootananition did not change from Tuatara's and TWRP did not replace CWM.

I tried to update/flash again but on next boot it froze at tuatara kernel boot screen.

I then done a full restore via RKBatchtool and everything is ok now...loving the new Nav bar!!! on my 8" display.

Over the space of 4 hrs I have had a few random reboots.... no sure why as they where totally random during setup of device (apps etc) will continue to monitor over the next few days.

Thanks to all you has made this happen....good work!

Ps. Chances are that i problem done something wrong so I'm not saying anything is wrong just letting you all know how it went for me
[Android Head-Units] f(x):
A proud new owner and completely noob here when it comes to andriod.

Can anyone tell me what is the different between CWM and TWRP recovery rom? Will I be able to flash the any custom rom posted on this thread with either one of it, or particular rom must go with one or the other?
[Android Head-Units] wacko37:
Picture of XdAuto b2 using smart launcher
[Android Head-Units] zanix:
I have just noticed a bug with the xdAuto navbar.

When media controls are selected, sometimes the back button and a 3 dot button will pop up and push off the volume and speedometer icons. It seems to happen when the keyboard pops up.
[Android Head-Units] Bokomaru:
I've figured out all the code to make reverse sensing it's own keycode and I'm commiting those changes to the repository now. The next release will have those changes in it.

The intent 'android.intent.action.KEYCODE_BONOVO_REVERSE' will be sent when reverse state changes

---------- Post added at 11:31 PM ---------- Previous post was at 11:27 PM ----------

I've got to dig in and see what is causing the recovery zip to not save the kernel and recovery, they are definitely in the zip but something isn't working right.

I know [MENTION=2190016]Zaphod-Beeblebrox[/MENTION] has seen some random crashing as well. I suspect this might have to do with the overclocking. Until we know for sure I think the best course of action is to make the default kernel not overclocked and then have an alternate kernel that can be flashed in recovery that is overclocked.
[Android Head-Units] ElfinJNoty:
Why can't you include the custom kernel with the stock kernls settings. And allow the kernel to be configurable with one of the popular kernel tuning apps

i.e Trickstermod, Device Control, Synapse, Kernel Auditor
[Android Head-Units] Bokomaru:
I have no idea how any of those apps work, generally I have no reason to overclock a device. I prefer to make sure the base is reliable before changing too many variables.
[Android Head-Units] wacko37:
Bloody hell your a busy man, will look forward to the next release :good:

Just wonder, when using the reverse camera linked to the reverse signal input (current setup), no matter what state the android box is in (booting up or even disconnected) it will always switch to the reverse picture on the H/U, obviously this wont be the case if you will be using the AVIn app/Input and tasker to know when to switch, as the Android box will need to be running to apply your fix, am i right?

If this is the case If i split the camera signal to both Inputs (reverse & AVIn) i should have both angels cover?

Regarding the random reboots, i always seem to be doing something on Torque, i will continue to monitor and if reboots continue i will remove torque and test again. (only if you agree that an app can cause a reboot?)
[Android Head-Units] Zaphod-Beeblebrox:
Can you post me a picture? I suspect the 3 dot button is the overflow menu button
[Android Head-Units] toologic:
to WIKI editor

Please add to wiki description about v39 and v40 MCU firmware

V40

<1> Add DVD and reverse OSD overlay

<2> Fix V37-V39 version can not wake Android

V39

<1> Fix external box Andrews hosts video chip initialization error

Source - support of russian locale seller (distributor?) Carpadmedia.ru - http://1drv.ms/1wEaJxJ
[Android Head-Units] Zaphod-Beeblebrox:
You know you can do that yourself, right?
[Android Head-Units] toologic:
Ok. i will try to do it :)

1. Small confusion in xdAuto 1.1.6b2 - after installation via recovery i get again AVIN application named NewsmyAirConditioning... :confused:

2. Key Light settings parameter do not fit on the screen. "Save" button is not visible.

3. I asked [MENTION=5498033]Summer[/MENTION] about sample ir-remote control AB (in facebook group). She told me that this example I can find on our forum. Sorry, maybe I did not carefully read a thread - but I did not see it. Could anyone use an infrared remote control? Please link for read.

4 and last Does anybody voltage measurements (or other signal) on the wires TXD - RXD (No. 8 and 9 in the picture 2). Especially interesting is the presence of such a signal when you touch the screen.
[Android Head-Units] Danny.69:
I use this remote control: http://es.aliexpress.com/store/prod...ss-Mouse-For-PC-Black/1166416_1802280369.html

but only functions: play / pause, forward music, music back, and the volume keys is the overall volume of android, not the music
[Android Head-Units] Bokomaru:
1. What language are you using? That specific string in the translations file must be wrong.

2. Known issue. Haven't gotten around to fixing it.

3. For testing I've used a random IR remote control and was able to set some mappings with the KeyTool app. Seemed to work fine, didn't test extensively.

4. I haven't had time to test, but based on where the traces go on the board I've assumed these were debugging pins so the manufacturer can do testing without removing the unit from a vehicle. One of these days I'll play with it, unless someone gets to it first.

---------- Post added at 09:03 AM ---------- Previous post was at 08:33 AM ----------

It's the 'ic_sysbar_home_dots'. If you turn off 'Media buttons in Navbar' you see it slide over under the clock.

On a NU3001, if you hit the capacitive power button and turn it back on it seems to happen.
[Android Head-Units] Zaphod-Beeblebrox:
I don't use the Media Buttons mode since I have a Nu5002 (I need my home button) - and that's what the clock & 3 buttons are.

There might be some logic failure in which views are visible when keyboard is active/de-activated.

I've been thinking of adding an option to allow/disallow all of the various buttons. It's a bit of paint to code, but still easier than a full up port of AOKP navbar.

I'll have to re-work some of the logic on those views then, and it'll fix.
[Android Head-Units] zanix:
I can get a photo after work today.
[Android Head-Units] defy_user1:
Hi there,

i tried to flash the new xdAuto img via rockchip tool, flashing went fine but now i am running into an issue... after reboot i can see the flying dots and nothing happens....

tried to flash again and i can see, after the teamwin logo disappears, some messages like "unable to mount" ... i think this is the fault.

what can I do?

How can i boot into twrp recovery?

thanks!

Edit:

I will follow the instructions to flash the recovery partition after I flashed the original ROM.

Hmpf... flashed the recovery files... but there is no "reboot to recovery" - app which is working :/

Edit2:

At least it worked...

Flashed Tuatara ROM via Rockchip Tool

Used CWM to flash the xdAuto

The Boot-Logo ist still the same but the rest seems to be OK
[Android Head-Units] DragonFlye:
Read this post http://xdaforums.com/showpost.php?p=60082536&postcount=3879 using a remote control with the NU3001.

It's an remote from another Android device, probably using the RC5 or RC6 protocol

from dmesg:

<6>[ 1.371823] lirc_dev: IR Remote Control driver registered, major 250
<6>[ 1.371861] IR NEC protocol handler initialized
<6>[ 1.371886] IR RC5(x) protocol handler initialized
<6>[ 1.371912] IR RC6 protocol handler initialized
<6>[ 1.371936] IR JVC protocol handler initialized
<6>[ 1.371961] IR Sony protocol handler initialized
<6>[ 1.371987] IR RC5 (streamzap) protocol handler initialized
<6>[ 1.372017] IR LIRC bridge handler initialized

The (partially learning) remote is an OEM device. This one is branded for Zidoo. If you look for it, it could probably be sold separate
[Android Head-Units] Zaphod-Beeblebrox:
I'm assuming you came from a stock setup. We can't seem to replicate this issue, but on 'virgin' units, the ROM isn't appearing to flash properly with RKBatchtool.

I've got 3 Android boxes, and have had trouble flashing two of them (one is still virgin - waiting for some time to take an image of that one before flashing).

What's worked for me is to flash Tuatara with RKbatchtool and let it boot. Then flash xdAuto1.1.6b with RKbatchtool and you should be golden.
[Android Head-Units] Duck Dodgers:
Wiki details

Summer confirmed that the website is incorrect and it is NOT WinCE, so should be pure android and same setup as the others. Wiki does not need to be changed :)
[Android Head-Units] runsnbunsn:
hey!

anyone tried Nu3001 or NU5002 in a Mazda 5/Premacy?

have the 2007 model and not shure if SWC will work, which is pretty important for a radio without volume knob

I found a Mazda 3 2008 user in this thread which says it works with Key 1 and GND connected, not much info anywhere else...
[Android Head-Units] zanix:
Just check if your car model uses resistive steering wheel controls, if it does it should work just fine.
[Android Head-Units] zanix:
Here you go
[Android Head-Units] zanix:
Good to know, thanks for checking
[Android Head-Units] pawcu:
What exactly is the problem with dual systems? Unfortunately the only system that has physical buttons is dual system and i would prefer if the radio had physical buttons.
[Android Head-Units] tedted22:
Yes, works perfectly. I have a Mazda 5 (2010) - the original not the new model. Just connect Key 1 and GND. There is no Key 2 on the Mazda ISO connector, so just leave that unconnected from the NU3001.

Looking at the Mazda iso connector (image attached), you connect Key 1 from NU3001 to "N" and Key GND to "P"

P.S. The NU3001 does have a volume control on the physical unit. It's not a knob but an up/down slider. But it works either way...
[Android Head-Units] pawcu:
Thanks. Unfortunately what i meant was that i wanted something physical to feel. AFAIK it is still touch, meaning it will be hard to find the slider unless you have to look at what you are touching, especially when you are driving. So i guess the questions still remains as to whether the dual systems are crap or decentish.

Thanks
[Android Head-Units] toologic:
As I wrote earlier, I updated the firmware to 1.1.6b2 through TVRP. After that I had a problem with Skype, Google Voice Search, and several reboots during the day.

Yesterday I reflash the box using RKBatchTool and today tested it on the road.

What do I get? Permanent reboot the device after 3-5 minutes. The reason is not clear. This can occur during configuration management, touch for call any application, when working radio, and when it is not running any application.
[Android Head-Units] blacklistedcard:
Its funny. I never had one reboot with my device. Even overclocking to 1.8ghz. Your reboots are bad. I wonder what is causing them?
[Android Head-Units] zanix:
Most of the Dual OS units run on WinCE and launch Android in a virtual machine. This causes them to be slow.

Some unit use a switch between the 2 OSes, that also means you would have to swap between them to use all the functions and you could not share data between the two.

The Dual OS units are also not compatible with the hardware in the NU series, so all the info in this thread would not apply to whatever you get.

---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------

No random reboots here, running xdAuto 1.1.6b2. I used the flash tool to go from Tuatara.
[Android Head-Units] pawcu:
OK thanks for the info. I guess ill have to get the touchscreen variant and work with it. Possibly try add some physical controls somehow.
[Android Head-Units] zanix:
This unit is compatible with steering wheel controls or any type of resistive controls
[Android Head-Units] usafle:
I've been out of the loop for sometime now recently due to work. For that reason, I have NO idea what the current ROM is??? I've tried to look through the threads / posts here and there seems to be like 10 different ROMs floating around now (yes exaggeration but funny one I thought)!!!!

Is there ONE rom now that we are focused on using / testing / developing or has everyone gone out and created his own ROM?
[Android Head-Units] blacklistedcard:
1.1.6b2. It is on the first page. It is a complied of the code on GIT Hub.
[Android Head-Units] usafle:
So this is the one that is being actively developed from now on?

Because I'd hate to see us start making some headway on "aesthetics and use" and now everyone branches out and creates their own ROM.

I'm flashing this version now, FULL WIPE and will reload everything. This way I ensure there are no "ghosts in the machine" from any previous version. Yes, it's a pain to reload / reconfigure everything but hey, that's what I'm here for :)
[Android Head-Units] kwalsh24:
Quick question, would it be possible to make a widget that would turn the Bluetooth of the hu not the box on and off? Or is there a feature on the new community development rom for that ?
[Android Head-Units] toologic:
I did reflashing 1.1.6b2 and again i get a few reboots after 3-5 minutes of use ab (on table).

I analyzed the bug report and saw at what frequency the processor works.

I think, that my problem with 100% cpu usage on 1800 mhz

Here are the statistics:
[Android Head-Units] Bokomaru:
xdAuto ROM 1.1.6b3

I hate to post an update and then run, but I'm heading out for the weekend so I won't really be able to respond much until Sunday. I just felt that getting the install from recovery working properly and disabling the overclocking were things that needed to get pushed out asap.

I still have not uncovered the issue related to flashing the image, I still need an image of the raw flash in order to troubleshoot the issue.

RkBatchTool flashable image

Recovery flashable zip

1.1.6b3: May 15th 2015

Update paths so install from recovery zip actually installs kernel and recovery

Disable overclocking in kernel by default (compile with CONFIG_MACH_RK3188_OVERCLOCK=y to enable)

Added REVERSE sensing keyinput and 'android.intent.action.KEYCODE_BONOVO_REVERSE' intent

---------- Post added at 12:03 PM ---------- Previous post was at 11:09 AM ----------

The governor was changed to performance at the same time the overclocking was added, so it should spend all of the time at the highest speed possible.

You can switch the governor back to 'interactive' which it was before by calling:

echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

If you want this change to persist you will have to add it to an /etc/init.d/ script.

---------- Post added at 11:09 AM ---------- Previous post was at 11:03 AM ----------

Yes it would be possible to do. Pretty much anything that the "Update Settings" app can do we can work with.
[Android Head-Units] kwalsh24:
That would be awesome if so. Then I wouldn't have to always open the Bluetooth app to disable it. My SIRIUSxm radio runs over that and it can be picky with syncing. So it will cut My fm on and off if it doesn't sync correctly. Gets annoying lol.
[Android Head-Units] blacklistedcard:
Try 1.7 and see if the reboots happen
[Android Head-Units] runsnbunsn:
Thanks! I think I'll give it a go and order one, still unsure if NU3001 or NU5002

from what a read both come pre-rooted, and page 1 says source code for NU3001 is there, do the ROMs shared here also work for the NU5002?
[Android Head-Units] wacko37:
Yeah I have the NU5002S and all roms here work on my unit
[Android Head-Units] Bokomaru:
Wow, seriously? "What the hell?". Next time I'll wait till everything is completely tested by the q&a department before making a beta release.
[Android Head-Units] jpapadami:
I would hope that "What the hell" in other languages is used as a way of saying "What happened?" (from a dev perspective) as we didn't have this problem in 1.1.6b2 :)

Thanks for all your support and efforts. You've been really active.
[Android Head-Units] ElfinJNoty:
Please don't hesitate to release a beta.... And also please don't be disrespectful to peeps trying their best and releasing their work to the masses. No need to discourage. If you want a solid stablish experience than stick to stock everything
[Android Head-Units] blacklistedcard:
Uumm.. I just built GIT and installed it with su fully working. Just had to update to the latest version from the play store, which it prompted.

---------- Post added at 02:05 AM ---------- Previous post was at 01:59 AM ----------

Built it with Linaro 4.9.3 and Android Linaro 4.9 with over clocking set to 1.8ghz.

My unit is working flawless. No SU or reboot problems.
[Android Head-Units] ElfinJNoty:
I don't have a device I can build with currently... Care to share your linaro optimized build please?
[Android Head-Units] horn34:
Anyone have any ideas? Tua's ROM is screwing up my Escort Live app due to all the NZ entries in build.prop.

Is there a specific app needed to modify build.prop in this ROM? I've tried with the default text editor and the ES File Explorer text editor, but the edits aren't saving.

And yes, the directory is set to R/W by Root Browser first.
[Android Head-Units] Danny.69:
you used some kind of IR receiver for the remote control work?

or works directly?
[Android Head-Units] pawcu:
Ok thanks. I might just end up getting one of these then. Reversing in my Hilux is proving to be a bigger challenge than i expected... Especially after coming from just riding a bike haha.

Are there any bugs that come when you buy it that need fixing? From the original post it seems that most of the bugs can be fixed.

Thanks once again.
[Android Head-Units] Zaphod-Beeblebrox:
It's not the first time I've seen one of [MENTION=5612737]toologic[/MENTION] post and thought to myself 'screw this'. I'll give him the benefit of the doubt and assume it's a language barrier.
[Android Head-Units] boschie:
The app you are using to edit the file needs to have root access gained by SuperSu. It has been written in a reply before.
[Android Head-Units] toologic:
To [MENTION=4173803]Bokomaru[/MENTION] and all members

I apologize if my exclamation angered you. My exclamation was supposed to mean exactly - what happened? And no more...

My spoken English is too bad, and I sometimes use google to translate.

I promise to use only technical terms, without slang, the true meaning of which is unknown to me until the end. :)
[Android Head-Units] Zaphod-Beeblebrox:
Bluetooth Music & AVIN testing

I started working on code to allow ducking in the BT Music app (BTW, it doesn't appear that I can control BT Music volume separately, so my implementation won't actually DUCK, but rather pause & restart BT Music)

I'm having some issues with both BT & AVIN audio on my particular setup, and want to know if anyone else is using this and how it works for them. I'm on MCU V40, and I've tested this with 1.1.6b and 1.1.6c to same effect:

If I play either BT or AVIN, I lose android audio. No mixing of paths appear to be happening on the MCU. Even when I quite BT or AVIN, I still have no android audio. Reboot doesn't fix. I have to physically unplug the android box. Once the box is plugged back in an booted up, I have android audio, until I use either of those apps again.

Is anyone else using either of these sources and what's your experience?
[Android Head-Units] ker2gsr:
I installed b3 and at first the su binary update failed but the second time I tried it successfully no need for kingo root
[Android Head-Units] DragonFlye:
Nope. The unit has an build-in IR-receiver. At least mine does (NU3001).

Just need to figure out which Consumer-IR protocol the remote uses. If the protocol is known you can buy (or use) any remote you'd like.

I know its NOT RC6 (that's from MCE remotes)

Surprise! Just tried my LG TV remote and the remote from my Yahama Receiver. Those work too!

Just start the KeyEditor App, switch to the IR Tab and press one of the blue buttons. Hold whatever remote you've got in front of the unit and see which one responds. If you've got a working one you can assign all of the available blue buttons to a remote button
[Android Head-Units] wacko37:
I have just installed this Rom on top of ...B2 using the recovery Zip with no problems at all. SuperSU Updated first time also.

Thanks guys once again, now to setup intent in tasker!:D

---------- Post added at 01:38 AM ---------- Previous post was at 01:08 AM ----------

Just updated to B3 Rom, Android audio (poweramp etc) is working ok after using both other sources AVIN and BT audio. I am also on MCU v40

Hope this helps
[Android Head-Units] Zaphod-Beeblebrox:
Can you use them concurrently?

Ie, Nav audio/directions overtop BT or AV?

Maybe I need to reflash MCU