yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] MrTSolar:
Also, regarding illumination, there are settings that I had to enable in the Update Settings app. I can't remember which menu item it was under, but the option was called Car Auto Brightness.

Do the capacitive buttons light up when you turn on the headlights, regardless of the screen dimming? If they light up with the headlights, then the illumination wire is connected. Some cars (Ford) only engage the dash lights if the headlights are on and it is dark enough.

The illumination wire should be an orange wire if you bought a harness adapter.
[Android Head-Units] Totoix:
If I enable Car Auto Brightness option, will the screen dim if there is +12V in ILL wire?
[Android Head-Units] MrTSolar:
Yes. Enable that option and set the desired brightness (I put mine at the minimum). When the dash lights come on, the screen should dim. There are also settings in that app to change the brightness of the capacitive touch buttons. The Red and Green sliders do nothing; the Blue one controls the lights (the app is set up for RGB LEDs, but the lights are only white).
[Android Head-Units] JanDK:
Thx a LOT for your advice and diagram, very kind of you [emoji108][emoji122]- I'll try to fix it in the weekend.

Also, my car does have a dimmer for the dash, perhaps I could take the signal from there (do not hope it'll interfere with the car....) I'll be back once I've tried either....

[emoji4]

Kindly

Jan
[Android Head-Units] Bokomaru:
Well it has all the functionality they list, it just has 2 extra "Spare Interfaces" that don't appear to be hooked to anything. When the decide what they would want to use them for it's cheaper to just redesign the board than the whole device.
[Android Head-Units] disdigg:
CarPad 3 NR3001

I received my NR3001 CarPad 3 very quickly. I believe it was about 7 days. I installed it yesterday in my 2005 Nissan Xterra (w/o Rockford Fosgate). I used the Metra 70-7550 harness (which may not work on later models, btw). I had to cut the iso connector attach it to the Metra harness. I used butt connectors and covered them in electrical tape for peace of mind. That took the majority of the time as it was more of a basic install. I didn't have time to properly run the usb cables, install my usb hub, back up camera or the included microphone for phone calls.

Should I try using the included mic for calls or would someone recommend a nicer noise canceling model?

Having installed the CarPad 3, I'm relieved that I didn't have to find a place to mount a separate Android box and route a cable between them. It's a nice unit and appears to be identical to the NR3001 from everything I've seen and read.

However,

I'm very disappointed that only 1gb of the 32gb is available for app storage

. I believe this is called the /data partition. Why would they leave it so small? It seems to me they literally used the very same code from the CarPad 2. The remaining storage appears to Android as an External SD card and is referred to as Nand Flash in the Settings --> Storage. Yes, I can move some apps to the SD card, but I thought the 32gb would be native storage... otherwise I could have gotten a CarPad 2 and added an sd card. There is no sdcard slot on the CarPad3, btw. Nevertheless, I don't regret my purchase and I'm confident that there will be a solution.

My plan is to run with it stock for a bit and later install xdAuto. I'm open to suggestions and will answer any questions I can... just don't ask me to do anything that will brick it (I've dragged my feet for a year and finally got one).
[Android Head-Units] JanDK:
Doesn't viper4android work on the built in radio app in XDauto 1.1.6c /v 48

I'm not able to make it work, despite I followed this procedure :

http://xdaforums.com/wiki/Newsmy_CarPad_NU3001/Viper4Android

Kindly

Jan
[Android Head-Units] Totoix:
Is there a process to replace a bonovo apk with a new (recently compiled) apk?
[Android Head-Units] m3co:
I want to buy the new unit, hope you guys can find a "easy" way to change rom to xdauto, and use more that a gig of memory... in the meantime ill standby and wait....
[Android Head-Units] -=Jeff=-:
\

to my knowledge, no it doesn't.. the audio from the radio never travels through the Android portion of the Unit so it will not be tweaked/changed by Viper4Audio
[Android Head-Units] JanDK:
It isn't that hard to go from stock ROM to Xdauto, once you've read the guide(s) a couple of times(and perhaps asked some questions), AND do follow them, then it isn't that hard. I'm a noob in this field myself, I managed to do it, so can you [emoji108]
[Android Head-Units] m3co:
It is a different in the new unit... it does not have a easy way to get to the boot menu.
[Android Head-Units] Bokomaru:
That is not true at all actually, there just isn't an easy way to get back to the bootloader if you end up bricking the unit. You would have to disassemble the unit to do so.

If I ever have some free time I'll see about making it so an update.img will work to upgrade xdAuto from stock so people don't have to hook up USB and can just put the image on a USB device.

---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------

That's correct, audio from the radio, bluetooth, or any source not generated from the Android portion will not be affected by Viper
[Android Head-Units] zeroprobe:
My Carpad 2 works with Poweramp and Viper4Android.

In Poweramp you have enable Music Mix and disabled their equalizer also.

EDIT: Never tested the Radio side. Not that fussed as Radio quality is never great anyway.
[Android Head-Units] m3co:
Happy to know that, hope to see very soon a "how to..." manual in the wiki to install xdauto in the NR3001HH0 unit :D
[Android Head-Units] kwalsh24:
Just thought I'd chime in. I received a new main board for my unit... Photos attached.

The new board seems to have issues with the Android box mind you... The screen turns on black. So emailed summer to see what to do next. The original board works fine.

original board installed...

Replacement board...

Original board pulled.
[Android Head-Units] JanDK:
[emoji51]sorry/ I overlooked that it was the new model/unit, I thought it was the old one.
[Android Head-Units] Totoix:
Is there a way to re-locate context menu icon? Since I disabled navbar, I can't see the conext menu. Is it possible to make context menu available on the right corner of the status bar ? If so, how can I do that?
[Android Head-Units] disdigg:
USB upgrade would be great, but in the meantime I believe I can handle using the rkBatch tool. I have experience installing custom roms in other Android devices but I have no desire to open it up. To avoid bricking it, would should I avoid doing? What might brick it?

My biggest issue right now is that only 1gb of 32gb is available for app storage. Will xdAuto allow me to significantly increase the partition? I would like it all to appear as internal if possible. The 32gb of storage is the main reason I opted for the CarPad 3.

Thanks!
[Android Head-Units] easyguy:
Hi Guys,

Long time, so I'm bored and decided to upgrade to the newest xdAuto, is the latest xd incorporated the latest stock rom?

What are most people using xdauto or stock rom?
[Android Head-Units] zanix:
The xdAuto ROM will give you 3GB for /data (app installs). What I'm not sure of is if you will see the remaining 29GB as external sd.
[Android Head-Units] MrTSolar:
What I found is that having the system partition separate from the data is beneficial, as loading different ROMs doesn't wipe out your stored data (music, photos, videos, etc.). I agree that the 1 GB system partition is severely limited.
[Android Head-Units] IdleCuriosity:
Horizontal white line on wakeup from standby

I tried adding a diagnostic printout inside android_power_wakeUp and this method is not getting called until after I touch the screen. I can turn on the ignition and sit watching the horizontal white line indefinitely, but it is not until I touch the screen that android_power_wakeUp gets called and I see my message (running logcat from an adb shell). So if sending the wakeup message three times is needed to get rid of the horizontal white line then we have a problem!

I am running v41 on my NU3001 for what it is worth. I tried all versions from about v39 to v48 with no change. I also tried xdAuto versions 1.1.6c2 and 1.1.6c3xx.

For me the problem is 100% reproducible: I set the standby time to "Half Hour", turn off the ignition for about 15 seconds, turn the ignition back on, and I get the horizontal white line. I have never been able to resume from standby without needing to touch the screen.

I am happy to assist with testing possible solutions if anyone has any ideas...
[Android Head-Units] Bokomaru:
On the next xdAuto release there will be an option to select ITU Region 2 for North America which has the proper AM spacing.
[Android Head-Units] leonkernan:
I've long suspected it is a timing issue, but moving the code around never solved it. I originally saw it after adding the audio focus code for sleep/wake to bonovohandle.

I think it's more likely the sleep message (notifyMcuSleep) isn't always getting sent to the MCU at the right time. Possibly if Android is too busy when the sleep occurs.

Sending the messages three times is a change made in stock 1.1.9 (i think) onward, that's why I added it to xdAuto too.
[Android Head-Units] Totoix:
Hello,

I am using xdAuto1.1.16c2. Since I disabled the navbar, my radio app's lines and buttons seems disordered. I have edited, layout-sw600dp-v13/radio_player_layout.xml and tried numerous things. I want the fm,am, and other buttons below them, heart, save, and the blue buttons in their line to move 8-10 pixels downwards. I edited neccessary lines compiled and replaced the apk. But nothing changed.

Lately, I changed the background height to fixed (550dp) for background not to strech. But had no luck too with this operation.

What can you suggest?
[Android Head-Units] shomesomesho:
Hey guys. So I got my NR3001 installed and wired up but i'm having some problems understanding how to flash a recovery and xdAuto. I bought a USB type A to type A cable and have it plugged into the "usb hard disk" connection, which is what [MENTION=4173803]Bokomaru[/MENTION] said is the same as the mini-usb on the older units.

I started with trying to flash TWRP. I followed the instructions and went to the radxa website. I downloaded the RKAndroid tool and the TWRP .img file. I changed the OTG model to "Connected Devices" and that let my computer acknowledge the device. I am having a hard time getting into "loader mode." If I plug the usb cable into the computer with the unit powered on, I get this response:

And if I power off the device completely, I get this response:

The Wiki said ADB was preferable, so I tried that. But when I tried to push the img I got "failed to copy read-only file system." I checked online and that's from /system/ not being marked R/W. So I opened ES File Explorer and tried to turn on root explorer and got this response:

I thought these devices came rooted? What am I missing? :good:
[Android Head-Units] zeroprobe:
Use KingRoot and run it from your laptop. Click Root Again when prompted.

I've amended the rooting guide on the wiki to also include steps to replace KingRoot with SuperSU.

http://xdaforums.com/wiki/Newsmy_CarPad_NU3001#Rooting
[Android Head-Units] shomesomesho:
Doh! ok. thank you. I ran kingo root and then continued following the instructions on the wiki page. Downloaded the Kingo-to-SuperSU and ran the terminal commands. I uninstalled the kingo app but I still see SuperUser, in addition to SuperSU. Should I just leave SuperUser alone and just use SuperSU?
[Android Head-Units] zeroprobe:
uninstall SuperUser too. SuperSU should be the default one now though.
[Android Head-Units] shomesomesho:
I can't uninstall it. I assume because it's installed as a system app. is disabling it ok? My goal is to just get to get xdAuto loaded on here.
[Android Head-Units] zeroprobe:
Should be fine.
[Android Head-Units] shomesomesho:
Got Root explorer to turn on and changed system to R/W but I still cannot Push the recovery image. same error. Read only file system. I tried restarting and permissions stay applied.

Is my pathing not valid in Windows?
[Android Head-Units] zeroprobe:
Flashing things like recovery, Don't you have to click the Switch button first in rocktool?
[Android Head-Units] shomesomesho:
I thought doing what is in red was a separate thing that required no tools from Rock

Edit: I tried to use the rock tools but i'm not sure how to get into "Loader Mode"
[Android Head-Units] zeroprobe:
This may work also.

Copy the recovery.img to the device

Use that Terminal Emulator like I did

type su

type dd if=/sdcard/recovery.img of=/dev/block/platform/emmc/by-name/recovery bs=4096

But with rocktools, just clicking the switch button should put it into the mode where you can flash the recovery.
[Android Head-Units] shomesomesho:
I just tried manually copying the recovery image to the "external_sd" and was denied.
[Android Head-Units] zeroprobe:
I'm not near my unit at the moment but will confirm how I did it when I am.
[Android Head-Units] shomesomesho:
Thank you for your help. :good:

I got it! I copied it to sdcard instead of external_sd and changed the terminal command to reflect it. worked fine. weird. wonder why I can't access external_sd
[Android Head-Units] Zaphod-Beeblebrox:
Use RKBatchtool instead. You'll have to start with xdAuto1.1.6c.img (we didn't make an .img of c2). This is a full/clean wipe that'll set the partitions up along with TWRP recovery.

Once you have that booting, copy the 1.1.6.c2.zip file over to your internal storage and use TWRP to flash that. From then on, you can use TWRP on device to flash.
[Android Head-Units] shomesomesho:
I will try it right now. Thank you.
[Android Head-Units] Zaphod-Beeblebrox:
http://xdaforums.com/wiki/Newsmy_CarPad_NU3001#Update_via_Computer_with_RK_Batch_Tool
[Android Head-Units] shomesomesho:
Got up to the part where I hit "switch" the screen went black, the pink square went away but a green square never appeared. The headunit screen is on but just black.
[Android Head-Units] Zaphod-Beeblebrox:
I think the black screen is normal for bootloader mode. The fact that you didn't get a green square probably means you don't have the bootloader device driver installed. There are two drivers that have to be installed - ADB & Bootloader.
[Android Head-Units] shomesomesho:
/sigh ok. Where can I get that? I'm sorry to be failing so miserably. lol. Earlier when trying to use ADB, I installed "android studio." Am I even on the right track?
[Android Head-Units] leonkernan:
You're close, try installing the driver on this page: http://www.cnx-software.com/2013/11...install-rockchip-usb-drivers-in-windows-xp78/

RKDriverAssistant is what you are looking for.
[Android Head-Units] shomesomesho:
THANK YOU and [MENTION=2190016]Zaphod-Beeblebrox[/MENTION] so much! I just got it to flash. :good::good::good::good:
[Android Head-Units] zanix:
Wiki Updated

I just updated the wiki to include the CarPad III (NR Series) information.

I also renamed the page to just "Newsmy CarPad", removed most of the specific references to NU3001, and updated the device side bar. There is still some info left to put in like hardware specs and variation photos. I'm working on the variation photos and I'm sure we'll get to the hardware soon enough.

http://xdaforums.com/wiki/Newsmy_CarPad

All old links to the wiki should auto redirect since wikis are cool like that.
[Android Head-Units] IdleCuriosity:
Horizontal white line on wakeup from standby

Out of curiosity I tried flashing the latest stock ROM (1.3.0) and the problem was resolved.

Then I installed xdAuto 1.1.6c3xx again, and confirmed that I still got the horizontal line every time I resumed.

Finally I tried installing just boot.img from the stock 1.3.0 ROM, so that I would be running the stock 1.3.0 kernel but with everything else xdAuto. Now I can resume perfectly! I have tried five or six times, with a perfect success rate.

So the problem would appear to be inside the kernel, and is something that Newsmy have fixed recently.

Is there any drawback to running a hybrid setup with the stock Newsmy boot image combined with everything else xdAuto?
[Android Head-Units] zeroprobe:
I downloaded the stock 1.3.0 and it seems UserData is 2.5gig. I'm not sure what version you are running initially on the CarPad3?

I've uploaded it and added to the wiki.

http://xdaforums.com/wiki/Newsmy_CarPad#NR3001_Downloads
[Android Head-Units] Totoix:
No answer? How should I edit res/layout-sw600dp-v13/radio_player_layout.xml so that the lines and buttos will not be disordered? If I turn on the navbar, the interface seems ok but I don't want the navbar. Any suggestion ???
[Android Head-Units] Bokomaru:
There is no external SD on Carpad3
[Android Head-Units] shomesomesho:
Well. I knew that, which makes me feel even more dumb. Thanks. Lol.
[Android Head-Units] Dream Reality Syndrome:
Is there a way to extract this from the downloaded image? I'm thinking I can fix my issues with standby by replacing some files in XDAuto with stuff from the original rom
[Android Head-Units] IdleCuriosity:
Extracting files from .img

Following the stock ROM link on the XDA Newsmy CarPad wiki, I started with a file named AD3188_CarPad_KK4.4.2_1.3.0_1024x600_update_2gbData.7z

I uncompressed this (at the Linux shell prompt) using the command:

7z x AD3188_CarPad_KK4.4.2_1.3.0_1024x600_update_2gbData.7z

giving me the file CarPad-II_update_v1.3.0.img which I renamed to just plain update.img:

mv CarPad-II_update_v1.3.0.img update.img

Next I downloaded some tools from the xdAuto Nu3001/rockdev git repository (sorry no links allowed for me yet):

afptool

rkImageMaker

unpack.sh
​

I then unpacked using the command:

./unpack.sh

which unpacked everything into a subdirectory called output. I found boot.img at:

output/Image/boot.img

​

Hope this helps!
[Android Head-Units] Totoix:
Please I still need this help. Radio application is designed for a screen which has navbar at the bottom. Please help me change the design of the layout so that the lines and buttons seems in order.
[Android Head-Units] bockywocky:
Incredible how fast this topic grows. I've been away for a few months and 200 posts have been added.

What is the latest MCU and best stable image today for my carpad 2?

Tomorow I gonna order another Android system with the same specs for my other car Peugeot 206

this one: http://www.witson.com/en/displayproduct.html?proID=102508072

WITSON: does anyone have experience with this supplier?

Regards,

Bocky Wocky
[Android Head-Units] Zaphod-Beeblebrox:
Bonovo had the great idea of explicitly specifying all the margins and offsets making that layout VERY SPECIFIC to the screen size. You'll have to undertake the process of revising every layout/object definition.

Or even better, you could completely re-do the layout and try to do a more generic/weighted layout that scales better for various screen/DPI settings.

Either way it will be time consuming. You might even be better off to pull the source from our github and work with it from within Android Studio, you'll at least get a more UI friendly environment to work with.

Once you get it done, feel free to issue a pull request. We'd love to see it/share with others.
[Android Head-Units] Totoix:
Thank you very much answering about this issue. I am willing to come up with at least the required changes for a full screen view.

I have edited, res/layout-sw600dp-v13/radio_player_layout.xml, compiled it and obtained an apk. I replaced the apk in apps folder with this one. But nothing changed. I worked in android studio too. But I could not manage to move buttons. It seems as I move the buttons in android studio interface(android studio tools show no problem in the interface by the way), but after deploying to the head unit, nothing seems to change.

What may I be doing wrong here? I only edited res/layout-sw600dp-v13/radio_player_layout.xml. I changed top margins of some buttons. There are also res/layout-sw480dp-v13 and res/layout-sw340dp-v13 directories. Do I need to change radio_player_layout.xml in these directories too?
[Android Head-Units] Zaphod-Beeblebrox:
IIRC the radio app lives in /system/apps. Make sure you are replacing the correct location.

second is figuring out which layout is actually being used in your environment. Depending on your DPI, etc: http://developer.android.com/guide/practices/screens_support.html This is along read, but will help you understand what each of those folders mean, and how android chooses which one to display.

If you are truly willing to re-design that layout without hard margins (using container layouts (linear, relative, etc)) with well designed gravity attributes should make it possible to redo that layout so that it works with ANY screen size/dpi, then I would suggest to delete *ALL* of the sub-layouts and create a new on in /res/layout ... by doing this, it will force Android to pick that one regardless of attributes.

In fact, even if it's not possible to get a good layout using gravity, it would be possible (and preferable) to take out all of the static number/dimensions and replace them with [MENTION=1228572]references[/MENTION] to dimensions stored within the layout. You could then create res/dimen folders for each of the screen widths and adjust as necessary.
[Android Head-Units] spoks:
12V adapter

I would not recommend it. First one I received, was already DOA - unsoldered and broken wires, broken paths on circuit plate. Second one seemed to work until ... bloved up. Naturally. I have to paint wall in that place now.

I doubt also it can handle 2A as stated in description.
[Android Head-Units] Khael:
Sorry man,

i have a nu5261 HU with and old firmware.

I'd like to update to a new firmware and MCU.

Can i use last 1.3.0 firmware?

Can i use the 2gb data partition? (with 1gb i can't install a lot of app)?

AD3188_CarPad_KK4.4.2_1.3.0_1024x600_update_2gbData.7z

is this the right file?

thanks in advance
[Android Head-Units] Eddy TheHell:
Hi, guys I need some help.

I have the nu9001 unit, kia k3 version of the nu3001.

Mine works with stock 1.1.3 rom and v35 mcu.

I want to update both but I found 2 version of the 1.3 rom, one with ( 2 gb data partition ).

Which one should I use?! Mine is 1 gb data partition which is my biggest problem and why I'm updating it.
[Android Head-Units] Dream Reality Syndrome:
I get stuck when I enter the command to unpack in terminal. I get this message "bash: ./unpack.sh: Permission denied"

*edit:

I finally got it to work. Had to move everything to my local hard drive. Thanks for the terminal commands! Always good to practice
[Android Head-Units] IdleCuriosity:
You need to make the script executable:

chmod +x unpack.sh

You may also need to do the same for rkImageMaker and afptool (mine were downloaded as part of a git sync and so had their permissions already set; I gather downloading individual files via the web interface doesn't preserve permissions...)
[Android Head-Units] Surgent:
I might have a go at this over the weekend too. The current implementation ****s me just enough to want to do something about it. cheers for the instructions
[Android Head-Units] DiGi91:
Still running the stock ROM and it has been smooth sailing, wondering what I can do to "jazz it up" a little bit. I have been looking into some frontends and tried a few but nothing to my liking. At this point I'm trying to make this thing more "car friendly" and closer to an actual head unit than a tablet. Still using Poweramp and it's been alright but I am always up to trying out other options.

Music: Poweramp

Nav: CoPilot

That's about all I use this thing for and I do miss XDAuto BUT it just never liked me or my headunit lol.

Any suggestions or feedback would be appreciated.
[Android Head-Units] zeroprobe:
Have you tried Automate Beta?
[Android Head-Units] Surgent:
+1

Get it here https://plus.google.com/communities/102908788212710276577
[Android Head-Units] jkchr1s:
So the stock rom fully resolved your audio skips? Are you running viper with the stock rom as well?