Has anyone had this issue? I went to check my sms and it just force closes... Rebooted and now it works, just all the messages were deleted. Not a big deal, just not sure if it could have received any messages in that time. Phone is rooted, stock rom, not a lot of apps. Pretty much stock all around (i'm lazy).
Thanks for any replies!
Any Solutions
Related
I've been having lag recently withing the SMS app. I will open it up and it's slow/sluggish and it takes my contacts pictures a while to load.
I know there are SMS apps like Handcent and Chomp, but I'm not a big fan of them. They've deleted all my texts multiple times and the interface looks cheap to me.
I delete my SMS threads every week or so and I do not have a lot of MMS messages in these threads. Does anyone else have this problem? Or better yet, have a fix for it?
Thanks.
wad3g said:
I've been having lag recently withing the SMS app. I will open it up and it's slow/sluggish and it takes my contacts pictures a while to load.
I know there are SMS apps like Handcent and Chomp, but I'm not a big fan of them. They've deleted all my texts multiple times and the interface looks cheap to me.
I delete my SMS threads every week or so and I do not have a lot of MMS messages in these threads. Does anyone else have this problem? Or better yet, have a fix for it?
Thanks.
Click to expand...
Click to collapse
I use handcent every day since the DX was released and it has never deleted any of my texts...and you can change the interface as well. And for what it's worth, haven't noticed any lag with it either. I just love the quick reply
Had a similar problem with my contact list...it was because I had removed atcmd.apk. Have you removed any bloatware?
Handcent > Stock messaging app
And if it deleted all your texts, you probably hit the delete button
I have removed bloatware so I'll need to check into that.
As for Handcent; it deleted all of my SMS messages twice. It originally did it to my friend, but I figured he was the one at fault. Shortly after that my texts got deleted. This never happened on the Droid X, only on the original Droid.
I just don't like the way the Handcent interface looks on my X, even though the stock SMS app is hideous in its own right.
i agree with you whole heartedly. i dont like chomp or handcent.. i know a lot of people do.. good for them. but i really want just the stock android 2.2 messaging.
I have the same problem. If I get a text notification and I select it from the pull down notification bar it takes forever to load. I've used hand cent and I got even more loading lag with that app so I uninstalled it. I'm wondering if its my conversation sizes or I'm running or of ram
Sent from my DROIDX using XDA App
How does DX handle deleted messages? I was just wondering bc I am used to Sense on WinMo and I would delete my messages - but then I noticed one day it stored all my deleted messages as well. Go figure.
Does DX work the same way? (haven't got mine yet) I mean could it be that you have hundreds of deleted texts hiding somewhere waiting to be emptied like on HTC Sense/WinMo?
I just wanted to let you guys know that I installed the MMS.apk package from the original Droid Cyanogen 5.0.8 build, and it works swimmingly. I used Titanium Backup to backup and remove the Motorola Text Messaging app and have seen no issues.
Also, if any of you have had a problem with receiving messages 2 or 3 at a time, (duplicates) this solved that problem for me.
hey where can i get my hands on that MMS.apk? please
Hi All
I have a strange problem. My ChompSMS shows a received message twice. Also I'm unable to access the stock message App anymore.
I must point out that I tried freezing the messaging apps using Titanium Backup as indicated in the following post.
http://forum.xda-developers.com/showpost.php?p=10800001&postcount=26
Initially I stopped getting messages on freezing them and then when I defrosted I see a message twice in the ChompSMS software and can't access the stock app at all. If I open the stock application it closes on its own.
I'm not sure if I can attribute everything that happened to the above post as it is working very well for lot of people. If anyone has any suggestions, please let me know.
Please note that I'm not getting the notification twice but I'm seeing a received message twice in ChompSMS. Also I see 2 new messages when I receive a new message. At least the notification is doing its thing. lol
Thanx for your suggestions!!
Up!!! the same to me now.
Anyone got solution?
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.
Hi all,
I hope I'm in the right forum, wasn't sure.
I've done a few searches and cannot find a solution.
I have the Samsung Galaxy S4 (i9505), which recently had stock android on it (rooted).
I installed CM11 M9 onto it a few days ago, but since then, I cannot receive text messages. I can only send.
This has been confirmed by putting my simcard into my old SGS3 (with stock), and it sends and receives text messages fine.
I've done the *#*#4636#*#* trick, clicking refresh and update for the SMSC, which comes up as Telstra +61418706700
When I run the default messaging app, it forced closes. I usually run Textra.
I have disabled Voice+ as I heard this could be the cause of the issue, but did not make any difference.
Any suggestions would be appreciated, as I need to receive all my text messages...
numloxx1978 said:
Hi all,
I hope I'm in the right forum, wasn't sure.
I've done a few searches and cannot find a solution.
I have the Samsung Galaxy S4 (i9505), which recently had stock android on it (rooted).
I installed CM11 M9 onto it a few days ago, but since then, I cannot receive text messages. I can only send.
This has been confirmed by putting my simcard into my old SGS3 (with stock), and it sends and receives text messages fine.
I've done the *#*#4636#*#* trick, clicking refresh and update for the SMSC, which comes up as Telstra +61418706700
When I run the default messaging app, it forced closes. I usually run Textra.
I have disabled Voice+ as I heard this could be the cause of the issue, but did not make any difference.
Any suggestions would be appreciated, as I need to receive all my text messages...
Click to expand...
Click to collapse
You should post your question here:
http://forum.xda-developers.com/showthread.php?t=2559336
Since the app is force closing, I guess it's a bad download or flash. Take a nandroid and do a clean flash...:good:
a103 said:
You should post your question here:
http://forum.xda-developers.com/showthread.php?t=2559336
Since the app is force closing, I guess it's a bad download or flash. Take a nandroid and do a clean flash...:good:
Click to expand...
Click to collapse
Thanks,
I'll check it out
Have reverted back to stock so I can check my messages, do some backups and give the whole thing another shot with a clean install.
I re-flashed and instead of restoring every app using Titanium backup, reinstalled only the apps with important info, such as Textra etc. Messaging works all good now. Thank you for your help
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