View Single Post
  #5 (permalink)  
Old 01-19-2009, 08:00 PM
Kolano's Avatar
Kolano
Regular 'Geeker
Offline
 
Join Date: May 2007
Posts: 422
Reputation: 71
Kolano is becoming a great contributor
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Question for our ROM cookers regarding program and storage memory of ROMS

Quote:
Originally Posted by aaronvlee View Post
one thing I've noticed is that these roms are absolutely awsome that I'm testing except one thing is unclear to me...

I'm to believe that installing apps in the storage memory rather than the program memory is either impossible or not concerning...but that would in theory free up the program memory's space enabling higher pagepool possibilities right? Would this kind of achievment be found in the cabs or the xml file that preinstalls the apps during selfprovisioning? I'ma noob and very unclear on what controls the installation paths, but if I can get a little direction (if no one knows), I'll be happy to investigate this for the sake of our VZW users (and Sprint users with MEGA-LOADED ROMS).

Any suggestions or opinions?
The way ROMs work anything they would install would have a copy within the ROM memory. Those copies usually defeat the purpose of installing files outside of ROM space.

Since storage cards are not impacted by flashing a ROM, you can usually set up shortcuts to reference things previously installed to the storage card. In some cases files may be spread around that would require restoration after a flash (or integration into a ROM), but this is typically not the case.

An other method of this is to use Teir Autoinstall to install from CABs on a storage card to storage memory during initialization.

Last edited by Kolano; 01-19-2009 at 08:04 PM.
Reply With Quote