We have moved to a new Sailfish OS Forum. Please start new discussions there.

Problems with "long" SMS messages (>160 chars.)

asked 2015-07-22 15:38:25 +0300

harrall gravatar image

updated 2017-04-05 10:21:51 +0300

Mohjive gravatar image

An SMS message is limited to 160 characters. You can of course write longer text messages, and have them combined into one continuous message. This is, however, not handled properly when emojis are used simultaneously with an SMS longer than 160 characters. I have tested this by messaging back and forth with an iPhone 5 and it seems that messages longer than the limit for one message, when combined with emojis, consistently get distorted. Depending of the message, the middle part can be left out or some ending from a previous long SMS can be attached. Have anyone else experienced this? And what might the problem be? I generally have little knowledge with encoding, especially with emojis and whatnot (they sometimes occopy more than one character space it seems).

Edit: I see this regularly and the message doesn't have to have emojis in them.

It happens quite frequently on my phone atm (large databse?) and I would be happy to provide more information about the issue if someone explained what I can do to collect it. Reach me at @Mohjive

edit retag flag offensive close delete



I have the same problem but I'm not sure if it's related to emojis. I got a long SMS and its first part is okay but the rest is something about getting ice cream and that was definitely not part of the original message. What's going on here?

Yo ( 2015-07-25 16:49:29 +0300 )edit

There is also: [Bug] Received SMS mixed together

Problems are existing with receiving and sending!

I have < 1024 messages with a contact. Received a message which made no sense (sender likely placed emojis in it). The beginning is missing and I just received the end.

Even worse:

Contact with some more messages, don't know if > 1024 but I don't think so. I sent a long message. It's in the history exactly as I wrote it. But the recipient got the begin with content from a sms I've sent 5 months ago, and the end with content of the actual one. Thats a no go which can have terrible consequences depending on whats getting mixed up here.

So has anyone of you opened a ticket? Is Jolla aware of this terrible bugs?

It could be a reason for me to switch mobile os. Because I now feel very insecure and uncomfortable as I don't know what content my device will really send.

A day or so after the receive bug appeared about every second message didn't get sent (correctly) (provider answered with an automated sms that it could not be transfered). To overcome this the message had to be written new i.e. with copy and paste. I backed up and imported my messages with the backup function after that. This solved the provider does not "want" to send issue. But the bug of sending wrong content happened after that, so with a relatively new imported database. Receiving bug was while on 1.1.4, sending bug on 1.1.6!

This all happened after I used xmpp for some days. But this messages were already deleted and the protocol was deactivated.

Halo2 ( 2015-07-31 19:08:49 +0300 )edit

I started a poll to see if it's related to many messages or database tempering. Please vote.

Yo ( 2015-08-19 18:44:16 +0300 )edit

Not using emoji, but have same problem.

nauevg ( 2016-06-05 18:08:25 +0300 )edit

Any news on this issue?

nauevg ( 2016-09-02 17:53:13 +0300 )edit

3 Answers

Sort by » oldest newest most voted

answered 2015-07-22 18:52:18 +0300

iKeivs gravatar image

Emojies requires different character encocing, because the general encoding system for SMS is ASCII. But when a SMS contains a different character (Not ASCII) then message is shrinked to 70 with something letters. Very common practice in Eastern Europe, because their alphabets contains a characters, which are not included in ASCII encoding. OK, enough with theory. I hope, that You understand what I mentioned.

edit flag offensive delete publish link more


Oh - so SMSs are sent with UTF-16 when they contain non-ascii characters? That seems stupid (unless you are the telco company), since UTF-8 would not have this problem.

Federico ( 2017-04-05 20:36:48 +0300 )edit

answered 2017-04-16 15:16:41 +0300

nauevg gravatar image

Look at this solution - https://together.jolla.com/question/102020/bug-received-sms-mixed-together/?answer=159895#post-id-159895. It helped me with mixed sms. Maybe this is the reason of this problem too.

edit flag offensive delete publish link more

answered 2015-07-22 19:36:31 +0300

Herve5 gravatar image

My experience at this moment is with Android SMS software (still waiting for the tablet ;-) On these softwares I learned that indeed the specific encoding of emojis (and of special characters : accentuated letters, etc.) can be done in various ways, that generally are dealt with properly, but there are some combinations of SMS transmitting and receiving softwares that will fail.

For instance, sending emo/accentuated chars from the android standard sms app to Blackberries fails (the blackberry receives parts of the sms interleaved with garbage chars).

To solve this in that specific situation I was led to abandon the standard andro SMS app and use instead an open source alternative, that presumably uses a more classical encoding -and in this case, with the same pair of phones, it does work.

So, my advice would be to try an alternate SMS sending app.

FWIW, the one I use on android is named 'SMSdroid', and is installable via F-Droid (which in turn, I heard, is available on Jollas)

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2015-07-22 15:38:25 +0300

Seen: 863 times

Last updated: Apr 16 '17