yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] JrOmnia:
JrOmnia, your Jetta doesn't have resistive SWCs and the VW-specific version of the Newsmy you bought doesn't need them. it should pick everything up from the car's CANbus using the adapter that's built in. Look around in your settings there should be a way to enable it.

Thanks alaninsitges but just to be sure here the setting you're referring to is the device settings and not the car settings right?

Bcoz I did look at the settings section in the device I can't recall any to do with SWC but I'll relook thoroughly once more.

Do you know what can be done to fix the flickering screen problem?

Thanks again
[Android Head-Units] Tuatara:
ROM Feedback ...

Time for some ROM feedback ...

First, is the dalvik memory allocation suitable for 1G versions of the android box? Anyone with a 1G experiencing any slow-down or memory issues? I'm hoping that the cache size does not adversely affect performance on lower-memory devices. If this is the case, then an updated build.prop would be in order.

Secondly, I'm now actively using the ROM (installing and configuring apps myself), and I'm seeing an issue I didn't have in any of my earlier testing.

Is anyone experiencing display flashing, black unpainted sections, or update blocks while using the ROM?

I may have been too aggressive with the graphics caching in the build.prop.

Please let me know if you're seeing any issues.

Relevant build.prop settings:

ro.hwui.texture_cache_size=72
ro.hwui.layer_cache_size=48
ro.hwui.path_cache_size=16
ro.hwui.shape_cache_size=4
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=6
ro.hwui.texture_cache_flush_rate=0.4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
ro.hwui.disable_scissor_opt=true

ROM builders - If you're experiencing issues, you can try changing (or just deleting!) these lines from your build.prop and let me know if it fixes it for you.

Default Settings are available here: https://source.android.com/devices/tech/debug/tuning.html

I'm presently trying the following less aggressive settings:

ro.hwui.disable_scissor_opt=false
ro.hwui.texture_cache_size=48
ro.hwui.layer_cache_size=32
ro.hwui.gradient_cache_size=1
ro.hwui.patch_cache_size=128
ro.hwui.path_cache_size=8
ro.hwui.shape_cache_size=2
ro.hwui.drop_shadow_cache_size=4
ro.hwui.buffer_cache_size=4
ro.hwui.texture_cache_flush_rate=0.5
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024

Please provide feedback ... let's get this ROM right! :D
[Android Head-Units] deeznutz1977:
I will let you know tomorrow I need to go to radio shack to pick up the adapter. BTW the high five dude thanks srsly. Expect a donation when I get my next check ( I get paid on the 1st and 15th
[Android Head-Units] usafle:
I installed it today as I was running out the door. Plugged it in and started to configure everything I had before. Yes I even had to go through the horrendous task of changing the time zone. Ugh. Lol

Quick things:

Busy Box install fails. Possibly a left over from my previous installs? Not sure if the device was really wiped using your ROM +Rk batch tool? Busy Box detected an old version installed when I first download and ran it.

Tried to update Viper to the newest version that was released a few days ago. Not sure if you baked it in? Regardless, when trying to update, it crashes the installer and Viper.

Viper by default is not activated and may cause confusion. Its not the default music effect nor was it switched "on". Not sure if that was by design or not but some may be under assumption its enabled?

What Viper driver did you bake in? Super audio quality..etc?

Other then that I didn't notice anything else. I'm just super excited to have something like this and these are only minor issues. My ROOT works and we have CWM. I'm dancing a jig!!!!!! Lol
[Android Head-Units] horn34:
The host USB port is the mini USB port. There's only one mini USB port on it. It sucks that you're getting video issues, maybe try a higher amp USB power source or find a power supply that works for the power input.
[Android Head-Units] Tuatara:
(I love useful feedback)

Arrgh. I feel your pain. Every time, without fail, I need to scroll all-the-way-down-to-the-end-of-the-list myself.

And then I need to change it from "Month / Day / Year", and "Minute : Hour : Second" to something usable. It's a miracle when I don't need to. :)

Busybox is pre-installed in the ROM. Are you updating busybox with another version from the playstore? I haven't tried doing this, as I've explicitly retained the version in the stock ROM.

Which version of busybox are you attempting to install?

The ViPER4Android version baked in is 2.3.4.0. This was the one released February 13 - reference http://vipersaudio.com/blog/?page_id=31

I have also contacted Jasper and have received his approval for the ROM inclusion.

If it crashes the installer, it may be that ViPER4Android should NOT be specified as a system app. Therefore, it may also need to be moved to the /system/preinstall directory to permit updates.

Putting APKs into the /system/app folder was my MAJOR error when building the first ROM for XDA.

This was done on purpose. I was planning to write up (or maybe someone else can?) all the information about ViPER4Android configuration into the Wiki, as given in this thread. There were a few people who had issues installing ViPER4Android, and it does make such a difference that I felt it should be included properly and optionally used/enabled as desired.

My feeling is - should it be pre-enabled, and if so - what Impulse Response should be used? What room size? Reverberation? Loudness? Who is to say you'd like my setup?

If it is available, pre-installed, with a large (recommended) series of Impulse Responses available ... a Wiki entry explaining how to use and configure it would let everyone adjust it to their liking.

(Background: I've designed and built noise-cancelling headphones, and have 2 patents in Acoustic technologies - virtual acoustics, and bass enhancement. People are very (very!) picky about their music and how it sounds!).

Yes. NEON_HQ library is baked in. I mentioned the version and that High Quality was used in the original ROM post/docs.

Yup! Fully Rooted, and ClockworkMod recovery were the two biggest issues I needed to address. Everything else I've been working on is "window dressing", and I will need feedback on - to see if it's a "good thing", "bad thing", or something which should come pre-configured or re-configured in some way.

Enjoy Root and ClockworkMod. It makes such a difference!
[Android Head-Units] Dream Reality Syndrome:
People are picky about their music and the way it sounds, myself included (self proclaimed amateur audiophile) so I appreciate that you would leave Viper optionally enabled rather than pre-enabled. Not everyone will have a need for it. For instance, I plan on routing the sound signal out the android unit into my Pioneer unit for my sound processing needs
[Android Head-Units] zanix:
I added your ROM to the wiki and duplicated your post there.

http://xdaforums.com/wiki/Newsmy_CarPad_NU3001#Tuatara_Carpad_II_ROM_-_ClockworkMod_Recovery

On another note, we may need to start making subpages on the wiki, it's getting quite large.

Hey alaninsitges, could you do a quick update on the first post? Mainly to note that the wiki has most of the info now.

Tuatara's instructions specified that it should be done with the flash tool, not via SD card.
[Android Head-Units] horn34:
I'm using this Sony, works fine.

http://www.amazon.com/Sony-Class-Memory-SF64UY-TQMN/dp/B00B7ID9CU
[Android Head-Units] spoks:
SD card

It is "amazing"! Sony cards works, Samsung - does not. How does it comes?

If only you have reformatted it from original state to FAT. Then you should mention it ;)
[Android Head-Units] alex0815:
Softbuttons with "no softbuttons" rom after update from 1.1.3

Hi,

I updated from Renedis 1.1.3 no-softbuttons to renedis 1.1.4 no-softbuttons, everything seemed to have worked just fine, but now I do have softbuttons. Reinstalling 1.1.4 didn't help either.

regards.

Alex

PS: Great work on the ROM in total!
[Android Head-Units] bockywocky:
Yes, know issue in this Renedis version.

Do a search in the wiki how to remove the softbuttons in the build.prop
[Android Head-Units] blinger:
You are not using the android box out of the headunit are you? Update settings app needs to connect to the headunit.

[MENTION=260727]Tuatara[/MENTION]

Thank you so much for the rom! Sorry if i missed this but would it be safe updating your rom from a stock rom via sd card? Ive reverted back to mcu v31 because the car speed auto volume seems to work better in that version.
[Android Head-Units] x5nder:
LOL. My Huawei E220 went from being recognized slowly, to not being recognized at all under Android after this command. Is there an AT-command to undo the 'modem-only' mode? :)
[Android Head-Units] Khael:
uploading files.zip :)
[Android Head-Units] usafle:
Since I'm writing my reply on a tablet I can't breakdown all your responses in quotes. Sorry. Ill just have to reply in order. My replys won't be as pretty as yours. Lol.

Time Zone:

I almost didn't install this ROM because of having to manually change to my own time zone. Don't let it happen again ;)

BusyBox:

On first boot I did not have a Busybox icon in my app drawer. When I went to the Play store it was listed as installable. So, I installed the apk. Upon opening the BB app I noticed that it said I already had it installed. I forget what version was still there. BB told me a newer version was available so I tried to update it and that's when the install failed. I'll not sure if the previous BB was installed to some sort of custom location or the default? Perhaps that's why it failed? Either that or, I'm just an idiot which could be a good possibility.

Viper stuff:

I wouldn't recommended installing it as a system app. Reading over at the Viper XDA thread it seems that it causes nothing but issues and makes it difficult to update if a newer version comes out before a ROM is released with the newer version.

I agree with your decision on NOT to have it enabled by default. We definitely need someone to write up instructions on how to activate and enable. My previous write up is poorly written and I'm aware of that. I just needed to get the info out there as quick as I could and screenshots and eloquently writting on a mobile device doesn't work well at all. I take the blame for that 100%.

My concern was that a new user, seeing that Viper is baked into the ROM would think that its enabled already. That's what I was trying to say.

NEON_HQ is "Super Audio Quality" or just high quality? In the past I always selected the Super audio driver since no need to worry about a battery drain in this device.

Please feel free to tell me if I'm being an a$$ with the replies. I don't want to be the one responsible for pissing you off and then you leave and stop coding. Lol!!!!!

---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------

I can answer for him (I hope): you have to use RKBatch tool to install his ROM. You can't upgrade from the SD as it re writes partitions on the device.
[Android Head-Units] Khael:
hello guys,

unfortunately my 3g pen doesn't works.

It's an Huawei e1820. I use it on my dd-wrt router but on this unit doesn't works.

1st of all i cant save apn configuration (i complete all but when i save it doesn't appera on profile).

and if i try to search network doesn't works.

I connected to the usb otg, is it right?

thanks :)
[Android Head-Units] Khael:
hi tuatara,

thanks for your job; i don't know why but try it on pc there was the pin...tomorrow i'll try again.

i have 2 question:

1) is possibile to receive sms with this key?

2) is possibile to check signal strength?

In the end, i don't understand the supply problem (i make same difficult to understand some post, my english isn't so good): now my 5216 unit give power to androix box trough fw cable.

I'd like to use the usb port fort the e1820 and usb otg for microphone.

I use ad 32gb sdcard.

Do u think thet power supply isn't enough?

i should use a powered usb hub or what else?

thanks in advance

Khael
[Android Head-Units] usafle:
Just got into my car after letting it sit for two days. Device is on but I have no audio. Nothing plays. Pandora, power amp, Waze not even in system setting and adjusting the sliders. I didn't do anything but park the car!

I've rebooted the device a few times. Still no audio. What. The. Hell.
[Android Head-Units] Khael:
1 times i had same problem (after a bluetooth call).

Do u try unplagging the firewire cable to android box?
[Android Head-Units] nestortoledo:
I have same problem too with old mcu/firm, just disable bluetooth and see if sound come back.
[Android Head-Units] usafle:
Unplugged the unit with car ignition off. As soon as i plugged it back in, power light came back on. Thought it wasn't supposed to do that? Shouldn't it stay off until i turn ignition switch back on?

Switch my replied around. Don't know what happened when I tried to multi quote.

Closed Bluetooth, no sound. Left it closed, reboot, no sound.

If I crank volume up, I can hear the speaker whine. So don't think it's my amplifier that died on me?
[Android Head-Units] ker2gsr:
I had the same issue before but not for having it off for 2 days just a random event I fixed it by reinstalling the mcu
[Android Head-Units] usafle:
**************Disregard. Found it.****************

Can't search on this Tapatalk app.

Can anyone provide a

Non FTP link to current MCU?

TIA!
[Android Head-Units] horn34:
Hey, I appreciate all the work you've done and your advice, but you realize the NU3001's android unit is basically a large Android stick? I don't know if you own any, but they pretty much all run off the power supplied to the micro or mini USB ports. While I see where you're coming from, I don't feel I'm stressing the OTG port, as all my peripherals are plugged into a powered USB hub, so the NU3001s android box isn't having to serve more than 500mA out of any USB port.
[Android Head-Units] horn34:
MCU v34

https://mega.co.nz/#!GhoVxCaS!Y_XPuVBIJeuvAkMwNAW1UlaNCd4cnNEzIhIU5JYI8us

Kingo Root

https://mega.co.nz/#!GpZgFLDS!NosoEvQSeiASc2UEjFrzUmuZFraaCIJ3prek3uvUVug

Rockchip Batch Tool and drivers

https://mega.co.nz/#!H4YS3IIQ!QORGfJCKuQpMCQ87x2sIY82lLQb1K0BVTB506JdNGUY
[Android Head-Units] Tuatara:
More power ...

Very true, and very smart of you. With a POWERED USB Hub - you're all good, and will not be exceeding the 500mA limit on the port. The Android "stick" will use around 300mA (max), leaving the remainder available. Since you're not using any additional power through USB (i.e. hooking up a 3G stick, keyboard, hard drive, flash drive, camera, microphone, and OBD II adapter through an unpowered USB hub) ... no worries.

My warning is directed at those who think they can power the android box through USB, and THEN hook up a 3G stick on the OTG port, and physical keyboard & mouse or something else on the Host port. With a powered USB hub - you will always be fine.
[Android Head-Units] deeznutz1977:
Anyone having driver issues http://blog.geekbuying.com/index.ph...drivers-auto-installation-tool-download-here/
[Android Head-Units] wacko37:
Thanks mate... this installs the drivers perfectly but sadly the batchtool still does not recognize it as connected.

This seems to be related to those using Windows 64bit. I'm using 8.1 64 bit, but have to use 32 bit when using the batchtool.

Thanks all the same ?
[Android Head-Units] -=Jeff=-:
I can't remember if I saw it somewhere in this thread, but how good the does the microphone that comes with the unit work for phone calls? I know it will not work for Google Now on android but is the Microphone any good for the purpose intended? if not, what is suggested?
[Android Head-Units] usafle:
I will have to check the Busybox app once I get back into the car later today and sort out my "no audio" issues.

Since I didn't see an actual APP icon for BusyBox, I assumed it wasn't installed and went to the play store to install it. When I opened the APP it told me BusyBox was already installed but I *think* there was a newer version of the binary available for install. So, I tried to update it and that's when the install failed.

I've not experienced any issues with your "aggressive" HWUI graphics optimization. Everything appears normal. Unless that is the reason I no longer have audio on the device? Then it's an issue. LOL

What, exactly, should I be looking for - graphics wise that would be an "issue"? Everything appears normal on my unit.

---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------

Just an FYI and not sure if it's your particular problem, but I had "Front" case mounted USB ports on my tower. Plugging the unit into those resulted it in not being detected. It was only until I plugged the unit into the rear USB ports did the unit get detected. Not sure if you are running a laptop or a full tower?

I'm using Windows 7 (because 8 is garbage LoL) and it's also 64bit.
[Android Head-Units] usafle:
Audio solution fixed

You all were correct. I had to downgrade the MCU to v31 and then I had audio. Brought it back up to current version and now I have audio.

Strange as I have ZERO idea how I lost audio....

Thank you all that replied and offered suggestions
[Android Head-Units] janla:
great job! minor issues

Hello Tuatara & all !

I have my NU5261S on your ROM now :victory:.

Fanfares sounds still in my had. Can you hear this also?

my minor issues:

- still no working 3G dongle.

Huawei E173 set for modem only mode using topnetinfo app (At commands based)

it recognizes modem and carrier and allow me to put sim pin code but then immediately off. Cellular data icon disapears from status bar and no connection anymore (however carrier detection still works). Can it be related to not enough power from usbs? My AB is powered well - by 12v/2A supply, but I wonder whether there is actually expected 500mA on usb output?

- compatibility for some apps - I tried to install blackberry blend app (one in a class). First, Google playstore says that my device is not compatible. I forced side installation, but then app itself says that it need android 4.4 or newer, and display at last 7". This is strange as accrding to details of Google Playstore Fix applied, it should show our devices as Nexus 7.

- bootanimation. I changed it with FactoryTool, but it seems that my animation is too short and is played only once. In result I have black screen for the most of the booting sequence. Is there any trick to force loop this animation?

- Xposed framework - no problem with installation, but cannot activate any module. Checkbox is not checkable, and only properties/uninstall options are in the menu. I was trying to switch off navbar this way but finally managed this by edition of build.prop together with "All in one gestures" app.

- Viper FX - never used it before and completely have no idea what should I check in the app settings. I have only TV hdmi connected at the moment so can not approach by try and mistake. I will try latter, but a short in-car how-to would be very helpful.
[Android Head-Units] wacko37:
Thanks for replying, yes using laptop and also win8 is sh$$ looking forward to free upgrade to win 10, tried all different usb ports, so i guessing this is a win8 problem.

I have installed win 7 32 bit on a thumb drive and all work as expected.
[Android Head-Units] kwalsh24:
Sorry, not the otg port its the other normal size port that's the only one that powers my unit, the mini doesn't do anything on its own.

Ill just try to hunt down a power adapter for it. Or at least a tip that plugs into the box and make my own from the 12v adapter I have which has a incorrect size plug.
[Android Head-Units] Firewater Burns:
Unfortunately, not much feedback to give on a 2g unit. It has been 100% stable, and I have yet to notice a display issue under light use. I have had it running for 20+ hours, in a couple of ~10 hour block intervals and some here or there time on the bench. It was mostly playing Pandora or Spotify while researching. I am waiting on a few hardware items and trying to figure out what I wish to load on it.
[Android Head-Units] Ekki_221:
There is no(!!) need to reflash the MCU to solve the Mute issue. It just helps to start the MCU program and Switch the mute Options on / off. Then a reset and Sound is back on again.

Regards,

Ekki
[Android Head-Units] priusfan:
Bonjour,

I have 1Gb unit.

I updated yesterday the MCU and made a restore with Tuatara's image.

Everything went smoothly.

In the beginning, Playstore was not working...

So I installed manually the apk I use (N7player, waze and canion) and everything worked as before.

This morning, the playstore is also working.

Thank You again....
[Android Head-Units] db2boy:
Android box power down time and full shutdown

Finally installed mine yesterday, all went great with install including SWC and unit sounds better than OEM factory radio did. I had a couple of questions, I'm using Tuataras latest ROM and MCU 34:-

1) Where are the settings for how long the android box stays on before shutting down, I know I saw them previously but can't locate them anymore?

2) Is there a way to shut down the android box cleanly for when I want to remove it from the car? Tuataras ROM has a reboot/shutdown app but the shutdown option reboots and doesn't shutdown.

3) I saw comments on adding Viper instructions to the wiki, but which profile (phone, bluetooth, etc) allows the HU to take advantage of Viper?

Cheers!
[Android Head-Units] welshblob:
I don't believe it has been included in an official release yet. They were in a specific test build found on the usual download site and it was in the update MCU app. Also someone looked at MCU 34 and says it appears to have the functions to make use of these settings.

Not that I have found so I'd be interested in that too.

Someone did a good write up on Viper config several pages back before Tuatara posted his rom I believe.
[Android Head-Units] usafle:
I'm going to attempt to take my PC out of its boxes on my days off starting tomorrow and write up a "nicer" instructional...complete with, hopefully, screenshots on the Viper install.

I've never written into the Wiki before so I'll probably just write the post in the thread and someone can either post it into the Wiki or just link it.
[Android Head-Units] blacklistedcard:
CWM booted just fine. The only touch key that works is the power button. Tapping on the screen I get no response. Plus the volume buttons did not move the selected option. I'll try a keyboard next.

---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------

Now we need to bake some new kernels. Noop, performance, Westwood and USB audio enabled.
[Android Head-Units] spoks:
No sound on unit.

There was some discussions before about muted state. Like this. It's more likely as you said - some values (cached state, temp or whatever) must be cleared or reseted. MCU reflash is just one of workarounds.
[Android Head-Units] alaninsitges:
This isn't exactly correct; the line outs on the Newsmy unit are horribly noisy (reported by myself and at least one other owner), I'm guessing because of a lack of proper shielding inside the HU. I'm using a USB DAC on the host port through an unpowered hub and it works and sounds great. I don't think there's a need to add the USB stuff they hacked together for the N7 car ROM.