Hey yall.
I'm using the Donut AOSP w/ eclair theme (http://forum.xda-developers.com/showthread.php?t=591104). For some reason, my sms doesn't work anymore and gives me an error of com.process.mms has some sort of problem and forces closed. I tried installing another sms program but it also force crashes since it relies off of the nonworking sms program.
Anyone have any ideas of how to fix this?
hi. My evo keeps on force closing in the messages app after a few text messages then it deletes them. This started when i installed the latest update. Please help because there is a 40 person waiting list at the sprint store for the evo so theres barely any there to get my phone exchanged.
-its not rooted btw
You try using Chomp or Handcent?
posted by Swyping on my Evo...
yeah i have. at first i was using handcent when it started to force close then delete. so i uninstalled it and used the standard app, and it did it 4 times since yesterday
SOLVED
it was my antivirus app. i did some research and it was most likely that
I've been on Rubix since 1.9.0 and this is the second time I've seen this issue.
It's possible that the first time the crash happens is unrelated but here goes: I was out in the middle of nowhere with intermittent service (BLM land in California). I got a decent bit of service, stopped driving, hit send on a text (using GO SMS) and while waiting for it to send I lost service. Then got service back and instantly I got a force close of com.android.mms.
The message will now stay in the thread with the status of "Sending...". When I attempt to send another message using GO SMS it just hangs in the "Sending..." status and does nothing. If I try with the stock messaging app it force closes on me the instant I send.
This happened to me before on RubiX 1.9.7 and happened this weekend on 2.0.1. I did a Titanium Backup of all my stuff, wiped, went back to stock RubiX 2.0.1, restored my TiBackup and I get the same force close. I only restored apps and "green" data items.
I'm about to wipe again and omit restoring anything MMS related (as I believe that's how I fixed it before). I've tried repairing permissions (using ROM Manager), wiping cache, clearing data from the Messaging app in Application Manager, deleting buttloads of messages and nearly all MMS messages, nothing has worked.
Anyone else seen this happen, on RubiX or other ROMs?
I've had something similar happen on liberty 1.5. Whenever I tried to send an mms message, it would force close and not send. I fixed it by reflashing the rom
Jmoney47 said:
I've had something similar happen on liberty 1.5. Whenever I tried to send an mms message, it would force close and not send. I fixed it by reflashing the rom
Click to expand...
Click to collapse
Did you restore all your text messages after re-flashing, and did you have the same issue after restoring?
I used the GO SMS backup service to backup and restore my messages. Sending messages was fine after I just re-flashed yesterday; but after I restored my messages (580, I believe) messaging started force closing on me again. Looks like it's SMS quantity related... they just add up so fast!.
Guess this can be considered closed.
Has anyone else run into this issue in the past week or so? Soon as I updated to the newest version of Google messenger ah which is now "Android messages" probably to reduce confusion between Facebook messenger, my messages app always says I have unread messages which I do not. I also do not use any other messaging app for texting. I do not even have the Facebook messenger app.
Things I have tried:
Deleting data on messages, fixes it temporarily after a restart but then comes right back.
Uninstalled app, restarted, reinstalled, restarted, still does it.
Tried clicking on every individual text message on each person, doesn't fix it.
Bothers me so much I did a factory reset, put no apps on my phone, disabled any bloat, downloaded Android messages, tried it, still saying I have unread messages.
I have no idea what else to try, from what I have heard on Reddit, many others are experiencing the same problem and no fix for them that they knew of yet.
I'm thinking it must be something with the recent update, obviously that was my first deduction after updating and it happening literally right after with never having problems but I'd figure I would try stuff and see what happens.
BlueForce64 said:
Has anyone else run into this issue in the past week or so? Soon as I updated to the newest version of Google messenger ah which is now "Android messages" probably to reduce confusion between Facebook messenger, my messages app always says I have unread messages which I do not. I also do not use any other messaging app for texting. I do not even have the Facebook messenger app.
Things I have tried:
Deleting data on messages, fixes it temporarily after a restart but then comes right back.
Uninstalled app, restarted, reinstalled, restarted, still does it.
Tried clicking on every individual text message on each person, doesn't fix it.
Bothers me so much I did a factory reset, put no apps on my phone, disabled any bloat, downloaded Android messages, tried it, still saying I have unread messages.
I have no idea what else to try, from what I have heard on Reddit, many others are experiencing the same problem and no fix for them that they knew of yet.
I'm thinking it must be something with the recent update, obviously that was my first deduction after updating and it happening literally right after with never having problems but I'd figure I would try stuff and see what happens.
Click to expand...
Click to collapse
Any updates? My wife's ZF is experiencing the same thing. I noticed it on my own device a few days ago, but, since I run Action Launcher, I just turned off notification badges.
Had same exact issue but fixed it
Yes I've had this same issue since the update and it turned out to be related to Verizon Messages app. I opened Verizon Messages, opened each "unread" thread then I closed the app and disabled it. No issues since then with the notification bug in Android Messages. Also I made Verizon Messages the default messenger temporarily while I did the above and then afterward I switched it back to Android Messages
I followed almost the exact same steps, except for making it the default messenger. I'll try it again today and see if it works. Thanks!
Marine034189 said:
Yes I've had this same issue since the update and it turned out to be related to Verizon Messages app. I opened Verizon Messages, opened each "unread" thread then I closed the app and disabled it. No issues since then with the notification bug in Android Messages. Also I made Verizon Messages the default messenger temporarily while I did the above and then afterward I switched it back to Android Messages
Click to expand...
Click to collapse
Hmmm, this also did not work for me. I did make it my default messenger while I read the messages then went to disable and force stop it. I tried many variations of enabling and disabling the app too like blocking notifications, turning off system control, denying all permissions, nothing seems to work. I guess we'll just have to wait for an official fix it seems.
Same here. My wife's has been doing this for the past week. Mine just received the push today for it so now mine is doing it. Hopefully they resolve the issue soon.
Ugh same here again..
Yeah it's happening again now on mine so it does indeed look like we will have to wait for an official fix :-/ I think I might just download an older version apk until they are able to push a fix out for it
Same problem here. Uninstalled and rebooted. Did not install update. Works fine. Will wait for next update release before trying update again.
Moto Z Force Droid
So I have another bug that MAY have started after the Nougat update.
I use Google Android Messages for sms and GBoard for my keyboard...
Lately when i'm texting to someone, when I go to reply to a text (maybe when the text thread is already open?) my keyboard doesn't work and I have to hit the back button which makes the keyboard go away then click on the message box to activate it again so it will work.
Is anyone else having this issue? Any fixes found?
I've tried clearing cache on both apps, this didn't fix the issue for me.