"Old" Apps2SD for FroYo Roms

"Old" Apps2SD for FroYo Roms - Desire General

Is it possible to have the old Apps2SD run on a FroYo Rom for Desire?
Because the built in Apps2SD still gets rid of some of my Internal Storage as if it downloads it internally then just installs externally keeping the internal version.
Over on the MoDaCo forum, Paul has the old Apps2SD on a FroYo Rom but for Nexus One
Is it only possible for completely rooted phones?
Sorry for sounding noobish, I'm a newbie

shoey-n said:
Is it possible to have the old Apps2SD run on a FroYo Rom for Desire?
Because the built in Apps2SD still gets rid of some of my Internal Storage as if it downloads it internally then just installs externally keeping the internal version.
Over on the MoDaCo forum, Paul has the old Apps2SD on a FroYo Rom but for Nexus One
Is it only possible for completely rooted phones?
Sorry for sounding noobish, I'm a newbie
Click to expand...
Click to collapse
Can you give a link?

I have the same problem with the built in apps2sd. My internal storage is full while I installed 99% of my apps external

lincore said:
Can you give a link?
Click to expand...
Click to collapse
Klick me I think its that
The new froyo a2sd method is bad, i love the old style too

Yer, that's the post I've seen, I've left a comment on that thread asking about the Apps2SD but no one has answered me yet.
The built in one in FroYo is terrible and fills up your SD Card and your Internal Storage.
If anyone knows how to implement the old style Apps2SD into FroYo, I think the majority will prefer it

I posted a week or so ago asking those who've developed in the Froyo framework just what the deal is with ext partitions. Got no response. Is it something in the Froyo kernel or the framework that poses a problem? Personally, I don't understand why ROM cooks are giving the new a2sd breathing room, as it's pants. In (for example) Richard Trip's Froyo where he exhorts us to get rid of our ext partitions before flashing, what would stop us just symlinking /data/app etc over to the SD?

fxone said:
Klick me I think its that
The new froyo a2sd method is bad, i love the old style too
Click to expand...
Click to collapse
I'm not modaco premium member and can't use online kitchen, if you provide me link where i can dl this rom with A2SD+ (old A2SD), I can try to bring it for our device

Yes, Froyo does support old a2sd, at least on my DeFrost 0.9b.
The problem is, a2sd mount the ext2 partition in /system/etc/init.d scripts.
For some reason unknown, DeFrost does not execute init.d files during boot.
Thus you will see bootanimation looping...
If you would like to try, use adb to login to the device whenyou see boot animation.
and run
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
this should be in boot.img-ramdisk/init.rc
hope it will appear in the next release.

ksc91u said:
Yes, Froyo does support old a2sd, at least on my DeFrost 0.9b.
The problem is, a2sd mount the ext2 partition in /system/etc/init.d scripts.
For some reason unknown, DeFrost does not execute init.d files during boot.
Thus you will see bootanimation looping...
If you would like to try, use adb to login to the device will you see boot animation.
and run
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
this should be in boot.img-ramdisk/init.rc
hope it will appear in the next release.
Click to expand...
Click to collapse
Ah. So basically, we need to somehow make sure the SD card is mounted early during the boot process then?

Try this update.
DeFrost 0.9b original kernel.
modified initramfs.
DeFrost only plz.

Yes, Froyo does support old a2sd, at least on my DeFrost 0.9b.
The problem is, a2sd mount the ext2 partition in /system/etc/init.d scripts.
For some reason unknown, DeFrost does not execute init.d files during boot.
Thus you will see bootanimation looping...
If you would like to try, use adb to login to the device whenyou see boot animation.
and run
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
this should be in boot.img-ramdisk/init.rc
hope it will appear in the next release.
Click to expand...
Click to collapse
It will be at some point, but there were other priorities also. Be patient please

Related

Installation Failures for Insanely Large Apps

(I posted this in general, but I think there's too much technical info for any user to be able to assist. I realize this isn't development related, but delete the post if it's too off-topic please.)
Over the past few months since 'Grocery iQ' has been out, I have been trying to install it. Despite trying it on several different ROMs on my old G1 and now several different ROMs on my Slide (including now Froyo) it seems that it doesn't like to install. From my experience it is the biggest direct-download from the Market that I have come across weighing in at 8.01MB - by 'direct-download' I mean that the application itself is downloaded entirely from the Market and the size I reference isn't from 'additional' files downloaded to the SD card after running the program.
Everytime I try to install it the system just says 'Installation Unsuccessful' and one time I got an error code: -18 (on Eugene's Froyo Kanged RC1). Fortunately I'm fluent enough with the device to have my SDK setup and I grabbed a logcat from the adb server. Using what debugging mind-set I've had from coding I was able to find the problem is:
Code:
D/VoldCmdListener( 122): asec list
I/PackageHelper( 1703): Size of container 10 MB 8401843 bytes
D/VoldCmdListener( 122): asec create smdl2tmp1 10 fat {} 10010
E/Vold ( 122): ASEC file '/mnt/secure/asec/smdl2tmp1.asec' currently exists - destroy it first! (No such file or directory)
W/Vold ( 122): Returning OperationFailed - no handler for errno 98
E/PackageHelper( 1703): Failed to create secure container smdl2tmp1
E/DefContainer( 1703): Failed to create container smdl2tmp1
What exactly is happening here? It almost looks like it's trying to create a secure environment for the install or the program uses copy-protection. Can someone please elaborate on this - hopefully a dev?
Thanks!

That's odd, it installed fine for me on SlideM4
How much free space do you have? Are you doing the install over WiFi?
After doing some research I believe that ASEC is part of the copy protection scheme used in a2sd on Froyo.

r0man said:
How much free space do you have? Are you doing the install over WiFi?
Click to expand...
Click to collapse
I have 95.51MB free >.> And I'm not sure why WiFi or 3G would matter, but I've tried both ways (unintentionally).
r0man said:
After doing some research I believe that ASEC is part of the copy protection scheme used in a2sd on Froyo.
Click to expand...
Click to collapse
Interesting. I'm not using A2SD though since my SD card is formatted entirely FAT32 (Froyo didn't like my card being FAT32+EXT3+Swap), but I wonder if Froyo A2SD runs entirely on FAT32? It would be complicated for Google to require people to partition their SD cards now that Froyo has A2SD built-in.

nbetcher said:
I have 95.51MB free >.> And I'm not sure why WiFi or 3G would matter, but I've tried both ways (unintentionally).
Interesting. I'm not using A2SD though since my SD card is formatted entirely FAT32 (Froyo didn't like my card being FAT32+EXT3+Swap), but I wonder if Froyo A2SD runs entirely on FAT32? It would be complicated for Google to require people to partition their SD cards now that Froyo has A2SD built-in.
Click to expand...
Click to collapse
Downloads over networks that aren't stable like 3G can cause bad downloads.
Froyo runs a2sd entirely on the SD card, if the app doesn't have the proper line of code specifying whether to go to SD card or internal memory I think that it won't install properly on Froyo, not sure though.

r0man said:
Froyo runs a2sd entirely on the SD card, if the app doesn't have the proper line of code specifying whether to go to SD card or internal memory I think that it won't install properly on Froyo, not sure though.
Click to expand...
Click to collapse
I'm still not sure whether it tries to use the FAT32 partition for A2SD (which I doubt since it cannot do symlinks among other stuff) or EXT2/3 on the SD card if present.
Anyways, I was fiddling with the settings more on the phone and there's a new option in the "Settings" that is "Cyanogenmod Settings." In there you can tell it whether to install to your SD card or not (it's not like the old checkbox for A2SD). I told it internal storage and the program still failed to install for the same reason.

nbetcher said:
I'm still not sure whether it tries to use the FAT32 partition for A2SD (which I doubt since it cannot do symlinks among other stuff) or EXT2/3 on the SD card if present.
Anyways, I was fiddling with the settings more on the phone and there's a new option in the "Settings" that is "Cyanogenmod Settings." In there you can tell it whether to install to your SD card or not (it's not like the old checkbox for A2SD). I told it internal storage and the program still failed to install for the same reason.
Click to expand...
Click to collapse
That is weird because I was gooing to tell you to go into CM settings and make sure to select internal. Maybe it is just the app???

sultan.of.swing said:
That is weird because I was gooing to tell you to go into CM settings and make sure to select internal. Maybe it is just the app???
Click to expand...
Click to collapse
No - no one on the market has made any comment regarding the problem. In fact everyone is saying how they love the program (minus the occasional moron).
I've had this same problem with my G1 and on a couple other ROMs on the Slide. R0man said it installed for him though on SlideMR4

Installed on my MR1V4-Remix over 3G fine. Did you try an ADB install through the SDK?
I can post for u if u wanna try that.
Sent from my MR1 V4 Remix 3G using Tapatalk

Fordude said:
I can post for u if u wanna try that.
Click to expand...
Click to collapse
Post the APK? That would be great. Thanks!

nbetcher, Froyo doesn't put the full app on SD card, just the majority of the files.

GroceryIQ
Really basic:
1. download
2. copy/move to SDK tools directory
3. From SDK tools directory (where file is downloaded) type this:
adb install com.coupons.GroceryIQ.apk
Hope this helps!

Fordude said:
GroceryIQ
Really basic:
1. download
2. copy/move to SDK tools directory
3. From SDK tools directory (where file is downloaded) type this:
adb install com.coupons.GroceryIQ.apk
Hope this helps!
Click to expand...
Click to collapse
Thanks for the upload. I already have an ADB environment setup, but unfortunately this method did not change the error. ADB returned:
Code:
pkg: /data/local/tmp/com.coupons.GroceryIQ.apk
Failure [INSTALL_FAILED_CONTAINER_ERROR]
ADB's logcat shows the same error as before (when installed using Market).

Slightly off topic, but you do ask about it, and I don't think I've seen it answered here, but in one of Eugene's thread, they do state that Froyo's inherent a2sd is all handled on FAT32 partitions. And I think on Eugene's Froyo release, it specifically runs into issues if you have an EXT partition... Just some anecdotal info.

froyo has apps2sd built in so no partitioning of the card is required. Just straight fat32 which is what it should be by default. This makes sense because the mainstream user isn't going to have a clue on how to partition an SD card and that just wouldn't be very user friendly...
And yes the froyo CM rom will have issues if your card has an ext but Eugene said apps2sd doesn't even work on the rom anyways. It's there but it does nothing.

nbetcher said:
Thanks for the upload. I already have an ADB environment setup, but unfortunately this method did not change the error. ADB returned:
Code:
pkg: /data/local/tmp/com.coupons.GroceryIQ.apk
Failure [INSTALL_FAILED_CONTAINER_ERROR]
ADB's logcat shows the same error as before (when installed using Market).
Click to expand...
Click to collapse
The apk is corrupted, apparently.

r0man said:
The apk is corrupted, apparently.
Click to expand...
Click to collapse
Nope. I used the same APK as Fordude (whom was able to install the program) provided through a reliable channel. If we took MD5Sums of both files I'd bet $10 that they're both the same.
After researching this extensively I'm coming to the conclusion that:
* This is a protected app; and
* Protected apps are broken on CM6/Espresso at the moment; OR
* There is some mis-configuration with Eugene's ROM; OR
* The kernel that is being used doesn't support a new(er) version of the dm_crypt api/module and/or the usage there-in with Froyo.
The last one in that list is the most likely, in my opinion. Many things like the camera are the first things to break in these major system upgrades since the software is using different APIs than the kernel module supports. (Remember that the kernel being used is still from the ORIGINAL shipment of this phone - 2.6.29, which is now over a year old and was specifically compiled for Espresso-stock.)
While I don't expect his ROM to be finished, I don't think this is something that anyone is even specifically aware of yet. It would be nice to know what Eugene thinks of this though.
Thanks for the help guys. Hopefully this will provide the community with some more information to make Froyo come to us quicker.

If we took MD5Sums of both files I'd bet $10 that they're both the same.
Click to expand...
Click to collapse
MD5Sum of the file I provided 38bef197bcd5133a20abf845e241ff18

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [HeroGSM] (01/29/2011)

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

Apps2SD on HTC Hero with default 2.1 ROM

Hi all, i've bought an HTC Hero with HTC's 2.1 ROM, and since it's still in warranty i don't want to flash it with a custom ROM now
I can't find a way to install apps on the SD, because all i find are cusom roms which already have apps2sd enabled...
What can i do if i want to keep my warranty?

Cero92 said:
Hi all, i've bought an HTC Hero with HTC's 2.1 ROM, and since it's still in warranty i don't want to flash it with a custom ROM now
I can't find a way to install apps on the SD, because all i find are cusom roms which already have apps2sd enabled...
What can i do if i want to keep my warranty?
Click to expand...
Click to collapse
no. you need root. If you like your warranty, and your phone gets broken in some way while rooting, you can just run the official RUU and return it back to stock state, and your provider will never know.

Cero92 said:
Hi all, i've bought an HTC Hero with HTC's 2.1 ROM, and since it's still in warranty i don't want to flash it with a custom ROM now
I can't find a way to install apps on the SD, because all i find are cusom roms which already have apps2sd enabled...
What can i do if i want to keep my warranty?
Click to expand...
Click to collapse
You can't enable app2sd without root, and if I am not mistaken, it's the rooting the will void your warranty....
I don't think you can mess with anything at the system level without voiding your warranty, which makes sense.
But, Andyt95 is right, if you mess something up, the RRU should restore it to the unrooted state.

I rooted it using this guide: http://forum.xda-developers.com/showthread.php?t=645253
I followed the first part up to the fourth point (i think recovery img is needed to flash, not to root, am i wrong?)
But, now?

ya recovery image needs when you want to flash something in your mobile . But to root your phone it don't need recovery
there are many apps out there which can give you root & most of them are compatible for Hero

Yes i rooted it
But what to do next to install apps on sd?
I can't find a tutorial, my mistake?

Cero92 said:
Yes i rooted it
But what to do next to install apps on sd?
I can't find a tutorial, my mistake?
Click to expand...
Click to collapse
You need to partition your card with a EXT 2 partition. Then install any custom ROM. Most support app2SD

nirmalv said:
You need to partition your card with a EXT 2 partition. Then install any custom ROM. Most support app2SD
Click to expand...
Click to collapse
Yes, but i'd like to jeep the default ROM for a while
Sent from my HTC Hero using XDA App

Cero92 said:
Yes, but i'd like to jeep the default ROM for a while
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
The problem is, its not a simple update, it needs support in the kernel ramdisk, busybox installed and some scripts.
Usually I don't like to recommend the Darktremor app2sd, because its a bit too bloated in my eyes, and I don't like things which are so complicated I can't understand them (and I have tried, but he has so much script for a relatively simple task...).
Anyway in this case, I think its your only bet.
DO A NANDROID BACKUP BEFORE YOU TRY ANYTHING - ESPECIALLY THIS!
EDIT: Taking another look, even it (the Darktremor app2sd) does not seem to fix the kernel's ramdisk. You might want to test it after a nandroid backup on the odd chance I am wrong (i.e. if your original ROM does run the init.d scripts - mine did not). I am afraid if I am right, the only way you can keep the original ROM and enable app2sd, is if you unpack the kernel ramdisk and edit the init.rc to run the init.d scripts - which is a bit more complicated than it sounds, but not that hard if you have the proper background....

erasmux said:
The problem is, its not a simple update, it needs support in the kernel ramdisk, busybox installed and some scripts.
Usually I don't like to recommend the Darktremor app2sd, because its a bit too bloated in my eyes, and I don't like things which are so complicated I can't understand them (and I have tried, but he has so much script for a relatively simple task...).
Anyway in this case, I think its your only bet.
DO A NANDROID BACKUP BEFORE YOU TRY ANYTHING - ESPECIALLY THIS!
EDIT: Taking another look, even it (the Darktremor app2sd) does not seem to fix the kernel's ramdisk. You might want to test it after a nandroid backup on the odd chance I am wrong (i.e. if your original ROM does run the init.d scripts - mine did not). I am afraid if I am right, the only way you can keep the original ROM and enable app2sd, is if you unpack the kernel ramdisk and edit the init.rc to run the init.d scripts - which is a bit more complicated than it sounds, but not that hard if you have the proper background....
Click to expand...
Click to collapse
I'm down to give this a try, my girl wants the stock rom and a2sd. Dam cake eaters! but is there a process to follow with this? I'm good enough to follow a process but not create it for a2sd. Any links to reference??

da-pharoah said:
I'm down to give this a try, my girl wants the stock rom and a2sd. Dam cake eaters! but is there a process to follow with this? I'm good enough to follow a process but not create it for a2sd. Any links to reference??
Click to expand...
Click to collapse
why stock though? have you considered that villainrom 13 is just like stock but better and has apps2sd? it's a full HTC sense 2.1 rom but rooted with apps2sd and a few small additions to ensure it runs as fast as possible and gives as much room as possible and runs a custom kernel ***
and you can revert by flashing an RUU which is super easy to do (I've done it before for warranty reasons) and the RUU (stock rom) works exactly the same, in fact IS exactly the same except for the features you're asking for.
***(which is pretty much required for apps2sd unless you want to hack it for a while and know how to do it yourself (it's a lot to ask the devs here to tell you everything you need to do if you're not a kernel developer already imho and even then there isn't a guarantee you wont' mess up your phone's stock rom).

dkelley said:
why stock though? have you considered that villainrom 13 is just like stock but better and has apps2sd? it's a full HTC sense 2.1 rom but rooted with apps2sd and a few small additions to ensure it runs as fast as possible and gives as much room as possible and runs a custom kernel ***
and you can revert by flashing an RUU which is super easy to do (I've done it before for warranty reasons) and the RUU (stock rom) works exactly the same, in fact IS exactly the same except for the features you're asking for.
***(which is pretty much required for apps2sd unless you want to hack it for a while and know how to do it yourself (it's a lot to ask the devs here to tell you everything you need to do if you're not a kernel developer already imho and even then there isn't a guarantee you wont' mess up your phone's stock rom).
Click to expand...
Click to collapse
Hi I am trying to find the step by step guide about how to setup Apps2SD working. But having tough time. I have done this with my HD2 but cant find much help for Hero.
I have Recovery image flashed with 8GB (class 6) SD Card.
Next I am looking to partition the card from recovery, but what should be the swap size?
Once partitioned I will try flashing Villainrom 13 ROM.
Thanks

nbhor said:
Hi I am trying to find the step by step guide about how to setup Apps2SD working. But having tough time. I have done this with my HD2 but cant find much help for Hero.
I have Recovery image flashed with 8GB (class 6) SD Card.
Next I am looking to partition the card from recovery, but what should be the swap size?
Once partitioned I will try flashing Villainrom 13 ROM.
Thanks
Click to expand...
Click to collapse
Swap does not seem to work well for the hero, therefore most ROMs will not enable it and I use 0 for the swap size when partitioning. If you still prefer to reserve room for it use something like 32 or 64.

dkelley said:
why stock though? have you considered that villainrom 13 is just like stock but better and has apps2sd? it's a full HTC sense 2.1 rom but rooted with apps2sd and a few small additions to ensure it runs as fast as possible and gives as much room as possible and runs a custom kernel ***
and you can revert by flashing an RUU which is super easy to do (I've done it before for warranty reasons) and the RUU (stock rom) works exactly the same, in fact IS exactly the same except for the features you're asking for.
***(which is pretty much required for apps2sd unless you want to hack it for a while and know how to do it yourself (it's a lot to ask the devs here to tell you everything you need to do if you're not a kernel developer already imho and even then there isn't a guarantee you wont' mess up your phone's stock rom).
Click to expand...
Click to collapse
thanks for the reply! but to answer your in short, My girl doesnt speak geek and gets pissed right away when the ROM she uses acts up. So in short stock roms is whats she likes. I have been trying to convince her to do another ROM but she is hard headed. I think i'll just flash the villainrom 13 and tell her its stock lol. Thanks again i'll check it out!

Tried multiple attempts from scratch every time.
Attempt 1 - Failed
Partitioned my SD Card for EXT 2 (512MB).
Tried flashing of Villainrom 13 ROM along with Dalvik2SD patch.
Installed bunch of apps. Checked size of EXT2 partition. Nothing changed. Its still same size as it was before installing apps. System memory reduced from its original value.
Attempt 2 - Failed
Partitioned my SD Card for EXT 3 (512MB).
Tried flashing of Villainrom 13 ROM along with Dalvik2SD patch.
Installed bunch of apps. Checked size of EXT3 partition. Nothing changed. Its still same size as it was before installing apps. System memory reduced from its original value.
Any suggestions?

nbhor said:
Tried multiple attempts from scratch every time.
Attempt 1 - Failed
Partitioned my SD Card for EXT 2 (512MB).
Tried flashing of Villainrom 13 ROM along with Dalvik2SD patch.
Installed bunch of apps. Checked size of EXT2 partition. Nothing changed. Its still same size as it was before installing apps. System memory reduced from its original value.
Attempt 2 - Failed
Partitioned my SD Card for EXT 3 (512MB).
Tried flashing of Villainrom 13 ROM along with Dalvik2SD patch.
Installed bunch of apps. Checked size of EXT3 partition. Nothing changed. Its still same size as it was before installing apps. System memory reduced from its original value.
Any suggestions?
Click to expand...
Click to collapse
System memory is still reduced with app2sd, since the /data/data folder is not moved to the SD.
Assuming you have adb working, check these two commands:
Code:
adb shell df -h
adb shell ls -ld /data/app
If you think you still have a problem please post the result of these two commands.

erasmux said:
System memory is still reduced with app2sd, since the /data/data folder is not moved to the SD.
Assuming you have adb working, check these two commands:
Code:
adb shell df -h
adb shell ls -ld /data/app
If you think you still have a problem please post the result of these two commands.
Click to expand...
Click to collapse
Do I run this command in terminal emulator on droid or use droid explorer > Terminal Command?
Can Root Explorer help? I am getting adb permission denied from terminal emulator.

nbhor said:
Do I run this command in terminal emulator on droid or use droid explorer > Terminal Command?
Can Root Explorer help? I am getting adb permission denied from terminal emulator.
Click to expand...
Click to collapse
well, I actually meant connecting the device w/ a USB cable to your computer and then from a command prompt (i.e. start -> run -> "cmd") using the "adb.exe" utility that comes with the android SDK (under the tools folder)....
You can run the same commands in a terminal windows just without the "adb shell":
Code:
df -h
ls -ld /data/app
Only problem is that then it you can't copy paste your result here.
for the "df -h" command take note of the mount of your sdcard which should start like this line:
Code:
/dev/block/mmcblk0p2 720.9M 506.3M 178.0M 74% /sd-ext
I would assume that for you the mount point (last value) would be /system/sd.
next check the "ls -ld /data/app" and make sure it is linked to the same location, in my case it is:
Code:
lrwxrwxrwx 1 root root 11 Apr 20 09:59 /data/app -> /sd-ext/app

erasmux said:
well, I actually meant connecting the device w/ a USB cable to your computer and then from a command prompt (i.e. start -> run -> "cmd") using the "adb.exe" utility that comes with the android SDK (under the tools folder)....
You can run the same commands in a terminal windows just without the "adb shell":
Code:
df -h
ls -ld /data/app
Only problem is that then it you can't copy paste your result here.
for the "df -h" command take note of the mount of your sdcard which should start like this line:
Code:
/dev/block/mmcblk0p2 720.9M 506.3M 178.0M 74% /sd-ext
I would assume that for you the mount point (last value) would be /system/sd.
next check the "ls -ld /data/app" and make sure it is linked to the same location, in my case it is:
Code:
lrwxrwxrwx 1 root root 11 Apr 20 09:59 /data/app -> /sd-ext/app
Click to expand...
Click to collapse
My results from above 2 commands
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.6M 0 95.6M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 162.8M 7.2M 96% /system
/dev/block/mtdblock5 165.8M 11.2M 154.5M 7% /data
/dev/block/mtdblock4 130.0M 58.8M 71.2M 45% /cache
/dev/block/mtdblock4 130.0M 58.8M 71.2M 45% /data/dalvik-cache
/dev/block//vold/179:1
6.8G 4.0G 2.8G 59% /sdcard
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls -ld /data/app
drwxrwx--x 1 1000 1000 2048 Apr 22 01:34 ?[1;34m/data/app?[0m

nbhor said:
My results from above 2 commands
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.6M 0 95.6M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 162.8M 7.2M 96% /system
/dev/block/mtdblock5 165.8M 11.2M 154.5M 7% /data
/dev/block/mtdblock4 130.0M 58.8M 71.2M 45% /cache
/dev/block/mtdblock4 130.0M 58.8M 71.2M 45% /data/dalvik-cache
/dev/block//vold/179:1
6.8G 4.0G 2.8G 59% /sdcard
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls -ld /data/app
drwxrwx--x 1 1000 1000 2048 Apr 22 01:34 ?[1;34m/data/app?[0m
Click to expand...
Click to collapse
Well, you really do *not* have app2sd enabled (I am sorry for my previous disbelief but I have seen many users in the past which only thought they did not have app2sd enabled).
From your previous posts I understand you are using VR13, so either ask on the VR13 thread how to enable app2sd (you can post the above as proof it is not working for you), or change to a ROM with more "stable" app2sd....

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [DesireZ] (01/29/2011)

What?! Thanks darktremor, used this with my slide, will be testing and update this post asap with feedback.
Just curious though, is this meant for froyo based roms or should it work with gingerbread also?... guess I could test and see. Also do we still need to used the 'a2sd reinstall' and 'a2sd cachesd' commands to install it?
Sent from my T-Mobile G2 using XDA App

will this also work with sense roms?

g1junky said:
will this also work with sense roms?
Click to expand...
Click to collapse
Not sure, that's why we are testing it.

I can't get it to work on CM7 nightly 11 ( That I know of).
Used Clockworkmod to set up the ext partition (which doesn't specify which filesystem so i'm guessing either ext2 or ext3); set partition to 512mb and swap to 0mb.
Card partitioned successfully according to CWM; upon flashing the app2sd.zip the installation goes through all steps and posts that the install was successful even though the little check box by install successful is the only one that is starred. I noticed that during the install the script mounts /system and /data to write to them...not sure if that is affected by GB. I thought I read somewhere that this script was designed to check for ext4.
Hell, idk lol. I nandroided and went for it, these are my findings.
scratch that, there's a part two i missed that involves command line functions in the terminal emulator app. It looks like it's working to me.
Edit2: From what ive moved to /sd-ext so far everything seems to be working. Moved my apps, app data, dalvik cache and /data/data.
So far I havent experienced any data loss when moving /data/data.

There's no reason it shouldn't work with Gingerbread, other than the usual suspect of the rom doesn't launch scripts at boot or doesn't have EXT support.
As for the commands, you shouldn't have to rerun those commands if you are upgrading.
KCRic said:
What?! Thanks darktremor, used this with my slide, will be testing and update this post asap with feedback.
Just curious though, is this meant for froyo based roms or should it work with gingerbread also?... guess I could test and see. Also do we still need to used the 'a2sd reinstall' and 'a2sd cachesd' commands to install it?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse

Yes, it should. I'm running a Sense UI rom on my Evo and it has 2.7.5.3 Beta 02.
g1junky said:
will this also work with sense roms?
Click to expand...
Click to collapse

I can honestly say that so far everything seems to be working well on my end. Dropped ~100megs of internal space usage and sent it to the sd.
The phone does seem a bit snappier, does this style of app2sd stress the card more than usual?

hmm.
I'm running cm 7 nightly 11, set 512mb, 0mb swap and I think I got everything right. Strangely enough, I keep getting reboots every time i run a command in terminal.
edit: a2sd command*

SWEEET..........
I too can confirm that this works with CM7 Nightly "Gingerbread" sweet, installed the zip file from recovery, QUICK NOTE: Had to mount /system and mount /data in recovery before installing the zip file from sdcard. This is great apps2ext that works with any rom. Now in my titanium back ups it shows three seperate storge locations: internal, SD card and SDCard(a2sd) plus it restored apps I previously had on my ext.2 partition from when I was running Enoms Rom....sweeeeeet.
Also dont forget to run the command in adb shell:
Code:
/system/bin/a2sd cachesd
if you want to move dalvik cache to sd.
UPDATE: internal memory free reads out of 1.37GB Avail. there is 1.28GB FREE and Ive got 77 apps installed right now and about too install a lot more..........
FYI im runnning a 16gb class 10 sd card with a 1024mb ext.2 partition

Most of the code is similar to the previous version. I think the snappiness may be that your SD card is faster than internal storage.
stevencpoynter said:
I can honestly say that so far everything seems to be working well on my end. Dropped ~100megs of internal space usage and sent it to the sd.
The phone does seem a bit snappier, does this style of app2sd stress the card more than usual?
Click to expand...
Click to collapse

Did you type su before you run an a2sd command?
zarskee seven nine said:
I'm running cm 7 nightly 11, set 512mb, 0mb swap and I think I got everything right. Strangely enough, I keep getting reboots every time i run a command in terminal.
edit: a2sd command*
Click to expand...
Click to collapse

Just so everyone knows (may want to add this to the OP you know, so you don't get a million ?'s) these are the commands you HAVE to enter after flashing it in recovery.
Code:
su [ENTER]
cd /system/bin [ENTER]
sh a2sd cachesd [ENTER]
Your phone will reboot and will take a bit to complete - be patient because it's moving all your apps and the dalvik cache.
Notes: Your memory will still drop (not by much) over time because the apps will still store cached memory on the phone. To deal with this use the 'datasd' command to move that info to the sdcard also. Also, use the 'a2sd help' command to find all the functions you can perform with this. If you've used this before then all of this is irrelevant

Was so excited about this , It worked perfectly on CM7 nightly builds but when I went to update the Nightly build from 11 to 12, problems, keep getting reboot, since all my apps including titanium were on EXT, I could not access them, so the modification didn't stick from build to build, had to full data wipe, so I guess I'll be coming back to this when CM7 stable is realeased.

Yah I did. It's a beta on a nightly rom...I'm not surprised that something would be weird. I know it worked sending my dalvik cache to sd for sure, but as far as my apps being reinstalled on sd..im not sure. I followed the directions to the t and i know i didnt skip steps cause i used to use this on my nexus one

joemm said:
Was so excited about this , It worked perfectly on CM7 nightly builds but when I went to update the Nightly build from 11 to 12, problems, keep getting reboot, since all my apps including titanium were on EXT, I could not access them, so the modification didn't stick from build to build, had to full data wipe, so I guess I'll be coming back to this when CM7 stable is realeased.
Click to expand...
Click to collapse
You may have to remove the script in terminal, reinstall the rom than rerun the zip script. I think that should work if you want to keep using this on nightlies

If you change roms (including moving between different nightly builds), you will need to reflash Darktremor.
The only time you don't have to do that is if Darktremor is already added on the rom you are loading. Since CM7 doesn't have Darktremor installed as part of its package, you'll have to reflash each time you change nightly builds.
If you still don't have access to your programs, type a2sd reinstall
My apologies.
zarskee seven nine said:
You may have to remove the script in terminal, reinstall the rom than rerun the zip script. I think that should work if you want to keep using this on nightlies
Click to expand...
Click to collapse

after several days nothing new in this android development section, today i saw something new here, keep your good work, gonna try it when i get home

This is about three months overdue. Unfortunately, job, family and the holiday season got the best of me.
fajarep said:
after several days nothing new in this android development section, today i saw something new here, keep your good work, gonna try it when i get home
Click to expand...
Click to collapse

For me it seems that it doesn't stick. I tried it with cm7, flashed it in recovery and when I booted up to run the commands in terminal they weren't there. No a2sd at all. Guess I could shove all in the ROM prior to flashing and see if that works.

[Script][A2SD]Darktremor 2.7.5.3 Beta 04 [MT4G] (01/29/2011)

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!

Develop Bugs

welcome