So I just installed the new AOKP Build 34 and booted up and errors start popping up, contacts has closed and acore crashes every 3 seconds. I redownloaded, rewiped, reflashed, same error. I searched around and found some people saying its contacts storage, so i cleared data and still get the same error. Any ideas? Thanks for any help
xcentrik05 said:
So I just installed the new AOKP Build 34 and booted up and errors start popping up, contacts has closed and acore crashes every 3 seconds. I redownloaded, rewiped, reflashed, same error. I searched around and found some people saying its contacts storage, so i cleared data and still get the same error. Any ideas? Thanks for any help
Click to expand...
Click to collapse
Did you even read the thread before you made this thread?
Sent from my SGH-I777 using Tapatalk 2 Beta-5
xcentrik05 said:
So I just installed the new AOKP Build 34 and booted up and errors start popping up, contacts has closed and acore crashes every 3 seconds. I redownloaded, rewiped, reflashed, same error. I searched around and found some people saying its contacts storage, so i cleared data and still get the same error. Any ideas? Thanks for any help
Click to expand...
Click to collapse
The first zip Task posted had borked framework (aka fc's up the ass.) He re-posted not too long after the fixed update.
Normally when there's nothing wrong (as in everything was packaged correctly) , and you were encountering the same errors it's an easy fix.
Go into recovery wipe dal & cache, wipe data/factory reset, use the kernel cleaning script for saftey precautions, install the latest aokp zip followed by gapps and you should be set.
Hope that helps, have a good one
Related
I keep getting this error when I access some of my contacts. It will show me no information, and then:
The process android.process.acore has stopped unexpectedly. Please try again.
I try again, and I can never get to the contact. I can however, still call them or message them. So the contact exists, I just keep getting the error when I try to see the details.
I flashed CM7. Then went to Cognition. Then flashed Unnamed, and now back to Cognition. I started getting the error first in Unnamed, so I flashed Cognition thinking it was that. First day, everything was fine. Now I keep getting that error.
Any ideas how to fix?
I had a similar issue, delete the Google + ICS version if you have that installed. If not try a factory Reset through Settings>Privacy That worked for me.
scoot05redss said:
I had a similar issue, delete the Google + ICS version if you have that installed. If not try a factory Reset through Settings>Privacy That worked for me.
Click to expand...
Click to collapse
Bingo! That was it. Deleted Google+ ICS and then restarted, and everything was back to normal.
Thanks!
Thanks you posted this right as I needed it! ICS Google+ was definitely the issue.
Glad I could help guys!
Sent from my Galaxy S II using the XDA app!
I rooted with CF-Root V6.4, and just did an OTA firmware update to go to XXLG3. After completing the update, I rebooted then re-rooted.
Everything seems to be working just fine, except that on every boot up, I now have an "Android Upgrading" message show up before the lock screen shows.
Anyone know how I can get rid of this?
------ Update -------------
I charged up the phone and then left it turned off over night. This morning, the "Android Upgrading" message on start up seems to have gone.
gregwee said:
I rooted with CF-Root V6.4, and just did an OTA firmware update to go to XXLG3. After completing the update, I rebooted then re-rooted.
Everything seems to be working just fine, except that on every boot up, I now have an "Android Upgrading" message show up before the lock screen shows.
Anyone know how I can get rid of this?
Click to expand...
Click to collapse
Wipe cache Wipe dalvik and fix permissions in recovery .
jje
JJEgan said:
Wipe cache Wipe dalvik and fix permissions in recovery .
jje
Click to expand...
Click to collapse
Just did what you said. After wipe cache, wipe dalvik, fix permissions and rebooted. After reboot, the phone started to redo "Android Upgrading, Optimising Applications", then the message "Android Upgrading, Starting Applications" is shown. Rebooted, and the 2nd message "Android Upgrading, Starting Applications" shows before the lock screen.
Any other suggestions?
Same problem here. I followed these steps but still getting this annoying "upgrading" message. Any other suggestion?
JJEgan said:
Wipe cache Wipe dalvik and fix permissions in recovery .
jje
Click to expand...
Click to collapse
Resolved itself
Last night, I charged it up to 100%, then shut it down and left it overnight. This morning, the annoying "Android Upgrading, Start Applications" message on boot up seemed to have gone. I didn't do anything at all. Glad it's gone though... :good:
gregwee said:
Last night, I charged it up to 100%, then shut it down and left it overnight. This morning, the annoying "Android Upgrading, Start Applications" message on boot up seemed to have gone. I didn't do anything at all. Glad it's gone though... :good:
Click to expand...
Click to collapse
When you wipe dalvik its normal to show it but just once. On the 2nd reboot should be gone. And thats how you fixed it.
Sent from my GT-I9300 using xda app-developers app
gregwee said:
I rooted with CF-Root V6.4, and just did an OTA firmware update to go to XXLG3. After completing the update, I rebooted then re-rooted.
Everything seems to be working just fine, except that on every boot up, I now have an "Android Upgrading" message show up before the lock screen shows.
Anyone know how I can get rid of this?
------ Update -------------
I charged up the phone and then left it turned off over night. This morning, the "Android Upgrading" message on start up seems to have gone.
Click to expand...
Click to collapse
Just don't know what to say...
I'm happy this thread helped to solve your problem...
Xda DEVELOPERS forum.
Sent from my Galaxy SIII
I still have this problem after following above given steps and even a few reboots. I suspect Lucky Patcher for that? Any idea ?
Anyone?
buyukbang said:
I still have this problem after following above given steps and even a few reboots. I suspect Lucky Patcher for that? Any idea ?
Click to expand...
Click to collapse
buyukbang said:
Anyone?
Click to expand...
Click to collapse
Stop using cracked apps...
I am not using such app lucky patcher and have this issue too... Did all steps suggested and its still there after every reboot...
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click Toolbox button then select 4th last option i.e Remove all odex files. Thats it android will reboot on itself and vola no android is upgrading. . Even if u didn't install apps like LP just try to remove faulty odex files(for location refer to attachment).
Check out attachement for help.
:good:Hits Thanks If I helped u:good:
"Process system isnt responding. Do you want to close it?
wait report ok
I get this message ALOT on all the JB roms out there now; it happens after a reboot/restart, and if I click ok, things seem to work normally after a few seconds...
Anyone else seeing this alot? Anyone figure out a way to stop it?
thanks!
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
johnrippa said:
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
ZPaul2Fresh8 said:
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
Click to expand...
Click to collapse
did that many many times, and it doesnt help
wase4711 said:
did that many many times, and it doesnt help
Click to expand...
Click to collapse
Did you restore apps from titanium backup? If so that may be it.
_____________________
Black Star VIII
Me too
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Problem gone (i hope)
strainhunter said:
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Click to expand...
Click to collapse
Hello Again,
The problem is gone for me i found out that it has something to do either with the Theme i was using, or/and the Launcher. Because i first switched my Launcher (Nova Launcher) to the Stock one (Trebuchet) (merely just because i did not know how i should fix that problem) then at the after the first reboot with stock launcher the problem was gone, but came back after i rebooted again. So i changed my Theme (JellyBeanExtreme) and the problem did not appear again "knockin´3x on wood^^"
Maybe this can help someone who had or will have this problem.
Greetings,
Strainhunter
wase4711 said:
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
Click to expand...
Click to collapse
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
CPA Poke said:
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
Click to expand...
Click to collapse
Does that leave your apps and data in place? Never thought of that
Sent from my SGH-I717 using XDA Premium HD app
did u install the walkman app for the note?
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
briand.mooreg said:
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
jrea77 said:
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
Click to expand...
Click to collapse
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
CPA Poke said:
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
Click to expand...
Click to collapse
ya...i noticed nothing was really wrong while getting the error, it just bug me that i was getting that little pop up window. i would hit "wait" or "cancel" and it didnt seem to make a difference, it would go away and that was it. once in a while it would pop back up when getting a text or call, before i could answer the call i had to click it to make it go away to be able to answer. so i decided not to use the theme and not worry about that error.....so would it be any theme or just some themes? maybe ill try other themes and see what happens.....
I am running Android 4.2.1 and have not installed or updated any apps over past week. This morning, I switch on my phone and this error popped up (pic). I tried restarting it several times during the day and the error is persistent. My phone feels sluggish but otherwise functions as it should. How do I find out what app is causing this error message? It appears to be system related. Is there an app in Play Store that can tell me exactly what is causing this error?
BTW, I rooted my phone some 2 months ago and everything works well so I doubt it is because my phone is rooted. All my apps installed via Play Store so shouldn't be any malwares involved.
Mainly this error is caused by using a particular rom.
Changing the rom might solve the problem.
dagger said:
Mainly this error is caused by using a particular rom.
Changing the rom might solve the problem.
Click to expand...
Click to collapse
My ROM is stock.
Ok did you flash any tweaking script??
dagger said:
Ok did you flash any tweaking script??
Click to expand...
Click to collapse
No, never tweaked anything except to root it but that was 2 months ago.
hmm.
Then try wiping the dalvik cache and the cache partition from recovery.
try it and then report..
OK, I will try your suggestions. Now I have to read up on just how to do that
dagger said:
hmm.
Then try wiping the dalvik cache and the cache partition from recovery.
try it and then report..
Click to expand...
Click to collapse
Sorry I could not manage to try cleaning the cache because my phone decided to brick itself the following morning. Just like that. This morning, alarm on my phone went off like usual and I always do a restart to be fresh for the day. The phone is stuck at green android man. I did a power and vol+ and got a dead android man. I created another thread asking for help in reviving my dead phone. If you have comments, I will appreciate it.
http://forum.xda-developers.com/showthread.php?p=43070181
Problem fixed.
My HTC one m8, continues to pop up "people stopped unexpectedly"
I cannot make any phone calls.
My rom s. Rom
Tried Google cache cleaning, people cache, twrp recover cache wipe, factory reset but all same result.
After factory reset via recovery, the default people and phone icons also gone, only one androbot icon which gives same message on clicking "people stopped unexpectedly"
Please help anyone
wasim9283 said:
My HTC one m8, continues to pop up "people stopped unexpectedly"
I cannot make any phone calls.
My rom s. Rom
Tried Google cache cleaning, people cache, twrp recover cache wipe, factory reset but all same result.
After factory reset via recovery, the default people and phone icons also gone, only one androbot icon which gives same message on clicking "people stopped unexpectedly"
Please help anyone
Click to expand...
Click to collapse
That is telling me those packages are corrupted or they are stored partly in the data partition (HTC roms are known for this.) reflash the rom
zelendel said:
That is telling me those packages are corrupted or they are stored partly in the data partition (HTC roms are known for this.) reflash the rom
Click to expand...
Click to collapse
Yup finally did the same, thanks