Thread: New to forum . pros and cons of custom roms
View Single Post
  #14 (permalink)  
Old 07-15-2007, 11:33 PM
gguruusa's Avatar
gguruusa
Deep Thinker
Offline
Location: Mountain top
  
Join Date: Jan 2007
Posts: 3,252
Reputation: 4726
gguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributions
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
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)
Reply With Quote