yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Duck Dodgers:
NU5261 HU received (thanks Summer)

Right guys and gals

Picked up the HU from DHL office last night and stupid of me but forgot I needed an external power adapter to set it up inside flat.

So I've ordered this - http://www.amazon.co.uk/dp/B00MPDJQFA/ref=pe_385721_37986871_TE_item - should power Android box and head unit fine (that's if the connector is the right size). Should be with me tomorrow and I have a long weekend to play with it.

Not sure what the stock ROM is. Is it ok to go straight to 1.1.6b3 and MCU v40 or does it need to be incremental changes?

Is CWM best for the initial full ROM backup (TWRP is imbedded in 1.1.6b3?)

Going to get all apps, etc. installed via house wifi so I can then get it installed in the car next week. I'll try and get various photos done periodically. I'm going to attempt to install a reversing camera (with wireless transmitter) too. Never done anything like this with the car before so be prepared for a lot of cursing and swearing!!!!!!

One thing that did surprise me (even though the dimensions are on the wiki!!!!) was the size of the Android box. I have another Android box for the TV and the one with the head unit is about half the size!

Anyway I'm sure I will be back over the next week with 1001 questions - that Wiki will not know what's hit it! :p
[Android Head-Units] pawcu:
Are there any wiring diagrams for the RM-X4S? thanks
[Android Head-Units] ultradj83:
Modify partitions

Hi there!

I want to expand /userdata partition from 1 to 3GB shrinking /user.

This is the standard layout:

So mmcblk0p7 needs to be increased to 3GB shrinking mmcblk0p11, other ones needs only to be moved.

How can I do this?

Thanks a lot!
[Android Head-Units] blacklistedcard:
Let me take a look at it.
[Android Head-Units] Fedorych:
Ask Tuatara.

It was once the Tuatara ROM 1.1.4.2 on Google Drive with

Now it is removed from there. I do not understand why he deleted it.

I installed it, and then updated on xdAuto 1.1.6b1 .

And now I have xdAuto 1.1.6b3 with 3Gb data partition:) Very comfortable.

In KeyEditor.apk set the command to "change source" on the physical button (my model NU5261S-H-H0) or steering wheel button. It will comfortably to switch from radio to music and back again.
[Android Head-Units] blacklistedcard:
My Alpine remote works with the NU3001.
[Android Head-Units] zanix:
There is a link on the wiki on how to do this

http://xdaforums.com/showpost.php?p=58859034&postcount=2975
[Android Head-Units] defy_user1:
Ordered the Blaupunkt RC10 IR Remote:

http://www.amazon.de/Blaupunkt-7607...sr=8-1&keywords=Blaupunkt+Fernbedienung+RC+10

I have another usual remote from my TV which works perfectly so I thought the RC10 wouldn't be a problem...

But it doesn't work! Nothing happens if I push any button :/

Is it possible to edit the IR-Receiver to get it working with this device?

Thanks!
[Android Head-Units] Duck Dodgers:
Minix AirMouse NEO A2 Lite

I've been using the Minix AirMouse NEO A2 Lite on my Android box (similar spec to Newsmy AB) for my TV and works great. Still waiting for the power adapter so I can use the AB/HU in my house and I'll test it then (hopefully sometime over the weekend)

Link is http://www.geekbuying.com/item/MINIX-NEO-A2-Lite-2-4G-Wireless-Keyboard---Air-Mouse-Support-Six-axis-Gyroscope-Accelerometer-for-Windows-Android-Linux-MAC-OS--Black-338989.html?utm_source=EMS&utm_medium=EMSPD_Product_Link&utm_campaign=EMSPD_Feed_338989
[Android Head-Units] Bokomaru:
If you have a PC power supply or something else that has 12 volts you can wire up 12 volts to the HU and it will supply power to the android box.
[Android Head-Units] larsomen:
I have multiple dedicated servers and vps's running at OVH.

250mbit upload guaranteed and unmetered bandwidth.

Located in france but has very low ping to the rest of the world.

Domain name also wouldn't be a problem for me :P

If i can help just let me know!
[Android Head-Units] Duck Dodgers:
Is there a way of connecting a laptop power supply to the head unit directly? I was going to connect the power adapter to the AB and connect the AB to the head unit via the firewire? Is that not correct?
[Android Head-Units] ultradj83:
Dears, is it possible to restore a bricked devices that can't need started the OS or recovery?

Thanks a lot!
[Android Head-Units] BonOeil:
Hi everybody,

After few months my HU works very good except for the 3G dongle too close of HU which making screen flickering.

What your prefered front-end ? I'm using Car Dashdroid but it lack things !
[Android Head-Units] Bokomaru:
There is a small hole on the android box you can hold a paper clip in while powering the device up to get it into bootloader mode. Then you can use the rockchip software to flash and img file on

---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------

The HU can power the android box, but the android box cannot power the HU. So your best bet is to supply 12 volts to the HU connector
[Android Head-Units] Psy87:
Hopefully you get it working.

Maybe the IR receiver can be wired to the TXD or RXD cables? I think WHEEL cables will not work since the IR Receiver transmits signals, not diffrent currents.

What voltage does the IR receiver need? 5V?
[Android Head-Units] Duck Dodgers:
Thanks Bokomaru

So what connector is required for the back of the HU so I can set it up at home (not connected to the car). I'm guessing that the adapter that I bought is useless then? I don't want to be connecting the 12v 2A power adapter direct to the Android Box as it may blow the board?!?!?!
[Android Head-Units] mikereidis:
Hi, As I also posted on the HueFei thread:

I would be interested to know if my Android Auto app might run on this Headunit.

I do not (yet) own any hardware headunit, except a Pioneer 4100-NEX for Android Auto testing/reverse-engineering.

APK and details here: http://xdaforums.com/showpost.php?p=60894402&postcount=94

Thanks ! :)
[Android Head-Units] ultradj83:
Dears,

I've just been flashing my 1st firmware with customer logo, animation, wallpaper and apps and /userdata expanded to 2GB..

It works, there's just a little problem...

I set 24 apps to by preinstalled, but some of the are missing.

How can I troubleshoot this?

Tks!
[Android Head-Units] DragonFlye:
Don't know if RC10 stands for the IR-protocol used but these are the protocols that get initialized:

<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
[Android Head-Units] defy_user1:
Well I read that the RC10 doesn't use a usual IR-protocol :( It is working with different lenghts of the signal etc...

I have to buy another sender now :mad:
[Android Head-Units] DragonFlye:
Hello, Welcome.

Forgive my ignorance.......but what does it do?

I've read the link but I still don't know what it does. It it some some of screen-mirroring?

It needs Android Auto (on the server side), I gather. The Aahead app installs on the HU but shows a blank black screen, not indicating if it has encountered errors. Android Auto does not install on my phone which is 4.4.2 (it needs >5.0)
[Android Head-Units] m.r.davies:
I'm now in the same boat

The joying one is quad core

http://www.aliexpress.com/item/2015...VD-player-GPS-Stereo-Wifi-3G/32297415686.html

but only 1gb ram....it does have 16gb of storage though and working RDS

what did you go for ? any advice for me?

---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------

I would prefer a hardware volume control

This model has WinCe and android

http://www.aliexpress.com/item/News...r-univeral-dual-system-carpad/2034998210.html

however, it was mentioned by the op this is a frankestien combined version

However, i dont plan to use CE but would like the volume knob

Any advice or comments appreciated!
[Android Head-Units] Stormbringer!:
Post number #4831 gave me the idea to download update-1.1.4.2- tuatara.img from the site where Fedorych said it wasnt there anymore (it is).

I used the rkbatchtool to recover update-1.1.4.2- tuatara.img file, booted up the system (took the opprotunity to upgrade my MCU) and then updated to xdAuto-1.1.6b3.img.

Now everything works as expected..
[Android Head-Units] deeznutz1977:
Question after u updated from tuatara's do u still have his boot animation?
[Android Head-Units] Stormbringer!:
Uhhh... not sure to be honest - I just did it really quick this morning since im heading out this weekend. The update-1.1.4.2- tuatara.img had an image of the green android guy on an angle with two gears above him and then the swirly colored orbs then android appeared and then the desktop... Think now its just the swirly orbs and android. then the desktop. Yeah, im not that technical with android - sorry!

---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------

Zaphod-Beeblebrox,

Love the rom now!!! :) :good:
[Android Head-Units] deeznutz1977:
Lol.. thanks bro..
[Android Head-Units] Danny.69:
and modifying the keyboard editor.apk to recognize a USB IR receiver ???

It can?
[Android Head-Units] mikereidis:
"Android Auto" (AA) is Googles "Big Thing" for car electronics and is Google's version of Apple's CarPlay.

There is AA info here: http://www.android.com/auto/ and for devs: https://developer.android.com/auto/index.html

On XDA, under the parent forum of this new section: http://xdaforums.com/android-auto/android-auto-general and offsite: http://forums.androidcentral.com/android-auto/

Android Auto has 2 main hardware components: A headunit in the car, and a phone (or tablet) running the AA companion app. You get in the car, plug your phone in by USB, the phone charges, and you get the AA screen on the HU. See links above for pics and videos.

AA is a "special environment" that goes well beyond screen mirroring. It's designed to be non-distracting, but this requires apps to have special AA support, which limits the apps that work, especially at present.

There was a LOT of excitement about AA, but that dissipated quickly when people realized they have to spend at least $500-700 for a compatible headunit, like the Pioneer 4100-NEX.

My headunit app can effectively turn a $200 tablet into a headunit, albeit with limited functions at present. So it's a much cheaper way to use, or just to test Android Auto.
[Android Head-Units] Tuatara:
My ROM version 1.1.4.3 has the same 3Gb partition layout - so you can just flash that one instead. I haven't deleted anything from my Drive ... ROM 1.1.4.2 is still there, so you could use that one if you wish.

I haven't had the time to look at xdauto yet, but I would have thought that the xdauto ROMs are also using the 3Gb partition format. But maybe not???

My full Google Drive link (with all folders accessible).
[Android Head-Units] leonkernan:
I'm going to give your app a run on Monday when I can borrow a Moto G from work to test with. (I'm an iPhone user)

I did a bit of reading an see you reverse engineered the protocol for your app to use, just wondering if you know of anyone doing the same on the Carplay side?
[Android Head-Units] skiddd:
Hi Guys,

I am using the NU-3001 running stock MCU+ROM for 4 months now. I think my MCU version is still V28 :)

Since I don't want to risk losing all my apps/customizations etc when I start experiment with MCU and ROM updates,

I have ordered the 100 U$D Android Box only from summer a few days ago as a test unit.

I also plan to replace the 8GB eMMC with a 64GB eMMC part# KLMCG8GE4A-A001.

I have a few question for the DEVs out here before I do the hardware mod:

1. Does the Android Box eMMC use a MBR+GPT Partition Table wherein I could just re-size the Data partition manually and correct the checksums by hand?

2. Are there any limitations on the Kernel side about the maximum Size of the eMMC that it supports?

3. I found some info here on how to adjust data partition:

http://xdaforums.com/showpost.php?p=58859034&postcount=2975

Would this be enough to re-size my data partitions for the 64GB eMMC?

Anyway, I know most people would warn me that Changing eMMC is hard and would require rework tools etc...

But luckily, this is something which is related to my line of work, so I will not have problem doing the following:

1. Removing original 8GB eMMC from Android Box PCB

2. Dumping Entire USER + BOOT1 + BOOT2 eMMC Partitions + EXT_CSD Block from the 8GB eMMC via a BGA Socket

** Modify Dump to work with the 64GB eMMC using info from DEVs in XDA

3. Writing Entire USER + BOOT1 + BOOT2 eMMC Partitions + EXT_CSD Block to the 64GB eMMC via a BGA Socket

4. Installing the 64GB on the Android box PCB

5. Hoping that the Android Box will still boot up after the Mod.

I have already modified a few Nokia Lumia phones by replacing the stock eMMCs with a larger capacity eMMC.

The WP OS automatically re-sizes the DATA partition Size in accordance to the eMMC Size so I did not have

to modify anything on the software side. I am planning to do the same on this Android Box.

That's all for now. I hope some Devs will shed some light into my inquiry.

Best Regards,
[Android Head-Units] DragonFlye:
Ok. thanks, It's clear to me now.

For testing purposes, it's a pity I don't have a lollipop device to install the AA companion app on to use it in conjunction with your AAhead app on the HU.

On the other hand, judging from the video's this would come in handy for "dumb" clients. The NU3001 however, is a full fledged android machine and you can have it do anything you'd like. Playing music using your favorite musicplayer, navigation using apps you'd like while still be able to interact with your phone and give the HU numerous (personalized) voice commands.

I see a (little) advantage if someone else (your passenger) would like to use your HU to check his notes or play his music. It's not bound to one user.

Perhaps I will be blown away once I actually can try it. They really should dispense with the cartoonish backgrounds though.....
[Android Head-Units] mikereidis:
:)

No, but I don't really follow iOS news.

I've thought about carPlay and iPads etc., but rejected the idea

Low level Linux and Android are my specialties and I don't see myself learning iOS.

This app will appeal more to "tinkerers" and most of those are Android people, running custom ROMs or root mods.
[Android Head-Units] mikereidis:
AA may not be much to look at yet, and there are many reliability, compatibility and other issues to be addressed.

But I am confident that Google will pump dozens to 100's of millions of $dollars into Android Auto in the next several years. Connected cars are one of the most important current battlegrounds for mobile & "Internet of Things".

Google's main advertising business is extremely hungry for more data about us; where we drive; when we last changed our oil,....

Imagine everyone in the car can plug in their phone for a charge, and each passenger has a big screen of their own to do just about anything. Mom in the "shotgun" seat can swipe and see what junior is doing in the back. They can all share a single LTE data connection.

Meanwhile, the "car" knows you're all hungry (it's 12:30 PM and it knows you usually eat at noon), so the "car" let's you know there's a drivethru window up ahead, and you're ahead of schedule so have time... And the "car" pays automatically. And orders ahead for you... And Google collects it's 25 cent commission for the Big Mac's.

This is all coming, and much, much more. Driverless cars will give us that much more time to consume Google's services. Fortunes will be made, and some lost.
[Android Head-Units] alaninsitges:
Wait, so this lets my Android 4.4.x head unit act like an Android Auto device? And I can plug my Nexus 6 into USB and get AA functionality? Holy ****. Dude you need to explain this better. It will be huge for a lot of Android HU owners.
[Android Head-Units] leonkernan:
Just to clarify, i'm not worried about iPads. I just want to plug my iPhone into my NU3001 and get Carplay, just like you've done with AA.

Anyway, i'm sure it will happen one day when these things become more popular.
[Android Head-Units] mikereidis:
:)

It allows ANY "compatible"* Android device to act as an Android Auto Headunit, like the recent Pioneer 41/71/8100-NEX line.

Could be a phone with a 4" screen, or a big ass 20+ inch Qualcomm developer tablet.

* - "Compatible":

- Android 2.3 or 4.0/4.1+ phone or tablet (only tested 4.1+ at present). Watches/wearables, Android TV or other Android related products likely won't work, but maybe could with some work.

- Device must support USB Host Mode, and practically speaking, needs a kernel that allows the phone/tablet to charge while in Host Mode, as well as a USB OTG Y cable and ideally a powered USB Hub.

- Requires a TouchScreen and good H.264 decoder, which I think almost any Android device has.

- May require some work/bug fixes from me to be compatible with specific devices. I officially support devices I own, like both Nexus 7's and Nexus 9. I am considering supporting these Chinese Headunits; in part because putting together a $200 tablet, the USB stuff, power supplies and other parts may be around the same price as these Chinese HUs, and purpose built hardware often works better than homebrew.

At present, functionality of the app is limited; it's mostly video from phone to tablet/HU and touch response in reverse direction. Audio is through the phone (so far), microphone does not work (yet) and phone calls thus likely won't work yet.

A Pioneer Headunit provides many other features that this does not, like AM/FM/HD radio.

I'll presume you understand Android Auto basics. Normally your phone plugs in the Headunit. In this case the phone plugs into an Android tablet or a 2nd phone that should be dash mounted, so you have 2 devices.

I had to put a LOT of effort into reverse-engineering the Android Auto USB protocol and expect this to be ongoing, unless info is released; it is not publicly documented. So far about 600 hours over the last 9 weeks, since the AA companion app was publicly released (only after Pioneer started selling HUs, with no AA software out yet.)
[Android Head-Units] Kevinkuensken:
[MENTION=260727]Tuatara[/MENTION]

when do you make a new Rom?
[Android Head-Units] Tuatara:
I'm not certain I will ... it seems that xdauto is progressing incredibly well, and I'm keen to get into that development process as soon as I can. (darn real-life work getting in the way! :()

Although ... if there is demand for it - I can probably put together a ROM based on the latest 1.1.5 ROM version, and incorporate any/all recommendations - like making a US/New York timezoned version. :rolleyes:

If it's asked for, and needed ... then I'll see when I can do this.
[Android Head-Units] alaninsitges:
After poring over the limited docs on their developer site I sort of figured nobody would be able to do it. Surely a lot of the interfaces are lollipop-specific. That's quite an accomplishment.

I'll install it today and see how it goes (obviously sending audio to the HU is gonna be obligatory before it passes beyond being a curiosity).
[Android Head-Units] Danny.69:
could you include the editor keyboard to recognize a USB IR receiver ???
[Android Head-Units] Zaphod-Beeblebrox:
Yes, this does have big implications. I too had thought about trying to do this for our units, but would never attempted it as reverse engineer of the protocols (way over my head!). But until Google release Android Auto source (if they ever will), I figured it impossible.

for those thinking that our unit has more flexibility and power than what AA does, you are correct. However, something like this just gives us another tool and possibility for customization. As the AA eco system takes off, you will find a lot more apps with touch friendly UI's that our small little niche market of developers will never be able to replicate. We will be able to use our units as stand alone devices when we want to, but harness AA as well. It is not an either/or proposition, but a value added on top of what we can already do. It makes use 'better' than a true AA unit in that way.

[MENTION=3575078]mikereidis[/MENTION], do you have any plans to open source this? (hint hint).

---------- Post added at 09:06 AM ---------- Previous post was at 09:00 AM ----------

This is not nearly as easy as you seem to think it is. The existing Key editor & key handling functions are meant to deal with signals from the MCU (resistive, touch, etc). Harnessing controls from a USB based IR receiver will require new broadcast receivers and processing on the Android side since those signals never come through the MCU. It's certainly possible, but its a fair amount of work, and we already have way too many things to do as it is. This is probably a low priority for most, as I don't think many are going to use this in this way.

Several of us have pointed you to other solutions (in particular leveraging other forms of Steering Wheel Controls) that should work with little to no effort.
[Android Head-Units] blacklistedcard:
Just grab some old remote that you have. Seems like the software is working with a bunch of remotes already.

TV or TV Tuner cards are working.
[Android Head-Units] Zaphod-Beeblebrox:
NU5002 (which he has, like me) does not have an IR sensor. I had thought that possibly the RX/TX lines on the harness would allow hook up a sensor, but evidently do not. A USB receiver would not pass those codes through the MCU. Key Editor will never see input.
[Android Head-Units] leonkernan:
Tonight I thought I'd see if I could locate some documentation on the Bluetooth chip used for handsfree support.

I didn't see anything on here so I dug around in the source and started comparing the various AT commands used with different documentation online.

The closest match i've come across is the Flaircomm FLC-BTM5xx line. The command set used in the BonovoBluetooth code is almost a perfect match for the codes in this document: http://www.bcdmicro.co.uk/PDF/BTM5xx-ProgGuide-V5.0.pdf

I thought this might come in handy if we want to extend or replace the Bluetooth support at some stage. I've added a line to the wiki with this link as well.

---------- Post added at 12:38 AM ---------- Previous post was at 12:30 AM ----------

I'm pretty sure those wires are related to CAN BUS support in some cars and aren't normal serial connections. There is a setting to configure the type of car connected in the MCU settings app.

Not sure if there is a CAN decoder chip in our unit though or if it requires a separate box from Newsmy. The various references to that are a bit vague.
[Android Head-Units] alaninsitges:
I've been playing with this today; I'll give you some feedback in your thread.
[Android Head-Units] Danny.69:
and would have a way to connect the IR remote control directly to the KEY1 and GND lines like a command at the wheel it were ???

You understand about that ??

or someone to understand
[Android Head-Units] nFKT:
From previous experience, I would not bother with a dual android/ce device. The CE side is useless and there is no benefit from a boot speed perspective. Also the software package is not updated and flawed.