I know what happens when you do a factory reset/wipe, but what exactly happens if I only wipe Dalvik Cache? (I'm about to flash a ROM, don't want to do a complete factory reset/wipe, but wondering if I can still help "eliminate ghosts" by wiping Dalvik Cache.)
Bump, is this just like a crazy question or something?
What exactly does wiping Dalvik cache do?
trunkstar1 said:
Bump, is this just like a crazy question or something?
What exactly does wiping Dalvik cache do?
Click to expand...
Click to collapse
dalvik is a virtual machine in android operating system that runs applications, which is similar java vm. dalvik builds some sort of cache of applications (i wouldn't go into details) to run them faster in dalvik cache space. you can clear them out, and android will rebuild the cache on the next boot. and the initial boot will take longer than usual once you wiped the dalvik cache because android needs to rebuild it.
So it's something that you can safely wipe on occasion right, just to clear up any bugs?
trunkstar1 said:
So it's something that you can safely wipe on occasion right, just to clear up any bugs?
Click to expand...
Click to collapse
when you flash a custom rom, usually the rom automatically wipes out dalvik cache to remove all that junk from the previous rom.. you do not need to wipe it regularly unless you flash apps or any other system modifications on top of the existing rom via clockworkmod recovery very often
But is there any "harm" in doing it? Any consequences other than a longer reboot time?
trunkstar1 said:
But is there any "harm" in doing it? Any consequences other than a longer reboot time?
Click to expand...
Click to collapse
Not at all. Apps will just be a little sluggish for a bit.
Sent from my SGH-T959 using XDA App
Using Kies to goto 2.2, does that wipes Dalvik cache? Koz I went to 2.2 from kies mini, then ODIN'd a Voodoo kernel and i never wiped it manually...
so should I?
many thanks
You are trying to not factory reset but any rom you will find will have a system, data, data_data and cache wipe built into it. You can try finding a Rom you like and remove the wipes from the update_script but those wipes are put there on purpose. Kies will wipe everything too.
or use root explorer go in to system and find dalvik cache and delete files =>
sir can i ask a question?
jaetm83 said:
dalvik is a virtual machine in android operating system that runs applications, which is similar java vm. dalvik builds some sort of cache of applications (i wouldn't go into details) to run them faster in dalvik cache space. you can clear them out, and android will rebuild the cache on the next boot. and the initial boot will take longer than usual once you wiped the dalvik cache because android needs to rebuild it.
Click to expand...
Click to collapse
is it normal to boot so long when i accidentally wipe dalvik cache? because im afraid and thinking my phone was brick what can i do to turn it back normal? wait to boot the system?
avie14 said:
is it normal to boot so long when i accidentally wipe dalvik cache? because im afraid and thinking my phone was brick what can i do to turn it back normal? wait to boot the system?
Click to expand...
Click to collapse
Yes it is normal for it to take longer than a normal bootup. It is rebuilding the Dalvik that was just wiped. #nosorcery
trunkstar1 said:
I know what happens when you do a factory reset/wipe, but what exactly happens if I only wipe Dalvik Cache? (I'm about to flash a ROM, don't want to do a complete factory reset/wipe, but wondering if I can still help "eliminate ghosts" by wiping Dalvik Cache.)
Click to expand...
Click to collapse
Thank you for this question, thank you guys now I know that wiping dalvik cache is not that bad at all.
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
Just flashed (clean flash) Jellybam 6.5 (up from 6.4) last night, and everything was butter until I tried to change my ringtone. If I select the 'sound' in settings, up pops "settings has stopped" and it closes out. Tried to reflash it twice...same result. eveything seems to work great but the sound settings. Has anyone else had this issue and if so, is there a fix other than reverting back to 6.4???
Just do a complete user data wipe with factory settings then cache and dalvick wipes... This should do the trick.
did that,done that...
snozim said:
Just do a complete user data wipe with factory settings then cache and dalvick wipes... This should do the trick.
Click to expand...
Click to collapse
I did, complete wipe- flash-clear same problem...then Darkside super wipe, cache, dalvik, internal, system then flash, wipe cache/dalvik same problem...did it 4 or 5 different times...same problem...
OP, you will have to go the site that has this said ROM, as it is no longer supported on XDA, as you will not see the threads on XDA or the OP/so called dev of those threads, which he is banned from XDA also. Thread Closed and Thank You.
I found same question in Dev forum but can't post as I'm still new. So I ask the same question here:
What is Davik Cache and what is normal Cache?
Are they the same thing or 2 different cache that must be wiped when flashing roms?
Normal Cache is any temporary information created or used by an app.
Dalvik Cache is a program cache area for the program dalvik. Dalvik is a java based virtual machine that is the bases for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. Sounds confusing. It's similar to the prefetch files in Windows.
When you full wipe the normal cache is being deleted automaticly. Dalvik cache is being deleted manually via any recovery. Under Advanced in CWM.
Sent from my Nexus 10 using Tapatalk HD
thanks
thanks
Thanks, now I understand better. I was wondering where is this Dalvik Cache as I couldn't find the clearing function, so it is only found in custom Recovery mode.
What about my factory default phone? Its stock recovery show up as Android system recovery <3E>, there's a wipe cache partition function. I tried it and all my apps still working ok.
Thanks!
Using flawless ics rom, and i started getting random reboots. Idk why, i didnt use titanium backup at all.
My apps are all useful right now so i dont wanna lose them. So how can i do like some soft wipe that doesnt delete all my apps? I dont want to do backups. Becoz it can lead to random reboot if i restore them.
Did wipe cache but no help.
Sent from my WT19i using xda app-developers app
Wipe Dalvik cache ...thats soft wipe...
Random reboots looks like more of kernel issue ...
The only things you can wipe without loosing data are cache and dalvik cache. But wiping dalvik cache won't change anything, because as far as I know the dalvik cache will be rebuilt on every boot
So try wiping cache or change the kernel for the rom
Sent from my Nexus 4 running Android 4.3
mihahn said:
The only things you can wipe without loosing data are cache and dalvik cache. But wiping dalvik cache won't change anything, because as far as I know the dalvik cache will be rebuilt on every boot
So try wiping cache or change the kernel for the rom
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Dalvik cache is rebuilt only on first boot or if an app is changed via recovery or if you upgrade to higher OS (like ics to JB)...
Some times it gets corrupted and wiping helps...(like 1 in 10 times...) and the cache gets rebuilt (android is upgrading....)
Cache is wiped whenever you reboot so it's one of the most pointless thing to do in recovery for stock roms..(wiping batteystats is the most pointless thing...)
On CM roms ,system dalvik lies in /cache so wiping cache is equivalent to wiping dalvik for system apps..
@OP
Use titanium backup to backup all apps and do a complete wipe..
karandpr said:
Dalvik cache is rebuilt only on first boot or if an app is changed via recovery or if you upgrade to higher OS (like ics to JB)...
Some times it gets corrupted and wiping helps...(like 1 in 10 times...) and the cache gets rebuilt (android is upgrading....)
Cache is wiped whenever you reboot so it's one of the most pointless thing to do in recovery for stock roms..(wiping batteystats is the most pointless thing...)
On CM roms ,system dalvik lies in /cache so wiping cache is equivalent to wiping dalvik for system apps..
@OP
Use titanium backup to backup all apps and do a complete wipe..
Click to expand...
Click to collapse
give him a medal :good: