I am on my 2nd phone and am still having this issue. My text messages split into multiple messages and not within the Sprint rules of 160 characters. Example...
Hey, I just wanted to say th
at i think you should try ano
ther phone.
That would be 3 different txt messages. Ive checked and unchecked the reassemble message box, replaced the phone, used the stock message app as well as GO, and still no luck. My gf has the same phone but hers doesn't do it.
Which language? English I assume? Try changing from US english to UK or something else.
Reason: I write in another language with special characters, and these seem to take up more 'characters' than standard ones. Has happened on 3+ different phones now.
I'm not sure if this applies to you, but if you use an emoji in the text, you get a limit of 60 (I think) characters per sms.
Related
Does anyone know what to add or remove or change in the registry to allow more than 160 characters on sending SMS ?
Thanks
this is a standard sms thing... you cant change how many characters to send in one message.. now you can type over 160 and your phone should display like 168/2 where the first number is characters and the 2nd number is how many sms' its going to send... and when it sends most newer phones will combine the 2 messages on the recieving device and it will display as 1
My O2 Xda Stealth shows as you described, however, it also gives me an error "Your Text Message cannot be sent". It works perfectly within 160 characteres (1/160) but as soon as you start with (2/320) shows the error when you hit SEND.
Any ideas ? Could you provide the Registry ?
Thanks
Maybe some restriction from your provider, I have O2 XDA Stealth too and I am sending longer messages without any problems...
Ok, thanks, let me go back an ask my Network provider to see if I have restriction.
shogunmark said:
this is a standard sms thing... you cant change how many characters to send in one message.. now you can type over 160 and your phone should display like 168/2 where the first number is characters and the 2nd number is how many sms' its going to send... and when it sends most newer phones will combine the 2 messages on the recieving device and it will display as 1
Click to expand...
Click to collapse
This issue was a nightmare for me until I realized how to overcome with continuous efforts. In my case I use the arabizer and thus, I can send 160 char. in one shot (english) but when I change to arabic, the number of char. turns to 1/70 (i.e. max of 70 char. per shot).
Now, that wasn't the case always, I upgraded to one of the latest arabizer versions and surprisingly, everytime I wanted to send english sms it only allowed 70 char! I had no time to dig and find out why is this happening, though I crossed check between older cab files and new ones and found that among the difference was that the new one had two fonts files those are "tahoma" and when installed, voila the problem was solved.
The moral is it is not a standard SMS thing, it is something with localization characters. May be
This is not the case. The question if you can send full 160 characters or only 70 characters depends on the fact wheather you use ASCII or UNICODE. In case of use Arabizer or some special national characters (same for us here in CZ), you can send only 70 characters per one message, but then you can continue and you can see i.e. 75/2 and the longer message will be sent by 2 parts. But he cannot send more than one message at all...
In my case was the Network. For some reason there was a limitation on sending SMS. Network customer service did not resolve my case, I surfed in Internet and found some tricks for GSM networks.
Bottom line I just write down the following ##004#[SEND] and then I received a message from the network "Success" or something like this (don't recall). But it was enough to be able to send more than 160 characters (obviously the system splitted it in "n" numbers of SMS when you submit it)
Hope it could also work with other peoples
Hi,
I am new to this forum, and I have problems.
I own a Sprint Touch.
I have installed a program Diopen, which installs the Korean IME and the font. So far I am able to read the Korean and write it through IE and Contacts, etc.
However, when I send a txt message and email that I wrote with Korean, the receivers (including me, I sent to myself both txt and email) only see ??? for email, and ____ for txt message.
Is there any way to see foreign language on emails and txt message?
At least for the email, I mean, email suppose to support all langaguages, but even the computer with various encodings shows the broken ???? letters.....
Help will be much appreciated
Thank You.
to add this, I use Windows Live for email and text.
I searched through the forum, so far the only solution for text message seems to change the setting to Unicode.
However, I dont see the setting that changes the message to Unicode on Windows Live.....
Are you in Korea when you sent the messages?
I read about that text messages managed by Korean telcom operators are encoded in KSC5601, instead of unicode which is used by other non-western languages like Chinese or Japanese. As such, unicode-typed korean text messages sent or received from oversea operators are not compatible, unless interoperability is ensured by the overseas carriers themselves. Not too sure but I read in the news that some cellphone operators in Philippines maybe one of them.
I am using Sprint Touch, also I am not sending txt oversea..
However, emails also doesnt work.. I used the encodings Korean, UTF-8 and Western European, but still the computer reads the emails full of '???????'
I tried mixing up the letters, I send 'ABCD (some korean)' and the email reads from my computer as 'ABCD ?????'. English reads perfectly but korean doesnt.
So far I have assumed to be and hoped to be only software problems, but someone from ppcgeek said that Sprint doesnt support Unicode? so that foreign languages cannot be sent.
edit...
it's not working.. i need to find a better way to extract those dll... in the mean time you can flash to hutch's rom and you will be able to send as unicode..
cheers
Hi, I am currently experiencing a wierd SMS issue on my Desire running Robo's HD rom 0.13. Lets point out first that my sms is fine, I can send and receive texts perfectly. Except for one contact.
Me and my girlfriend text a lot, and I believe my phone doesn't want me to. Whenever I text her, she texts back, and I go to text her back,it says message not sent. However, if I delete the thread (with two messages in) and create new message,it sends fine. Baring in mind we exchange around 100sms per day, I am having to delete the thread and create a new text message just to get one through, which is getting quite annoying. I shall just stress this is the only contact out of the 25-30 people I text regularly who I am having this problem with. The things I have tried are:
Deleting and creating new contact
Changing her number to various formats (+44, 44, 07 etc)
Reboots (many of them)
Changing her contact name
Different sms apps (chomp, stock, handcent)
Nothing has worked, and the problem still remains. I would really like this sorted, as it is getting quite annoying. Any help will be greatly appreciated.
tucka20 said:
Hi, I am currently experiencing a wierd SMS issue on my Desire running Robo's HD rom 0.13. Lets point out first that my sms is fine, I can send and receive texts perfectly. Except for one contact.
Me and my girlfriend text a lot, and I believe my phone doesn't want me to. Whenever I text her, she texts back, and I go to text her back,it says message not sent. However, if I delete the thread (with two messages in) and create new message,it sends fine. Baring in mind we exchange around 100sms per day, I am having to delete the thread and create a new text message just to get one through, which is getting quite annoying. I shall just stress this is the only contact out of the 25-30 people I text regularly who I am having this problem with. The things I have tried are:
Deleting and creating new contact
Changing her number to various formats (+44, 44, 07 etc)
Reboots (many of them)
Changing her contact name
Different sms apps (chomp, stock, handcent)
Nothing has worked, and the problem still remains. I would really like this sorted, as it is getting quite annoying. Any help will be greatly appreciated.
Click to expand...
Click to collapse
Tried another radio?
jmelhus said:
Tried another radio?
Click to expand...
Click to collapse
Yep, forgot to mention have used both 5.09.05.30 and 5.10.05.30 with the same results. She has no problem texting me (hero with cm 6 froyo), nor does her friend texting her (stock 2.2 desire)
tucka20 said:
Yep, forgot to mention have used both 5.09.05.30 and 5.10.05.30 with the same results. She has no problem texting me (hero with cm 6 froyo), nor does her friend texting her (stock 2.2 desire)
Click to expand...
Click to collapse
Well, I'm experiencing it sometimes as well on my phone, but not as frequent as you are describing here.
I had this issue once with a Sony Ericson. It dissapeared when changing carrier and sim. Maybe you can try a "pay as you go" sim card for one day?
Ok, this is so weird. Had this problem on Android 4.0.2 and it's still here in 4.0.4.
As soon as I start typing in my language (I'm Roumanian), using any 3-rd party keyboard, I get a limited number of SMS characters.
When I type in English I find no problem. I get the 167 characters normal for a SMS message.
I attached two screenshots to show you what I'm talking about.
Does anyone have an answer? What should I do?
I cant see your attached image (the server is blocked here) but I have this same problem writing in portuguese. It is because of the encoding of the accents. As soon as you include an accent the encoding of the entire message changes and the message limit is reduced.
juliano_q said:
I cant see your attached image (the server is blocked here) but I have this same problem writing in portuguese. It is because of the encoding of the accents. As soon as you include an accent the encoding of the entire message changes and the message limit is reduced.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I even tried 3-rd party SMS apps and still I get only 70 characters out of the normal 167. Is this an issue that Google overlooked?
Edit: It seems that Apple users are experiencing the same issue.
"This is only an issue for non-English speaking countries... That's why this is not a big deal for the North-Americans that (comprehensively) sometimes simply don't understand what are we talking about...
In any mobile Phone (iPhone included), when you write a SMS using special characters like "ç","á","é","í","ó","ú","ñ","ä", etc, the SMS are limited to only 70 characters instead of 160 characters because a extended encoding is necessary! So, you pay 3x the price of an SMS if you write 160 characters (it will send 3 SMS: 70+70+20). Besides that, the risk of the SMS not being delivered is higher because it is actually sending 3 SMS at once and sometimes it gets broken in the way.
So, to solve this issue, there is a feature in any Nokia mobile phone almost for 10 YEARS (!!!) called: "SMS Extended Character Set": ON/OFF
If turned ON, it uses extended character set with 70 characters per SMS and the destination Phone gets all the special characters: "ç","á","é","í","ó","ú","ñ","ä"
If it is turned OFF: the phone allows to write special characters, with 160 characters per SMS, but automatically converts the special characters to their basic equivalents "c","a","e","i","o","u","n","a" when sending the SMS.
... It is amazing how Apple is 10 years behind other mobile manufacturers in this matter... Maybe because Nokia is originally from Finland (where they use special characters and experienced the issue) while Apple is from the USA, where they naturally (and sadly) don't recognize this as a issue.
Imagine if you send 1000 SMS in a week and you have to pay them (many people pay them)... You have to be very careful not to introduce any special character otherwise you pay 3x the money!"
Hi everyone, it's good to be back after a while!
Whenever I send a text message to someone, no matter who it is, I type everything correctly, like ã, é, õ, ç and all the special characters that my language has, and I also send emojis, as everyone else does.
My problem is that the receiver only receives normal letters without the special characters, a capital Ç and blank spaces instead of the emojis I've sent.
This has me believing that for some reason, my Pixel "turned on an option" that only lets me send SMS in the most basic format possible, like it used to be back in the day, before SMS evolved to supporting emojis and all that. The only way I can send "emojis" is if I type ": - )" instead of choosing an actual emoji.
I've been in touch with my carrier (Vodafone) and they said there's nothing wrong with my SIM and that the problem should be on the phone, with a reasonable doubt.
Has anyone around here experienced a similar issue? I've tried everything I can remember, including a Factory Reset but nothing did the trick.
EDIT: I forgot to mention that I've had a popup message show up on Messages saying "to support a message from your carrier, the message needs to be converted" (or similar) and it makes you tap Yes or the message won't be sent.
Best Regards and sorry for the long post! :good:
awildsloth said:
Hi everyone, it's good to be back after a while!
Whenever I send a text message to someone, no matter who it is, I type everything correctly, like ã, é, õ, ç and all the special characters that my language has, and I also send emojis, as everyone else does.
My problem is that the receiver only receives normal letters without the special characters, a capital Ç and blank spaces instead of the emojis I've sent.
This has me believing that for some reason, my Pixel "turned on an option" that only lets me send SMS in the most basic format possible, like it used to be back in the day, before SMS evolved to supporting emojis and all that. The only way I can send "emojis" is if I type ": - )" instead of choosing an actual emoji.
I've been in touch with my carrier (Vodafone) and they said there's nothing wrong with my SIM and that the problem should be on the phone, with a reasonable doubt.
Has anyone around here experienced a similar issue? I've tried everything I can remember, including a Factory Reset but nothing did the trick.
EDIT: I forgot to mention that I've had a popup message show up on Messages saying "to support a message from your carrier, the message needs to be converted" (or similar) and it makes you tap Yes or the message won't be sent.
Best Regards and sorry for the long post! :good:
Click to expand...
Click to collapse
In Google message app, settings, advanced there is an option for simple character set, try change it
siggey said:
In Google message app, settings, advanced there is an option for simple character set, try change it
Click to expand...
Click to collapse
It's already turned off, didn't do the trick unfortunately.
awildsloth said:
It's already turned off, didn't do the trick unfortunately.
Click to expand...
Click to collapse
Hi there , where you able to solve this?
I'm on Vodafone PT too and I'm having the same problem , the Pixel 2 only sends blank texts when I send a emoji.
The problem isn't with your P2XLs guys. Ask your recipients if THEY have the simple character set enabled in Messages. If they don't the problem is possibly font related on their end.
Strephon Alkhalikoi said:
The problem isn't with your P2XLs guys. Ask your recipients if THEY have the simple character set enabled in Messages. If they don't the problem is possibly font related on their end.
Click to expand...
Click to collapse
The problem is some incompatibility with AOSP and the way it manages the Unicode with Vodafone PT or something like that, beacuse the Emojis work with other mobile carriers and with Vodafone PT they don't.
It's really something or with Google or with Vodafone.
Vodafone more than likely. If it were Google it would be a global issue, affecting all handsets. This issue isn't affecting mine.
Strephon Alkhalikoi said:
Vodafone more than likely. If it were Google it would be a global issue, affecting all handsets. This issue isn't affecting mine.
Click to expand...
Click to collapse
But do you have Vodafone PT as a carrier?
No I don't, and that's why Vodafone is the likely culprit.