Hi!
I'm using DeFrost 1.8 and I think that my confusion will be same on any other FroYo ROM.
I know that DeFrost has Apps2SD buildin and cause it's a FroYo ROM, already have the FroYo-style Apps2SD.
I must confess that i don't care where my apps are installed. I just supose that are stored on SD card using old-Apps2SD method.
Now, I've installed App2SD from Market and show some apps that are on internal memory and some on SD card, but there are lot more apps that I have installed on my phone that don't show up on this app.
Now, I'm very confused with this.
When I install a new app from Market, in what location is installed ? Internal, SD card using App2SD-old or App2SD-FroYo ?
How can I select the default location for new installations ?
I have SpareParts from LeoFroyo and App2sd location is on 'Default'. This means internal memory or old-style App2SD or what ?
If my ROM has buildin old-style App2SD, I can suppose that 'default' means this method. Or not ?
Is your SD card setup for old-A2SD with an EXT3 partition? If not, then they'll either go on the internal memory or the SD card using FroYo-A2SD (although not all apps are installed to the SD card as the creator may not have updated them yet)
Another question:
I actually haven't any Ext3 partition and may applications already installed, some on internal memory and some with the froyo-a2sd on the sd card.
I would like to create an Ext3 partition. I was thinking about the following steps:
- backup the fat32 content of the sd
- create a 1Gb ext3 partition
- restore the content of the Fat32 partition to SD
The problem is:
I will probably lose all the applications installed on the internal memory
Is it right? How can I solve this? Do I have to move everything to the new partition?
Which directories do I have to copy on Ext3?
Is sufficient to backup everything with Titanium and the restore once the Ext3 has been created?
Another problem is:
I started the system with an Ext3 partition and I couldn't access any application I installed before. Is there a way to recover those applications?
Once I erased the Ext3 partition (without installing anything on it) the phone started a boot loop.
What if I create the Ext3 before installing the new rom?
Thank you in advance.
Regards,
Daemon
EddyOS said:
Is your SD card setup for old-A2SD with an EXT3 partition? If not, then they'll either go on the internal memory or the SD card using FroYo-A2SD (although not all apps are installed to the SD card as the creator may not have updated them yet)
Click to expand...
Click to collapse
Yes, my SD card have an ext3 partition. So, the apps that don't appear at the App2SD applicaction, it's supposed that are on the ext3 partition ?
Then, why I have some apps in internal memory and other on FroYo-app2sd and the rest on ext3 part ?
I can't understand this.
Hey guys
Im on holiday now so cannot really check myself the differences, but just wanted some quick info on the A2SD, with the official froyo i was hoping everybody will start using it, but somehow people still using the old method, whys that?
thanks
Froyo A2SD is completely reliant on app developers. If the devs doesn't allow it in their app then it can't be moved to the SD card. This is really only a problem because Froyo is still new.
Old A2SD you can dump everything on the SD
However, I'd be interested in seeing if there is a way to force an app onto the nand using A2SD+. Would work better for things like widgets, home replacements etc, as they'd run quicker for people with slow sd cards.
Probably because the FroYo one sucks !
Why ? Well, mostly because devs have to rewrite their apps so they can use FroYo's app2sd function...
With the "old-fashioned" a2sd, there is no need to do anything, just sit and enjoy the free space
APP2SD allows you to move certain apps to your SD card and run them from there BUT as these are placed on the normal root of the SD when you mount the SD, via USB for example, you loose access to these apps until you remount SD. This means you cant install widgets to the SD and such like.
APP2SD+ on the other hand uses an ext3 partition (or ext4 on newer versions) which then installs all apps & widgets to that partition and when the SD is mounted you dont lose any apps or widgets as is located in a seperate partition.
Hope that helps.
Sent from my HTC Desire using XDA App
Sent from my HTC Desire using XDA App
wow! thats quick thanks for you input guys think you explained everything i wanted to know really
Id want to use the offical a2sd as i think using ext3 partitioned sd card have already slightly damaged the card cuz it keeps giving me errors everytime i connect it to a pc
mrwookie6379 said:
APP2SD allows you to move certain apps to your SD card and run them from there BUT as these are placed on the normal root of the SD when you mount the SD, via USB for example, you loose access to these apps until you remount SD. This means you cant install widgets to the SD and such like.
APP2SD+ on the other hand uses an ext3 partition (or ext4 on newer versions) which then installs all apps & widgets to that partition and when the SD is mounted you dont lose any apps or widgets as is located in a seperate partition.
Hope that helps.
Click to expand...
Click to collapse
So let me understand the names:
APPS2SD = Froyo Original (comes with official Froyo release)
APPS2SD+ = Hacked version which has been out since FRF50 leak?
EDIT: But if APPS2SD+ is so much better (keeps apps on ext3 partition), why to people keep using the original APPS2SD on their ROMs?
Check this explaination. Quoted from neoKushan from yesterdays thread.
neoKushan said:
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".
Click to expand...
Click to collapse
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Vice83 said:
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Click to expand...
Click to collapse
You can do that thru recovery-windows.bat by going thru recovery mode by volume down + power, go to recovery then when the red exclamation point appears just run the recovery-windows.bat by double clicking on it. You can get these files from r5-desire-root-alt from the rooting process files (search the forums for this if you don't have it). But be cautious cause when you partition your sd card, all your files will be wiped so make sure to backup everything you need. Cheers!
Edit:
Actually this summary about the ap2sd and ap2sd+ and froyo ap2sd should be stickyed for everyone, so it would not be ask over and over again.
Couple of extra ways to partition:
1) Flash AmonRA's Recovery to your phone (I used Unrevoked to do it)
2) Use GParted on a Linux LiveCD (e.g Slax) to partition your card exactly how you want it
Vice83 said:
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Click to expand...
Click to collapse
ROM Manager is probably the easiest way to do it, but I was stuck with EXACTLY the same problem when I rooted. I chose to flash AMON Ra recovery (don't have the link, but you can google it up), and then used that to create a 1024MB ext partition. Then used AMON Ra again to convert the ext partition to ext3. Hope that helps.
However, one question I have regarding neoKushan's explanation is that if I did create a 1024MB ext3 partition, then the same capacity should be visible in the phone's internal memory. However, after I rooted and restored my apps, I could only see about 100+ MB of free internal memory. Can anyone help me with this please? Am using the Opendesire Official Froyo 1.0c ROM that has A2SD built in
deepdevil said:
ROM Manager is probably the easiest way to do it, but I was stuck with EXACTLY the same problem when I rooted. I chose to flash AMON Ra recovery (don't have the link, but you can google it up), and then used that to create a 1024MB ext partition. Then used AMON Ra again to convert the ext partition to ext3. Hope that helps.
However, one question I have regarding neoKushan's explanation is that if I did create a 1024MB ext3 partition, then the same capacity should be visible in the phone's internal memory. However, after I rooted and restored my apps, I could only see about 100+ MB of free internal memory. Can anyone help me with this please? Am using the Opendesire Official Froyo 1.0c ROM that has A2SD built in
Click to expand...
Click to collapse
I'm not sure about what exact capacity for the internal memory after partitioning to ext3 but when I was on Opendesire before for the eclair 2.1 after I'm done flashing the rom and setting up the whole ap2sd+ my internal memory was 410mb. I used:
swap=0
ext=1024
fat32 is for the rest of the card
Then after upgrading to froyo rooted ROM, I'm only getting 140mb tops. I dunno... I'm too lazy now to get into it right now... maybe soon I'll play around with it again so I can get back my 410mb internal space with the ap2sd+
Stewge said:
Froyo A2SD is completely reliant on app developers. If the devs doesn't allow it in their app then it can't be moved to the SD card. This is really only a problem because Froyo is still new.
Click to expand...
Click to collapse
Not 100% true, because you can change the default install location to SD card (via ADB if stock, and an app if rooted) and then you can have the vast majority of your apps on SD card even if they've not been updated for Froyo.
Regards,
Dave
I always thought the main negative with A2SD+ was that the cache was moved to the sdcard, which of course would wear out the sdcard (slightly) quicker.
Vice83 said:
So let me understand the names:
APPS2SD = Froyo Original (comes with official Froyo release)
APPS2SD+ = Hacked version which has been out since FRF50 leak?
EDIT: But if APPS2SD+ is so much better (keeps apps on ext3 partition), why to people keep using the original APPS2SD on their ROMs?
Click to expand...
Click to collapse
Not exactly!
Prior to Froyo, there were principally two versions of Apps2SD:
1. APPS2SD (or A2SD )
2. APPS2SD+ (or A2SD+)
The first would move your apps to the EXT partition, and the second would move your apps and the Dalvik cache to the EXT partition (see here for an explanation of the Dalvik cache).
Now we have Froyo, we have "native", or "Froyo" apps2sd as well, which does much the same as (1) above except that there is no EXT partition and the apps are on the FAT32 partition of your SD card.
Regards,
Dave
sparksalot said:
I always thought the main negative with A2SD+ was that the cache was moved to the sdcard, which of course would wear out the sdcard (slightly) quicker.
Click to expand...
Click to collapse
Dalvik cache is only actually updated when a new app is installed or and old app is updated, so whilst it will incur more writes to SD card, it probably isn't anywhere near as much as the apps write themselves to the FAT32 partition.
Regards,
Dave
Great summary, but can I format my 8 GB SD card as EXT3 and just forget about the FAT partition? I'm using Ubuntu on my laptop and my EXT4 /home partition is just fine for storing images, movies etc. I really don't get this ado about having an EXT and a FAT partition. Or am I wrong here?
quick question, if i move to another bigger sd card, can i copy my card and transfer it to the new one without losing the EXT, and the apps on it? would i need to make a image of the card? thanx for any advice.
make a backup of them first on your pc and copy them to the newly partitioned sdcard....ext to ext and fat to fat
So there is 3 versions?
1. Froyo A2sd = fat32 only = apps installed to sd
2. A2sd = fat32 + ext = apps installed to sd in ext partition
3. A2sd+ = fat32 + ext = apps installed and Dalvik cache moved to sd in ext partition
Is there any more variants? lol
Sent from my HTC Desire using XDA App
Hey, so I've rooted my phone, installed CWM. Now I'm kinda confused how to install Link2SD.
I've a 16 GB SD card with me. All I need to do is, boot into recovery and then partition the SD card?
Do I need to do anything else?
Also, What's that swap memory? (The option which comes after selecting the partition size) What should I choose in that part? I read somewhere that I should choose 32/64 MB only..
I'm using HTC Wildfire S A510e with the latest update having Gingerbread 2.3.5
Thanks
Well partition your SDcard and create two primary partitions. Format the second partion as ext4 and use tune2fs to disable journalling.
Install Link2SD configure it and select ext4 as the second partition. It will automatically mount it then.
I'm still trying to contact the developer to mount without barriers and atime to get better performance.
i used minitool partition wizard on my pc to do it, but i think you can through CWM as well. i originally tried making the 2nd partition FAT32, but my l2sd didnt recognize it, so i redone it in sdext2. on my wifes wildfire s i tried ext2 first, and ended up having to change it to FAT32. theoretically you should be able to use the partitioning on CWM and get l2sd to work, but if it doesnt detect your second partition then just try different formats if you can. minitool is a free program if you need it, and is available with a simple google search. there are also several other threads about l2sd all around xda and the net, so if you get stuck just search them up. once partitioned, go into l2sd and press the menu button and select more, then create mount scripts. this will get it running, and also will show if there are any issues with your partition.
Hey everyone. I'm going nuts trying to figure out how to use Link2SD. I partitioned my 32G SD card using Mini Partition Tool. I made a 1 gig partition. I've tried FAT32 and EXT2. After partitioning, i rebooted and tried Link2SD. I keep getting the error "Mount script cannot be created. [1] Segmentation fault mount ..."
Is there any solution for the xperia play? I manually moved my apps but still ran out of space keeping system tools like Titanium Backup on the internal. Maybe I should make them System Apps?
I use the following on mine setup:
64gb Card (Fat32 - Primary)
5GB for EXT4 partition (Make sure when you partition it to set it as primary.)
300mb Swap Partition
I had an issue with Link2SD too ad it was because I was not setting the EXT partition as primary, oncei formatted it again as primary Link2SD had not issue with it. Try that.
ozzmanj1 said:
I use the following on mine setup:
64gb Card (Fat32 - Primary)
5GB for EXT4 partition (Make sure when you partition it to set it as primary.)
300mb Swap Partition
I had an issue with Link2SD too ad it was because I was not setting the EXT partition as primary, oncei formatted it again as primary Link2SD had not issue with it. Try that.
Click to expand...
Click to collapse
Hey thanks for the reply. Just tried what you said. My FAT32, ext4, and Swap are all Primary and sill no go. I get the same error (segmentation fault mount -t ext4...). When Link2SD opens I've tried selecting all the options for the parition type too and none of them work.
Anything else I can try? Does the order of the partitions make any difference? Right now I am Primary, ext4, Swap.
echardcore said:
Hey thanks for the reply. Just tried what you said. My FAT32, ext4, and Swap are all Primary and sill no go. I get the same error. When Link2SD opens I've tried selecting all the options for the parition type too and none of them work.
Anything else I can try? Does the order of the partitions make any difference? Right now I am Primary, ext4, Swap.
Click to expand...
Click to collapse
Ah.... okay, I should have clarified this, only the fat32 and EXT partition are set to Primary. Swap Partition is set to logical, setting all three to primary causes issues.
Reformat only the swap and format to logical. Then in Link2SD force it to reinstall the scripting and see if that fixes it.
ozzmanj1 said:
Ah.... okay, I should have clarified this, only the fat32 and EXT partition are set to Primary. Swap Partition is set to logical, setting all three to primary causes issues.
Reformat only the swap and format to logical. Then in Link2SD force it to reinstall the scripting and see if that fixes it.
Click to expand...
Click to collapse
Okay then. New problem. Now Link2SD says "No SD card present" and android doesn't mount it either.
This is killing me slowly.
I'll try to reformat the whole card via a reader...
Didnt work. SD card still not recognized.
echardcore said:
Okay then. New problem. Now Link2SD says "No SD card present" and android doesn't mount it either.
This is killing me slowly.
I'll try to reformat the whole card via a reader...
Didnt work. SD card still not recognized.
Click to expand...
Click to collapse
OK. If your willing, lets start fresh. I am guessing you have your SDcard files backed up. Using Minitool partition delete all partitions and format as FAT32. Then create another partition of your size and format it as EXT (I prefer 4, EXT4) and set it to EXT(2,3,4,etc) and Primary. Then just for kicks, do not make a swap partition. I read that its not necessary, however I always do it..... well necessary only if you use a swap manager. So after the fat32 and ext partitions are made and minitool has created them. Take out the card, put it back into your pc and see if windows sees the fat32 partition. If good place it back into your phone and see if it upon bootup sees your sdcard.
Just in case as a reference here is the tutorial from the developer of Link2SD on how to set it up.
http://www.link2sd.info/description
ozzmanj1 said:
OK. If your willing, lets start fresh. I am guessing you have your SDcard files backed up. Using Minitool partition delete all partitions and format as FAT32. Then create another partition of your size and format it as EXT (I prefer 4, EXT4) and set it to EXT(2,3,4,etc) and Primary. Then just for kicks, do not make a swap partition. I read that its not necessary, however I always do it..... well necessary only if you use a swap manager. So after the fat32 and ext partitions are made and minitool has created them. Take out the card, put it back into your pc and see if windows sees the fat32 partition. If good place it back into your phone and see if it upon bootup sees your sdcard.
Just in case as a reference here is the tutorial from the developer of Link2SD on how to set it up.
http://www.link2sd.info/description
Click to expand...
Click to collapse
PC sees the FAT32. Phone sees the card now. Link2SD shows the partition but cant mount it and create the script for it. Also tried as ext2. Thanks for your help. I am going to try to update the ROM.
After updating the ROM to 2.4.0 and waiting 10 mins and rebooting as usual. was able to successfully link the partition! Thanks for your help!
No problem. Glad you got it working.
Sent from my R800at using xda premium
Got all my apps installed! Woot! Also, something must have been messed up with my previous flash.. I wasn't able to restore apps the newer way from titanium backup. I had to do it the old way one by one.
phone is going to make a great gaming alternative to my SGSII.
Seems I've made a bit of a booboo somewhere. I was recreating the ext3 partition on my sd card. I deleted the existing ext4 partition and resized the fat32 partition to take up the slack left behind. When I checked the partitions afterwards, everything was fine and all my files were present and correct in my fat32 partition. I booted into recovery, formatted all partitions except my fat32 and went to install my rom again. Except I forgot to put it on the sd card. So I copied it back on to my sd card, stuck the card back in the phone, booted into recovery and promptly got a message that pb99diag.zip is missing. I've checked the entire fat32 partition and there's no sign of it. I tried renaming "OTA_Bravo_Froyo_HTC_WWE_2.29.405.5-2.29.405.2_releasedauhl6jhok5cmdm6.zip" to "pb99diag.zip" but it doesn't seem to like it.
How can I get back into recovery without the pb99diag.zip?
found a similar thread: http://www.modaco.com/topic/348778-hboot-looking-for-pb99diagzip-why/
It's because you resized it, I believe it might eventually stop searching for the file and go into recovery, but it's not ideal.
I'd try backing up sd again, and completely reformatting and partitioning again, but using up to date gparted instead.
- Also, why did you need to change from ext4 to ext3? ext4 is marginally faster, most ROMs support ext4.
- And are you trying to install an RUU? In which case you don't need an ext partition at all?
Sorry just trying to understand your overall aim...
- Also, why did you need to change from ext4 to ext3? ext4 is marginally faster, most ROMs support ext4.
- And are you trying to install an RUU? In which case you don't need an ext partition at all?
Click to expand...
Click to collapse
I had 2 2gb ext partitions, ext3, ext4. I didn't need 2 so deleted 1 and just created a single ext3 partition. I wanted to go back to my PA jb 4.2.2 which was working fine until I used link2sd to free up some more system space but because its sh1t it just completely ballsed up my entire install. I installed an RU and this left me rooted with s-off and it was plain sailing from there to reinstall recovery and flash my custom rom again. I'm using a different sd card now (for testing purposes) but I'm still getting the pb99 errors. As you say, it will eventually allow me into recovery and I can continue what I'm doing but it takes ages and I've never had this issue before.
I'm using MiniTool Partition Wizard Professional to create my partitions.
mickrick said:
I'm using MiniTool Partition Wizard Professional to create my partitions.
Click to expand...
Click to collapse
There's your main problem, do not use MiniTool Partition Wizard. More often than not it creates improperly aligned partitions. Link2SD won't have helped either, it's a messy method and you don't need it with 4.2.2 ROMs, follow the instructions to activate A2SD via terminal commands.
I would backup the FAT32 partition of your sd card, and reformat and repartition the whole thing using gparted. Use this video guide to help
Basically you want to remove all partitions and create one FAT32 partition, and max 2GB ext4 partition. You might as well keep it ext4 over ext3, it should be marginally faster.
Then full wipe and reflash ROM, don't use link2SD.
You should also look to s-off, search for guides, much more powerful, and useful if things go wrong.