My wife has had a Note 3 for a month or so now. She's on stock unrooted 4.3. When she uses the default messaging app and writes an SMS message longer than 160 characters (I haven't counted, but presume this is an SMS 160 character limit issue), only the first 160 characters send, and the rest of the message never gets to the recipient. The app gives no indication that anything unusual has happened. We only figured this out by sending messages back-and-forth and comparing the results. I use a Galaxy S4, rooted stock 4.2.2, and the default messaging app doesn't have the same problem. Using Handcent fixes the issue on her phone, but she prefers to use the stock messaging app. I've searched here, the Sprint Community, and on Google and don't see anyone else having this same issue. Any ideas?
Auto combination checked?
Thanks for taking the time to reply...turns out the issue is with my S4, not the Note (I haven't figured out what it is yet)...please feel free to delete this thread.
Chops it up on both Verizon and Sprint s4's I have also.
In case anyone comes across this later with a similar problem, unchecking that auto combination box in the messaging app on my S4 fixed the problem...I have Handcent set as the default SMS app, but I guess that check box still affects the handling of large SMS.
Related
I have Google Voice integration set up via Sprint (and I'm using the default text message handler).
For some reason when I have a conversation actually open on the screen I can get a text message (sound and vibration), and the message bar at the top will preview it, but it's not showing in the actual conversation.
I've missed several MMS this way (as well as normal texts).
Craysh said:
I have Google Voice integration set up via Sprint (and I'm using the default text message handler).
For some reason when I have a conversation actually open on the screen I can get a text message (sound and vibration), and the message bar at the top will preview it, but it's not showing in the actual conversation.
I've missed several MMS this way (as well as normal texts).
Click to expand...
Click to collapse
yea, if i read your post right, it sounds like the same bug i've been experiecing. def an odd bug in the htc sense messaging app they provide as stock software. i'm also using gv thru sprint integration. usually hitting the back arrow to exit the conversation and move back to the sms inbox then allows the new message to populate.
because of this bug i've now developer the habiting of exiting all conversations and going back to the inbox before turning the screen off or switching programs.
if you're experiencing a different bug, could you perhaps provide more detail?
Pretty much the exact same thing except it never comes back, even if I hit back and go back into it.
I'll give another messaging app a try.
Craysh said:
Pretty much the exact same thing except it never comes back, even if I hit back and go back into it.
I'll give another messaging app a try.
Click to expand...
Click to collapse
oh how odd the message doesn't appear when you exit the conversation..
perhaps there is an issue with the sms-mms database the app is using. the only easy solution there would be to wipe the database it is using and start fresh. i don't think there are any tools for analyzing the sms-mms database used by the htc messaging app as the sms-mms databased used by the aosp messaging app is different.
if wiping the database doesnt clear the issue, then it would appear most definitely to be a htc messaging app bug.
also, the nice option with google voice is you can check the gv app on your device to see whether or not the actual message came all the way through. if it appears in gv, but not in htc stock messaging app, thats def a bad sign for the htc messaging app (assuming you have good cell signal).
perhaps one of the developers might be encouraged to take a look into the app and see if its a bug they're able to fix through decompiling and recompiling the app.
Handcent seems to have fixed the issue.
I wouldn't be able to check Google Voice since the issue seems to have been most prevalent on MMS messages.
I've had lots of issues with Google Voice integration. I would randomly stop getting text messages for 1-2 hours at a time, every 2-3 days. If I checked Google Voice the messages were there, but they never came in on my phone. I could send messages to other carriers just fine. I couldn't get their messages though. Sprint was no go both ways.
After I deactivated Google Voice, the issue went away. Sucks, I'd love to use the application.
Currently using Handcent as my messaging app (but have also verified this in the stock messaging app). Whenever I get longer type of texts from my friends (most using iphones) it shows as a MMS message.
Is there a setting I may have missed to stop this? It's getting really annoying.
Also, is there a way to disable that stupid slideshow when someone sends more than 1 picture in a text?
I text back and forth with my wife all the time... She has an iPhone 4S. I have never had any of her texts arrive as MMS unless they were that. I still use the stock app and running on the stock ROM unrooted. You said you verified this on the stock app, but was that ever before installing the Handcent app or only after?
As far as the stupid slideshow issue... I hate it too... Even if it's only 1 single solitary picture it will play the slideshow... Stupid... Not sure why, but I can't help with that.
Should be normal......... depending on how much you're typing. If you pass the length of 3 text messages, it automatically gets turned into mms to be able to send all of it in one go.
If you're typing less than 3 text messages worth and it still gets sent as an mms, you have a problem.
Sent from my SAMSUNG-SGH-I777 using XDA App
I recently flashed an AOSP rom, Rage 1.6 to be exact, and I noticed that when I text them ladies, messages over 160 characters/letters get split up into multiple text. So eventually the receiver gets up to 3 separate texts for 1 message. Do all aosp roms do this?
im_high_tech said:
I recently flashed an AOSP rom, Rage 1.6 to be exact, and I noticed that when I text them ladies, messages over 160 characters/letters get split up into multiple text. So eventually the receiver gets up to 3 separate texts for 1 message. Do all aosp roms do this?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Short_Message_Service
The maximum length of any SMS message is 160 characters. If you send one longer, the recipient always receives the messages split up.. its just a matter of whether or not their SMS client (or yours for that matter) displays them as a single message, or displays them broken up into the individual messages.
While some SMS clients do recognize multiple messages to be parts of a single longer message and display it as such, others don't.
For example, I don't use the stock SMS client for Android. I only use Google Voice, and it always displays longer messages as one coherent message, even though the recipient's client may display 3 separate incomplete messages.
Using the stock messaging app on Adrenaline 2.0, I texted someone a lengthy message (over 160 characters) and they received it as a whole message. Then when I flashed an AOSP rom, using also the stock messaging app, I texted the same person. It started breaking up the text into multiple messages. I just tried using Handcent SMS and now that person is receiving one long text instead of multiple.
So basically it's the apps fault hu? I just wish there was a setting where I could change it.
Some apps provide the ability to send longer messages (>160 char) as MMS instead of SMS. I couldn't guess what the default setting is, but I know handcent has that ability (I've used handcent since I had my original Moto Droid).
im_high_tech said:
Using the stock messaging app on Adrenaline 2.0, I texted someone a lengthy message (over 160 characters) and they received it as a whole message. Then when I flashed an AOSP rom, using also the stock messaging app, I texted the same person. It started breaking up the text into multiple messages. I just tried using Handcent SMS and now that person is receiving one long text instead of multiple.
So basically it's the apps fault hu? I just wish there was a setting where I could change it.
Click to expand...
Click to collapse
theascended said:
Some apps provide the ability to send longer messages (>160 char) as MMS instead of SMS. I couldn't guess what the default setting is, but I know handcent has that ability (I've used handcent since I had my original Moto Droid).
Click to expand...
Click to collapse
yep sense based roms will convert an sms to mms seamlessly so you dont see the splits. if you want to make it longer in aosp just send an mms.
More than 160 characters in a text? Dude...send an email at that point.
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've been attempting to use Signal as my default SMS app for the convenience of not switching between two different apps for messages. It mostly works fine, but as the title says, if I send a long SMS that needs to be split into multiple messages, it always fails to send. I'm on US Cellular, if that matters. It doesn't have an issue with this functionality in the default app (Google's Messages) or the other third party SMS app I tend to use, Pulse SMS from Luke Klinker. It also doesn't have any options to convert long SMS to MMS, as some apps do.
Googling for the issue, I was able to find some similar problems for specific model of phones from a few years ago, but that had all appeared to have been reported on and patched at that time.
Is anyone else using Signal on their V30? If so, can you successfully send a long text message?
If anyone has any suggestions or anything, let me know. Otherwise I'll try to report it to the Signal team soon.