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
Related
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.
Hello everyone,
I just got my HTC Desire, and I've been looking around at all of the cool things I can do with it. Unfortunately, I'm not the most technically savvy when it comes to these kinds of things.
I understand that if I truly want to unlock the power of my phone, I need to root it. I'm not exactly sure how to do that. I found a guide on this website that explains how, of course, but I'm not sure if my phone is a candidate for such an operation.
For instance, to get my build number I need to go to the 'About phone' section and find the RC number. However, when I look at my build number on my phone, I don't see 'RC' anywhere.
I just got the phone, so I assume everything on it is as up to factory date as possible...
Firmware version 2.1 update 1
Kernel version 2.6.29
Build number 1.18
Software number 1.18
Any information at all would be greatly appreciated. Thank you. I'm using the guide located here...
[edit]I tried to post the link, but as a new user I am unable to...[/edit]
Also, I know this is a silly question, but how do I make the keyboard appear when typing? I did it once, and am not sure how. I would, of course, read the manual for such a trivial thing, but I live in Japan, and only have a second grader's kanji reading ability. Thanks.
First of all good luck with the new phone
For the root part, the phone is quite good by itself, and after you recieve the official update to froyo, most of the earlier reasons for rooting is eliminated.
If you want to root it, you should understand, that there is allways a risk of breaking it even though it is very small.
The things you could gain from rooting is access to some special apps like screenshot apps, and special backup programs, which can backup far more, than non root apps. The most interesting part though is the custom roms with custom themes, which is only available with root.
If you want to root, you should try using unrevoked, which makes it very easy. You should read more about it in the forum though, to see, if your phone i compatible with the current version.
Btw. the keyboard should appear when you touch a box with text input.
I see. Thank you for the useful information. When can I update to froyo? I've read a little bit about it here and there, but I don't really know much about it.
And when you say "custom ROMs with custome themes," what do you mean? What kind of ROMs? When/If I get Froyo, will I be able to use custom ROMs, or will that only be possible on a rooted phone?
And when I touch a box with text input, a keypad shows up... not a keyboard. Like I said, I got it to come up once, but I have NO idea how. I've tried to recreate the situation (by just randomly hitting buttons/parts of the screen), but I have yet to reproduce the keyboard. Like I said, by default, a keypad just shows up.
Thanks again!
@Keypad/board thing
Go to settings -> language & keyboard -> touch input
and check if your keyboard is set to QWERTZ or QWERTY depending on your location
Most of us have got the official update, but i don't know, if it is delayed in asia or something. Try searching for new updates:
settings ->about phone ->System software update -> check now
About custom roms, those are for root users only as i said before.
About the keyboard, i am not sure, if i get you right. When you touch the textbox, the keyboard app opens. If you mean you want full qwerty keyboard, it is changed in settings:
settings ->Language and keyboard ->Touch input ->keyboard types
Rooting and custom rom is much more than theme customization. It allows the phone to do exactly what u want it to be: install apps to SD (on ext3), move cache to SD, set cpu clock for longer battery life, hack the keyboard, etc.
Spend some time searching how to do it
from my Desire + XDA App
Thanks guys for the responses.
I tried to update, but it says that my phone is currently up to date, so maybe there is a delay in the Asian market. No big deal... I can wait.
And as far as the keyboard goes, yes, I'm saying that I can't figure out how to get the QWERTY keyboard to show up. All I can get is a keypad, like on your home telephone.
When I go to settings -> Language and keyboard I only have the ability to select the language (English or 日本語), or iWnn IME.
In the iWnn IME selection, there is no option anywhere to change to a QWERTY keyboard. I got it to come up once, though... so I know it's possible, at least.
I think I'm just going to go back to the store and ask the employees if they can help a bakana gaijin.
ありがとう
Mr. Slippery
ROMs affected for sure: iNsertCoin v2.0.0 and RCMixHD v3.5 (both A2SD)
Whenever I type in characters in HTC Dialer to search for a name (e.g. 846 for contacts named 'Tim') the first number gets ignored, resulting in search results starting with characters represented by the numbers '46', e.g. 'Ho...'.
Similarly, when I try to access the test screen via *#*#4636#*#*, the first character '*' gets ignored (it even disappears after putting in the first '#').
If I put in something, then remove it with backspace and start over, it does work.
Don't think it's relevant, but Baseband version is 32.49.00.32U_5.11.05.27.
What is happening here? Tried setting different locale in settings, different keyboards, no change. Thanks in advance.
Ok second post now. Maybe your phone is a little nakered, rom broke a little. It seems your just getting software errors which happen when you flash custom roms.
Posted this here in Q&A after iNsertCoin developer suggested me to do so. He heard of this problem before, but had no solution. Hopefully other ppl have found one, but an extensive search both here and on other forums did not give any result.
Solved
After (quite!) some more research, I've found a similar problem described in the topics below. The presented fix there also solved my problem (see quote):
With great help of some participants of xda forum a workaround for this issue has been found: just remove the dialer shortcut from the dock (set it to "blank") and then add it back in (a shortcut to "Phone" app). This will fix the problem.
Apparently, people who are not experiencing the issue are the people who already recreated their dialer shortcut while customizing the dock. Meanwhile, people who keep the initial dock (or, more precisely, the initial dialer shortcut) all experience this problem. The problem is not limited to Plus version - a plain LaucherPro has it as well.
It looks like LauncherPro, as shipped, uses some unorthodox way to launch the dialer (I wonder why), which is what's causing the latter to act up. Recreating it as an ordinary app shortcut fixes the problem.
Click to expand...
Click to collapse
Sources:
http://www.launcherpro.com/forum/viewtopic.php?f=14&t=5884
http://forum.xda-developers.com/showpost.php?p=10490200&postcount=15
Hi
I have a mysterious problem with one of my applications. For some reason it doesn’t work properly with Samsung Galaxy Tab 2 10' (probably other devices too, this is the only one I’m sure of). Unfortunately I don’t have access to such device and sense I make no money on my application (it’s free) I was hoping that someone here could help me test this .
My application is used for education and is mostly designed to learn foreign languages. One way to practice is to use flashcard that I have implemented in OpenGL. To get this working I render bitmaps with text that is shown on the cards.
One user has reported that this doesn’t work with Tab 2, after a while the text is no longer visible. If the application is paused and then restored it works again. The bitmaps are rendered in a thread and I think that is the problem (if no threads are used it seems to work better). All devices I’m using for testing works fine so I’m really puzzled.
To test this please download and install:
http://www.pekspro.com/vokabelbeta/Vokabel1_13d.apk
Open the application, go to the files and open a file in the examples.
When the file is open, go the the tab Quiz and select Flashcard (3d).
Every second time bitmaps are generated in a thread, other times without any thread. On the top of screen there is some debug text. Please let me know what is says if cards are stopped working. Or even better send me a log from the application.
This feels like a weird request, but please please please help me solve this problem. It literally keeps me sleepless, xda is my only hope .
I can confirm that after a couple of questions, the flashcards go blank.
The debug text doesn't seem to change though
(Alive counter:nnn Duplicate request for: xxx)
It only seems to happen in landscape and it can be cured by rotating to portrait then back again...
In portrait mode the debug in this case is always just 'single thread'.
I would have a go on the emulator set to 10" landscape.
Thank you so very much . This is really interesting information for me.
I have done some testing with the emulator and some other devices but haven’t been to replicate the problem. I have reviewed my code and changed a couple of things that might cause some problems. Do you mind do a second test?
http://www.pekspro.com/vokabelbeta/Vokabel1_13e.apk
Either way I’m really thankful for this
Now the problem is solved. Thanks for all feedback
pekspro said:
Now the problem is solved. Thanks for all feedback
Click to expand...
Click to collapse
OK good to hear.. sorry I didn't notice your second message !
Hi, I'm looking for a screenshot of S4 mini keyboard layout with special characters (the one you get with one click from the standard qwerty keyboard). My phone is bricked and one of my passwords was a pattern made out of the special characters, I remember just the moves but not the characters ... Thanks!
PetrD said:
Hi, I'm looking for a screenshot of S4 mini keyboard layout with special characters (the one you get with one click from the standard qwerty keyboard). My phone is bricked and one of my passwords was a pattern made out of the special characters, I remember just the moves but not the characters ... Thanks!
Click to expand...
Click to collapse
which rom or update were you on? that would really make a difference. I have an extra i9195 i could restore to factory to help out
edit: with some google work ive found screenshots of the keyboard from some reviews, give these a shot:
https://i-cdn.phonearena.com/images...amsung-Galaxy-Note-3-Review-065-messaging.jpg
https://i-cdn.phonearena.com/images...amsung-Galaxy-Note-3-Review-064-messaging.jpg
http://www.technobuffalo.com/wp-content/uploads/2013/04/Samsung-Galaxy-S4-VS-HTC-One-Keyboard.jpg
YES! I have a similar problem and searching the forums or even the larger internet hasn't helped...
I don't suppose either of you have a spare sound of the i9195's battery cover being removed and replaced three times in quick succession, followed by a final delayed occurrence of the sound that takes precisely as long in delay as the first three together took to make respectively, only a moment before?
I've looked everywhere for that sound, it was once included with every i9195(lte) as part of the stock functionality, which made it very convenient to hear anytime it was required.
The device is practically uselessness without it, I usually always make backups but this time, stupidly, I've recorded over the cassette I stored the audio files on accidentally with silence. When I load"" it up TWRP refuses to recognise it completely.
I think, maybe, my recovery needs to be rolled back, it worked fine in an older version I had but, unfortunately, the name of that version is written on a text document that was also stored on the same tape...
What can I do to restore the original correct sequence again, will the old Samsung keyboard character-map really help with the restore, I have several great photos of one, too. Or is my phone bricked, along with the cassette?
Thanks a lot for the screenshot, one them matched my keyboard!
I tried this method originally as well but was discouraged when first one or two keyboards did not work.