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.
Hi all
I've just switched to ICS from the rom uploaded by kwiboo.
everything seems fine except that i can't configure my Google account.
when i try to add an account, i can't see Google account. if i try to add it as a corporate, i always get a message saying "unfortunately, exchange server stopped"
any one faced the same problem ?
Sent from my Nexus S using XDA App
Sounds like you've got a bad zip download or flash. Try wiping system, boot, data, cache and re-flash. Post this stuff in Kwiboo's thread for support.
hmm hey ask around the glaxy nexus people might just be a ICCS bug too
ICS wifi issue
Google account works fine with me, 3G is a bit unstable though.
Been flashin all the ICS betas prepared by drew and on none of them my wifi worked.
Flashed newly published AOSP ICS rom but wifi still refuses to work
It doesn't seem to find any of the networks around me. Any suggestions how to correct that?
Also, i've noticed that battery drain is huge with this rom. 12% off in just 23 minutes.
it happened to me too, when i tried my luck flashing ICS on top of CM7 nightly without wiping data.
it works ok when wiping like we should tho
Wipe it! Should work afterward
Thank you all
I wiped the cache first but it didn't work.
then I wiped the whole thing. It's working now.
thanks again.
Gonizahavy said:
it happened to me too, when i tried my luck flashing ICS on top of CM7 nightly without wiping data.
it works ok when wiping like we should tho
Click to expand...
Click to collapse
is there any way to do this without wipin all the data? maybe wiping just the data for google apps?
Yeah, I simply added my Google account like on any other Android release without any issues
Just upgrade my 16g Nexus 7 to CM10.1 M2. After restart everything is fine but the device keeps on showing "upgrading" on every bounce as if the dalvik cache is getting cleared.
It only takes a few seconds but am noticing that SU shows messages about apps granted root...
Also I noticed my background will from time to time reset to default and my notification icons in status bar don't always show.
Tried to uninstall ti backup, wipe the cache again to no avail.
Upgraded to the latest nightly... Still no luck.
Trying to avoid having to do a full wipe. Any ideas?
samw52000 said:
Just upgrade my 16g Nexus 7 to CM10.1 M2. After restart everything is fine but the device keeps on showing "upgrading" on every bounce as if the dalvik cache is getting cleared.
It only takes a few seconds but am noticing that SU shows messages about apps granted root...
Also I noticed my background will from time to time reset to default and my notification icons in status bar don't always show.
Tried to uninstall ti backup, wipe the cache again to no avail.
Upgraded to the latest nightly... Still no luck.
Trying to avoid having to do a full wipe. Any ideas?
Click to expand...
Click to collapse
Wipe and reflash.
Whenever flashers have odd things happen, it is a common mindset to wipe and reflash. Just be sure you wipe system and factory reset before flashing.
Just seems to be just so much work for what this actually do... Device otherwise works fine.
Trying a different supersu package... Will probably give it a few more days before doing anything since its just so minor...
My Phone.apk is always getting Force close when i'm calling or receiving calls..... i'm using cm-9-20130929 (latest version)
Please,, can anyone give me a solution for this matter
Try wiping cache and dalvik cache. Otherwise use the old nightly.
f3tus said:
Try wiping cache and dalvik cache. Otherwise use the old nightly.
Click to expand...
Click to collapse
And also when i'm receiving a call ,contact icon is filled with half of the screen.....
i have tried this but didn't work - http://deezthomas.com/9-tutorials/10...d-for-cm9.html,,,do u know how to fix diz?
A bit of a weird one.
Updated to CM12.1 Atares ROM :good: I have been running CM12 ROMS for ages and updated to the 12.1 via the OTG in settings and using Nightlies.
I have only noticed problem yesterday and going back to CM12 just causes more problems, also going back to the previous Nightly doesn't help
I cannot access Google Play Store. 'Check your connection and try again' All WiFi settings are correct etc... even when using mobile data, I still cannot get access.
My GT1905 has disappeared off my devices list on the play store too! I've also noticed that Google+ has disappeared off my phone too, but more interestingly my SUBCARD app has gone too! (not sure if others have gone but I noticed this as I like a subway :yum: ) But... if I go to the playstore on my phone (or PC/tablet etc...) via chrome it says it's installed! I cannot access it via my apps list.
So other than doing a wipe of my phone if there any other suggestions?
Did you perform a full wipe before updating?
You cannot just flash it over an old CM 12 you need a fresh install.
Lennyz1988 said:
Did you perform a full wipe before updating?
You cannot just flash it over an old CM 12 you need a fresh install.
Click to expand...
Click to collapse
Well I would of done if it hadn't come via the OTA updates, never noticed it went from CM12 to CM12.1 until Monday/Tuesday last week.
Will do a full wipe later on today and see what happens.
GiGoVX said:
Well I would of done if it hadn't come via the OTA updates, never noticed it went from CM12 to CM12.1 until Monday/Tuesday last week.
Will do a full wipe later on today and see what happens.
Click to expand...
Click to collapse
Custom rom OTA's are not like official rom OTA's. Doing a wipe is still recommended. Anyway, force stopping google play and clearing app cache and data might help you in this case.
Had similar issues on other roms, even though I wiped before flashing.
GDReaper said:
Custom rom OTA's are not like official rom OTA's. Doing a wipe is still recommended. Anyway, force stopping google play and clearing app cache and data might help you in this case.
Had similar issues on other roms, even though I wiped before flashing.
Click to expand...
Click to collapse
I tried clearing all data and cache and also force stopping. WhisperPush kept crashing too.
Wiped the phone and started again, all sorted now with CM12.1 latest nightly build
Cheers for the advice guys.