Don't know why is this limitation for 1 SMS.
Is there any fix for this ?
Using Trin with WM6
Lol dude, it's standard for every phone/phone provider..
http://en.wikipedia.org/wiki/Short_message_service
"SMS was originally defined as part of the GSM series of standards in 1985[1] as a means of sending messages of up to 160 characters, to and from GSM mobile handsets"
WOW
Is the Trinity your first mobile phone???
Lucky you!!!!
Heh, well some differences in mobile operaters exists and some binary related stuff ( encoding etc ...) & mobile operator SMS prefixes ( extra services ) change that.
Also there is a math difference in length of 2nd 3th ... SMS and any other multi SMS option ( info for next multi SMS etc ...).
And the answer about no of phones : I had cca 20 phones till now and trin is not the only phone 4 me now
So differnces exists and the standard is not fixed (140 b/160 t).
I'm speechless...
This one should be on the Top 10 most funny threads of year 2007.
Well done!
Don't know why it is so funny ?
It is a question after all, isn't it or I should refraze my question ?
don't rephrase anything, just laugh with us.....
lolz
well apparently a short msg is 160 chars
as they charge you pr. msg they have to some sort of limit to make money
i think we should stage a demonstration... like a boycott or something..
An SMS message is 140 bytes. Most of us use the 7-bit GSM alphabet, which means 160 characters. This can be shorter if you use another alphabet, such as 8-bit which would mean 140 characters. SMS can be concatenated, ie long messages are sent (and billed) as several SMS which can be appended in the receiving phone (will be perceived as one SMS by the recipient). In this case, there is a header on each message, which takes up some space. This means 153 or 151 user characters per part of the message, depending on which header type is used (8-bit or 16-bit sequence number), if a single SMS is 160 characters.
Related
Hello,
I'm developing an application for windows mobile 6.5. Im writing the code in c#.net and want to send sms due to my app.
I checked out the POOM and sms sending worked fine.
Code:
SmsMessage msg = new SmsMessage();
msg.To.Add(receiver);
msg.Body = messageText;
msg.Send();
But there's one problem. I want that the messages will be saved/copied to the "send messages" folder, after my program has sent them.
How can I realize that. Is it possible with the POOM, oder should I work with MAPI and generate a converted copy of the msg-Object in the "send messages"-folder?
greets,
raffi
p.s.: Please excuse my english. I'm a german pupil and I knwo that my english isn't the best. So if you got in trouble, while reading my post, ask me and I'll try to explain the problematic part in another way...
I dont know how to implement the code, but I believe that it involves the SmsAccount class and the Folder class. I have seen examples online showing something like :
Code:
SmsAccount x;
Folder outbox;
outbox = x.outbox;
or something of the likes, but I cannot produce that code when making my own program without getting errors about undefined properties, etc. THe MSDN site is pretty useless on this topic too. It seems as tho the Microsoft.WindowsMobile class and its subclasses are under-documented...
Hi,
there is an issue on Sense's SMS app (and actually in Android SMS app) and non-GSM 7-bit characters. This ticket on Android's Google Code explains it well : code.google.com/p/android/issues/detail?id=6522 (seems like that has a new user i can't share "real" links).
It's kinda annoying when you're not an english user (a simple accent use 60 chars).
Seems like a simple option for turning off unicode should work...
My question : is it possible for you guys to fix this in roms ? Maybe easier by updating stock sms app ? Not possible at all ?
Thx in advance for your replies !
I fully agree! An option to turn off special characters (some accents work without using 60 chars, like é à è). would be great!
This is a bug in Android and judging by its age, I won't hold my breath to a solution. Even more if it's solved at framework level. This way, we'll be waiting long time for it to be release in an official HTC update.
For the time being, I'm using HTC IME mod with character replacement in SMS. Settings -> Language & Keyboard -> HTC_IME mod -> Text Input (mods by jonas)...
This way it is still possible to have text prediction and, in SMS, the forbidden characters are replaced.
It's NOT a fix. Just a very good workaround. At least when using Compact QWERTY.
Resurrecting this thread as it is annoying.
That and the fact that on my old Nokia phones (N82 at least, my previous one, for sure), I had an option to prevent this.
Character encoding — To use character conversion to another encoding system when available, select Reduced support.
Click to expand...
Click to collapse
This was in Messaging>Options >Settings > Text message.
When "Reduced support" was selected, even with special characters, the char count wouldn't go from 160 to 70 when using those characters. Isn't there such an option in Android ?
As non-english languages often use those chars (â, ê...) using 2 sms when I could use one sucks.
The workaround above is OK (not really, need to use qwerty ), but I like to use the correct spelling of words.
Thanks if anyone can help with this issue.
Possible EVO Text Bug
This bug will only affect those who write texts in languages other than English.
You are allowed 160 characters in a text message. However, if you type a character using an accent, like this: ñ, you will be limited to 70 characters!!!
This happens with 2.1 as well as 2.2. It happens in the stock text program, as well as SMS Pop Up. I haven't tried any others.
Say you start a new text. It will show you have "X" amount of characters remaining out of 160, like: 94/160.
Now type an accented character, say é.
You will now have 3/70. I have confirmed this with someone on Android Forums.
This is an issue because Sprint charges 20 cents per International text. Therefore, I have to send TWO texts to convey what I should be able to with one text.
Received a reply over on Android Forums from user Gary Coleman. Haven't checked the accuracy, but fwiw:
"Depends on the character. GSM and CDMA use different character encoding for SMS (GSM 03.38 v. CDMA 3GPP2 C.R1001). Both are limited in the allowable characters for SMS to provide for the 160 character message length. To get the full 160 character message all characters would have to fall under 8-bit length (UTF-8) - (actually it's a 7-bit set for 160 length, 8-bit for 140 and 16-bit for 70, but I'm just going to say 8 & 16 for this). Certain special characters required 16-bit (UTF-16). If a single character in the message is UTF-16, the entire message is treated as UTF-16 and the allowable message length drops to 70. So certain characters you are using are UTF-16. Some characters may be treated as UTF-8 in GSM and UTF-16 in CDMA. It is based on GSM and CDMA SMS standards and it not something special to the Evo.
So the moral of the story is....don't use funny letters."
I know this has been discussed before as an issue with the 3G Slide but I'm wondering if anyone wants to try to get magenta to do something about it. With how much they advertise this phone and used it in everything that had to do with them why did they either not set a user agent for mms messaging, resulting in the server to default to the lowest setting or, why did they set it so low for our phone? My Blackberry 8900 sent pics well over 1MB just fine with no resizing (with EDGE at that) as many other phones do.
I've had enough of the 1KB - 25KB mms messages, sending and receiving. I know a few apps attempt to fix this but even with CM6 having that option built in - it still does it, as I'm sure many of you notice for large pics. So maybe we should do the same thing that was done with the source code and bluetooth code issue. Anyone up for it?
On a secondary note: In the mms.apk the UA is listed as: http://www.htcmms.com.tw/Android/common/mytouch3g/ua-profile.xml which has a max height/width of 480x640 and max size of 307200 (300K). If I replaced that with say: http://www.htcmms.com.tw/gen/HTC_HD2_T8585-1.0.xml with a h/w of 1600x1600 and size of 600K, would it work? Yes I know it's windows but that shouldn't effect the mms aspect.
mikechannon - if you will, please keep this open for a while and delete it at your discretion.
I thought HTC would fix this issue in Sense 4.0...but they dont seem to have done it still...Anyone have any workaround?
Here's the problem -
If I have two contacts with similar numbers,
Say Mr. A with a number 1234567890
and Mr. B with a number 2234567890
HTC Sense is not able to distinguish between the two. It offers to link the two contacts and even though I dismiss this request, thereafter if I send a text or call Mr. A, it will show Mr. B or vice versa.
Please help!!!
What about if you set one with your country code e.g. +44112345678 and the other without e.g. 2212345678. It might be enough to confuse Sense that they are different.
Sent from my HTC One X using Tapatalk 2
That won't help either... It's designed to match just the last few digits specifically to ignore the country code or IDD it calling cards prefix.
Even old school Nokias used to do this.
It's annoying when you get that one in a million match, especially if they are commonly used.
You bet...and in my case it's a husband and wife who have similar numbers, so half the time i message the husband but it shows the wife's name when its been sent...i have stopped sending cheeky messages to this friend of mine lest they get delivered to his wife by mistake!!!
By default the One X will mach tge last 7 digits. If ur stock, i dont think u can do anything. But if ur rooted, u can increase itto 8 or 9 by changing the following in build.prop:
ro.phone.min_match.HTC__J15=7
Click to expand...
Click to collapse
Where HTC__J15 is the CID number (yours might be different) & 7 is the minimum number of maching digits (change it 8 or 9 as you wish).