I'm running the latest version of MIUI, and after an hour or two goes by when using my phone, most of my applications crash upon launch, including messaging, browser, words with friends, titanium backup, ect. The issue is resolved by restarting the phone 3 or 4 times, but after an hour or two they all start crashing again. It seemed to be worse on 1.7.22, but it still happens on 1.7.15. Any ideas?
use cm7 or odin back to stock and then reflash miui again
Yeah I was afraid of that. I'll give it a go.
It happens to me also. So...I'm gonna flash Trigger Redux build 14 soon, but I'll miss all the MIUI goodness.
There's a fix somewhere, it's because the data is full. I completely forgot where. That's why you shouldn't backup data using titanium backup
Sent from my SGH-T959 using Tapatalk
Related
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.
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.
Hello guys, I use google Voice for my Voicemails. Ever since I got my Nexus 4 back in early December I couldn't get it to work. Even on stock without rooting.
I have tried many roms, and factory resets and as soon as I open the app it force closes.
Currently on Xylon ROM 16 and Franco Kernel 33
Gapps 20121212
Any help would be appreciated.
You've tried all the usual fixes right? Wipe app data, fix permissions, uninstall/reinstall the app? Also are you restoring the app & data with Titanium Backup (or something similar)? If you are, uninstall the app and go to the play store and install it from there. Are you restoring any system data with Titanium Backup (or something similar)? Not a good idea to restore system data especially if your changing roms.
In the same boat as OP. Haven't tried any custom ROMs yet. That was gonna be my next move, but it appears to be futile.
I've tried everything. Un install, install... Wiping data and such. And no I am not using Titanium Backup to restore.
Sent from my Nexus 4 using Tapatalk 2
Okay so, I hope this is temporary but I installed the apk with the version 0.4.2.54 and it's working with this one. I tried updating it via the play store and encountered the problem again.
I hope the next update will fix it.
Sent from my Nexus 4 using Tapatalk 2
Ever since my OTA update two days ago, I've had nothing but serious issues with my N7. I was stock rooted before and regularly backed up my files. Since the update, my N7 has been horrendously slow. It takes forever for any of the app icons or widgets to load. I just re-rooted tonight and have been waiting now for 17 minutes, and still the pages haven't properly loaded; they're all still blank. When opening apps, it'll either be so slow that I get the message saying either to wait or just close it. Other times when trying to open apps, it'll just hang indefinitely. Swiftkey is pretty much unusable, it's so slow. Everything is just so frustratingly slow now. How can I fix this? Is anyone else having this problem? 4.3 has been nothing but a nightmare for me. It's made my N7 unusable.
Lakilaulea said:
Ever since my OTA update two days ago, I've had nothing but serious issues with my N7. I was stock rooted before and regularly backed up my files. Since the update, my N7 has been horrendously slow. It takes forever for any of the app icons or widgets to load. I just re-rooted tonight and have been waiting now for 17 minutes, and still the pages haven't properly loaded; they're all still blank. When opening apps, it'll either be so slow that I get the message saying either to wait or just close it. Other times when trying to open apps, it'll just hang indefinitely. Swiftkey is pretty much unusable, it's so slow. Everything is just so frustratingly slow now. How can I fix this? Is anyone else having this problem? 4.3 has been nothing but a nightmare for me. It's made my N7 unusable.
Click to expand...
Click to collapse
Try booting recovery and clearing the cache. But I really don't know if that'll work.
Otherwise you can trying factory resetting and restoring from one of your backups.
If that still doesn't work you could download a stock 4.3 image and flash it. Then restore your backup.
Sent from my Nexus 7 using xda app-developers app
theaftermath said:
Try booting recovery and clearing the cache. But I really don't know if that'll work.
Otherwise you can trying factory resetting and restoring from one of your backups.
If that still doesn't work you could download a stock 4.3 image and flash it. Then restore your backup.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i was rooted / open bootloader made a huge mistake re-locking the bootloader without backup lol duh:silly: so it wiped the whole tab went to 4.2.2 locked bootloader and non root. so i just ota updated to 4.3 re-installed any apps that i remember and google didnt automatically download. now i have a fresh system with no crap all over the place in the files and lots of storage ..... i will fill it with crap again lol but yeah now rooted 4.3 smooth as hell and fast as f***
Lakilaulea said:
Ever since my OTA update two days ago, I've had nothing but serious issues with my N7. I was stock rooted before and regularly backed up my files. Since the update, my N7 has been horrendously slow. It takes forever for any of the app icons or widgets to load. I just re-rooted tonight and have been waiting now for 17 minutes, and still the pages haven't properly loaded; they're all still blank. When opening apps, it'll either be so slow that I get the message saying either to wait or just close it. Other times when trying to open apps, it'll just hang indefinitely. Swiftkey is pretty much unusable, it's so slow. Everything is just so frustratingly slow now. How can I fix this? Is anyone else having this problem? 4.3 has been nothing but a nightmare for me. It's made my N7 unusable.
Click to expand...
Click to collapse
try completely wipe your device, make sure you backup everything you need to the emulated /SDCARD and back that up onto your PC. Then do a fresh reinstall. Also check background apps, some malware might be the problem
chismay said:
i was rooted / open bootloader made a huge mistake re-locking the bootloader without backup lol duh:silly: so it wiped the whole tab went to 4.2.2 locked bootloader and non root. so i just ota updated to 4.3 re-installed any apps that i remember and google didnt automatically download. now i have a fresh system with no crap all over the place in the files and lots of storage ..... i will fill it with crap again lol but yeah now rooted 4.3 smooth as hell and fast as f***
Click to expand...
Click to collapse
Well there you go. I also made the mistake of relocking once upon a time.
Sent from my Nexus 7 using xda app-developers app
So I backed up all my stuff through Titanium Backup to Dropbox and did a factory reset. After reinstalling everything, I reboot the device. Now it won't get past the colored X. What do I do now?
PROBLEMI have been using my oneplus two for like 2 months and i did not face any issues. After the latest 2.1.2 update, after a few days my apps started crashing. Only a few did not crash, my Facebook, messenger, uc browser, 9gag and all my games crash, when i open them their is either a black or white screen and then it crashes
THINGS I DID first i booted into stock recovery and wiped data and cache. This did not work and the problem still Persisted.
Then i factory rest my phone. This worked and all my apps were back to normal. Untill it happened again today and i do not want to go through the hassle to factory reset again.
Is anyone facing these issues?
Can any dev get me a solution for this problem.
Richard322 said:
PROBLEMI have been using my oneplus two for like 2 months and i did not face any issues. After the latest 2.1.2 update, after a few days my apps started crashing. Only a few did not crash, my Facebook, messenger, uc browser, 9gag and all my games crash, when i open them their is either a black or white screen and then it crashes
THINGS I DID first i booted into stock recovery and wiped data and cache. This did not work and the problem still Persisted.
Then i factory rest my phone. This worked and all my apps were back to normal. Untill it happened again today and i do not want to go through the hassle to factory reset again.
Is anyone facing these issues?
Can any dev get me a solution for this problem.
Click to expand...
Click to collapse
Same for me! Some days the app crash and other days they boot... I don't know why...
davidelolli said:
Same for me! Some days the app crash and other days they boot... I don't know why...
Click to expand...
Click to collapse
Did you find any solution for it?
Same here updated to 2.1.2. my gmail crashes after opening any mail.i was gone mad through formating and settings up my OPT daily one or three times.i have sent email to google but no reply.
After one week i have decided to root my OPT.i have rooted and installed Unofficial Temasek Based CM 12.1(ROM @ WebCS).Believe me it has no any crash and best rom i have ever used.this rom has 2 bugs.fingerprint sensor and laser autofocus.
After using CM 12.1 i have restored my nandroid backup of oxygen OS.
Now all the app crashing has gone.i am using OPT as my daily driver.