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.
Related
I've been having this problem on and off for a while, mostly I believed it was related to something getting corrupted when I restored my apps to a new Rom with Titanium Backup.
I am happy to say, that after scouring the web for days, and trying a lot of wrong information, I finally figured out how to fix this.
It's real easy. All you need to do is remove any *.apk files located in the /cache directory on your phone (did not even need to remount- though I did it as root just in case).
I never did figure out why only some apps will have this problem or how the problem first comes about, but I have successfully done this twice and have since been able to install/update files that had this error before.
Update (3/3/11): OK - After scouring the Internet for over a month I finally figured it out. My info above was only part right. The problem is specifically with ROMs/Kernels that move the dalvik-cache to the /cache directory (HTC puts it in the /data dir).
In any case, when it's in /data, it is using app space, and therefore you usually run out of app space and know about it. However, because this is in /cache, you don't really know what you are using. As you load up on apps, your dalvik-cache grows, and since these apps need the .dex files in the cache, even if you clear your cache, it will just get re-created.
the /cache dir is also where the apps are temporarily stored while downloading from the market. So....
1. If you are getting immediate download fails, that means that your cache is so full that you don't even have space for the temp file.
2. If you get "Invalid Package" that likely means that there was not enough cache left to install the .dex files (the download is also taking up some of this space).
Unfortunately, the only way to fix this is to either remove some of your apps, or move your cache to your SD card.
HOWEVER, I found this great app on the market called Link2SD, that allows you to only move select apps to the SD card, and you can also move the dalvik-cache files associated with these apps.
see this thread for specifics: http://forum.xda-developers.com/showpost.php?p=10711328&postcount=1
it lets you select which apps to move. You will need to create a new partition on your card, though.
So far results have been great and I can finally update the 30+ apps that have been stuck for me for the last 2 months.
almost forgot, if you adb shell or use terminal emulator, you can type "df" to see how much space is left on all your mounts.
My phone has been doing the same thing with the whole package file is invalid bs. I tried to follow your instructions on going to the /cache folder. When I went to the folder, it was empty, so I wasn't able to remove any .apk files. So now what? How do I fix this?
If you use a File Managemet app like ASTRO, it will show the folder as empty because you need root access to see the dir. However, if you use Terminal Emulator or adb shell (as root) you will see that there are indeed other directories, and probably these orphaned .apk files.
Hi,
I'm also having the same issue with invalid package. I cleared the /cahch direcotry and still have the issue -- Is there something else i can try before wiping and starting over?
thanks
Rudey
It could also be caused by the .android_secure folder on your SD card. Clearing this folder and letting the market restore them solves issues a lot ofthe time.
As always use TiBackup or something to backup all your apps first too to be safe.
As the OP, I can tell you that I have, in fact, been unable to fix this problem.
Initially the suggestion I posted above worked, however a couple of days later is was no longer working again.
I have tried every trick on the web, including:
1. Removing SD card.
2. Deleting the above mentioned folder
3. clearing market cache
4. Clearing all caches in recovery
5. logging out and back in to google talk.
The only thing that fixes it is a complete factory reset.
I currently have a combination of 3 errors:
1. No download at all.
2. Download unsuccessful
3. Invalid Package
some apps will still update, but what is really weird is that I am even getting invalid package on new apps (so its not a corrupt app already installed on the phone).
One last thought. Once I am unable to update an app, even if I remove it, I can no longer restore the backup using Titanium.
oughta try reformating your SD card and let the phone reformat it too.
sgt. slaughter said:
oughta try reformating your SD card and let the phone reformat it too.
Click to expand...
Click to collapse
don't see why this is different than un-mounting the SD which should do the same thing and has been tried.
sw99 said:
don't see why this is different than un-mounting the SD which should do the same thing and has been tried.
Click to expand...
Click to collapse
na actually reformating it will fully wipe everything on the SD and having the phone do it is best always as its always better to format with the device your using the disk on the most in general.
Found the problem, updated in OP.
sw99 said:
I've been having this problem on and off for a while, mostly I believed it was related to something getting corrupted when I restored my apps to a new Rom with Titanium Backup.
I am happy to say, that after scouring the web for days, and trying a lot of wrong information, I finally figured out how to fix this.
It's real easy. All you need to do is remove any *.apk files located in the /cache directory on your phone (did not even need to remount- though I did it as root just in case).
I never did figure out why only some apps will have this problem or how the problem first comes about, but I have successfully done this twice and have since been able to install/update files that had this error before.
Update (3/3/11): OK - After scouring the Internet for over a month I finally figured it out. My info above was only part right. The problem is specifically with ROMs/Kernels that move the dalvik-cache to the /cache directory (HTC puts it in the /data dir).
In any case, when it's in /data, it is using app space, and therefore you usually run out of app space and know about it. However, because this is in /cache, you don't really know what you are using. As you load up on apps, your dalvik-cache grows, and since these apps need the .dex files in the cache, even if you clear your cache, it will just get re-created.
the /cache dir is also where the apps are temporarily stored while downloading from the market. So....
1. If you are getting immediate download fails, that means that your cache is so full that you don't even have space for the temp file.
2. If you get "Invalid Package" that likely means that there was not enough cache left to install the .dex files (the download is also taking up some of this space).
Unfortunately, the only way to fix this is to either remove some of your apps, or move your cache to your SD card.
HOWEVER, I found this great app on the market called Link2SD, that allows you to only move select apps to the SD card, and you can also move the dalvik-cache files associated with these apps.
see this thread for specifics: http://forum.xda-developers.com/showpost.php?p=10711328&postcount=1
it lets you select which apps to move. You will need to create a new partition on your card, though.
So far results have been great and I can finally update the 30+ apps that have been stuck for me for the last 2 months.
almost forgot, if you adb shell or use terminal emulator, you can type "df" to see how much space is left on all your mounts.
Click to expand...
Click to collapse
Didnt solve my issue.. I had reformatted my phone and SD card and reinstalled my apps. It was working fine again but now its back to some apps update fine.. some get DOWNLOAD UNSUCCESSFUL and some get PACKAGE FILE INVALID.. any ideas.. Im on sprint lovers rom (latest)
It appears th LINK 2 SD needs a second partition that I dont have nor use with SPRINT LOVERS ROM and 2.2 .... am I missing something??
To the OP,
The program you linked to seems to be a variation of dark tremor's a2sd method (http://forum.xda-developers.com/showthread.php?t=715116). His lets you move data, cache, and/or dc to the ext partition, but doesn't (at least I don't believe it does) give you granular control over which apps remain in the standard location.
In my own use, I chose to move all user installed apps to sd, but dc remained on the internal memory (albeit, not in /data, but in the /cache partition). I figured this way, even if the sd card is missing, the phone will still boot. I won't have access to anything I installed, but whatever the rom came with will still be accessible.
Follow the instructions on that thread and create the second partition. You won't need more than 500mb. apps2sd or link2sd is the only way you can fix this problem unless you want to remove some of your apps.
Sent from my PC36100 using XDA App
gpz1100 said:
To the OP,
The program you linked to seems to be a variation of dark tremor's a2sd method (http://forum.xda-developers.com/showthread.php?t=715116). His lets you move data, cache, and/or dc to the ext partition, but doesn't (at least I don't believe it does) give you granular control over which apps remain in the standard location.
In my own use, I chose to move all user installed apps to sd, but dc remained on the internal memory (albeit, not in /data, but in the /cache partition). I figured this way, even if the sd card is missing, the phone will still boot. I won't have access to anything I installed, but whatever the rom came with will still be accessible.
Click to expand...
Click to collapse
Yes that's true, and I eventually went the app2sd route. However, I was trying to avoid that because of the slow speed of my sd card.
Sent from my PC36100 using XDA App
sw99 said:
Yes that's true, and I eventually went the app2sd route. However, I was trying to avoid that because of the slow speed of my sd card.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm not sure which app2sd method you're referring to, but keep the following in mind. I discovered this after my backup images failed to restore properly.
In the past, i'd be backing up boot, system, and data partitions. Obviously with dt's a2sd, I need to include the ext partition now. No problem. BUT, when restoring, i'd run into issues where my apps were present, but all settings were lost. After much confusion and head scratching, I tried wiping cache and dc AFTER the restore, but before the initial boot. The restore was a success now!
Apparently, with a2sd on the ext3, some remnants of cache or dc remain when backing up, even if cache is not selected. As part of any good restore, first thing is to always wipe, so now we end up with a hodge podge of files in the cache which I think causes the OS to revert all the settings back to default.
Just something to keep in mind.
i wanted to go back how my dhd was.. lots of problem.. i havent fix my radio problem yet and now this invaled package thing *face palm*
My phone is HTC G7, and I use data2sd to get 1.5G rom space, now there is still about 1.2G left, but I also met the "invalid package file" problem. I can't find any *.apk in /cache, (root, with "ls -a"). But if I uninstall some apps, I could install or update other apps successfully. I could not use Link2sd for I already have data2sd and I guess it's not a problem of insufficient space, because I still have enough rom space.
Do you have any new solutions?
supericexu said:
My phone is HTC G7, and I use data2sd to get 1.5G rom space, now there is still about 1.2G left, but I also met the "invalid package file" problem. I can't find any *.apk in /cache, (root, with "ls -a"). But if I uninstall some apps, I could install or update other apps successfully. I could not use Link2sd for I already have data2sd and I guess it's not a problem of insufficient space, because I still have enough rom space.
Do you have any new solutions?
Click to expand...
Click to collapse
The problem is not the apps, its the /cache running out of space. I suspect that the app you are using cannot move the dalvik-cache files (and is really just a shortcut to android's app2sd - which is not the same as darktremor or link2sd).
in terminal us df -k to see how much space you have on each mount to confirm that there is little space in cache.
If you really have that much space in your apps mount, then I would suggest moving the dalvik-cache back to its original location (search for instructions, as the only way I know how to do it is by installing darktremor's app2sd). If you are still having problems, you really are limited to either partitioning your SD card and using apps2sd or link2sd or removing apps.
hope this helps.
I have been having this issue for a couple of months now - with a bit of a twist. After wiping my dalvik-cache, my apps began to sucsessfully update - except for Google apps.
I have no idea why just those apps, but going into settings/Applications/Manage applications, and selecting each app, then clearing that apps cache, allowed those apps to sucessfully update also.
I am thankful I did not have to resort to the above fix.
Any solution if not rooted?
I've just started to get this error when trying to update the Google+ app. The error is only happening with Google+, every other app I update/install works fine.
I haven't rooted my device, and I'm hoping there's a way to fix the issue without rooting?
Device: Nexus One
Rom: Stock Android
Version: 2.3.4
Although I couldn't see anything in the cache directories, I checked in /system/app and couldn't find any package that looked like it would be Google+.
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.
So, I am ready to flash something other than the stock ROMs, or at least the purely rooted stock ROMs. I want to try out NunHugger's Epiphany ROM, which looks nice. When I wipe, will it leave the /sdcard folder alone? I just want to make sure I wont lose some of my books and game saves and such.
Edit: I just realized how dumb a question this must actually be, as I am pretty sure /sdcard is left alone, considering the ROM being flashed is also stored there (/sdcard/download). But I'd still like confirmation to be clear. I promise I am not as stupid as this post is.
Your External SD card is not effected.
Generally, you internal memory is referred to as SD card. Your removable SD is referred to as External SD.
The OS, has it's own space, so if you do the usual wipes, even Mounts and Storage format, your things will still be there. (unless you toggle to format entire internal memory)
Generally, the stuff you download and goes to SD, is still there after you flash. 9 times out of 10.
I have flashed over 150 times, and still I have things that I downloaded.
Ah yes, I didn't specify, going under the assumption everyone knows the difference of ext_sdcard and sdcard. I was referring to the internal sdcard. But thanks for the confirmation.
Yea I was scared when I flashed my first ROM. I ran 2 backups of everything and then realized that everything on the /sdcard partition was still there. I would still back that stuff up just in case
I'm sure the application data gets cleared when your doing the necessary wipes and formats prior to flashing. So there go your game saves and such. Happens to me when I flash a new roms. I just do backups with Titanium and restore them, no biggie. Just make sure you backup before you flash.
I've just installed the Paranoid-Jellybean 1.99
http://forum.xda-developers.com/showthread.php?t=1793180
on my EU HTC HD2
I can't anderstand what sd the idea behind program S2E, it seems its purpose is to move apps to SD but when used it this way then all newly installed Widgets disappeared What's more even without launching S2E in Settings thare are options to move individual apps to SD (not for all in fact)
it isn't talking about the normal fat partition on the sd card, you must have an EXT partition created before using the app.
What it does, is take the ext partition on the sd card and makes the system think that it is internal memory, thus giving you more 'internal' memory for apps and data and such like.
This isn't the same as choosing 'move to sd ' in the settings - apps options, as this moves the app to the FAT (windows) partition of the sd card. Some apps wont work when 'moved to sd', however they WILL work from the ext partition, because android thinks its internal.
So, if you haven't already got an ext partition, back up the contents of your current sd card (it will get wiped) then reboot into cwm, choose 'advanced - partition sd card' and choose a partition size. (512 or 1024 is usually plenty) then restart android and try the app again.
Any apps that you have already 'moved to sd', go move them back to internal, and the system should automatically move them from the FAT partition to the EXT partition.
Tahnk you for your explanation. Also I must apologize I confused the names of the programs - in fact its S2E rather than A2S (the previous post have written from memory). However probabely this s2e serves the same purpose, as it has such relevant commands:
Applications - Location: /data/app
Private apps - Location: /data/app-private
...
and so on, until:
Dalvik cache - Moving from /data to /sd-ext
So, I've chosen the first option and got displayed:
Application
Moving from /data to /sd-ext
Reboot is required!
and rebooted the phone, but the result was disappointing - several apps dissappeared including all Widgets!
Of course I've had ext3 partition previously set.
What was wrong?
Other question please: exactly WHAT is worth moving to SD Ext partition, Dalvik cache too?
yea they do the same/similar things - namely move parts of the system to the ext partition, and create symbolic links so that the system doesnt notice they've moved.
You seem to be moving your entire data folder to the ext, which i believe has an impact on boot performance, since the data partition wont be mounted straight away, and android needs it during boot.
I don't know a great deal about the various app2sd scripts, but the ones i've used normally only move the /data/app/ (your user installed apps folder) and the dalvik cache to the sd-ext partition.
samsamuel said:
yea they do the same/similar things - namely move parts of the system to the ext partition, and create symbolic links so that the system doesnt notice they've moved.
You seem to be moving your entire data folder to the ext, which i believe has an impact on boot performance, since the data partition wont be mounted straight away, and android needs it during boot.
I don't know a great deal about the various app2sd scripts, but the ones i've used normally only move the /data/app/ (your user installed apps folder) and the dalvik cache to the sd-ext partition.
Click to expand...
Click to collapse
So won't it exert excessive load on SD card which could lead to some sort of instability or other issues?
ioy said:
So won't it exert excessive load on SD card which could lead to some sort of instability or other issues?
Click to expand...
Click to collapse
better than exerting load on the nand and increasing the chances of bad blocks, right?
samsamuel said:
better than exerting load on the nand and increasing the chances of bad blocks, right?
Click to expand...
Click to collapse
theoretically YES but then does it also apply for the whole Android ROM itself (please compare the neighbouring discussion "is NAND Android better than SD and why?")
ioy said:
(please compare
Click to expand...
Click to collapse
no thanks, i have far more interesting things to do. i couldn't care less if there's excess load, though i'm pretty sure there isn't, since i've been running an ext partition for several months and no problems.
Have you understood me well? I've asked about the problem probably NAND ROMs themselves wear NAND memory too so would it be safer (for the device) to use SD ROMs (which write only on SD memory all the time)? How do you think, could it be the case?
i think if it were of any real benefit, people would be talking about it, but no one does. I guess its down to you, if YOU think it will help, then do it. If you don't, don't!
I guess battery drain would be teh real deal maker/breaker. I havent used sd android, but i believe it to be (in general terms) a little less stable, more prone to slowdowns, and harder on teh battery. But thats all anecdotal evidence, as i said, ive never booted sd android.
(edit - i must say, in humour, not meaning offence, that between this thread and your other thread, you sound like a guy who just bought a sports car and wants to cycle to work to save wear and tear on teh car )
Why? It's been stuck at 60.5mb used and 1.2GB free according to Diskinfo forever now. Ever since I restored Madvane's unrooted B180 backup & then flashed root with Magisk.
Why does it bother me? Because I have no idea what I'm talking about and I feel like maybe Cache is storing in the Data Partition where I install my apps...? Is it?
Also with 1.2GB free in the Cache parition & 1.2GB free in the System Partition, can I just partition those and make the Data partition bigger for more available Internal Storage for apps and stuff? I mean I have external storage as default location but so many files still get installed on internal and I'd like to expand that if I could alter these partitions.
Anybody done that before or can answer my questions? Thanks! Images attached
Anyone ?
I have not read of anyone here repartitioning internal storage. I don't think it's as simple as repartitioning a PC hard drive with a GUI tool.
Do you have any tools in mind to do this repartitioning? I think it would be a highly risky operation, so be sure to make full backups and note all the original settings of existing partitions before repartitioning.
You can Google threads on people repartitioning internal storage for other phones, but note the ones who ran into problems and bricked their phones.
I wouldn't mess with the partition sizes, personally.. in theory it works, but it can trigger some arcane safeguards added by oems.
Try wiping the cache partition in twrp..? Could have gotten bugged, which would throw an error and require reformatting
Is there any indication of a problem with the cache partition?
It's biggest usage would be to download an OTA file, so unless that's happening, I would expect cache partition to remain remain mostly empty as OP reported. Probably what's in there is TWRP or stock recovery logs - you can confirm with a root file manager.
Wiping the cache partition as suggested won't harm anything and it would be interesting to know what it's reported usage is after wipe and reboot.
divineBliss said:
Is there any indication of a problem with the cache partition?
It's biggest usage would be to download an OTA file, so unless that's happening, I would expect cache partition to remain remain mostly empty as OP reported. Probably what's in there is TWRP or stock recovery logs - you can confirm with a root file manager.
Wiping the cache partition as suggested won't harm anything and it would be interesting to know what it's reported usage is after wipe and reboot.
Click to expand...
Click to collapse
I guess that was my question too. If there was any idication of an issue here. Seeing that free space I'd like to have it though.
On another note. There's no indication of anything being wrong with my Data partition but I formatted it to ext4 back when I bricked my phone in a hope it would fix something. But it seems fine. IDK what they default partition type was.
My data partition is ext4, which I believe is the stock default type.
divineBliss said:
My data partition is ext4, which I believe is the stock default type.
Click to expand...
Click to collapse
Thanks man you've been allot of help. Have you tried L-Speed? I'm thinking about trying it. I do have Kernel Auditiur installed. Don't use it.
Nothing is broke but thought about trying L-Speed.
Never heard of it. If you try it, let us know what you think.
WifiGhost said:
Thanks man you've been allot of help. Have you tried L-Speed? I'm thinking about trying it. I do have Kernel Auditiur installed. Don't use it.
Nothing is broke but thought about trying L-Speed.
Click to expand...
Click to collapse
divineBliss said:
Never heard of it. If you try it, let us know what you think.
Click to expand...
Click to collapse
I just tried it seems like a nice and easy way to tweak performance or battery.
I prefer kernel adiuator myself.. L Speed has too many generic settings which do next to nothing for actual performance, reminiscent of the many garbage tweak programs that have been out there for years. K.A. allowed for better control of the cpu governor settings, which allowed me to negate some of the impact of emui's 'battery optimization'. A little bit of entropy tweaking on top of that, and I no longer experience nearly the amount of choppiness