yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] easyguy:
So I rushed home from work to install the HU. One of the easiest install that I had to do. I made one wrong assumption though. When I plugged everything in, and started the car, I saw nothing on the screen. I was thinking to myself, damn I must have mixed up some cables. Wrong@! After replugging everything back in I thought to myself, let see what will happen when I plug in the android brain...guess what, the screen came alive!!!

The unit is beautiful and smooth!!! I'm so glad I waited and ordered this HU, this beat my expectation. I'm glad I didnt buy the AN-21 or the HUiFei units. I snapped a few pictures, but this weekend I will do a full video review. Anyone noticed that after you turn off the car and take out the keys, the android brain still had this blue light on? I hope I can start my car tomorrow. LOL

Bare in mind this is at night when I'm done with everything.

[IMG="nu3001"]http://s28.postimg.org/svchqn6hp/20141028_202614.jpg[/IMG]

My area is not the best so I bought a fake face plate, it works well. Ghetto style!

[IMG="faceplate on NU3001"]http://s14.postimg.org/qdren0h8h/20141028_202456.jpg[/IMG]
[Android Head-Units] renedis:
- CWM backup completed succesfully after flashing the recovery.img to the right partition with RKDevelopTool om my debloated 1.1.4 ROM.

- Flashed your ROM and run AnTuTU benchmark.

- CWM restore completed.

Got my settings, bootscreens etc all back. Partition size is still set to your settings (3GB apps, 4/5GB internal_sd).

AnTuTU benchmark (v5.6.1):

25232

I noticed the following:

- I did not got any question from SuperSU after flashing your ROM.

- Newsmy upgraded from boot version 2.10 to version 2.15 when they released 1.1.4 official. How come that your 1.1.4 version has boot version 2.10.

- MCU app is called different in your version.
[Android Head-Units] :
Webcam

so far i tested c270 c525 and both work just fine with the radio haven't came across any apps that don't recognize the camera just make sure you plugged in camera before you turn on radio
[Android Head-Units] Khael:
Daily update:

on VW, the illuminated cable shouldn't be connected. Without this connection illumination will work correctly!

Today after 3hrs i mount my back camera but there is an electrical interference and doesen't works :/ anyway isn't an issue of the HE!

TomTom Go is very beautiful, very nice app with a very good looks!

Today i also connect radio but without RDS and regional mode is useless

i have 2 question:

1) is possibile to hide top bar android?

2) still have problem with modem huawei. correctly sect as modem only doesn't works. an user told that i can use sms and can watch singla strength!

Is it true?
[Android Head-Units] Tuatara:
Ok ... I've downloaded the APK. Hopefully I'll find some time soon to test and see if I can resolve the issue(s).

I'll see what I've missed in making the Play Store think the Carpad is a Nexus 7 ... I thought I had that working.
[Android Head-Units] Khael:
I userd and rns510 after to buy this HE.

Maybe the biggest problem is that there is no RDS and regional mode, but reception isn't poor! Maybe at least on rns level!
[Android Head-Units] Tuatara:
Cheers. I've now downloaded them both, and will check the differences in each and see what has been updated/changed between 1.1.2->1.1.3->1.1.4 within the versions.

---------- Post added at 11:30 AM ---------- Previous post was at 11:18 AM ----------

You can, but I don't believe that you will get the benefit of the new partition layout, or if the incorrect partition information & loader change will affect the device operation. You can try it, and see if it works. Worst case, you will need to to the recommended full restore. Absolute worst case, you will need to put it into bootloader mode (gently press in the little silver pin-button using a paperclip until you feel a click, and power on the android box), and do a full restore from there (it will be a black/blank screen, but the RKBatchTool will show a green square). You can't brick this device, but I'd recommend the proper route for the first update.

Also, if you wish to retain all of your current settings, I'd recommend flashing the ClockworkMod recovery partition separately, doing a backupusing CWM, flashing the full ROM using restore, and then restoring using CWM from backup. Both toologic and renedis have had success using the "dd" method to flash the recovery partition only, and successfully restored from backup. (much happiness)

---------- Post added at 11:36 AM ---------- Previous post was at 11:30 AM ----------

I've seen that the FTDI, Prolific, and SiliconLabs chipsets are generally supported in Android, but I haven't checked them specifically in our ROM (can't check everything). I just know that the FTDI chipset driver is definitely available for all modern ROMs, so I'm sticking with that for my device(s).

You shouldn't need to use the Mini USB OTG port for a USB OBD adapter. The Host port should work just fine, and is what I am using through a powered hub. We should possibly start a list of all the USB Host device controllers, and OBD devices which are known working in the Wiki.
[Android Head-Units] :
i can't install from pc my surface pro 3 doesn't recognize the device. i tried everything possible, even had another member try for me to no avail. so if i do do sd card install and doesn't work i cant fix radio. ugh this blows i really wanted to try this new rom
[Android Head-Units] Tuatara:
The radio audio does not go through the android device. It is mixed in the headunit (which means ViPER can not be used on it).

The radio control is done through the (virtual) serial port device on android, which communicates with the MCU.

RDS information is very, very slow. The MCU could easily provide all of this data over the serial port connection without issue.

The serial port is effectively just a "command and control" link. Very little information actually travels across there. The HDMI link is taking up the largest portion of the bandwidth, along with the audio from android. The rest is completely negligible. The android box sends commands like: "Set radio on", "Set station to FM 91.0", "Set input to AV In", etc. RDS coming back the other way would be like "[Station] WKRP Cincinatti", "[Song] Now Playing: American Pie by Don McLean" ... and would update about once every 5 seconds or so (at most).

Wifi for me is fine within the house, and out in the driveway - but I've got a WiFi running DD-WRT, and have boosted the power/range significantly.

The WiFi (driver and antenna) is inside the Android Box, and is (from memory of the tear-down photos) a small PCB trace antenna mounted/stuck to the case lid, and is combined with the android bluetooth antenna (just like in a laptop). They're never really good to begin with. I may take my android box apart to see what kind of antenna is being used and/or if there is a (reasonably easy) hardware modification which can be made to use a better quality (external) antenna. If it has standard connectors inside, then a cable could be brought external, and a WiFi external antenna mounted/placed in a better location in the car (like for GPS). If I do this, I'll take photos of the modification, and provide details. Not sure if I will though, as I'm going to use a 3G stick ... but having a real "war driver" might be fun to have. :D

---------- Post added at 11:55 AM ---------- Previous post was at 11:51 AM ----------

Hang on a bit ... I'm frustrated at work and am taking a break. I'll see if I can make you a ROM which has the standard partition layout, so an upgrade would be doable. This would be untested, but I'm very confident I'll get it right. Watch this space! :)
[Android Head-Units] :
really! thank you so much i really appreciate it
[Android Head-Units] Zaphod-Beeblebrox:
We actually already have a full AOSP build/source. Renedis has it posted on his FTP. the first 'custom' rom we had for this device from Reddotnet13 was 1.0.9 fully compiled from source. The AOKP build that I was working on was not tripped up by the Bonovo/MCU stuff (the changes Bonovo made are actually pretty easy to find in the source, and not nearly as extensive as one would think). My problems were trying to integrate the RK SDK into a build tree that's compatible with AOKP/CM's build system. This is where I have little to no experience in device bring up. And the more I learned, and the more I saw in regards to the RK system, the more I began to realize, their device tree's do things that Android Dev SHOULD NOT DO. In that I mean that they made significant changes to the frameworks and the build/core to make their stuff work, rather than keeping as much as possible contained in the device and vendor trees.

While this is workable for a single device build, it makes integrating back into a multi-device ecosystem like AOKP or CM a nightmare. However, I was very close. The manifest in my github will make a bootable version of AOKP with a few minor manual tweaks. But I never got the WiFi/Bluetooth and EMMC drivers worked out properly.

That's not to say that just using the 1.0.9 source we have is a bad thing. I just wanted a few AOKP features built in (NavBar/StatusBar mods I wrote, along with immersive mode, the theme engine, etc). Most of these things can be replicated with Xposed and Gravity Box (which is what I'm doing on my unit now), it just takes longer to set up, and isn't quite as flexible as AOKP's system.

And we don't need to write custom Bonovo apps. We have the source for them as of 1.0.9. They are posted on my github as well. All the 'reverse engineering' you might needs it contained within that source. What we need to discover is what they've added to the MCU since 1.0.9 and how to tap into it. We can then modify and re-purpose the existing apps.

When I mentioned to you in a PM about adding audio ducking to the radio, I might not have expressed just how easy it would be to do. KK already has an audio 'focus' system in place for apps to signal each other on audio intentions. I just need to add a few sub routines to properly take audio focus, and to handle volume ducking with KK notifies me that another source has requested short term focus. We could even make the radio auto quit when another app (media player) requests permanent focus. No more double music playing, etc...
[Android Head-Units] renedis:
Windows 8 and/or USB3 right?

Please make sure the drivers are installed on the correct way.

Then. In the RKBatchtool folder you have the file named "config.ini".

Open it and search for "SUPPORTLOWUSB="

Change to: "SUPPORTLOWUSB=TRUE"

Open RKBatchTool after that and your device now gets recognized in the application!

---------- Post added at 12:57 AM ---------- Previous post was at 12:50 AM ----------

Having CWM recovery is great :) Makes testing a lot easier.

I'm 100% sure that I saw boot 2.10. But when I decompiled your rom and I see 2.15 too.

MCU function stays the same, so no biggy about that. It seems that it used to called "MCU" and now "Update Setting". In your ROM it is called MCU. I've seen it before.
[Android Head-Units] :
THEN I RECOMMEND you get the c525 has a wider lens so i can see more and autoguard dash cam works great records in background and saves video at end of drive also deletes oldest videos when data limit you set is reached
[Android Head-Units] :
it worked!!! Thank you so much

---------- Post added at 03:38 AM ---------- Previous post was at 03:34 AM ----------

you guys know there is a version 1.7 i have it if you want it
[Android Head-Units] Tuatara:
Ah ... now I understand. Thank you. I've not looked into the source beyond the Bonovo applications and the changes (in basic overview) which were made for that. I think I did that while skimming around in files your GitHub. Nor have I looked into the Rockchip specific device tree (and the issues therein). Are there any other Rockchip devices already ported to AOKP/CM? Possibly some of the work has been done, or the issues identified in another project?

I'm not sure I'll get any time to look into this (with you) for quite a while ... but I'll see if I can spot anything. Otherwise, this could be a slower, ongoing project we can try to solve.

Yeah ... I'm resisting the desire to install Xposed ... and I'm trying to keep my wishes more 'stock' at the moment ... just for stability once I have it working as I'd like it to.

Yes, the MCU functions which have been added should be possible to clean through decompiling the latest apps, and it shouldn't be too hard to figure out their signalling/data content from that. We could (in theory) develop our own custom apps, or just re-skin the existing ones a bit better. My original intent was to not do much more than that, but maybe it would be worth it to do.

Ah! That'd be awesome. I'm much (much) more of a hardware device designer/developer than an Android software developer, but I enjoy working on all aspects. I'll need you provide more info in what is involved in doing this. PM sent ...

---------- Post added at 04:29 PM ---------- Previous post was at 03:49 PM ----------

Well ... it is basically double the price for me, but if it's twice as good then it's worth it.

Any recommendations on the other Logitech Cameras? They should all be UVC, and therefore compatible AFAIK. It just comes down to what's the best one to spend the money on ... and then the time to get it working.

Logitech C170 VGA - 1.3-megapixel - NZD$26.45

Logitech C270 HD720p - 3-megapixel - NZD$44.85

Logitech C525 HD720p - 8-megapixel - NZD$77.05

Logitech C615 HD1080p - 8-megapixel - NZD$95.45

Logitech C920 HD1080p - Carl Zeiss 15-megapixel - NZD$127.65

Logitech C930e HD1080p - Carl Zeiss 15-megapixel - NZD$138.00

Are there any other UVC webcams which have a wide FOV? Something 120' or better like a Hero would be ideal.

---------- Post added at 04:34 PM ---------- Previous post was at 04:29 PM ----------

Hey ... a bit late to the party, and you might not need it now ... but I've finally built that ROM for you to update via the SD Card, and keep the original partition layout. It's up on my Google Drive now.
[Android Head-Units] :
yea i got it working and camera is just plug and play with your rom and buy it off of ebay got mine for 20usd
[Android Head-Units] Tuatara:
Untested update - Tuatara 1.1.4.3

In case anyone finds out by accident, I've updated my Google Drive with a ROM version which includes the minor changes & fixes I've found (decided on) to date. I built this in some time I had at work today, and will be testing these tonight. But I decided to use the work connection to upload them quickly and save myself some waiting time. There should not be any issues with the build, but I'm putting them out with an UNTESTED warning. If you've updated to 1.1.4.2 previously, then 1.1.4.3 can also be done through the SD Card if you wish to. (Partition layout is the same).

I've also put a couple of test versions up:

an sd card version with the original partition layout for those who can't (yet) repartition their devices to try it

a version with the "radio test" Bonovo apps

and a number of build.prop examples which can be used to create custom versions.

All changes are detailed in my original 1.1.4 post - linked in my signature.
[Android Head-Units] -=Jeff=-:
Did I read correctly somewhere that I could install CWM to backup my current rom settings, then Flash the Tuatara's ROM with the partition change then restore the back up of my previous apps?

which post was it or are there steps for that in the wiki?
[Android Head-Units] Tuatara:
Yes ... just a few pages back in the thread:

http://xdaforums.com/showpost.php?p=58962639&postcount=3099

Standard ClockworkMod backup & restore procedure.
[Android Head-Units] :
just finished installing and setting everything up and ran into two problems one goolge now doesnt hear my voice anymore and if i use robin personal assistant anytime it listen for my voice a message pops up saying google app has stopped. While other voice hearing apps can hear me these two can't also here beta maps all the settings dissapear no matter how many times i install it or where ever i install it at please help
[Android Head-Units] spoks:
Perhaps it would be useful to find out if your Huawei have some FW updates?

---------- Post added at 10:32 AM ---------- Previous post was at 10:11 AM ----------

Maybe at once you can implement those language translations too?

With 1.1.1 newsmy changed it to other name and then back to old MCU in 1.1.3 or 1.1.4
[Android Head-Units] horn34:
I have an offshore seedbox with an unlimited gig line, so hosting bandwidth won't be an issue. I would suggest using a public tracker, like kickass torrents (https://kickass.to/) because using private trackers can be pretty problematic. Most private trackers restrict access for anyone but registered users, so everyone here would have to a current, viable registration with that tracker to access files. Public trackers don't have that limitation.
[Android Head-Units] toologic:
[MENTION=349778]renedis[/MENTION] [MENTION=260727]Tuatara[/MENTION] and other guru

Let's update our language packs (resources) upto 1.1.4 bonovo apps

I think it is not hard work - only BonovoMCU had big anount new resource strings

We can do it before China NY holidays will end and next update (possible 1.1.5) will be with new (our latest) lang resources

What you think about it?
[Android Head-Units] janla:
Wow!

Many thanks for this :)

My turn now, obviously I am going to instal&test this ROM variant.

Do I really know how to recover using bootloader?

Actually I have performed this procedure many times on other devices, and always the hardest point was to memorize the proper key combination to enter bootloader mode ;)

So the question is what is hardware button combination for bootloader mode for our device?

I assume remote - i.e. ADB-related method may not work in case of not booting device.
[Android Head-Units] spoks:
Only problem is that Newsmy will have a bit different set of translations (if and when they will have it), because Summer asked translations for less apps, but with more strings if we compare it with our previously made translations.

But in time they would become equal anyway :)
[Android Head-Units] db2boy:
I need to take the box back out and do some measurements within in the house and break wifi analyzer out on a few devices and pin point what is happening. I don't expect it to be great buried in a car, in the dash etc but it does seem very bad atm where all my other devices have worked great in the garage. I'm using an Asus RT-AC66U which has been incredible but maybe time to look at a slight relocation and directional antenna. I'd be very interested in any HW mods :)
[Android Head-Units] usafle:
Viper4Android Set up and Install

Step One:

Launch Viper4Android and hit the menu key (it's on the upper right - 3 vertical dots) to get the drop down box as seen below in this screenshot:

You want to select from here UI Setting and change it to Expert as seen below:

[IMG="Expert Mode Selected"]http://drive.google.com/uc?export=view&id=0B1uULUT9jTAAY1BKclZ1dndrd3M[/IMG]

Step Two:

Go back into the Menu key and look for Lock Effect Profile then this menu will show up:

[IMG="Lock Effect Profile"]http://drive.google.com/uc?export=view&id=0B1uULUT9jTAAbHE4Mm9fdjRfS3c[/IMG]

From here you want to select Headset. This will "trick" Viper4Android into thinking you have more then one tiny phone speaker hooked up to the unit and allow you to customize things such as the Bass and clarity, etc.

Once that is done, you can now set up Viper4Android's audio customizations.

Step Three:

The following screenshots are how I have Viper setup for my unit. I have an powered Amplifier with a crossover built in along with Aftermarket speakers and a Subwoofer box. So, you are going to have to tinker it to your liking.

[IMG="Make sure this is checked"]http://drive.google.com/uc?export=view&id=0B1uULUT9jTAAYlVnRmExaUJpdkU[/IMG]

Make sure "Master Power" is checked.

The only thing you want to change here is the Convolver. This will have the biggest impact on how your music sounds.

As [MENTION=260727]Tuatara[/MENTION] has already 'pre-loaded' all of my Convolvers here you only need to select the one that best suits you!!

Make sure Viper Bass and Clarity are checked. Again, tinker to your liking the different outputs of those but leave them checked. Clarity Mode: XHiFi should not be changed.

Step Four:

Go play some music and then go back to Viper4Android while the music is playing. Select the menu key and then select Driver Status.

If everything is working correctly, you should see this screen:

Processing should say YES if everything is set up correctly. (I forgot to play some music when I took the screenshot - Sorry)

That's it! Enjoy your music!

(FYI: Figuring out how to share photos from Google Drive and inserting them into here absolutely sucked!)

Hopefully this helps!
[Android Head-Units] Zaphod-Beeblebrox:
I am already seeing some blank images as usage goes up. Google Drive is probably not the best solution for this. Imgur is my go to when I need to share out an image. Free, easy, variety of link options for embedded.

Warning. Visiting the Imgur home page has a habit of being a time sink. You can easily loose 20 to 30 minutes just hitting 'next' photo. :)
[Android Head-Units] usafle:
Odd... I spent hours researching on how to share GDrive images. The pictures load each and every time for me. I was thinking about imgur or another site, but the thought of having to register on another site just to share pictures annoys the heck out of me.
[Android Head-Units] zanix:
Very nice, thanks for the write up.

I think at this point someone (probably me) needs to split up the wiki page into sub-pages.
[Android Head-Units] typos1:
On the HuiFei type units (also RockChip based - RK3066, with STMicroElectronics MCU, though different to the NU3001's) all of the custom ROMs use the standard RockChip update method of putting the update.image on the root of the SD card , no one uses the RKbatchtools + pc method (unless they use TWRP, see below). And each ROM has been repartitioned, there are no problems with installing custom ROMs in this way, just thought you might like to know this.

A custom recovery (TWRP) is working on the HuiFei type units but its optional for custom ROMs you dont have to use it (although if you use it then you cant update using the SD card method). A mouse has to be used for control though as none of the buttons (or touchscreen) work in TWRP because theyre controlled by the MCU as they also appear to be in the Newsmy (the HuiFeis do not have removable boxes, everything is inside the headunit).

Just thought you might find this info useful. :)
[Android Head-Units] jpapadami:
Does anybody know how to stop apps from launching on their own after reboot, when a USB device is plugged into the unit? I use an OBDLink SX USB adapter and after boot, Torque Pro always starts and I have to exit it to get to the home screen. Same goes for a DVBT/T2 tuner that I have plugged in the OTG port which launches the default app set for it. I tried using AutoRun Manager to disable the listeners that are registered for each default app that uses the corresponding USB device, but that doesn't seem to work.
[Android Head-Units] spoks:
Yesterday I updated my 1GB device to 1.1.4.3- tuatara.img

Hardest part was ... to get out Android box from installation place :D

Update went smooth and until now HU works as expected, at least radio, music playing, wifi, bluetooth calls etc.

Thank you, Tuatara for your job. I hope Newsmy will be smart enough to contact you for cooperation on RDS problem solving.

---------- Post added at 03:00 PM ---------- Previous post was at 02:56 PM ----------

Maybe you have accidentally in preferences checked option to start up after reboot?

I don't know about DVBT turner, but Torque has such option. ;)
[Android Head-Units] jpapadami:
No, it's unchecked by default.
[Android Head-Units] nestortoledo:
I found this litle toy http://www.amazon.co.uk/Satechi®-Bl...=1424957561&sr=8-2&keywords=satechi+bluetooth

That looks nice, apparently should work with out units, what you guys think?