[Android Software/Hacking General [Developers Only]] stempox:
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