Texting on my rooted thunderbolt is fine until I receive an MMS message. Once an MMS comes in, I can look at that one, then within a few seconds, I get the error message:
Sorry!
The process com.android.mms has stopped unexpectedly. Please try again
with just a "Force close" button
After I force close, I can't receive ANY txt messages (regular or mms) until I reboot my phone. I can send messages and people will receive them - but nothing comes in. Also, while in this state - if someone does send me a txt not only do I not get it, but it doesn't come in at all even after I reboot (meaning it's not sitting in some queue and I just get it later). So I really have no choice but to reboot my phone after this happens if I don't want to miss any important txts.
I have tried rebooting into CWM Recovery and selecting "fix permissions" (I really thought this was going to work) and just for kicks I also wiped cache. But it didn't help. I'm debating about restoring to factory defaults, rerooting and restoring via titanium backup - but that's a long process that I really don't want to do if there is another way to fix this.
At the very least, does anyone know of a way to kickstart the failed process without rebooting? I could at least live with that for a while.
I've done some googling, and did find other people with similar issues, but not much in the way of definitive fixes.
Thanks for any help!
Sorry!
The process com.android.mms has stopped unexpectedly. Please try again
with just a "Force close" button
After I force close, I can't receive ANY txt messages (regular or mms) until I reboot my phone. I can send messages and people will receive them - but nothing comes in. Also, while in this state - if someone does send me a txt not only do I not get it, but it doesn't come in at all even after I reboot (meaning it's not sitting in some queue and I just get it later). So I really have no choice but to reboot my phone after this happens if I don't want to miss any important txts.
I have tried rebooting into CWM Recovery and selecting "fix permissions" (I really thought this was going to work) and just for kicks I also wiped cache. But it didn't help. I'm debating about restoring to factory defaults, rerooting and restoring via titanium backup - but that's a long process that I really don't want to do if there is another way to fix this.
At the very least, does anyone know of a way to kickstart the failed process without rebooting? I could at least live with that for a while.
I've done some googling, and did find other people with similar issues, but not much in the way of definitive fixes.
Thanks for any help!