saltire
Android Expert
Ah well, so much for trying to be helpful completely forgot about that
@albert_htc - glad you got things sorted, did you use the script to move Dalvik to SD as well after all? Just interested if it works with 2.2.1
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Oxygen 2.2.1 - Disk Space Low !
- Thread starter albert_htc
- Start date
-
- Tags
- htc desire
Ah well, so much for trying to be helpful completely forgot about that
@albert_htc - glad you got things sorted, did you use the script to move Dalvik to SD as well after all? Just interested if it works with 2.2.1
albert_htc
Well-Known Member
Hi
Yep the script works fine with 2.2.1
as does the trackpad wake and widgetlocker
Thanks
Yep the script works fine with 2.2.1
as does the trackpad wake and widgetlocker
Thanks
Oxygen does come with an a2sd script, and these are always automatic. It isn't DarkTremor though, so the a2sd commands in the terminal won't work.
When you say DT wasn't moving things and you had to move them by hand, how did you check where they were and what did you do to move them? If the script is working the apks are moved to ext unless you explicitly move them to SD (which moves them off sd-ext and to the fat partition. However, DT does not move the dalvik cache unless you tell it to, so that still uses internal storage for each app you install. Also if the app has a lib that is not moved, so some apps with large libs use less internal space if you do move them to SD. Both of these can be confusing.
i checked it through the terminal but i am not sure about the commands (it was something like ls -l data i think)
and i knew that the dalvik cache was not on the ext partition
so i tried first to move it through some script dalvik2sd but i had the new clockwork 4 version and it didn't allowed me so i gave up from that method and i installed darktremor script (not sure if this messed up my a2sd , becouse it was already rellocated)
after installing DT i run the check command and saw that the applications are installing on the sd card only the dalvik cache was internal and i changed that and also the zipaign command (not sure if it is worth it... it is loading my applications slow at startup i think)
then i started installing applications and i was thinking that they were going to the sd card but then i saw how my internal memory was filled then i went manually through every one (not every one but almost all) with the move to sd card way
it is not a problem to move them manually but i thought that was the script job ...
now wait a minute DT script is moving the applications to the ext partition that i have ? (i thought i created that 512mb only for the dalvik cache and that the applications are moved to the fat32 sd partition)
p.s on what percentage does your phone turns off ?
i think mine does that at 15% but i am not sure ... i have the phone few days and i have noticed that couple of days ago
so is there something i can change about this ?
calibrate the baterry ? or change some option in the phone that it turns off at lower percentage
The point of any of these a2sd scripts is to move apps to the ext partition. Basically what it does is create a directory /sd-ext/app and make /data/app a symbolic link to that, after which any app that's "on the phone" is actually on sd-ext.
To check this, if I type "ls -l /data/app" in the terminal I see "/data/app -> /sd-ext/app".
Some also move the dalvik cache to sd-ext automatically, some need a add-on to do this (those included with Oxygen and Redux are like this), and DarkTremor can be configured to do it but doesn't by default. The fact that different implementations behave in different ways is a common source of confusion.
One big advantage of moving apps to sd-ext is that you can move apps with widgets, while the widgets will fail if you move the app to fat32.
As for battery, I rarely let mine run that low, but last time I did it was somewhere around 15% when it turned off. You don't want it to over-discharge, but it might be that calibrating will improve it a little. Not bothered for a long time myself though.
To check this, if I type "ls -l /data/app" in the terminal I see "/data/app -> /sd-ext/app".
Some also move the dalvik cache to sd-ext automatically, some need a add-on to do this (those included with Oxygen and Redux are like this), and DarkTremor can be configured to do it but doesn't by default. The fact that different implementations behave in different ways is a common source of confusion.
One big advantage of moving apps to sd-ext is that you can move apps with widgets, while the widgets will fail if you move the app to fat32.
As for battery, I rarely let mine run that low, but last time I did it was somewhere around 15% when it turned off. You don't want it to over-discharge, but it might be that calibrating will improve it a little. Not bothered for a long time myself though.
so except for the widgets is there any other advantage if the applications are on the ext4 part ? like speed or else
i have checked through terminal (ls -l data) and it says that the applications are transfered to the sd-ext/app but then again why did it filled my internal
so now if i install some application it should go on the ext4 part right ? and i can check it with a viewer on windows (i am going to try but i think it goes in the internal)
i have checked through terminal (ls -l data) and it says that the applications are transfered to the sd-ext/app but then again why did it filled my internal
so now if i install some application it should go on the ext4 part right ? and i can check it with a viewer on windows (i am going to try but i think it goes in the internal)
It used to be really easy: this time last year we could simply say a2sd+ using sd-ext moves more of the app, moves all user apps, widgets still work, and you can use the apps while the card is mounted in disk drive mode.
The last three are still true. The "more of the app" has become more complicated though. The reason we'd say more of the app is that using ext also moves the dalvik cache, which the built-in move to sd (i.e. to fat32) does not. But as we've seen, that is optional on some scripts these days, so if you want that advantage you have to make sure you actually get it.
Then there's the fact that moving to fat with gingerbread moves the app's lib, which under Froyo it did not, and moving to ext does not. Some apps have no lib, some have a tiny one, but there are a few which have a large one, and these therefore use less internal storage (/data partition in the phone storage) when moved to fat with a gingerbread ROM. However, while the space-efficient way of handling those apps is to move the dalvik to ext then the app to fat, that then leaves the elements of the app split between 3 locations (ext, fat32 and /data), which isn't a pretty solution.
So the bottom line is that using ext allows you to move more apps than fat (all user apps), run widgets and still use them when the card is mounted on a computer. Compared with moving every possible app to sd the effect on space will depend on which apps you have. Personally I stopped trying to optimise space app by app and moved them all to ext, but I'm not short of internal space.
If you are wondering why someone might choose not to move the dalvik cache, the usual argument given is performance. However, I used to move it with a class 2 card and the performance difference was negligible.
The last three are still true. The "more of the app" has become more complicated though. The reason we'd say more of the app is that using ext also moves the dalvik cache, which the built-in move to sd (i.e. to fat32) does not. But as we've seen, that is optional on some scripts these days, so if you want that advantage you have to make sure you actually get it.
Then there's the fact that moving to fat with gingerbread moves the app's lib, which under Froyo it did not, and moving to ext does not. Some apps have no lib, some have a tiny one, but there are a few which have a large one, and these therefore use less internal storage (/data partition in the phone storage) when moved to fat with a gingerbread ROM. However, while the space-efficient way of handling those apps is to move the dalvik to ext then the app to fat, that then leaves the elements of the app split between 3 locations (ext, fat32 and /data), which isn't a pretty solution.
So the bottom line is that using ext allows you to move more apps than fat (all user apps), run widgets and still use them when the card is mounted on a computer. Compared with moving every possible app to sd the effect on space will depend on which apps you have. Personally I stopped trying to optimise space app by app and moved them all to ext, but I'm not short of internal space.
If you are wondering why someone might choose not to move the dalvik cache, the usual argument given is performance. However, I used to move it with a class 2 card and the performance difference was negligible.