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.
Related
I don't believe Ive seen this mentioned anywhere yet, so I figured Id remind those who know, and inform the newbies who don't know.
Ive heard people who have applied various lag fixes complain that their phone slows down over time when opening apps. This "fix" i am about to mention is really easy and can help anyone not just those who have problems with an applied lag fix.
If you open Rom Manager and use Fix Permissions, wait for it to finish, then select Reboot to Recovery, and wipe Cache, and then go to Advanced Settings, and wipe dalvik cache, then reboot normally, your phone will hang at the Galaxy S bootscreen for a few minutes, it might take a while because it is rebuilding the dalvik cache, you should notice things running smoothly again and apps opening quicker.
Hope this helps anyone out there!
Does wiping those 2 cache's screw up installed apps? Where you have to download them all again?
Bronk93 said:
Does wiping those 2 cache's screw up installed apps? Where you have to download them all again?
Click to expand...
Click to collapse
No, wiping the caches shouldn't affect your installed apps.
And all the same, if you still worry about it, just run a nandroid backup before you wipe the caches, then if you run into any issues, just restore, or advanced-restore only your data partition.
cheers,
=)
~ Jocelyn
So not a big deal cause I have replaced my update.zip with the clock work reboot update.zip and can reach clockwork still by "reinstalling packages" but I tried this fix and now can't reboot into recovery straight to clockwork through rom manager cause it says something to the effect of
E: can't reboot cause file /cache/update.zip missing
(bad)
Click to expand...
Click to collapse
Not exact but obviously there was a vital cached update.zip that was used in order to reboot directly into clockwork through rom manager.... Any idea on a fix? Think it would be unwise to just reflash clockwork through rom manager again to recache the file? Would anything else be effected like possibly overwriting my past nand recoveries? Thanks guys/gals for any help on this one.
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
Bump for the safety of reflashing clockwork to replace cache file?
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
p()()pypants said:
Bump for the safety of reflashing clockwork to replace cache file?
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
Click to expand...
Click to collapse
yes, your missing the update.zip that unzipps itself to run clockwork. So yes flash the update.zip again through rom manager.
I just creates the update.zip file so it will not do any harm.
Awesome I assumed just as much but wanted confirmation first, thank you much
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
I've done this, and it worked just fine.
Thanks OP!
it worked perfectly, thanks
speedysilwady said:
I don't believe Ive seen this mentioned anywhere yet, so I figured Id remind those who know, and inform the newbies who don't know.
Ive heard people who have applied various lag fixes complain that their phone slows down over time when opening apps. This "fix" i am about to mention is really easy and can help anyone not just those who have problems with an applied lag fix.
If you open Rom Manager and use Fix Permissions, wait for it to finish, then select Reboot to Recovery, and wipe Cache, and then go to Advanced Settings, and wipe dalvik cache, then reboot normally, your phone will hang at the Galaxy S bootscreen for a few minutes, it might take a while because it is rebuilding the dalvik cache, you should notice things running smoothly again and apps opening quicker.
Hope this helps anyone out there!
Click to expand...
Click to collapse
Thank you! Am trying this now and will post any impressions after.
EDIT: Immediately after re-booting, it definitely seems smoother and snappier - thanks again for this. I was wondering if I should do something like this, but didn't know what, because I'd flashed Eugene's Vibrant6 and a lag fix and then restored to my pre-flash nandroid. I thought the phone's performance was suffering after all that, and I definitely found this tip helpful, so really appreciated!
I am running BAMF gingerbread and for some reason, my lockscreen does not appear whenever i wake my phone up. I tried running other gingerbread roms and the same problem happened. I always wipe the phone plus the cache.
Why isn't my lockscreen showing up?
I have kinda that prob when I reboot my CM7 rom while plugged in.
Sent from my ADR6400L using XDA App
Do you think its a problem with gingerbread roms or just my phone?
You checked all the settings? Tablet tweaks? For cm7 its under tablet tweaks but Idk if your rom has that.
Yes I checked all the settings, nothing about a lockscreen option.
Hmm I will check out some info. You can always download a lockscreen app if it doesn't get resolved.
It works sometimes and then sometimes it doesn't, I don't get it. Thank you for the help man, appreciate it.
Not a problem. I would try booting to recovery and wiping cache. Then reboot. See if that works. You can reflash rom and clear cache/delvik cache if you need. Good luck. Hope it is resolved.
I've wiped all the cache and the data. The last rom I was running had this problem, and the one before that it would sometimes not come up but not as bad as this.
I have no idea what the problem could be.
I realize you said that you wipe data and cache before installing but are you by any chance restoring any system data with TitaniumBackup? Restoring some system related stuff (red or green. I think it's the green Settings Storage one but I haven't looked into it personally.) has been known to cause issues such as the lockscreen, home and search keys not working.
Absolute_Zero said:
I realize you said that you wipe data and cache before installing but are you by any chance restoring any system data with TitaniumBackup? Restoring some system related stuff (red or green. I think it's the green Settings Storage one but I haven't looked into it personally.) has been known to cause issues such as the lockscreen, home and search keys not working.
Click to expand...
Click to collapse
Nope, I don't even have titaniumbackup on my phone.
it is a gingerbread problem,you can either reflash your rom to get it back or use a car dock to unlock it and change your lockscreen the change it back,if it is not there use rootexplorer to copy it from the rom to your system/apps folder set permissions reboot then change it back,just happens that the lock screen disappears never got an answer as to why but that is how I have fixed it everytime
Sent from my ADR6400L using XDA Premium App
I recently flashed over to powerwash 1.2 and ever since then none of my data gets saved at all. Like when I reboot all my apps are there but when I use one of them it is like its brand new and have to reenter my info. I tried re-flashing, wiping the data everything and nothing seems to work. Any fix's?
Never mind i got it all sorted out now finally. Mods can close this thread
Did u wipe dalvik cache and system?
Sent from my SCH-I500 using XDA App
Hello all
How often should you clear cache or fix permission using CWM?
Jim
Sent from my VEGAn-TAB using XDA
Personally I do it when ever the ROM that I am on starts acting a bit quirky. Which is not very often if you are running a stable build like VeganTab, CM7 or even the Froyo ROMs that have been out for a while. If you ever see yourself loading up a bunch of apps and running them allot. Over time you might would want to clear the cache and definitely fix permissions to get things back in order.
jweir said:
How often should you clear cache or fix permission using CWM?
Click to expand...
Click to collapse
They're not something you need to do often, or even occasionally, as part of some preventive maintenance regimen.
If you switch ROMs, then you will have to clear cache. Actually, it's best to do a "wipe data/factory reset" in CWM in this case--cache will get formatted in the process.
You would want to clear cache if you upgrade the current ROM; it is better, though, to instead wipe dalvik-cache. Similarly, if you upgrade an app manually--ie. not via the Market or the usual Android update process: eg. by overwriting an app in /system/app or /data/app and rebooting the system--you might want to clear cache.
You might have to clear cache after powering on the tablet after a long (weeks, months) period of inactivity. In this case, the battery will go flat and the system will lose its date and time--going back in time, so to speak. This might, in turn,cause cached data to go out of whack--though Android should take care of this normally.
The "fix permissions" step is needed even less. This link explains why you would want to use it: Again, it might be needed after a ROM update, and not otherwise. This means that doing a fix permissions after a SD card repartition or a wipe data/factory reset step is nonsensical--the fix_permissions script operates on existing data.
Hello!
Norwegian Noob here. I got the basics, nothing more.
I just used Link2SD to clean cache and to clean Dalvik Cache, and i may also have cleaned 2nd partition garbage.
Then i rebooted, and nothing happens. it just kept staying at the white "HTC" -screen over the night (gave it some time).
The morning after i went into CWM to wipe dalvik cache and clean cache. Then at reboot it needs some time (10min, i guess dalvik buildup?).
When its done and it gets to the "desktop", the apps just say "loading".
When i try to do something at all, i just get message saying for example "sorry, settings (process com.android.settings) stopped. try again".
Some apps can be used, like go sms pro, clockwidget, flashlightwidget, but no other apps like calculator, calendar, tapatalk.
Now if i try to reboot, it just keeps staying at the white HTC-screen. Then i have to take out battery, boot into recovery, delete dalvik cache again, and reboot. then the same thing happens again.
I would be happy for any suggestions i can get (and sorry for my bad english:laugh: )
My system:
HTC Desire A8181
Android 2.3
Cyanogen 7.2.0.1 (if i dont remember completely wrong, cant check as process crash)
Additional info; link2sd may have been automatically installed to SD, and may not have been moved to phone by me before i wiped dalvik via link2sd-settings.
No one with any suggestions?
Have to delete everything and install rom again if i cant solve this :-\
Sent from my GT-S5690 using Tapatalk 2
Sounds like you did more than delete just your cache and dalvik, couldn't say for sure but my guess is you have some apps or at least data installed in a partition you erased.
You will almost for surely need to wipe all and flash ROM or backup. You can try to fix permissions in recovery but I doubt it will help.
Sent from my Nexus 4 using xda premium