Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

The process com.android.phone has stopped unexpectedly.


This topic has been archived. This means that you cannot reply to this topic.
7 replies to this topic

#1 Ofca

Ofca
  • Members
  • 6 posts

Posted 23 May 2012 - 09:34 PM

As in subject, I receive the The process com.android.phone has stopped unexpectedly. After that I need to enter PIN again, and phone reconnects to the network.

It doesn't always occur, it happens randomly (or for reason that eludes me) when answering or placing calls.

It started when I upgraded from nightly 263 to 7.2RC1, and happens ever since, also on current nightly.

Any idea how to debug/fix this?

Edited by Ofca, 23 May 2012 - 09:36 PM.


#2 bassmadrigal

bassmadrigal
  • Administrators
  • 7,954 posts

Posted 24 May 2012 - 03:06 PM

Have you tried formatting the /system partition and reinstalling CM and gapps? This doesn't cause any data loss.

#3 Ofca

Ofca
  • Members
  • 6 posts

Posted 25 May 2012 - 08:19 AM

Not yet, I'll try it and report back. Thanks for the suggestion.

#4 Ofca

Ofca
  • Members
  • 6 posts

Posted 27 May 2012 - 02:06 AM

Unfortunately this didn't help. Any other ideas?

#5 bassmadrigal

bassmadrigal
  • Administrators
  • 7,954 posts

Posted 27 May 2012 - 02:26 AM

You might need to perform a Factory Reset/Data Wipe. You can back up your apps and app data with a program like Titanium Backup, but be careful that you don't restore any system-related settings as it could bring your problem right back.

#6 Ofca

Ofca
  • Members
  • 6 posts

Posted 10 September 2012 - 01:36 PM

Unfortunately it's happening again.

I used log collector to help in getting to the root cause of the problem. It seems that com.android.phone wants more memory than it can get, but that's my uneducated guess.

http://pastie.org/4695710

#7 TheGreenJester

TheGreenJester
  • Members
  • 70 posts

Posted 11 September 2012 - 01:22 AM

There was sufficient memory free for the phone process itself.  The lack of memory occured when it tried to redraw the screen.  Are you using the stock launcher?  Are you using a live wallpaper?  I'm not sure what would cause this, I've never seen it before.

#8 Ofca

Ofca
  • Members
  • 6 posts

Posted 11 September 2012 - 11:58 AM

I'm using the stock launcher from CM7.2, and I'm not using a live wallpaper. It happens only when placing or answering calls, randomly. I collected logs for pretty much every crash lately and it's same thing all the time.