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.
Related
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.
Searched, but found no anwer to this question so.....
Does anybody know how to edit the word substitution list for SMS texting on the TMO-US branded TP2? I had a cooked Touch Flo Rom on my Wing that handled it beautifully, but the stock substitution on the TP2 only seems to automatically capitalize the first word and is missing a few things that I really got used to:
* "i" by itself got capitalized (even in the middle of a sentence)
* "dont" got its apostrophe along with "didnt", "wouldnt", etc.
* I can't swear to it, but I even think it managed some other contractions like "You've" and "You'll"
TIA
its because word completion doesn't work. search for word completion & you'll find countless threads on how to enable it again. Warning though, it will disable the functionality of FN+SYM to get the symbol menu
All the threads I found are talking about a T9 word completion, which I don't really care to use. I'm looking for an auto-correct functiont that automatically replaces "misspelled" words like "dont" with the correct spelling ("don't") after you hit the space bar. I don't like word completion, per se. I just use the auto-correct as a short cut so I don't have to "Alt-K" to get an apostrophe. Has anybody worked on this, or have I missed the thread that discusses it by not searching the right terms?
[Edit]
This is for use with the hardware keyboard, BTW
[\Edit]
If you set up the word completion like it says & then use Advanced Config to set the number of suggestions to 0 then all that will work is the auto correction
@xnifex,
Thanks, I had decided to take the plunge and do the reg hack like it said, and discovered exactly what you said I'd find. Thanks for being patient with my stubbornosity. Still no fix for the [Alt + ,] for the symbols, then? Granted, it's pretty well worth the trade-off for me, since I rarely go into the symbols menu, but I hate knowing that something's "broken", even if I don't use it much.
People are always in a hurry to get somewhere. A common issue is to inform someone waiting for us that we are, let’s say, a bit late and maybe reassure him that we will be there in some time. It would be great if we could send a message to that someone telling him our approximate location and an estimate time to reach the destination ( maybe along with some excuses )
Sorry I'M Late was developed to achieve this task. This application allows a user to get his aproximate location and then send it to someone else though an SMS. While the idea itself is not new, my objective was in the first instance to create a User Interface as easy and friendly i could, secondly I wanted to exploit CellID localization instead of GPS. The last thing i wanted to do was to provide a more human readable message to be sent: most of the application i've tested, use GPS positioning to get a precise localization but then they send Latitude and Longitude coordinates or Google Maps links and usually when i want to tell someone where i am, i use street names instead of coordinates
Uploaded with ImageShack.us
[17/07/2010] Today I've released the new version of Sorry I'M Late with some new additions and fixes (thanks for all your hints and suggestions). Following is the updated feature list, along with the changelog (for more technical stuff).
[18/07/2010] Released 1.5.1 version. I forgot to add compression to the network calls o) so this is basically just a patch release
Some features:
Doesn't require GPS antenna
Finger friendly UI thanks to SenseSDK from Steady Software
Call history access to guess the most probable recipients
Native SMS application used to send message to allow last minute changes
Currently localized in 12 different languages (English, Italian, Czech, Polish, German, French, Spanish, Portoguese, Russian, Dutch, Swedish and Japanese) *new v 1.5*
Support for custom messages via template *new v 1.5*
Reduced network bandwidth usage *new v 1.5.1*
Requirements:
.NET Compact Framework 3.5 required
data connection is used to retrieve street names so be aware of this before you start the application
Changelog:
1.5.1
- added compression support on network calls to reduce bandwidth usage
1.5
- added internationalization resources (12 languages support)
- improved position approximation, now integrated with landmarks from Wikipedia
- moved localization algorithms to a remote server to reduce network calls and CPU load
- added icons
- new option menu
- added option to append a link pointing to the location on Google Maps
- added option to create a template message to be used instead of default one
- fixed single line help on main screen (at least i hope so )
1.0
- first public release
Notes:
Currently the remote server is located on a free host. Usually it's fast an reliable but network problems can occour
In order to display the new application icon on the Start Menu, a soft reset may be required
As you may have noticed, there is a new "Twitter" option available but it's disabled. I'm thinking whether include it or not in a future release.
Last but not least, thanks to:
- Jack_Surfer (for polish translation)
- claus1953 (for spanish translation)
- dr.cryo (for czech translation)
- mike2nl (for dutch translation)
- Cunione (for french translation)
- Mad Marc (for german translation)
- Celso Marques (for portoguese translation)
- PlackSlayer (for japanese translation)
- scanie (for swedish translation)
- serfer222 (for russian translation)
- the0ne (for video review on YouTube)
- Cunione (for icons)
- billyJ (for icons)
- bernabap (for icons)
- tunnuz (for icons)
Lol, I saw the tittle and thought this was an (AI) app that generates intelligent excuses given some contextual information
Anyway, great app.
Installed, but can't find icon. I also installed to SD card? Thanks
EDIT: ok I'm running it from the sorryimlate.exe file in file browser. Works, don't understand the contact selection just yet. It seems like from call history. Pretty neat so far. Thanks.
noellenchris said:
Installed, but can't find icon. I also installed to SD card? Thanks
Click to expand...
Click to collapse
Sorry for the missing shortcut, my mistake . I've updated the cab so now it creates the proper start menu shortcut.
noellenchris said:
EDIT: ok I'm running it from the sorryimlate.exe file in file browser. Works, don't understand the contact selection just yet. It seems like from call history. Pretty neat so far. Thanks.
Click to expand...
Click to collapse
You're right! Actually the contact list is populated with numbers fetched from the call history. it is a very simple algorithm that group the caller IDs and count them, then the list is ordered from the most called to the less. the idea is that if you need to send someone a message to say you're late, it is very likely that it is a person you call or receive calls from. you're still able to pick a contact from the address book however, selecting the first option and then searching for it just before sending the actual SMS.
As ai said, for now it is a very simple algorithm, maybe in the next release i'll try to refine it a bit, for example considering also the date of the calls.
Cool little app ;-)
It would bee even better if it was possible to choose more then one contact from the list.
And there is missing a dot at the end of the message.
Thanks for the suggestion i think that this will definitely come with the next release.
Maybe set an own default message? So I can set in my own language.
first of all.. this is a wonderful idea.. and i'm glad to see the sense interface once again.. but for some reason whenever i run the application it disconnects me from the network and starts looking up a signal. after it finds one and i click "find it", it disconnects me from the network once more...
when i try choosing from the contact list the app crashes..
hmm
jan-willem3 said:
Maybe set an own default message? So I can set in my own language.
Click to expand...
Click to collapse
yes, you can expect that on the next release
oh and by the way, for now there are only English and Italian as available languages, but if someone have a little time to translate the strings in other lenguages i will surely appreciate that.
nir36 said:
first of all.. this is a wonderful idea.. and i'm glad to see the sense interface once again.. but for some reason whenever i run the application it disconnects me from the network and starts looking up a signal. after it finds one and i click "find it", it disconnects me from the network once more...
when i try choosing from the contact list the app crashes..
hmm
Click to expand...
Click to collapse
the fact it disconnect is actually a desired behavior. When the application boots up it forces a network deregistration and then reconnects in the hope to associate with another GSM tower and thus have two distinct point used to approximate the position instead of just one.
speaking about the crash, can you tell me please the exact steps you perform before the problem shows ?
Really great app, works flawlessly on my TouchPro. Thanks !!
I would really like to see this on WP7 as well
how to do translation in txt file?
i've attached to the first post a txt file containing some xml tags. you just need to translate the strings inside <Value></Value> tags.
Thanks a lot
It sounds very interesting, because a all the time stop and go traffic here in our country, this app can help out .. possible.
Polish translation
Hi,
here is my Polish translation of the strings.txt for this interresting app
View attachment strings.txt
Attached spanish translation text.
Thanks to claus1953 and Jack_Surfer for translations, i will include them in the next release (due to next week, so stay tuned )
Czech translation
Hi Stefano.
Very useful app! Thanks for it.
I'm sending Czech translation. Please send me message in case of further releases and new strings for translating.
Regards
Pavel
And here the 1st ducth translation. Possible some changings to do, because i have made the translation before i have used the app.
Ciao Ste !
Nice app and very useful !
Here my french translation.
I had a few bugs :
- In the help, the description box, is only on 1 line. Not multi-lines like you show it in the screenshot.
- Is it possible to add a "." after the location ? (at the end of the sentence)
Ex. : "Hi! I'm around xda forum. I'll be there in 15 minutes.
- Can you add the localisation name (the city name) after the address ?
- Where is located the language file ? Is it possible to make a function that will check a language folder insted of including it in a .cab file ? (should be easier for all translaters)
I tell you back that's a nice app.
Bravo, bel lavoro. Quand'è che fai la version 1.5 ???
thx
hey!thx a lot! it is a great idear!
what wouldbe great: a map link in the sms, so the receiver have only to click on the link zo see my position on Google maps.
possibility to send a email
thx one more time, its great!
I saw too many threads, but I dont found any solution.
When I send special characters like, "á,à,é,i,ã,ó,ç", the other phone doesnt see it, or in some cases show garbage. I cant understand it. If someone could help me, I appreciate it.
See the image - i40.tinypic.com/jgqps9.png (I cant put link because of post's limit.)
I had a similar issue both with special characters and other alphabets (Cyrillic one)... In my case it wasn't a problem with my phone but with both service provider (that was strangely resolved very fast) and the recipients phone (which didn't support those characters).
So, have you tried sending this type of messages to other phones and was the result the same?
I send to mate of mine.
My phone - "simão", his phone appears "imo".
Thank you for reply.
I would try to send such a message to some other (models of) phones just to be sure whether this character limitation is imposed by your mobile service provider (which is less probable) or is plain inability of that particular phone you are messaging to encode such special characters...
Impossible to be limitation of my mobile. I have 100% certainty that be ROM's problem. I change it on sunday.
ROM - Runnymede AIO V3.0.5
Last ROM - leedroid. I hadn't any problem until sunday.
I tested swype keyboard, HTC_IME mod, LatinIME. No solution.
Very well then, that clears it up... It could be ROM bound problem... Hopefully you'll solve it by reflashing to another ROM since it appears that your current ROM is faulty in terms of character encoding, it has nothing to do with keyboards...
Although i had run some of the previous versions of the Runnymede AIO and had no problems with texting characters such as č, ć, ž, š etc. Sorry that I can't help you...
While didn't have any solution, I disable special characters (Messages-Settings-SMS-SMS characters-off)
Thank you for all your replys.
Best regards
I am pretty sure I haven't lost it and my memory is tricking me, but before some update or another if you were entering text in almost any app (SMS most notably) and got to the end of the piece of text and saw that word correction had put in a word you didn't want you could click on the word and the word prediction list would appear again and a simple click to change to another word???
I am not 100% sure when this functionality disappeared, must be at least 6 months ago. I thought it was just some glitch and was expecting it to return when resetting. Just did a reset (Android 5.0.1) and still nothing happens.
Drives me crazy, have to place the cursor after the word, delete it and re-type. It was so sweet before.
Please let me know if I am wrong - and if not is there any way to get this functionality back.
julesgilson said:
I am pretty sure I haven't lost it and my memory is tricking me, but before some update or another if you were entering text in almost any app (SMS most notably) and got to the end of the piece of text and saw that word correction had put in a word you didn't want you could click on the word and the word prediction list would appear again and a simple click to change to another word???
I am not 100% sure when this functionality disappeared, must be at least 6 months ago. I thought it was just some glitch and was expecting it to return when resetting. Just did a reset (Android 5.0.1) and still nothing happens.
Drives me crazy, have to place the cursor after the word, delete it and re-type. It was so sweet before.
Please let me know if I am wrong - and if not is there any way to get this functionality back.
Click to expand...
Click to collapse
Try this! open messages, new message, to the left of the space bar hold comma, go to advanced and tick word prediction and next word prediction!
NornIron75 said:
Try this! open messages, new message, to the left of the space bar hold comma, go to advanced and tick word prediction and next word prediction!
Click to expand...
Click to collapse
Appreciate your help. I think I have tried turning on and off every setting I can find related to word prediction/correction. nothing seems to help.
So do you have a M8 with 5.0.1 that does as I describe? I would really like to know if it is just my phone. Fixing it if it is must then be possible. If I imagined it, well then I can forget about it and seek other help
julesgilson said:
I am pretty sure I haven't lost it and my memory is tricking me, but before some update or another if you were entering text in almost any app (SMS most notably) and got to the end of the piece of text and saw that word correction had put in a word you didn't want you could click on the word and the word prediction list would appear again and a simple click to change to another word???
I am not 100% sure when this functionality disappeared, must be at least 6 months ago. I thought it was just some glitch and was expecting it to return when resetting. Just did a reset (Android 5.0.1) and still nothing happens.
Drives me crazy, have to place the cursor after the word, delete it and re-type. It was so sweet before.
Please let me know if I am wrong - and if not is there any way to get this functionality back.
Click to expand...
Click to collapse
Hi, julesgilson...
My M8 is currently running Android 5.0.1/Sense 6, and although I don't use the stock HTC Sense keyboard, preferring instead to use Fleksy, I have noticed this annoying peculiarity with the Sense keyboard myself.
Here are some further observations...
With the stock Sense keyboard, a word is only correctable (with selectable alternatives) only as long as the word being typed remains HIGHLIGHTED. As soon as you hit the space bar, with the intention to type the next word, the HIGHLIGHT is gone, and the original word can no longer be corrected or alternatives suggested.
The HIGHLIGHT then shifts to the next word being typed, and with possible corrections and alternative suggestions for this new word.
Tracking back over a given paragraph (or even to just the last word) and manually highlighting a previously typed word, doesn't, as you might expect, provide any alternatives or spelling corrections.
-----
This behaviour is entirely at odds with 3rd party keyboards like SwiftKey, Swype and even Googles own keyboard, where ANY word in a given paragraph can be selected and corrections/alternatives suggested.
The stock Sense 6 keyboard under Lollipop 5.0.1 seems incapable of retrospectively correcting previously typed words!!!
I'm no programmer, but it seems to me, that the stock Sense keyboard is only capable of correcting a word while it remains in the 'buffer'... that is to say, while it's being typed and so long as it's highlighted.
The instant you move on to the next word (with the space bar), the word is 'forgotten' by the keyboard and can no longer be corrected or alternatives suggested.
-----
This sort of thing is difficult to describe, so I suggest you download Googles keyboard from PlayStore... type some random passage in Google Keep (or wherever) and then using Googles keyboard, randomly select a word in that passage and you will see that Googles keyboard correctly identifies the selected word, and suggests alternatives.
And then try the same experiment with the stock Sense keyboard...
Rgrds,
Ged.
Yes! That's exactly it - like you say pretty difficult to describe concisely. The strange thing is that it used to do it, possibly before Lollipop.
Now that someone else has confirmed it seems a general issue with the HTC keyboard I will give up trying to fix it and look for another keyboard.
Greatly appreciated.