When looking at an individual text inside a thread on some of the longer messages it will have "..." in the middle of the message and I'll have to pinch-to-resize the message text to see what it said. It's incredibly annoying because I communicate almost solely via MMS/SMS E-mail during the work-day and it seems this has to be a wide-spread issue.
Anyone else have this issue or have a fix? :fingers-crossed:
Related
Hey guys & gals,
I am having an issue with most of my incoming SMS text messages not showing up in the Samsung Messaging App (or Handcent) Thread or Folders Views. They appear in the Notifications Bar just fine, but when I tap the Notification Bar and then tap on the Notification itself, it takes me to the Messaging App where I don't see the message at all. I see everything I sent out, but not what comes in (the majority of the time). Some incoming messages do show up in the threads, but most of them don't.
Anyone else having this issue? Any insight? Thanks!
Anyone???
No one has any input, ideas, suggestions, agreements or disagreements? Please!
yea i have had this happen on every device i have owned g1, nexus,hd2(with android) and vibrant. seems to happen every once in a while when it does i just delete the whole thread and they appear again. not sure why this occurs though
I have had my HTC Desire Z for a couple of weeks now and I am receiving the following message when typing a text message "The application Messages (process com.android.mms) has stopped unexpectedly. Please try again."
I have the standard ROM and have only done one OTA update and since then I think the problem has been happening. I did the update fairly soon after receiving the phone so I cannot be 100% certain this is the problem but I believe it could be
Does anyone have any ideas what is causing this and how I can fix the problem. I have imported my SMS messages from my old Nokia 5800 by bluetooth using the standard phone Setup wizard
When the message appears I get kicked out of the message I was typing and it is saved as a draft. The problem occurs if I use the on screen keypad or use the keyboard
The phone is not rooted or modified at all. I have a few applications I have downloaded but all of these came from the Market
Any help much appreciated
G2 user here and i have the same thing happening with one specific messaging thread. Every time the person would send me a text after the picture, i couldnt reply or view the messages until AFTER the message had scrolled past the top of my screen. If i scroll up to the picture, the messaging app crashes, so my only option is to delete the messaging thread (which i would rather not do).
It is probably a corrupt picture.
I am also open to suggestions on how to either delete that specific message without removing the entire thread.
i have had the same problem on my g2 after bit i discovered only happened to me consistently when i started writing an mms message (with photo) with keyboard closed and then opened the keyboard to type my text message once photo in message already - i get this crash when i send nearly everytime after the steps above (end up in draft without text i typed). not had this happen in ~1mo now as long as open keyboard first before starting the mms message. your mileage may vary !
Sent from my T-Mobile G2 using XDA App
This problem happens to my phone when typing and trying to send a standard SMS message. I have sent a MMS message but only one to get the settings and functionality enabled.
It is possible that I could have a corrupt picture message as I imported my messages from my old phone but didnt import any attachements or images so it could be the message is linked to a MMS picture which is no longer on my phone.
Is there either a way to disable all previous messages coming up when typing a new message or replying to a message or can I somehow get into the message database to remove corrupt messages
Hi all,
I work with a guy who has a Droid 2 and every time he sends a text message, it shows a failed delivery icon in the notification bar and says "2 Text messages not sent." When clicked, it just takes him back to the inbox. However, the message that is sent does reach its recipient (my Dinc for testing purposes).
He is not rooted, and he's running the stock messaging app (for all intents and purposes, he does not "use" his Android the way we do, it's a work phone).
Any thoughts on why it's doing this?
EDIT: For what it's worth, he does not have any "drafts" in his Messages that could be causing this issue.
EDIT 2: This has been corrected. There were unsent messages that the stock messaging app was not showing. Upon downloading Handcent, said messages were made visible and were removed.
I just got my Verizon Galaxy Note 3 yesterday and so far loving the device. I've noticed one thing that is a little odd though and wondering if anyone else is experiencing this. When I sent SMS messages, the "read receipt" doesn't work properly. If you press and hold an individual sent message and then select "view message details", it says "Error code:Addr.Vcnt.". The message however are delivered just fine and nobody on the other end notices. I use Chomp SMS as my SMS app, and because of this error code the messages always say they are "pending" instead of checking off with a green check box to indicate that they were received. I don't think it's a Chomp SMS issue because the same error code comes up if I sent my messages through the stock SMS app.
MMS messages work just fine, so the issue only occurs with SMS messages. Has anybody else experienced this and know of a fix?
pdykstra said:
I just got my Verizon Galaxy Note 3 yesterday and so far loving the device. I've noticed one thing that is a little odd though and wondering if anyone else is experiencing this. When I sent SMS messages, the "read receipt" doesn't work properly. If you press and hold an individual sent message and then select "view message details", it says "Error code:Addr.Vcnt.". The message however are delivered just fine and nobody on the other end notices. I use Chomp SMS as my SMS app, and because of this error code the messages always say they are "pending" instead of checking off with a green check box to indicate that they were received. I don't think it's a Chomp SMS issue because the same error code comes up if I sent my messages through the stock SMS app.
MMS messages work just fine, so the issue only occurs with SMS messages. Has anybody else experienced this and know of a fix?
Click to expand...
Click to collapse
Just as an update in case anyone else ever runs into this problem, I uninstalled Chomp SMS and read receipt started working again.
I'm running a rooted/debloated otherwise Stock T-Mobile Firmware on my SG5, and seeing a major strange WhatsApp problem This issue looks like a defeat of WhatsApp secure message pipe. I have turned it in to the Developer but no answer [other than the robot]. Description: In a group conversation where both Galaxy and iPhone are in play, I will randomly have a WhatsApp message notification with the tagged "Download" trigger for grabbing the attachment, but when doing so [opening the Attachment], the entire message suddenly moves from WhatsApp to the default Messaging app. Bizarre. I see nothing like this in any of their FAQ, but then it is a hard problem to search terms for.
is this a 'feature' of some kind at work that if the message has been compromised, before trashing it all it resends the entire thing to insecure Messaging? I could see some logic there.