Related
I've used Cyanogen Mod for quite a while without issue. Then, last week my camera started force closing. So far as I knowing didn't change any settings or install an app that would mess with it. Haven't updated radios, etc...it just stopped. I've cleared the cache in apps settings, there is space on the card.
Any suggestions? Thanks!
clear cache and dalvik from recovery, and reboot. If that doesnt work, you will probably have to reflash the rom.
sitlet said:
clear cache and dalvik from recovery, and reboot. If that doesnt work, you will probably have to reflash the rom.
Click to expand...
Click to collapse
Do I need to back anything up before doing this? Thanks.
Sent from my PC36100 using Tapatalk
polkadots said:
Do I need to back anything up before doing this? Thanks.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Shouldn't lose anything, as you are just clearing cache files. However, it can never hurt to do a backup first, only takes a couple minutes.
Ugh. I did a full wipe and upgraded to 7.1 (was on 7.0.2)...Camera is still FC'ing...again, it works with other apps (Vignette, Goggles) but not the stock camera. It worked just fine until two weeks ago...and then, nothing. No clue why. :/
Well, now it works...I did one more wipe and it just started working. Thanks!
Try fix permissions, worked for me
Sent from my PC36100 using xda premium
hi everyone. ok here's my problem, yesterday i installed acs ics 5.5 rom, then i nandroid restored the ei22 deodexed stock just to test the nandroid restore, just to see if it worked for me. i then again flashed back to the ics 5.5 rom, and this morning i nandroid back to ei22 again, because i wasn't happy of the non - 4g function.
anyways, later on today i decided to go into "my files" and delete 3 of the 4 nandroid backups that i had. because i believe the 3 that i deleted were bad. well after i did that, i started getting apps force closes, and now i can't open gtalk or my text message app.
if i do a factory reset, should that fix the problem? before i turn to odin and perform the whole process all over again?
NOTE - everytime i did the restores and flashes, i did do a pre-rom wipe with acs recovery.
androidmaster1 said:
hi everyone. ok here's my problem, yesterday i installed acs ics 5.5 rom, then i nandroid restored the ei22 deodexed stock just to test the nandroid restore, just to see if it worked for me. i then again flashed back to the ics 5.5 rom, and this morning i nandroid back to ei22 again, because i wasn't happy of the non - 4g function.
anyways, later on today i decided to go into "my files" and delete 3 of the 4 nandroid backups that i had. because i believe the 3 that i deleted were bad. well after i did that, i started getting apps force closes, and now i can't open gtalk or my text message app.
if i do a factory reset, should that fix the problem? before i turn to odin and perform the whole process all over again?
NOTE - everytime i did the restores and flashes, i did do a pre-rom wipe with acs recovery.
Click to expand...
Click to collapse
Someeone just posted a similiar issue they associated with the8ir sd card.
They said after nand bkp they had fc's and no apps on sd showed. Wiping cache and dalvik would be pre factory default wipe imho.
Sent from my SPH-D700 using XDA App
Yes, a Factory data reset will clear the FCs. But you will lose 3rd party apps and anything you have set up will have to be set up again. If you have a nandroid you can trust you can do an advanced restore data to get those things back.
Sent from my SPH-D700 using XDA App
so does that mean that i have to go into recovery and repartition the sd card?
update - heres what it says on bootup - UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.
WHAT DOES THAT MEAN?
androidmaster1 said:
update - heres what it says on bootup - UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.
WHAT DOES THAT MEAN?
Click to expand...
Click to collapse
No idea but sounds like you need to do a factory reste
sent from a phone using an app
Djinn23 said:
No idea but sounds like you need to do a factory reste
sent from a phone using an app
Click to expand...
Click to collapse
None of that will touch your sd card. And you don't need to. The errors are in phone memory.
kennyglass123 said:
None of that will touch your sd card. And you don't need to. The errors are in phone memory.
Click to expand...
Click to collapse
+1
sent from a phone using an app
ok, here is the update to what's happened. last night i odin back to ec05 and redid the process again for updating and rooting, and now everything works ok.
i don't know what happened, but it was so bad, that i couldn't even use my phones dialer to make a call. but the problem is fixed. THANKYOU EVERYONE, for your help, i really appreciate it.
androidmaster1 said:
ok, here is the update to what's happened. last night i odin back to ec05 and redid the process again for updating and rooting, and now everything works ok.
i don't know what happened, but it was so bad, that i couldn't even use my phones dialer to make a call. but the problem is fixed. THANKYOU EVERYONE, for your help, i really appreciate it.
Click to expand...
Click to collapse
Awesome good work. Just out of curriosity...did you try the reccomendations here? What were the results?
Glad u got it up and thanks for the update.
sent from a phone using an app
yes i did. i did a factory reset and wiped the cache partition and dalvik cache, and still nothing. somehow after i deleted the 3 nandroid backups, things got messed up. i kept getting errors of framework and gapps process issues. i don't know what could have caused it, but it wasn't pretty. at least i was able to get it fixed with odin.
question regarding this type of issue though, if i would have checked marked re-partion along with the reboot, what would happen? cuz i was really tempted to do so, but i didn't, given the fact that i didn't know exactly what would happen.
If you check repartition you need to include the PIT file which is the map of the partition for our phone. That will put your phones partition back to what it was when new.
ok, and where can i find the pit file? sorry again for the dumb question, but this is the part that is very new to me.
androidmaster1 said:
ok, and where can i find the pit file? sorry again for the dumb question, but this is the part that is very new to me.
Click to expand...
Click to collapse
No problem, we are here to help. The PIT file should be packaged with Odin so when you unpacked it into a directory it should be there. Victoryxxxxx.PIT
ohh yea, i have that file. so that's what that file is for. ever since i got odin and started using it, i've bee wondering what that file was for. ok, so, in what type of circumstances can i use that file? like what happened to my phone yesterday? or what?
just so i have an idea of when i should use it.
When in doubt you can always use the PIT and repartition. F.reset resets all the clocks in the phone so there is no need to fear if you accidentally leave that checked.
I'm having the same issues here. Once I flash a rom, after a week or two I get this FCs but I notice this usually happens when I swap batteries or restart my phone. Once I flash a new rom or same rom everything works just fine until I have to swap or restart my phone.
What's causing this? Mine friend epic is having the same issue and he is getting tired of the phone to the point of putting it for sale. Is there a way to fix this?
Sent from my SPH-D700 using XDA App
lepapirriky said:
I'm having the same issues here. Once I flash a rom, after a week or two I get this FCs but I notice this usually happens when I swap batteries or restart my phone. Once I flash a new rom or same rom everything works just fine until I have to swap or restart my phone.
What's causing this? Mine friend epic is having the same issue and he is getting tired of the phone to the point of putting it for sale. Is there a way to fix this?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
You are not shutting down correctly causing bad data writes to your phone. Turn power off, after the vibration make sure keyboard lights are off before you pull battery. Also make sure you have journaling enabled.
Sent from my SPH-D700 using XDA App
I have used marcusant and sleeper rom at the moment, and they usually shut downs completely with the screen, but yes I make sure the light on the kb are shut. I don't know much about journaling, I guess I have to read about it.
Sent from my SPH-D700 using XDA App
lepapirriky said:
I have used marcusant and sleeper rom at the moment, and they usually shut downs completely with the screen, but yes I make sure the light on the kb are shut. I don't know much about journaling, I guess I have to read about it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Then it is strange that swapping batteries would cause any kind of data corruption. I believe those ROMs have journaling on by default. FCs are usually easy to fix. Most times it is a Google Services Framework error. This can be fixed using Titanium Backup and scrolling to Google Framework Services, select it and choose wipe data. Do that for any other app that FCs as well.
Sent from my SPH-D700 using XDA App
As the title states... Dialer keeps force closing.. Can't make or receive calls. Everything else works fine.. wifi and all apps... This started after I flashed CM7 kang 2. I have tried wiping phone and reinstalled Juggernaught but I still get the same error's. Once I try dialing the screen will go blank. The call will go through to the phone I call but I can't hear them and they can't hear me. Then com.android.phone will FC. The phone stays connected though. I have to actually reboot the phone or the call won't end.... Any help would be appreciated, or any ideas to try. Thanks
Anyone have any ideas ???
Try pulling the phone apk from ur ROM zip and pushin to sys app
Sent from the horsemen of death using the galaxy at his will
Maybe try using tdj' s super wipe script. Its in the dev section. Sounds like something got out of whack. After running the script you will need to reflash your rom.
Sent from my SGH-T989 using xda premium
I ran tdj Super wipe and then flashed jugernaut and still have the same problem. I wonder if it's possible the CM7 Kang install caused a hardware issue.. Hope not as I really do not want an expensive paperweight...
Look for ROM Manager on the market. There's a feature that lets you fix file system permissions. That should hopefully help you with your force close issues.
Sent from my SGH-T989
already did fix permissions with rom manager. DID Not Help
Racing19969 said:
already did fix permissions with rom manager. DID Not Help
Click to expand...
Click to collapse
Did you flash a radio?
Sent from my SGH-T989 using xda premium
download a different dialer app from market and see if that helps
F Odin to stock with a proper pit file (if available). Odin the default modem. There's no way it won't work after that.
Sent from my SGH-T989 using xda premium
Try clearing cache then dalvick cache then run fix permissions and reboot sometimes works.
If not backup and format data and system and flash ROM zip (download and save ROM zip to sdcard before formatting /system)
It usually is a corrupt system file sometimes happens to me with lots of tweaking and testing LoL
Sent from my SGH-T989 using Xparent Green Tapatalk
got this after a reboot... must have done something wrong... =P Anyone know what this is and how I can get rid of it?
Playing with the dialer codes?!
From recovery clearing cache an dalvik I think will get rid of that.
Sent from my SGH-T999 using xda app-developers app
didn't seem to work.. any other suggestions? you think flashing to stock with odin will help? i tried to flash a stock rom with clockwork mod but didn't help... flashing to a jelly bean rom did get rid of it though... but would like to know what's causing this
Factory reset?
My unicorn died, back on the pony.
Only time I've ever seen that was after testing dialer codes.
Can't remember for sure how I got rid of it but I thought it was by cleating dalvik. May have had to factory reset or reflash rom though.
Sent from my SGH-T999 using xda app-developers app
Okay figured it out.
http://forum.xda-developers.com/showthread.php?t=1703175
This is something that's bothered me since upgrading to 4.1.1. Doing just what the title says. So far, I've tried clearing the dalvik cache, wiping the cache partition, uninstalling titanium backup and restarting, as well as uninstalling ROM toolbox and lucky patcher. I'm rooted with chainfire's "quick" method but I also had root before upgrading from ICS. I also tried bin4ry's universal ICS/Jellybean method after upgrading before finding chainfire's, witch, I am suspicious of bin4ry's causing the bug in the first place. The message shows briefly after the glowing "Samsung" boot animation. I have scoured to the bottom of the internet looking for an answer, but I really, really do not want to re-flash the stock rom again. Any reason why this happens? Any way to fix it without wiping my phone; if that works?
Sent from my SAMSUNG-SGH-I747
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Any reasons why this happens?
Mine is doing the same thing.
peneoark said:
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
It's not wiping the dalvik cache. The system displays the message briefly with no application count. I just assumed it was normal on 4.1.1
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Several people seem to claim otherwise, Google shows. My tenant's and several of my friend's phones don't do it. I'll try reverting to factory and upgrading again in a few days if there are no other solutions.
Sent from my SAMSUNG-SGH-I747
Mine showed up after the Google wallet mod. Also had it happen after removing some stock apps although I'm not sure which caused it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've removed a lot of at&t's bloatware, along with S-Suggest, "help" and ypmobile. I've also frozen s-voice and the samsung keyboard in favor of SwiftKey. I've removed bloatware in both so far. Maybe once I revert, I'll try to find out more about the problem. Until my phone is sick of the cache partition wipes and ruthless dalvik cache destruction, I will continue to try in vain. For the good of my OCD.
Sent from my SAMSUNG-SGH-I747
Many ROMs and Kernels are set to ziplalign apps on boot to improve performance.
I want to say this was also implemented in stock JB, or its set in CWM's init.d script for the newer versions.
This also happens each time you wipe dalvik and/or if you have Titanium Backup set to intergrate sys dalvik into ROM
I just did the HOWTO root after upgrading to stock JB, and after reading this post I did a quick reboot and yeh, the message appears for me as well.
Never integrated sysdalvik w/ titanium backup. I've also rebooted the phone without clearing dalvik, and never had cwm. Probably a few things I should have mentioned earlier, but they never crossed my mind.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Fixed the problem. Turns out you do need to re flash the whole phone. Reset to factory in recovery, then wipe the cache AND the dalvik, then reset to stock using ODIN. IT IS IMPERATIVE THAT YOU RESET TO FACTORY. The phone will remain soft bricked otherwise. A tutorial can be found here: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/. The only tried and true way to get the bug out. As far as I know. If anyone has any more ideas as to how this problem occurs, I'd still like to hear them.
Sent from my rooted SAMSUNG SGH-I747. THANKS CHAINFIRE!!
I rarely reboot these days. I do my CWM backups online.
But when I do reboot, I do get that updating message and have been seening that from as far back as I can remember. It bugged me at first but not now. For me, it only does it for about 2-4secs so I don't bother trying to fix it.
I have the cause in my case but I don't have the solution. I flashed a mod I found here http://forum.xda-developers.com/showthread.php?t=2044449, apn_editor_1.1.zip. Now every reboot I get Android Is Upgrading.... Starting apps.
How do I stop the phone from trying to add this mod?
Just got the same problem. Had super SU on the phone (soft root), so i tried to fully root (i installed xblasttools, and had to flash pa-icons, so i could change the color of the battery, but i couldn't because it said signature failed). Downloaded philz kernel/root, flashed with recovery. Then i uninstalled the Super su rebooted and there it was; Andriod is upgrading ...
I'm on 4.1.2, Samsung GT-i9100. Help !
P.S Uninstalled the superuser that i got with the phil kernel and installed Super SU. Also i did wipe the davlik and cache. Same stuff.
I got the Android is upgrading message before. It was because I tried to convert a user app to a system app. Converted it back to a user app and it went away. I think it had something to do with having an apk file but no corresponding odex file for that app in /system/app
Sent from my SGH-I747M using xda app-developers app
I have found why this happens, issue is with lucky patcher, when you patch application it creates <appname.odex> this odex file is somehow diffrent than real odex, so when you wipe dalvik cache it caches all your apps and then you have Android is starting apps on each boot. The solution is to delete all apps odexes wich you patched, reboot phone, this time it will not display "android is starting apps" and will work until you delete dalvik again. It is possible to apply patch with Lucky Patcher to dalvih cache instead of creating odex, but you loose your crack when you wipe dalvik again.
This is the solution, if someone have better way of doing it post here, also sorry if thread is old.
magix01 said:
I have found why this happens, issue is with lucky patcher, when you patch application it creates <appname.odex> this odex file is somehow diffrent than real odex, so when you wipe dalvik cache it caches all your apps and then you have Android is starting apps on each boot. The solution is to delete all apps odexes wich you patched, reboot phone, this time it will not display "android is starting apps" and will work until you delete dalvik again. It is possible to apply patch with Lucky Patcher to dalvih cache instead of creating odex, but you loose your crack when you wipe dalvik again.
This is the solution, if someone have better way of doing it post here, also sorry if thread is old.
Click to expand...
Click to collapse
Thank you for pointing out Lucky Patcher. The "android is starting apps" notification started when I deodexed my rom. I uninstalled those patched apps, reinstalled and re-patched normally with Lucky Patcher 3.9.9.1 and that notification is gone.
:good:
coffee black said:
Thank you for pointing out Lucky Patcher. The "android is starting apps" notification started when I deodexed my rom. I uninstalled those patched apps, reinstalled and re-patched normally with Lucky Patcher 3.9.9.1 and that notification is gone.
:good:
Click to expand...
Click to collapse
Next time just cut odex files to other location, reboot phone and copy odexes back, this should be alot easyer
Try to reflash your rom that may help some how
Sent from my GT-I9500 using xda app-developers app