Abstract: There are already guides Iink2sd but I found one that would explain what and how well (especially for situations where often changing environment in the terminal (nell'ol is common: P)) ... this is not to criticize it will detract from the other guides, but take it as a surplus and maybe a riaggiornata ...
NB the operation is not lost at all risky, there is no risk damage hardware parts (well unless it fits the sd in microwave instead of in the PC eheh) cmq the only risk they are encountered are deletion data maybe when not is expected ...
so I recommend: In addition to the backups you make with programs for the purpose, fateanche a manual backup only your important data (photos, music documents etc...)
Link2sd a2sd but what are they?
Well since he was born Android has always been the problem of limited space in memoriainterna (which is what is always a moment) Well some froyo app from Android 2.2 (and now as orasempre more but not all) have the ability to move part of the data in sd gaining space ...
But this is a temporary remedy because as said it does not work for all apps (vedifacebook, see tapatalk) and even more if you can move most of them stay in internal memory (see shazam only 4 to 8 megabytes are moved) In addition, the sd (to be supported by Windows) has a fat32 file system which is less performance native linux file system (on which Android is based) which is the extEcco that spring scripts or programs which allow you to use partition for ext as a support app and let you move all the apps you want and totally
Why not Link2s A2sd (opinion)
A2sd is comfortable, once it is installed correctly (and many of his rom already fitted) does everything he is no longer needed the user's hand, but this can also be a point against, a2sd running fact does not automatically decide which applications move and what not, in fact some apps (music player and other keyboard messages) have more or less need to reside in memory (in the common case where the SD is low, or mainstream it will be slower when reading / writing with respect to internal memory).
Then if you use a2sd is as if you had more internal memory, whatever you do you load the app will be moved to SD, but if you have other 80/100/120 MB free internal memory or why not use them?
NB Link2sd does not move the app to sd (in saying that this system is the other way as it does a2sd if I remember correctly) but creates a link to this built-in memory that points to quell'app (connection of small size) that allows to make one believe that they still reside in memory favoring some aspects (such as Rom cm7 based on the widget must be on internal memory to run, but connected with link2sd work great (with a2sd NO)) said this:
Prerequisites
Legend * = recommended but not necessary
- Root: Even if you create the root partition need not, use the program correctly (and I mean properly use the COLLEAGUE and NOT MOVE) requires such permission, so before you start all is well run the root.
- * Recovery: Although not required to perform the steps, I highly recommend you install it (if possible) because they create the second partition with limited recovery problems
- Card Reader * PC: If you have the recovery in the cell is not necessary if you do not have one you can use the mass storage of the cell, but remove the card from the terminal ensures a more successful and reduces the problems
- A bit (maybe + P) with patience: Perform this guide is neither simple nor quick, arm yourself with good patience and dont miss any point of the guide
Phase 0 (prepare the terminal to support EXT)
In order to use (or rather because Android to see them) EXT partitions must have installed a kernel with support for this file system (if you have a custom rom 90/100 will also be your custom kernel, and so probably with support for ext partitions ( in the right section to ask questions)) ... If not, or at least your terminal has the stock kernel you must install a custom kernel (WITH SUPPORT PARTITIONS EXT), to do this:
- You have installed ClockworkMod!!!
- Obtain a custom kernel and save it in sd
- Enter in recovery
- Wipe cache partition
- Advanced -> Wipe Dalvik Cache
- Install zip from sd card
- Select the file. Zip kernel
- After the restart flash
NB Do not ask me how or where procurere cwm install a custom kernel, look or ask in the sections of your terminal ... I do not know all the sections of all the terminals: P
NO EXT? DO NOT WORRY
In the event that your terminal does not want to know about custom kernel and / or does not support ext partitions, but you do not maintain the momentum it is possible to use a second fat partition instead of a partition ext (for CONNECT apps as you would with ext and NOT move to SD would like Android natively), you are obliged to do this to partition the sd from the PC (phase 1 method 2) and then when Iink2sd will ask you to create the script choose the last option (fat) This I say this being toric, reading and seeing the possibilities of Iink2sd these options, but I have not ever experienced it ...
NB a user happened to create 2 partitions a fat 15 and a 1 GB and 2 ° link2sd saw as the partition 15, so take care to create for the first (and first) + one large, the primary, then secondary
I hear you ask me but what changes? At this point I can use the native method ... Well in part it is but I remember that the native method does not allow you to move all apps, and in any case you can not fully move the app (eg Shazam is approx. 8mb, Android allows you to displace only 4 ... Iink2sd approx. 7.90: P)
And then you ask, so why should I beat to change your kernel to use ext partition when I can use a second in fat? Android comes to linux, the file system of choice for linux is the ext, the fat supports it but the performance of SD are lower (ie faster than FAT EXT)
Phase 1 (prepare well for the sd)
NB If your Custom Rom relies on an ext4 partition out of the box (due to use A2sd) skip this step, the SD is already OK
Method 1 (Partitioning with ClockworkMod)
NB THIS METHOD FORMAT THE PARTITION EVEN FULLY SD FAT (WITH ALL YOUR DATA)
- Make sure you install ClockworkMod (if not the next step will restore the phone to factory!!)
- Enter in recovery (Home Key, Key you down Power button. At the same time)
- Advanced -> Partition SD
- Ext size (to the space that you think should be space for our app connected insd (ext))
- Swap size (depends on the device, no need for this guide, then select any (or set to 0) or better under the guidance of your ROM
- Reboot
Method 2 (partitioning via PC)
- Remove the sd (smontandola or turning off the phone first) from the phone
- Insert (sd card slot or whatever) on your PC
- Total backup (not copy paste, but back up all files including hidden and system)
- Download a program to partition the disks (Linux: GParted, Windows: minitool partitionwizard (or more if you prefer)
- From the program partition the sd (ext2/ext3/ext4 (cwm uses Ext4 (at least the latest version!)); Remaining in Fat32 (win95 fat if you use linux))
- Restore your backups in the partition Fat32 (Windows will only see that (of course the original smallest where you started)
- Put the SD and start terminal
NB Applications of the system can not move it much less of fat on ext ... (Well something is let into the internal memory: P)
Step 2 (removing script A2sd)
NB In case the Romani preabilitato this script (in this case the SD will already be partitioned, and then will not have performed the step 1)
- Open the terminal emulator (if there is pre-installed download it from marketqui)
- Give the following commands: su -> nocache a2sd (move the cache back on memory internal applications (make sure you have at least 60 mb free!!!!!) If you have not enough space will be cleared to make way for the app user cache)
- Reboot the phone automatically
- Open a new terminal emulator
- Give the following commands -> a2sd NODATA -> remove as2sd
- Further automatic reboot
Phase 3 (installation and configuration Link2sd)
- Access to the market and scarikate Link2sd-Open Link2sd
- When asked to create the script (needed to be able to use its primary function) create it by indicating the type of ext partition you created (if you do not know what you used ext try with ext4, if on error try the 3 and so on (do not use ext partitions that are not used unless you have written the part in blue (of course this guide))
- Restart the phone (with notice of this same Iink2sd)
- Open Link2sd -> Settings -> Location of Installation -> Internal, (this to avoid that when you install an application that is automatically moved to the partition Fat32 (it would for many applications mb or if there is little internal memory free) do not want because we want to move on and not on the invoice, ext)
NB Although you set the correct installation position some nice heavy apps like games (see Cordy, Train Crysis ...) are developed to be installed ONLY on secondary storage (it's just a setting apk) here there is nothing to to be installed on fat32 (at least in part), so you have to manually bring them on internal memory before connecting.
In each case: DO NOT and I repeat DO NOT connect applications that have been moved to SD from Android (do not break anything but it is a task incasinaria and unnecessary) (link2sd to see the message "The Sheda SD"), or leave them (memory full ext?!?) or the first move of internal memory and then connected (see below to find out why)
Phase 4 (using Link2sd)
Method 1 (autocollegamento)
Useful to emulate a2sd (Please do not XD) or if you have already installed all the apps and the next will be important only secondary app is not essential for your everyday
- Open Link2sd -> Settings
- Check Auto Link (This link automatically for all new applications you are planning to install
- Settings autocollegamento
- Check all the items (or those who want it)
Method 2 (your decision)
- Open Link2sd
- Cap on interest
- Create Shortcut
- Select all the possible points (or ones you want)
NB plugged after the application will Create Shortcut and Move to SD (the first is the correct one, the second shift in the application as it would natively android fat (use only in the unlikely event that ended both internal memory and memory ext))
In case you want to bring the app to internal memory followed the same procedure but this time (of course) rather than create shortcut you plug "remove link" and select all entries
Step 5 (Titanium backup restore backup)
In case you have totally changed ROM or restored for some reason the same then you also did a wipe of the system (or reset to factory settings) but at the same time you have saved all your backups with titanium backup ...
The problem is that when you restore the backup to our dear friend Link2sd not come into play automatically (even if you have performed the phase 4 ... 1 method as it would a2sd)
then:
- Make sure that you complete the Phase 3 (otherwise we would go to the last point in space against depletion and subsequent installation of the app in the fat32 thing I do not want: P)
- Check free space on internal memory
- Restore a part of that application (in your opinion) can be in internal memory
- Perform Step 4 Method 2 for all newly installed app (or those who want to) freeing memory
- Perform this procedure from step 2 ("Check space ...") until completion of the restoration
NB Important Update 01/05/2012 Help!!
The latest versions of Titanium Backup, or / and maybe / probably Link2sd this is much more automatic / unavoidable, in fact if you backupped based application and when you restore all the necessary requirements (link2sd autocollegamento configured and enabled) this application in most cases will be linked automatically ...
NB I said in most cases, then restore cmq a little at a time and date reset with a shrug link2sd your app to check for proper connection.
Step 6 (rispostamento Dalvik Cache)
In the case of cwm have given the command "wipe Dalvik cache" (this is when you install a new kernel or something). O cm ² in the case where the Dalvik cache has been deleted
NB after it is cleared to restart it but it will be recreated in memory (so be careful if you do an operation like this make sure you have a 60 MB free internal memory otherwise you risk it being deleted the app and if you're unlucky (as has happened to me once) will clear your link2sd)
- Open Link2sd
- Other
- Connect arch Dalvik cache (this will move again Dalvik cache on your ext partition) (a bit like the command for the competing a2sd cachesd a2sd)
Superfluous but recommended: Clean with a little of everything on the menu commands that you will find more (such as cleaning the second partition, take away the remnants of the old Dalvik bad if this has been cleared, clean Dalvik, delete cache ...) in fact do the a little cleaning will not hurt
NB may happen that once made this your system see the app but not connected reisca open them, this is because the new kernel does not support partitions ext and then the system sees connections but can not get to the app ... Simply put again the kernel of the first, or ask and we'll help you
Step 7 (after ROM upgrade script recreation)
In the case to mount a ROM with frequent updates (as in the case of nightly cm7) Link2sd is faster to reconfigure to the competitor (which you should repeat all the steps to replace the script) ...
During the upgrade will delete all files that are not included in the rom (including our link2sd scripts created during installation) and then be recreated
NB first start after upgrade link2sd will give you an error (see alert of activation in the notification area) ... now all the applications that you had moved to be unattainable, but do not worry.
Method 1 (If you have received the alert notification activated)
- Plug the notification
- Will open Link2sd
- A window with an alert message with 3 buttons to choose from and choose "Rebuild Script On activation"
- Select the partition type
- Ok
- A message of success
- Restart (boot slow, normal, because it will rearrange a bit 'of things)
Method 2 (If you have deleted the notice or did not appear)
- Open Lin2sd
- A window with an alert message with 3 buttons to choose from and choose "Rebuild
- Script On activation "
- Continue as explained in method 1 after the same point
Method 3 (If no window appears with a message alert)
- Open Link2sd
- Other
- Rebuild Script On activation
- Select the partition type
- Continue as explained in method 1 after the same point
NB If the guide to update your ROM (not all require it) needs to do a wipe run Dalvik also Fase6.
NB If (when plugged Remake Script) rather than a success message will receive a Failure message read what is written ... if it says resource buisy simply means that at the time could not write at that point because we're already working something else, then wait a bit and try again, if it persists reboot and try again.
If the message is different, but an error cmq posted and we'll help you.
It can happen in fact to be corrupted ext partition, then will re-create ... Or the new version of the Roma has changed and this kernel does not support the ext partition and then just change the kernel etc ...
NB The second method for partitioning not've never tested since I always used to partition ext rom already during installation ...
[In fact, there is a remote possibility that the file system created for fat is not the same one that uses Android, and so this is not recognizing it will ask you to format the sd (I may be right backups) but if you format from your terminal Android will also repartitioned the entire sd in fat (losing the ext partition), then the right eye and scelete File System for the fat partition, and if that happens just said put it back again on the pc and reformatted the sd only the fat partition by trying another file system ( that it is always a factor)] ... Board cmq install cwm and follow method 1
I think everything is ... I hope I have done something to please ...
I remember as always that there is a button below Thanks, a message that says enjoy an excellent guide, but thanks in + x in the box following users have thanked ... even more pleasure : D
Related
Hi, I have been testing several NAND set-ups
-system to NAND and data to resized data,img
-system to resized system.img and data to resized data.img
-system to NAND and data to ext2
...
I am currently using NAND and data to ext2 partition, so all apps are installed there. After lots of reading I can not understand posts that are obsolete and posts that are not so I would appreciate if someone can explain me the basics and optimal setup for incubus superfroyo RLS14/15 roms:
I have now 4 partitions:
1) fat32,
2) 1,5G ext2 (app, app-private etc),
3) 1,5G ext2 (lost+found folder) and
4) 96M lynux-swap.
- How can I turn ext2 to ext3? do I need to do so? I have also read about ext4. Upgrading to ext3/ext4 applies to my 2) partition, to my 3) partition or to both? will I loose data stored? "there is no ext3/ext4 fs because there isn't the support on the compiled kernel. Ext3/ex4 are journal file system so are bad for limited writing device like nand or sd and thre is no good rease to use it" answered by l1qd1.
- How can I check if my lynux-swap is enabled and used by the rom?
- Do partitions 2) and 3) really need to be <1,5 G? why so?
- Can I take apk from apps folder in partition 2) in case I want to keep them for future fresh installs?
- What is lynux-swap optimal size? a 1,5G partition would be worse than 96 M? Why?
- Which tools are you using with incubus roms to manage installaion location and similar functionalities?
Another big mark I have is about deoxeding installed aps (not belonging to the ROM). Should I do it? why? how?
Pretty basic stuff I guess for experienced users & programmers, but I am new to lynux and android. Have read lots of things but it is difficult to learn by myself what would work with our Polaris and incubus ROMS and dzo/kk kernels,
Stick to ext2 man, you won't turn your old engine to 240mph on a Ford Model T.
You're not getting some major boost if the hardware dosn't use it, so I'd stick with ext2.
And you also want Super FroYo on your ext2 partition, yes? I'm here to help.
- How can I check if my lynux-swap is enabled and used by the rom?
adb shell
Code:
free
if on swap you have 0 it isn't enabled.
Code:
swapon /dev/device
to enable it or i suggest you tu use compcache.
- Do partitions 2) and 3) really need to be <1,5 G? No
- Can I take apk from apps folder in partition 2) in case I want to keep them for future fresh installs? Yes but not all apk support this
- What is lynux-swap optimal size? a 1,5G partition would be worse than 96 M? Why? Too Big = more sparse but it's a problem only for real disk so you can create a swap big as you want but it's unuseful (100 M is enaught)
i suggest you to switch to my kernels because are more updated and kk move to another device.
Yah l1q1d I love ur kernels. Eager for more !
l1q1d, I am testing your kernel as you advised me. I could apply the wifi patch without problems using your androiupdate18-09-10, as you told me some time ago they are both 2.6.25.
However I do not manage to turn linux-swap on: that's what I do: I install ubuntu, I use G-Parted to create partitions on the sd card. When I do so, the third partition is always shown as linux-swap in G-Parted but when I test adb shell -> parted -> print, it always shows as ext2. I can not dismount and can not swap on it.
The other way round, if I deleted all partitions with G-Parted and create the partitions with mkpartsfs or if I use mkfs to change the third partition from ext2 to linux-swap, then sometimes I can swap on it (directly on adb shell or with G-Parted) but when I unplug the device will tell me the card is empty and will not be able to mount it, access it from ubuntu or from the device. If I reboot then, the system will hang until I install both data and sysetm to nand. This happens no matter if I activate or not from the polaris or even if I switch on or off usb mode. The card at that point is useless. I guess the partition table or some other basic file is messed.
Could you please explain a little more how can I come with a 13.5G fat32 partition, a 2,4 ext2 partiions and a 0,1 lynux swap swapped on partition??
I really need to test this set up, since with the standard set-up (system to nand, fat32 for files and ext2 for installed apps I can not install all apps I use since performance drops significantly).
regards
well, ... dumb me, maybe with compcache you are referring to launch a script?
where do I get this compcache.sh? how do I launch it? from adb? from the terminal? from the sd card?...
HELP!!!! Link2SD not mounting Sd-ext partition
every time while opening this app it asks for type of partition I'm using and then asks for reboot
I chose ext3 as I'm using teejay's CWM
I even check the type of partition using Minitool and it says ext3 and primary
why Link2Sd not mounting sd-ext then?? plz Help
I'm using chocobread 3.2
And as it already has S2E so before doing all this I had uninstalled S2E using root explorer method.
I selected 512mb size
swap size= 0mb
I'm using verbatim class 4 sd card(4 GB)
I followed these steps to partition SD card and Setting up Link2SD by A.cid given in thread
http://forum.xda-developers.com/showthread.php?p=27132543#post27132543
Q) How to create a sd partition?
A) You will need
• A good micro sd-card, with a class greater than 4
(the class is usually printed on the card itself, it’s the number inside the letter ‘C’)
• A rooted galaxy fit running android 2.3.x (preferably on a stock rom), with ClockworkMod recovery
Steps:
• Backup all your data.
• Reboot into CWM.
• Go under “advanced”>”partition sd card”.
• Select the size of your second partition (On my first try, I made a partition of 1024MB but found it too big with a lot of space unused, so I deleted the partition and made a new one of 512MB)
This is your choice, choose one depending on the total size of your card, the no. of apps/games you’ll have etc.
• After selecting that, select swap size as 0MB (This one also is your choice, but I’ll explain why to take 0MB, and not anything else)
• Now wait till the process is completed, and reboot.
As far as I know, CWM v5 makes a partition of EXT3 format.
Q) Why to select swap size as 0MB?
A) Swap partition is made with the objective of utilizing it as VIRTUAL RAM. Now this may sound as a good thing, but in reality the ram in our fit is way faster than the average class 10 micro sd-card. So, instead of speeding up your system, it will slow down your system horribly after a certain point.
So, in short, you shouldn’t be using a swap partition, hence there is no point in creating one if you are not utilizing it.
Steps to setup Link2sd:
• Download Link2sd from Play Store (it’s a free app).
• After it gets installed, run it, and allow root access.
• You will get a message to select the format of your sd partition, select “ext3”.
• Link2sd will then automatically create mount scripts that it requires to work, and will then tell you to reboot your phone.
• Do a proper reboot, and not a ‘hot reboot’.
• After rebooting, open up Link2sd, press menu then select “settings”.
• Select/check the options “automatically link newly installed applications to sd”, “auto link notification”, “relink lib files at boot” (and “fast scroll”, if you want).
• For “install location” option, select “internal”.
• Then go to “auto link settings” and select/check all the three options (you can skip/ unselect “link dalvik-cache file” if you wish)
• Done
Now, every new app that you will install will automatically be moved to your sd ext partition.[/INDENT]
Nikhil_G said:
HELP!!!! Link2SD not mounting Sd-ext partition
every time while opening this app it asks for type of partition I'm using and then asks for reboot
I chose ext3 as I'm using teejay's CWM
I even check the type of partition using Minitool and it says ext3 and primary
why Link2Sd not mounting sd-ext then?? plz Help
I'm using chocobread 3.2
And as it already has S2E so before doing all this I had uninstalled S2E using root explorer method.
I selected 512mb size
swap size= 0mb
I'm using verbatim class 4 sd card(4 GB)
I followed these steps to partition SD card and Setting up Link2SD by A.cid given in thread
http://forum.xda-developers.com/showthread.php?p=27132543#post27132543
Q) How to create a sd partition?
A) You will need
• A good micro sd-card, with a class greater than 4
(the class is usually printed on the card itself, it’s the number inside the letter ‘C’)
• A rooted galaxy fit running android 2.3.x (preferably on a stock rom), with ClockworkMod recovery
Steps:
• Backup all your data.
• Reboot into CWM.
• Go under “advanced”>”partition sd card”.
• Select the size of your second partition (On my first try, I made a partition of 1024MB but found it too big with a lot of space unused, so I deleted the partition and made a new one of 512MB)
This is your choice, choose one depending on the total size of your card, the no. of apps/games you’ll have etc.
• After selecting that, select swap size as 0MB (This one also is your choice, but I’ll explain why to take 0MB, and not anything else)
• Now wait till the process is completed, and reboot.
As far as I know, CWM v5 makes a partition of EXT3 format.
Q) Why to select swap size as 0MB?
A) Swap partition is made with the objective of utilizing it as VIRTUAL RAM. Now this may sound as a good thing, but in reality the ram in our fit is way faster than the average class 10 micro sd-card. So, instead of speeding up your system, it will slow down your system horribly after a certain point.
So, in short, you shouldn’t be using a swap partition, hence there is no point in creating one if you are not utilizing it.
Steps to setup Link2sd:
• Download Link2sd from Play Store (it’s a free app).
• After it gets installed, run it, and allow root access.
• You will get a message to select the format of your sd partition, select “ext3”.
• Link2sd will then automatically create mount scripts that it requires to work, and will then tell you to reboot your phone.
• Do a proper reboot, and not a ‘hot reboot’.
• After rebooting, open up Link2sd, press menu then select “settings”.
• Select/check the options “automatically link newly installed applications to sd”, “auto link notification”, “relink lib files at boot” (and “fast scroll”, if you want).
• For “install location” option, select “internal”.
• Then go to “auto link settings” and select/check all the three options (you can skip/ unselect “link dalvik-cache file” if you wish)
• Done
Now, every new app that you will install will automatically be moved to your sd ext partition.[/INDENT]
Click to expand...
Click to collapse
Same prob.
Can anyone help with link2sd on galaxy fit plz...
Sent from my GT-S5670 using xda premium
try different ext
Try ext4, it will surely work..
I had same prob on some roms..
"Bt nxt tym you flash anything through recovery you may have to mount ext4 again... "-nt pretty sure about this though..
Sent from my GT-S5670 using XDA
Nikhil_G said:
Can anyone help with link2sd on galaxy fit plz...
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
You didnt try the stuff I had replied about in my thread?
Sent from my GT-S5670
link2sd not working
try to format the sd card with MiniTool Partition Wizard Home Edition and make last partition as primary and Ext4.
problem that i can't see available memory..
I can't see the available memory , I mean i have partitioned 1024mb..but wen i see in the task manager it just shows 180mb..
pardasanichirag2 said:
I can't see the available memory , I mean i have partitioned 1024mb..but wen i see in the task manager it just shows 180mb..
Click to expand...
Click to collapse
That's normal, the task manager just displays the internal memory of the phone, I'm using S2E with Official Cyanogenmod and it works fine.
pardasanichirag2 said:
I can't see the available memory , I mean i have partitioned 1024mb..but wen i see in the task manager it just shows 180mb..
Click to expand...
Click to collapse
Use titanium backup or sd maid , these apps could show the size of your ext4 partition
Sent from my GT-S5670 using xda premium
you can mount your ext partition from cwm recovery - mount and storage - mount sd ext and reboot ...then in link2sd go in storage info you can see the sizes of partitions
Cheers
Sent from my GT-S5670 using xda premium
Hi All,
I got errors mentioned in the title and after few searches, found that there are few Galaxy SL owners who had got into this issue.
Currently Known Root Cause:
A hardware issue possibly due to a board issue or loose attachment of internal SD card to the motherboard (Grrrrrrr SAMSUNG!)
Symptoms:
- Suddenly core applications like phone/messaging start force closing (sometimes all open apps). Only a reboot will solve the issue.
- Sudden reboot of the phone after few hours of running (or even sleeping)
- Sometimes the restart itself hanging with a yellow message "Unknown Upload Mode"
- Message in status bar "Internal SD card has been removed unexpectedly" or "Internal SD card not accessible" or something like "Damaged SD card"
Known Solution:
1. Replacement of board from Samsung Service Center (Good for you if you are within the warranty period)
2. Do some hardware hack to remove the internal SD completely (http://forum.xda-developers.com/showthread.php?t=1651619)
I got this issue just after I finished my warranty period, and hence, I was trying to find if I can do something about this issue by my own. What I wanted was to actually swap my internal SD storage with a proper external SD storage. This is not same as the popular "swapping the internal and external SD card" topic, but that and something more as well!! This will solve the issue of force closes and sudden reboots (may still not solve issue of reboot getting stuck, but I assume phone will not need frequent reboot after solving first 2 issues!)
Galaxy SL has 3 partitions created in the card:
1. ext3 partition for data
2. another small FAT partition - (for what? not sure)
3. Third FAT partition which acts as the normal internal SD card (which is accessible when working as USB mass storage)
Intention here is to move all the partitions to the external SD. Looking at the mount points and vold.fstab, I could not find where the 2nd partition in the above list is mounted/used (If anyone knows, please let me know). So I decided to move atleast the ext3 (data) and fat (/sdcard) to the external SD.
Following are the steps I followed for doing the same:
WARNING!!!
1. Copy these at your own risk. I am not responsible if you brick your phone or lose your data/applications/settings or if the phone goes to a boot loop!
2. Do not continue if you do not understand what is written here
3. Doing this will change the /data partition. So wiping data partition in the normal way will not work (say from CWM). You may need to do 2 steps - wipe (internal) data normally (say using CWM), wipe (external SD) data manually by disabling the script mentioned in the procedure and wiping using make_ext4fs tool (steps are given in PART 3 of this post).
4. This has been tested only on CM9 Alpha 6-11 / rooted DDLF2. Theoretically it may or may not work on other ROMs, depending on other tweaks and changes in the system, no guaranty offered!
5. In case you mess it up, most of the time (but no guarantees!), you can recover by flashing from beginning using ODIN some base versions like KPE and then come to your normal ROM, followed by a nandroid recovery (so better do a nandroid backup before you try anything .
Pre-requisites:
- Rooted Phone
- Kernel with init.d support (and preferably ext4 as well if you want that)
- Basic ADB knowledge
- A blank micro SD card with at least class 4 (class 6 or greater preferred) speed and with sufficient capacity - say 8/16/32 GB
PART 1 - PREPARING THE EXTERNAL SD
--------------------------------------------------------------------
0. !!! FIRST !!!
Do a Nandroid Backup (and also other app level backups like Titanium or MyBackup)
Backup contents of your FAT partition (mmcblk0p1) - ie, the internal SD card card
Backup contents of your external SD card
1. Download sdparted-recovery.zip from web (http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage - check messages like 11 to see the basic usage) and extract the contents
2. Using ADB, copy the extracted files in sdparted directory into /system/bin, change permission for all of them to 755 using chmod
3. Put a clean external SD card into the phone
4. In an ADB shell, run /system/bin/parted giving mmcblk1 as the target. Now resize the existing FAT partition (this is the first and default partition in the card). Tips:
print gives the existing partition(s)
help gives help on various options
for resizing and creating partitions, inputs should be derived from the initial print output (which gave the first and last points)
Eg: If card is 16GB, and you want to reserve 4GB for data, then resize the first partition to 12GB
5. Create a new partition of type ext2 with remaining size (say 4G in our case). Save and quit parted.
7. (Do this only if your kernel supports ext3/ext4) Run "tune2fs -j /dev/block/mmcblk1p2" to convert ext2 to ext3
8. (Do this only if your kernel supports ext4) Using ADB, copy "make_ext4fs" (attached) to /system/bin
9. (Do this only if your kernel supports ext4) Convert ext3 partition to ext4 using make_ext4fs ("make_ext4fs /dev/block/mmcblk1p2")
10. Now the partitions are ready
- They will be visible as mmcblk1p1 (FAT) and mmcblk1p2 (ext4) when you cat the /proc/partitions
- They will be visible as partitions 1(FAT) and 2 (ext4) in the print output of parted.
Confirm the above before proceeding further.
PART 2 - SWAPPING EXTERNAL AND INTERNAL SD
---------------------------------------------------------------------------------
1. Write a script, say 00remnt similar to the attached sample file which currently I am using (If you do not follow the script, better don't proceed. Else check if things are fine for your current base ROM settings)
2. Push this into /etc/init.d/ using ADB
3. Change permissions of the file to 755
4. If you need, copy the contents of your internal SD card FAT partition (/sdcard) to the external SD card FAT partition (/sdcard/external_sd or /emmc)
5. Use the popular (relevant methods) to swap the internal and external FAT partitions (which actually changes the vold.fstab contents). Normal search in the forum will give you the available methods - some ROMs support it as options, others have mods which will accomplish the same
5. Reboot and enjoy
Voila!!! Now the system is not using internal SD card (for most purposes) at all!! And your phone can now run for days without abrupt force closes and reboot. You still may get a message like SD card is removed/damaged, (and /emmc or /sdcard/exteranal_sd may become inaccessible - so better use it only as a temporary storage!). But you can safely ignore these messages as that is the internal SD card which we are not using anyway... Enjoy...
PART 3 - WIPING DATA PARTITION (in case you need this step later)
-----------------------------------------------------------------------------------------------------------
1. Change permission of the 00remnt to 644
2. Reboot the phone (now the phone will come up with default internal SD partition for data)
3. From ADB shell, execute "make_ext4fs /dev/block/mmcblk1p2" (see PART 1 on how to get this tool)
4. Change permission of the 00remnt to 755
5. Reboot the phone to recovery, wipe the /data as normal
rgds,
Dipu.
PS: If any one knows how our phone uses the 2nd partition in the internal SD card, please let me know... I am assuming that it is not used for any critical purposes (as my phone ran successfully for few days without any issue). May be it is used in some kernel/ROM, if so, please let me know.
Though i didn't understand a word(being an internee dentist) it will be useful to others.appreciate your efforts!!
Sent from my GT-I9003 using xda app-developers app
This is what i call a complete and useful guide.
This should become a sticky.. now... NOW!
+1 for sticky, superb info.
that would be a really nice sticky
i had the motherboard changed..
Thanks Dipu K for your efforts.
I've tried this solution in my I9003, and I have only a problem: When reboot the phone, /data is copied into de Ext4 partition on SD card, but all aplications have errors because isn´t possible to unmount /data,
Here is the messaje in remnt-log (only a few lines):
Code:
...
3. Make Directory --->
4. Mount new data partition from external SD --->
5. Copy the current files in /data
6. Remove current files in /data
7. Unmount /data
umount: can't umount /data: Device or resource busy
8. Remove dir /data as a safety measure
9. Linking external sd data partition as /data
10. Final Mount status --->
...
What can I do to correct this?
Thanks
bfsa said:
...
What can I do to correct this?
Thanks
Click to expand...
Click to collapse
Finally, I've changed a line on 00remnt, and seems to work properly: busybox umount -l /data 2>> /system/remnt-log
Where can I get make_ext4fs? Sadly the same case has happened to me...
Hi Guys.
I am using alpha 4 from last one month and experience was awesome but from last 1 week I am getting lot of FC for lot of services like exchange service gapps what's up camera and lot more. I am not sure why FC issue started happening from last one week.
History :
I was using CM 10 alpha 1 then alpha 2 then alpha 3 and now on alpha 4.
I really fed up with Force close issue from last one week . I tried reboot but still 80% of apps and services getting FC. Please guide me on this .
Sent from my GT-I9003 using xda app-developers app
Sent from my GT-I9003 using xda app-developers app
hi all, i have a galaxy i9003 with a corrupted or completely dead (not sure) internal memory chip. I have come to this conclusion after 3 days of trying to install custom and stock roms. I can access recovery and download mode but i cant install any ROM, the phone keeps rebooting after the SAMSUNG (whole screen black except SAMSUNG in the middle). All i have is atm this http://forum.xda-developers.com/showthread.php?t=1351056 installed on my phone via ODIN. I dont have knowledge about ADB, can somebody help me out with instructions more?
Pre-requisites:
- Rooted Phone
Click to expand...
Click to collapse
Is there a solution without a rooted phone or can I root it somehow, even if the there is a hardware defect? I got an error with /dev/block/mmcblk1p that rfs can't be written.
I have a problem. My friend gave me an i9003. Wipe is not working at all, even from Recovery. I connect the phone to PC and use the internal card, no matter what I do, changes don't apply. I copy/paste/delete/format/even odin flash, no good. Everything comes back as before reboot. What is it related to?
I used to have an i9000, but nothing applies to i9003. I flashed i9000 1000 times and at last got a mmcblk02 error, fixed it with external sd swap. I'm thinking of swapping emmc with sd on this one too, but cant install a rom from CWM, I can install CWM from ODIN though and can flash CFROOT too, but in CWM internal storage can't be mounted... Motherboard problem?
I will try to use this guide and report back soon...
allxx said:
I have a problem. My friend gave me an i9003. Wipe is not working at all, even from Recovery. I connect the phone to PC and use the internal card, no matter what I do, changes don't apply. I copy/paste/delete/format/even odin flash, no good. Everything comes back as before reboot. What is it related to?
I used to have an i9000, but nothing applies to i9003. I flashed i9000 1000 times and at last got a mmcblk02 error, fixed it with external sd swap. I'm thinking of swapping emmc with sd on this one too, but cant install a rom from CWM, I can install CWM from ODIN though and can flash CFROOT too, but in CWM internal storage can't be mounted... Motherboard problem?
I will try to use this guide and report back soon...
Click to expand...
Click to collapse
Please do send us a report, I'd appreciate it very much. Have to deal with a similar situation as well for an old i9003. I've tried to employ the steps mentioned here but could not get it to work as well.
Hi everybody!
Had to remove the internal SD to install everything on the external one by following the mentioned post. Nothing else worked.
http://forum.xda-developers.com/showthread.php?t=1651619
can anyone here recomended me custom rom that already with swap sdcard?
Dipu K said:
Hi All,
I got errors mentioned in the title and after few searches, found that there are few Galaxy SL owners who had got into this issue.
Currently Known Root Cause:
A hardware issue possibly due to a board issue or loose attachment of internal SD card to the motherboard (Grrrrrrr SAMSUNG!)
Symptoms:
- Suddenly core applications like phone/messaging start force closing (sometimes all open apps). Only a reboot will solve the issue.
- Sudden reboot of the phone after few hours of running (or even sleeping)
- Sometimes the restart itself hanging with a yellow message "Unknown Upload Mode"
- Message in status bar "Internal SD card has been removed unexpectedly" or "Internal SD card not accessible" or something like "Damaged SD card"
Known Solution:
1. Replacement of board from Samsung Service Center (Good for you if you are within the warranty period)
2. Do some hardware hack to remove the internal SD completely (http://forum.xda-developers.com/showthread.php?t=1651619)
I got this issue just after I finished my warranty period, and hence, I was trying to find if I can do something about this issue by my own. What I wanted was to actually swap my internal SD storage with a proper external SD storage. This is not same as the popular "swapping the internal and external SD card" topic, but that and something more as well!! This will solve the issue of force closes and sudden reboots (may still not solve issue of reboot getting stuck, but I assume phone will not need frequent reboot after solving first 2 issues!)
Galaxy SL has 3 partitions created in the card:
1. ext3 partition for data
2. another small FAT partition - (for what? not sure)
3. Third FAT partition which acts as the normal internal SD card (which is accessible when working as USB mass storage)
Intention here is to move all the partitions to the external SD. Looking at the mount points and vold.fstab, I could not find where the 2nd partition in the above list is mounted/used (If anyone knows, please let me know). So I decided to move atleast the ext3 (data) and fat (/sdcard) to the external SD.
Following are the steps I followed for doing the same:
WARNING!!!
1. Copy these at your own risk. I am not responsible if you brick your phone or lose your data/applications/settings or if the phone goes to a boot loop!
2. Do not continue if you do not understand what is written here
3. Doing this will change the /data partition. So wiping data partition in the normal way will not work (say from CWM). You may need to do 2 steps - wipe (internal) data normally (say using CWM), wipe (external SD) data manually by disabling the script mentioned in the procedure and wiping using make_ext4fs tool (steps are given in PART 3 of this post).
4. This has been tested only on CM9 Alpha 6-11 / rooted DDLF2. Theoretically it may or may not work on other ROMs, depending on other tweaks and changes in the system, no guaranty offered!
5. In case you mess it up, most of the time (but no guarantees!), you can recover by flashing from beginning using ODIN some base versions like KPE and then come to your normal ROM, followed by a nandroid recovery (so better do a nandroid backup before you try anything .
Pre-requisites:
- Rooted Phone
- Kernel with init.d support (and preferably ext4 as well if you want that)
- Basic ADB knowledge
- A blank micro SD card with at least class 4 (class 6 or greater preferred) speed and with sufficient capacity - say 8/16/32 GB
PART 1 - PREPARING THE EXTERNAL SD
--------------------------------------------------------------------
0. !!! FIRST !!!
Do a Nandroid Backup (and also other app level backups like Titanium or MyBackup)
Backup contents of your FAT partition (mmcblk0p1) - ie, the internal SD card card
Backup contents of your external SD card
1. Download sdparted-recovery.zip from web (http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage - check messages like 11 to see the basic usage) and extract the contents
2. Using ADB, copy the extracted files in sdparted directory into /system/bin, change permission for all of them to 755 using chmod
3. Put a clean external SD card into the phone
4. In an ADB shell, run /system/bin/parted giving mmcblk1 as the target. Now resize the existing FAT partition (this is the first and default partition in the card). Tips:
print gives the existing partition(s)
help gives help on various options
for resizing and creating partitions, inputs should be derived from the initial print output (which gave the first and last points)
Eg: If card is 16GB, and you want to reserve 4GB for data, then resize the first partition to 12GB
5. Create a new partition of type ext2 with remaining size (say 4G in our case). Save and quit parted.
7. (Do this only if your kernel supports ext3/ext4) Run "tune2fs -j /dev/block/mmcblk1p2" to convert ext2 to ext3
8. (Do this only if your kernel supports ext4) Using ADB, copy "make_ext4fs" (attached) to /system/bin
9. (Do this only if your kernel supports ext4) Convert ext3 partition to ext4 using make_ext4fs ("make_ext4fs /dev/block/mmcblk1p2")
10. Now the partitions are ready
- They will be visible as mmcblk1p1 (FAT) and mmcblk1p2 (ext4) when you cat the /proc/partitions
- They will be visible as partitions 1(FAT) and 2 (ext4) in the print output of parted.
Confirm the above before proceeding further.
PART 2 - SWAPPING EXTERNAL AND INTERNAL SD
---------------------------------------------------------------------------------
1. Write a script, say 00remnt similar to the attached sample file which currently I am using (If you do not follow the script, better don't proceed. Else check if things are fine for your current base ROM settings)
2. Push this into /etc/init.d/ using ADB
3. Change permissions of the file to 755
4. If you need, copy the contents of your internal SD card FAT partition (/sdcard) to the external SD card FAT partition (/sdcard/external_sd or /emmc)
5. Use the popular (relevant methods) to swap the internal and external FAT partitions (which actually changes the vold.fstab contents). Normal search in the forum will give you the available methods - some ROMs support it as options, others have mods which will accomplish the same
5. Reboot and enjoy
Voila!!! Now the system is not using internal SD card (for most purposes) at all!! And your phone can now run for days without abrupt force closes and reboot. You still may get a message like SD card is removed/damaged, (and /emmc or /sdcard/exteranal_sd may become inaccessible - so better use it only as a temporary storage!). But you can safely ignore these messages as that is the internal SD card which we are not using anyway... Enjoy...
PART 3 - WIPING DATA PARTITION (in case you need this step later)
-----------------------------------------------------------------------------------------------------------
1. Change permission of the 00remnt to 644
2. Reboot the phone (now the phone will come up with default internal SD partition for data)
3. From ADB shell, execute "make_ext4fs /dev/block/mmcblk1p2" (see PART 1 on how to get this tool)
4. Change permission of the 00remnt to 755
5. Reboot the phone to recovery, wipe the /data as normal
rgds,
Dipu.
PS: If any one knows how our phone uses the 2nd partition in the internal SD card, please let me know... I am assuming that it is not used for any critical purposes (as my phone ran successfully for few days without any issue). May be it is used in some kernel/ROM, if so, please let me know.
Click to expand...
Click to collapse
Somebody's Samsung Galaxy SL i9003 had wiped the internal SD card by itself! Is this even possible that it just wipes/formats on it's own? Is there any advice? The contacts appear to still be there.
This Script + boot.img Aims to make as much as possible use of the sdcard (ext2 Partition) and use it as the internal space of the phone.
Anyone who got the time to download v2 can use the "upgrade-from-v2" script to upgrade to version 3 (you need 2 reboots), in version 3 (if you installed v1 you need to wipe/factory + format ext2)
In version 3 the script deletes Maps.apk and Street.apk & language Packs of keyboard. (if you want it, backup those apks and install them again to /data) with the space left in /custpack partition the script is able to link all dalvik of system and custpack apps, this drives the reads/write of the sdcard to 0 zero, everything in the phone is fast as normal since it will use its nand, and the sd is dedicated to every new apk is installed.
Change log:
Version 5
1. Changed the way it copies files to retain file attributes
2. Copy with force over-write
3. Check for deleted apps and delete files from ext durring the schedule check for linking.
This change will correct problems were one app would brake after a reboot (if this app was installed before)
Note: file name says v4 but its v5
Version 4 Deals with random broken libraries after a reboot.
Notice:
Use a Fast SDCard class 6 or 10 with good response time
* First boot up takes much longer.
* Then you have to reboot again 1 time to be fully installed.
* Give the ext2 partition 1.5 Giga Or 2giga its enough.
Troubleshooting:
* If you having problems with an app, uninstall it, reboot, then install it again.
Back up all of your apps:
adb shell
mkdir /sdcard/myapps
cp /data/app/* /sdcard/myapps
Click to expand...
Click to collapse
And after the wipe etc.
adb shell
cp /sdcard/myapps/* /data/app/
reboot
Click to expand...
Click to collapse
Installation
1. While the phone is turned on completely, (and rooted run Setup.bat
2. Turn off phone and flash the new boot.img (sd-boot.img )
3. Turn on phone enter to recovery and wipe/factory data.
4. Format sdcard with ext2 Partition, insert it, turn on phone and wait a lot for the first boot as it will take time
Only at your own risk Be careful because you have to flash the modified boot.img to use it.. flash it using the files you used to flash boot for rooting the phone.
Note: All bugs have been fixed, version 6. Actually with a class 10 my phone runs more smoothly and faster even than stock rom... if anyone is intersting for a release.. leave a comment.
frapedas said:
This Script + boot.img Aims to make as much as possible use of the sdcard (ext2 Partition) and use it as the internal space of the phone.
Anyone who got the time to download v2 can use the "upgrade-from-v2" script to upgrade to version 3 (you need 2 reboots), in version 3 (if you installed v1 you need to wipe/factory + format ext2)
In version 3 the script deletes Maps.apk and Street.apk & language Packs of keyboard. (if you want it, backup those apks and install them again to /data) with the space left in /custpack partition the script is able to link all dalvik of system and custpack apps, this drives the reads/write of the sdcard to 0 zero, everything in the phone is fast as normal since it will use its nand, and the sd is dedicated to every new apk is installed.
Change log:
Version 5
1. Changed the way it copies files to retain file attributes
2. Copy with force over-write
3. Check for deleted apps and delete files from ext durring the schedule check for linking.
This change will correct problems were one app would brake after a reboot (if this app was installed before)
Note: file name says v4 but its v5
Version 4 Deals with random broken libraries after a reboot.
Notice:
Use a Fast SDCard class 6 or 10 with good response time
* First boot up takes much longer.
* Then you have to reboot again 1 time to be fully installed.
* Give the ext2 partition 1.5 Giga Or 2giga its enough.
Troubleshooting:
* If you having problems with an app, uninstall it, reboot, then install it again.
Back up all of your apps:
And after the wipe etc.
Installation
1. While the phone is turned on completely, (and rooted run Setup.bat
2. Turn off phone and flash the new boot.img (sd-boot.img )
3. Turn on phone enter to recovery and wipe/factory data.
4. Format sdcard with ext2 Partition, insert it, turn on phone and wait a lot for the first boot as it will take time
Only at your own risk Be careful because you have to flash the modified boot.img to use it.. flash it using the files you used to flash boot for rooting the phone.
Note: All bugs have been fixed, version 6. Actually with a class 10 my phone runs more smoothly and faster even than stock rom... if anyone is intersting for a release.. leave a comment.
Click to expand...
Click to collapse
Hi frapedas, sorry for the late reply
This works in 991D?
I cant get dalvik cache in SD card with Yuwing scriptz
qashqool said:
Hi frapedas, sorry for the late reply
This works in 991D?
I cant get dalvik cache in SD card with Yuwing scriptz
Click to expand...
Click to collapse
yes it should work
Hi There
Can someone explain what he\she did to partition SD card, and make all apps get installed on it.
Please note :
1. I don't want to use Titanium backup for this usage. I don't have the paid version and I'm tired of doing this one app at a time.
2. I saw some guides on the net, but they were all for GB.
(partition the microSD on PC using minitool) -can we use ext4 on our MTD ROMs ? What is the 1st partition for ? and the 2nd ?
(install busybox and super user) - Is it still needed ? (MIUI for example has LBE as su).
(install Link2SD) - Is it always in memory ?
(reboot and put partitioned SD card)
(Define Link2SD)
3. I also saw swapper instructions but I can manage with 170MB free RAM memory I get after removing all unnecessary system apps, and I remember ppl saying then that it kills the SDCard very quickly.
If someone has a clear guide or instructions that he knows work, that will be nice.
Thanks in advance.
Step 1. Partition your SD card to have a sd-ext partition. This can definitely be ext2 or FAT16. Anything else depends on your kernel. Most of them do support ext3 and 4, but... start with something fairly basic.
Regarding recoveries:
TWRP has always failed for me on this, so I'd avoid that.
This may be doable in CWM. I've seen reference to that newer versions of CWM removed the partition option, so you might need to flash an ICS ROM with an older kernel, repartition, and then flash back to the one you want.
Also note that if you use CWM to repartition, your SD-card will be wiped. So do a backup first.
Step 2. Install Mounts2SD. Either from XDA or the Play Store. Even if you do take it from the Play Store to get update notifications, I highly suggest grabbing the recovery script from the XDA thread so that you can get back your shifted applications without needing to re-download and install M2SD, since it likes to be on internal which means... shifted off.
Step 3. Open Mounts2SD. Grant SU rights at whatever point it asks for it during step 3. Hit the menu button. Go to Application Settings. Install the Startup Script. Tell it to use the built-in busybox as well, so that you don't need to install anything or worry about it failing. Back out of the Application Settings.
Step 4. Press on the Wrench to go into the actual specific settings. I currently have forced Cache, 1% Storage Threshold, Applications are the only bit moved, the File System Check is on and using the Ext4 Driver, 128KB Deadline for Internal and 4096 with Deadline for External, and Safe Mode is disabled. But decide on what you want yourself, set it, go back to the Eye to see your current info.
Step 5. Reboot.
Step 6. Wait 1-30 minutes for it to finish moving all your stuff around.
Step 7. Unlock your phone, open Mounts2SD, and make sure everything looks pretty on that first 'Eye' info tab. If you like it then close Mounts2SD and keep going on your merry way. If you don't like it or you've done something like offload your data and now your phone is wretchedly slow, go to the Wrench, change your settings, go back to the Eye, and reboot again. Repeat until satisfied.
I thought it would be simplier.
A few more questions:
1. If I partition SD on PC, then I don't need any partitioning on recovery so it should work fine even on TWRP or advanced CWMs. Am I right?
2. Why do I need scripts for? Isn't the app enough?
3. Why should/could it possibly slow down my device? TB 'move to SD' for all doesn't slow my device what so ever.
4. How and where do I see what partition is used for what?
5. How much RAM does the app take?
6. Have you tried other apps link2sd or something CM has built in I think.?
Thanks.
sent from me
New answers to new questions.
1. Skip step 1 if you've done it on your PC. I just suggested recovery as that's easy... if you've made your sd-ext partition on the PC, step 1 is done.
2. No clue on Link2SD. I use Mounts2SD instead since it lets me set things. It probably does the same thing though and sets a init.d script that gets run during startup.
3. True. For some reason though having all your data moved to sd-ext makes our phone go to a crawl. Same if you move off the dalvik.
4. That's in Mounts2SD. No clue how you can see if you're using Link2SD.
5. For Mounts2SD, none while it's being used, since it just runs as a startup script. The app is just to control the script.
6. Not successfully. I had tried 5 or 6 different apps back a year ago or so when I first started playing with sd-ext and Mounts2SD was the best and free, so... never looked back after that. Now you can also do some system-flag tweaking if you want to donate, but the sd-ext stuff is all free.
I was able to successfully partition SD and use mount2sd on 4.3 SlimBean.
however, it was rather slow.
CM 10.1 and CM10.2 by DJL. did not allow me to partition nor did they recognize SlimBean's partition even if I replaced them kernel (to NilTMT).
I'm currently using CM10.1 which is stable as a daily driver and manually swapping apps with TB, I hate it, but this is the best combination I've come so far.
I sold my wife's SGS4G and upgraded her to SGS3 and hopefully in a year I will do the same. it had its moments, but on the bottom line it's a pretty ****ty phone with its lack of internal mem...but hey, it drove so many of us to go deeper and deeper trying to understand and made us more tecnolgical and solution oriented.
Mounts2SD worked for me on CM10.1, so not sure why it failed for you. Ah well.
A few things I have found...
Yes, you can partition on Windows, but you're really asking for trouble. It's not too bad download Ubuntu or the like and you can boot off a USB stick without touching your Windows install.
The TeamAcid kernels that I know of handle ext2/3/4 file systems. All kinds of arguments as to which are better. I personally use ext4 and don't find it obviously "slow" for the way I use my phone.
That said, what the boot scripts (which are part of a flashed "kernel" for the SGS4G) actually do with a "special" partition is another story. In some cases the first stages of booting will look for special partitions and mount them in pre-configured places. For example, the second partition of the removable card might be mounted on /sd-ext/ in many CyanogenMod ROMs. Many (most?) SGS4G ROMs don't have these "special" mount rules defined.
Moving an app to SD using the "native" approach just moves the app and none of its data to the SD card. It won't for example, move 25 MB of mail from /data/data to your microSD
Moving an app to SD (or anywhere else) doesn't keep it from generating its classes in /data/dalvik-cache -- It isn't "free" to have an app on SD as far as internal storage goes, even if it doesn't write any data.
Moving an app to SD will absolutely slow down your boot time. It does it by creating a file that contains a file system that then gets read and mounted at boot time. You can watch the parade of them getting mounted using adb logcat. It can take a minute or two to mount them all. Once mounted, that double layer of file systems shouldn't slow you down too much, since it is basically a read-only kind of thing.
Scripts are required since you need to be able to "fake out" the operating system as to where things are stored for anything (except if you just use the native app to SD method). In most cases you need new partitions mounted before the Android part of the OS starts running.
Some scripts are more robust than others.
TitaniumBackup (paid version) has a way to move data to an external partition. It works like a charm for me (64 GB Sandisk UHS-1 / Class 10 microSD). It was very tweaky for me to get it to recognize the ext4 partition the first time. It can bulk-move app data to the partition. I don't know which, if any, of the other scripts move the data to an external partition.
On my phone, an ext4 file system can be significantly faster than the internal yaffs, especially for write. Alas, it usually seems to be read that is a killer for most things in an well-written app. On my phone, yaffs can be faster than ext4 for short reads. Who knows how this would play out in real-world usage.
Other things that TitaniumBackup can do that help free up internal storage, at least in the paid version, are:
Dalvik cache cleanup
Integrate system Dalvik cache into ROM
Integrate update into ROM
Convert to system app
I can confirm Link2SD works where Mount2SD fails, which is an ext3 partitioned sd-ext on AOKP. it doesn't get any simpler than that.
sent from me