I've read a lot about Ext2,3 and 4 partitions, Swap, Fat32 primaries, etc.
I don't understand any of it and I can't seem to find any explanations.
Right now I'm running Vipermod's ROM but I was going to flash Synergy until I saw that it seems to require partitions to be set up in some particular way?
Any help would be appreciated.
you can do fine with the way your card is set up now, no extra partitions required.
If you have a fast card, you can partition it to have what most call SD-EXT. my understanding is that its used to store applications automatically with A2SD ( apps to SD ) you can also move swap and dalvik-cache to the SD card, but only if its fast enough. Class 4 is recomended. but most say you shouldnt waste it on a class 10 since the evo doesnt use that much speed.
EXT 4 is supposed to the format for sd-ext or the dalvik. fat and fat 32 are for everything else, so windows can read the SD card.
ext 2 and 3 are the previous formats, but ext 4 is faster, but not always supported. ext 3 is the most common
Related
Ok, so I brought a new 16Gb Class 4 microSd card and I am going to partition it. I was wondering how much should I allocate to each partition type?
1. How does 14gb fat32, rest ext2 sound?
2. Should I leave any space for swap?
3. Also, out of Darktremor a2sd and Data to sd with dalvik-cache to ram, which one should I use?
4. In case if I upgrade my rom, do I have to re-enable them and copy the stuff again? Hows their compatibility with regard to upgrading?
5. Performance/drawbacks?
Thank You.
Also, does it make a difference which one is partitioned first?
Here: http://forum.xda-developers.com/showthread.php?t=1093317
It's mentioned that EXT2 is to be partitioned first but,
Here: http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning
Fat32 is partitioned first.
make Fat32 first if you want sd card to be recognized by Windows... if ext2 will be first, you cant access second partition on the SD card...
What about Swap?
Guys I made the partitions as said but the phone says damaged sd card. But if I format by phone, it runs ok. Any idea?
Clear your doubts guys!!!
Ok, so here's the deal, in a very longwinded way that should hopefully explain everything and answer ALL questions.
You have an SD card in your phone and, a bit like normal PC Hard Drives, you can "partition" them (split them into two or more sections of different filesystems). Normally, your SD card is just one big FAT32 partition, which is fine for storing your pics, messages, emails, etc.
Now, other then your Phone's SD card, your phone will have its own internal flash memory (or "NAND") storage. Tradditionally with Android, you could only install applications to this NAND storage, you cannot install them onto your SD card. So if you have an empty 32GB SD card, but only 5Mb of internal phone storage, you still wont be able to install many apps, if any at all.
This was done to protect the apps from things like piracy - it's not easy to access the location where apps are installed on your phone's internal storage (normally impossible without root), so you can't for example buy an app, copy it, refund it, then install it again.
Still, this is no good for those of us who like to install lots and lots of apps, legitimately, as we run out of internal storage very quickly.
So Google came up with a way to install apps to the SD card. A folder is created called something like .android_secure and this stores (I believe) encrypted versions of applications, but there's a few catches:
1) Apps aren't automatically stored here, you have to manually "move" them
2) Not all apps are capable of being moved, in fact most apps aren't, the developer needs to update their app and allow it. Some apps aren't and wont be updated and some developers may not want to allow it for whatever reason.
3) Not all app data is moved, most of it is but some data is left on your phone so many people still run out of internal storage quickly.
4) You can force ALL apps to be moved to this area by default, but it breaks incompatible ones - such as Widgets, which are unable to load due to the SD card not being "prepared".
So that's Froyo's version. Before Froyo existed, some very clever people came up with a thing called "Apps2SD". Remember I said that your SD card normally is one big FAT32 partition? Well, Apps2SD works by having your SD card patitioned into TWO filesystems. A normal FAT32 partition for your usual stuff and a secondary "EXT" partition. EXT is just a filesystem, like FAT32 or NTFS, but it's the filesystem used by Android internally. The SD card is normally FAT32 because it's a "universal" filesystem, that just about any machine will be able to read, whereas EXT filesystems are generally Linux only, but I digress.
EXT has several different versions. The most common one you'll see is ext3. The main difference between ext2 and ext3 is "journaling", which is just a fancy way of saying that should an operation (such as copying, writing or reading) be interrupted unexpectedly (say, by you turning your phone off), then no data should be lost or corrupted. You know how when you turn your phone on, it says "preparing SD card"? It takes a few minutes, but what it's actually doing is checking that the FAT32 partition hasn't been damaged, because FAT does NOT have journaling. If you used a computer back in the Windows 98 days, you may remember that lovely blue "Scandisk" screen that had to run every time you didn't shut your computer down correctly - that's the same thing. But then Windows 2000/XP came along with NTFS, which also has journaling, meaning you had less chance of loosing data. But I digress once more.
So you have your SD card partitioned into EXT and FAT32. Generally it doesn't matter if it's ext3 or ext4, but you don't get any real advantage with ext4 over ext3 in this instance. Apps2SD then runs a special script on your phone which "symbolically links" the folder from your phone's internal storage where your apps are normally stored, to the ext partition on your SD card. A symbolic link is a bit like a shortcut for folders, except it's transparent to the OS: In other words, Android doesn't know that when it's installing it's apps to the internal phone storage, it's actually being stored on the SD card. This effectively boosts your internal phone memory from the previous 5mb that you had in my example above, up to whatever size you made the ext partition on your SD card (often 512Mb or 1Gb, but it depends on how many apps you install).
Plus, because it's "journaled", it doesn't need to be "prepared", meaning it's ready to go as soon as the phone starts - so your widgets and apps work immediately (unlike "forced" Froyo Apps2SD, where widgets disappear).
The catch with Apps2SD is that whatever space the ext partition takes up is taken away from the SD card. So if you have a 4Gb card (with something like 3.5Gb of actual storage) and you make a 512Mb ext partition, your SD card will "shrink" to 3Gb. The space isn't actually lost, it's just being used by the ext partition. If you reformat your card, you'll get it back.
Finally, there's a difference between "Apps2SD" and "Apps2SD+". Remember I said that your apps are stored on a special folder inside your Phone's NAND storage? Well, that was a bit of a lie. It's actually stored in TWO places. There's a second area which is called the Davlik Cache. You don't really need to worry about what this is for (Hint: IT's to do with the Java runetime your phone uses to run apps), all you need to know is that apps use it to store data, which also eats up internal phone memory. Apps2SD+ moves davlik cache to the ext partition on your SD card as well, freeing up even more space. Some people believe that this may come at the cost of performance, as the internal NAND memory should be faster than your SD card (Which is why you also get people arguing over which "class" SD card is better for Apps2SD - the logic being that a faster SD card means less impact from this move), but the truth of the matter is that your applications will be running from your Phone's RAM anyway, so performance isn't really impacted at all. Since most apps are only a few hundred Kb's in size, or a couple of MB at the most, it's a non-issue.
Finally, any recent version of Apps2SD/Apps2SD+ should work with an SD card that is or isn't formatted with an ext partition. It'll check for this partition when your phone first boots and if it's not there, just use internal phone storage.
Having an ext partition WITHOUT Apps2SD+ shouldn't cause any issues, either, so you can format your SD card whenever you're ready.
So in summary:
Apps2SD "fakes" your phone's internal memory and puts it all on a hidden section of your SD card.
Apps2SD+ pushes even more content to the SD card, freeing up even more space on the phone itself.
"Froyo" Apps2SD has various limitations that "old" apps2SD does not, but is much easier to handle as it doesn't involve any kind of "partitioning".
IF U LIKE HIT THANKS​
Good idea, mate
Hi,
I recently bought a Sandisk 32GB Class 4 Micro SD card for my ST15i on ICS. I'm planning to move/link non system-related apps to it and store all my videos, music and pics into it. I've come across several threads regarding the issue at hand and this raised several questions:
1.) Is it advisable to partition it? If so, how and what would be the best method?
2.) How should I divide the space and what format should I use (FAT32, ext, etc)? Any rule I should follow?
3.) Lastly, which is better: link or to move apps using Link2SD or App2SD?
Thanks in advance.
1-yes, it's okay.
Download mini tool partition - Home edition
2- Fat for 2GB
Fat32 for 4GB or Above-----u should use Fat 32
if u partition the SD card ext size must be
128mb
256mb
512mb
1024mb ---don't use than 1024mb
3- I think link2sd is better, but app2sd also good.
What he ^ said. But to make a few adds,
You format the whole sd card as fat 32, and set a high cluster size value. Then create ext partition which can be made in fat32, ext2 or ext3 (ext3 is said to be best)
You can also partition the sd card from cwn recovery (remember it will wipe all data on card).
Linking is better because it moves a larger number of info onto the sd card, i use link2sd which is very simple and efficient. Nonetheless when linking most backup apps except titanium will not be able to follow the simlink to the apk (i think mbackup also just solved this issue but i'm not sure), but they will backup the app data.
Also be sure to tweak your sd card speed in case you havent already done that. A 1024 read ahed value should be the best option for your class
bandarigoda123 said:
1-yes, it's okay.
Download mini tool partition - Home edition
2- Fat for 2GB
Fat32 for 4GB or Above-----u should use Fat 32
if u partition the SD card ext size must be
128mb
256mb
512mb
1024mb ---don't use than 1024mb
3- I think link2sd is better, but app2sd also good.
Click to expand...
Click to collapse
Rudjgaard said:
What he ^ said. But to make a few adds,
You format the whole sd card as fat 32, and set a high cluster size value. Then create ext partition which can be made in fat32, ext2 or ext3 (ext3 is said to be best)
You can also partition the sd card from cwn recovery (remember it will wipe all data on card).
Linking is better because it moves a larger number of info onto the sd card, i use link2sd which is very simple and efficient. Nonetheless when linking most backup apps except titanium will not be able to follow the simlink to the apk (i think mbackup also just solved this issue but i'm not sure), but they will backup the app data.
Also be sure to tweak your sd card speed in case you havent already done that. A 1024 read ahed value should be the best option for your class
Click to expand...
Click to collapse
Thanks for the input, guys. I'm getting a clearer picture on what I should do with my new external storage. Now, let me ask a few more questions:
a.) Any particular reason why I should use ext3? Shouldn't the partition be both FAT32's?
b.) If I do use ext3, what would be the reason? Any advantage over FAT32? Also, is ext4 better?
b.) What should be the ratio when I partition my card? Ex. 50:50, 75:25, etc.
Again, thanks. I'll be doing my own research on the topic while I'm away.
1- u can use fat32 too. But ext 2,3,4 are better. If the rom support u can use ext 3 or 4..
2- ext3 is better than ext2 (correct me if i wrong)..yeah use ext4
3- for ext - 1024mb is enough
for ur swap 128
sd card should be fat32
---------- Post added at 09:37 AM ---------- Previous post was at 09:35 AM ----------
As above guy said, use cwm
hmmm...the safest format when you want to partitions your SD card is FAT/FAT32....EXT2/EXT3/EXT4 is good but depend on your kernel...you your using custom kernel then those format wont be any problem to your phone....
here is the best way to partition your 32Gb SD card....
for your main storage/primary = FAT32
for your 2nd partition/primary = EXT2/EXT3/EXT4
for linux swap = you dont need this partitions so its an option....
Size for your main storage = the remaining size after you have partition it
Size for your 2nd partition = 1024mb (do not go beyond this size)
Size for Swap (option) = 100mb....
Pusak Gaoq said:
hmmm...the safest format when you want to partitions your SD card is FAT/FAT32....EXT2/EXT3/EXT4 is good but depend on your kernel...you your using custom kernel then those format wont be any problem to your phone....
here is the best way to partition your 32Gb SD card....
for your main storage/primary = FAT32
for your 2nd partition/primary = EXT2/EXT3/EXT4
for linux swap = you dont need this partitions so its an option....
Size for your main storage = the remaining size after you have partition it
Size for your 2nd partition = 1024mb (do not go beyond this size)
Size for Swap (option) = 100mb....
Click to expand...
Click to collapse
Yeah,
I've went ahead and formatted my SD card into one FAT32 and one ext3 partition (still thinking about ext3, though). I've linked my apps to the ext3 partition. I've managed to free up about 100mb+ in internal storage space. Time to clean up my system ROM, let's see how much free space I can get.
Thanks to Pusak Gaoq, bandarigoda123 and Rudjgaard. You've all been great.
Haha, no problem bro.
hi guys,
I partitioned sd card ext with 1GB with FAT32 using mini partion tool
when boot ON the Phone & using with LINK2SD Main sd card & ext sd card showing the same size of 1GB ....
is the problem with ROM ??
I tried with another sd card but the issue is same
i'm using stock rom & 16 GB Sandisk C10 sd card
Pls help me......
Link2SD
The XPERIA X10i running GB 2.3 is a bit problematic with partitions.
The OS only mounts the first partition it finds and that's normally the second partition. Doh!!
The following patch may be of some help to you
SE2.3.3-link2sd-patch.zip
It is assumed you have formatted both partitions as primary.
Everybody should use Link2SD if they have an XPERIA X10, just because most quality class6/class10 cards have better read/write speed than internal flash and with a 1-2GB sdext2 partition more space too.
Considerations
I'd format the second partition as ext3 and 2GB if Link2SD is to be used, especially if a gamer.
I would only use a class6/class10 'quality' 32GB microSD card or greater.
Copy the contents of the /data/sdext2 partition to a NAS/external server
(1) I'd format the partition to be used with Link2SD as ext3 ( I've found on my builds I can't use ext4, but would, if I could ), just because it'll give better performance. In a gaming environment 1GB can be used up pretty quickly if libraries and data are linked too.
(2) The cost of quality class6/class10 microSD cards has really dropped in price now that extreme and extreme pro cards (50MB+ write) are all the rage. It's just a pain having to rebuild a working Link2SD environment onto a larger card at a later date, when a lesser card, no longer meets needs.
But given I'm using a 64GB card, I would say that.
(3) If you copy the contents of the second partition to a linux system /folder it makes a great recovery, as you only have to restore the Link2SD second partition and you get all your apps back, data and all. I copy my /data/sdext2 partition onto my NAS every now and then and it has saved my bacon a few times when microSD/SD cards have gone belly up.
Read somewhere that the Moto E actually supports 64GB (and even 128GB) MicroSD cards BUT only when they're formatted to FAT32, 'cause the device also prompts the user to do it when inserted. As we know in order to use Link2SD we need to format the card with EXT partitions and stuff like that, that should render the card uncompatible, or am I wrong?
Yeah, 64GB sdcard is working smoothly.
But I think you mixed something up. For Link2SD you have to create a 2nd partition on the SDCard. And this 2nd partition needs to be EXT formatted, while the main partition stays FAT32.
I recommend to not more thank 1,4 GB for the 2nd partition as Link2SD only moves apk and dex-files which isn't really that much.
Now I got it.
Is there any other way, with any other app, that can actually move the entire app from the internal memory to the SD Card, or at least move a significantly part of it in order to save some internal space? I thought Link2SD was able to do it, but you said it's not so useful since it only moves dex and apk files...