[Android Head-Units] Tuatara:
From what I've seen in the "test_language" and "test_radio" versions, these were only the start of the language and radio updates. The actual language changes did not appear to be complete, as when I glanced at the files, there were still "Hello World!", "Hallo wereld!", and "Hallo Welt!" strings in there. I believe that they are just testing versions, and do not contain the full language support yet. While they might be an improvement on what we currently have, the version they appear to be compiled for is 1.1.2, and not 1.1.4. It's probably worth the wait until the next update and go from there.

---------- Post added at 01:41 PM ---------- Previous post was at 01:34 PM ----------

This is only a build.prop variant ... just to see if it will work for PlayStore APK selections (i.e. to have most everything available). You will need to merge the build.prop into the ROM yourself.

Unfortunately I have not had the time to test anything last night, and won't have the time today either.

You can use ADB to get into bootloader mode (in case the android bootloops, or won't fully boot). "adb shell reboot bootloader" should do it.

Alternatively, there is a small silver "pinhole" on the side of the unit. With the unit powered-off, gently press this pin-button in with a paperclip until you feel a soft-click. GENTLY!!! (I can't stress this enough - I just broke mine, by pushing the physical button off the PCB inside - it's just a very small surface mount button at the edge of the PCB. Not much PCB trace holding it in place. So be very gentle. I broke mine off, even with my own warnings :() Power on the unit, and it will come up 'black screen', but RKBatchTool will come up with a Green Box, just as if you did the "Switch".

Let me know how your testing goes.

---------- Post added at 01:57 PM ---------- Previous post was at 01:41 PM ----------

Thank you for the useful information. Definitely interesting! A few questions (since I didn't test everything, and I have made a few assumptions).

I thought that the SDCard update was intended to retain the current settings/user data during the ROM upgrade. If the flash itself is repartitioned, then I would believe it to be "impossible" to keep the data, as this partition could shrink/grow to any size. If there is a partition change, does the SDCard update method format all the partitions if the layout is different in any way, and retain the partitions if they are the same? If so, then that could be a suitable update method - with caveats/warnings to back everything up first, if the partitions have been changed.

The ClockworkMod I built does work with Touch (swipes), and keyboard and mouse control are working perfectly (for me - someone else has had an issue with mouse control, but mine is working flawlessly). However, it is the same as the HuiFei units, the hardware buttons do not work.

Hmmm ... that gives me an idea. I might see if I can get the SDCard update method (or something which replicates it) working within ClockworkMod - if and only if we can be certain that this update method works reliably with partition changes, and/or data retention. That would give us the best of all worlds - SDCard update and CWM recovery. Potentially just packaging a ROM update as a installable ZIP would do it.

Thanks again for the info! More to develop and test.