When I open Messages and am in the All messages folder literally all messages are appearing under one or two conversations.
e.g.
User A sends me an SMS.. all further messages appear under User A..
User B sends me an SMS.. all further messages appear under User B..
User C sends me an SMS.. all further messages appear under User B... and so on.
the problem extends into replies as well.. b/c the messages to User C are grouped under User B.. any reply to User C ends up being sent to User B.
I have made few modifications to my stock ROM.. certainly haven't been fiddling around with the Messages app so this behaviour is quite odd.
Messages Version number is: 2.0.0082.47214 release-keys
Wondering if anyone else seen this problem?
Cheers,
mils
Same problem
Hey Mills I have the same issue and i posted a similar post called "SMS Grouping" in the forums but no replies yet. I thought i was having the problem bc i sync'd with outlook but I removed all my contacts and moved them to google. That still didnt work. I use T-Mobile USA and the funny thing is the only messages that the only SMS that to not thread with all my other are my 404 alerts for weather and horoscope. I hope some one can help I'm sure we are not the only 2 with this problem. Ill keep you updated is i discover anything
Related
Hi guys,
I've just found out that I could not delete now SOME of the messages from one of my contacts unlike before. Menu->Delete Messages are no longer working for that person, and to my amazement for this person only. The feature is still working with my other contact's SMS.
I hope anybody can offer some help.
Thanks.
Just to check, there are messages from that person to delete, rather than an empty list?
Can you select them in 'all messages'?
Just moved from an EVO 4G to a Galaxy S. This may sound dumb, but when I delete the threads of text messages, the contact stays in text messages and I can't for the life of me figure out how to delete them. My EVO didn't have this problem.
This is a problem due to my phone being the recipient of pages from work, each server sends as a unique sender... over the course of a few weeks I'll have hundreds of contacts in text messages if I can't delete them. I've tried clearing my contact storage, I've tried deleting all threads, nothing gets rid of them. The contacts in question say SMS:0, MMS:0 so the thread was deleted, but the sender remains.. How do I clear the sender from text messages?
Oh well, FYI for anyone that may have found this on a search with the same problem. I was told by both Sprint and Samsung it's a known issue. Details on my home page if you look at my profile, sorry, can't post external links yet...
Hello All,
I have been experiencing a strange problem for a long time and now I'd finally like to eliminate it.
When I first got my DS5 (bought directly from Dell at announcement!), I moved my contacts database over from a couple WinMobile2003 phones (HTC TyTN I & II). The conversion went smoothly except for the strange occurrence of extraneous characters - in particular commas! I've combed the contacts database on the DS5 and removed and corrected any and all problem entries.
After all this the native Froyo 2.2.2 ('351) SMS application sometimes shows commas in a thread for a particular contact, for example, if the messages for contact entry "John Doe" with number "+1-800-555-1212' is being viewed, the SMS app shows "John Doe <,18005551212>"! If I attempt to just reply from within the thread, I will get an error indicating there was a problem with the number (due to the",")! So, if I want to reply to a "corrupted entry", I have to use the phone app's contacts feature to send a SMS and strangely when my message is sent, it automatically opens the SMS app with the correct name and number without the extraneous comma... If I then exit the thread to top-level listing of all messages, then re-enter the previously correct thread - the comma is now shown! It seems whatever database the SMS program uses is screwed up. By the way, I have even deleted a corrupted thread and when a new message is sent or received, the comma comes back!
Before I attempt a complete reinstall of everything and a re-sync with my Gmail contacts. (along with backed-up SMS, MMS & Call Log using the Market App "Backup to Gmail") , I was wondering if anyone else had experienced the same problem and corrected it?
Thanks, in advance, for your all's help...
Problem:
Occasional text messages are not "received". Just as a rough number, I'd say over 90% of SMS sent to me, I get. But I have been able to narrow down the problem with the missing ones.
I only noticed the issue because while at home or when I have headphones in, I have tasker set up to announce the name of the sender of a new SMS to me. Once in a while, it would say the name, but I wouldn't get a new text notification sound nor would I get a new message in any messaging app.
Phone info:
Nexus5
Android 4.4.4 rooted
Stock rom, kernel, etc.
Carrier is T-Mobile
Messaging apps used (not at the same time) are Hangouts, Smitten SMS, Google Messenger
Useful information:
1. This is NOT an iMessage issue. Missing messages have come from both android and apple phones. The last time this happened was today from a S5.
2. This is NOT a carrier issue. The message is received by the OS.
3. This is NOT an app issue. The message is not picked up by stock messaging app or any others.
4. This is NOT a formatting/encoding issue. I have people resend the message (copy/paste) and the resend always goes through and is shown in the messaging app.
5. This is NOT a group messaging issue. These are one on one conversations.
6. The missing message does NOT show up in /data/data/com.android.providers.telephony/databases/mmssms.db.
7. If I set up Tasker to log all incoming SMS, it IS able to log the missing message AS IT IS RECEIVED BY THE OS.
My theory:
Tasker can catch these missing messages, but the mmssms.db won't see them. So that tells me that somewhere between the phone getting the message and the phone logging it to the mmssms.db to be read by messaging apps, there is a failure. I do not know Android well enough to precisely say where this failure is happening. Because Tasker isn't logging them as they hit the DB but prior to that.
If someone more knowledgeable with how the android os handles SMS wants to chime in here, that would be great.
Anyone else experiencing the same? Any additional ideas here?
I am experiencing the same issue and searching to find a solution.
Android 4.4.4
Motorola Moto G
Cricket is my carrier
Did you ever find a solution? Thanks!
I started noticing a slowdown on my LG V20 in the last week or 2. It was very random. I believe it is because I have about 57,000 text messages.
I do not need 57,000 text messages. I normally use Chomp or Textra apps. At this time, some text messages started to not come through to me. For example, my boss texted me and then called me later when I did not respond. Screenshots show she sent the text but I never received it. This happens rarely, but has happened with my sister and my wife as well.
I loaded the default AT&T text message and asked it to truncate all converstaions at 1000 messages per thread (I have 2 threads over 12000 messages). It was unable to do it. I then installed Textra again and asked it to do the same thing - it could not delete old messages or keep conversations at 1000. However, Textra shows some of the dropped text messages. The other apps (Chomp, default AT&T, and Handcent) do not show them at all.
My only solution is to delete all the text messages. I would like to keep the recent ones but no app seems to be able to keep the limits I have set on the threads.
Is there some type of SMS/MMS management app that would manually force the conversations to their limits (1000 messages per conversation?).
I believe when I updated to this phone, and I transferred my messages from my S7, maybe an error was introduced?
One conversation thread has a triangle with an exclamation point inside it. Maybe that thread is damaged?
Any advice appreciated.