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.
Hello!
Please help, this is driving me insane.I've had a galaxy S4 for almost a year now. I had it rooted and ****ed around with it a bit, it was all good. Then I was running low on space and got a disk checker or whatever it's called to show me how my space was being used. A lot of it was in caches. I downloaded a file manager and went on a cache deleting spree. One of the caches I deleted was google. Ever since that day everytime I start my phone:
Samsung Link has stopped
Dropbox has stopped
Google + has stopped
Google search has stopped
The phone in general just worked extremely ****ty.So I decided today that it was time for a factory reset. I run it, all good. The phone restarts in factory settings.. and I get the exact same error messages. ?So I decided that I would do the hard reset. Shut it off, volume up + home + power, wipe/delete all data. EXACT SAME PROBLEM. WHAT?How is that possible? I wipe my phone completely and end up with the same problems? How do I reinstall the OS? Since I'm going to be uninstalling the OS completely (probably the only solution to my problems), is there anyway to get a nice clean OS? And not the one full of bloatware from my carrier? I really just want to start over from a fresh OS.
I also tried just running a software update, but I got the error message 'this phone has been modified and cannot be updated'. I guess that's because it's rooted..
Thank you for your help
[Q] need help! how to fix "the process com.android.phone has stopped" error?
I didn't do anything on my g7102, not rooted. It just suddenly happen when i'm trying to call someone. I've tried clearing the Phone cache and data and turn off/on my phone, but the error stil there. Any other way to fix this without doing a factory reset or flash new stock rom? My phone comes with a 4.4.2 version already when i bought it.
bukog25 said:
I didn't do anything on my g7102, not rooted. It just suddenly happen when i'm trying to call someone. I've tried clearing the Phone cache and data and turn off/on my phone, but the error stil there. Any other way to fix this without doing a factory reset or flash new stock rom? My phone comes with a 4.4.2 version already when i bought it.
Click to expand...
Click to collapse
Try clearing phone storage in app manager in settings... if this doesn't work then do a factory reset....
bukog25 said:
I didn't do anything on my g7102, not rooted. It just suddenly happen when i'm trying to call someone. I've tried clearing the Phone cache and data and turn off/on my phone, but the error stil there. Any other way to fix this without doing a factory reset or flash new stock rom? My phone comes with a 4.4.2 version already when i bought it.
Click to expand...
Click to collapse
"... , now we shall here something! ... " -Pygmalion, G.B
Shaw
Sammy started shipping Grand 2s with KitKat ...
@Rahul10
Take a look.
Hi all, I have a D802 with the latest Android Lollipop. Recently, I can't access the phone's setting. Everytime I try launching the Setting app, it will just quickly show an app crash message then jump back to the app drawer. I tried rebooting the phone and would really like to avoid resetting the phone (even soft reset is not possible as I still need access to the Setting app in order to do a factory reset). Any advice? Many many thanks.
i think a factory reset its needed.
I'm trying to help my mother without having her do a factory reset. She has a stock S5, running 6.0.1, unrooted, and while on vacation overseas she started getting nonstop error messages that com.android.phone has stopped. It keeps popping up no matter what is being done on the phone. Tried safe mode, clearing all cache, clearing cache and data on phone and SIM toolkit apps. Also tried installing alternate dialer/phone apps and setting them as default, all to no avail.
I was thinking that perhaps installing an apk of the stock phone app might work, but not sure, nor can I seem to find one anywhere. I do have a rooted S5 running 4.4.2 if there is a way I can pull the apk from there.
Worse case scenario we'll try a factory reset, but I'd like to make sure we've exhausted all other options first.
Thanks
bgg1 said:
I'm trying to help my mother without having her do a factory reset. She has a stock S5, running 6.0.1, unrooted, and while on vacation overseas she started getting nonstop error messages that com.android.phone has stopped. It keeps popping up no matter what is being done on the phone. Tried safe mode, clearing all cache, clearing cache and data on phone and SIM toolkit apps. Also tried installing alternate dialer/phone apps and setting them as default, all to no avail.
I was thinking that perhaps installing an apk of the stock phone app might work, but not sure, nor can I seem to find one anywhere. I do have a rooted S5 running 4.4.2 if there is a way I can pull the apk from there.
Worse case scenario we'll try a factory reset, but I'd like to make sure we've exhausted all other options first.
Thanks
Click to expand...
Click to collapse
Eject the Sim and see if it continues.
Sent from my SM-G955U using Tapatalk
FatalONEM8 said:
Eject the Sim and see if it continues.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Sorry, forgot to mention that I already tried that, and the SD card as well. Waiting to see if she can get hold of a different SIM to somehow "reset" the network.
It's interesting because it basically happened when she traveled overseas, so I'm wondering if that triggered it somehow.
Just as a follow up, she ended up just ditching the phone and getting an S9. Thanks anyway for the ideas.