|
Ok, I am gently poking the Rom Kitchen version.
helmi_c, is there any info anywhere on what is in this version? Is it the same as the one we've been installing? Is it newer?
(1) I cannot tell for sure if .NETCF 2.0 is in it - guess I will need to flash to be sure, but it seems like some kinda .NET is in the rom kitchen stuff.
(2) I think I applied the 'Pic & Video' dll fix to the rom kitchen (put correct dlls in \OEM\MouHid.dll folder, and they look to have made it into the rom build)
(3) Got rid of the bad .dl_ files in same folder
(4) removed all T9 Language dlls from same folder
(5) removed pocket msn, because it's evil, from \OEM - just deleted \OEM\MSN1-3
Built rom, build succeeeded.
So... assuming I understand what I am doing (yeah, right) I think I might be able to add packages - seems pretty straightforward.
What is the advantage/disadvantage of using Rom Kitchen over the more manual way Wideawake/ Colonel are using?
The advantages I see are, its a lot easier to share 'preinstalled packages' with other people - you just need to give them the folder contents that drop into the \OEM folder, and they should be able to re-build their Custom rom... or likewise, its easy to take addons OUT of a custom rom just by removing the folder you don't want from the \OEM folder, and rebuilding the ROM...
So, for example, I could make one or more SPRINT addons (to get the needed Sprint Extended Rom stuff, but no junkware) and then have a sprint-specific ROM build, but our verizon (and other carrier) friends would just not use those OEM folder(s) when building their custom ROMs.
Anyway, just some poking around for now, nothing major to report.
|