When I type an accentuated character the number of available characters decrease. As an example, when I start a new sms I have 0/160 characters available. Then if I type an 'รก' the counter reads 1/70 but if I type an 'a' it reads 1/160. I think I had the same problem in my old Nokia phone and I solved it deselecting unicode charset or something like that but I can't find that option on the desire z... can anyone help me?
I have the same problem in French.
There is no solution but praying that Google decides to fix this. There's an open issue on the Google Code page here http://code.google.com/p/android/issues/detail?id=6522 but few people starred it. The more people will star it the more chances we have to see it fixed someday.
It's not a Google issue. The problem lies with the encoding of those characters.
The "content" part of the SMS can have a maximum of 160 characters when encoded in 7-bit ASCII. This means each character takes up 7 bits. However, the standard ASCII encoding only included the basic latin characters. Letters with diacritics need to be encoded in unicode (16 bits/character), which limits the SMS size to 70 characters.
Details here: http://www.mediaburst.co.uk/blog/the-gsm-character-set/
and here: http://www.bullsmind.com/technology/spanish-language-and-sms-messages/
Related
As a former 3y user of UIQ3 phones ( SE M600 & P1 ) I'm missing some very comfortable functions as :
1. Adding multiple SMS recipients at a time. I usually send messages to 20 or more recipients and selecting them 1 by 1 takes a looooot of time.
2. Displaying contacts in different pattern - for example company first, name second etc.
Thanks for helping.
1. In the "To" field of the messaging app, you can simply start typing the contact's name and it will predict the number. It's intuitive, easy and fast. So this shouldn't be a problem.
2. In the default Windows Mobile contacts app, you can view by company or by name. So, also no problems here.
By the way, this is not specific to the TP2. This applies to all Windows Mobile devices. You may want to do some more research into this platform if you are interested in buying it.
by the way: is it possible to create SMS-Groups like in 3rd Party tools ?
Hi all,
Ive noticed for my ATT tilt 2, the text messaging limits it to only 160 characters. When i go over the 160 character limit, i dont see the rest of the message and im not sure if whether the characters past 160 characters are sent or not. Is there anyway to change this? Thanks in advance for any replies.
Cheers!
ATT has a limit per characters per message, so one text message will be 160 character limit, then it will create another text message with another limit of 160 characters so you will be sending two text messages. Hope this helps
Huh? I'm on the Tilt 2 stock ROM also, and I don't see this issue at all. Which one of the multiple (sigh...) texting methods are you using? The one where you click the new message icon within the Messages tab? Or the one within the threaded texting feature? Or the one where you click New Message within the "all messages" screen?
That's kinda ridiculous now that I think about it...
Thread closed - Duplicate thread exists in Rhodium themes, applications and software forum.
In future read and abide by forum rules. No duplication of posts/threads. Failure to abide by forum rules will result in a temp ban heading your way!
The "Find my Phone" and other similar tools on windowsphone.live.com use standard SMS messages.
The messages are in the format
SkY#AAAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==
with a sender ID of "Microsoft"
I have successfully sent a message which was *hidden* on my WP7 - spoofing "Microsoft" may be enough to do this.
The string itself looks a lot like Base64 encoding, but is not.
Has anyone else done anything with these messages? What did you find?
"The string itself looks a lot like Base64 encoding, but is not"
- From my research that is the "device-id" (one part of the "==")
I have not received any of this type as an sms.
Strange that it showed up on yours :S
When i'am using the swiftkey keyboard, (or swype for that matter), i do not get word predicitons in some text fields such as :-
1) Stock browser Search
2) Google Play Search Box,
And many other places.
IT is quite annoying because, the main idea of these apps is to provide meaningful predictions.. Is there anyway to fix this?
But what to Fix?
shubhamsizzles said:
When i'am using the swiftkey keyboard, (or swype for that matter), i do not get word predicitons in some text fields such as :-
1) Stock browser Search
2) Google Play Search Box,
And many other places.
IT is quite annoying because, the main idea of these apps is to provide meaningful predictions.. Is there anyway to fix this?
Click to expand...
Click to collapse
No. There's nothing wrong to get fixed!
Even with the HTC Sense Input, we don't get word suggestions in Stock or any other browser's address bar and play Store Search box as there we don't need any grammer.
The phone knows that the name of the website (in case of browser's address box) and the name of an app (in case of play store's search box) may not be there feeded in the dictionary. The names of the websites or apps aren't words that are there in a dictionary. But when you type a message, you're typing a language which needs grammar and these words used are there in the dictionary so the phone will automatically provide you word suggestions.
Paresh Kalinani said:
No. There's nothing wrong to get fixed!
Even with the HTC Sense Input, we don't get word suggestions in Stock or any other browser's address bar and play Store Search box as there we don't need any grammer.
The phone knows that the name of the website (in case of browser's address box) and the name of an app (in case of play store's search box) may not be there feeded in the dictionary. The names of the websites or apps aren't words that are there in a dictionary. But when you type a message, you're typing a language which needs grammar and these words used are there in the dictionary so the phone will automatically provide you word suggestions.
Click to expand...
Click to collapse
Dude, I agree in case of google play you probably don't require predictions..
But, wouldnt it be helpful if you had predictions if if u were searching for something loooong in the browser..
And as i said , they were only two examples... the predicions also don't work in text fields of 3rd party apps.
with swype u can save a word in the custom dictionary and, just "swype" to get those words/email id's/usernames/numbers passwords even in ANY text
So its was quite annoying when i switched over to swiftkey.
I heard the bug is fixed in android 4.0.4? Is there a workaround?
Hey. This is by far the noob-iest question I have made. How the hell do I enable 160 characters in SMS instead of 60?
Sent from my Galaxy Nexus using xda premium
It is 160 character by default/SMS
Think you can type up to 3 SMS before it turns to MMS .
Hope that helps
jelly buttery smoothness
It is 160 ascii characters. If you are typing in other Unicode character sets you will not get that. For instance when I type message in Chinese I only get about half as many characters per message.
I write in Greek and it writes 65 chars before 2nd message kicks in. That really sucks. I can write a long message but I will be charged as sending 65 per each
Sent from my Galaxy Nexus using xda premium