Darktremor A2SD version 2.7 Update 3r1 (2010-06-26)
18 Roms install with Darktremor A2SD across 6 different Android phones.
Note: 2.7 update 3r1 fixes an issue where dalvik-cache was automatically loading to the SD card on boot. This may have been causing issues with some of the roms out there (especially Blue Echo 2.1.4). Thanks to Papa Smurf151 and Flipzmode for bringing this to my attention.
2.7 update 3r1 also has a2sd functions moved to launcha2sd...this program runs under bash instead of sh. This will help with roms that have issues where the open bracket on an IF statement is treated as a command rather than a condition ( [: not found )
Features for 2.7 update 3:
2.7 update 3 is all about dalvik-cache.
I noticed that some rom developers have been putting their dalvik-cache onto the /cache partition. This partition is a large (usually as large as the /data partition) that is mostly unused (I'm sure it is needed for installs, etc). I've taken that idea and applied it to Darktremor A2SD.
If you are running a rom that has uses the cache partition to store dalvik-cache, this update will not force it to move back to the internal storage.
It introduces new algorithms to detect dalvik-cache on cache partition. It also adds two new options:
a2sd cachepart - Moves the dalvik-cache to the cache partition
a2sd cachesd - Moves the dalvik-cache to the SD card (same as a2sd cache...eventually, a2sd cache will be deprecated).
If you experience boot loops when you move the dalvik-cache to the cache partition, go into adb shell while the phone is boot looping and run the following commands:
a2sd nocache (if you want to put your dalvik-cache on your internal storage) or a2sd cachesd (if you want to put your dalvik-cache on your SD card)
a2sd resetcache (this clears the dalvik-cache and reboots)
Click to expand...
Click to collapse
If you are using Modaco's ROM, Darktremor A2SD isn't guaranteed to work with this rom. I'm investigating as to why, but keep in mind that if the phone goes into a bootloop, restore your phone via Nandroid. If you are submitting a problem to me when using Modaco ROM, include a logcat when the phone first boots. This will help me try to identify the issue and possibly release a workaround update.
Click to expand...
Click to collapse
Do a nandroid backup first of your working ROM. This is in case you find a bug (or run into an issue) and have to reload your phone.
Click to expand...
Click to collapse
If you are visiting the Hero CDMA forums and you use another Android-based phone, I encourage you to try the Darktremor A2SD on your phone. I would like to expand this program beyond the Hero CDMA if possible.
Look in the credits below to see the Roms that have been tested.
Here's the program:
2.7 Update 3r1 - http://www.darktremor.info/files/a2sd/a2sd-2.7-update3r1-signed.zip
Requirement: An ext2, ext3, or ext4 partition on your SD Card and a custom Rom that supports Apps2SD or A2SD
A2SD will not work on stock HTC Rom as stock roms do not have any method of launching A2SD in the boot image (unless they have been modified to work with A2SD). Try one of the many custom roms available if you want to use A2SD.
What is this?
A2SD (also known as Apps2SD) is a script that runs when you phone boots. Many of the ROM developers include the script in one form or another. Originally based on Cyanogen's Apps2SD, this script will allow a user to free up more storage space on their phone.
How does it do it? It uses an ext2, ext3 or ext4 partition (if one exists) to move all your free and purchased apps (not core apps) to the ext2/ext/ext4 partition on your SD card. It also tricks Android into thinking it is storing your programs in the internal storage space by linking the install directories (/data/app and /data/app-private) to similar directories on the sd card.
Current roms that have Darktremor A2SD built in:
Note: Be careful when choosing a rom. Flash a rom not designed for your phone and you may brick it.
I'm not responsible for bricked phones due to wrong rom flashed. Flash at your own risk.
Fresh Rom 2.1.2 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=681856
FreshToast 2.1 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=683746
Sprint 2.1 Stock ROM (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=703267
ZenEXP 0.9.6.2 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=666967
Buufed 1.7.2 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=689142
Blue Echo 2.1.5 (CDMA Hero) - http://forum.xda-developers.com/showthread.php?t=699975
HoneyBun v.3 (CDMA Hero) - http://forum.androidcentral.com/htc-hero-roms-hacks/14674-honeybun-v1-based-off-official-ruu.html
Click to expand...
Click to collapse
ZenExp Eris Expresso Rev 7 (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=688687
Fresh Rom 2.1.1 for Eris (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=674170
Buufed 1.7.2 for Eris (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=690902
Eris Lightning 3.02 (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=675957
Evil Eris 2.0.1 (HTC Eris) - http://forum.xda-developers.com/showthread.php?t=650302
Click to expand...
Click to collapse
Fresh Evo 0.3 (HTC Evo) - http://forum.xda-developers.com/showthread.php?t=700448
Supersonic 2.0 (HTC Evo) - http://forum.xda-developers.com/showthread.php?t=698594
Click to expand...
Click to collapse
Daguu Espresso Rom v1.2 (GSM Hero) - http://forum.xda-developers.com/showthread.php?t=693069
Click to expand...
Click to collapse
Kang-o-rama 0.9 Froyo ROM (Nexus One) - http://forum.xda-developers.com/showthread.php?p=6973422
Click to expand...
Click to collapse
Pulse Oscillation Rom R7B (T-Mobile Pulse) - http://android.modaco.com/content/t...daco-com/309811/pulse-2-1-oscillation-rom-r7/
FLB-Mod (T-Mobile Pulse) - http://android.modaco.com/content/t...sed-vanilla-ish-rom-with-tweaks/#entry1303318
Note: T-Mobile Pulse is made by Huawei, which puts this as the first phone outside the HTC phones that Darktremor A2SD works on. There's hope for the Samsung Moment yet.
Click to expand...
Click to collapse
I'm may have left some off this list. If your rom isn't on this list, send me a PM with the name and location (thread) so I know how to properly catalog it.
Click to expand...
Click to collapse
To find out all the features you can do with Darktremor A2SD, type /system/bin/a2sd help in the phone's terminal shell (or adb shell).
HOW TO INSTALL:
Since you are flashing this version to your phone, do a nandroid backup of your phone before starting these instructions. Also, it is preferred you use RA 1.6.2 Recovery or Godspeed Recovery (there may be issues with earlier recovery versions...I am checking this out).
1. Download the program above.
2. Determine if you have setup your SD Card with an ext partition
If you have setup your SD card already (existing users of A2SD...any version):
a. Copy the program to your SD card. One way of doing that is to use ADB by typing this command:
adb push a2sd-2.7-3r1-signed.zip /sdcard/a2sd-2.7-3r1-signed.zip
b. Reboot into recovery
Click to expand...
Click to collapse
If you have not setup your SD card (for those new to A2SD):
a. BACKUP YOUR SD CARD TO YOUR COMPUTER. Can't stress this enough, as partitioning will wipe the entire card.
b. Reboot into recovery
c. In Android System Recovery, select Partition sdcard
d. In the Partition sdcard menu, select Partition SD
e. Follow the instructions on the phone to partition your SD card. You can optionally set a swap file while you are partitioning your SD card.
f. In the Partition sdcard menu, select SD:ext2 to ext3. Follow the instructions on the screen.
g. Only perform this step if you want ext4 and your ROM supports it: In the partition sdcard menu, select SD:ext3 to ext4. Follow the instructions on the sdcard.
h. Press the back button on the phone to go back to the main menu.
i. Put the A2SD file on the SD card (and all your other files you backed up earlier) by selecting USB-MS toggle and transfer the files to your computer.
Click to expand...
Click to collapse
3. In recovery, select Flash zip from sdcard.
4. In Flash zip from sdcard, select the a2sd package file you downloaded earlier. Press HOME to flash.
5. Reboot phone.
Click to expand...
Click to collapse
NOTE: Due to an issue with the Sprint Hero source code, ext4 partitions may only work intermittently. You may not want to use an ext4 partition unless the ROM you are using is certified to have a working ext4 partition. If you have issues with ext4, repartition your SD card for ext3.
Click to expand...
Click to collapse
If you apply this program and your market suddenly stops working, perform the following steps:
1. Remount your internal storage to read-write by typing adb remount
2. Go into your phone's terminal by typing adb shell
3. Type /system/bin/a2sd fixmarket. This will relocate the market to /system/app and allows you to choose it in the All Programs screen. You will need to drag it back onto your desktop if you want it there.
Click to expand...
Click to collapse
NOTE: If you apply Darktremor A2SD 2.7 and still notice internal storage is decreasing, this is due to the dalvik-cache not being moved. By default, Darktremor A2SD will not move the dalvik-cache on boot.
If you want to move the dalvik-cache to the sd card, type:
a2sd cache (old command to move dalvik to SD card - will be phased out soon)
a2sd cachesd (new command to move dalvik to SD card)
a2sd cachepart (command to move dalvik to cache partition)
Make sure your SD card is at least a Class 4 before doing this, otherwise you may run into performance issues, unless you move the dalvik to the cache partition.
You still have other caches (i.e. browser caches) and other data being stored and updated in Internal Storage, so the number of free space will continue to drop, but at a slower rate (unless you are engage in heavy web surfing, tweeting or facebook socializing.)
Click to expand...
Click to collapse
What does this program do:
1. Moves applications to the sd card
2. Moves dalvik-cache to the sd card (a2sd cachesd) or to the cache partition (a2sd cachepart...when the rom supports it). Not active on boot by default.
3. Activates swap partition if one exists (a2sd swap to activate, a2sd noswap to deactivate)
4. Allows the user to deactivate a2sd without removing the ext2/ext3 partition (a2sd remove to deactivate, a2sd install to activate)
5. Allows the user to restore dalvik-cache back to the main memory (a2sd nocache)
6. Allows the user to deactivate swap (a2sd noswap to deactivate, a2sd swap to activate)
7. Creates the /system/sd mount if one doesn't exists.
8. Checks the symlinks and flag files. Reports to the user what needs to be repaired. (a2sd check)
9. Repair symlinks based on active flag files. (a2sd repair)
10. Zipaligns all programs in /data/app and /data/app-private. Using the align command, /system/app will also be zipaligned. You can turn on and off ZipAlign (a2sd zipalign / a2sd nozipalign). Not active on boot by default.
11. Wipes dalvik-cache without the need to go into a recovery partition (a2sd resetcache)
12. Checks how much space is being used on your ext partition (a2sd diskspace)
13. Repairs missing or corrupted market in Android 2.1 (a2sd fixmarket)
14. Uses its own Busybox installation to ensure stability (/system/bin/busybox.a2sd)
How to tell if it is working:
1. On your computer in the Android SDK Tools directory, type adb shell
2. In the adb shell, type /system/bin/a2sd check
3. Read the report. It will tell you if all is well. If you see anything with [X], type a2sd repair
If you want to move the apps to the SD card (when the program doesn't do it for you or you have moved the apps to the internal storage in the past):
1. Enter the ADB Shell by typing adb shell
2. In the ADB shell, type /system/bin/a2sd install
To prevent A2SD from running, type /system/bin/a2sd remove
If you have any issues, you can PM me for assistance, send e-mail to rtkirton at gmail dot com, or look me up on gtalk.
Special Thanks to the following people
Thanks to the following people for helping me on this (2.7 testing):
Toastcfh
- For assisting me in getting my test kernel setup to run ext4...that helped tremendously with development.
- For testing it (along with Flipzmode) on FreshToast 2.0 (CDMA Hero).
- For (along with Flipzmode) helping to identify the disappearing marketplace issue.
shahid.malik
- For testing on VillianROM 5.5 (GSM Hero)
- For testing on VanillaEclair 2.0.1 (GSM Hero)
Andrizoid
- For testing on Evil Eris 2.0 (HTC Eris)
Framework43
- For adding to Evil Eris 2.0.1 (HTC Eris)
DS36
- For testing on Eris Official 1.0 Alpha w/ Controllable Overclocking (HTC Eris)
4SidedDice (and others)
- For testing it on DamageControl's 2.08 and later (CDMA Hero)
Flipzmode
- For including it (along with Toastcfh) in FreshToast 2.0 (CDMA Hero)
- For including it in Fresh 2.1.x (CDMA Hero)
- For including it in Fresh Evo (HTC Evo)
- For (along with Toastcfh) helping to identify the disappearing marketplace issue.
Kurt666
- For testing on Pay's ROM for Desire v1.4 (HTC Desire)
Cordy
- For helping with general testing of 2.7
zygame
- For including it on Daguu_Espresso_v1.2_By_FlZyGaMeUp-Pre-release-2
chuckhriczko
- For including it in SuperSonic v2.0 (HTC Evo)
zenulator
- For including it in ZenEXP 0.9.6.2 (HTC Hero)
crunchybutternut
- For including it in Buufed 1.7.2 (HTC Hero)
.mac
- For including it in ZenEXP Eris Expresso (HTC Eris)
Papa Smurf151
- For including it in Blue Echo 2.1.3 (HTC Hero)
beezy420
- For including it in HoneyBun v.3 (HTC Hero)
britoso
- For testing it on Froyo FRF50 and FRF83 (Nexus One)
djmcnz
- For including it in Kang-o-rama 0.9 Froyo (Nexus One)
If I forgot anyone...let me know.
Click to expand...
Click to collapse
Change Log
Version 2.7 Update 3r1
1. Fixes a bug in fixa2sd that causes the dalvik-cache to automatically move to the SD card.
2. Created a new program called launcha2sd that now does the launching functions of a2sd. The program a2sd now launches launcha2sd using bash. This fixes any /system/bin/sh issues with open brackets being interpreted at commands rather than conditions in an IF statement.
Version 2.7 Update 3
1. If a rom has the dalvik-cache on the cache partition, it will not attempt to move it to the internal cache.
2. Users now have an option to move the dalvik-cache to the cache partition. The option to move dalvik-cache to the SD card is still retained.
3. New commands introduced: cachepart moves dalvik-cache to cache partition, cachesd moves dalvik-cache to sd card (phased replacement to a2sd cache).
4. Fixes some minor bugs.
Version 2.7 Update 2
1. The /system partition returns to read-only state when the program is finished. The /data partition is left untouched.
2. ZipAlign does not automatically start on boot. You must type a2sd zipalign to activate the start on boot feature.
3. Taken out visual references of CyanogenMod's cm.filesystem.ready and DamageControl's dc.filesystem.ready. It now refers to both visually as "File System Ready property"
4. A2SD Check no longer mounts the ext partition. It will indicate when the ext partition is not already mounted. This should help in troubleshooting roms that do not automatically launch A2SD.
Version 2.7 Update 1
Reversed a decision on 2.7 final to set /system and /data to read-only when the program completes. This is causing major issues with some newer roms.
Version 2.7
1. Completely rebuild the entire program from ground up. Attempted to simplify the process and to better detect different environments.
2. All programs use the included busybox.a2sd to avoid conflicts with the different busybox installations.
3. Mounts /system and /data in read-write to prevent any conflicts. Remounts them in read-only when completed.
4. Except for a2sd, all programs built as bash scripts
5. Separated the original program into the following programs:
a2sd - Simple script that detects whether the init.rc was fixed with the cm.filesystem.ready and sets it accordingly. Starts starta2sd if either a command is included or the cm.filesystem.ready patch is installed, otherwise runs A2SD that does not move dalvik-cache. Runs a smaller version of the boota2sd if the cm.filesystem.ready or dc.filesystem.ready are not present.
starta2sd - Processes all commands...it's the controller program. Adds the following commands: align, zipalign, nozipalign, resetcache, clearcache, fixmarket, diskspace.
boota2sd - Used when the cm.filesystem.ready fix or the dc.filesystem.ready fix is present in init.rc. Resets dalvik-cache, app and app-private to internal storage upon the following conditions:
1. Mount failure or missing ext partition, and
2. Any or all key directories are symlinked to the SD card.
This step prevents a bootloop or a stall from occuring during the boot process. Also incorporates better detection of mounted partition. If it detects the partition mounted in /proc/mounts, it will skip trying to mount.
Automatically executes fixa2sd if the flags and symlinks to dalvik-cache, app and/or app-private do not match.
Also moved the mounting of the swap partition to the end and reintegrated auto partition detection when mounting (similar to A2SD 2.6.1). Added ZipAlign functions.
chka2sd - Incorporates bug fixes that did not detect the dalvik-cache correctly. New report layout (should be simpler to read). Code was simplified.
fixa2sd - Incorporates same bug fixes as chka2sd. Does a better detection of flag files and symlinks. Code was simplified.
setupa2sd - Used to execute setup commands from starta2sd (install, remove, cache, nocache, align, fixmarket). Also controls a2sd help.
aligna2sd - zip aligns all apk files in /data/app and /data/app-private.
010a2sdmodaco - Part of the Beta8 Modaco Desire testing, does the following:
1. If 02cachedalvikcache exists, back the program up and overwrite the program, preventing the contents from executing.
2. if 40a2sd exists, do the same thing.
Version 2.6.1
1. Mainly a bugfix. Corrects the dalvik-cache code where it would put the dalvik-cache back on the sd card even when the flag file was set.
2. Put the flag files back on /system/sd. Fresh 2.0d was incompatible with the new setup (it doesn't mount the /sdcard until later in the boot process).
3. Added code for Fresh 2.0d...the boot can be hung if the dalvik-cache is changed during boot. Program automatically determines if 04apps2sd exists in /system/etc/init.d (this is signature for any roms built from Fresh 2.0d) and automatically sets the NoCache flag if the dalvik-cache is in internal memory and the NoCache flag isn't set.
4. Fixed swap code. It was not turning on swap when it should.
5. (Release 1) - Fixed some minor issues.
6. (Release 2) - Recreated a new flash package that is more compatible with different recovery system.
Version 2.6
1. Moves all flag files from /system/sd to /sdcard. The kernel mounts the FAT32 SD partition and that will be available before Apps2SD runs. Future flag file creation will be in /sdcard.
2. Added a check feature (a2sd check). This will check your flag files and symlinks. A report on your screen will tell you what needs to be fixed, if any.
3. Added a repair feature (a2sd repair). This will repair your a2sd installation.
4. Flashing the A2SD checks Busybox installation and reinstalls it if necessary (it only checks for a missing Busybox installation...it won't replace the one you have installed).
5. Automatically remounts /system and /data partitions for read-write access when started with any of the install/repair options (install, repair, cache, nocache, remove).
6. Fixed mount command...now uses auto detect rather than the individual partitions. This allows A2SD to work on ext4.
7. Separate nocache version available for slower SD cards.
Version 2.5
1. Added functionality to move dalvik-cache to the ext partition.
2. Added option a2sd cache to manually move the dalvik-cache to the ext partition.
3. Added option a2sd nocache to manually move the dalvik-cache back to the internal phone storage.
4. Added option a2sd install to setup a2sd on a phone (all apps and dalvik-cache on ext partition)
5. Added option a2sd remove to revert all a2sd changes back to normal mode (all apps and dalvik-cache in internal storage).
6. Added option a2sd noswap to turn off swap partition.
7. Added option a2sd swap to turn on swap partition.
Click to expand...
Click to collapse
Thank you! I LOVE a2sd
Works like a Charm !!! Thank YOU !!!
Darktremor A2SD version 2.7 release 3r1 is now available. This fixes a bug in fixa2sd that may cause the dalvik-cache to move to the SD card automatically.
This also incorporates a new launching method using bash as the shell (the old a2sd file is now launcha2sd...a new a2sd file is created that launches launcha2sd in the bash shell.
Noob Question.
I installed a new 16G sd card, then followed instructions to partition. Everything looked great. Then moved all my back-up files and Dark Tremors from my computer to the sd card. Flashed Kings ALL Format, flashed Rom Kinged Hateslinger, let phone reboot and settle. Then, booted into recovery, then wiped dalvik and cache, flashed Dark Tremors (newest veersion). Rebooted fine, in Titanium Back Up/Overview it states that I have dtapp2sd with 1.89 GB of free space.
Question:why are my apps not moving to this partition automatically?
Please help and Thank you to ALL Developers on this site!
Related
I have a complex problem i'm trying to get around to for month now. Maybe someone has a tip for me:
When installing a new ROM, there are always preinstalled programs turning up that are not part of the ROM. I assume those are on my SDCard because of the Apps2SD/Link2SD setups i have been running for awhile. Was still a bit wondering why they are turning up, because they are not "linked" (didnt reinstall apps2sd or link2sd), but they are available nevertheless ...
What remains is that i need to check/fix my apps2sd setup, but i cant access the linux partitions from my PC because of USB/cardreader problems..
Is there an app out there that lets me access (and maybe even change) my ext partitions content ? Commandline stuff is fine for me.
System: CM7 XT70, 16GB SD with SWAP and Ext3
Ps.: If i can even change to ext4 that way, that would be awesome.
One thing you can do is make an nandroid backup of the "SD Data" partition (that's what nandroid calls the ext partition). For that partition, nandroid backs everything up into a *.tar and a *.md5. You can then copy the tar file to your computer, extract it, modify it etc. When you're done create a new *.tar file and a corresponding *.md5 and use nandroid to restore your new *.tar. When nandroid restores the "SD Data" partiton, it first reformats the entire partition to ext2 and then extracts the tar onto it. If you use XT720 OpenRecovery there's a "SD utilities" function that you can use to convert the existing ext2 to ext3 or ext4 (be aware that ext4 requires ROM support--I think most of the recent ones do...). The regular OpenRecovery does not support ext4 (you won't be able to make a nandroid of "SD Data")--you next XT720 OpenRecovery.
If you want to repartition... I don't know if that can be done on the phone itself.
If you want to just disable app2ext, look inside /system/etc/init.d and find the script that mounts /sd-ext and then move/delete/rename it.
i reclaimed control over my phone! thx
it turned out all /data/app was linked to the ext3 partition ... another reason why my phone was slow.
PRE-INSATLLED :
Backup files on your SD (recommended)
Make sure that you have a 2nd partition on your SD card. If none, partition using CWM or any other method
Format 2nd partition to EXT3/4 using CWM or any other method
Make sure that 2nd partition is mounted at boot. You can check this by typing the command below -
Code:
mount | grep sd-ext
you will get something like this :
Code:
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,barrier=1,nodel
alloc,data=ordered)
How to install:
Download Darktremor Apps2SD 2.7.5.3 Beta 04 and save it on your SD ==> http://api.viglink.com/api/click?for...a04-signed.zip
Reboot in recovery
Backup
Mount system and data partitions (Main Menu > mounts and storage)
Install file in Step 1 (Main Menu > install zip from sd > choose zip from sdcard)
Reboot. Done!
NOTE: After the phones boots, it will reboot again. This is normal because a2sd will automatically move apps to the 2nd partition of your SD
CREDITS : PARASMI
Thanks this worked perfectly
just one thing, your link didn't work for me for some reason http://forum.xda-developers.com/showthread.php?t=715116 I also installed A2SD GUI successfully and that's working as well
This is a simple and effective (moves most space hogging folders from internal memory to sd-ext) APP2SD solution.
It moves the following things from /data partition to ext partition on SD card:
/data/app => /sd-ext/app
/data/app-private => /sd-ext/app-private
/data/dalvik-cache => /sd-ext/dalvik-cache
and creates symlinks to new locations in place of original folders.
Solution consists of 2 via recovery flashable ZIPs:
sd-ext_patch-signed-vXX.zip - this updates/creates CyanogenMod 7/9 script that mounts SD card ext partition to /sd-ext so /sd-ext can be any ext version (by default it can be only ext3) and installs e2fsck. This must be re-flashed after each ROM update (unless you know that ROM will mount your /sd-ext out of the box).
to_sd-ext_patch-signed-vXX.zip - actually moves folders to ext partition on SD card. This can be flashed only after first boot into ROM after wiping /data. It should be re-flashed only in conjunction with wiping /data and /sd-ext.
This mod requires ext2/ext3/ext4 partition on SD card.
Always make full Nandroid backup before flashing this mod or updating ROM with mod installed!
Disclaimer: I am not responsible for anything that may happen as a result of using this mod.
Installation/usage:
To install mod on a working ROM:
Flash sd-ext_patch-signed-vXX.zip via Recovery.
Flash to_sd-ext_patch-signed-vXX.zip via Recovery.
After updating ROM:
Re-flash sd-ext_patch-signed-vXX.zip without booting into updated ROM.
After wiping /data from Recovery:
Delete moved folders from /sd-ext (in most cases you will want to do this by wiping /sd-ext from Recovery).
Boot into your ROM.
Re-flash to_sd-ext_patch-signed-vXX.zip via Recovery.
This mod is tested with CyanogenMod 7 (7.1 by mik_os and 7.2 official builds) and CyanogenMod 9 by hephappy and Amon RA recovery 3.0.6.
If you are using Clockworkmod Recovery see this post.
+1
Is this mod developed by you?
DJoptimus-One said:
Is this mod developed by you?
Click to expand...
Click to collapse
Yes
DavisNT said:
Yes
Click to expand...
Click to collapse
Nice work, I'm surely gonna try
Keep up.
Good work here!! Really nice to see some REAL development here
Will try it and report soon.........
Sent from heaven, wandering with Steve Jobs
Any feedback yet? Would love to give it a try :thumbup:
Sent from my LG-P500 using XDA
FitAmp said:
Any feedback yet? Would love to give it a try :thumbup:
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Don't ask for that, try it yourself!!
nice work will try
Does this work on gb?2.3.3?
How to move app's ? Does this automatically moves it?
Sent from my LG-P500 using XDA
Just flashed on cm9 weekly... so for so good
Sent from my LG-P500 using XDA
Good work. Nice example of KISS approach - three symlinks + few lines of other code
dynamite33 said:
Does this work on gb?2.3.3?
How to move app's ? Does this automatically moves it?
Click to expand...
Click to collapse
You can make full Nandroid backup (Nand backup in recovery) and try whether it works on your ROM.
This requires the following things:
ext partition on SD card (you must have partitioned your SD card)
ROM that supports init.d scripts
kernel that supports ext filesystem version that is on SD card
You can test all this by (making full Nandroid backup and) flashing sd-ext_patch-signed-vXX.zip, booting in Android and issuing the following commands in Terminal Emulator:
Code:
su
mount
mount | grep sd-ext
If you see line like this somewhere in the output:
Code:
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
then /sd-ext is mounted and you can proceed to flashing to_sd-ext_patch-signed-vXX.zip.
Apps are moved when flashing to_sd-ext_patch-signed-vXX.zip.
DavisNT said:
You can make full Nandroid backup (Nand backup in recovery) and try whether it works on your ROM.
This requires the following things:
ext partition on SD card (you must have partitioned your SD card)
ROM that supports init.d scripts
kernel that supports ext filesystem version that is on SD card
You can test all this by (making full Nandroid backup and) flashing sd-ext_patch-signed-vXX.zip, booting in Android and issuing the following commands in Terminal Emulator:
Code:
su
mount
mount | grep sd-ext
If you see line like this somewhere in the output:
Code:
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
then /sd-ext is mounted and you can proceed to flashing to_sd-ext_patch-signed-vXX.zip.
Apps are moved when flashing to_sd-ext_patch-signed-vXX.zip.
Click to expand...
Click to collapse
Ok thanx a lot! Will try it.
Sent from my LG-P500 using XDA
hi DavisNT
i use Link2sd now, and want to try ur script, can i remove link2sd and use ur script without problem and without losing my apps ?
GonDr said:
i use Link2sd now, and want to try ur script, can i remove link2sd and use ur script without problem and without losing my apps ?
Click to expand...
Click to collapse
Try it, but remember to take full Nandroid backup before trying.
You can do this:
do full Nandroid backup from recovery
With Link2SD move all applications back to internal memory
delete mount scripts created by Link2SD (probably there is a kind of uninstall option in Link2SD)
install my mod
If you don't have enough space in internal memory, then it is possible to use Titanium Backup to backup and restore apps (however I am not sure whether Titanium Backup can backup data of applications linked with Link2SD - probably can, but I am not sure).
DavisNT said:
Try it, but remember to take full Nandroid backup before trying.
You can do this:
do full Nandroid backup from recovery
With Link2SD move all applications back to internal memory
delete mount scripts created by Link2SD (probably there is a kind of uninstall option in Link2SD)
install my mod
If you don't have enough space in internal memory, then it is possible to use Titanium Backup to backup and restore apps (however I am not sure whether Titanium Backup can backup data of applications linked with Link2SD - probably can, but I am not sure).
Click to expand...
Click to collapse
I don't think that titanium can restore anything to sdext, it just saves anything, including linked stuff and if trying to restore everything together it will fail, if the total of backed apps is larger than internal storage...
However, if link2sd is installed, the later will start linking data/apps 'on the fly' as Tib restores them. That's why it is essential to install link2sd or similar before going to batch-restore everything.
I guess this script should handle it in a similar way? I'm going to try anyway.
My idea was backing up most of apps with Titanium Backup while using Link2SD, then removing them (and moving left apps back to internal memory, uninstalling Link2SD mount scripts) and restoring after installing my script (Move to sd-ext).
Move to sd-ext links all applications (and dalvik cache, but not application data and library files extracted to data folders) at once - Titanium Backup will restore directly to SD card
can you explain me what's the difference between this mod and d2sd ungaze?
thanks
mutia said:
can you explain me what's the difference between this mod and d2sd ungaze?
thanks
Click to expand...
Click to collapse
If I correctly got what D2SD ungaze does, then it moves applications, applications data and libraries (/data/app, /data/app-private and /data/data) to SD card ext partition and leaves Dalvik cache (/data/dalvik-cache) on internal memory (/data partition).
While my mod moves and links applications and Dalvik cache (see first post in this thread for details), leaving all other folders (some system configuration and application data and libraries) in internal memory (/data partition).
Also technical implementation is very different from my mod. D2SD ungaze copies everything and links back certain things. It looks like D2SD ungaze also doesn't free space on /data partition.
DavisNT said:
You can make full Nandroid backup (Nand backup in recovery) and try whether it works on your ROM.
This requires the following things:
ext partition on SD card (you must have partitioned your SD card)
ROM that supports init.d scripts
kernel that supports ext filesystem version that is on SD card
You can test all this by (making full Nandroid backup and) flashing sd-ext_patch-signed-vXX.zip, booting in Android and issuing the following commands in Terminal Emulator:
Code:
su
mount
mount | grep sd-ext
If you see line like this somewhere in the output:
Code:
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
then /sd-ext is mounted and you can proceed to flashing to_sd-ext_patch-signed-vXX.zip.
Apps are moved when flashing to_sd-ext_patch-signed-vXX.zip.
Click to expand...
Click to collapse
i flashed the first zip file, then made this test through Terminal Emulator and got a line similar to the one you mentioned (my sd-ext is type 3, and the info in brackets was a bit different).
then i flashed second zip file.
the free RAM space increased (which necessarily means that things were moved to the sd-card, right?)
i then installed an app - and saw RAM decreasing accordingly, plus - the sd-ext folder is empty
how can i know if it works ?!?
@mrvek: a follow-up to http://review.cyanogenmod.org/61837
dalvik.vm.dexopt-data-only is being completely removed from CM currently, btw.
I've been playing with a little hack.
To get the unused/wasted space of system partition back to the read/write domain, we can swap the cache and system partition names (they are usually mounted by name, so the partitions can be effectively swapped by this).
Code:
diff --git a/fs/partitions/efi.c b/fs/partitions/efi.c
index 6296b40..4bc9234 100644
--- a/fs/partitions/efi.c
+++ b/fs/partitions/efi.c
@@ -666,6 +666,12 @@ int efi_partition(struct parsed_partitions *state)
info->volname[label_count] = c;
label_count++;
}
+ if (!strcmp(info->volname, "cache")) {
+ strcpy(info->volname, "system");
+ } else if (!strcmp(info->volname, "system")) {
+ strcpy(info->volname, "cache");
+ }
state->parts[i + 1].has_info = true;
}
kfree(ptes);
userdata are not affected by this change (no wipe/factory reset by user required), system has still almost 250MB free available when the current CM11+gapps are installed to the formerly cache, now system partition.
The r/w mounted cache has around 1.4 GB now.
The following script can be put as e.g. 10dex2cache to /system/etc/init.d
Code:
#!/system/bin/sh
rm -rf /data/dalvik-cache/*
/system/xbin/mount --bind /cache/dalvik-cache /data/dalvik-cache
So the dalvik-cache is stored in cache partition, freeing some space from userdata
In my case, it means over 400MB more free space in userdata when dalvik is used.
ART files are much bigger (the test of ART actually made me do this, as I haven't had enough free space in data for the switch to ART anymore).
plus:
- more free space in data
- much less wasted space in r/o mounted system
minus:
- free space in cache is not monitored, if it runs out, things will fail miserably without proper user notification of the cause (that's the main reason why dex in cache support is being removed from CM; when switched to ART, I have currently less than 400MB free in cache...)
- users would need to use a recovery with the same hack in its kernel => using some random available recovery build would result in partition mismatch
- fastboot erase cache issued by user would erase system...
- it's a hack
I'd welcome some opinions about this hack, @stargo , thanks .
Is a kernel-hack the only way to change the mounts? (I assumed I would find something like fstab or similar).
I wished we could partition our phone >.<
Btw. I am not able to switch to ART. (Over 2.9 GB free space on the phone.)
After a reboot it's back to dalvik again. (build 03.08.2014; dd.mm.yyyy) It must be one of the installed apps, maybe XPrivacy.
Loader009 said:
Is a kernel-hack the only way to change the mounts? (I assumed I would find something like fstab or similar).
I wished we could partition our phone >.<
Btw. I am not able to switch to ART. (Over 2.9 GB free space on the phone.)
After a reboot it's back to dalvik again. (build 03.08.2014; dd.mm.yyyy) It must be one of the installed apps, maybe XPrivacy.
Click to expand...
Click to collapse
Kernel hack is certainly not the only way, but it's the simplest way - you do it at a single low level place and that's it, both android system and recoveries are then covered.
xposed is not compatible with ART - it's the xposed framework what keeps switching the VM back to dalvik for you.
If I apply the kernel fix, I don't need the mount script, right?
Fr4gg0r said:
If I apply the kernel fix, I don't need the mount script, right?
Click to expand...
Click to collapse
The kernel hack effectively swaps system and cache partitions (stock system partition is 1.4 GB, cache 755.9MB; the kernel hack will swap them to 1.4GB r/w mounted cache and 755.9MB r/o mounted system)
The bind mount script is just one of the possible ways of use of the gained space in the now larger (by the kernel hack), read/write mounted cache - it moves the dalvik-cache from /data partition to /cache partition...
why cant we just change our partition sizes like the touchpad?
http://forum.xda-developers.com/showthread.php?t=2756314
No idea Simply throwing parted at it doesn't work, it seems that the partition table is saved somewhere else (Result: data was moved, but original partition table restored -> broken data)
I also tried unsuccessfully parted.
When I was done with parted, I rebooted. All partitions were reverted back to stock.
I believe it is as mifritscher said...
There has been a lot of questions throughout various threads about converting your Note 3 file system to f2fs. This is a simple way to convert your current file system to f2fs on N9005 and N900T. I have not tried it on other Note 3 variants because I do not have access to them but I would think that the change would be similar.
First off, you need to have a f2fs compatible ROM installed with compatible f2fs kernel. I used Shinto [Shuriken] Kernel from @CekMTL to do this on N9005 and N900T. The kernel can be found HERE .
If your ROM and kernel meet the above requirements:
1. Backup everything you want to keep from your internal SD card, this process will wipe internal SD.
2. Update TWRP to the latest and greatest 2.8.1.0, go HERE
3. Drop to TWRP
4. IF YOU MISSED IT BY NOT READING #1, YOU WILL LOSE ALL PERSONAL DATA ON YOUR INTERNAL STORAGE BY DOING THIS!
5. Run a FULL NANDROID BACKUP to your External SD Card.
6. Go to SETTINGS and unselect (un tick) “use rm -rf instead of formatting” (We want TWRP to actually format with f2fs)
7. Go to Wipe and Choose Advanced Wipe
8. Select System and choose change or repair file system
9. Choose f2fs and go through the steps where it tells you that all data will be lost and apply it.
10. Follow steps 7-9 for Data and Cache one at a time.
11. Go to SETTINGS and select (tick) “use rm -rf instead of formatting” (We don’t want to restore back to EXT4)
12. Do a restore, but ONLY CHECK SYSTEM & DATA for restoral, NOTHING ELSE IS NEEDED.
13. It will tell you that your backup was made with ext4 and may not boot, don't worry it will boot.
14. After restore, reboot your device. First boot will take a few because it's a new file system and your apps will have to reconfigure themselves, etc
FROM @CekMTL : As for the external SD card and f2fs, it is mounted differently and your Kernel WILL NOT SUPPORT IT [f2fs on external SD card], so DO NOT format your external SD card to f2fs! (hopefully I said that enough times)
***DISCLAIMER***
You do thisl at your own risk! It has been tested completely and works perfectly on N900T as well as N9005. If you wreck your phone, soft brick, hard brick, your battery explodes, your screen jumps up and cuts you, your credit score tanks, your wife leaves you, your dog leaves you, your cat kills you, the sky falls, or anything else... it is not anyones fault but your own. Thank you
Updater process ended with error