[Desire Android Development] tkirton:
Just install it.

When an A2SD+ needs to be "activated", the developer has code that turns on or off a flag. I know Damaged and TrevE (TrevE makes a competing Apps2SD) uses a property file that has certain variables in it. These are flag variables and they are used to control the program.

Darktremor uses a similar design...but instead of using a property file to control the program, I use a series of flag files. These files always reside in the /data directory and start with a dot (".") as part of the filename. Here are the list of flag files:

.noa2sd - prevents moving of apps and private apps to the SD card. The EXT partition will still mount, in case you change your mind.

.noswap - prevents using the swap partition on the SD card for a swap file.

.zipalign - performs a zipalign optimization upon every boot

.dalvikcache - automatically moves the dalvik-cache to the SD card

.dcpartition - automatically moves the dalvik-cache to the cache partition (/cache)

.lmoptimum - Sets optimum settings for low memory killer

.lmstrict - Sets strict settings for low memory killer

.lmaggressive - Sets aggressive memory killing settings for low memory killer

.lmextreme - Sets extreme memory killing settings for low memory killer

.lmultimate - Sets highest memory killing settings for low memory killer.

.lmmoderate - Sets moderate memory killing settings for low memory killer (lowest setting other than system default).

.mvdalvik - A temporary flag file used by a2sd nocache and a2sd nocachereset...this is the dalvik-cache to be moved to /data/dalvik-cache when the dalvik-cache mount cannot be terminated without a reboot.

Darktremor incorporates three different types of launch codes: Direct to /system/bin/a2sd, using Busybox Run-Parts on /system/etc/init.d, and the latest CyanogenMod method of using /system/bin/sysinit script to launch Apps2sd. As long as the rom uses one of these methods, it will launch.

If you already have the launch command (a compatible apps2sd rom) and you have the entire rom unzipped somewhere (along with someway to sign it once you assemble it), then you simply do the following:

1. Unzip http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-signed.zip into a separate directory.

EDIT: That link is for the soon to be released 2.7.5.2. Here's the link to 2.7.5.1: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.1-adv-signed.zip

2. Copy the contents of /system/bin from Darktremor zip file to the /system/bin folder of your disassembled ROM.

3. Copy the a2sd program in /system/xbin from Darktremor zip to the /system/xbin founder of your disassembled ROM.

4. Copy the contents of /data from Darktremor zip file to the /data folder of your disassembled ROM.

5. Look at your /system/etc/init.d folder in your ROM and look for any file that starts with "04". If you don't have a /system/etc/init.d folder, skip to Step 6

a. If you do have a file that starts with "04", look for the next empty number you can use (i.e. "05"). Copy the /system/etc/init.d/04apps2sd file from the Darktremor zip to XXapps2sd file on your roms /system/etc/init.d, replacing the XX with the empty number you found. (i.e. If there's a file that starts with "04" and "05", but not one that starts with "06", then you copy 04apps2sd into your rom and name it 06apps2sd).

b. If you do not have a file that starts with "04", simply copy /system/etc/init.d/04apps2sd from the Darktremor zip to /system/etc/init.d on your ROM.

c. Remove any files (other than the one you just added) that have the words "apps2sd", "a2sd", "cache", "dalvik" in the name from your /system/etc/init.d folder in your rom. These programs, created by other rom developers, can interfere with Darktremor Apps2SD.

6. That should be it...I can't think of anything else you need to do. Zip the contents of your ROM into a zip folder and then digitally sign it. Test it and see if it works.