I'm running the latest version of ACS, and I keep getting a force close loop for "com.sec.android.provider.logsprovider", when I boot. Meaning I tap force close, and it comes right back, giving me no access to my phone. This is after two crashes (using the phone then it turns off). Does anyone have a suggestion? My father's Evo did this too, and he had to scream at Sprint before they'd swap the phone, but it's working fine now. I have the insurance thing on my plan, should I try that? If so, would I have to use Odin first?
Did you try to restore a backup with titanium backup??? I would boot to clockwork recovery and try to fix permissions by going to advanced in the menu.
Already done. I wiped user settings or whatever too. I'm now trying to reflash ACS and it says can't open /sdcard/foo/bar/syndicatefro110-standard-signed.zip (bad) could it be my sdcard? Does Sprint cover those under my hardware thing? I'm using ext4 afaik.
Im not sure if the cover the sd card I want to say no unless it is under a month old. However I wouldnt bring the phone in like that I would odin to a stock unrooted rom. Try to recopy the acs rom to the root of your sd card and then wipe data/factory reset 3 times in clockwork and then try to reinstall the rom.
I've been having issues on all my roms, so I'm thinking it could be my sd card. I'll bring it in as a last resort. Don't want to Odin if I can avoid it. Thanks for the help.
the logs provider has to do with mms and call logs and the sd card shouldn't affect it since it is a system app data/data/com.sec.android.provider.logsprovider. Did you try to clear the dalvik in advanced within clockwork???
That's crazy, I'm having the same exact problem. I was running the latest ACS fine for weeks and then I just rebooted it and BAM, 'Force closes' like crazy!
I reformatted, cleared all cache and factory reset to no avail. I still kept getting the same things pop up. I finally installed it through the zip file the 3rd time and somehow iit's working fine. I lost all my apps and evidently they didn't back up to my google account.
I'm too scared to reboot myphone now since that's what seems to trigger the problem.
Anybody know the source of the problem?
Curious if your getting any oneDram errors in dmesg? Seems like you guys are starting to have those odd errors were seeing in the Bonsai 4.1.0 beta.
Sent from Bonsai 7.0.3
I don't think i saw a oneDram error message, I remember seeing force closes for most of the services or processes that usually run in the background like phone and DRM service.
The persistent force close message that kept popping up was the logs.provider one.
This problem is currently happening to me now
I'm to lazy to fix it now though by the end of the week I'll do something
This happened to me while I had very bad/varying signal
(0-2 bars on a six bar scale)
And low battery
(40%ish)
I clicked on my email app and while it was loading I locked my phone and walked toward a window for better signal
When I looked back at my phone it rebooted by it self and everything is force closing like email and messaging.
Sent from my SPH-D700 using XDA Premium App
Yeah that's very similar to how out started with me too. Actually it might be exactly how it started.
Please let us know what you find out, because I've actually had this problem once before with an ACS rom.
I had my phone do this the other day with the logs provider. Reinstalled the rom (ACS Latest) and the issue went away...
Brother has been having the same issue for weeks on his epic too. He was running Bonsai 4.0.1 getting the same force closes, only his started first when he tried to open his mms app... He installed the latest ACS to see if it was Bonsai, about an hour later got the force closes again until he had an endless loop again.
We checked our memory blocks just for giggles and noticed he has 3 bad blocks while i have 11... cant be the issue...
He would get those force closes on EB13 and DK28 too.
We always do the 3x 3x 3x dance in clockwork before installing a rom too...
Dont know if this info helps or not. He thought about going stock and hitting up a Sprint store today and taking out an insurance claim....
Sorry I missed this thread.
Here's what I want you guys to do.
Back up your sdcard to your pc. ( just the files you wanna save.
Format your sd card with your phone
put the rom zip on your sdcard
Back up everything with your favorite back up program. titanium or mybackup root.
Reboot into cwm make sure it's 3.0.0.6
Wipe data, cache, dalvik 3x's ( don't cheat )
Flash your rom.
Boot your phone.
Restore your back up from your backup program. ( apps only no data )
Reboot into cwm again.
This time only wipe cache and dalvik 3x's ( no cheating )
Reboot and you should be good to go
Sent from my SPH-D700 using Tapatalk
^ This is a guaranteed solution to any unexpected FC problems.
k0nane said:
^ This is a guaranteed solution to any unexpected FC problems.
Click to expand...
Click to collapse
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Top Nurse said:
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
I said for FCs, not bricks.
I'm having the exact same problem with the same ROM. The other day it froze after I took a picture and wouldn't respond. Had to do a battery pull after which I was stuck in an endless boot loop.
Tried just reflashing the ROM from SD and no dice, then cleared all caches 3 times and reflashed and I had a working phone again.
Then about 10 minutes ago I was using the phone and it shut down out of nowhere, after that booted back up with a tone of force closes and now the log provider force close won't go away. I'm just going to switch ROMs cause this is ridiculous.
No need to do that. The solution for freezing is excrutiatingly simple - and if it only freezes when you're in the camera, you need only format your SD card.
Do that, wipe data, and reflash, and everything will work 100% perfectly.
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
darksideauto said:
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
Click to expand...
Click to collapse
As expected - Nandroid bad data, and your bad data will remain. Use MyBackup Root for that.
Just take a Nandroid backup and restore it when you're running properly - or use the zip in the development section to turn journaling on. No problem.
Related
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...
he's done that already.
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger
Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger
Interesting theory.... worth a try.
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger
com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!
Question, Im getting alot of "com.google.process.gapps" force closes on my EVO since I restored a few apps thru Titanium Backup. I rooted about a week ago and never had any issues with this. The only apps that I restored was angry birds and a to-do-list app along with all the data that came with the apps. I have tried cleaning caches and restarting the phone and nothing seems to work... what would you suggest? I seen a few threads when i searched - but they were for the G1 and the Captivate, nothing for the EVO... any help would be appriciated...
TIA
JS3
Did u flash any Rom or Theme??
nope, I rooted and am still using the stock ROM... I was going to flash Frost or some thing, but I want to make sure this doesnt carry over to the flashed ROM, or if there is a fix...I would prefere to fix it...
I am also getting a force close on the phone process.... when some one calls me and I ignore the call it force closes the process for the phone as well...
Try reinstalling the gapps.apk. One of them must of been corrupted by the data you restored.
do you know where I can find that at? I have never heard of it...
Also the thing that is confusing, is I can still access my market, maps, latitude, people, gmail... etc
If the apk or files were corrupted, I wouldnt be able to access those apps... i will try to reinstall the apk, but I would like to know what I did to make this error happen, so I know not to do it again...
one thing I think it could have been was there were two "people" files in my Titanium Back up... One was up near the top it said "People 1.00" and then there was one near the bottom with a line thru it that said "People 1.1.1" or some thing to that effect... I deleted the one at the bottom with the line thru it cause I thought I didnt need it any more... could this be wahts up with this error?
I can still access People thru the People widget, but some times it takes abnormally longer to load my list of contacts...
I can also still access Market, Gmail, Maps, Latitude...
I just clciked on Talk and it seems to be the problem, every time I click Talk it brings up the force close issue...
should I just reinstall the Talk.apk?
I also get "com.android.phone" force close when I decline a call...
when I went into my ROM manager, I clicked the "fix permissions" and it says "error occurred while attempting to run privlaged commands"
Any info on any of this would be great...
Anyone out there
Sent from my EVO while tethered into the Matrix thru Wifi...
Okay well I have googled/searched XDA 'til I was green in the face... I still can't figure out how to fix this issue?
Just answer me this, If I do an entire factory reset - will I loose root?
I have wiped the cache thru recovery, Should I try wiping the delvic-cache also, before I factory reset to see if that works??
I can not find any where to download the "gapps.apk" anywhere, I found this one thread that told me to install these in this order:
1. TalkProvider.apk
2. GTalkService.apk
3. Talk.apk
but none of them worked... they wouldnt even install... it just kept saying install failed...so I found another thread with the 2.2 gtalk and it installed...but Im still getting the error...
I have been getting several other errors, like htc.bgp force close (or some thing like that) as well as com.android.phone force close...
So should I just do a NAND restore or should I do a factory reset instead? OR should I run the RUU and start over to root...??
I am at wits end here and am not getting anywhere with searching...
TIA
I would start with a NAND restore. (Hopefully you have one from before the problem started)
If that doesn't fix it, do a factory reset.
If that doesn't fix it, Factory reset and instal a custom ROM (Sprint Lovers is very close to stock if that's what you like)
I don't think running an RUU is necessary. Once you obtain full Root, you should be able to fix any problem with .apk's or programs on the phone.
Biggest Fro said:
I would start with a NAND restore. (Hopefully you have one from before the problem started)
If that doesn't fix it, do a factory reset.
If that doesn't fix it, Factory reset and instal a custom ROM (Sprint Lovers is very close to stock if that's what you like)
I don't think running an RUU is necessary. Once you obtain full Root, you should be able to fix any problem with .apk's or programs on the phone.
Click to expand...
Click to collapse
Thanks for the input, I was beginning to think I was invisible... lol... I will try that and see what happens...
Well, I went ahead and tried one more thing before I did what you said to do and I think it worked... I went into my EVO while in Disk Drive mode and I cut my entire Titanium Backup folder out of the phone and copied it onto my Desk top. Then I went into my OLD EVO files from the end of the year and I copied the latest folder into my phone. I then went to Charge only, clicked TB and refreshed the app list... Then I was left with a ton of apps that were not installed on my phone. I then went thru each one and restored the ones that were still installed and deleted the ones that were not... (except for the stock apps that came with the phone), so far so good... I will test it more tonight and see whats up, have not gotten any force closes since I finished...
One thing I would like to know tho - where can I get the stock dialer.apk
Some how it got deleted off my new EVO and when I try to load up one of the htc.dialer.apk from my old EVO - the new one does not recognize it... I am currently useing "dialer one" from the market - but I would prefere to make my NAND back up of the Official stock ROM with all the stock apps...any ideas?
EDIT: Okay, fixed the com.google.process.apps issue but did not fix the other force closes... I guess I will have to try the steps above - and worse case - ill just run the RUU and start all over...
I had this problem once and it was related to a widget I downloaded that retrieved missed calls. Don't know if that helps.
Sent from my PC36100 using XDA App
sw99 said:
I had this problem once and it was related to a widget I downloaded that retrieved missed calls. Don't know if that helps.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
But thats the thing - I didnt download anything - I restored two apps, one was opera mini with data and the other was spareparts... then I lost my htc dialer - so I installed Dialer one from the market... I dunno Im just gonna have to do the stpes above and if they dont work - Ill just wipe and run RUU and reroot... no biggie...
Okay I did a NAND restore... then I went thru and set up ALL my apps and settings again and then I did a fresh NAND Backup with clockwork first AND then Amon_Ra... all seemed well except, after I did the Clockwork Backup... I was getting "com.smithmicro.DM has stopped unexpectedly" so searched and read a little and it seemed to have some thing to do with the PRL/Profile updater... so i went into the settings and opened the app manager and cleared the "data" in com.smithmicro.DM and then I restarted the phone and that seemed to fix it... thanks for all the help...
JS3
I have tried flashing a couple different roms, including Bonsai, TrulyEpic Rebirth. I get everything up and running, and a few reboots later, I turn my phone on, and I'm back at the setup screen, where you enter your gmail acct info, and it teaches you how to use the Swype keyboard and everything. I get through all that, and i just have a barrage of "this program force-closed" windows. Everytime I do that, I have to start all over. I've had to do this 5 or 6 times since I got the phone on Monday.
What I do is:
Flash DK28 with Odin.
One-click root/clockwork recovery 3.0.0.5
Let the system do the ext4 conversion
factory reset, clear cache partition, clear dalvik cache 3x
flash rom
restore all my apps
then, a few reboots later, I end up with the setup screen, and the barrage of FC notifications.
Am I missing something?
EDIT: WHOOPS. I'm half asleep and didn't read that right. When you say restore apps, are you restoring a cwm backup or are you talking about the app restoration build into the setup wizard?l
Built in setup app.
I used to have this problem too, it was very frustrating. For me, I finally narrowed it down to somehow corrupting the ROM by using the 3-button instant reboot method. Since I was using the no-journaling mod I figured that somehow I was forcing a re-boot while the system was writing something? I don't really know for sure though, but I can say now that I use QuickBoot and avoid the 3-button method, I haven't had any problems. Good luck!
Thanks. I have yet to try the no-journaling mod, nor do I know what the 3 button method is. I've been using a widget called "boot control", but I'll switch back to quick-boot (i've used it in the past) to see if that helps.
Many months back I did my first rooting of my Epic 4G and I installed the Syndicate Frozen Rom version 2.1.1. Kernal version 2.6.32.9 and Build number Twilight Zone v1.1.1 - Hajime-taisho.
Lately I get this when the phone rebooted:
su binary outdated
When I tried to update it says the updater is incapable of updating my binary since it is installed in /sbin.
That was fine for a while but a few days later I am getting all these popups that say "Sorry! The application Swype (process com.swype.android.inputmethod) has stopped unexpectedly. Please try again. Then gives a force close button.
The MMS process also pops up and several others. I cleared some of the caches last night like I read to do here and it worked over night but this morning it is back and making the phone unusuable.
Tried to go to into CMR and clear the caches there and reboot but that didn't help.
Any ideas of what I can do? Can I reflash the rom without losing all my data?
Thanks for any help you can provide.
Note: Also getting this gapps error. And the phone is just rebooting on its own.
You need to upgrade to the newer superuser. Maybe try going to the market and getting it, or someone here may have the apk for you.
Went to the Market and downloaded the SuperUser Update Fixer and it said it didn't have anything to fix. I updated Superuser, ran the update fix and I am still getting that su binary outdated message. And my phone keeps rebooting.
Another error I am getting is an "acore" process needing a force close too.
Did you clear data in Google Framework Services?
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Did you clear data in Google Framework Services?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks just tried that but still not working. Getting all these force stop windows from acore to mms to gaaps and swype and then it reboots.
Then you are left with Factory data reset and restoring apps from the mrket so you don't restore any corrupted data. Make sure when you get a good working phone again to flash the journal on script.
Sent from my SPH-D700 using XDA App
Hmmmm. OK. Should I do a backup in CMR? I am in the process of doing a Titanium backup right now.
Do you think I should update the ROM or just reflash the one I had before?
Not sure what flash the journal on script is.
ryan4sc said:
Hmmmm. OK. Should I do a backup in CMR? I am in the process of doing a Titanium backup right now.
Do you think I should update the ROM or just reflash the one I had before?
Not sure what flash the journal on script is.
Click to expand...
Click to collapse
Your choice but updated rom* never hurts ..
*/ F u autocorrect
Something had to be corrupted. I flashed Syndicate Frozen ROM 1.2 and a new kernal and was still getting those errors. So I had to do a backup, wipe the phone and then reinstall and that fixed everything. I reinstalled most of the apps and so far no more errors. Thanks for the help!
Hey guys. I've had it with MIUI. and i'm ready to switch to a new rom. i figured now was as good a time as any to try out CM7. So i downloaded the latest stable version, backed up my existing install and flashed. The phone got stuck at the bootscreen. I assumed it was because i neglected to wipe data and cache, so i went back, wiped everything, reflashed and booted into CM7(after an extensive wait)
Everything was running great and i just finished restoring my apps with MyBackup. I was getting FCs on a few apps, but i chocked it up to CM7 not having all the components that some of those apps require. I was about to start removing the offenders when the phone crashed and went back to the bootscreen. It sat there for 2 hours before i pulled the battery and restored back to MIUI.
In short, i really want to try out CM7, but if it's going to be this unstable, obviously it won't cut it. Am i doing something wrong??
Some apps just do not play nicely when being restored from a backup. Can you restore apps 1 at a time so that you only get the apps that you know work? Then re-download the apps that are causing problems.
Possibly. That seems like an unnecessary step though. Would a rom really crash because of app incompatibility? I thought they would just FC every time i tried to run them, not blow up the whole ROM.
If you are using ROM MANAGER you can try to use the utility for "Fix Permissions". I'm sure there is a way to do it in the recovery them selves, but the process escapes me.
This is not an uncommon requirement when restoring from one complex ROM to another.
I had some quirkiness restoring a few apps with Titanium backup. I ended up just reinstalling them from Market and haven't had issues since. Also, after restoring my contacts with Mobile Backup II, I could not edit them from the phone. Force closes. Had to delete them and re-sync with Gmail and exchange server. No problems after that.
I have flashed Synergy, Swagged Out Stock, SavagedZen, and a few others and always wandered back to CM7. In my experience, whenever you switch ROMs like that, there are always quirks, so I have taken to getting apps one at a time from MyBackup Root when I do switch. And yeah, I have had App conflicts cause forced bootloops before, it is not completely unheard of. I second the notion of installing one at a time, and Market DLing any that force loops. And as always, I reccomend a cache/dalvik/data whipe when switching full roms.