[Android Head-Units] Tuatara:
Apologies for my absence ... Real Life deadlines ...

Ok. I was under the mistaken assumption that the SD Card update would preserve the settings. Since it does not, I'm going to look into supporting the SD Card update within the Clockwork Mod recovery. There must be a way to do this ... maybe even possible to retain the settings as an OTA update ... but that could be very difficult. I'll see what I can do.

Nope. Confirmed. SD Card will wipe everything. Only the OTA update method could work. My error in assumption.

When editing build.prop you MUST use an editor which can edit in the UNIX format. Using Notepad or any other windows centric editor will cause boot failure. On windows you can use Notepad++ (highly recommended).

Once the ClockworkMod has been flashed to the recovery partition, the Android Box will NOT update using the SDCard method (recovery partition isn't there). I will look into supporting both ClockworkMod and SD Card update in my next version. I will see if there is a "non-wipe" update method possibility, but I don't believe that this can be easily achieved.

Unfortunately the SD Card update method is not supported when ClockworkMod is flashed. I'll look into adding a SDCard update method, as I can see how this would be useful. :cool:

I'm using PAL cameras without issue. Others have used NTSC. My bet is that the headunit is auto-detecting the video signal timing and display it accordingly.

This is why I increased the partition size from 1Gb to 3Gb in my ROM. If you have Rooted your AB properly, then ES File Explorer can traverse the root folders. I'm fairly certain you won't find anything of note to delete from there. The best answer would be to flash ClockworkMod to the recovery partition, back up your device, flash my ROM with larger partition space, and then restore your data.

What type of flickering are you experiencing? Is this drawing flickering (black update regions, colour bars, portions of the display updating late), or is this full-screen flickering ... i.e. the whole screen goes black?

In my first ROM 1.1.4.1 - I found that the graphics cache settings were too aggressive, and it was attempting to retain too much in memory, and not releasing enough back to the OS (under load). In the latest ROM I have reduced these values, and have not experienced the update-region flashing since.

Otherwise though, I have also experienced the full-screen flashing. From what I can determine this is due to the HDMI data on the Firewire cable. For some reason the cable is very sensitive to connection (impedance mis-match? capacitive issues - humidity related, or otherwise?). I've "bound" my cable to the Android Box using electricians tape (just wrapped it tight down along the side), to prevent any movement and a snug connection. I have since then not experienced any issues. It could very well be the cable itself causing the issues. I'm looking into getting another new (very short) Firewire cable as replacement, and will update with results.

This could well be a supply loading issue within the headunit, or noise affecting the HMDI transmission. Grounding is an excellent suggestion - ensure that there is no fluctuation in the supply. In theory this could also be the reason behind the flickering I encountered - the headunit (or other elements in the car) can be inducing noise into the Firewire cable (like the hum you hear in a radio close to a transformer). The HDMI over Firewire transmission may be very sensitive to any noise, and my 'electricians tape' patch has simply re-routed the cable to avoid this induced noise, or it is just a placebo and the wire is no longer acting as an antenna. I'll try to do more testing.