I've also tried to load up a circle battery icon (via UOT kitchen) but on this (and not surprisingly since this rom is based on it) and the HH ROM this mod fails, suspect it's down to the modified kernel; another problem i cannot solve easily.
I also noticed that both this ROM and the HH eat up my battery, but I suspect this is down to some app I'm running so I'm busy eliminating each one at a time. The battery drain is enormous, and I don't use that word lightly. The phone will go from full battery charge to completely drained overnight. From all the 2.1 and 2.2 roms I tried, this and HH are the only ones giving me this problem.
I am now using this ROM as my everyday one and I have to congratulate all involved. It runs smooth and all is working on it. The issues outlined above are only annoyances and do not deter from the general good use of this ROM.
EDIT: I made progress with this by following instrucitons found here on this site at: http://android.modac...-alpha-release/
Howerver, while the unpacking works fine and I was able to find the logo.bmp (red devil), removing it and re-packing it produces the boot.img, however the perl scripts used are obviously for the Pulse and therefore the base addresses are wrong; e.g. it produces a 2K boot.img instead of the SF 4K. Any devs on here want to lend a helping hand please ? Either fix the perl scripts (which would really come in handy for other wanna-be devs) so they work with our SF, or just take the boot.img, remove the logo.bmp, repack and upload here.
Just as a reminder here's the SF mapping:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00480000 00020000 "recovery"
mtd1: 00480000 00020000 "boot"
mtd2: 00180000 00020000 "splash"
mtd3: 00060000 00020000 "misc"
mtd4: 02940000 00020000 "cache"
mtd5: 0cf80000 00020000 "system"
mtd6: 0d020000 00020000 "userdata"
mtd7: 00180000 00020000 "persist"
UPDATE: after a lot of reading through various forums finally got this to work. I had to unpack boot.img, remove logo.bmp and re-pack using mkbootfs and mkbootimg. Finally tested with fastboot and all is now fine, the little Red Devil has gone forever.
On a personal note I have no idea why devs do this. One can simply leave the boot.img well alone and place whatever bootanimation they want either in framework or bootanimation.zip, where it would be a lot easier to remove. I don't mind devs 'signing' their ROMs, inded I fully support it, but please accept we do not all have the same aesthetic tastes in 'eye candy'.
Edited by xzyk, 13 December 2010 - 09:49 PM.