Ok so I have a backup of my stock rom, the r2 with sense, and a villain Rom. I was going to just make a back up of every Rom I like so I could just recover to the one I want to use whenever I want to use it, with all my settings and stuff in order.... so my question is do backups take a lot of memory or space? Do I want to limit how many recovery backups I have?
Sent from my HTC Vision using XDA App
One Nandroid backup of Hero is taking about 300 - 400 MB on SD card. I can't check out the exact size at the moment. It makes a dump of NAND flash of your phone, excluding some areas. There is 512 MB of NAND flash memory on Hero. That is theoretical maximum size of backup. You can have as many backups as you like without any negative consequences. SD card size is the only limit.
Unless ofc you are doing ext updates too. That will start to eat much more space if you install a lot of apps to ext.
My backups usually end up at around 280mb. You have a good idea as long as your SD card is big.
Related
Everytime I flash a different rom more of phone storage space is taken away.
I am down to 677MB available out of 12.78GB total. Before I flashed the last rom I had almost 3GB available. I notice this everytime I flash a rom.
What do I do to reclaim the space? Is it Nandroid Backups that are taking all the space?
Any help would be appreciated.
Thanks.
If you're making nandroid backup before every rom update and not removing old nandroid backups then i would say that's what taking up space.
I have one backup that i fall back on to go back to mostly all stock and maybe 2nd one that ill fall back on for the more recent configuration. i dont keep more than 2 back ups at a time.
You can use a file manage and locate clockwork in your internal SD card and in the backup folder remove old back ups just keep what you need
I have a HTC Legend running on NewSense RC4. I have App2SD installed. I've changed the default install location to SD Card via " pm shell setInstallLocation 2". Though I've done all this, I have only around 2-3 MB space always. I're removed the data and cache for many apps. Yet, this is the situation. And I only have 52 APPS.
Please tell me another method to increase the amount of space. Please don't sugesst me to flash to another ROM.
I also read somewhere about partitions on SD card or something. Can you please enlighten me on this?
Note: I read to fast and COMPLETELY skipped the part where you said "Don't tell me to flash another rom" I am soooooo sorry!
The only other option I can give you is to flash Cyanogenmod7 and use data2ext if you want app space, but that is probably out of the question for you!
On the partitioning note:
Partitioning quite simply means splitting your microSD card into 2 or more PARTS (hintART-itioning). Often times, partitioning is used to create a separate space for apps2SD or data2ext. The simplest way to partition is to download rom manager (you must have root and be able to boot into recovery) and choose the option "partition sd card" choose 0 swap , then choose 512mb partitioning space! WARNING: this will delete EVERYTHING on your memory card, so either turn back, or backip tour mem. Card! After it is partitioned, you can proceed to add apps to the new partition of your SD card. Note this will, like I said, split your memory card space! Ex:
If you hav a 1 GB (1024 MB) Memory card, after partitioning, your memory for files will decrease to 512 mb, while 512 mb is reserved for your apps!
Just a word of advice from a fellow XDA-er!
I am not aware whether or not the HTC legend runs Cyanogenmod7 or not, but it would be well worth the flash to use it. Unless you are in love with the Sense UI (because CM7 uses 2.3.3 Gingerbread) then come on over to the Cyan side . Data2ext takes your ENTIRE data section of your phone (that part that holds the meat and bones of an app, PLUS the huge apk file) and puts it in that partition you created. Data2ext is simply a flashable script that puts that partition in action. After flashing the script via recovery, just go to your terminal emulator app on your phone and on the first line, type "su" (without quotes) and then type "data2ext --enable" (exactly as typed without quotes) and vuala, your REAL data section on your phone is literally virtually UNTOUCHED! Which makes your phone a lot faster. There is also a script that let's you choose the size of your partition (no more than 2 GB is strongly recommended) but I haven't used that script just yet, but will soon! Data2ext is WAY bettr than apps to SD! I know that I did way more than just answer your question, but I wanted to answer, plus give a better alternative should you choose to use it
Hope I answered ur question,
Ognimnella
Sent from my T-Mobile myTouch 3G Slide using XDA App
ognimnella said:
Note: I read to fast and COMPLETELY skipped the part where you said "Don't tell me to flash another rom" I am soooooo sorry!
The only other option I can give you is to flash Cyanogenmod7 and use data2ext if you want app space, but that is probably out of the question for you!
On the partitioning note:
Partitioning quite simply means splitting your microSD card into 2 or more PARTS (hintART-itioning). Often times, partitioning is used to create a separate space for apps2SD or data2ext. The simplest way to partition is to download rom manager (you must have root and be able to boot into recovery) and choose the option "partition sd card" choose 0 swap , then choose 512mb partitioning space! WARNING: this will delete EVERYTHING on your memory card, so either turn back, or backip tour mem. Card! After it is partitioned, you can proceed to add apps to the new partition of your SD card. Note this will, like I said, split your memory card space! Ex:
If you hav a 1 GB (1024 MB) Memory card, after partitioning, your memory for files will decrease to 512 mb, while 512 mb is reserved for your apps!
Just a word of advice from a fellow XDA-er!
I am not aware whether or not the HTC legend runs Cyanogenmod7 or not, but it would be well worth the flash to use it. Unless you are in love with the Sense UI (because CM7 uses 2.3.3 Gingerbread) then come on over to the Cyan side . Data2ext takes your ENTIRE data section of your phone (that part that holds the meat and bones of an app, PLUS the huge apk file) and puts it in that partition you created. Data2ext is simply a flashable script that puts that partition in action. After flashing the script via recovery, just go to your terminal emulator app on your phone and on the first line, type "su" (without quotes) and then type "data2ext --enable" (exactly as typed without quotes) and vuala, your REAL data section on your phone is literally virtually UNTOUCHED! Which makes your phone a lot faster. There is also a script that let's you choose the size of your partition (no more than 2 GB is strongly recommended) but I haven't used that script just yet, but will soon! Data2ext is WAY bettr than apps to SD! I know that I did way more than just answer your question, but I wanted to answer, plus give a better alternative should you choose to use it
Hope I answered ur question,
Ognimnella
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Yes, I read about the partitioning method. I've a few questions.
1. Will this method work on ANY ROM ?
2. Will I reclaim ALL my internal memory?
3. Is this is a sure shot method to install AS MANY apps as we need (the only condition being you that much SD card partition space) ?
4. Can you please link me to a detailed tutorial?
abhishek_turbo911 said:
Yes, I read about the partitioning method. I've a few questions.
1. Will this method work on ANY ROM ?
2. Will I reclaim ALL my internal memory?
3. Is this is a sure shot method to install AS MANY apps as we need (the only condition being you that much SD card partition space) ?
4. Can you please link me to a detailed tutorial?
Click to expand...
Click to collapse
1. Method will only work on rom that support it.
2. You will get a lot of internal memory back but data will remain internal unless you move app's data to sd-ext also.
3. Method trick the phone into thinking the sd-ext is part of your internal memory so you'll be able to install a good amount of apps.
4. Search Dark Tremor's a2sd or S2E in the market.
abhishek_turbo911 said:
Yes, I read about the partitioning method. I've a few questions.
1. Will this method work on ANY ROM ?
2. Will I reclaim ALL my internal memory?
3. Is this is a sure shot method to install AS MANY apps as we need (the only condition being you that much SD card partition space) ?
4. Can you please link me to a detailed tutorial?
Click to expand...
Click to collapse
1. No to my knowledge it only works on CM7 (and you said flashing a new rom is out of the question)
2. Yes, plus more
3. Yes, so far, I hav somewhere around 85 apps installed (and that's with 512 mb only, with 150-200mb still left
4. http://forum.xda-developers.com/showthread.php?t=902395
P.S. - If you want to have the freedom of installing up to 2GB partition space for apps, use data2ext-v4. If you want the already preset 512mb, then use data2ext-v7 (it is thoroughly explained in the post)
Sent from my T-Mobile myTouch 3G Slide using XDA App
Hoping someone can help me understand the implications of using the above methods of backup as it relates to device performance and restore.
First is a question about how Android memory works. I'm running Virtuous Unity 2.39 on an Inspire. According to TiBu my System ROM is 575MB with 40.4MB free, 1.21GB internal with 648 free. The system memory manager says I have 180MB of memory available. So, I'm not sure which memory is which. What's used for storage, and what's used for runtime of programs? Am I correct to assume that if I move programs from internal memory to storage that I'll be able to run more apps at any given time?
Here are my questions.
Will moving some (larger) apps like CoPilot (33MB), Documents2Go (11MB), SPB Wallet (12MB) and infrequently used utilities like SpeedTest benefit the handset performance in any real way, or am I over-thinking this?
If the answer to the above is 'yes', there is a performance gain, what happens when I do a Nandroid or TiBu backup in preparation for a ROM upgrade? I know that TiBu has the setting 'Restore backups to... Original Location' as one of the options. Does this mean I could theoretically restore apps to an entirely new (blank) card if need be?
Will using a utility like D2SD (if I partition my card with an EXT4 segment) likewise help in any substantial way?
How can I help organize the apps and data on the card so that it reduces 'clutter' and presents a more easily managed folder structure to find things that I need?
Thanks in advance for your help!
Anyone out there have thoughts on this?
The system ROM, is the memory used by the custom rom. It stores all the files the rom needs to run. The internal memory is the memory used for storage by all the apps, etc. you have. The 180mb you had free, is the RAM. You'll notice it'll be at different amounts (depending on how many things are running, and how resource consuming the are).
1. Yes, but only if your internal memory is very low (low enough to get the "low space" warning (or at least close to that).
2. No (not fully). Some may be restored fine but some would be corrupted.
3. Only if your device's internal memory (in total) is low.
4. Usually when you move an app to the SD card, they automatically organize themselves in one folder called ".android_secure"
Hope this clarifies some things for you .
Theonew said:
The 180mb you had free, is the RAM. You'll notice it'll be at different amounts (depending on how many things are running, and how resource consuming the are).
Click to expand...
Click to collapse
I appreciate your reply.
So, there wouldn't be any performance improvement if I were to free up more RAM or perhaps create an EXT4 partition on the SD card for system use?
BillTheCat said:
I appreciate your reply.
So, there wouldn't be any performance improvement if I were to free up more RAM or perhaps create an EXT4 partition on the SD card for system use?
Click to expand...
Click to collapse
Yes there will be a performance gain if you free up RAM but creating an EXT4 partition does not contribute to that. That partition will only be for storage.
I'm using Clockworkmod 6.0.1 to backup. Is this called nandroid backup ? So it backs up about 10-15mins and it's only 10mb size~?? I was backing up custom rom. I also have copy of my original rom wich is a bit more that 1GB tar file. But why now if only take 10mb with 15min backing time?
I was backing data on external sd card. Before backup it had 9gb free space, but after only 7gb. I went to folder where backup is "Computer\GT-I9300\Card\clockworkmod\backup\2012-08-26.18.42.40" and there is only 16.9 mb total of all the files instead of those 2 gb.
Also what give "free nandroid space" option. I did it and it fried about 2gb on internal memory.
Well, with clockworkmod 6 and up, the first nandroid is always big while future nandroids are incremental. Why? Well, it creates a blobs folder of around 2gb with everything, then folders for each rom which are about 10-20mb each. Every new ROM that's backed up only add what's not already there in the blobs file, i.e. it uses stuff from your previous nandroids if nothing new has been added to conserve space.
Instead of having 10 nandroids with all being 2gb, it now only takes a huge 2gb nandroid and only add what's new from newer nandroids.
Kinda hard to explain as I don't really know how to put it.
There are some issues still with this version of CWM. I'd stick with v 5 until they are worked out. They have to do with the way the internal and external SD structure is for the device and both the SII and SIII are effected by it. If you try to restore, it will probably fail.
Done it myself on my SII. I've since learned and stay with v 5 until 6 is solid, and that might be a while. The incremental update feature with blobs is nice, and I hope it works right. It's never worked right for me yet, however. Maybe things are fixed by now. I'm not sure.
Theshawty said:
Well, with clockworkmod 6 and up, the first nandroid is always big while future nandroids are incremental. Why? Well, it creates a blobs folder of around 2gb with everything, then folders for each rom which are about 10-20mb each. Every new ROM that's backed up only add what's not already there in the blobs file, i.e. it uses stuff from your previous nandroids if nothing new has been added to conserve space.
Instead of having 10 nandroids with all being 2gb, it now only takes a huge 2gb nandroid and only add what's new from newer nandroids.
Kinda hard to explain as I don't really know how to put it.
Click to expand...
Click to collapse
Wow... Very nice space saver, but i will revert to v5 now. Thanks!
Pickepys said:
Wow... Very nice space saver, but i will revert to v5 now. Thanks!
Click to expand...
Click to collapse
It sure is, and would be great if it CWM6 actually worked on our phones.
Theshawty said:
It sure is, and would be great if it CWM6 actually worked on our phones.
Click to expand...
Click to collapse
One more thing. I just deleted backup folder on external sd card wich was about 1gb with blobs folder (wich was just few kilobaits) and gained 3gb of space back. How i can view those HIDDEN FILES throught pc i always wondered.
Pickepys said:
One more thing. I just deleted backup folder on external sd card wich was about 1gb with blobs folder (wich was just few kilobaits) and gained 3gb of space back. How i can view those HIDDEN FILES throught pc i always wondered.
Click to expand...
Click to collapse
No idea. Not too familiar with CWN6. I've only used it very briefly.
donalgodon said:
There are some issues still with this version of CWM. I'd stick with v 5 until they are worked out. They have to do with the way the internal and external SD structure is for the device and both the SII and SIII are effected by it. If you try to restore, it will probably fail.
Done it myself on my SII. I've since learned and stay with v 5 until 6 is solid, and that might be a while. The incremental update feature with blobs is nice, and I hope it works right. It's never worked right for me yet, however. Maybe things are fixed by now. I'm not sure.
Click to expand...
Click to collapse
I've had a couple of hiccups since v6 too. The backups have failed on me and I think it's since I moved the files (backup. and BLOBS) to a different location (ext sd or pc) prior to doing a full system wipe.
Gutted that I lost stuff as a result because I'd used it successfully lots of times and trusted it to work.
Sent from my GT-I9300 using xda app-developers app
I'm trying to create an image of my device, but the memory of the device is way more than half full.
Since ClockWorkMod is trying to backup to the DEVICE memory, and not the SD card memory, it obviously doesn't have enough room to do so.
How can I change the location of where it does the backup?
I'm using ClockWorkMod recovery v4.0.1.5 with CF root, and I'm quite a newbie when it comes to ROM changing and everything, never done that.
Thanks
In the backup/restore settings in CWRecovery, you should have the option to backup to internal/external storage. Choose external if you don't have enough space in internal.
MistahBungle said:
In the backup/restore settings in CWRecovery, you should have the option to backup to internal/external storage. Choose external if you don't have enough space in internal.
Click to expand...
Click to collapse
I do not see any "settings" in the backup/restore.
Also - I cleared about 700MB from my device memory, leaving it with 10GB used space and 2GB free, and it seems like it did a backup which its size is about 2GB leaving me with about 100 free MB. How does it make sense? doesn't it backup the data like images and videos?
Will still prefer to try and backup to SD.
Thanks
CWM will make an 'image' of the phone at the time you make the backup minus the modem & external SD card (if you have one). If you have photos/videos/whatever stored in the usual place on the internal storage these will be backed up. That backup size is normal.
Do you have an external/separate SD card, or are you talking about the two separate parts of the internal storage; you have the part that's used by the 'system'; & the 'userspace' which is normally referred to as 'sdcard' ? If you are using an external/separate SD card, there's definitely an option in the backup & restore settings to backup to external SD card (I'm looking at that menu right now).
I have a feeling the version of CWM you're using may have something to do with you not having these options; 4x is ancient, I don't even remember what options are in the menus of that; we're now using 6x.
Perhaps you might want to use a kernel that has a more recent version of CWM if that's the case & it's not allowing you do what you want ?
MistahBungle said:
CWM will make an 'image' of the phone at the time you make the backup minus the modem & external SD card (if you have one). If you have photos/videos/whatever stored in the usual place on the internal storage these will be backed up. That backup size is normal.
Do you have an external/separate SD card, or are you talking about the two separate parts of the internal storage; you have the part that's used by the 'system'; & the 'userspace' which is normally referred to as 'sdcard' ? If you are using an external/separate SD card, there's definitely an option in the backup & restore settings to backup to external SD card (I'm looking at that menu right now).
I have a feeling the version of CWM you're using may have something to do with you not having these options; 4x is ancient, I don't even remember what options are in the menus of that; we're now using 6x.
Perhaps you might want to use a kernel that has a more recent version of CWM if that's the case & it's not allowing you do what you want ?
Click to expand...
Click to collapse
I did mean the external storage, yes.
I tried to update to 6x but it stayed the same version.
Anyway, if you're sure it makes sense that 10GB became 2GB after backup, then I'll trust that and will use the backup it created in the internal storage.
What I meant was, you said the backup size was ~2GB; that is indeed normal. If you attempt to update CWM independently of the kernel, you will revert to whatever version is baked into the kernel when you next reboot. If you want to update to a permanent later version of CWM, you'll need to flash a kernel that has said version of CWM.
if you're on PhilZ kernel, you can choose to compress the backup file. (low, medium or high compression)
You can also get a smaller file size, by uninstalling apps you certainly dont need. You can clear off cache files.
For cleanup i recommend Clean Master - search playstore