Micromax Takes OnePlus to Court! Android Wear Receives Lollipop – XDA TV

Android 5.0 Lollipop is available officially for the Moto 360! … more

Google Invites Selected Devs to Buy Project Tango Development Kit

Just about a month ago, the curious Project Tango development kit was … more

YU Yureka: Indian Handset with CyanogenMod

Thesoap opera involving Cyanogen Inc., OnePlus, and Micromax is one of the most talked about … more

Chainfire Turns Your Bootanimation into a Logging Center

Having a nice boot animation certainly adds a little bit of aesthetic polish to your … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

com.android.mms force close now

OP nitefallz

1st June 2009, 04:26 PM   |  #1  
OP Senior Member
Thanks Meter: 7
 
198 posts
Join Date:Joined: Sep 2006
Something happened to my over the weekend. I found it had reset and kept resetting on the loading screen. I took the battery out, popped it on and turned it on. It made it to the home screen but all the apps I had stored on the SD card would close unexpectedly. It looked like ext2 partition crapped out or something as none of those apps would run. So I restored a backup from Nandroid and everything was working again EXCEPT for my SMS/MMS.

Whenever I go into messages, it crashes with a "force close" prompt stating com.android.mms closed unexpectedly. I'm thinking if I could clear all the messages I had save that would solve the problem, but I have no clue where they're stored.

Any advice?
1st June 2009, 07:03 PM   |  #2  
OP Senior Member
Thanks Meter: 7
 
198 posts
Join Date:Joined: Sep 2006
Found what I needed here: http://forum.xda-developers.com/show...ed#post2976069

I deleted the DB with the messages, all is well.
11th September 2010, 02:35 PM   |  #3  
HorNet505's Avatar
Senior Member
Springfield
Thanks Meter: 0
 
215 posts
Join Date:Joined: Jan 2007
More
same problem here,
clicking "sms" pops up an error msg "com.android.mms ended unexpected"
I have not found any .db files yet :(
9th November 2010, 03:36 PM   |  #4  
Junior Member
Thanks Meter: 0
 
21 posts
Join Date:Joined: Jun 2010
Hello,
Did you deleted mmssms.db or some of "PART_XXXXXXXXXX" files too?
Thanks!
27th December 2010, 04:07 AM   |  #5  
Junior Member
Flag Phoenix
Thanks Meter: 0
 
3 posts
Join Date:Joined: Dec 2009
More
Deleting the mmssms.db file
For no apparent reason my phone's messaging app suddenly started force closing. After multiple reboots, even taking the battery out while phone was on, changing the language settings, and even doing a data factory reset, nothing worked. Found this post and deleted the mmssms.db file, now messaging app works fine, tho I lost all the old messages. That's ok, I had all but the last day backed up to Gmail anyway. So, just delete the database file.
MIUI Fanboy
18th January 2011, 05:39 PM   |  #6  
Guest
Thanks Meter: 0
 
n/a posts
Quote:
Originally Posted by VirtuallyNadine

For no apparent reason my phone's messaging app suddenly started force closing. After multiple reboots, even taking the battery out while phone was on, changing the language settings, and even doing a data factory reset, nothing worked. Found this post and deleted the mmssms.db file, now messaging app works fine, tho I lost all the old messages. That's ok, I had all but the last day backed up to Gmail anyway. So, just delete the database file.

I have the same problem. Did you permanently delete the database or is it still there? Cos I tried to delete the database throught root explorer but it still remains altho it has deleted all the messages saved in it.
5th February 2011, 08:21 PM   |  #7  
zekesic's Avatar
Member
Thanks Meter: 2
 
43 posts
Join Date:Joined: Jan 2011
More
any news on the com.android.mms subject????? I feel very frustrated with my android and i looked everywhere on the internet and can't manage to fix it!
30th June 2011, 02:21 PM   |  #8  
Junior Member
Thanks Meter: 3
 
1 posts
Join Date:Joined: Jun 2011
A possible fix
Here's what I did that fixed mine:

I think the root-cause of this error occurred from restoring old messages. There must have been a character/corruption somewhere that was screwing everything up.

Please note the following: I'm using an Evo 4G, running gingerbread-evo-deck-1.2 ROM. I realize this is a G1 thread, but this came up first on google, so I think it would be most helpful here. I was getting the error as described when using the "Messaging" app.

What I did:
  1. Terminal Emulator
  2. su (allow root if prompted)
  3. rm /data/data/com.android.providers.telephony/databases/mmssms.db
  4. Menu > Reset terminal (probably an unnecessary step, but it's what I did)
  5. home screen > remove battery while running
  6. wait 20 seconds
  7. reboot


I don't know why removing the battery that way works. I did try force closing the "Message" app and it didn't work. I realize now I probably should have tried to figure out how to kill the underlying framework, but oh well. I'm not going to try breaking it again.
The Following 3 Users Say Thank You to echoota For This Useful Post: [ View ]
16th September 2011, 08:02 PM   |  #9  
Junior Member
Flag Rio de Janeiro
Thanks Meter: 5
 
20 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by echoota

Here's what I did that fixed mine:

I think the root-cause of this error occurred from restoring old messages. There must have been a character/corruption somewhere that was screwing everything up.

Please note the following: I'm using an Evo 4G, running gingerbread-evo-deck-1.2 ROM. I realize this is a G1 thread, but this came up first on google, so I think it would be most helpful here. I was getting the error as described when using the "Messaging" app.

What I did:

  1. Terminal Emulator
  2. su (allow root if prompted)
  3. rm /data/data/com.android.providers.telephony/databases/mmssms.db
  4. Menu > Reset terminal (probably an unnecessary step, but it's what I did)
  5. home screen > remove battery while running
  6. wait 20 seconds
  7. reboot


I don't know why removing the battery that way works. I did try force closing the "Message" app and it didn't work. I realize now I probably should have tried to figure out how to kill the underlying framework, but oh well. I'm not going to try breaking it again.


Works for me thanks

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes