yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] kwalsh24:
What he said haha.... I was just in the middle ofof trying to word this lol

---------- Post added at 07:07 AM ---------- Previous post was at 07:05 AM ----------

If anyone is able to do this, and make the avin app run in the background, id gladly donate to their effort. These are my two Biggest let Downs with this unit.
[Android Head-Units] typos1:
Ok, maybe I gave an incorrect example, but you need some stuff implemented in the MCU to acheive some basic stuff . . . or bypass the MCU altogether.

Not knocking what youre doing by any means - it will be great to have AOKP on a headunit, but the MCU needs better functionality.
[Android Head-Units] kwalsh24:
I do need to send a big thanks out to jpapadami. He aided my igo issue and its been resolved. No clue wtf was wrong with every version I downloaded. However things now work after hours of frustration.

Back to bed for me, been up since 5am local, amd I work at 9, time for an hour nap lol
[Android Head-Units] Zaphod-Beeblebrox:
It's very doable. And it's not about money. But we need more people looking into the code. It's not like it's not available. I'll say it again. This is a developers site. There are many tutorials on how to set up a build environment in a VM/Spare computer, whatever. Learn how to do it. Build from source. Tweak it. I started with very small tweaks to my Galaxy Nexus after ICS. I didn't know the first bit of Java. I just made some XML layout tweaks. It eventually grew into learning some Java and making UI tweaks.

By the time it was done, I had coded some of the more memorable features of AOKP.
[Android Head-Units] renedis:
The Netherlands is easy..

When sended with China post you do not have to pay tax or pass custom declarations. When sended with DHL/Fedex you always have to pay tax (21%).

Tests are never done.. That takes to much time.

heck.. I would almost say, send it to me and I send it to Germany (costs 30 euro).
[Android Head-Units] Zaphod-Beeblebrox:
You'll need to think a lot harder. Most things people have mentioned are very doable within existing infrastructure. About the only things that can't be done would involve EQ type effects on core app (Radio/AV/Bluetooth?). But it's likely that the hardware isn't even there to support this.
[Android Head-Units] renedis:
/off topic:

So funny to read this.. It is 13:19 o'clock at this moment in my country..

/ on topic
[Android Head-Units] typos1:
My point is that Newsmy need to optimise the MCU and develop it further so its more like the MCU on the HuiFei/KGL and the AN21-U etc.
[Android Head-Units] kwalsh24:
I agree, when comparing the two first hand, the newsmy product feels so far behind vs the huifei product. Its nearly tempting to pull the newsmy and bench it for a while, and put the huifei back in. Buuuut that unit is soon to go into my dads car, as I did sell off his crappy audiosources unit to help aid the purchase of the newsmy unit [emoji6]

Newsmy has our money, we backed them to get the units, now its time for them to back their unit, develop it so we can praise it to others so they can buy it and support them.

Honestly, right now I wouldn't recommend this unit to anyone in its current software state. If someone asked me right now which to get for every day use, id say the huifei just due to its development. Once this unit gets development more, then that would change
[Android Head-Units] Zaphod-Beeblebrox:
And my point was that this is XDA Developers. We don't sit around *****ing about what a manufacturer hasn't done. We figure out how to do it ourselves.

The Core apps and MCU handling code is right here:

https://github.com/Zaphod-Beeblebrox/packages_apps_BonovoApps

Learning this stuff is not nearly as hard as you might think. It just takes some time and a lot of stubbornness.
[Android Head-Units] typos1:
Are you reading this Summer ? - get your devs to buy a HuiFei or Klyde or AN21-U unit and copy the MCU functionality !!

It will be much more productive for you than editing the Wiki.
[Android Head-Units] kwalsh24:
... don't think my nap is happening lol ...
[Android Head-Units] typos1:
Oh, I dont need lessons in stubbornness !! Lol

But its not MCU handling I m referring to, its the actual MCU and its software/functionality.

No one has touched it on this unit AFAIK, for instance what make is it, what software does it use ? But I am working on the assumption that Newsmy will eventually sort this.
[Android Head-Units] -=Jeff=-:
Alright I spent more time on my unit sine I got it yesterday.. I did get one of my serial (USB) devices to work with it. it turns out it was the version of apk I used.. Anyway, I am feeling a bit better about the unit but like kwalsh I am a bit bummed that I cannot set AVIN then navigate to another app, although I have not tried it yet.

My biggest issue right now is a couple of the APKs I want to use don't scale right on the screen (I think the 240DPI setting has something to do with it :) ) Anyway, I would like to install xposed framework to handle the couple apps, but I cannot get the unit to connect to a PC to even attempt to root..

When I force install drivers from the RKbatch 1.6 zip off the WIKI this is what I get:

Error say code 10 unable to start

tried a couple different versions that seem to allow it to function and seem to be working, then Kingo does not recognize it. current version on the NU3001 I have is MCU =31 and ROM 1.1.1. I would like to install renedis version on here, but if I cannot connect to the PC I am afraid I will brick the unit. I have USB Debugging checked, Should USB storage be on or off? (on android) right now I am powering the unit like normal connected to the headunit and

So, any suggestions on what to try next to get the unit to connect? I had used the same pc for a mk809iii HDMI stick with android.

Not having much luck with it

THANKS
[Android Head-Units] jpapadami:
As it seems that I am in the same boat as you were when you started out learning to build roms from source code, I plan on reading some tutorials and get a build environment up and running. What would help is instead of going through all the posts on the forums, have the people who are currently working on the dev part to add to the wiki what obstacles/issues or even a checklist of things that need to get done so people who are learning can have a starting point of where to direct their efforts. Some of the things I remember we discussed offline were:

1. AOKP can't compile and build right

2. Compiling of kernel modules

Something like this would be really helpful for people who want to jump in and help. If that's doable, it would be great.
[Android Head-Units] welshblob:
This is partly why I bought this unit as I want something to kick start my delving into android and skinning/writing some apps. There is a certain amount of "there's an app for that" mentality which has stopped me in the past as generally you can find an app that which may meet most of your requirements, but not necessarily all. Hoping to find some time soon now that am able to power the android box out of the car.
[Android Head-Units] nestortoledo:
Between all, most of us looked for a PURE ANDROID UNIT.

Something, that have all android have, and less china app that normaly looks ugly and dosent work as they need to doo.

And i think thats i what we get. only radio, mcu are modified apps, rest all are android stock.

Since day one, i know i want to make my theme, and use the units on my way.

Newsmy have dual wince/android units with same hardware but with more customized software for be more complete out of the box.

When i buy the unit i know what im buying.

may be im wrong. but what newsmy try to do with this units nu3001 is include a tablet on the car nothing else.

And for me the unit is working fine for day to day use.

Music works. GPS works, Bluetooth works. Internet works. Backup camera works fine

Its right bluetooth have some problems at start, but this problems was solved (for me at least ) on recent updates.

Also its ok radio dosent have working rds, but we have signs they are working on it. Other way huafei units have rds, but horrible quality signal.

I prefer to have good quality signal and be hable to listen radio on my garage, than have a rds.
[Android Head-Units] usafle:
Update on my ROOT issue and screen auto-dim

Not that many care since most of us are up in arms about Summer changing the Wiki and lack of help in compiling a ROM. But; figure I'd update my above issues.

SuperSU will not work if I update to newest version on Play Store. I've tried every step imaginable and every which way to do it. Nor will any of the other SuperSU apps work. If I update the app and or Binary, I lose ROOT. No way around it.

Right now SU works from the pre installed KingoRoot app. However BusyBox won't install correctly because it's looking for the new SU binary.

Xposed works fine along with some of my other ROOT apps.

So until someone releases a custom ROM pre rooted.....I'm stuck here.

Forgive me but I forgot which user posted a video about his auto brightness working when head lights are on. Thank you whomever took time out to do that.

I've looked at your video and made the same changes to my unit. I will admit that the brightness lowers A BIT. However, if I manually change the brightness to the lowest setting, its a big difference -a lot lower brightness setting then the "auto brightness" .

Your video appears the same way. It lowers it but doesn't lower it ALL the way. Try then lowest manual brightness setting and see if you notice a difference in the brightness of the unit?
[Android Head-Units] kwalsh24:
I really hope that's not the case. Even tho, that's exactly how it feels.
[Android Head-Units] welshblob:
No that's a bit unfair. I think it should read ...

may be im wrong. but what newsmy try to do with this units nu3001 is include a tablet on the car but with integration and support for installing into a car where possible i.e. mounting, connections, CAN bus, SWC, AMP etc. and with varying additional functionality for specific car models

What they have removed mainly is the CD/DVD drive that I have no use for and the WInCE part.
[Android Head-Units] -=Jeff=-:
Sorry I am unable to help but was curious how you were able to gain root originally? I am not having any luck
[Android Head-Units] welshblob:
I care, thanks for the update ;)
[Android Head-Units] nestortoledo:
Yes of course, include a tablet on the car integrating it. But they dont spend so much time or effort on software. just added the basic and needed things.

Something liek leave nu3001 and variants for advanced users. and dual wince/android for peopel that want something better out of the box.

If not why they are still updating the dual wince/android versions?
[Android Head-Units] usafle:
I simply started from scratch and used the RKBatch tool to "restore" the newest factory ROM and then used the KingoROOT app to "enable" SuperSU.

Again, as long as I don't update the SuperSU app from the one that is installed from KingoROOT app, then I can keep ROOT apps (SOME) working.

Awww. I am truly touched. At least that's ONE person. Lol
[Android Head-Units] bockywocky:
It would have been better that someone only can edit the wiki after 50 posts or more.
[Android Head-Units] -=Jeff=-:
Huh.. interesting, I guess I am having other issues where fresh out of the box Kingo does not even see the device for rooting.. not sure what is going on.. all I really want is xposed framework
[Android Head-Units] spoks:
I do agree with you.
[Android Head-Units] kwalsh24:
It does feel like a stripped down version of their wince unit, hell there was a shortcut to launch wince on my unit when I first got it.

However, I do still stand behind what I said, it really does feel like a radio with a tablet meshed with it
[Android Head-Units] usafle:
You have the required drivers installed from RKBatch Tool? That's the only drivers that work. If RKBatch can see the device then so should the Kingo app.
[Android Head-Units] -=Jeff=-:
Yes but the RKbatch 1.6 drivers report a code 10 in windows (unable to start). I tried the RKBatch 1.7 as well. I have uninstalled both and win7 shows this:

when I install 1.6 I get this::
[Android Head-Units] welshblob:
I think we're in a transition period as these products evolve as these devices were originally based on WinCE then there is a fair amount of effort tied up in the hardware and software for that especially the ones made for specific car models. They then bolted on android boards to get a product to market quickly and the minimum software necessary . Until we're here with android only devices that still probably don't have the same level of support that WinCE does although I guess manufacturers are at different stages with this.

It would make it easier if would only make the hardware open with documented specs and APIs but I guess they are concerned about competition in this area and being ripped off. I doubt any of this software is properly documented either that would make porting a bit easier or maybe I'm being unfair.
[Android Head-Units] usafle:
I'm sure you've already tried to manually / force install the drivers?

I can't recall if I ran into an issue using Win7 x64 or they just installed because it was so long ago....

I've used this App before with success in removing all remnants of USB device drivers and starting over again.
[Android Head-Units] Zaphod-Beeblebrox:
My latest AOKP code on github will compile. there are 2 lib files that aren't getting put into the correct directory, and a third that doesn't seem to be getting built. I manually fix those three things and I can boot into AOKP. Having issues with external_sd mounting, and none of the radios are working. (WiFi/Bluetooth). I'm slowly making progress, but this isn't the sort of thing I have any knowledge at. I'm having to learn a lot of this as I go (which should be a lesson to others. Ignorance is not static. It's dynamic. and it's controlled by your desire to accomplish something).

2) I'm using red's kernel in my builds. follow the instructions on his github and it builds fine and is included in my system image.

3) My biggest gripe is that I haven't figured out the RK3188 recovery system yet. The Boot & Recovery images that I build don't work. I have to pack the boot/recovery images from a stock (or amplified) ROM) to get mine to boot.

---------- Post added at 09:37 AM ---------- Previous post was at 09:35 AM ----------

The 'RockChip Class' driver should be for bootloader mode. Use the drivers in the rockbatch archive.

The other one should be your ADB device. I'm pretty sure I used the stock Google USB driver in the SDK for that.
[Android Head-Units] renedis:
Which micro USB cable are you using? The OTG cable? If so, use an other micro USB cable.

Also.. When you succesfully start the android box and get connected to the computer to transfer files (the computer sees the android box as external disk) you can easily change the mode in RKbatchtool by pressing "SWITCH" in the program. After that you can upgrade the rom.

Working on that way I found out that it is a lot easier to do then pressing that tiny button and hope that it went well..
[Android Head-Units] spoks:
:laugh: I got from Summer in white box without any manual (just small bucklet from other - dual system Android unit) and without any sticker on unit. Android box with Newsmy name.
[Android Head-Units] renedis:
You do know that is based on 1.0.9 and the source code of 1.1.2 is also available? (download @ my ftp).
[Android Head-Units] bockywocky:
Same problem here :(

Even try force installing the driver
[Android Head-Units] Zaphod-Beeblebrox:
I assume you mean you have Kernel source for 1.1.2 If so, yes, I have it too. I can build with that one as well. I think I actually merged the new kernel into my platform_manifest. Can't remember :)

If you mean you have full 1.1.2 source (which I doubt, as I've read every excruciating comment in this thread and haven't see any mention of that) then let me know.
[Android Head-Units] sam275:
You have to install universal ADB google driver and all will be OK

I had is the same problem
[Android Head-Units] renedis:
Sorry my bad.. kernel of 1.1.2 in kernel 1.1.2 folder on my FTP.

---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------

PM me NOW and I can help you via TeamViewer
[Android Head-Units] bockywocky:
Thank you, gonna try that
[Android Head-Units] ficu1985:
It only works with x86 systems. You need to press the reset buttons while introducing the main cable that connects the screen to the android box
[Android Head-Units] Ekki_221:
Just use the Google universal ADB Driver instead, then everything works...
[Android Head-Units] -=Jeff=-:
I have a Full size USB (from PC) to Mini USB connected directly to the Android box.

When I connect on the Touch screen there is an Option for USB storage do I need that on or off?

Yes the switch works and it makes the one box in the RK tool green. If I upload you version 1.1.2 (once I get to download it) will it already have root? my first plan was to root the device to allow use of Xposed framework. I am still not having any luck getting Kingo to recognize the device even though I can get the rockchip driver to be detected. Now the rkbatch v1.6 uses a 3.0.0 driver, I can get it recognied only with the 3.5 or 3.7 rockchip driver
[Android Head-Units] bockywocky:
Ok clear. I have to wait for my new Android box first. It will be replaced by Summer since it was blown.
[Android Head-Units] nestortoledo:
Here is the small video i promise

[YOUTUBE]iI8y4Y8hXPM[/YOUTUBE]
[Android Head-Units] renedis:
Use the kingo app when your android box is in "USB storage" mode!
[Android Head-Units] spoks:
Somewhere earlier was posted youtube videos how update rom, including driver installing.

Seems this one www.youtube.com/watch?v=_BVZXn9n3LM
[Android Head-Units] -=Jeff=-:
Thanks I will try it tonight
[Android Head-Units] ficu1985:
Update
[Android Head-Units] usafle:
Let me know when English is up please.

Thanks!
[Android Head-Units] nestortoledo:
The icons that need to be translated are only 3 (Phone, Music, Contacts) ,i upload on this post.

Any way will try to upload full zip package tonight
[Android Head-Units] typos1:
There are at least 5 different types of Android head units around (S150, AN21-U, WD8801, HuiFei/KLD/RM/GS/JY, Ownice) around, they all have MCUs for the tuner and amp and to facilitate the usual car stereo functions. Theyve been around for at least 3 years, theres lots of support for them, more than for WinCE (I dont know why these companies still bother with WinCE, though most companies stopped the whole dual boot thing a few years back, Newsmy persist with it for some reason). We are "here" with pure Android (well as pure as it can get with an MCU in the mix).

The problem seems to be Newsmy's MCU, which is very immature compared to the other units. Most of these Chinese headunit companies release products that arent fully developed and carry on development after sales start, Newsmy is no different, its just that their MCU is even less developed than the others, probably because its their first pure Android unit. I m sure theyll continue to add features to the MCU over the coming months.
[Android Head-Units] Zaphod-Beeblebrox:
I'm not sure you have a full understanding of just how the MCU/Android symbiotic works. And while it will vary somewhat between system, you keep talking about how the MCU is under-developed. It's not. It's the MCU controls within our version of Android. Spend some time combing through the code I linked a few pages back and you'll see that many of the functions people want are either possible or even partially started in the MCU handling code.
[Android Head-Units] zanix:
This makes sense, if I did not authorize reselling then I would probably want to not advertise the resellers. If there is a list of official sellers, then we should definitely have them on the wiki and state that any other sources are "at your own risk". This also makes sense from a support stance as well. I would not want to support a clone of a product I make.

Check the wiki, it has a guide on this plus a few other things.

http://xdaforums.com/wiki/Newsmy_CarPad_NU3001

I really wish I knew Java and Android more, and I plan on learning soon, so I can contribute in that way as well. I really like this device. I came from using a Nexus 7/various components/amp hack job in my car to this and I really want to support and promote Newsmy for how cool they have been with us.

Summer is offering a fixed price (stated on a forum post from her and the wiki) for us even if their prices on Aliexpress jump up just by contacting her. She has also personally handled any purchasing or shipping errors people have had. One member was even able to get just the screen (digitizer maybe?) because he cracked it and we thought there was no way they would send only that. We also have the source code from v1.0.9, they could have told us to delete it but they haven't. And yes, she did delete a section in the wiki which I think was wrong, but I feel that is forgivable. If the other sellers we promote or show on the wiki are fakes or clones, this is a slap to their faces since we would not be supporting them and that would give them good reason to not support us. I would love to change the list to 'official sellers' and I really hope there are so people can get this device without having to deal with customs and other possible issues when shipping from China.

---------- Post added at 09:54 AM ---------- Previous post was at 09:51 AM ----------

Yes, I'm using a generic Bluetooth OBD II scanner I bought from Amazon a couple years ago.
[Android Head-Units] bas-r:
Quite a shame to see Summer virtually leave XDA and only communicating via Facebook now.

Though I do understand, given the backlash she received over meddling in "our" wiki...
[Android Head-Units] jpapadami:
I don't think she left XDA. She has just been more active in FB because (and this is my opinion) she can offer support while simultaneously reach out to more potential customers. The group grew pretty quickly, from 10 to now 30 members in a week.
[Android Head-Units] usafle:
Do you think she even saw the "back lash"? She's only made like 3 posts on here before messing with the Wiki. Lol

+1 for generic OBD BT device. Caveat: be careful as the one I'm using stays ON 24/7. Learned that the hard way after jumping into the car after a few days away and hearing the dreaded •click click° of a dead car battery!

Currently looking for one that stops broadcasting when the ignition is turned off.
[Android Head-Units] typos1:
I see, I thought that they had to be enabled on the MCU side of things first, if its just a question of developing the Bonovo apps that interact with the MCU further thats good news.
[Android Head-Units] zanix:
Yeah, mine stays on but apparently my battery can handle it. The only ones I have seen that shut off when the car does are the expensive ones like ScanTool.
[Android Head-Units] jpapadami:
There are bluetooh OBD adatpers that you can power off manually.
[Android Head-Units] zanix:
Would be neat to wire the on/off to the car's ignition power.
[Android Head-Units] kwalsh24:
You'd think that that the obdII port would be wired to the ignition, instead of an always on state, as a majority of the time when you use the port, you have to have the ignition on anyhow.
[Android Head-Units] usafle:
I've got a Honda CRZ which is a hybrid but not a girl Prius hybrid. Lol

Anyway, its got a itty Bitty 12v battery for the car. Anything that draws power kills the battery unfortunately.

Hence why I was so concerned about the "brain" staying on....
[Android Head-Units] kwalsh24:
Ah just run a line to them cells that run the electric motor in that baby and you'll ne good to go ;)

I've got a big ol honker of a battery in my diesel Jetta, so nothing to worry there lol
[Android Head-Units] usafle:
Some of those generic cheap ones can't handle the "fast" data transfer speeds that Torque utilizes. The one knock off OBDII scanner I have throws errors to Torque if I try to enable the speed