[ROM] [January 31] CM7 - PyroMod - Stable Version 2.3.7

/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

Apps2ext (previously called apps2SD) moved all user installed apps to a secondary ext partition on your sdcard. 
This method had the advantage of being straight forward and simple, However, it had the drawback of being difficult to set up. 
This method is no longer officially supported by CyanogenMod. 
Please see the forum for device specific work-arounds if you really want apps2EXT on CyanogenMod.

Even though we have 1GB space of internal memory and a lot of the G2 users believe that is enough. 
The more apps that are installed, the slower our phones can get after time.

Apps2ext takes all of that stress from our internal storage and diverts it to our sd-ext partition if there's any. 
This results in our phones never have to worry about slowing down just because of the number of apps that we have installed.

Swap is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM. 
The computer will attempt to keep as much information as possible in RAM until the RAM is full. 
At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes. 
If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped'). 
The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.

Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory. 
Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits. 
When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed. 
In some applications, this makes it seem as if the application never closed at all. 
This is not much different from traditional swap, except that Android apps are specially programed to write out very specific information, making Android's Memory Manager more efficient that swap.