Hello,
I rooted my eris about a month ago and have flashed about every rom thats been on grdlock's site. But one thing I've never been quite clear on is the whole wipe process. Can someone explain the difference between the factory wipe and the dalvik wipe? For instance why should i do one or the other or both before flashing a new custom rom?
HTC Droid Eris ROOT
Aloysious 2.0 v.7
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Can anybody help??
The factory wipe cleans the phones OS out, the dalvik wipe clears the cache. You don't need to know exactly what they do to know they definitely make ROMs run much cleaner when you do it, because I really dont know the specifics. I don't know how commands are programmed into DOS but I still know that the commands work...if that metaphor makes any sense.
PS - you should definitely do both before flashing a new ROM or restoring a nandroid backup
thanks taco. that helps a ton.
lol
chaneer said:
thanks taco. that helps a ton.
Click to expand...
Click to collapse
Sorry to let you down my friend.
factory wipe is like formating your harddrive on your computer before installing a new OS.
dalvik is a way to run multiple virtual machines where parts of the applications your running on android also run during normal operation to minimize memory and cpu usage, the cache obviously plays a part in memory usage, clearing this is like rebooting the ram on your computer to run faster.
in summary: format both and google your questions before asking them.
thanks guys. and trust me i did search all over for this but couldnt find a definitive answer. i just wanted to know for myself exactly what each "wipe-type" does, but i'll just stick with using both before i flash a new rom unless the dev instructs otherwise.
factory wipe is like formating your harddrive on your computer before installing a new OS.
dalvik is a way to run multiple virtual machines where parts of the applications your running on android also run during normal operation to minimize memory and cpu usage, the cache obviously plays a part in memory usage, clearing this is like rebooting the ram on your computer to run faster.
in summary: format both and google your questions before asking them.
Click to expand...
Click to collapse
Factory wipe is not wiping the os
...factory is like restoring the os, to how it came when you first got your computer, deleting all your programs, personal files, and stuff, that you added over the life of your computer.
You got cache down though.
Hope that makes it a little more clear.
Sent from my Eris using the XDA mobile application powered by Tapatalk
[ROM](7-19-11) SNS Gingerbread v1.4.1, OTA 4.24 Sense, Now W/ Remap Rosies.
Hey guys,
So I'm planning to flash the ROM at this URL: http://forum.xda-developers.com/showthread.php?t=1131217 but it requires that I "wipe" first. My rank says it all--I'm new to this stuff.
So, to the question; What should I wipe, and any tips on flashing this ROM?
Thanks,
Lacedaemon
Well, Its for a different phone, so I would say no.
First of all, Linux has a few different folders. /data is used to install all your apps and stuff, but /system is for the 0S and stuff. The /system section is restricted unless you gain root access. Anyways, /system isn't removed via factory reset, just /data. Installing a new rom, /system has files usually overwritten.... Hope that helps a little. The other folders are for cleaning up what's ever left over.
It may be a stupid question .. Do i have to check the 3 boxes
backup existing rom
wipe data and cache
wipe dalvik cache
every time i do a update ??
Thks
No you do not have to. I only check wipe dalvik which is also optional,but has resulted in better performance for most users here. If you check wipe data and cache then all of your apps will be deleted and you will have to reinstall.
I am also basing this on guessing that you are running CM7, please let me know if that isn't correct.
superDel said:
It may be a stupid question .. Do i have to check the 3 boxes
backup existing rom
wipe data and cache
wipe dalvik cache
every time i do a update ??
Thks
Click to expand...
Click to collapse
You don't "have to" do a backup but it is good to in case something is messed up. I think if you wipe data it wipes your existing apps so I don't do that. But yeah I would definitely wipe dalvik.
superDel said:
It may be a stupid question .. Do i have to check the 3 boxes
backup existing rom
wipe data and cache
wipe dalvik cache
every time i do a update ??
Thks
Click to expand...
Click to collapse
depends on what rom your are flashing. So with that, let me ask the question. What rom are you flashing? If you're using CM7, those roms can technically be flashed without wiping anything although you may want to wipe the dalvik cache just to play it safe. In doing so you won't need to re-install any apps or enter your account data over again. Some other roms automatically wipe for you. But like others have suggested, you should get into the practice of trying to wipe whenever you can, and use titanium to only restore your apps. Hope that helps.
This is completely irrelevant but I noticed that your signature says do not click thanks. I don't know if you have that there so people will click it, but I clicked it just to be an ass lol. Meant for above poster ^
Edit: Okay I get it now lol. I didn't really look at it, but I see it now so ignore that lol.
i know what im gonna post is not relevant to the actual topic, but since it says "update" as a title, ill post my little rant anyway..
for some odd reason my google search layout has been updated and i really dont like it..
it's on big fonts, compressed on the right side of the screen and there's a huge empty space on the left.. sooo ugly! ughh and really confusing to look at..
why is android's UI/design so mediocre? is google ever going to improve this area? even google gadgets is weak compared to yahoo widgets..
end of my rant thank you.. pfft
Hello,
I would like to ask a couple of questions regarding x10 which has been tickling my mind for sometime.
1> Can anyone share their setcpu profiles for good battery and performance?
2> What exactly is Dalvik Cache? Why do we use it? and why does it have to be wiped for every rom installation. I'm personally interested to find an answer for this question.
Thanks for the help!
Neo said:
Hello,
I would like to ask a couple of questions regarding x10 which has been tickling my mind for sometime.
1> Can anyone share their setcpu profiles for good battery and performance?
2> What exactly is Dalvik Cache? Why do we use it? and why does it have to be wiped for every rom installation. I'm personally interested to find an answer for this question.
Thanks for the help!
Click to expand...
Click to collapse
1. What has helped me a lot with battery life was the Screen Off profile in SetCPU. Set it to 245-384, governor: powersave. If you have delay when turning on the screen, set the governor to on demand. See my signature for more details!
2. Dalvik cache is an application cache area for the program dalvik.
Dalvik is a java based virtual machine that is the base for running your apps (the ones that have .apk extension).
In order to make access times faster (in cases where there's no JIT (just-in-time) compiler installed by default),
the dalvik-cache is the result of dalvik doing a optimization of the running programs.
Sounds confusing, I know. Think of it as similar to the prefetch files in Windows.
It's not always necessary to wipe the Dalvik Cache when installing a new ROM,
because most ROM zips include an update-script that wipes the DATA partition, therefore including the dalvik-cache,
but it doesn't hurt to do it either, it's a precaution measure.
Hope I helped!
Thank you so much mate.Totally get it now although the word “cache“ made sense earlier I've seen users wiping it frequently and i thought of getting to know about it
Ps.a thank you will be sent when i get to my pc
Sent from my X10i using XDA App
Neo said:
Thank you so much mate.Totally get it now although the word “cache“ made sense earlier I've seen users wiping it frequently and i thought of getting to know about it
Ps.a thank you will be sent when i get to my pc
Sent from my X10i using XDA App
Click to expand...
Click to collapse
You're welcome!
Also, may I add, wiping the dalvik cache often is not wise, in general.
It kind of defeats its purpose!
If I am restoring my device should I delete all data?(data, cache, and dalvik cache )
I do. But its not necessary.
Sent from my SGH-I777 using Tapatalk
I never do.
I never clear before a restore since it's all pretty much overwritten anyway. Only thing that might stay the same is dalvik. Does anyone know if that is included in a nand backup?
Sent from my SGH-I777 using xda premium
Depends, if you no longer need the data, wipe it. If you do then don't wipe.
@ mfreywald - If I understand you right. If your nanodroid back up it on the phone then yes. If it in your SD card then no.
I run jivy's kernel cleaning script (wipes cache and dalvik twice) before any restore or flash - might not be necessary, but I've NEVER had a bootloop or other issue like that since I started doing it.
alacrify said:
I run jivy's kernel cleaning script (wipes cache and dalvik twice) before any restore or flash - might not be necessary, but I've NEVER had a bootloop or other issue like that since I started doing it.
Click to expand...
Click to collapse
Ahh, the old "kill a fly with a sledge hammer" philosophy. I'm in that camp too. A few extra seconds in CWM can save a headache later. A habit I picked up on my Captivate. Between each flash I wipe data, wipe cache, wipe dalvik twice, and generally format system.
Sent from my SGH-I777 using Tapatalk 2 Beta-4
I do not. Kinda pointless since you are rewriting the rom when restoring anyways
In3rDm0RetHeNu said:
If I am restoring my device should I delete all data?(data, cache, and dalvik cache )
Click to expand...
Click to collapse
not mandatory but I do anyways just to be safe. it is kind of like the "safely eject usb" function on windows. nobody really uses it because it isn't a mandatory thing; but there is always that 5%
I was getting out of space on my internal phone, so I decided to clear wipe cache and dalvik cache through CWM, but I find i save a lot of space BUT some apps stop working, maybe they are lost. So was does this actually do? Why are the apps there, but can't work? :crying:
Ok, after rebooting they are actually working again, i didn't even lost any data (progress on games) but I am really concerned what does this really do??
rolo143 said:
I was getting out of space on my internal phone, so I decided to clear wipe cache and dalvik cache through CWM, but I find i save a lot of space BUT some apps stop working, maybe they are lost. So was does this actually do? Why are the apps there, but can't work? :crying:
Ok, after rebooting they are actually working again, i didn't even lost any data (progress on games) but I am really concerned what does this really do??
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Dalvik_(software)
When you reboot, Dalvik cache and Cache are re-created. So no space saved this way.
Feanor88 said:
http://en.wikipedia.org/wiki/Dalvik_(software)
When you reboot, Dalvik cache and Cache are re-created. So no space saved this way.
Click to expand...
Click to collapse
I was wondering what wiping the Dalvik cache did, too. I installed an inverted app and someone told me I needed to wipe the Dalvik cache in order for it to remain in place after a reboot, so I did that. Now my phone says "Optimizing apps..." It must rbe e-creating the cache.
As far as I know, when a rom boots up for the first time Dalvik goes through each & every apk's & extract the Dex & put it in the cache. So probably it is a location of all apks. If dalvik cache is not wiped after a new rom is installed,dalvik cache will skip because it founds the dexed cache files attach to the directory. The result is "Force close" issues.
So wiping dalvik cache can be done without any problem many times within the same rom & that's why is shows "optiming apps" after a dalvik cache wipe.
saqib nazm said:
As far as I know, when a rom boots up for the first time Dalvik goes through each & every apk's & extract the Dex & put it in the cache. So probably it is a location of all apks. If dalvik cache is not wiped after a new rom is installed,dalvik cache will skip because it founds the dexed cache files attach to the directory. The result is "Force close" issues.
So wiping dalvik cache can be done without any problem many times within the same rom & that's why is shows "optiming apps" after a dalvik cache wipe.
Click to expand...
Click to collapse
Thanks! That's in line with my suspicion, except I didn't know when I posted my question that an apk file was nothing but a zip file that contains a dex (Dalvik executable) and a bunch of other files. Your explanation makes sense. I also noticed that if I install an individual app from a zip file using CWM Recovery, then it clears the relevant part of the Dalvik cache for me. That doesn't happen when I install an apk file directly using Root Explorer.
guys one line question i am performing "Wipe cache and dalvik-cache" will my phone internal memory be deleted ? thanks a ton
deepankarbu said:
guys one line question i am performing "Wipe cache and dalvik-cache" will my phone internal memory be deleted ? thanks a ton
Click to expand...
Click to collapse
Nop, it will not
Sent from my SK17i using xda premium
Phone didn't boot after wiping Dalvik Cache
Hi Geeks
i have an Xperia Arc S modded with Cyanogenmod JellyBean 4.1.2 Cooked ROM
i had alot of memory issues as applications keep closing whenever system runs out of memory, it is always obvious in the DSP application with the walkman in addition to visualizations inside the walkman
i searched for a solution and some told me that wiping the dalvik cache might solve the problem, so i gave it a try and rebooted in CWM recovery mode "built inside ROM" , cleared the Dalvik cache , and the phone keeps displaying the Xperia Logo without any further progress, as if it's in somekinda loop !
any idea what to do next without wiping my Data ? thank you all
BR
AMR
Koptanov said:
Hi Geeks
i have an Xperia Arc S modded with Cyanogenmod JellyBean 4.1.2 Cooked ROM
i had alot of memory issues as applications keep closing whenever system runs out of memory, it is always obvious in the DSP application with the walkman in addition to visualizations inside the walkman
i searched for a solution and some told me that wiping the dalvik cache might solve the problem, so i gave it a try and rebooted in CWM recovery mode "built inside ROM" , cleared the Dalvik cache , and the phone keeps displaying the Xperia Logo without any further progress, as if it's in somekinda loop !
any idea what to do next without wiping my Data ? thank you all
BR
AMR
Click to expand...
Click to collapse
Are you sure you only wiped the dalvik?
Sent from Myushi
clears app cache
rolo143 said:
I was getting out of space on my internal phone, so I decided to clear wipe cache and dalvik cache through CWM, but I find i save a lot of space BUT some apps stop working, maybe they are lost. So was does this actually do? Why are the apps there, but can't work? :crying:
Ok, after rebooting they are actually working again, i didn't even lost any data (progress on games) but I am really concerned what does this really do??
Click to expand...
Click to collapse
it clears the app running cache stored in os.
absolutely ..
XperienceD said:
Are you sure you only wiped the dalvik?
Sent from Myushi
Click to expand...
Click to collapse
Yes sir it's only the dalvik cache, both ways this ROM was pretty heavy and i'm not satisfied with the reboot every 2 or 3 hours of use, i will install xperia ultimate HD ROM, they say it's pretty stable and has no problems, and it has the sound enhancements i needed in the Jellybean cooked ROM
thanks for your reply
alcatel 918n
XperienceD said:
Are you sure you only wiped the dalvik?
Sent from Myushi
Click to expand...
Click to collapse
My phone also has those options built-in. If you did the dalvik only it should get back to where you have the icons. BUT, if you did something else aside from the dalvik, my guess would be goodbye data and hello to phone repairs. Please research first before you do anything on your phone. Your phone and my phone have very powerful built-in tools. It could brick the phone. I hope you did not wipe data and flash.
help! my phone's boot taking too long
i wiped /cache and dalvik cache and format /cache. it's taking took long. been waiting for almost 1 hour.
Lucky Patcher Dalvik-cache
I am getting out of space msg when using Lucky Patcher.....apk will be patched on boot......it says to clear dalvik cache to save space.....is this a good idea(will I loose any data from game etc?) or this a issue with lucky patcher?
Clearing Dalvik
Feanor88 said:
When you reboot, Dalvik cache and Cache are re-created. So no space saved this way.
Click to expand...
Click to collapse
Um, that would involve the re- "optimization" process at each boot. Depending on the number of apps you have installed, this process can take an hour.
Simply put, the Dalvik cache is where a virtual machine program (like VMware Player, Workstation or Fusion or MSVM) called "Dalvik" stores information the applications on your device request it to. This storage is for the purpose of making app load times shorter, but because it's all low-level stuff, it has to be loaded prior to the AndroidOS frontend...Fortunately, this cache only needs to be rebuilt when a flag has been set indicating the need, which is set whenever the cache is cleared. Note the distinction between "loading" and "rebuilding" this cache. "Load" is synonymous with "read" and "rebuild" means "write." So time-wise it is the distinction in effort between reading a book and writing one.
Typically I only clear it for troubleshooting reasons; if something is not working. The latest Cyanogenmod has a major problem where the desktop data is liable to randomly corrupt.
Typically, the only solution is a Dalvik wipe in CM or whatever. If you have recently installed a large number of apps(over twenty)then it might be best to clear the cache via recovery at the next cold boot, especially if your device does weird stuff like getting hot, discharging while plugged in to the OEM charger, widgets crash spontaneously, wallpapers are replaced by defaults, etc....Some of these symptoms can also indicate a virus or malware infection,(especially on custom ROMs or rooted devices) so diagnosis is differential.
But essentially there is no harm in re-building the Dalvik cache, other than the time taken to do so.
Koptanov said:
Yes sir it's only the dalvik cache, both ways this ROM was pretty heavy and i'm not satisfied with the reboot every 2 or 3 hours of use, i will install xperia ultimate HD ROM, they say it's pretty stable and has no problems, and it has the sound enhancements i needed in the Jellybean cooked ROM
thanks for your reply
Click to expand...
Click to collapse
CM has this new MAJOR stability issue, it seems. The random crashes and reboots will soon combine(if they haven't already)with the deletion of your desktop customizations and your widgets will begin vanishing forever. Not even a full wipe and rebuild will bring them back.
Been using AOKP on Nexus 7 2013 for a month now. It is based on CM, but it is way more stable.....haven't needed to re-boot in two weeks! Uptime, baby!
UPDATE 04/05/2014: Been running without rebooting for over a month, now. AOKP is definitely WAY more stable than any other ROM I've used.
Dalvik explained
Saqib Nazm said:
As far as I know, when a rom boots up for the first time Dalvik goes through each & every apk's & extract the Dex & put it in the cache. So probably it is a location of all apks. If dalvik cache is not wiped after a new rom is installed,dalvik cache will skip because it founds the dexed cache files attach to the directory. The result is "Force close" issues.
So wiping dalvik cache can be done without any problem many times within the same rom & that's why is shows "optiming apps" after a dalvik cache wipe.
Click to expand...
Click to collapse
There is a full explanation of the dalvik cache on wikipedia.
The wiki entry fully explains dalvik cache and the integral part it plays in your android system. In very simple terms, it is a cache that allows the system to talk to the exe of a program without the need to load the cache on each and every start. The dalvik is is loaded once, and then never again (unless you wipe the dalvik cache, in which case, it is rebuilt upon reboot). There is no affect on any given program when the dalvik cache is wiped, other than starting slower the first time it is started after the wipe.
Related (I think) - Samsung Galaxy S5 running CM 12.1 latest nightly (6-14). I started on CM 12.0 nightlies in March or April and transitioned to 12.1 within a day or two acter it showed up. That was a relatively noticeable transition requiring new gapps and a factory reset as I recall. I read somewhere that wiping cache and dalvik cache was unnecessary between one 12.0 nightly to another and between one 12.1 nightly to another, so I typically have not performed the cache and dalvik wipe during nightly upgrades, of which I've probably done 30 or 40 since I started on 12.0. After each nightly update flash, when I ask TWRP to reboot the system, without wipes, all my 160 or so apps are optimized, taking some time, before the noot is compete. This morning out of curiosity, after the nee ROM was flashed, I chose the option in TWRP to wipe the cache and dalvik cache before I askefasked TWRP to reboot the system. The wipe process took at least as long to complete as a typical optimization, and when I rebooted, I still got the lengthy optimization. So I'm tbinking either there's no relationship berween app optimization and wiping the caches, or CM and/or TWRP automatically wipes the caches whether I do or not.
---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------
Please forgive typos in my previous post - SwiftKey or something is making proofreading and editing difficult today.
Not the exact answer, but may interests u.
Koptanov said:
Hi Geeks
i have an Xperia Arc S modded with Cyanogenmod JellyBean 4.1.2 Cooked ROM
i had alot of memory issues as applications keep closing whenever system runs out of memory, it is always obvious in the DSP application with the walkman in addition to visualizations inside the walkman
AMR
Click to expand...
Click to collapse
Hi, I do not have the exact answer. But I wanted to share my own observation. When I wipe dalvik caches through CWM recovery, I find my phone taking a long time to finish booting every time. Sometimes I thought it would not boot up, I removed the battery and tried to swith on and my phone boots up. I do not know why it happens, may be I had installed a large no of apps.
I've got Nexus 5 with bootloader unlocked , after few weeks security patch arrived and after the phone switched off and showed error symbol and when I entered recovery mode it showed that error in system/bin.sh files need some help here