|
||||
Well, mostly true. Some OEMs have an initflashfiles.dat file in them. This file can (among other tings) make copies of ROM files in other directories. The copies will eat into your program memory.
A good example of this is the OEM for Anaston's Slider 2.01 program I made - all the bitmaps (which is about 95% of the application size) have to be relocated to another directory. As such, including this OEM in your ROM doesn't really save program memory - it only saves you installation time. (Anaston is working on eliminating the need to copy the bitmaps, so there will be a greater benefit to cooking in future version of his Slider program) |
|
||||
@ comanick on a less technical note-
here's my two bits (or maybe just worth one?) For better or worse, this can become an obsession as there's something new to play with every week it seems. Just when you have worked the kinks out of your phone, there's a new rom with its own kinks. Switching back to an official and theoretically more stable ROM will make you realize exactly how slow and clunky it was beforehand, and you'll be back to the endless search for a stable rom with all the bells and whistles. That said, if you're into this stuff, it's fun. Just don't flash a new ROM if you will not be able reflash for a while. ie, i was on vacation last week, which for me needs to entail no computer projects, and my phone froze and had to be hard reset, thus leaving me without my PIM info until i could get back to the computer. Now it runs like a champ on the colonel's latest, but I am feeling the itch to use the helmi kitchen. however, i am also a sunrocket subscriber for my landline phone, and since they vanished overnight and took my dial tone with them, i probably need some stability for a little while. it never ends...! |
|
|
|