I didn't notice this issue with Passion RC1. With Euphoria RC1 the. Superuser app has "crashed." I installed by wiping data/factory reset, wiped cache, wiped dalvik cache, formatted system, flashed and rebooted, let settle for 10-15 minutes to settle and rebooted. It stops when trying to 'allow' and when try to access "stops" instead of opening. Doesn't show an uninstall option under managing apps. Any help greatly appreciated.
dbethards said:
I didn't notice this issue with Passion RC1. With Euphoria RC1 the. Superuser app has "crashed." I installed by wiping data/factory reset, wiped cache, wiped dalvik cache, formatted system, flashed and rebooted, let settle for 10-15 minutes to settle and rebooted. It stops when trying to 'allow' and when try to access "stops" instead of opening. Doesn't show an uninstall option under managing apps. Any help greatly appreciated.
Click to expand...
Click to collapse
You may want to try posting here:
http://forum.xda-developers.com/forumdisplay.php?f=747
I didn't have an issue with this issue with Passion RC1. With Euphoria RC1 the Superuser app has crashed, I installed by wiping data/factory reset, wiped cache, wiped dalvik cache, formatted system, flashed and rebooted, let settle for 10-15 minutes and rebooted. It stops when trying to 'allow' and when I try to access it stops instead of opening. I don't see an uninstall option under app management so I could try reinstall. Any help greatly appreciated!
Go to manage apps->superuser and clear cache and clear data. If that doesn't work, head to the market and see if Chains has an update for you. May need the update fixer too.
Maybe doing Fix permissions from CWM would help.
Searched high and low on XDA and Google and could not find anything related to my particular issue. I'm running CM7 RC1 with Gingerbread 2.3.7 It seems like the problem is mostly occurring when I long press a contact to call or message, not when I take the longer route and tap the contact photo to the right on the contact info, then tap the phone icon and select which number to call....However I slightly remember there being a setting in the "CyanogenMod Settings" that stated something like "this setting may cause a lot of FCs" I just can't remember which setting it was... Here is the FC I'm getting:
The application VZ Navigator (process com.vznaigator.DROIDX2) has stopped unexpectedly. Please try again.
"Yes I am a noob to XDA but I have a lot of experience and understanding of flashing roms and what not, been flashing since HTC Dream."
Wipe dalvik cache in recovery.
Thank You!!
Thanks for the reply! I will try that, one question though. During the CM7 Install dragon said to wipe dalvik cache, can't remember when exactly in the install he said to do so but I followed the instructions EXACTLY, since then haven't had any problems whatsoever but this...Anyway, when I boot into recovery it doesn't actually said "dalvik cache" it just says "wipe cache partition". Is that the same thing? Also, I just recently flashed CM7 for the second or 3rd time as I had a problem with my primary gmail password yada yada...so now I have everything set up how I want in and now I'm moving on to Titanium Backup settings and freezing some apps (I am aware of which one I should and should not freeze) but being that I don't even use VZNAVIGATOR wouldn't it be wise to just freeze it? Thanks again so much for your help, wiping cache now....
To wipe dalvik cache go into the advanced section in bsr... Dalvik cache is listed there.
Sent from my MB870 using XDA
Wiped Cache Partition
So I booted into recovery and wiped the cache partition and rebooted. Everything seemed fine except that my roaming triangle icon was blinking so I connected to my wifi and my service came back. Then I did the *228 thing and updated my roaming capabilities, all is well with the service now. After that before I tried exiting out of my contact/dialer etc. I got the VZNAVIGATOR FC again. Going to try to freeze it in TB. Anymore suggestions would be much appreciated.
Dalvik Cache
Ok got your reply post about Dalvik location, wiping now, thanks again!!!
CM7 Android Recovery
when I open the CM7 Android Recovery app, (I already have it installed) and tap Recovery Mode, the phone shuts off and doesn't boot into recovery mode. So even after I manually power it up and open the CM7 Android Recovery
app and try to install first, then tap recovery mode, it does the same thing...any ideas??
My Apologies...
Sorry for all the questions. I research XDA and found that I need to have it plugged into the A/C. So now I was able to boot into recovery and wipe the Dalvik Cache. Thanks so much again, I will repost if it works.
Problem Solved!!
Thanks for the useful information! Very much appreciated.
Personally I would get rid of VZ Navigation and use Google navigation its much better. That's just my 2 cents!
Sent from my DROID X2 using XDA
Triscuit said:
Personally I would get rid of VZ Navigation and use Google navigation its much better. That's just my 2 cents!
Sent from my DROID X2 using XDA
Click to expand...
Click to collapse
He wasn't using VZ Navigator, it's just that if you flash over something (in this case the stock rom) without wiping the dalvik cache, there are bits of apps left over that you will see spontaneously force closing.
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
So, I recently flashed Omega 10, did a full wipe. Had Omega 8.1 prior. All of a sudden, Im getting "not enough space. free some up" etc. And this is after a fresh flash. So thinking it might be a bug, I wiped again, flashed 8.1 back on and behold same problem. The odd thing is, I can take photos fine, etc, boat load of storage, I just cant open gallery. Installed a 3rd party app called quickpics, that opens fine, but spams me with "cannot open database" messages.
Any idea?
Have tried just going into settings apps/all and wiping the cache for your gallery.
sounds like it may just need to be cleared out.
Yeh, in recovery when I flashed, I wiped SYSTEM, CACHE, DALVIK, BATTERY & DATA. Just finished putting the stock rom back on, and excatly the same issue.
not thorugh CWM......through settings.
you will not be wiping the cache partition of the phone you will be wiping the cache of the app.
and worse case have tried just removing the app, rebooting and placing it back.....it may fix that memory error upon reinstallation if the wipe of the Gallery Cache does not work.
I wiped cache/data of both Gallery and Media storage apps, same thing. Copied the APK for gallery, removed it with rom toolbox, and reinstalled, same thing.
currently restoring to my nandroid backup, see how we go.
Restoring nandroid did the trick.
Good deal, glad it worked out