[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [Evo] (01/29/2011)
- Thread starter tkirton
- Start date
DT apps2sd uses the "a2sd" commands to work with applications. The initial invoking of DT moves all apps to the ext2/3/4 partition. "a2sd remove" moves the apps off the ex2/3/4 partition. "a2sd reinstall" moves them back.
I use Titanium Backup to check where my apps are stored: The initial page has storage data at the bottom. What you want is about at least 100MB of internal memory free, and your ext partition using a couple 100 or so MBs - depending on the number of apps you have installed.
I think the first couple of posts talk about or have links for the DT commands.
Note: the DT apps2d is different than the "native" Froyo apps2sd, and they use different parts of the sdcard.
Note 2: DT extends the "internal" memory space, so your apps may still have the "Move to SD Card" option, IIRC.
I use Titanium Backup to check where my apps are stored: The initial page has storage data at the bottom. What you want is about at least 100MB of internal memory free, and your ext partition using a couple 100 or so MBs - depending on the number of apps you have installed.
I think the first couple of posts talk about or have links for the DT commands.
Note: the DT apps2d is different than the "native" Froyo apps2sd, and they use different parts of the sdcard.
Note 2: DT extends the "internal" memory space, so your apps may still have the "Move to SD Card" option, IIRC.
thanks for the help. so if the apps still have the "Move to SD Card" option, should i move them or not? is it just a case of the OS not recognizing that a2sd has moved them to the SD card already? also, i did a "a2sd reinstall" command after a2sd was already set up. it caused a few force closes and immediately rebooted my phone. could doing that if a2sd is set up correctly cause problems or break anything?
As it seems there is still a lot of confusion.
For newcomers, all that is needed is the 'a2sd reinstall' command, this will make ALL applications run from your SD Card.
If you want to run your Dalvik Cache from your SD Card that you should consider the 'a2sd cachesdreset' command (minimum class 4 recommended)
For newcomers, all that is needed is the 'a2sd reinstall' command, this will make ALL applications run from your SD Card.
If you want to run your Dalvik Cache from your SD Card that you should consider the 'a2sd cachesdreset' command (minimum class 4 recommended)
did the 2sd reinstall and rebooted
did the a2sd cachesdreset and rebooted and using a rom that has this cooked into it.... from your list of approved roms....
Try this: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03b-signed.zip
This has a fix for a2sd and dtapp (used by the dtinstall script) that I am including in Beta 04. This should fix the issue of quick boot issue (which is Apps2SD thinking you are running it from the command line...Busybox PS kept saying that android.process.acore exists when it didn't....changed the PS command from Busybox to Toolbox.)
This has a fix for a2sd and dtapp (used by the dtinstall script) that I am including in Beta 04. This should fix the issue of quick boot issue (which is Apps2SD thinking you are running it from the command line...Busybox PS kept saying that android.process.acore exists when it didn't....changed the PS command from Busybox to Toolbox.)
Well, I didn't bother to run an a2sd check once the ROM booted up. but I currently am using 2.7.5.2 with no problems. I flashed 2.7.5.3 beta 02, wiped cache/dalvik, and rebooted.
It was then that I realized the quick boot time meant no ext3 and from there the app drawer had none of my programs in it. So, I just assumed it was because of beta status and nandroided.
Should I give beta 03a a shot?
Well, then the excuse after Froyo will be they are waiting for Gingerbread to drop.
I'll see what I can do. I can't promise anything, but I'll try.
I'll see what I can do. I can't promise anything, but I'll try.
well the excuses from the epic devs is they are waiting for official froyo to drop first!
BUT if you can port it ill be glad to test for you and ill donate.
This is the common confusion that happened when Froyo was released.
Starting with Froyo, Google included an implementation of Apps2SD that uses the existing FAT32 partition on your SD card. It creates a special folder on your SD card that is normally hidden (most File Managers can see it, though). The options you are seeing regarding moving apps to SD card is from this version of Apps2SD.
This version only moves applications. Dalvik-cache is still left in internal storage and can eat away at your phone storage, even with applications on your SD card. Plus, program data is also left on internal storage, so any web browsing and additional program information will eat away at your internal storage.
The plus side on this implementation is you don't need to know anything else and you don't need to root. Plus, if the programs are compiled using at least Froyo SDK, you can choose which programs move to SD card and which ones stay (some programs will automatically move to the SD card...Angry Birds is one example).
The minus is that some report is that it is a slower implementation of Apps2SD, plus you can't move dalvik-cache or program data. Also, this implementation is only available in version 2.2 and greater (Froyo, Gingerbread). Also, unless programs were recompiled using the Froyo or Gingerbread SDK, they will not move to the SD card without using a third party program or a rom that is designed to force the move.
Classic Apps2SD (also knows as A2SD+, Apps2EXT, SD-EXT) is an implementation that has existed since Cupcake (version 1.5..it may have existed before that). This implementation uses a native Linux (EXT2, EXT3 or EXT4) partition you create on your SD card to move your applications to. The benefit to this is that since Android's kernel is Linux, there is no special instructions to get applications to run in this partition. The trick to this implementation is that it uses a well-documented Linux function called Symbolic Links. Symbolic links perform a similar function as shortcuts do in Windows. The application directory is not located in internal storage, but on the SD card. A pointer file is created to redirect any programs to reference the SD card. This function is behind the scenes...Android will always think it is saving to internal storage when it is really saving to the SD card.
The plus side to this is that some people claim operations are faster in this implementation (since it is using native Linux filesystem). Also, using the same redirections, other files can be put on the SD card (dalvik-cache [Dalvik2SD, Cache2SD] and program data [Data2SD]), freeing up more internal space. Plus, it is compatible with all versions of Android.
The minus side to this is that you would have to repartition your SD card into two partitions (EXT2 / EXT3 / EXT4, and FAT32). You will need to root your phone. Stock roms (or the original software that came on your phone) will not work with this implementation unless it is modified. Also, you will need a third-party implementation (most roms have some form of Apps2SD/Apps2EXT implementation, so this is not usually a concern). You will usually not be able to pick and choose which program to send to external storage...it's usually all or nothing.
Starting with Froyo, Google included an implementation of Apps2SD that uses the existing FAT32 partition on your SD card. It creates a special folder on your SD card that is normally hidden (most File Managers can see it, though). The options you are seeing regarding moving apps to SD card is from this version of Apps2SD.
This version only moves applications. Dalvik-cache is still left in internal storage and can eat away at your phone storage, even with applications on your SD card. Plus, program data is also left on internal storage, so any web browsing and additional program information will eat away at your internal storage.
The plus side on this implementation is you don't need to know anything else and you don't need to root. Plus, if the programs are compiled using at least Froyo SDK, you can choose which programs move to SD card and which ones stay (some programs will automatically move to the SD card...Angry Birds is one example).
The minus is that some report is that it is a slower implementation of Apps2SD, plus you can't move dalvik-cache or program data. Also, this implementation is only available in version 2.2 and greater (Froyo, Gingerbread). Also, unless programs were recompiled using the Froyo or Gingerbread SDK, they will not move to the SD card without using a third party program or a rom that is designed to force the move.
Classic Apps2SD (also knows as A2SD+, Apps2EXT, SD-EXT) is an implementation that has existed since Cupcake (version 1.5..it may have existed before that). This implementation uses a native Linux (EXT2, EXT3 or EXT4) partition you create on your SD card to move your applications to. The benefit to this is that since Android's kernel is Linux, there is no special instructions to get applications to run in this partition. The trick to this implementation is that it uses a well-documented Linux function called Symbolic Links. Symbolic links perform a similar function as shortcuts do in Windows. The application directory is not located in internal storage, but on the SD card. A pointer file is created to redirect any programs to reference the SD card. This function is behind the scenes...Android will always think it is saving to internal storage when it is really saving to the SD card.
The plus side to this is that some people claim operations are faster in this implementation (since it is using native Linux filesystem). Also, using the same redirections, other files can be put on the SD card (dalvik-cache [Dalvik2SD, Cache2SD] and program data [Data2SD]), freeing up more internal space. Plus, it is compatible with all versions of Android.
The minus side to this is that you would have to repartition your SD card into two partitions (EXT2 / EXT3 / EXT4, and FAT32). You will need to root your phone. Stock roms (or the original software that came on your phone) will not work with this implementation unless it is modified. Also, you will need a third-party implementation (most roms have some form of Apps2SD/Apps2EXT implementation, so this is not usually a concern). You will usually not be able to pick and choose which program to send to external storage...it's usually all or nothing.
freeza
Recognized Developer
Unfortunately, no go. Boot loops.
working ver: 2.7.5.2
dalvik-cache: cache partition
apps: 2GB EXT3
card: 32GB Class 10
Last edited:
Here's what you need to know...When you are in the app manager and you see apps on the SD tab they are actually on the FAT32 partition and not on the EXT2/3/4 partition. This is common with certain apps like google sky map and angry birds because they are coded to automatically install themselves on the FAT32 partition. When you see an app on the SD tab in app manager simply click on the move to phone(which is actually not the internal storage anymore but the EXT2/3/4 partition you created). By moving it from SD to phone from the native app manager you are tricking the OS into using DT a2sd which is different from froyo apps2sd...so if an app in the app manager says you can move it to phone go ahead and do that...This is rare and usually only happens for very large apps that were already designed to use the native apps2sd...I also recently became aware that after updates to certain apps they move themselves back to the FAT32 partition do to how they are written...simply go to app manager and move to phone anything showing on the SD tab and you are good to go....
I found a tool on Market called "Autostart (Root)" by blank-online.eu. Could this be used to utilize Darktremor on roms that don't have it cooked in?
If I understand it correctly it makes it possible to run scripts that the user creates on boot.
The description isn't exactly extensive.
This has been a telepathic transmission from the Outer Limits.
If I understand it correctly it makes it possible to run scripts that the user creates on boot.
The description isn't exactly extensive.
This has been a telepathic transmission from the Outer Limits.
Try 04 Beta. And if that doesn't work...I don't know after that point. I do know I've fixed it on a couple of roms that were not moving past the boot screen.
Not in this particular case...the problem is that the EXT partition has to be mounted before the android.process.acore comes online, otherwise, you could go into a bootloop or have no applications (the latter could be fixed with the script...but Data2SD and Dalvik2SD will cause unpredictable operation).
freeza
Recognized Developer
No go on beta 4
I don't get it. 2.7.5.2 works fine. I used Amon_RA 2.2.1 recovery to partition this SD card as 2GB EXT3.
Code:
[ ] Darktremor Apps2SD Log
[ ] Started: Sun Jan 30 02:58:40 UTC 2011
[ ] File running: Main Apps2SD launch (a2sd, apps2sd or 04apps2sd)
[ ] cm.filesystem.ready does not exist and android.process.acore does not exists
[ ] Started with no parameters. Possible boot launch
[ ] Inserting parameter: boot
[ ] Directory Listing: /dev/block:
brw------- 1 0 0 7, 0 Jan 30 02:58 loop0
brw------- 1 0 0 7, 1 Jan 30 02:58 loop1
brw------- 1 0 0 7, 2 Jan 30 02:58 loop2
brw------- 1 0 0 7, 3 Jan 30 02:58 loop3
brw------- 1 0 0 7, 4 Jan 30 02:58 loop4
brw------- 1 0 0 7, 5 Jan 30 02:58 loop5
brw------- 1 0 0 7, 6 Jan 30 02:58 loop6
brw------- 1 0 0 7, 7 Jan 30 02:58 loop7
brw------- 1 0 0 179, 0 Jan 30 02:58 mmcblk0
brw------- 1 0 0 179, 1 Jan 30 02:58 mmcblk0p1
brw------- 1 0 0 179, 2 Jan 30 02:58 mmcblk0p2
brw------- 1 0 0 179, 3 Jan 30 02:58 mmcblk0p3
brw------- 1 0 0 31, 0 Jan 30 02:58 mtdblock0
brw------- 1 0 0 31, 1 Jan 30 02:58 mtdblock1
brw------- 1 0 0 31, 2 Jan 30 02:58 mtdblock2
brw------- 1 0 0 31, 3 Jan 30 02:58 mtdblock3
brw------- 1 0 0 31, 4 Jan 30 02:58 mtdblock4
brw------- 1 0 0 31, 5 Jan 30 02:58 mtdblock5
brw------- 1 0 0 31, 6 Jan 30 02:58 mtdblock6
[ ] Listing partitions currently active:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mtdblock4 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
[ ] Attempting to launch program: launcha2sd
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4 (2011-01-26)
[-] Checkpoint 1: Check for SD Card Fix and Implement.
[!] Read Ahead Buffer is greater than threshold.
Threshold is: 128
Current setting is: 128
[!] No changes will be made.
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
[-] Checkpoint 4: Determine Mount Point.
[-] Checkpoint 5: Set Parameter Variables.
[ ] Using Busybox located at: /system/xbin/busybox
[-] Checkpoint 6: Insert CyanogenMod patch.
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
[-] Checkpoint 8: Resetting Dalvik Cache Partition
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
[ ] Mounting /data/dalvik-cache
[ ] Mounting Dalvik-Cache to /cache partition successful.
[-] Checkpoint 10: Checking for existence of command parameter
[-] Checkpoint 11: Check for a2sd help command
[-] Checkpoint 12: Check for a2sd check command
[-] Checkpoint 13: Display version information.
[ ] Displaying version information: 2.7.5.3 Beta 4
[-] Checkpoint 14: Check for filesystem support.
[ ] Listing /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev inotifyfs
nodev devpts
ext3
ext2
nodev ramfs
vfat
yaffs
yaffs2
[-] Checkpoint 15: Mount partition.
[ ] Directory Listing of /dev/block
brw------- 1 0 0 7, 0 Jan 30 02:58 /dev/block/loop0
brw------- 1 0 0 7, 1 Jan 30 02:58 /dev/block/loop1
brw------- 1 0 0 7, 2 Jan 30 02:58 /dev/block/loop2
brw------- 1 0 0 7, 3 Jan 30 02:58 /dev/block/loop3
brw------- 1 0 0 7, 4 Jan 30 02:58 /dev/block/loop4
brw------- 1 0 0 7, 5 Jan 30 02:58 /dev/block/loop5
brw------- 1 0 0 7, 6 Jan 30 02:58 /dev/block/loop6
brw------- 1 0 0 7, 7 Jan 30 02:58 /dev/block/loop7
brw------- 1 0 0 179, 0 Jan 30 02:58 /dev/block/mmcblk0
brw------- 1 0 0 179, 1 Jan 30 02:58 /dev/block/mmcblk0p1
brw------- 1 0 0 179, 2 Jan 30 02:58 /dev/block/mmcblk0p2
brw------- 1 0 0 179, 3 Jan 30 02:58 /dev/block/mmcblk0p3
brw------- 1 0 0 31, 0 Jan 30 02:58 /dev/block/mtdblock0
brw------- 1 0 0 31, 1 Jan 30 02:58 /dev/block/mtdblock1
brw------- 1 0 0 31, 2 Jan 30 02:58 /dev/block/mtdblock2
brw------- 1 0 0 31, 3 Jan 30 02:58 /dev/block/mtdblock3
brw------- 1 0 0 31, 4 Jan 30 02:58 /dev/block/mtdblock4
brw------- 1 0 0 31, 5 Jan 30 02:58 /dev/block/mtdblock5
brw------- 1 0 0 31, 6 Jan 30 02:58 /dev/block/mtdblock6
[ ] Listing of partitions on /dev/block/mmcblk0
[X] No ext partitions found on /dev/block/mmcblk0.
[!] No block device /dev/block/mmcblk1
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk2
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk3
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk4
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk5
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk6
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk7
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk8
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk9
[X] Could not find a block device.
Attempting another pass to see if any
block devices may have came online since
the last scan.
[ ] Directory Listing of /dev/block
brw------- 1 0 0 7, 0 Jan 30 02:58 /dev/block/loop0
brw------- 1 0 0 7, 1 Jan 30 02:58 /dev/block/loop1
brw------- 1 0 0 7, 2 Jan 30 02:58 /dev/block/loop2
brw------- 1 0 0 7, 3 Jan 30 02:58 /dev/block/loop3
brw------- 1 0 0 7, 4 Jan 30 02:58 /dev/block/loop4
brw------- 1 0 0 7, 5 Jan 30 02:58 /dev/block/loop5
brw------- 1 0 0 7, 6 Jan 30 02:58 /dev/block/loop6
brw------- 1 0 0 7, 7 Jan 30 02:58 /dev/block/loop7
brw------- 1 0 0 179, 0 Jan 30 02:58 /dev/block/mmcblk0
brw------- 1 0 0 179, 1 Jan 30 02:58 /dev/block/mmcblk0p1
brw------- 1 0 0 179, 2 Jan 30 02:58 /dev/block/mmcblk0p2
brw------- 1 0 0 179, 3 Jan 30 02:58 /dev/block/mmcblk0p3
brw------- 1 0 0 31, 0 Jan 30 02:58 /dev/block/mtdblock0
brw------- 1 0 0 31, 1 Jan 30 02:58 /dev/block/mtdblock1
brw------- 1 0 0 31, 2 Jan 30 02:58 /dev/block/mtdblock2
brw------- 1 0 0 31, 3 Jan 30 02:58 /dev/block/mtdblock3
brw------- 1 0 0 31, 4 Jan 30 02:58 /dev/block/mtdblock4
brw------- 1 0 0 31, 5 Jan 30 02:58 /dev/block/mtdblock5
brw------- 1 0 0 31, 6 Jan 30 02:58 /dev/block/mtdblock6
[ ] Listing of partitions on /dev/block/mmcblk0
[X] No ext partitions found on /dev/block/mmcblk0.
[!] No block device /dev/block/mmcblk1
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk2
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk3
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk4
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk5
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk6
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk7
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk8
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk9
[X] Could not find a block device.
Attempting another pass to see if any
block devices may have came online since
the last scan.
[ ] Directory Listing of /dev/block
brw------- 1 0 0 7, 0 Jan 30 02:58 /dev/block/loop0
brw------- 1 0 0 7, 1 Jan 30 02:58 /dev/block/loop1
brw------- 1 0 0 7, 2 Jan 30 02:58 /dev/block/loop2
brw------- 1 0 0 7, 3 Jan 30 02:58 /dev/block/loop3
brw------- 1 0 0 7, 4 Jan 30 02:58 /dev/block/loop4
brw------- 1 0 0 7, 5 Jan 30 02:58 /dev/block/loop5
brw------- 1 0 0 7, 6 Jan 30 02:58 /dev/block/loop6
brw------- 1 0 0 7, 7 Jan 30 02:58 /dev/block/loop7
brw------- 1 0 0 179, 0 Jan 30 02:58 /dev/block/mmcblk0
brw------- 1 0 0 179, 1 Jan 30 02:58 /dev/block/mmcblk0p1
brw------- 1 0 0 179, 2 Jan 30 02:58 /dev/block/mmcblk0p2
brw------- 1 0 0 179, 3 Jan 30 02:58 /dev/block/mmcblk0p3
brw------- 1 0 0 31, 0 Jan 30 02:58 /dev/block/mtdblock0
brw------- 1 0 0 31, 1 Jan 30 02:58 /dev/block/mtdblock1
brw------- 1 0 0 31, 2 Jan 30 02:58 /dev/block/mtdblock2
brw------- 1 0 0 31, 3 Jan 30 02:58 /dev/block/mtdblock3
brw------- 1 0 0 31, 4 Jan 30 02:58 /dev/block/mtdblock4
brw------- 1 0 0 31, 5 Jan 30 02:58 /dev/block/mtdblock5
brw------- 1 0 0 31, 6 Jan 30 02:58 /dev/block/mtdblock6
[ ] Listing of partitions on /dev/block/mmcblk0
[X] No ext partitions found on /dev/block/mmcblk0.
[!] No block device /dev/block/mmcblk1
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk2
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk3
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk4
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk5
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk6
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk7
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk8
[ ] Continuing search for EXT partition.
[!] No block device /dev/block/mmcblk9
[X] Could not find a block device.
[X] No block devices are mountable.
[ ] Running Program: starta2sd
[X] No a2sd.swap environment variable found.
[ ] a2sdcmd = bootprotect
[!] BOOT PROTECTION ACTIVATED!!!
[ ] Setting File System Ready property to 1.
[ ] Program ending: starta2sd
[ ] Setting Filesystem Ready flags.
Contact Travis Kirton (rtkirton@gmail.com) for assistance.
[ ] Ending program: a2sd / apps2sd / 04apps2sd
[ ] Started with parameter: check
[ ] Directory Listing: /dev/block:
brw------- 1 0 0 7, 0 Jan 30 02:58 loop0
brw------- 1 0 0 7, 1 Jan 30 02:58 loop1
brw------- 1 0 0 7, 2 Jan 30 02:58 loop2
brw------- 1 0 0 7, 3 Jan 30 02:58 loop3
brw------- 1 0 0 7, 4 Jan 30 02:58 loop4
brw------- 1 0 0 7, 5 Jan 30 02:58 loop5
brw------- 1 0 0 7, 6 Jan 30 02:58 loop6
brw------- 1 0 0 7, 7 Jan 30 02:58 loop7
brw------- 1 0 0 179, 0 Jan 30 02:58 mmcblk0
brw------- 1 0 0 179, 1 Jan 30 02:58 mmcblk0p1
brw------- 1 0 0 179, 2 Jan 30 02:58 mmcblk0p2
brw------- 1 0 0 179, 3 Jan 30 02:58 mmcblk0p3
brw------- 1 0 0 31, 0 Jan 30 02:58 mtdblock0
brw------- 1 0 0 31, 1 Jan 30 02:58 mtdblock1
brw------- 1 0 0 31, 2 Jan 30 02:58 mtdblock2
brw------- 1 0 0 31, 3 Jan 30 02:58 mtdblock3
brw------- 1 0 0 31, 4 Jan 30 02:58 mtdblock4
brw------- 1 0 0 31, 5 Jan 30 02:58 mtdblock5
brw------- 1 0 0 31, 6 Jan 30 02:58 mtdblock6
drwxr-xr-x 2 0 0 120 Jan 30 02:58 vold
[ ] Listing partitions currently active:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mtdblock4 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
/dev/block/mtdblock5 /data/dalvik-cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[ ] Attempting to launch program: launcha2sd
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4 (2011-01-26)
[-] Checkpoint 1: Check for SD Card Fix and Implement.
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
[-] Checkpoint 4: Determine Mount Point.
[-] Checkpoint 5: Set Parameter Variables.
[ ] Using Busybox located at: /system/xbin/busybox
[-] Checkpoint 6: Insert CyanogenMod patch.
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
[-] Checkpoint 8: Resetting Dalvik Cache Partition
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
[-] Checkpoint 10: Checking for existence of command parameter
[-] Checkpoint 11: Check for a2sd help command
[-] Checkpoint 12: Check for a2sd check command
[ ] Attempting to execute: chka2sd
[ ] Starting Program: chka2sd
Darktremor 2.7.5.3 Beta 4 Apps2SD Status Report
===================================================================================
Legend: [*]=Setting is correct
[!]=Setting is correct, but not optimal.
[X]=Setting is incorrect and needs to be fixed or option is not available.
===================================================================================
Block Device - [X] Not Found
- [X] SD card cannot mount
[ ] Returned to file: launcha2sd
[ ] Ending program: launcha2sd
[ ] Ending program: a2sd / apps2sd / 04apps2sd
Last edited:
Does that have something to do with /proc/filesystems? Mine mentions ext2 and ext3.
I looked around in my init.rc as well. I don't remember seeing anything that your dev guide said was necessary, but I am the rankest of amateurs with android/*nix.
This has been a telepathic transmission from the Outer Limits.
I can tell you the difference: 2.7.5.2 does a blind mount (it assumes your EXT is either on mmcblk0p2 or mmcblk1p2...you can't have it in any other position)
2.7.5.3 uses a combination of Busybox FDisk, Busybox Grep and Busybox Awk to mount your partition.
Since FDisk wasn't used in the previous version, I would suspect that is the issue.
What ROM are you using and I'll check it out. Maybe I can get a workaround for you.
2.7.5.3 uses a combination of Busybox FDisk, Busybox Grep and Busybox Awk to mount your partition.
Since FDisk wasn't used in the previous version, I would suspect that is the issue.
What ROM are you using and I'll check it out. Maybe I can get a workaround for you.
No go on beta 4
I don't get it. 2.7.5.2 works fine. I used Amon_RA 2.2.1 recovery to partition this SD card as 2GB EXT3.
Code:[ ] Darktremor Apps2SD Log [ ] Started: Sun Jan 30 02:58:40 UTC 2011 [ ] File running: Main Apps2SD launch (a2sd, apps2sd or 04apps2sd) [ ] cm.filesystem.ready does not exist and android.process.acore does not exists [ ] Started with no parameters. Possible boot launch [ ] Inserting parameter: boot [ ] Directory Listing: /dev/block: brw------- 1 0 0 7, 0 Jan 30 02:58 loop0 brw------- 1 0 0 7, 1 Jan 30 02:58 loop1 brw------- 1 0 0 7, 2 Jan 30 02:58 loop2 brw------- 1 0 0 7, 3 Jan 30 02:58 loop3 brw------- 1 0 0 7, 4 Jan 30 02:58 loop4 brw------- 1 0 0 7, 5 Jan 30 02:58 loop5 brw------- 1 0 0 7, 6 Jan 30 02:58 loop6 brw------- 1 0 0 7, 7 Jan 30 02:58 loop7 brw------- 1 0 0 179, 0 Jan 30 02:58 mmcblk0 brw------- 1 0 0 179, 1 Jan 30 02:58 mmcblk0p1 brw------- 1 0 0 179, 2 Jan 30 02:58 mmcblk0p2 brw------- 1 0 0 179, 3 Jan 30 02:58 mmcblk0p3 brw------- 1 0 0 31, 0 Jan 30 02:58 mtdblock0 brw------- 1 0 0 31, 1 Jan 30 02:58 mtdblock1 brw------- 1 0 0 31, 2 Jan 30 02:58 mtdblock2 brw------- 1 0 0 31, 3 Jan 30 02:58 mtdblock3 brw------- 1 0 0 31, 4 Jan 30 02:58 mtdblock4 brw------- 1 0 0 31, 5 Jan 30 02:58 mtdblock5 brw------- 1 0 0 31, 6 Jan 30 02:58 mtdblock6 [ ] Listing partitions currently active: rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 /dev/block/mtdblock4 /system yaffs2 ro,relatime 0 0 /dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,relatime 0 0 /dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,relatime 0 0 tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0 [ ] Attempting to launch program: launcha2sd __ _____ | \ | | | | |__/ | Darktremor Apps2SD 2.7.5.3 Beta 4 (2011-01-26) [-] Checkpoint 1: Check for SD Card Fix and Implement. [!] Read Ahead Buffer is greater than threshold. Threshold is: 128 Current setting is: 128 [!] No changes will be made. [-] Checkpoint 2: Run Dalvik Heap Program (if exists). [-] Checkpoint 3: Run Set Low Memory Killer Program (if exists). [-] Checkpoint 4: Determine Mount Point. [-] Checkpoint 5: Set Parameter Variables. [ ] Using Busybox located at: /system/xbin/busybox [-] Checkpoint 6: Insert CyanogenMod patch. [-] Checkpoint 7: Complete Dalvik Cache Move (if applicable). [-] Checkpoint 8: Resetting Dalvik Cache Partition [-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable) [ ] Mounting /data/dalvik-cache [ ] Mounting Dalvik-Cache to /cache partition successful. [-] Checkpoint 10: Checking for existence of command parameter [-] Checkpoint 11: Check for a2sd help command [-] Checkpoint 12: Check for a2sd check command [-] Checkpoint 13: Display version information. [ ] Displaying version information: 2.7.5.3 Beta 4 [-] Checkpoint 14: Check for filesystem support. [ ] Listing /proc/filesystems nodev sysfs nodev rootfs nodev bdev nodev proc nodev cgroup nodev tmpfs nodev debugfs nodev sockfs nodev pipefs nodev anon_inodefs nodev inotifyfs nodev devpts ext3 ext2 nodev ramfs vfat yaffs yaffs2 [-] Checkpoint 15: Mount partition. [ ] Directory Listing of /dev/block brw------- 1 0 0 7, 0 Jan 30 02:58 /dev/block/loop0 brw------- 1 0 0 7, 1 Jan 30 02:58 /dev/block/loop1 brw------- 1 0 0 7, 2 Jan 30 02:58 /dev/block/loop2 brw------- 1 0 0 7, 3 Jan 30 02:58 /dev/block/loop3 brw------- 1 0 0 7, 4 Jan 30 02:58 /dev/block/loop4 brw------- 1 0 0 7, 5 Jan 30 02:58 /dev/block/loop5 brw------- 1 0 0 7, 6 Jan 30 02:58 /dev/block/loop6 brw------- 1 0 0 7, 7 Jan 30 02:58 /dev/block/loop7 brw------- 1 0 0 179, 0 Jan 30 02:58 /dev/block/mmcblk0 brw------- 1 0 0 179, 1 Jan 30 02:58 /dev/block/mmcblk0p1 brw------- 1 0 0 179, 2 Jan 30 02:58 /dev/block/mmcblk0p2 brw------- 1 0 0 179, 3 Jan 30 02:58 /dev/block/mmcblk0p3 brw------- 1 0 0 31, 0 Jan 30 02:58 /dev/block/mtdblock0 brw------- 1 0 0 31, 1 Jan 30 02:58 /dev/block/mtdblock1 brw------- 1 0 0 31, 2 Jan 30 02:58 /dev/block/mtdblock2 brw------- 1 0 0 31, 3 Jan 30 02:58 /dev/block/mtdblock3 brw------- 1 0 0 31, 4 Jan 30 02:58 /dev/block/mtdblock4 brw------- 1 0 0 31, 5 Jan 30 02:58 /dev/block/mtdblock5 brw------- 1 0 0 31, 6 Jan 30 02:58 /dev/block/mtdblock6 [ ] Listing of partitions on /dev/block/mmcblk0 [X] No ext partitions found on /dev/block/mmcblk0. [!] No block device /dev/block/mmcblk1 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk2 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk3 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk4 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk5 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk6 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk7 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk8 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk9 [X] Could not find a block device. Attempting another pass to see if any block devices may have came online since the last scan. [ ] Directory Listing of /dev/block brw------- 1 0 0 7, 0 Jan 30 02:58 /dev/block/loop0 brw------- 1 0 0 7, 1 Jan 30 02:58 /dev/block/loop1 brw------- 1 0 0 7, 2 Jan 30 02:58 /dev/block/loop2 brw------- 1 0 0 7, 3 Jan 30 02:58 /dev/block/loop3 brw------- 1 0 0 7, 4 Jan 30 02:58 /dev/block/loop4 brw------- 1 0 0 7, 5 Jan 30 02:58 /dev/block/loop5 brw------- 1 0 0 7, 6 Jan 30 02:58 /dev/block/loop6 brw------- 1 0 0 7, 7 Jan 30 02:58 /dev/block/loop7 brw------- 1 0 0 179, 0 Jan 30 02:58 /dev/block/mmcblk0 brw------- 1 0 0 179, 1 Jan 30 02:58 /dev/block/mmcblk0p1 brw------- 1 0 0 179, 2 Jan 30 02:58 /dev/block/mmcblk0p2 brw------- 1 0 0 179, 3 Jan 30 02:58 /dev/block/mmcblk0p3 brw------- 1 0 0 31, 0 Jan 30 02:58 /dev/block/mtdblock0 brw------- 1 0 0 31, 1 Jan 30 02:58 /dev/block/mtdblock1 brw------- 1 0 0 31, 2 Jan 30 02:58 /dev/block/mtdblock2 brw------- 1 0 0 31, 3 Jan 30 02:58 /dev/block/mtdblock3 brw------- 1 0 0 31, 4 Jan 30 02:58 /dev/block/mtdblock4 brw------- 1 0 0 31, 5 Jan 30 02:58 /dev/block/mtdblock5 brw------- 1 0 0 31, 6 Jan 30 02:58 /dev/block/mtdblock6 [ ] Listing of partitions on /dev/block/mmcblk0 [X] No ext partitions found on /dev/block/mmcblk0. [!] No block device /dev/block/mmcblk1 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk2 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk3 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk4 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk5 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk6 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk7 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk8 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk9 [X] Could not find a block device. Attempting another pass to see if any block devices may have came online since the last scan. [ ] Directory Listing of /dev/block brw------- 1 0 0 7, 0 Jan 30 02:58 /dev/block/loop0 brw------- 1 0 0 7, 1 Jan 30 02:58 /dev/block/loop1 brw------- 1 0 0 7, 2 Jan 30 02:58 /dev/block/loop2 brw------- 1 0 0 7, 3 Jan 30 02:58 /dev/block/loop3 brw------- 1 0 0 7, 4 Jan 30 02:58 /dev/block/loop4 brw------- 1 0 0 7, 5 Jan 30 02:58 /dev/block/loop5 brw------- 1 0 0 7, 6 Jan 30 02:58 /dev/block/loop6 brw------- 1 0 0 7, 7 Jan 30 02:58 /dev/block/loop7 brw------- 1 0 0 179, 0 Jan 30 02:58 /dev/block/mmcblk0 brw------- 1 0 0 179, 1 Jan 30 02:58 /dev/block/mmcblk0p1 brw------- 1 0 0 179, 2 Jan 30 02:58 /dev/block/mmcblk0p2 brw------- 1 0 0 179, 3 Jan 30 02:58 /dev/block/mmcblk0p3 brw------- 1 0 0 31, 0 Jan 30 02:58 /dev/block/mtdblock0 brw------- 1 0 0 31, 1 Jan 30 02:58 /dev/block/mtdblock1 brw------- 1 0 0 31, 2 Jan 30 02:58 /dev/block/mtdblock2 brw------- 1 0 0 31, 3 Jan 30 02:58 /dev/block/mtdblock3 brw------- 1 0 0 31, 4 Jan 30 02:58 /dev/block/mtdblock4 brw------- 1 0 0 31, 5 Jan 30 02:58 /dev/block/mtdblock5 brw------- 1 0 0 31, 6 Jan 30 02:58 /dev/block/mtdblock6 [ ] Listing of partitions on /dev/block/mmcblk0 [X] No ext partitions found on /dev/block/mmcblk0. [!] No block device /dev/block/mmcblk1 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk2 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk3 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk4 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk5 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk6 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk7 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk8 [ ] Continuing search for EXT partition. [!] No block device /dev/block/mmcblk9 [X] Could not find a block device. [X] No block devices are mountable. [ ] Running Program: starta2sd [X] No a2sd.swap environment variable found. [ ] a2sdcmd = bootprotect [!] BOOT PROTECTION ACTIVATED!!! [ ] Setting File System Ready property to 1. [ ] Program ending: starta2sd [ ] Setting Filesystem Ready flags. Contact Travis Kirton (rtkirton@gmail.com) for assistance. [ ] Ending program: a2sd / apps2sd / 04apps2sd [ ] Started with parameter: check [ ] Directory Listing: /dev/block: brw------- 1 0 0 7, 0 Jan 30 02:58 loop0 brw------- 1 0 0 7, 1 Jan 30 02:58 loop1 brw------- 1 0 0 7, 2 Jan 30 02:58 loop2 brw------- 1 0 0 7, 3 Jan 30 02:58 loop3 brw------- 1 0 0 7, 4 Jan 30 02:58 loop4 brw------- 1 0 0 7, 5 Jan 30 02:58 loop5 brw------- 1 0 0 7, 6 Jan 30 02:58 loop6 brw------- 1 0 0 7, 7 Jan 30 02:58 loop7 brw------- 1 0 0 179, 0 Jan 30 02:58 mmcblk0 brw------- 1 0 0 179, 1 Jan 30 02:58 mmcblk0p1 brw------- 1 0 0 179, 2 Jan 30 02:58 mmcblk0p2 brw------- 1 0 0 179, 3 Jan 30 02:58 mmcblk0p3 brw------- 1 0 0 31, 0 Jan 30 02:58 mtdblock0 brw------- 1 0 0 31, 1 Jan 30 02:58 mtdblock1 brw------- 1 0 0 31, 2 Jan 30 02:58 mtdblock2 brw------- 1 0 0 31, 3 Jan 30 02:58 mtdblock3 brw------- 1 0 0 31, 4 Jan 30 02:58 mtdblock4 brw------- 1 0 0 31, 5 Jan 30 02:58 mtdblock5 brw------- 1 0 0 31, 6 Jan 30 02:58 mtdblock6 drwxr-xr-x 2 0 0 120 Jan 30 02:58 vold [ ] Listing partitions currently active: rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 /dev/block/mtdblock4 /system yaffs2 ro,relatime 0 0 /dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev,relatime 0 0 /dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,relatime 0 0 tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0 /dev/block/mtdblock5 /data/dalvik-cache yaffs2 rw,nosuid,nodev,relatime 0 0 /dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 [ ] Attempting to launch program: launcha2sd __ _____ | \ | | | | |__/ | Darktremor Apps2SD 2.7.5.3 Beta 4 (2011-01-26) [-] Checkpoint 1: Check for SD Card Fix and Implement. [-] Checkpoint 2: Run Dalvik Heap Program (if exists). [-] Checkpoint 3: Run Set Low Memory Killer Program (if exists). [-] Checkpoint 4: Determine Mount Point. [-] Checkpoint 5: Set Parameter Variables. [ ] Using Busybox located at: /system/xbin/busybox [-] Checkpoint 6: Insert CyanogenMod patch. [-] Checkpoint 7: Complete Dalvik Cache Move (if applicable). [-] Checkpoint 8: Resetting Dalvik Cache Partition [-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable) [-] Checkpoint 10: Checking for existence of command parameter [-] Checkpoint 11: Check for a2sd help command [-] Checkpoint 12: Check for a2sd check command [ ] Attempting to execute: chka2sd [ ] Starting Program: chka2sd Darktremor 2.7.5.3 Beta 4 Apps2SD Status Report =================================================================================== Legend: [*]=Setting is correct [!]=Setting is correct, but not optimal. [X]=Setting is incorrect and needs to be fixed or option is not available. =================================================================================== Block Device - [X] Not Found - [X] SD card cannot mount [ ] Returned to file: launcha2sd [ ] Ending program: launcha2sd [ ] Ending program: a2sd / apps2sd / 04apps2sd
freeza
Recognized Developer
Fresh 3.5.0.1, but busybox version is like 1.18 or something. would that make any difference? I also have a bunch of crap stripped out of it.
That's strange...I tested 04 Beta on Fresh Evo 3.5.0.1 before I released it (that was earlier today) and it worked fine. In fact, I tested it with two different sets of code, the last code is the release code.
It shouldn't...but if you want to, run a2sd usedtbusybox and it will use the Busybox supplied with the Darktremor package (/system/bin/busybox.a2sd). See if that helps.
It may be you'll have to reflash Fresh Evo 3.5.0.1 on top of itself.
It shouldn't...but if you want to, run a2sd usedtbusybox and it will use the Busybox supplied with the Darktremor package (/system/bin/busybox.a2sd). See if that helps.
It may be you'll have to reflash Fresh Evo 3.5.0.1 on top of itself.
freeza
Recognized Developer
I'll try that.
I'm trying to remember if I removed anything of significance. Would the SD card read_ahead fix going around have anything to do with it? I changed mine to 512KB...or perhaps recovery version? I am now using amon_ra's 2.3 test04...umm 32MB vm_heap size...sense apps almost entirely gone.
Could be. Darktremor has the SD card fix in it (which reminds me, I have to add that to changelog)...but I set mine to 128 as described by documents.
When I was experimenting with it, I set it to 256 and killed my battery (and I have one of those big Seidio 3500mAh battery). I had to wait for it to recharge in my Hero (as my Evo wouldn't recharge anything until I took the battery out for about 10 minutes...had a smaller battery I was trying to use until the big battery charged.)
Unless my experience was completely coincidence, my experience is that anything bigger than 128 and the phone becomes unpredictable. Not really sure why, though.
When I was experimenting with it, I set it to 256 and killed my battery (and I have one of those big Seidio 3500mAh battery). I had to wait for it to recharge in my Hero (as my Evo wouldn't recharge anything until I took the battery out for about 10 minutes...had a smaller battery I was trying to use until the big battery charged.)
Unless my experience was completely coincidence, my experience is that anything bigger than 128 and the phone becomes unpredictable. Not really sure why, though.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
9Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.2
FYI - GParted can resize the partitions while preserving data.
However the above method is more reliable.2
Wipe everything, verify that your partition is there by wiping the SD-ext, then flash your rom. Let it boot up, then verify in Titanitum Backup that the EXT partition is still there. If so, then per our discussion in another thread, download Terminal Emulator and move the cache to the SD (a2sd cachesdreset). The phone will reboot and take a while to pull up your home screen (its rebuilding your cache on the SD).2This is the common confusion that happened when Froyo was released.
Starting with Froyo, Google included an implementation of Apps2SD that uses the existing FAT32 partition on your SD card. It creates a special folder on your SD card that is normally hidden (most File Managers can see it, though). The options you are seeing regarding moving apps to SD card is from this version of Apps2SD.
This version only moves applications. Dalvik-cache is still left in internal storage and can eat away at your phone storage, even with applications on your SD card. Plus, program data is also left on internal storage, so any web browsing and additional program information will eat away at your internal storage.
The plus side on this implementation is you don't need to know anything else and you don't need to root. Plus, if the programs are compiled using at least Froyo SDK, you can choose which programs move to SD card and which ones stay (some programs will automatically move to the SD card...Angry Birds is one example).
The minus is that some report is that it is a slower implementation of Apps2SD, plus you can't move dalvik-cache or program data. Also, this implementation is only available in version 2.2 and greater (Froyo, Gingerbread). Also, unless programs were recompiled using the Froyo or Gingerbread SDK, they will not move to the SD card without using a third party program or a rom that is designed to force the move.
Classic Apps2SD (also knows as A2SD+, Apps2EXT, SD-EXT) is an implementation that has existed since Cupcake (version 1.5..it may have existed before that). This implementation uses a native Linux (EXT2, EXT3 or EXT4) partition you create on your SD card to move your applications to. The benefit to this is that since Android's kernel is Linux, there is no special instructions to get applications to run in this partition. The trick to this implementation is that it uses a well-documented Linux function called Symbolic Links. Symbolic links perform a similar function as shortcuts do in Windows. The application directory is not located in internal storage, but on the SD card. A pointer file is created to redirect any programs to reference the SD card. This function is behind the scenes...Android will always think it is saving to internal storage when it is really saving to the SD card.
The plus side to this is that some people claim operations are faster in this implementation (since it is using native Linux filesystem). Also, using the same redirections, other files can be put on the SD card (dalvik-cache [Dalvik2SD, Cache2SD] and program data [Data2SD]), freeing up more internal space. Plus, it is compatible with all versions of Android.
The minus side to this is that you would have to repartition your SD card into two partitions (EXT2 / EXT3 / EXT4, and FAT32). You will need to root your phone. Stock roms (or the original software that came on your phone) will not work with this implementation unless it is modified. Also, you will need a third-party implementation (most roms have some form of Apps2SD/Apps2EXT implementation, so this is not usually a concern). You will usually not be able to pick and choose which program to send to external storage...it's usually all or nothing.
1You have to root...otherwise, the phone won't give you sufficient permissions for Darktremor Apps2SD to work
You then have a second problem. No unmodified Stock ROM can run any version of Apps2SD (other than Froyo/Gingerbread) as those ROMs will not execute boot scripts. You'll need to switch to a different ROM.
New posts
-
How To Guide How to convert from ColorOS to Global ..US.. India On Chinese Oneplus 12- Latest: MorphlinG12195
-
-