All of a sudden i can not get the number 1 to type or the @ to type out. For some reason its like its frozen on the left side. The 2 types out and the # sign after the @. Has anyone else had this problem? Other than that all numbers letters symbols are fine and caps. Plz need help. Also tried different keyboard too.
Swype took care of my problem all good.
You mean on the physical keyboard?
I had problems with mine, it started getting "bubbly" and one of the keys got stuck "the @ key". I had to press it hard so it would unstuck.
Sent from my Milestone using XDA Premium App
If you are using CM7, have you checked whether you are using the correct keyboard layout? Settings->CyanogenMod settings->Input->Keyboard layout ?
Related
Hey guys,
I've running the latest CM7 on my Milestone and noticed some issues with the physical keyboard.
Well, I've installed Korean ime(dioime.apk) and put all needed libraries and even swapped text_code_map, all the keychars and keylayouts(which are stocks from a Korean rom).
It seemed working fine and noticed caps and alt do not work properly on the keyboard.
Once I use the caps key, it stucks with capital letters even tho the bar shows the triangle.
For the alt key, it sometimes changes en to kr and sometimes just doesn't work.
So, I thought sth wrong with the latinime and swapped to the stocks but still no luck.
Can anyone help me with this pls???
I've attached the files. pls have a look.
bump bump!!
Can someone give me any idea??
bump bump!!
I installed the RenovateRom, which is really great. http://forum.xda-developers.com/showthread.php?t=2202696
But since they Removed the "select input method" notification. I dont know how to change the keyboard, i wanna use the original jellybean keyboard.
can anyone help me how to change the keyboard ?
thanks in advance.
What about if you just go into settings, language and input or something like that, then keyboard. Select keyboard and I would think you would be good.
On most keyboards, if you hold down on one of the buttons such as "spacebar" or "123" or one of ones on the bottom row, it will give you pop up a box to select your keyboard. On the stock JB keyboard, you hold the space bar to get the pop up.
hi,
i tried both. no way to change the keyboard on HTC ONE with your hints.
very strange.
someone any other idea ?
You can download something called "input select method" from the play store. I love the renovate roms but can never understand why they remove the input method selector.
Anyhow, hope that helps.
Sent from my HTC One using xda app-developers app
hunwar said:
hi,
i tried both. no way to change the keyboard on HTC ONE with your hints.
very strange.
someone any other idea ?
Click to expand...
Click to collapse
Sorry to hear that. I have a Nexus 4 (my first Android) and I thought they are all the same.
same problem here.
for others who need a fast solution: play.google.com/store/apps/details?id=com.maddingtonspice.simtest
I have tried other keyboards and the stock keyboard it seems it varies on rom i use. Every word i type in text shows up underlined in red like its a typo but its obviously not seeing as i know how to spell words like fun and goodbye etc. Any advice from anyone how to fix this ?
Just wondering.... Can you check if your phone's defaults language "English"
Sent from my Nexus 7 using Tapatalk 4
Has anyone noticed that since HTC removed and replaced the phone pad and XT9 when you go to choose one single letter when typing then go to choose another single letter, it automatically adds a space in between the letters now?
Example: e y
I can't find a setting for auto spacing anywhere either. Do you think it's an error in the way they took it out then replaced it? I've never had this issue before the update.
I'm including an annotated screenshot of this page to help explain a little better what I mean.
Sent from my HTC One using xda app-developers app
Hey man, I am having the exact same issue as you... It's fine for people who use QWERTY keyboard as you select each individual letter yourself... Where as when you use the phone keypad you have to select them with the prediction, of course it then thinks you've entered a word and adds the space... If anyone knows a fix for this that'd be great!! I am even willing to try and edit the HTC_IME if someone can tell me where this setting might be stored.
I am also running into HTCs famous dictionary losing words like "am" "go" "in" etc... Yes it took me a hell of a long time to type this message on my phone...
Ever since I got my One, through both major updates, I've had a problem with capitalization in Swype. Namely, when I'm typing a word out that I know isn't in the dictionary, I will tap shift for a capital letter, the shift key highlights signifying that I am, in fact, in shift mode, and start typing only to find that the first letter comes out lower case anyway. I then delete what I've typed and start over again, the second time working. It happens probably 8 to 9 times out of every 10 and I'm pretty damn sick of it. Anyone else have this problem? Know a cause? Have a solution? Please let me know!
Sent from my HTCONE using Tapatalk
I stopped using Swype
Project D said:
Ever since I got my One, through both major updates, I've had a problem with capitalization in Swype. Namely, when I'm typing a word out that I know isn't in the dictionary, I will tap shift for a capital letter, the shift key highlights signifying that I am, in fact, in shift mode, and start typing only to find that the first letter comes out lower case anyway. I then delete what I've typed and start over again, the second time working. It happens probably 8 to 9 times out of every 10 and I'm pretty damn sick of it. Anyone else have this problem? Know a cause? Have a solution? Please let me know!
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I had the same problem with Swype, along with a few others. It got so annoying for me that I just quit using Swype and went to the Google keyboard with gesture typing. I'm very close now to giving up on gesture typing altogether.
I'm also interested if someone has a solution to the Swype problem.