Related
the process android.process.acore has stopped unexpectedly
it keeps FCing and restarting on its own, make the phone un-usable because everytime i try to press a button, it will freeze, put up this FC, and when i click "force close" it will close what i was trying to open, and the cycle starts over again
i'm stock with the new JI6 update via KIES mini, had no problems for 3 days, and last night the phone ran out of batteries while i was out of the house and when i got back, i plugged it in, turned it on and i got this FC as the phone was doing the start-up media scan thing.
it will show this FC everytime i reboot as well
under settings -> manage applications -> running services there is a service called 'contacts storage' which is governed by android.process.acore
that's the only other clue i could dig out
*edit* mine doesn't seem to have anything to do with facebook, however, i can't access my contacts as everytime i try, this FC will force me out of the contacts screen
I've seen them a lot of times. When I get them, I just re-flash a new ROM onto my phone. It usually happens when I do something stupid to my phone.
i didnt do anything to it! everything was working, even after i updated to JI6 ... nothing was broken till it ran out juice yesturday.
I'll get this when I do a Titanium restore and restore the system data by mistake.
This should be in Q&A not development.
Also, try clearing your caches in Clockwork Recovery
Sent from my SGH-T959 using XDA App
Hello,
This is really annoying. It is the 5th time it happened to me since i bought my Dell Streak. Using the Power Control widget, i choose the bluetooth, and it shows an error message saying : "Sorry ! The application Settings (process com.android.settings) has stopped unexpectedly. Please try again." . The last time i had this, i had to do a factory reset. Somebody on internet had indicated to install the bluetooth widget. Yes, with it i can stop the bluetooth. But as soon as i start it again, the same message will be shown. I tried to reboot, remove the battery, etc... but nothing, still the same problem. Is there any solution for this? I hate to do another factory reset.
I am on 2.2.2, build 15609, rooted, that's it. Help is really appreciated. Thanks in advance
YD
youbethor.detzatze said:
Hello,
This is really annoying. It is the 5th time it happened to me since i bought my Dell Streak. Using the Power Control widget, i choose the bluetooth, and it shows an error message saying : "Sorry ! The application Settings (process com.android.settings) has stopped unexpectedly. Please try again." . The last time i had this, i had to do a factory reset. Somebody on internet had indicated to install the bluetooth widget. Yes, with it i can stop the bluetooth. But as soon as i start it again, the same message will be shown. I tried to reboot, remove the battery, etc... but nothing, still the same problem. Is there any solution for this? I hate to do another factory reset.
I am on 2.2.2, build 15609, rooted, that's it. Help is really appreciated. Thanks in advance
YD
Click to expand...
Click to collapse
I am having the same issue Even though I did a factory reset. The problem persists!
So please help me ...
some great people out there
Just wanted to respond to this thread and express thanks that there are some great altruistic people out there. My Dell Streak had the same problem of being unable to access settings/wireless. Googling and distilling advice, the way that avoided a nightmare factory reset for me was a combination of Free Power Widget by BK Mobility and APN Backup and Restore by Ritesh Sahu, both free from Android Market. I backed up the APNs then deleted them. I put the Free Power widget on my desktop and was able to deactivate and activate my wifi. I was able to then access settings/wireless again but (obviously no APN settings) so exit and restore the APN settings fron Ritesh' app. And all is right with my mobile world again and a big thank you to the developers of these 2 apps. Now off to Android Market to give them top ratings.
Permission repair often helps with these kinds of issues.
I am using dell streak 2.2.2 with streakdroid 1.9.1
After using it for 3-4 days everything started force closing.
For eg.-
process com.google.process.gapps
process com.android.mms
process com.google.android.gm
process com.cooliris.media
etc etc....
I factory reset my phone nd den tried it again but again the same problem after 2 days..And a lot of other downloaded apps also start force closing. I am fed up of factory resetting my phone again and again.
Thnx..
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
Hello
I've had a Samsung Galaxy S3 for ages, unfortunately for me, the phone recently just switched off, then on, then won't go past the "Samsung" screen. Ah, I thought (well, something a bit more sweary) - but I had a backup identical model phone in case one broke, so I started using that. Moved all my apps, installed banking app etc, and then happy.
Or so I thought...
The new (well, it's an old phone, but one I haven't been using, bought as back up) phone now switches off when charging every night, an issue which was going to switch to me charging it during the day when I can stare at it and see if anything happens to make it switch off, but then I realised it switches off each night even when it isn't charging.
I have a bigger battery to hold a charge for a few days, and so even when I don't charge it, just have it next to me as I sleep - and next morning it will be off. I presume it might be switching off around 5am... this is only a rough guide as if I switch it back on, and flick through the phone, I see my unread emails are up to around 5am, and then after a few minutes it logs back into the internet etc and brings me newer emails.
I first thought it was that it kept switching off when charging... but now I know it does it at (I presume) the same time every night even when it's not charging. Can't use it as an alarm clock anymore, as it's off before the alarm goes off. Anyone have any idea what's happening?
Did you copy all of your data and settings?. Most likely you have a software conflict going on.
I highly recommend you backup your data from all 3rd party apps. Do not backup your system apps data, google data, apps or games that cloud sync or phone settings, ie wifi passwords etc.
You must allow samsung apps, google and other cloud apps to sync their own way and you must calibrate the phone for wifi manually.
Beyond that you'll need to reflash stock firmware and start over using the guidlines I have given you above after restoration of the firmware (and root if required).
Beamed in by telepathy.
I assume when I installed on the other phone, it switched settings when I log in to various things. Because I installed everything asap, I've no idea if one thing is causing the issue.
How do I get the phone to calibrate manually? Apologies, I'm not great with techie stuff I add the wifi details, and logged into settings - is that manually? Things are backed up to themselves, so when I log back in it resets to previous settings when it syncs. Should I try and work out how to prevent all things from backing up manually? Haven't logged back into any games, although they might be installed, haven't actually signed in or used them.
How would I go about reflashing stock firmware? Doesn't sound like anything I've ever done before, but up for a challenge
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
shivadow said:
By manually i mean just setup wifi yourself rather than allowing a backup. Same for system apps.
The app data will contain references to the old phone which will confuse it. All of that must be rewritten on the specific device to match the phones identity.
3rd party apps are usually OK with backups but still shouldn't be trusted, but they don't usually bootloop the phone. They just force close instead.
Flashing firmware will reset the phone back to factory and rewrite the operating system, removing any software bugs in the process. To learn how to use odin you can find countless guides online too.
A straight forward "factory reset" via either the phone software or the recovery menu could solve the problem rather than flashing.
If I were you, I'd just factory reset it and then allow the phone to run for a few hours to see if the problem reoccurs in a factory state. If the phone asks for a google login just use the normal account and allow all updates to happen but switch off backup and sync for the short term. If all seems good then you know there was a bad app somewhere.
Beamed in by telepathy.
Click to expand...
Click to collapse
Ahh, cool, gottcha! Ok, will try soon. Surprisingly, I've switched off the phone every night instead of it auto-switching off at around 5-6am, and surprisingly it's so far going well. Had it on for 3 days and only at 47% now, so it's promising, still does switch off occasionally during the day, but I've just ignored that. Will do a factory reset in the next couple of days and report back Thanks for the help
It's been a week already since i have this problem, but i was using my instagram app normally and tried to open the app once again, since i closed it for a second, but the moment i did, the app seemingly resetted itself and started to configure the language which never did, since it went on indefinitely; i couldn't use my instagram app anymore, so i tried resetting my phone, that didn't work. Then i tried uninstalling my app, but it just refuses to be uninstalled, sometimes even resetting the entire cellphone because of it, i'm trying everything i can do to avoid doing a factory reset, so i'm trying to find some help; what could be happening to my phone?