what are the differences and which one is the best?
they're just different ways of moving bits of apps and associated around between various partitions. each thread should give some kind of detail as to how they work. you can browse your partitions using something like 'diskusage' to see.
basically you have system and user apps, app data and dalvik cache. the scripts move different bits around and share them between internal memory /data and sd-ext. i've read that generally app data is better on nand, and needs a faster sd card if you want data on sd-ext. the sd-card also needs to be correctly partitioned regardless of script. ext4 should also in theory be a little faster than ext2 or ext3.
some scripts will appear to 'extend' your internal memory giving the impression of a larger data partition, but in reality it's no different as long as the partition is actually in use.
ultimately each script will give you more space for apps, some more than others. which is 'best' is dependent on a number of factors, sd-card class, rom, hboot, and how many apps you really need . you need to try a few to see any real difference for your setup. nandroid backup, delete the script from system/etc/init.d before flashing a new one.
personally, they're all the 'best' as long as i have 'enough' space for apps, and they aren't crashing or being really slow :good:
Related
1) I have an ext3 partition on my SD card, which means my Desire is A2SD/A2SD+ compliant right? But whether A2SD or A2SD+ is in effect depends on the ROM I'm running - am I right to say this?
2) What exactly is Hboot? I seem to recall having read somewhere that Hboot is an alternative to A2SD... can anybody clarify? (And before you start flaming that there are a thousand and one topics on this already, I tried searching, but search was down)
1. Yes that's correct.
2. Hboot us essentially a different set of partitions for your desire's system. Currently your desire has internal memory split into 250mb system, 150mb data and a cache partition. The rom goes in system, apps in data. If the rom is small (aosp roms are smaller than sense due to the lack of sense which takes up tons of space) you can flash a different hboot which will change the layout of your phones internal memory. N1 table for instance has about 175 for system and a larger data partition, while the oxygen hboot has a tiny (90mb) system partition and a massive (300 odd mb) data partition negating the need for a2sd+ at all.
Hope that helps
Sent from my HTC Desire using XDA App
lick_the_fish said:
1. Yes that's correct.
2. Hboot us essentially a different set of partitions for your desire's system. Currently your desire has internal memory split into 250mb system, 150mb data and a cache partition. The rom goes in system, apps in data. If the rom is small (aosp roms are smaller than sense due to the lack of sense which takes up tons of space) you can flash a different hboot which will change the layout of your phones internal memory. N1 table for instance has about 175 for system and a larger data partition, while the oxygen hboot has a tiny (90mb) system partition and a massive (300 odd mb) data partition negating the need for a2sd+ at all.
Hope that helps
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Super informative, better than I could have hoped for Thanks!
Anyway I'm going to flash CM7 now, but on my previous ROM (GingerVillain), I'm pretty sure A2SD/A2SD+ was working fine, but in Titanium Backup it shows that my internal data partition was pretty congested. Any ideas?
fterh said:
Super informative, better than I could have hoped for Thanks!
Anyway I'm going to flash CM7 now, but on my previous ROM (GingerVillain), I'm pretty sure A2SD/A2SD+ was working fine, but in Titanium Backup it shows that my internal data partition was pretty congested. Any ideas?
Click to expand...
Click to collapse
I'm no expert and don't fully understand how a2sd+ installs apps etc. I don't know if it uses phone data first and then ext partition or what.
Sent from my HTC Desire using XDA App
fterh said:
Super informative, better than I could have hoped for Thanks!
Anyway I'm going to flash CM7 now, but on my previous ROM (GingerVillain), I'm pretty sure A2SD/A2SD+ was working fine, but in Titanium Backup it shows that my internal data partition was pretty congested. Any ideas?
Click to expand...
Click to collapse
Titanium Backup doesn't always show the correct info when it comes to available memory.
On gingervillian you have to use a dalvik-cache to ext script to create space on the internal memory, if you didn't do that then it can fill up quickly.
lick_the_fish said:
I'm no expert and don't fully understand how a2sd+ installs apps etc. I don't know if it uses phone data first and then ext partition or what.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
a2sd+ uses the ext partition on you sd card to move the apk file of applications. however, there are still some parts of the app, mainly the dalvik cache, which remain on the data partition in your phone's internal memory; that's why your internal storage still decreases, even when using an a2sd+-enabled ROM. there are some scripts which will move this dalvik cache to the sd card as well, but be sure you read carefully before applying and pay close attention to whether your card is fast enough so as not to generate performance issues (generally, you would need at least a class-4 card, with a class-6 or higher being recommended)
Hi!
I would know it's better A2SD, A2SD+ or DATA++ in relation of a Class 2 SD (4 GB included in Desire).
Thanks in advance.
Since the Data++ version is claimed to fit in a 90MB /sytem partition, I assume that in this version a large part of the ROM has been moved to the sd-ext. This allows you to use a smaller /system and hence have a larger /data partition (hence the name). I'm not sure (because I've only read the first couple of posts, nothing more) whether the Data++ also includes a2sd, or just assumes you will keep your apps in the enlarged data partition. It's probably in the LeeDroid thread somewhere.
If you are not S-Off then it's easy - you want the a2sd version, no argument.
If you are, and are using a custom mtd or an alpharev table with a small /system, large /data, you could try Data++. Which is better will depend on which works best for you (in terms of speed, number of apps you need to install). I've never used either, so cannot offer any experience there.
Click to expand...
Click to collapse
Source: http://androidforums.com/desire-all-things-root/372688-whats-difference-between-data-a2sd.html
So, the data++ script uses the ext3 partition more than the a2sd/a2sd+ layout (only difference between a2sd/a2sd+ is that with a2sd+ the dalvik cache will also be moved to sd-ext). If you sd card is too slow, there could occur perfomance problems. But I used an class 2 sd card with a2sd+ myself and never had perfomance problems. So I would say it's your choice.
The speed of sd card actually becomes really important if you want to use data2sd (aka data2ext).
Hi!
Just would like to know the pros and cons of formatting into ext4 on my SD.
As far as I can find :
Pros : Supports files larger than 4GB as Fat32 cannot
That's about it I think...
Cons : Windows cannot natively detect such a partition
Why I ask this is I just saw a this post
blahbl4hblah said:
Having sd-ext partition on your sdcard will always be benefical, the phone will run so much better believe me
Click to expand...
Click to collapse
I'm ready to go ext4 if there's any performance gain, who wouldn't? But what gain is there, and what would I lose in return?
ArmedandDangerous said:
Hi!
Just would like to know the pros and cons of formatting into ext4 on my SD.
As far as I can find :
Pros : Supports files larger than 4GB as Fat32 cannot
That's about it I think...
Cons : Windows cannot natively detect such a partition
Why I ask this is I just saw a this post
I'm ready to go ext4 if there's any performance gain, who wouldn't? But what gain is there, and what would I lose in return?
Click to expand...
Click to collapse
You're mixing things up here a bit I think. Sd-ext referrs to having a partition on your sdcard to allow support for Apps2SD (basically being able to move apps to your SD card and run them from there in order to free up space); you'd basically repartition the card so that there's an ext3/4 partition for apps and a FAT32 partition for data.
As for the ext4 filesystem, it does allow for larger file sizes and is also a bit faster but you're correct in the fact that you won't be able to natively mount it on a Windows system.
Sent from my T-Mobile G2 using XDA App
OriginalGabriel said:
You're mixing things up here a bit I think. Sd-ext referrs to having a partition on your sdcard to allow support for Apps2SD (basically being able to move apps to your SD card and run them from there in order to free up space); you'd basically repartition the card so that there's an ext3/4 partition for apps and a FAT32 partition for data.
As for the ext4 filesystem, it does allow for larger file sizes and is also a bit faster but you're correct in the fact that you won't be able to natively mount it on a Windows system.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
But don't we already have Apps2SD in GB, + all the apps that do it for you. How is this different, apart from some apps that can't natively be moved? And why is it faster? Internal memory should always load faster, should it not?
ArmedandDangerous said:
But don't we already have Apps2SD in GB, + all the apps that do it for you. How is this different, apart from some apps that can't natively be moved? And why is it faster? Internal memory should always load faster, should it not?
Click to expand...
Click to collapse
GB has the ability to do Apps2SD but it requires the partitioning as, I believe, a symlink is set up so that partition on the sdcard acts as a part of the devices internal storage.
As for speed, just moving apps to your sdcard won't speed up your phone; what that poster you quoted was talking about (most likely, I'd have to see the original thread) was converting your devices partitions (/system, /data, /cache, etc.) from ext3 to ext4. ext4 is a bit faster however some ROMs do not fully support it.
Sent from my T-Mobile G2 using XDA App
Ok, let's clear this up. GB has Apps2FAT32 (a2sd) natively. A2EXT is completely different but none of that is the point of the OP's question.
When it comes to our phones - there is almost no notable performance gain when using EXT4 over any other EXT format. Our phones don't utilize FAT32 internally - just on the sdcard. EXT4 is designed for use with massive file systems. A couple Gigs really doesn't access it's full potential.
While the question is interesting, I'm not really sure what you're planning on doing. Don't format your sdcard entirely in EXT format, and don't attempt to format your phones partitions as FAT32. The result would be... just don't do it.
Just read this on the portal
http://www.xda-developers.com/andro...hd2-data-successfully-moved-to-ext-partition/
This has two main advantages: larger sized data partition and more speed as EXT is inherently faster for I/O purposes.
Click to expand...
Click to collapse
How do I go about formatting a section of my SD into ext4, with existing SD data intact.
And how do I move apps that area already in my phone's internal memory to the ext4 partition? I know there's an option in ROM Manager and CWM, but just don't want to mess anything up
ArmedandDangerous said:
Just read this on the portal
http://www.xda-developers.com/andro...hd2-data-successfully-moved-to-ext-partition/
How do I go about formatting a section of my SD into ext4, with existing SD data intact.
And how do I move apps that area already in my phone's internal memory to the ext4 partition? I know there's an option in ROM Manager and CWM, but just don't want to mess anything up
Click to expand...
Click to collapse
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
blackknightavalon said:
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
Click to expand...
Click to collapse
Thankfully I am already using meXdroid~ Guess I'll just wait for the new version in the next few days to do the formatting. Can I backup all my apps with Titanium Backup, flash ROM (wipe data/cache and dalvik cache), restore with Titanium.
Or would I have to reinstall every app again so that it goes into the ext4 partition?
blackknightavalon said:
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
Click to expand...
Click to collapse
There's a script to accomplish this on pretty much any ROM. It *should* work on current ROMs too. It's called 'darktremor a2sd'. Still find it amazing people forget about that one when this question comes up because it's one oldest methods of obtaining a2sd.
I'm still not understanding the OP's question. Are you wanting to do this for an IO performance gain or for space? I can understand doing it for space if you have a ton of apps but if you're doing it for performance it's a waste of your time. You're internal partitions should already be in EXT4 format (use 4EXT Recovery if they're not).
KCRic said:
There's a script to accomplish this on pretty much any ROM. It *should* work on current ROMs too. It's called 'darktremor a2sd'. Still find it amazing people forget about that one when this question comes up because it's one oldest methods of obtaining a2sd.
I'm still not understanding the OP's question. Are you wanting to do this for an IO performance gain or for space? I can understand doing it for space if you have a ton of apps but if you're doing it for performance it's a waste of your time. You're internal partitions should already be in EXT4 format (use 4EXT Recovery if they're not).
Click to expand...
Click to collapse
I'm doing it for the performance. Have been using 4EXT for a few days and loving it. Already converted internal memory to ext4 from ext3. If further partitioning my SD card for performance is really not noticeable, then I guess I've got nothing to worry about
Dear XDA forum,
since a few roms i always get a "low on storage" warning, even after factory reset and flashing a new rom.
So i'd want to ask for a small summery of what storage there is inside the desire and on the sdcard and how to solve this problem
My sdcard is 16GB class 10. I didnt partition it manually (i think).
according to my desire it has effective 14.2gb.about 2gb are used and 4gb are free? that doesnt sound right.
so i guess its 2 partitions?
could anyone please tell me which mountpoint is which?
and how do i solve the low storage problem? do i need some a2sd script or do i have to more the internal storage to the sdcard?
which mountpoints do the scripts actarlly move?
i have no problem with repartitioning my sdcard. i was given to understand that u usually need a fat32 partition (for apps i guess) and an ext2/3 partition afterwards. some scripts even allow a swap partition at the end of the sdcard to be used as swap space. is that a good idea?
i know its a lot of questions :/ but i hope for some good answers :>
thanks & greetings,
soomon
my advice would be to backup your sd card and (re)partition using gparted, start from scratch because I don't know what your current configuration is, step 5 here
choose ext3/ext4 partition (max ~1.5GB) depending on rom requirements, most support ext4 and should be slightly faster. most roms don't need swap partition.
in simple terms, your space will get taken up by apps (apks), dalvik cache, app cache and app data. most custom roms will automatically move apks to your sd-ext partition. there are various different scripts which move the other bits around. generally it is better to keep app data on internal (/data partition)
regardless of which rom you choose, use an app like 'diskusage' to browse all your partitions, so you can work out where and how all your space is being use.
to maximise space you also need to be s-off and correct hboot for the rom (again should be stated within each rom thread, or search within it)
ok so the first partition on the sdcard will become my sd-ext which will replace the /data partition on the internal storage.
I guess is hould try data2sd then?
with a class 10 it should not get that slow and i get loads of space on that partition.
thanks for your help.
also use links2d,very usefull.....
hi again,
as i see in a terminal emulator by typing "df -h"
my data is 150mb and has 15mb left, so i guess i better moe the whole partition to the sdcard as i'd have to move all the apps to the sdcard anyway sooner or later.
my /system has only 5mb of 250mb left. is that a problem?
soomon said:
hi again,
as i see in a terminal emulator by typing "df -h"
my data is 150mb and has 15mb left, so i guess i better moe the whole partition to the sdcard as i'd have to move all the apps to the sdcard anyway sooner or later.
my /system has only 5mb of 250mb left. is that a problem?
Click to expand...
Click to collapse
depends entirely what rom you're running if any, and what scripts it uses. basically you should be able to find some way to install many apps without running out of space (one of the main reasons for rooting in the first place ).
with your current setup, you could try something like link2sd to just move apps and dalvik to sd, see if you have enough space that way. you shouldnt have to manually 'move to sd', keeping them on 'internal' tricks them to sd-ext. (you can use something like 'diskusage' to check they're actually on the sd-ext)
the system partition is meant to be mostly full. free space on /system is wasted space.
you're still on stock hboot, which is why your data partition is so small.
if you install another rom, many of them have a smaller system size, so if you're s-off you can flash a different hboot to repartition your internal memory layout: your system size will reduce to roughly match your rom, and the saved space is converted into extra data space, see alpharev.nl for hboots.
e.g. if your rom system is 140MB, will fit nicely into cm7r2 hboot with 145MB system, and you get 287MB of data instead of 150MB. 287MB can be enough to store app data and dalvik cache if you don't have too many apps.
i refer you to these sets of guides for further reading, should explain a lot more, and better than i have...
thanks eddie,
i'm still s-on and stock hboot, but i use a custom rom: http://forum.xda-developers.com/showthread.php?t=1766550
i guess the problem is that LBE gues 4 and lookout together need over 22mb of space :/
i'll try link2sd then.
thanks!
hm.. when i try to install link2sd i get "insufficient storage available". that program is not even 1MB in size and i have 15mb of free space on the internal storage.. what can i do?
edit: i'll try to install it at home with an adb tool. maybe i have more luck with that.
follow instructions for a2sd with that rom (scroll down). this will move apps and dalvik to sd-ext automatically. or follow/search the thread for other methods, it's regularly discussed...
[not used link2sd, it should in theory do the same thing, but my advice would be to stick with the instructions as that's the recommended way if you really need/want to install link2sd...uninstall something else to make more space ]
ofc removing apps might help (althrough i only installed 2 or 3). but 15mb should be enough to install a 800kb software
gonna try to install some apps later after running a2sd.
thanks a lot man didnt see that information.
Hi, I installed rom cleaner and uninstalled it this morning.At that time I had ARHD 7 installed.
I think it has some how resized my sd-ext partition.
Since then I was not able to install any other rom. (eg AKOP,MIUI, Codefirex)
They all end up with a boot loop. AKOP was partially success but, it showed less internal storage capacity. Hence I could not install any apps.
However I manged to install ARHD again after several tries.
My questions are.
1. Whats the default internal storage size in HTC DHD.
2. Is this because of changing from android 2.3.5 to 4.1+
3. In past I've had no trouble changing roms between miui<->Akop<->viperX
you should search your queries here
regardless, never used rom cleaner, but no app or zip should resize your ext partition. what's important is how you made the partition, round here we recommend 4ext recovery, which is also available for your phone, or gparted.
the sd-ext size will remain at whatever size you pick.
depending on what rom you choose, some will require an sd-ext partition to work at all, others you may need to manually enable it. the rom normally needs some sort of script to be able to see and use the ext partition. details should be searchable in the respective rom threads.
you won't necessarily 'see' you total internal memory read 'internal + sd-ext', but as long as your sd-ext is mainly being used for apps it doesn't really matter. traditionally it's best to use your real internal memory for app data as it's faster than most sd cards.