First and foremost...hello to you all my fellow dream users. This is officially my first thread I've ever created as a member on xda. Yet I am far from a noob. I've been around for quite some time, even before becoming a member. Needless to say, I wanted to share a common thought with you all.
Lets face it, we all are not perfect. 50% of us or more dont make up our bed right away as soon as we wake up out of it. Hell, Im sure a lot of us dont seperate our laundry as we produce it not just as we wash it. Throughout the long hard work week for some of us, (especially those with kids, have two myself), we just dont always find the time to pick up here and there as we would like to, or wash the dishes as we use them instead of letting a sink pile up first. But im sure, if there is any ounce of humane sanity and hygiene in your body, eventually you'll get around to it right? Right.
So getting to the point...must it be a written rule that you only wipe your cache, ext, etc. right before flashing a rom? I dont think so. Your phone is always something you have time for, even if its just 5 min out of a smoke break at work. So you are always using it. So it should be pretty piled up. Would it kill you to turn off your G1 one or two nights out of the week right before bed, boot into recovery, wipe your dalvik, wipe your ext, repair your ext, fix your permissions, reboot it and let that puppy charge for another long day of use tomorrow?. I should say so. It wouldn't hurt. Now as far as wiping data, I dont know, thats too much. But I personally found that if you randomly wipe your system clean(other than data) once or twice a week or every other day, when comes time to flash that new awesome rom you've been impatiently waiting for the dev to post, you will be able to do so with no wipe at all. And more than likely, you wont have any problems with it, atleast none on your behalf. Just a thought...... why wouldn't you? hmmmm
wiping
I like wiping my card but i had a few questions. When wiping your ext. I believe your wiping a portion of your sd card and i think it may ware out your card.(not sure) i probably flash about 6 to 10 roms a week. Can i overflash my G1? Or wipe it out from wiping it so much?
antonio91282 said:
I like wiping my card but i had a few questions. When wiping your ext. I believe your wiping a portion of your sd card and i think it may ware out your card.(not sure) i probably flash about 6 to 10 roms a week. Can i overflash my G1? Or wipe it out from wiping it so much?
Click to expand...
Click to collapse
How many times can you wipe a baby's ass before it stops working? Exactly. Wipe away my friend. Just remember ALWAYS BACKUP before wiping. Its like wearing your seatbelt, for safety. You can not ruin your card for wiping, if anything that'll help it. That is...for a good quality card as far as I know....maybe there are some cheap under market sd cards that cant take the hard use, but I recommend not buying cheap stuff
I think you don't understand what wiping does. Give me a minute, I'm at work, and I'll explain.
jubeh said:
I think you don't understand what wiping does. Give me a minute, I'm at work, and I'll explain.
Click to expand...
Click to collapse
take your time...as Im am awaiting to be enlightened. Wipe means to erase-delete-remove-vanish-clean-destroy......if you got any more definition do feel free to post em
Klyentel said:
take your time...as Im am awaiting to be enlightened. Wipe means to erase-delete-remove-vanish-clean-destroy......if you got any more definition do feel free to post em
Click to expand...
Click to collapse
But the matter is; what is it that's being erased-deleted-removed-vanished-cleaned-destroyed?
Wiping, as it currently works on Amon-RA's recovery, which I'm almost sure is the one you're using, erases these directories/partitions:
-Wipe data/factory reset: formats the /data and /cache mounts on the nand (internal memory), that means, the mount is erased and re-checked for errors and the blocks re-numbered to account for missing blocks, but this is already fixed by ext3-4 on the fly. /data holds your personalization information, saved messages, downloaded apps, phone numbers, basically, everything that means you've settled into your phone. Erase this alone, and your phone is in the same state as if it was the first time you turned it on (it'll even prompt you to sign to your google account).
/cache is used less, it only stores Browser cache and OTA updates, so this one is safe to erase, but offers no benefit (maybe only in browsing).
-Wipe Dalvik-cache: for any apk or jar in your phone that doesn't have an odex, a classes.dex file is created in /data/dalvik-cache. This file is not mutated at all during it's life in /dalvik-cache, it's not written-to, only read. It won't change, so it's not like the file will eventually get bloated.
What does happen is that if you have a lot of programs, the size of dalvik-cache will grow, but unless you uninstall the programs, there's nothing you can do about it, the file MUST be there.
-Wipe SD:ext partition: the SD:ext partition is really mmcblk0p2, and it's a symbolic link of your phone's /data/app, /data/app-private, /data/lost+found, and /data/dalvik-cache. The a2sd script moves the files from your phone's internal memory to the sd's ext partition as a means to save space in /data, but mostly so that you have more space for your apps and data (you decide the size of your symlinked space). Erasing your ext partition has the same penalty as erasing /data, again, because it's the same partition that was moved outside for larger space. Wiping it erases your downloaded apps (which you'll have to re-download), lost+found files (hardly any, really), and also wipes your dalvik-cache, which will be recreated upon boot anyway.
-Fix permissions: This one makes sense, but only after flashing a rom. Here's the thinking. Some "devs" have no idea what they're doing with their update-scripts and end up changing the permissions on several apps, which results in uid mismatches and ultimately prevents apps, or even the whole rom from starting.
Here's the kicker, the only time permission changes happen is when flashing a rom or an upgrade.
Changing permissions is not in the normal behavior of the rom, so, if you do run it, you're basically wasting your time because it has no effect whatsoever.
-Repair ext: I'll give you this one, as this one does make sense, mostly if your ext partition is ext2. Ext3 and Ext4 are journaled systems, so they do routine checks on themselves. Repair ext is an added check that doesn't hurt (because flash and nand cells do go bad every now and then), but doing it every week is overkill (unless you flash more than once per day). I'd say once a month or two is fine.
I think the real fault in your thinking (and I'm not only saying you) is that you guys are still thinking of nand and flash in terms of mechanical storage (hdd, cd, etc).
With memory, there's no seek time (except as defined by the system or medium bus), and there's no positioning of the reading head, or file fragmentation (well files do get fragmented, but it's inconsequential).
All your solutions make sense if you're running a computer with a physical, mechanical drive, but on a flash/nand/electric drive they're useless, and, in fact, the unnecessary writes lower the life of the drive itself.
The one true culprit in the decrease of performance in a rom that has been lived-in is usage. As you start getting comfortable, you start downloading apps, and a lot of those apps have listeners, and those listeners run all the time. Widgets are also memory hogs as they have to be persistent.
The only solution is more meory.
Wipe-now, and don't wipe later doesn't make much sense, if you think about it, because you're suggesting wiping once a week as opposed to wiping once when changing roms, which is a lot less frequent.
Wow....thank you. I mean really...thank you. I did not know half the stuff you just posted.
Thats very interesting, although it was only thoughtful thinking, I dont actually wipe that many times, but its just that i get tired of reading all these post of people having problems after flashing a perfectly good rom, all because their ext is corrupted or they didn't wipe like prompted or something. I figure if I can get people to think of ways to keep their phones running perfectly fine consistently as opposed to flashing so many times they dont even remember what stable really means, then it will post a lot less questions on the forum. Thats all.
but dude you're really smart, you must be a dev. Thanx for your time.
jubeh said:
But the matter is; what is it that's being erased-deleted-removed-vanished-cleaned-destroyed?
Wiping, as it currently works on Amon-RA's recovery, which I'm almost sure is the one you're using, erases these directories/partitions:
-Wipe data/factory reset: formats the /data and /cache mounts on the nand (internal memory), that means, the mount is erased and re-checked for errors and the blocks re-numbered to account for missing blocks, but this is already fixed by ext3-4 on the fly. /data holds your personalization information, saved messages, downloaded apps, phone numbers, basically, everything that means you've settled into your phone. Erase this alone, and your phone is in the same state as if it was the first time you turned it on (it'll even prompt you to sign to your google account).
/cache is used less, it only stores Browser cache and OTA updates, so this one is safe to erase, but offers no benefit (maybe only in browsing).
-Wipe Dalvik-cache: for any apk or jar in your phone that doesn't have an odex, a classes.dex file is created in /data/dalvik-cache. This file is not mutated at all during it's life in /dalvik-cache, it's not written-to, only read. It won't change, so it's not like the file will eventually get bloated.
What does happen is that if you have a lot of programs, the size of dalvik-cache will grow, but unless you uninstall the programs, there's nothing you can do about it, the file MUST be there.
-Wipe SD:ext partition: the SD:ext partition is really mmcblk0p2, and it's a symbolic link of your phone's /data/app, /data/app-private, /data/lost+found, and /data/dalvik-cache. The a2sd script moves the files from your phone's internal memory to the sd's ext partition as a means to save space in /data, but mostly so that you have more space for your apps and data (you decide the size of your symlinked space). Erasing your ext partition has the same penalty as erasing /data, again, because it's the same partition that was moved outside for larger space. Wiping it erases your downloaded apps (which you'll have to re-download), lost+found files (hardly any, really), and also wipes your dalvik-cache, which will be recreated upon boot anyway.
-Fix permissions: This one makes sense, but only after flashing a rom. Here's the thinking. Some "devs" have no idea what they're doing with their update-scripts and end up changing the permissions on several apps, which results in uid mismatches and ultimately prevents apps, or even the whole rom from starting.
Here's the kicker, the only time permission changes happen is when flashing a rom or an upgrade.
Changing permissions is not in the normal behavior of the rom, so, if you do run it, you're basically wasting your time because it has no effect whatsoever.
-Repair ext: I'll give you this one, as this one does make sense, mostly if your ext partition is ext2. Ext3 and Ext4 are journaled systems, so they do routine checks on themselves. Repair ext is an added check that doesn't hurt (because flash and nand cells do go bad every now and then), but doing it every week is overkill (unless you flash more than once per day). I'd say once a month or two is fine.
I think the real fault in your thinking (and I'm not only saying you) is that you guys are still thinking of nand and flash in terms of mechanical storage (hdd, cd, etc).
With memory, there's no seek time (except as defined by the system or medium bus), and there's no positioning of the reading head, or file fragmentation (well files do get fragmented, but it's inconsequential).
All your solutions make sense if you're running a computer with a physical, mechanical drive, but on a flash/nand/electric drive they're useless, and, in fact, the unnecessary writes lower the life of the drive itself.
The one true culprit in the decrease of performance in a rom that has been lived-in is usage. As you start getting comfortable, you start downloading apps, and a lot of those apps have listeners, and those listeners run all the time. Widgets are also memory hogs as they have to be persistent.
The only solution is more meory.
Wipe-now, and don't wipe later doesn't make much sense, if you think about it, because you're suggesting wiping once a week as opposed to wiping once when changing roms, which is a lot less frequent.
Click to expand...
Click to collapse
:O
I'm voting to make this to be post of the month. Great info.
jubeh said:
But the matter is; what is it that's being erased-deleted-removed-vanished-cleaned-destroyed?...
Click to expand...
Click to collapse
Honestly, one of the best posts I have ever seen here. Kudos to you for taking the time to spell that all out.
I've been using my ADP1 since December 2008. In the time I have owned it and used it DAILY, and HEAVILY, I have NOT ONCE wiped it.
NEVER.
It is snappy and fast.
I do keep it clean, but not by doing anything drastic.
And this is despite several OS upgrades, trying out a few custom roms, apps2sd with a TON of apps installed, etc., etc., etc.
This is really really frustrating. I've rooted my phone, but no matter what ROM I use (except for the official ones), I get random crashes constantly. Sometimes it will be swype, other times Android, other times many many others.
I've tried about every ROM out there. Bittersweet, Aloysius, Darchdroid, etc. etc. What could the problem be? My phone runs fine on stock software! My SD partition is currently 512MB ext2 with the remainder (1.5GB) as FAT32. Could that be the problem? I'm running recovery image 1.6.2.
I'm just wondering if the custom ROMS install some of the software in places (SD card, etc.) that the officials ROMs do not and maybe since I'm not partitioned properly, I get crashing? I don't have a swap partition either.
Any ideas?!?
have you wiped everything befor flashing the roms?
You're probably doing something wrong when you flash. Make sure to wipe your data.
Could also be apps you have installed, remember, Android multi-tasks, so an app can cause a crash when it isn't in the forefront
Here's my process when I flash.
1. Copy the zip file to the SD card.
2. Turn off phone.
3. Press and hold HOME while turning phone on.
4. Wait for recovery menu and wipe Davlik and phone.
5. Go back and flash phone to the zip file on SD.
6. Reboot phone.
You don't have to format the SD every time do you? I just formatted it completely and created an EXT2 and FAT32 partition. Do I need a swap partition?
I'm just really at a loss. I'm so tired of trying ROMs...but they all crash. Am I missing something in the process? How does everyone else do it?
Is there a quick way to (re)install all my apps after changing ROMs?
Been using Pongster's awesome NAND HyperDroid build since v5 and have been upgrading along the way by reinstalling the data section from my CWM backup. Recently on v11 I started having a few glitches and upgrading to v12 only made matters much worse. I just want to start a fresh on v12, but is there a way quicker than writing down all my apps then selecting each from the market. Have looked in Android Market on using desktop PC and it only lists 11 apps. Thanks.
SheenaIsAPunkRocker said:
Is there a quick way to (re)install all my apps after changing ROMs?
Click to expand...
Click to collapse
I believe Titanium Backup Pro is the most popular choice, it can restore all your apps and data automatically, plus there's an option to repair missing market links.
That rom uses an ext partition, so as well as restoring the data partition after a fresh flash, if you also restore the sd-ext partition (same method), all your installed apps will be restored, complete with all their settings still in place, since you are restoring data too.
D'oh, and double d'oh. Thanks for the tips. I backed everything up using Titanium backup. Being running HyperDroid without an EXT partition so while I was in the process of installing v12 again, I thought I'd use the handy partition function in ClockworkMod. However, what it fails to mention is in re-partition my SD Card for me it would handily wipe everything Looks like I'm hosed now anyway!
nooOO!, hah, oh well, it happens, and theres no better learning curve than seeing mistakes in action.
I literally had the SD card in my desktop to copy everything on it, but before I did, I put the SD back into the phone to do something else ... never got around to doing that copy. At least phone numbers are backed up on Google (I hope!), but I guess I'll have to start again on Tower Raiders 2, that's the real loss!!
since you are at a fresh start, you COULD try reinstalling all the apps, and THEN restore the data partition, which (unless im wrong) holds settings? ,,though i know some stuff uses folders on the fat32 part of the sd card too, , so may not work, , worth a try if you're in an investigative frame of mind.
Can anyone explain to me why when I have a 1Gb Ext4 partition on my SD card with only 367Mb used I am getting Low Storage warning when restoring my apps (143 of them) through Titanium Backup onto a clean HardDroid2 CM7 build with A2SD flashed and confirmed working? When I check it states 199Mb used, 13Mb free but when I use Root Explorer to look into SD-Ext I have App, Private App, Data, Dalvik, etc and all of the app APKs appear to be in there. Am I missing something here? I had the same issue for the first time a couple of days ago when I reflashed Hyperdroid - never had it before, and always do full Task29/fresh MAGLDR/fresh CWM/CWM wipe wipe wipe/etc for each new ROM so SD Ext is always reformatted too. It's driving me nuts
when you install an app, the size of that app gets knocked off the available space, but gets restored when you reboot, so try installing a few, check eth remaining space, then reboot, see if the reported space changes. (Ive never tested it myself, just repeating something i read)_
..also using app2sd and my phone mem seems to decrease also.
When i look into /data and /sdext i see in both the app folder with all apps installed.
but the used space seems to be bigger on the sd-ext.
...when you install e.g. Angry birds with 20 mb you will notice that your internal storage will NOT decrease to that amount: thats the reason why the data folder is smaller than the sd ext.
Seems so that parts of the apps are stored on the phone mem although we ve got app2sd with an sd ext.
Once i tried to delete that data folder, but then all apps stopped working.
In twyeens rom you can move your apps to sd, there was a fix some months ago, so that all apps runs fine from it also e.g. angry birds.
Sent from my HTC HD2 using XDA Premium App
Hello fellow xda- users & developers,
This is the first time Post on the forum since I really didn't find the need to.
I own an HD2 and it's been through quite a few roms (mostly CM7). Not too long ago I flashed the Medroid ICS CM9 remix(task9 fresh install on every flash) and it was really smooth, but it had random reboots and not a fully developed camcorder. So until yesterday I flashed the MIUI HSTR SGSII v4.0 which is by far the most elegant rom but as all there had to be a flaw. As i was installing my desired apps and after a dozen apps I got the "insufficient storage available". I had this problem with a few past roms but i would flash a new one. The ICS rom didn't have this problem. I also have 669MB Internal memory, 7.09GB SD Card.
I have tried fresh intalling it, clearing cache, wipe/factory reset. I have search the forum, and used the knowledge of the users but nothing seems to solve this problem.
I would much appreciate if there are suggestions to solving this problem out there.
Much thanks in advance cheers.
I'm facing the same problem. Everything was perfect but suddenly for last few days when I try to install some apps it says Insufficient storage and whenever I try to update any apps from Google Play it says Insufficient storage.
NAND ROM : [NIGHTLY][Full HWA] CyanogenMod 9 [4.0.4][Kernel: cmhtcleo/tytung]
8GB SD Card with 2GB ext4 partition.
simple2ext app showing following information:
DATA:
Size: 218MB
Used: 103MB
Free: 115MB
SD-EXT:
Size: 1922MB
Used: 190MB
Free: 1731MB
Cache:
Size: 2MB
Used: 784KB
Free: 1MB
Any suggestion please ?
I wonder how he got 669mb of Internal memory. I'm jealous!
669 MB ? is it possible? I don't think so. But if he said it an be. See if you guys know how to repartition MGDLR then you can make the partition of 150 MB. For ICS or CM7 roms 150 is well enough. and then you can have enough memory.
You can also use APPs to SD to have more memory.
try using cache clearing apps to clear the cache so that u can have extra memory.
Hey guys,
I see the same error message with running 'MccM MixTheme V1.3 HTC Sense.Iphone.ICS.Latest Miui Base'. However the worst part is that the issue appears as soon as I try to install my first app on the phone, so I can't do anything besides use what comes with the stock. Oddly enough, just 1 other fellow member faced this issue (and reported it in the DEV thread), however no one posted a solution to it. BTW I've installed the ROM 3 times with the same observations.
Could someone care to help with this please?
I have solved my problem. I faced that problem because I changed the setting last week, I set the app data to be saved in SD-EXT. I set the app data to be saved in phone storage last night and rebooted my HD2, problem solved. I have updated all the apps which were showing errors
Sent from my HTC HD2 using xda app-developers app
had the same issue. All I did was clear cache via Recovery and the problem is now gone
I just backed up all my data, and wipe data/factory reset.. Solve the problem.