Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Using two 2.0 emulators and the native messaging application –
if I send a text message which exceeds 160 characters in length, the receiving emulator gets the message, but the text is all scrambled. Does anyone else see this? Is this a bug with the emulator, or a real problem with the 2.0 devices as well?
Thanks
Yes, I have seen it too.
There is a standard limit on the number of character a SMS message can contain and it is 160 characters(when each character is represented using 7 bits).When the length of the SMS exceeds 160 characters your message is received on the other emulator in parts. The encoding gets affected also, I think and therefore we see garbled characters.
Also, note that when the number of characters in your SMS exceeds 160×3 characters your message is converted to MMS automatically, on the emulator. If you are trying to send it from code, send it as an MMS; MMS can handle longer messages SMS only 160. Alternatively, you can also send data as Multipart SMSes.