Lately, I've been flashing a bunch of different ROMs, and in each one, they require you to have a certain amount of your memory partitioned. I'm not too experienced in this particular area and I've been wondering what is the point of all the partitioning?
Why can't we just have one partition and run things off of that like with a computer running on windows??
What are the differences between ext2 and ext3 and so on?
So far, I've only been able to find out that the swap partition is for memory extension when the phone is currently using all of its ram, it can convert some of the sd card's memory to use for programs. Can anyone provide more insight on this?
I've asked myself the same questions .... hope someone will explain...
hacker01 said:
Lately, I've been flashing a bunch of different ROMs, and in each one, they require you to have a certain amount of your memory partitioned. I'm not too experienced in this particular area and I've been wondering what is the point of all the partitioning?
Why can't we just have one partition and run things off of that like with a computer running on windows??
What are the differences between ext2 and ext3 and so on?
So far, I've only been able to find out that the swap partition is for memory extension when the phone is currently using all of its ram, it can convert some of the sd card's memory to use for programs. Can anyone provide more insight on this?
Click to expand...
Click to collapse
It would be helpful if you mentioned what phone you're using.
Generally the reason you have a /data and /system partition separately are so that you can either upgrade or reinstall Android without losing your data. If you reflashed whatever ROM you're on right now again, without wiping anything, all of your apps and settings would still be there (although any mods you flashed to modify the ROM itself would need to be flashed again).
System - Holds Android itself and any apps that came with the ROM. Some ROMs (or rather updater scripts inside of ZIP files) will install some apps in the data partition to save space.
Data - Your settings and any applications you installed.
Sometimes you WILL have to wipe everything to go to a different ROM, but for the most part if you're on an official ROM that came with your phone, and your carrier pushes an update, you don't have to.
I'm guessing you have an older phone if you need to make a swap file. A swap file is like RAM in the form of a file; if your phone runs out of usable RAM, it can use the [slower, but useful] swap file, which is like memory you reserve from storage [your MicroSD card]. Windows and other OS's use swap files too, but given how much RAM we have in computers today, we hardly ever use it.
EXT 2 fs - A non-journaling file system. It's quicker than EXT 3 and takes up less space for itself in memory (not for files, just for itself), but it's more susceptible to corruption if you randomly turn off the phone while a file is being accessed.
EXT 3 fs - A journaling file system, which means that it keeps track of any file operations within itself. While it's slower than EXT 2 and takes up more space, it is more reliable and is safer in terms of file integrity.
There's also EXT 4, but only certain phones are compatible with that, mostly Samsung Galaxy S phones.
tl;dr: It keeps everything modular.
Thanks for the explanation. It helped
Sent from my PC36100 using XDA Premium App
I put this short guide together because I tend to see a lot of confusion regarding what a "wipe data / factory reset" does to your phone.
These are the steps you should take before loading a new ROM:
1) Download your new ROM and relevant supporting or needed files like modem, alternate kernel, etc., and place them on your internal SD.
2) Backup your applications, settings, messages, etc., with a backup tool like Titanium Backup, image specific backup tool, etc.
3) Boot into recovery and run a “wipe data/factory reset"
4) Follow the developers ROM loading instructions.
When you perform a “wipe data/factory reset” the content of the following directories are deleted :
/data
/cache
/datadata
/sd-ext
/sdcard/.android_secure
Nothing else on your SD card (internal or external) outside of these directories is modified so it is safe to leave files outside of the above mentioned directories without fear of losing them. Your external SD card and SIM do not need to be removed. The goal here is load a new or updated ROM in as much a clean environment that you can. Files left behind in these, especially cache and davlik-cache can cause some of the strangest problems. The kind that nobody can really resolve.
/cache - This is the partition where Android stores frequently accessed data and application components to make these, as implied, respond much faster as well as faster to retrieve / access.
/datadata – This directory contains the library, database, user specific configuration files as well as log files for its specific application installed in the /data directory.
/data directory is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially restores it to the way it was when you first booted it, or how it was after your last custom ROM install.
If your ROM uses an /sd-ext partition on your SD card for data storage your /data directory is mapped to /sd-ext and wiping the /sd-ext directory will result in losing your data.
/sd-ext is used for apps moved to your SD card. Your Android OS runs natively in an ext format while your SD card has a fat32 format, which is used typically for USB storage devices, Windows computers, etc.
The sd-ext partition is an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have APP2SD or data2ext enabled. It is popularly used on devices that have little memory allotted to the /data partition. A misfortune that in my experience, Captivate does not partake in. Still, users who want to install more programs than the internal memory allows can take advantage of this partition and use it with a ROM supporting this feature.
The folder named .android_secure is where apps are stored when you perform the "move from phone to SDram/SD card" operation.
Consider this, Apps2SD uses the fat32 portion of your SD card, which is obviously limiting because it isn't Androids native file system. However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.
Disclaimer! I am not responsible for any damage you may cause to your phone or SD Card if you try to enable/use sd-ext.
To enable sd-ext in ClockWork Mod (ROM Manager):
Boot into CWM
Go to Advanced
Then to "Partition SD Card"
Choose an sd-ext size
Then choose a swap size, or not. Swap is just like windows' virtual memory. The system will use it when you're running low on RAM and use it as temporary RAM storage. This is where you'll probably see an increase in speed.
Just for fun I put sd-ext at 512MB and Swap at 64MB which is probably more than plenty for the swap. The swap will assist a little with memory and with the extra space I can move my apps over to it with a program like App2SD or in most custom ROMs nowadays just use the "move to USB" option in "Manage Applications". Titanium Backup will also move apps to SD for you and I'm sure you can find plenty more in the market.
You can also use a tool like Minitool Partition Wizard:
1. Open Minitool Partition Wizard
2. Delete Existing Partition from SDCard (Backup data first!!)
3. Create Fat32 Partition
Note: Set all partitions to PRIMARY (Steps 3 - 6)
4. Create EXT2 Partition (System) about 150MB-200MB depend on ROM
5. Create EXT2 Partition (Data) about 150MB-250MB
6. Create EXT2 Partition (Cache) about 50MB
Personally I don't see a need to do any of this on either of my Captivate phones though I have played with it on my DEV phone.
And since it does play a big role and needs to be cleared at times...
Davlik-Cache - dalvik cache is a program cache area for the program "Dalvik". Dalvik is a java based virtual machine that is the base for running your (.apk) programs. In order to make access times faster (there wasn't a JIT compiler installed by default until Android 2.2), the dalvik-cache is the result of dalvik doing a optimization of the running program/s. This optimization is kept so that it is then re-used every time you use your application/s. By default, davlik-cache is located in your /data partition.
No, I'm not looking for donations. Just trying to clarify things for some.
Great info, but a "guide" assists you in doing something, this is just straight info.
While I initially intended on writing it to guide flashers into the benefits of a wipe data / factory reset, and avoiding the myriad of strange issues experienced, I can see now where it can more construed as informational. Hmmm... maybe I'll add more to it or ask a mod to change the title topic for me.
Regardless, my hope is that some people get some benefit out of it otherwise I've only wasted my time.
Thanks, I've been wondering for a while what that actually did.
Great start for a guide that should clear the boards up a bit. I vote it to be stickied after adding a bit more info on backing up, partitioning the sd card, dalvik cache, etc.
I think it is important to explain that a reset should not be done after flashing a custom ROM because it deletes the Dev's settings/data/non-system apps. Instead flashers should either reset after flashing back to stock or before flashing a custom ROM over the current custom ROM.
Cozmo1 said:
I put this short guide together because I tend to see a lot of confusion regarding what a "wipe data / factory reset" does to your phone.
When you perform a “wipe data/factory reset” the content of the following directories are deleted :
/data
/cache
/datadata
/sd-ext
/sdcard/.android_secure
/cache - This is the partition where Android stores frequently accessed data and application components to make these, as implied, respond much faster as well as faster to retrieve / access.
/datadata – This directory contains the library, database, user specific configuration files as well as log files for its specific application installed in the /data directory.
/data directory is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially restores it to the way it was when you first booted it, or how it was after your last custom ROM install.
If your ROM uses an /sd-ext partition on your SD card for data storage your /data directory is mapped to /sd-ext and wiping the /sd-ext directory will result in losing your data.
/sd-ext is used for apps moved to your SD card. Your Android OS runs natively in an ext format while your SD card has a fat32 format, which is used typically for USB storage devices, Windows computers, etc.
The folder named .android_secure is where apps are stored when you perform the "move from phone to SDram/SD card" operation.
Consider this, Apps2SD uses the fat32 portion of your SD card, which is obviously limiting because it isn't Androids native file system. However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.
Nothing else on your SD card (internal or external) is modified so it is safe to leave files outside of the above mentioned directories without fear of losing them.
If you plan on trying several different ROM's and/or updating your favorite ROM every time a new version is released you need to invest in an application like Titanium Backup or one that comes with your ROM if it's supplied with one. MIUI includes one that works extremely well. Performing a “wipe data/factory reset" after loading your new ROM and before booting into it should provide you with a smoother transition to your newly chosen or upgraded ROM. Having a standard backup and restoral process should help you enjoy it quicker too.
Click to expand...
Click to collapse
Here is something I keep in a word file to help answer what you are also trying to answer. It is a bit shorter and simplified but it may help to polish your thread for us simpletons.
Dalvik cache is a place where the Android OS re-compiles the executable programs the first time to optimize them. It does this when you make a major change like replace the kernel/modem. Clearing the Dalvik cache will force Android OS to recompile the apps for the the new kernel/modem. This can take time on the first boot after clearing the Dalvik cache.
Also the main data Cache is used by the Android OS at run-time to write temporary files for specific reasons. You want to clear this out so it doesn't re-use the old cached data.
Manually clearing both caches allows the new kernel/modem to be installed in a "cleaner" environment. It's just preventative maintenance.
snowake said:
I think it is important to explain that a reset should not be done after flashing a custom ROM because it deletes the Dev's settings/data/non-system apps. Instead flashers should either reset after flashing back to stock or before flashing a custom ROM over the current custom ROM.
Click to expand...
Click to collapse
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Cozmo1 said:
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Click to expand...
Click to collapse
do u have more info about "format your SD card, or partition a part of it as a ext file system" or how to do that.
i have read someone format part of the sdcard (class 10)to ext 2 or 4,to make the write n read faster.is that what you mean.can u guide me to the right direction.thank in advance.
? ? ? about this......(However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.)
Cozmo1 said:
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Click to expand...
Click to collapse
I struggled with all of this my first first few flashes.
xpakage said:
...Dalvik cache is a place where the Android OS re-compiles the executable programs the first time to optimize them.
...
Also the main data Cache is used by the Android OS at run-time to write temporary files for specific reasons.
Manually clearing both caches allows the new kernel/modem to be installed in a "cleaner" environment. It's just preventative maintenance.[/I]
Click to expand...
Click to collapse
That is much more boiled down. I looked back at the "how to flash" threads and a couple good explanations on custom roms. None explain this that I found.
Cosmo, here are some more thoughts on misunderstandings I have had and seen posted. Like post above I pasted from my notes, so may be incorrect.
Bootloaders: Same for Froyo/Eclaire in both i897 and i9000 roms. GB requires new bootloaders, but i897 are apparently cross-compatible. However, issues seem to pop up on i9000 roms with GB i897 bootloaders. If flashing back to Froyo, use the full jf6 stock, not cezar's stock eclaire without bootloaders.
Using Tibu: If no useful data (i.e. Bookmarks on dolphin) then simply click data only when restoring user apps. Typically no issues when restoring user apps after switching Android versions. However, system apps should not be restored because of the rom customizations. Especially when switching to GB because it uses different directory structure. I do not seem to have issues when staying on same version and restoring foreground (user accessible) apps with data only or restoring green text color sys apps with Tibu as icon (i.e. Accounts).
Rom manager: really only need the app if flash to stock and need to flash rom directly from cwm. If so, then flash cwm (top button in menu) and choose phone. This places update.zip in /sd, which is opened after selecting "reinstall update" in stock recovery. Usually have to select it twice for it to work. This will replace ATT stock 2e recovery (blue text) with cwm 2.5 (froyo).
Voodoo color, lagfix, sound: must either be included in kernel. Lagfix simply allows user to format sd as ext4 (linux). Color balances display so less blue iodes are used and color is more realistic. Sound allows clearer sound through headphones through tweaks enabled in voodoo app. If sound is not in kernel then purchase voodoo pro in market and it will install it into the kernel (if rooted, even if stock).
Thanks for clearing that up!
- Aaron
Updated with more details.
Really, really useful. Had no idea partition options were available to this extent! Especially swap. By mini tool are you referring to Easus' program? I am definitely checking this out tonight. Thanks!
Great guide. In order to clear
/sdcard dir I master clear it after flashing to stock. Is there an alternate method besides deleting dirs myself?
snowake said:
Great guide. In order to clear
/sdcard dir I master clear it after flashing to stock. Is there an alternate method besides deleting dirs myself?
Click to expand...
Click to collapse
That is probably the safest way to do it within the phone itself. An alternate way would be to mount it to your computer:
In Windows right click the drive that was assigned to your internal SD card and then click on format. By default it'll most likely set you to Fat32 and if you click format it'll say its complete, but nothing will be deleted. Android being a Linux OS doesn't use fat. You can format it by choosing exFat, but by doing this...
!!!WARNING!!! be aware that you will lose everything on your internal SD card AND your external SD card.
Emphasis placed mainly for others that read this and might not know.
Safer and easier to do it within the phone.
snowake said:
Really, really useful. Had no idea partition options were available to this extent! Especially swap. By mini tool are you referring to Easus' program? I am definitely checking this out tonight. Thanks!
Click to expand...
Click to collapse
This one is from MiniTool, though I wouldn't be surprised if Easus owned them. I didn't investigate to confirm. You can get the free home edition of MiniTool Partition Wizard here.
Very nice infos. Deserves a sticky, although, probably in a different thread.
Some information on what "Master Clear" in Odin would also be helpful - I have never trusted my phone to 'truly' clear everything on the phone, I have found the Odin Master Clear option to be much more complete.
It is a bit odd, I do this with my PC every six months, I back everything up and format the drive and start over again (after running Spinrite on all the drives) - I do this on / around New Years and again over 4th of July weekend and I decided this past weekend to also do the same with my smart phones (4 Cappies) and tablets (Ipad and 2 Android tabs) this past weekend.
It gives me that sort of squeaky clean feeling and seems to make my devices run smoother. Maybe its all in my head, dunno *shrugs*.
One thing I can say however, I have not had a hard drive go bad on me since I started the Spinrite thing 10 years ago (I still have an 8 GB hdd in my desktop that is working!!).
Any decent update(r)-script will do this for you.
Sent from my Infuse 4G
littlewierdo said:
Very nice infos. Deserves a sticky, although, probably in a different thread.
Some information on what "Master Clear" in Odin would also be helpful - I have never trusted my phone to 'truly' clear everything on the phone, I have found the Odin Master Clear option to be much more complete.
It is a bit odd, I do this with my PC every six months, I back everything up and format the drive and start over again (after running Spinrite on all the drives) - I do this on / around New Years and again over 4th of July weekend and I decided this past weekend to also do the same with my smart phones (4 Cappies) and tablets (Ipad and 2 Android tabs) this past weekend.
It gives me that sort of squeaky clean feeling and seems to make my devices run smoother. Maybe its all in my head, dunno *shrugs*.
One thing I can say however, I have not had a hard drive go bad on me since I started the Spinrite thing 10 years ago (I still have an 8 GB hdd in my desktop that is working!!).
Click to expand...
Click to collapse
I can run some tests on Odin's master clear to confirm what it does. Initially I would believe it does the same as a "wipe data / factory reset", but testing should let us know for sure. I'll test it this weekend. Maybe sooner.
Awesome to hear that I'm not the only advocate for SpinRite and I still use it a lot though not every 6 months like you do. It's definitely worth having and using.
MikeyMike01 said:
Any decent update(r)-script will do this for you.
Sent from my Infuse 4G
Click to expand...
Click to collapse
I totally 100% agree with you, MikeyMike01. Unfortunately, not all update scripts are created equally Asides from teaching people how to script themselves or parse through it, a task I do not have the time or patience to tackle, this it probably the easiest and best way to have users try to avoid the many and strange issues posted that possibly / most likely could've been avoided by using the tools at their disposal.
On a side note... I didn't notice you got yourself an Infuse 4G. Congrats! How do you like it? I've been out of contract for almost a year now and wouldn't mind upgrading (my wife is in contract), but I haven't seen anything really worth upgrading to or that does something I really need/want that the Captivate cannot, atm. I haven't looked up any specs and reviews on the Infuse yet tho.
Hi guys.
Samsung Galaxy Ace, Android 2.3.6, rooted, with several system apps uninstalled successfully using Titanium Backup.
2gb sdcard is about 3/4 full. It is only now that I'm considering making a 2nd partition.
1. If I copy EVERYTHING in the sdcard to my laptop, then create the 2nd partition, and copied everything back to the 2nd partition, will everything (i.e. my installed apps) still run smoothly as before? Or do I have to re-install everything?
2. Link2sd is compatible with stock ROM, correct?
3. If I use link2sd, are the 'links' copied to the first partition or second?
4. I don't plan on upgrading the size of my sdcard (2gb) since I'm not a heavy gamer, I have only 10 casual games, biggest of which is about 8mb, and about 10+ other small apps. The only thing that takes a big chunk of space is the map for the Sygic navigation app. So how big should each partition be (how big for 1st partition and how big for 2nd partition) for someone like me?
5. I don't plan on using custom ROMs, so is FAT32 the ideal format for me?
6. Is it necessary to flash clockworkmod Recovery?
7. If everything is working ok with link2sd, can I flash the stock recovery back?
Thanks guys!!!
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
Ok, I have two Devices a t959 and a t959v. I have brought them both up to android 4.x.x with the appropriate files for the device. Somehow the T959 repartitioned the amount of system RAM from 500Mb to 1.5Gb while the t959v is still at 500mb. On the t959 I flashed to stock, using the Samsung Vibrant Root tools. (T959UVJFD)
then the update.zip recovery from 03.11.2102. then to cm-7.2.0-vibrantmtd and then to Xperia Vibrantmtd 4.2.2. I didn't notice the repartition until I ran out of space installing the same apps that were on the t959 and then compared the two phones under settings/apps. the t959v says 410Mb used and 117Mb free. the t959 says 373mb used and a whopping 1.1Gb free.
I looked at the log for the Xperia update and came across this: "Creating file system with parameters: Size: 1589624832 This would indicate that the partitioning happened during that update.
My upgrade path on the t959v was Oneclick Stock restore, then bhundven-blastoff-v2.5. then CM 11-20140908-UNOFFICIAL-galaxys4gmtd.
I didn't see anything similar during the update in the t959v.
So my dumb question is: Is there a way to have a similar memory partition on the t959v?
It seems to be that having the larger system partition goes a long way to making the phone really useable since after about 9 apps the normal system partition fills up. Is there a downside to having the larger system partition?
thewizardofahhs said:
Ok, I have two Devices a t959 and a t959v. I have brought them both up to android 4.x.x with the appropriate files for the device. Somehow the T959 repartitioned the amount of system RAM from 500Mb to 1.5Gb while the t959v is still at 500mb. On the t959 I flashed to stock, using the Samsung Vibrant Root tools. (T959UVJFD)
then the update.zip recovery from 03.11.2102. then to cm-7.2.0-vibrantmtd and then to Xperia Vibrantmtd 4.2.2. I didn't notice the repartition until I ran out of space installing the same apps that were on the t959 and then compared the two phones under settings/apps. the t959v says 410Mb used and 117Mb free. the t959 says 373mb used and a whopping 1.1Gb free.
I looked at the log for the Xperia update and came across this: "Creating file system with parameters: Size: 1589624832 This would indicate that the partitioning happened during that update.
My upgrade path on the t959v was Oneclick Stock restore, then bhundven-blastoff-v2.5. then CM 11-20140908-UNOFFICIAL-galaxys4gmtd.
I didn't see anything similar during the update in the t959v.
So my dumb question is: Is there a way to have a similar memory partition on the t959v?
It seems to be that having the larger system partition goes a long way to making the phone really useable since after about 9 apps the normal system partition fills up. Is there a downside to having the larger system partition?
Click to expand...
Click to collapse
First off, welcome to the forums!
By "system RAM", I'm assuming that you mean data storage for apps. There are typically three main partition to worry about: the system partition which contains all the preinstalled apps and the OS (Android), the data partition which stores all user installed apps and data, and the sdcard partition (optional) which stores music, videos, pictures etc. The RAM is used by the phone as a place to hold the data that is currently being used.
The TL,DR version is this: The T959 has 16gb of storage, the T959V has only 1GB. Read on for more info...
One of the key differences (to the end user) of the T959 and the T959V is that the T959 has an internal SD card while the T959V does not. So for the T959, there is 16GB of space, some of which is used for the data, some for the system, and the rest for the sdcard partition. On the other hand, the T959V just has a larger oneNand partition than the T959. On the T959, it stores the recovery, boot, and efs partitions (which are not really important for the end user, just that they work ) So on the T959V, it has a larger one (about 1GB) that stores the data and system partition in addition to the recovery, boot, etc partitions. The sdcard partition is used when you insert a microSD card into the phone. On the T959, when you insert an microSD card it is used as yet another partition that the T959V doesn't have.
Note that this is a bit of a simplification.
It is possible to have more space on the data partition to install apps, but then you have to move the data partition to the microSD card. This is slower but definitely possible.
Hope this helps.