I'm having this strange issue where my messenger has decided to start converting conversations to MMS automatically for some reason. It seems to be when I am texting iphone users, but I can't 100% confirm that.
For simplicity's sake let's say I start a new text message conversation with someone. I add them to the recipients section and send them a message. First one works fine. Now I press the back key to go back to the screen where all my conversations are shown. Instead of the contact name that was there when I started conversation, the phone number is displayed followed by the @provider.com (IE [email protected]). If I go back into the conversation i get a little popup at the bottom saying "Converting to MMS." The contact at the top is still listed as the phone number and not the contact name. If I try sending a message it doesn't go through.
I scrolled through my conversation window and I noticed that my phone also converted several old conversations in this same fasion (changed the recipient to a [email protected]). Now anytime i need to send a text to one of these people I have to start a new conversation every single time.
I tried to clear cache out and data for the messaging app and it continued to happen. The weirdest part about this is that the default messaging app, and gosms both convert the conversations, but textra does not.
Has anyone ever experienced this type of behavior before? I did some googling but couldn't turn anything up.
Something similar: when I write slightly longer SMS, it tells me: converting to mms, and they don't go through. This didn't happen to my previous phones. . But I did not notice the change in recipient ID.
Sent from my SM-G935F using XDA-Developers Legacy app
I think you cab set the max length inside an XML in system. I can't remember which duke though, sorry.
It sounds like you have a short limit, which causes the text to become an MMS.
ras0787 said:
I'm having this strange issue where my messenger has decided to start converting conversations to MMS automatically for some reason. It seems to be when I am texting iphone users, but I can't 100% confirm that.
For simplicity's sake let's say I start a new text message conversation with someone. I add them to the recipients section and send them a message. First one works fine. Now I press the back key to go back to the screen where all my conversations are shown. Instead of the contact name that was there when I started conversation, the phone number is displayed followed by the @provider.com (IE [email protected]). If I go back into the conversation i get a little popup at the bottom saying "Converting to MMS." The contact at the top is still listed as the phone number and not the contact name. If I try sending a message it doesn't go through.
I scrolled through my conversation window and I noticed that my phone also converted several old conversations in this same fasion (changed the recipient to a [email protected]). Now anytime i need to send a text to one of these people I have to start a new conversation every single time.
I tried to clear cache out and data for the messaging app and it continued to happen. The weirdest part about this is that the default messaging app, and gosms both convert the conversations, but textra does not.
Has anyone ever experienced this type of behavior before? I did some googling but couldn't turn anything up.
Click to expand...
Click to collapse
try another sms app!
if it works fine with another app then go to setting > apps > select samsung sms app > storage : clear cache & data then force stop!
:good:
Related
Yesterday, I was texting with someone with who I texted a lot. When you press "All messages" you get the windows mobile messages. Suddenly, every message I've received from that person was gone when you pressed that person's name in the messages list.. When I then go into the TouchFLO messages I still see all the previous ones but in the Win. Mobile they're all gone.. Is this because of an overflow or something? And is there a file where every message is kept?
Mike
I was reading something on here not long ago about text messages. Basically, there are 2 copies. 1) in WM itself, which appears under the messaging application. 2) in TF3D itself. To delete all messages, you need to delete from both areas.
Ok so this notification just started on my Eris! when I get a message(only text not emails) this grey envelope with a arrow on it comes up in my notifications even after I’ve read and replied to the message its still there until I click it and i take me to the message that ive already replied to. I’ve turned of all settings has far as auto retrieve and text notification but it still comes up! I deleted a bunch of apps thinking maybe one of them was causing this. I called htc they had no answers but to do a hard reset and lose everything not something I want to do! So if ya know something that would help please let me know thanks!
I found a fix
Aspotcat can be downloaded from the market it will show you what is running with ur text. found out some weird app was on there but no where to be found in my phone deleted it and problem solved!
Okay..seems like you have two text message applications....
IF thats the case, then try the following:
Your stock application can be reached from the app drawer...go there and then open the stock sms application...then go to settings and remove the check next to "notification"....
Now you should only have a notification every time you receive a text from the secondary application you're using..(i.e., handcent, byte sms, etc)
Now if you did that and your message is still showing..delete all of the messages in the stock application...this should clear it...or then simply open every single text up..(im sure you're running threaded messaging so it'll be a little eaiser)
If that still doesnt work...repeat the following using your secondary messaging application (handcent..blah blah)
Now if you did that and your message is still showing..delete all of the messages in the stock application...this should clear it...or then simply open every single text up..(im sure you're running threaded messaging so it'll be a little eaiser)
If you're still having problems...and are on a rooted rom....reflash a custom rom and you'll be fine!!
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
I have a problem with the incoming SMSs ,when I receive a sms the time on it is lagging behind my DELL STREAK set time,when I select either internet time or service provider time. Eg time set through internet is 7.00 PM but when I receive a reply for my msgs/sms it is 6.50 PM ,thus it is lagging behind,and the sequence of the msg thread becomes upside down.If I correct this lag by manually setting the time,my mobile clock becomes 9-10 mins behind actual time.how do i correct this?the sim works fine in other handsets.
Sounds like its the sms app itself, try looking through in app preferences for time stamp issues if that doesnt work try "go sms" free from the market, it has various fixes, troubleshooting options which may isolate the problem
Ya mine does the same thing on the Rogers network. It's pretty frustrating - I tried some different apps, the is an sms time fix on the market that worked, but then it broke my notifications, so the sms would come in showing the right time, but I wouldn't be notified of new messages, so that didn't work for me.
As mentioned above, the best remedy for me was to use another sms app, like go sms or I actually prefer Handcent SMS, all free from the market, Handcent SMS fixed the time issue and also has some other cool features that I like including an unread reminder etc.
I'm not sure why no one knows what causes this or how to fix it in the native app, but either way, the other sms apps are better anyway so you win in the end
-Steve
What settings do you use on Handcent? I'm on Rogers too and my SMS come in with a -4 hour timestamp. Not all though, but some. So it's pretty weird.
isnt the time stamp on a text, the time it was sent not the time it was recieved. So maybe you phone is just taking ages to recieve texts?
No, it doesn't take 4 hours to recieve a text. Something is screwing up the incoming text's timestamp. When I get a text without first texting someone, it displays the correct incoming timestamp, but if I close Handcent and then open again, it will show that message as -4 hours. The minutes remain correct though. But if I text someone and they reply, the timestamp remains correct. Been trying different settings in the Recieved Messages menu. Provider's delievery report checked, unchecked. Handcent delievery report checked, unchecked. Combinations of the two. Offset recieved messages by -4 hours. Can't seem to fix that little quirk.
I got the Samsung Gear at IO (yea) and have been going through the user adjustment phase, happily have pretty much everything working (I use a Galaxy Nexus as the phone stock. I receive text and I can send emails (from the watch) but for some reason I can't send text from the watch. It says it is sent, goes through all the motions, asks for recipient, clarifies to send to the mobile number and gets the text via voice and then says it is sending and gives a success green check, but the message is lost does not show on phone hangout or messaging log, nor does the recipient get it.. Anyone have any ideas?? or is my problem unique to me?
Hidden choice message on Phone for sending text
Finally found my "missing texts.. when I was sending, the phone was opening a choice dialog to choose between Google voice or messaging, I chose messaging and checked always and all is now working, buy the way retweeting to twitter using the bunting app has a similar issue, it opens the native vs edit retweet chice, which cannot be set to default one way so you need to pull the phone out...