Related
Introducing...
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
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
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.
Bump thread...new version 2.7.5.3 Beta 02 is released.
Bump---new version available.
Most ROMs include most of the functionality you described.
What are the gains of getting this? If I read things a little, there is somekind of app whereby the user can control the parameters?
Some people believe this version makes the phone respond faster because rather than using a FAT32 implementation of Apps2SD, which (from my understanding) has to go through some form of encryption/decryption (could be wrong on that account), this version uses native Linux partitions to store the data. This also uses symbolic links (native to Linux) to redirect the files to the SD card.
Apparently, from what I have read as well, some programs leave traces of themselves in Internal storage even if they are moved to the SD card by Froyo (although I can't find any evidence of that on my phone), this would insure that the entire program is on the SD card.
On top of that, this version can move dalvik-cache to the SD card, which Froyo's implementation cannot do. That helps with freeing up more internal space.
The newer 2.7.5.3 also has a method of moving the program data (/data/data) to the SD card as well, freeing up even more memory. Froyo also can't do this.
While it is true that most roms offer similar functionality, most Apps2SD implementations are also designed for the rom they run. If you have a rom that does the same functionality as Darktremor, then you should stick with what you have. This is for people who need more functionality with their Apps2SD or people who use roms like CyanogenMod which doesn't have an Apps2SD implementation.
riemervdzee said:
Most ROMs include most of the functionality you described.
What are the gains of getting this? If I read things a little, there is somekind of app whereby the user can control the parameters?
Click to expand...
Click to collapse
tkirton said:
Some people believe this version makes the phone respond faster because rather than using a FAT32 implementation of Apps2SD....
{I edited out all of this stuff since the person you're replying to is an advanced kernel developer who knows all of this and was suggesting that all existing roms other than stock CM roms come with ext-based apps2sd which support dalvik2sd and so on, just like this does}...
...While it is true that most roms offer similar functionality, most Apps2SD implementations are also designed for the rom they run. If you have a rom that does the same functionality as Darktremor, then you should stick with what you have. This is for people who need more functionality with their Apps2SD or people who use roms like CyanogenMod which doesn't have an Apps2SD implementation.
Click to expand...
Click to collapse
So this is useful for CM roms - that is true. It's probably the main reason to use this since I too don't see anything that would really be better than the apps2sd built into the roms I've been using other than this taking more space.
Possibly this thread could be renamed with "for CM stock roms" or something so it's really clear to users of those roms that they could get these benefits easily.
My thought on this issue is this: I'm not going to attempt to convince you to try it. If you want to run it, great. If you don't, that's fine as well (some people feel Froyo Apps2SD is enough, and I respect that).
I always believe that, if you have something that works fine for you, don't change. If your Apps2SD implementation works for you, then stick with that.
dkelley said:
So this is useful for CM roms - that is true. It's probably the main reason to use this since I too don't see anything that would really be better than the apps2sd built into the roms I've been using other than this taking more space.
Possibly this thread could be renamed with "for CM stock roms" or something so it's really clear to users of those roms that they could get these benefits easily.
Click to expand...
Click to collapse
Do I need to turn on the Application moving thing in Cyanogen mod, or just DT just run in the background automatically?
I'm using CM7 by the way.
tkirton said:
My thought on this issue is this: I'm not going to attempt to convince you to try it. If you want to run it, great. If you don't, that's fine as well (some people feel Froyo Apps2SD is enough, and I respect that).
I always believe that, if you have something that works fine for you, don't change. If your Apps2SD implementation works for you, then stick with that.
Click to expand...
Click to collapse
interesting - you missed my point entirely LoL, but that is very fair what you said.
I was clarifying that this tool is really targetted at, and most useful for, CM users.
and from what I've been told this particular version beta3a is working perfectly with CM7 gingerbread.
takuhii said:
Do I need to turn on the Application moving thing in Cyanogen mod, or just DT just run in the background automatically?
I'm using CM7 by the way.
Click to expand...
Click to collapse
if you use this all you do is flash it and you're done. no more thinking about application control other than to move certain apps to "phone" memory if they FC after being installed and you find them defaulting to be in "sd card" memory (which often causes issues in some gingerbread installs).
Using this on CM7 with an ext4 partition, works very well. One thing I had to do manually is run 'a2sd cachesd', moving the dalvik to the sd card. Assuming the built in a2sd (ext) in other roms do this automatically, as my free internal space was much lower (with the same apps) until I did this step. Performance seemed the same either way, just the free storage number changed )
Quick question about the datasd command. Aside from saving space, would this (or could this) allow one to preserve apps in between wipes (i.e. different rom installs)? As a wipeaholic I'd love to just have my apps/data sitting on ext partition and have them show up automatically whenever I flash a new rom.
scrollo said:
Using this on CM7 with an ext4 partition, works very well. One thing I had to do manually is run 'a2sd cachesd', moving the dalvik to the sd card. Assuming the built in a2sd (ext) in other roms do this automatically, as my free internal space was much lower (with the same apps) until I did this step. Performance seemed the same either way, just the free storage number changed )
Quick question about the datasd command. Aside from saving space, would this (or could this) allow one to preserve apps in between wipes (i.e. different rom installs)? As a wipeaholic I'd love to just have my apps/data sitting on ext partition and have them show up automatically whenever I flash a new rom.
Click to expand...
Click to collapse
I am running this on CM7 too, I moved Dalvik-cache to the CACHE folder/partition. This ROM just blazes along now...
Application moving thing is Froyo Apps2SD. Darktremor does it automatically.
takuhii said:
Do I need to turn on the Application moving thing in Cyanogen mod, or just DT just run in the background automatically?
I'm using CM7 by the way.
Click to expand...
Click to collapse
I actually did get the point, but couldn't come up with an appropriate response. I don't know much about the HTC Hero GSM. My first Android phone was the HTC Hero CDMA, which I found out is a different beast altogether.
For the Hero CDMA, we have both CyanogenMod (AOSP) and SenseUI (HTC) roms. Darktremor is relevant to both types of rom types, so both AOSP and HTC rom users can use it. That's where I had troubles actually coming up with the appropriate response...I don't know if you guys have SenseUI and I'm not familiar with other roms you have.
Beta 04 should work better for CM users..
dkelley said:
interesting - you missed my point entirely LoL, but that is very fair what you said.
I was clarifying that this tool is really targetted at, and most useful for, CM users.
and from what I've been told this particular version beta3a is working perfectly with CM7 gingerbread.
Click to expand...
Click to collapse
Theoretically, it should preserve the data (though I don't think anyone, including myself, has done that yet). This should be useful if you were going between nightly builds (seeing that you are on CM7, I presume that's why you asked the question), but switching between two different roms may result in unpredictable operation.
scrollo said:
Using this on CM7 with an ext4 partition, works very well. One thing I had to do manually is run 'a2sd cachesd', moving the dalvik to the sd card. Assuming the built in a2sd (ext) in other roms do this automatically, as my free internal space was much lower (with the same apps) until I did this step. Performance seemed the same either way, just the free storage number changed )
Quick question about the datasd command. Aside from saving space, would this (or could this) allow one to preserve apps in between wipes (i.e. different rom installs)? As a wipeaholic I'd love to just have my apps/data sitting on ext partition and have them show up automatically whenever I flash a new rom.
Click to expand...
Click to collapse
tkirton said:
Application moving thing is Froyo Apps2SD. Darktremor does it automatically.
Click to expand...
Click to collapse
I think its time we refered to your A2SD as A2EXT, this is more suitable now since Google has as implemented A2SD(froyo fat32). Darktremor A2EXT is better name for this work.
Keep up the good work.
Sent from my HTC Hero
Or Apps2EXT...
Actually, on 2.7.6 (or 2.7.5.3 final), I was thinking on renaming everything to Darktremor Toolbox (or something along those lines...anything but Darktremor Apps2SD), since this thing does more than just move applications to the EXT partition. It also moves Dalvik-Cache (Dalvik2SD and Dalvik2Cache) and Program files (Data2SD), plus adjust Low Memory killer settings, sets the Dalvik heap size, converts partitions, implements the Evo SD Card speed fix (which not sure if this works for anyone else), fixes APK permissions, and possibly one or two more things I can't recall off the top of my head.
It seems the program has outgrown its name, plus the confusion between this program and Froyo Apps2SD is getting worse.
adisa said:
I think its time we refered to your A2SD as A2EXT, this is more suitable now since Google has as implemented A2SD(froyo fat32). Darktremor A2EXT is better name for this work.
Keep up the good work.
Sent from my HTC Hero
Click to expand...
Click to collapse
tkirton said:
Theoretically, it should preserve the data (though I don't think anyone, including myself, has done that yet). This should be useful if you were going between nightly builds (seeing that you are on CM7, I presume that's why you asked the question), but switching between two different roms may result in unpredictable operation.
Click to expand...
Click to collapse
It does preserve them. I use this to test different roms on the leo...makes it so I do NOT have to reinstall all the apps.
do I need to flash this every time I flash a new cm7 nightly?
Yes...CM 7 Nightly builds (as with other roms) will wipe out the /system partition before installing the rom, so Darktremor's files are wiped clean as well. You will need to reflash Darktremor in order to restore the boot scripts.
alioooop said:
do I need to flash this every time I flash a new cm7 nightly?
Click to expand...
Click to collapse
Introducing...
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
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
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.
Is there really any need for this if we have froyo? If so please fill me in, I just don't see the point.
Sent from my HTC Glacier
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Actually, there is. The dalvik-cache doesn't move to your FAT32 partition, so you will still eat up storage space with it.
Also, this program offers other features, such as Low Memory Killer tweaking and heap size adjustments.
Some people also reported that the apps run faster when they are placed on an EXT partition rather than using Froyo's FAT32 implemetation. Personally, I haven't really benchmarked it, so I can't tell you from personal experience if it is faster or not.
I guess it's a personal preference.
stoneyjonez said:
Is there really any need for this if we have froyo? If so please fill me in, I just don't see the point.
Sent from my HTC Glacier
Click to expand...
Click to collapse
That may be true right now, but apps are getting bigger in the Android market. I know for other phones, it can be a necessity.
As I said in the previous post...it's more of a preference.
stoneyjonez said:
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Click to expand...
Click to collapse
May I ask if this App2SD working in CM7 nightly ? Thanks to advise .
Depends on who built it.
I have users that say this works perfectly with CM7. During my testing using CM7, I didn't get it to work because the build I had didn't have EXT support (which is needed for Darktremor to work).
So, I would say do a backup of your phone and try it. If you can't get it working, you are more than welcome to send me the logs at [email protected] and I'll see what happened (logs are located on /data directory: files are dta2sd.log, dta2sd.lg1, dta2sd.lg2)
ajaxchen said:
May I ask if this App2SD working in CM7 nightly ? Thanks to advise .
Click to expand...
Click to collapse
Thanks for your promptly reply ; I will give it a try later . But i am wondering if it's a issue that CWM recovery 3.0.0.5 can not find my EXT partition (I had created my 1GB EXT3 with CWM recovery already) ?
That could be an issue. I'm not familiar with that recovery, but if it has a repair function, you should try to run it.
If you don't have that option or the repair was unsuccessful, I would offload the contents of your FAT32 partition on a computer and repartition the card.
ajaxchen said:
Thanks for your promptly reply ; I will give it a try later . But i am wondering if it's a issue that CWM recovery 3.0.0.5 can not find my EXT partition (I had created my 1GB EXT3 with CWM recovery already) ?
Click to expand...
Click to collapse
This would be way easier with amon RA recovery. I remember having it on my g1 and never had problems with it. Clockwork is good but making partitions and ext 3 and 4 is simple from the phone.
Sent from my HTC Glacier using XDA App
I added a new command in Beta 03 that should make it easier to convert EXT2 to EXT3:
a2sd convert-ext3
Killbynature said:
This would be way easier with amon RA recovery. I remember having it on my g1 and never had problems with it. Clockwork is good but making partitions and ext 3 and 4 is simple from the phone.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Is it possible to put the commands into an .apk, just to make it less intimidating and easier to use for some of us? I have no developer skills or I'd try.
stoneyjonez said:
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Well there are people who like games and seeing that some of the games in marketplace are 80mb each and some even reach over 100. I filled my 500mb internal storage because i like to game on my phone.
It's in the planning stages. The goal is to build an interface so an average user can interact with it. Sadly, I'm not very good at Java yet and I haven't found a programmer to assist me in this quest. But it's still being planned and will happen eventually.
agriff said:
Is it possible to put the commands into an .apk, just to make it less intimidating and easier to use for some of us? I have no developer skills or I'd try.
Click to expand...
Click to collapse
is the performance changed when the cache isn't in the phone? How much is the card speed (class) important?
Card speed is important when writing. For dalvik-cache and apps, not that much. For moving /data/data to the SD card, it may make a difference.
Read speed is dependent on the quality of the card you are using.
As for performance, I only notice the speed difference when things like dalvik-cache is getting rebuilt. Normal operation...I don't notice the difference.
MuF123 said:
is the performance changed when the cache isn't in the phone? How much is the card speed (class) important?
Click to expand...
Click to collapse
What's the use? We've got plenty of internal storage space.
If you have plenty of space for everything, don't use it. It's not a requirement to use.
It's for people who may want to use it just because they can or they may have a need for it.
Part Four said:
What's the use? We've got plenty of internal storage space.
Click to expand...
Click to collapse
tkirton said:
If you have plenty of space for everything, don't use it. It's not a requirement to use.
It's for people who may want to use it just because they can or they may have a need for it.
Click to expand...
Click to collapse
Not really.
tried working on desire hd stock rom but its not working gets installed successfully but a2sd commands dont work!
HI All,
Hope you can take a look over my setup and help me maximize the space on this phone.
I have rooted, S-off'ed and Followed several guides trying 3 Roms. I like Leedroid best and want to use it going forward. However I keep running out of space after a couple of months and find myself wiping the phone down to start again. despite using the 3.0.8.2 a2sd version of the rom.
I've read posts about this issue suggesting A2SD reintall or terminal emulator fix's but they refer to CM7 and other Roms so I am fearful of trying them out without consulting the experts.
Can anyone see what I'm doing wrong or suggest a new approach I would be willing to wipe everything and start again I.e re-install apps from the market because TB keeps my contact sms etc safe.
I dont know what a2sd leedroid comes packaged with. the "a2sd reinstall" command from terminal is something specific to Dark Tremor a2sd. This can be installed on any rom, so it could be that. This wont break anything if you have any other a2sd solution as these commands wont be programmed into the script.
If it has got Dark tremor, moving dalvik-cache onto sd ext would save space too. the command for that would be "a2sd cachesd"
Hi RootSU, Thanks for your reply. I've downloaded the terminal emulator and tried those commands, doesn't seem to work.
I suppose what I'm trying to Ask is: To run Leedroid what is the optimum configuration to fit the most apps without getting running low message coming up.
Here is the quick sys info which i got too.
LeeDroid ROM does not have the DarkTremor's script - so the a2sd commands won't work. AFAIK, it uses MCRScripts.
There should be an application like that in the ROM with preinstalled scripts.
The last time is used there was and after running the script which moved the dalvik to the SD the problem got solved.
This is the link for the patch:
http://forum.xda-developers.com/showpost.php?p=15732939&postcount=384ton
Yep, just found that add o in the thread:
http://leedroid.ftp.rshost.eu/Bravo_Addons/Move-Dalvik-to-sdext.zip
if you havent done this, it will save a lot of space.
Ok thanks,
I saved that file to SDcard rebooted to recovery and Applied Zip file, It seemed to go well took a while but no errors. Here is a new pic of system info not really much change is there ?
Can you suggest any other checks ?
Not really. may be you already did this? How many apps have you got?
Are you s-off? Maybe try data++ version?
i used to use this rom, now on HD port
can't remember, but i think the A2SD rom already moves the dalvik cache to ext, so flashing that zip won't save anything. you must have a lot of data on internal
to maximise internal storage use the data++ ROM
there is a very good FAQ on how to install it, and more importantly, explains the difference.
since you are already S-OFF, it involves changing hboot to maximise internal memory. then you can move dalvik to ext to have even more...
thanks guys makes sense, Eddie giving this FAQ a go.
Hello guys!
I've recently tried to install a better android version.
Tried different CM10 ROMs. Most of them worked, but discovered that i can't fully use A2SD, Link2SD or Mounts2SD, which turned out to be a big disappointment, so i went back to CM 7.2.0.1.
What's the point of having 4.2.2 if i can only install maximum 10 apps?
A2SD seemed to be pretty good untill I've noticed that i have to reboot every time after i install an app, and on top of that, it would move to ext only a part of the new app..
Question 1:
Am i doing something wrong or what? Is there a way to move the system apps on the ext4 partition like i am doing with the help of Mounts2SD on CM7.2?
Question 2:
I'm using a Class 10 32GB Sandisk Extreme. Is it ok to use 8192kb on CFQ? What do u guys think i should use for the I/O scheduling?
Question 3:
I'm also using V6 Supercharger Script which is awesome!! But sometimes i get lags or the phone freezes. Do u think that this is a script conflict or the I/O schedule is wrong?
Thanks in advance!
My configuration in the ss bellow..
moved to Q&A.
Please do not post in the dev forum unless you are releasing development work.
Sorry, i thought that this was the correct section for my questions.
For app space stuff, see my replies in this similar thread http://forum.xda-developers.com/showthread.php?t=2573306
- Check your sd partition
- You should be on cm7r2 hboot for more efficient use of space
Hey everybody,
Have a strange problem. My phone keeps saying I'm low on space, despite the fact that I have a 1,5 gb sd-ext, and still ~880 mb free.
The sd is formatted with 4ext, and the partition is ext4. The SD card is class 10.
See the attached file for a visual of what I'm talking about.
Hope that someone can help
Cheers,
- H
EDIT:
Aaaaannd, now it's stuck on boot...
I had simmilar problems with various APP 2 SD scripts, including INT2EXT (+)
I had problems downloading form Play Store, because it told me that I don't have enough space, nor I could install from SD Card.
My suggestion is:
1.Wipe everything except SD Card and flash the rom again, you can't boot in it anyway, can you?
2. Find a rom to install, and flash it.
3. Search for better app2sd scripts, ( If using gingerbread you could use Link2SD - Used it alot in gingerbread, it doesn't work well in ICS & up )
My questions:
What rom are you using?
What APP2SD script are you using?
Click to expand...
Click to collapse
Silly me, noticed your signature.
If you are stuck in a bootloop, and don't know what to do, do following:
1. Turn off your phone.
2. Boot in recovery
3. Connect your phone to pc with USB
4. If you're using 4ext then it will be toggle usb storage, if clockworkmod ( classic ) then it will be under mounts
5. Copy a downloaded rom to your sd card.
6. Flash it!
Hey bro,
Thanks for the response..
No, it boots just fine.. it's just weird.. but I think I get it now.. It has something to do what the script actually moves to sd-ext, what HBOOT u use, i.e. how much space is allocated for system, data, etc.. ..
You see, before I got a Desire, I had a Samsung Galaxy Gio, running a custom CM 7 ROM, with Darktremor a2sd script. That worked PERFECTLY for me, coz I had set it up to move more or less everything to sd-ext. And although I had almost 1GB of apps, I didn't notice any lag or performance loss.
But now, I'm new to Desire, and I don't know a lot of these "new" a2sd scripts and how to configure them properly.. So it's gonna take a little time experimenting what works, and so on.
The first custom ROM for Desire I installed was a MildWild GB ROM - great ROM. Fast, stabile, just awesome..
But then I started experimenting with various ICS and JB ROMS, and then the problems began to show.. but basicly I think, and I sure dont wont to offend anybody, that the devs should make their ROMS without a a2sd script of their choosing, or at least give us an option to install it or not. Then we're (more) free to install whatever a2sd script we wish, without having to go through /init.d and removing existing script, and what not..
But yeah, it's all good.. Just got play around with it some more
Thanks anyway tho,
- H
EvilShadeZ said:
I had simmilar problems with various APP 2 SD scripts, including INT2EXT (+)
I had problems downloading form Play Store, because it told me that I don't have enough space, nor I could install from SD Card.
My suggestion is:
1.Wipe everything except SD Card and flash the rom again, you can't boot in it anyway, can you?
2. Find a rom to install, and flash it.
3. Search for better app2sd scripts, ( If using gingerbread you could use Link2SD - Used it alot in gingerbread, it doesn't work well in ICS & up )
Silly me, noticed your signature.
If you are stuck in a bootloop, and don't know what to do, do following:
1. Turn off your phone.
2. Boot in recovery
3. Connect your phone to pc with USB
4. If you're using 4ext then it will be toggle usb storage, if clockworkmod ( classic ) then it will be under mounts
5. Copy a downloaded rom to your sd card.
6. Flash it!
Click to expand...
Click to collapse
hhaznadar85 said:
Hey bro,
Thanks for the response..
No, it boots just fine.. it's just weird.. but I think I get it now.. It has something to do what the script actually moves to sd-ext, what HBOOT u use, i.e. how much space is allocated for system, data, etc.. ..
You see, before I got a Desire, I had a Samsung Galaxy Gio, running a custom CM 7 ROM, with Darktremor a2sd script. That worked PERFECTLY for me, coz I had set it up to move more or less everything to sd-ext. And although I had almost 1GB of apps, I didn't notice any lag or performance loss.
But now, I'm new to Desire, and I don't know a lot of these "new" a2sd scripts and how to configure them properly.. So it's gonna take a little time experimenting what works, and so on.
The first custom ROM for Desire I installed was a MildWild GB ROM - great ROM. Fast, stabile, just awesome..
But then I started experimenting with various ICS and JB ROMS, and then the problems began to show.. but basicly I think, and I sure dont wont to offend anybody, that the devs should make their ROMS without a a2sd script of their choosing, or at least give us an option to install it or not. Then we're (more) free to install whatever a2sd script we wish, without having to go through /init.d and removing existing script, and what not..
But yeah, it's all good.. Just got play around with it some more
Thanks anyway tho,
- H
Click to expand...
Click to collapse
How did you partition your sd-card? Using what?
Using 4ext - following ur guide actually... (tnx btw - awesome guide)
Sent from my HTC Desire using xda app-developers app
hhaznadar85 said:
Using 4ext - following ur guide actually... (tnx btw - awesome guide)
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Try re-flashing the CM7 and try using INT2EXT+, sometimes APP2SD scripts doesn't work as they should, If you don't want to use scripts, you could use Link2SD - good choice aswell.
My setup:
Previously:
Stock Alpha Rev HBOOT
1.5 GB SD-EXT
4ext
cm7.2
Int2ext+
Now:
Everything the same except app2sd script and rom.
Evervolv Kitkat w/ built in App2SD
EvilShadeZ said:
Try re-flashing the CM7 and try using INT2EXT+, sometimes APP2SD scripts doesn't work as they should, If you don't want to use scripts, you could use Link2SD - good choice aswell.
My setup:
Previously:
Stock Alpha Rev HBOOT
1.5 GB SD-EXT
4ext
cm7.2
Int2ext+
Now:
Everything the same except app2sd script and rom.
Evervolv Kitkat w/ built in App2SD
Click to expand...
Click to collapse
Yeah, tell me about it.. altough, I've never had problems with the "old", original DarkTremmor a2sd script.. it's this "new" modified a2sd xdata thing that bugs me.. And I can't, for the life of me, figure out how to remove it completly, and replace it with the original DT a2sd script.. (it's built-in VJ's JB ROM, which I'm currently playing with.. )
But thanks anyway man,
- H
hhaznadar85 said:
Yeah, tell me about it.. altough, I've never had problems with the "old", original DarkTremmor a2sd script.. it's this "new" modified a2sd xdata thing that bugs me.. And I can't, for the life of me, figure out how to remove it completly, and replace it with the original DT a2sd script.. (it's built-in VJ's JB ROM, which I'm currently playing with.. )
But thanks anyway man,
- H
Click to expand...
Click to collapse
If there's app2sd in rom, but you need to activate it with terminal, then you might consider not to. Just give other APP2SD / Mount 2 SD scripts a try.
Link for INT2EXT:
CronMod Scripts ( INT2EXT )
I suggest you taking Int2Ext+
INT2EXT+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
Click to expand...
Click to collapse
Never really had problems with space running out on internal w/ it.
As ICS / JB roms go, I find them slow, and unresponsive, but kitkat is opposite
EvilShadeZ said:
If there's app2sd in rom, but you need to activate it with terminal, then you might consider not to. Just give other APP2SD / Mount 2 SD scripts a try.
Link for INT2EXT:
CronMod Scripts ( INT2EXT )
I suggest you taking Int2Ext+
Never really had problems with space running out on internal w/ it.
As ICS / JB roms go, I find them slow, and unresponsive, but kitkat is opposite
Click to expand...
Click to collapse
Wow, thanks a lot! These CronMod scripts look great. Gonna try it out tomorrow.
But this is just weird.. I tried pretty much everything; not activating it in terminal, then try to remove it; stuck on boot, tried replacing the script manually using root explorer --> stuck. Tried replacing the script in the ROM package (zip file) before flashing it --> stuck.. I'd just LOVE to see the decompiled framework, to see how the f**k it's embeded in this ROM, to make it so impossible to get rid of...?!?
Cheers,
- H
hhaznadar85 said:
Wow, thanks a lot! These CronMod scripts look great. Gonna try it out tomorrow.
But this is just weird.. I tried pretty much everything; not activating it in terminal, then try to remove it; stuck on boot, tried replacing the script manually using root explorer --> stuck. Tried replacing the script in the ROM package (zip file) before flashing it --> stuck.. I'd just LOVE to see the decompiled framework, to see how the f**k it's embeded in this ROM, to make it so impossible to get rid of...?!?
Cheers,
- H
Click to expand...
Click to collapse
If you want the same rom:
Open .zip package of the on pc.
Then Go in system/etc/init.d
delete something like: mountext and app2sd ( should look simmilar )
Then archive it (System, BOOT.img, META-INF ) Swith archiver program - Winrar perhaps? ( Using .ZIP ) extension.
Then put it in your sd card.
Then Wipe everything ( except sdcard )
Flash the rom.
Flash the Int2Ext script,
Wipe sd-ext again.
Boot.
If this doesn't work for you, you're doomed!
j/k. Just try another rom.
Highly suggest trying latest nightly for Evervolv Kitkat. (Evervolv / Bravo page.)
Since it's nightly you'll gonna find bugs, but from my experience it's better than all the ICS / JB roms. Might argue about GB roms.
If you decide to get KitKat, you can enable App2SD in it's terminal (not in the rom - fetch it at google play)l:
su
a2sd install
y
n
y
Click to expand...
Click to collapse
NO EVERVOLV NIGHTLY TALKS HERE!