Android.process.acore has stopped unexpectedly

**Mikey47** · 01-01-2013, 12:12 AM

Oh, oh. Texting my kids at midnight and my phone is continually showing this error... Anyone else? Does Jelly Bean not like 2013?

**UbaidAbid** · 01-01-2013, 12:46 AM

having the same problem with my one x.

**skrilexx** · 01-01-2013, 01:13 AM

Same problem with HOX (jb) plz fix
Somebody has any solution?

**Chekesha Rashad** · 01-01-2013, 02:13 AM

Me too..I have tried turning off and on and it keeps popping up. I have an HTC Evo lte

**delthor7** · 01-01-2013, 04:23 AM

Mine too. (and my wife's phone) wtf?!

Sent from my EVO using Android Central Forums

**Marim2** · 01-01-2013, 05:29 AM

Me too

**DroidXcon** · 01-01-2013, 05:43 AM

Originally Posted by Marim2

Me too

Do you have your contacts backed up?
Try uninstalling Facebook if that is installed. If this does not fix your problem then try the following.

Settings>Applications>System Applications>Contacts Sync Adapter and press Clear Data, this error usually goes away. If this doesn't work, try clearing the data on Settings>Applications>System Applications>Contacts or Settings>Applications>System Applications>Contacts Storage.

If problem is fixed, then restore contacts and reinstall Facebook and make sure you don't sync contacts with it.

Good luck. Im going to sleep.
Sorry if this wasn't helpful

From my Galaxy Note 2 via Tapatalk

**Zookeeper63** · 01-01-2013, 06:06 AM

I turned off sync, nuked my contacts and reloaded them...all fixed.

**Mikey47** · 01-01-2013, 06:19 AM

This is bull! Another totally inexcusable software bug!!

I opened a ticket with HTC already, will wait to hear what they say.

**preman007** · 01-01-2013, 07:01 AM

Thanks I got same message to

**thatevoguy** · 01-01-2013, 10:11 AM

It appears that HTC contacts doesn't like 2013!

I just sent the following to HTC:

"As of this morning I keep getting the following error message every 5 or so seconds on my sprint Evo 4GLTE that has had all recent updates.

"Sorry! android.process.acore has stopped unexpectedly. Would you like to send an error report to HTC? This will help us improve our products".

I have been sending reports. Based upon the stack trace in the error message, the first line in the trace says "Time Format Error : 20130229" (See attached), I think there is an issue with the date rolling over to 2013. Please look into this error."

**nrgtek** · 01-01-2013, 10:16 AM

Getting this too. Glad I found this thread. I will try to uninstall FB and see what happens.

My battery died this morning and this was coming up after recharging. Was hoping it wasn't something because of that. The 2013 bug sounds possible too.

**DroidXcon** · 01-01-2013, 10:17 AM

Yeah I mentioned it was contacts a couple posts back

From my Galaxy Note 2 via Tapatalk

**thatevoguy** · 01-01-2013, 10:27 AM

Originally Posted by DroidXcon

Yeah I mentioned it was contacts a couple posts back

I posted what I saw in the stack trace to build upon what you stated. For what it's worth, none of the suggestions above has helped.

**nrgtek** · 01-01-2013, 10:29 AM

Originally Posted by DroidXcon

Do you have your contacts backed up?
Try uninstalling Facebook if that is installed. If this does not fix your problem then try the following.

Settings>Applications>System Applications>Contacts Sync Adapter and press Clear Data, this error usually goes away. If this doesn't work, try clearing the data on Settings>Applications>System Applications>Contacts or Settings>Applications>System Applications>Contacts Storage.

If problem is fixed, then restore contacts and reinstall Facebook and make sure you don't sync contacts with it.

Good luck. Im going to sleep.
Sorry if this wasn't helpful

From my Galaxy Note 2 via Tapatalk

hmm...I don't have these steps on my HTC ONE X+

**Mikey47** · 01-01-2013, 10:33 AM

Yep, been emailing with support too. If they ask you to test it safe mode, I can assure you that it still happens in safe mode.

I'm sure they will accuse you of having a real killer running too.

Boy some developer hard-coded a reference to 2012?!? Unbelievable!

**nrgtek** · 01-01-2013, 10:35 AM

Originally Posted by Mikey47

Yep, been emailing with support too. If they ask you to test it safe mode, I can assure you that it still happens in safe mode.

I'm sure they will accuse you of having a real killer running too.

Boy some developer hard-coded a reference to 2012?!? Unbelievable!

Didn't google do the same thing with their new nexus? Forgot December.

**thatevoguy** · 01-01-2013, 10:39 AM

I repeated the steps above, turning off sync for both FB and my google account, deleted the contacts and now re-synching. The message has gone away for now. Fingers crossed.

**Mikey47** · 01-01-2013, 10:54 AM

Originally Posted by thatevoguy

I repeated the steps above, turning off sync for both FB and my google account, deleted the contacts and now re-synching. The message has gone away for now. Fingers crossed.

So, if reloading your contacts resolved this some developer screwed up some data when reading contacts from Google and/or Facebook. Still unbelievable!

**BoredandTattooed** · 01-01-2013, 11:12 AM

What's unbelievable? That developers are human and might make mistakes too?

Btw, I cannot recreate this issue.... I'm unaffected..

**Mikey47** · 01-01-2013, 11:27 AM

Originally Posted by BoredandTattooed

Btw, I cannot recreate this issue.... I'm unaffected..

Hmm. Anyone else who has this problem do a factory reset after updating? And likewise those of you unaffected, have you not done a factory reset?

Or is this somehow related to those of us affected by the contact lag issue with ICS?

**YazanAkkash** · 01-01-2013, 11:58 AM

I guess you are right, its related to 2013. I started receiving this error on my htc one x directly on midnight new year's eve, what i did is that i put the date back to 31 dec 2012 for a few minutes , then put it back to jan 1 and the error stopped from showing, hope it will work with u too guys

**Mikey47** · 01-01-2013, 12:05 PM

Take a very close look at the stack trace attached. It is saying there is a Time format error, with the argument being "20130229".

Of course that's an error, this is NOT a leap year! Now the only question is where in the world is it getting that date from?!?

**Christopher Gregoriou** · 01-01-2013, 12:12 PM

First disable automatic network update for date, time and time zone and then manually set the date to Dec 1 2012 for 5 minutes. Then set the date back to today's date and enable auto network updates. Worked like a charm (so far

)

**Mikey47** · 01-01-2013, 12:31 PM

Originally Posted by Christopher Gregoriou

First disable automatic network update for date, time and time zone and then manually set the date to Dec 1 2012 for 5 minutes. Then set the date back to today's date and enable auto network updates. Worked like a charm (so far

)

Since I'm working with HTC on this I'm going to leave mine "broken" for now. If changing the date works that makes me think that this might also go away at midnight tonight too. "20130229" is 60 days from today, wonder if that might be significant somehow.