[Android Head-Units] Tuatara:
Great. That's confirmation that ClockworkMod recovery is working perfectly. It's one thing to have it work for you ... and another if it works for everyone else!

Odd that the mouse isn't working ... I'll look into that and see if I can correct that, along with the (custom) Newsmy hardware buttons (thanks Zaphod).

Ok. Thank you for the feedback. I'm going to go through the language and radio update ROMs from renedis' FTP and will see what the differences are. If I can see anything of note, I'll try making a ROM which includes the 'latest' versions of these files as a testing version. Personally I would like to have the android box keep power for 12+ hours (maybe 24 hours), to have an instant boot in the mornings. After a day though, the full shutdown is perfect.

---------- Post added at 12:18 PM ---------- Previous post was at 12:03 PM ----------

Yeah ... the work done is amazing, but it does sound like a huge hack/effort. Using a Jellybean/Kitkat kernel and making Lollipop run on that. It's just like the backporting I was doing for Windows Mobile ... yeah, you might/should get it to work ... mostly. :(

Damn ... so that's why they don't work in ClockworkMod. I can't test that, so I was hoping the regular keys would work. Now I'm fairly sure I won't be able to fix that - at least not without help from Oma and source to recompile the ClockworkMod recovery binary.

There actually have been very few changes in the ROM applications and kernel between versions. Some binaries are very different, some have only been recompiled and signed again. The large majority have remained quite stable since 1.0.9. I believe that Newsmy is now primarily working on the MCU and the bonovo apps, since the device is stable - in order to properly complete and "brand" the device as Newsmy. This is where all the value add is.

Given that we (sort of) know the MCU interface (from the android end), we could theoretically build custom versions of the bonovo apps, which can operate/control the MCU appropriately. A decompiler on the updated versions would give us the interface requirements. This would provide the greatest benefits for the least amount of work.

Having a full kernel & AOKP/AOSP ROM would be the ultimate goal, but that would need a full understanding of the hardware and architecture. That's a lot of reverse engineering - it's not just the MCU interface. It can be done, but just like for the MCU source code, it's an almost impossible task to do without all the supporting documentation and design.

---------- Post added at 12:25 PM ---------- Previous post was at 12:18 PM ----------

Great news. Recovery is working well - so I can now leave that partition alone.

I also basically got the same AnTuTu results: 25202

Good - you shouldn't get any warnings from SuperSU. It's now installed correctly, with all binaries (supolicy and update methods) in place. When the next version is released it should (hopefully) upgrade and be able to replace the binaries without any issues.

Boot version: You had me worried about this for a moment - but I've decompiled the ROM again, and the boot loader version I have in there is 2.15 - both the binary, and in the parameter file. Are you certain of this?

MCU App is taken directly and unchanged from the STOCK 1.1.4 ROM. Newsmy changed the MCU app name sometime between 1.0.9 and 1.1.4 ... maybe you're remembering the older name?

---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------

Great. I'll go out and get a c270 then (they're cheap), and see if I can get video to work for use as a "car recorder".