How do I fix this issues where incoming messages are split and end up with 0001/0002 and the second part of the message is split into two messages?
Bump. Help?
Text messages are limited to 160 characters therefore it splits them and puts that 01/02 so the person receiving the messages knows what's first and second and third and etc
Related
Wondering if anyone else has the same issue in android that I have, where some (not all) of my incoming texts are displayed in in some asian character set.
After doing some testing, it appears to be that any text message I receive with an apostrophe causes the entire message to be converted to this non English character set. I'm on Sprint and so is the phone sending me the message.
Anyone else?
Any fix for this?
Thanks!
So I seem to have a messaging problem I cannot figure out. I can't pinpoint exactly when it started happening but it was around the time I installed CM7 RC1 or nightly 38...
I only get my messages in bunches some time after they are sent. Its like after a while multiple texts get pushed through, just not when they were sent from the person. Sometimes i get multiple texts in the wrong order. I've also figured out the only way to get the texts to come through is when i call someone. Once i call someone, multiple texts push through.....really strange
Its like the phone has to actively access the network before is receives text messages...
I have no clue what this could be, any suggestions
Similar issue
I loaded the same Rom but it appears if I send out a txt with multiple recipients only one recipient gets it.
Every time someone sends me a text from an iPhone to my Droid Incredible it is formatted as an MMS and appears that way on my bill. Anyone know how to fix that problem, on either end?
Is it every text message or just ones that are over 160 characters? I think those sometimes get converted to MMS, and sometimes they get broken up into multiple messages, depending on the messaging app.
I have been having the same problem for months, and have not found an solution yet. Any luck on your end? Oh, and for me it is every text message, even if the message is only a couple words long.
I use GoSMS and don't have this problem.
I have two related mediocre annoyances with text massages:
1. When sending a text greater than 160 characters, the receiver receives it split as two, starting with "(1/2)..." and "(2/2)...".
2. When receiving a text message greater than 160 characters, I not only see the same "(1/2)," but when it should be only two separate texts, it gets split into three and almost always out of order.
I've tried the stock messaging app, handcent, chomp, and go sms...same thing for all of them. I understand that this mostly has to do with Verizon's CDMA network. Is there anything that can be done in custom ROMs or Messaging apk's to fix this?
My info:
Network: Verizon
Phone: Galaxy Nexus
ROM: AOKP M3
Kernel: Matr1x
160 characters is the limit for sms text messages for every phone on the planet.
its the limit of the sms system, not the phones or the cellphone companies.
This is definitely just how SMS works.
That is an option in the settings of the SMS application. Normally, the message is joined automatically by the receiver phone, unless you specify that the GN has to split it itself.
cirian75 said:
160 characters is the limit for sms text messages for every phone on the planet.
its the limit of the sms system, not the phones or the cellphone companies.
Click to expand...
Click to collapse
Yes, I'm well aware of that. However, the text messages are not getting rejoined by neither sender nor receiver as they should be.
I noticed that when receiving some international SMS sometimes the numbers don't show "+"
And hangouts gets screwed up.
For example I'm texting someone in UK using +44XXXXXX number
They respond but now the number looks like 44XXXXXX without +
So hangouts doesn't associate the incoming message with the same contact and decides to open a new thread. But I cannot even respond to message in the same thread because I need the + sign. So now I'm receiving messages in one thread and sending them in another.
I don't remember ever having this problem with stock messages app. How can I fix this?