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.
I have not installed any apps to my phones internel memory. I use titanium to move all apps except for keyboad, live wallpapers, widgets to the phone sdcard. 2 days ago I had 213mb of internel memory, now I am at 103mb of internel mrmory and I have no idea why. I tried deleting dalvik cache (dont think there is a way to move dalvik to sdcard with stock rom/kernel) and it didnt change much. Does anyone have any ideas where the memory leak is or what apps that even though are installed to the sdcard may be using up internel memory? Thank you
Saw the Dalvik2Cache.zip and that didnt do much, then saw the Dalvik_Hack under page 3 of the same thread and that seems to have made a lot more internel memory, I will keep an eye out on it and see if this is just a temporary fix or maybe its a permanent fix. It may just have been all the dalvik cache taking up space but over 100mb in 2-3 days seems like a lot of cache.
Here is the thread I followed, post # 24 by FrAsErTaG with the "CONFIRMED WORKING: http://www.mediafire.com/?3yfj8t8ld5yjez9
jgregoryj1 said:
I have not installed any apps to my phones internel memory. I use titanium to move all apps except for keyboad, live wallpapers, widgets to the phone sdcard. 2 days ago I had 213mb of internel memory, now I am at 103mb of internel mrmory and I have no idea why. I tried deleting dalvik cache (dont think there is a way to move dalvik to sdcard with stock rom/kernel) and it didnt change much. Does anyone have any ideas where the memory leak is or what apps that even though are installed to the sdcard may be using up internel memory? Thank you
Saw the Dalvik2Cache.zip and that didnt do much, then saw the Dalvik_Hack under page 3 of the same thread and that seems to have made a lot more internel memory, I will keep an eye out on it and see if this is just a temporary fix or maybe its a permanent fix. It may just have been all the dalvik cache taking up space but over 100mb in 2-3 days seems like a lot of cache.
Here is the thread I followed, post # 24 by FrAsErTaG with the "CONFIRMED WORKING: http://www.mediafire.com/?3yfj8t8ld5yjez9
Click to expand...
Click to collapse
It will most probably be the dalvik cache, .dex files can be anything up to 1-2mb+ for each app. IMO dalvik2cache is a bad idea, on the latest FW the /cache partition has been reduced to 100mb, fill that up and you will be unable to download from the market. You should try link2sd, it will work on any rooted phone with stock kernel. (as long as you make the 2nd partition fat.) And it will move the app, library and .dex files to your 2nd partition and it will mount the 2nd patition on boot so keyboards/widgets are unaffected. I have 350+ apps installed on my phone and thanks to link2sd i still have 235mb free and phone is fast as hell
Thats cool. My old phone I had the sdcard partitioned with an EXT3, I would love to do that with this phone but dont think its supported yet. I may be wrong but I have not found anything like that for the Verizon R800x. Do you know if there is a way to remove the dalvik2cache hack if I wanted to revert it back to internel memory?
jgregoryj1 said:
Thats cool. My old phone I had the sdcard partitioned with an EXT3, I would love to do that with this phone but dont think its supported yet. I may be wrong but I have not found anything like that for the Verizon R800x. Do you know if there is a way to remove the dalvik2cache hack if I wanted to revert it back to internel memory?
Click to expand...
Click to collapse
It will work on any android as long as your rooted. You need to make the 2nd partition fat though not ext2/3/4 as fat has native support so no custom kernel is needed. It calls to install-recovey.sh not init.d too so you can use stock kernel To remove dalvik2cache, unzip the zip you flashed look at the files in the .zip and delete the corresponding ones on your device
Thank you, I will do that, look through the .zip and delete the files. I already downloaded and installed the Link2sd. I am all about getting more memory out of the pathetic 400mb SE put in place, don't know why the hell they didnt just give us at least 2gb. But whatever still love the phone even with the limitation. Anyway what I ws going to say was I all for gaining memory ut not ifi ts going to make my phone crash some time down the road.
Since lot of users are having problems with bootloops after wiping data I think we need to find a solution.As I read it happens because the data partition has changed after installing aio mod(I would like to note that I am one of the users that face bootloops and I have installed aio mod in the past)
I was thinking if we could change the data partition size to the original again or something like that.Any ideas are welcomed..! :fingers-crossed:
Great idea I can help testing
My only other gripe at the moment is the clock not working on custom roms, non from the market work either. Sounds are non-existent
I can't confirm, that it is related to aio-mod.
i tried different roms and never had problems with bootloops after wiping data (e.g. CM10.2 and JB one
It can't be the data partition size, we don't have any tool that can re-partition the data partition or any other. The AIO mod and some others haven't changed anything to the data partition, only some script that places some files in other location on the data partition. And those script are located on the system partition.
I don't know why you all have this, but some do some don't. like with the recovery's. some can format the system with the build in line in the updater-script, some can't. I think there are just some small differences between the phones. But i dunno what.
Does anyone know of a method to force the J5 phone to use the SD Card for cache files without rooting?
I've only had the phone a week and already internal memory is getting very low. I thought if cached data could automatically go onto the SD Card I would gain a bit of space. Having looked at the threads regarding rooting the J5 I think I want to take more time to understand the process rather than a leap in the dark.
Many thanks,
Anne
You can access your storage and execute clean cache to wipe out all these unwanted files in a few seconds. It is in the settings menu.
Cache; whether stored in your phone memory or SDcards would eventually eat-up your storage and eitherway, not a good thing IMHO.
Hello Anne, Rooting Your Galaxy J5 Is Quite Easier Than You Think, Provided You Have The Tools And Follow The Instructions. Try Using TWRP Recovery By @Nick Verse, Flashing Instructions Are Well Detailed On His Thread. I'm Sorry I Couldn't Provide The Links But You Can Search It. Good Luck
Hello guys! Cache partition is only 200MB on our device, so it is not the issue here. You must move your applications to SD, but you will experience some lags, due to I/O speed limitations.
Furthermore, if we move cache to SD, more lags will happen.
Can be used an init.d which clear cache automatically, or use Tasker app to clear cache whenever you want (I prefer Tasker).
#Henkate said:
Can be used an init.d which clear cache automatically, or use Tasker app to clear cache whenever you want (I prefer Tasker).
Click to expand...
Click to collapse
Why don't you simply wipe cache from recovery?
Nick Verse said:
Why don't you simply wipe cache from recovery?
Click to expand...
Click to collapse
It can be done with some terminal command, can't remember it right now, but can be found on Google. Is easier this way and isn't necessary to reboot the phone.
#Henkate said:
It can be done with some terminal command, can't remember it right now, but can be found on Google. Is easier this way and isn't necessary to reboot the phone.
Click to expand...
Click to collapse
Thanks for all your replies. I've been clearing cache and generally getting rid of junk but the internal memory was almost 95% used nonetheless. No programs were able to update and taking a photo meant having to delete another.
So bit the bullet and after more investigation rooted the phone today. Tomorrow I shall partition the sd card so that some of it (the majority) can act as internal memory. <rant>Don't understand why Android (Google) have such limitations in their op system. More and more apps are available and they get larger and larger so more and more memory is needed. Currently memory is as cheap as chips, so why limit how and where it is used?</rant>
Anne