Hey guys,
ist there any way to stop the keyboard from popping up automatically when an input is necessary? It´s pretty annoying.
no way to do so?
Indeed it is.
Try NullKB, it's a Keyboard that is a pixel, and effectively eliminates the Kb. Only drawback is, if you DO need it you have to change it back, hope it helps!
Related
Hey guys, recently joined this forum since i got my first wm device, the SE X1
I searched the forum trying to find a way to stop the virtual keyboard from popping upp as soon as I select an input box in the opera web browser. So I was hoping you guys could help me.
oh btw, atm - I suck on wm, but Im very keen on learning so if you have any newbie tips for me that would be great too.
thanks,
Agaas
Agaas said:
Hey guys, recently joined this forum since i got my first wm device, the SE X1
I searched the forum trying to find a way to stop the virtual keyboard from popping upp as soon as I select an input box in the opera web browser. So I was hoping you guys could help me.
oh btw, atm - I suck on wm, but Im very keen on learning so if you have any newbie tips for me that would be great too.
thanks,
Agaas
Click to expand...
Click to collapse
Can't answer ur question, but am gonna ask another - if you don't mind... "does the on-screen keyboard come up when the hardware keyboard is opened too?"
AFAIK this is a persistent problem, but there is a null keyboard without any keys which wont get in your way when it pops up.
http://freewareppc.com/utilities/nullkeyboard.shtml
Surur
yes, thats the problem! it does so when its open. wouldnt mind if it did when closes
thanks for the link to the null keyboard, unfortunatly it didnt work. Ille see if I cant find another one
okey, I tried "Phm null keyboard", it worked but made the icon flick and looked strange so I removed it
Doesn't bother me just hit a button on the hardware keyboard and it dissapears
someone else who has a tip?
Same problem since years and generations of WM
I don't recognize it anymore. One tab on the hardware-keyboard and it is off again.
Pls. This can't be difficult to fix for a smart person.
The easiest fix currently known has already been stated.
Place the cursor into a text box, and allow the on-screen keyboard to pop up. Then slide the phone open and expose the hardware keyboard. Next hit the space key, and then slide the phone closed.
Problem solved until you bring the on-screen keyboard up again.
NotATreoFan said:
The easiest fix currently known has already been stated.
Place the cursor into a text box, and allow the on-screen keyboard to pop up. Then slide the phone open and expose the hardware keyboard. Next hit the space key, and then slide the phone closed.
Problem solved until you bring the on-screen keyboard up again.
Click to expand...
Click to collapse
Yes ofcourse but it would be nice to somehow disable it from popping up automaticly
I don't see the big problem about this issue. Does the keyboard stay up on the Xperia? I know on my device all I do is hit the text box and start typing on the hardware keyboard and the virtual disappears as soon as I hit the first key.
Kloc said:
I don't see the big problem about this issue. Does the keyboard stay up on the Xperia? I know on my device all I do is hit the text box and start typing on the hardware keyboard and the virtual disappears as soon as I hit the first key.
Click to expand...
Click to collapse
That's correct it does disappear on the X1.
The symbol key on the keyboard doesnt work in Opera... the on screen symbol menu wont come up
Im sure i saw a registry hack for this problem. does anuone have any more info#?
anyone know of a registry hack yet? This keyboard popping up is getting on my nerves now
here's a reg tweak
http://neato4u.wordpress.com/2009/07/22/disable-the-virtual-keyboard-on-windows-mobile/
it does bother me, but as soon as i press a key on the keyboard it goes away... i've come to live with it. i use skyfire most the time anyways
neato4u said:
here's a reg tweak
http://neato4u.wordpress.com/2009/07/22/disable-the-virtual-keyboard-on-windows-mobile/
Click to expand...
Click to collapse
I tried that and could get no virtual keyboard to come up even when I wanted one. Had to change the value back again.
The auto complete for the hardware keyboard (which I believe is modified).
Is quite annoying. I am on Cyanogen 7.6.2...
I tried turning it off through settings and no luck... It makes my typing much slower.
Is there a file to remove through terminal emulator or ADB?
Don't press the text field when the keyboard is open. A little trick I found out to stop it. If you disable it, you disable autocomplete on the VK.
I know that but that is plain annoying too
Kainous said:
I know that but that is plain annoying too
Click to expand...
Click to collapse
Can't really do anything about it...
alritewhadeva said:
Can't really do anything about it...
Click to expand...
Click to collapse
if you turn off the HTC keyboard, you can disable it properly i believe
Would be awesome if there was a way to disable autocomplete for the hardware keyboard without having to disable it for the VK. I understand the reason why there's not such an option, as I assume the HTC_IME is really only available (in the wild) on phones that have no physical keyboard, so no such distinction is necessary.
Is this something that could be hacked or modified? I don't suppose there's source available for the HTC_IME?
Would be nice if there was an option as I much rather hte HTC_IME, especially in protrait mode for the phone keypad and T9. Best way is to get used of using the trackball to move into the text field instead of touching it to avoid prompting the auto correct when using the hardware keyboard.
Maybe someone might work on a more internal solution when the time comes.
Go into
Settings > Locale and Text > Touch Input
Disable Prediction and Word Completion
That will fix it
nephron said:
Go into
Settings > Locale and Text > Touch Input
Disable Prediction and Word Completion
That will fix it
Click to expand...
Click to collapse
I think the problem is that this also disables VK's autocomplete.
This problem is the reason why I went with the Chinese IME. I do use the Chinese part, but not enough to be the deal breaker. The HTC_IME has better portrait mode VK, but the autocomplete-with-hard-keyboard kept me from using it.
On Cyanogen's todo list, it says something about stopping interference with HTC_IME and the physical keyboard. I think he might have been talking about the autocomplete thing, not sure though.
unclejimbo88 said:
On Cyanogen's todo list, it says something about stopping interference with HTC_IME and the physical keyboard. I think he might have been talking about the autocomplete thing, not sure though.
Click to expand...
Click to collapse
Yea i had seen and i hope its for that it annoys the crap out of me
Hey, I'm probably about to smell like noob here but; Is there any way to have the phone actually change input method when rotating? For example, when portrait have swype, but when rotating to landscape, have it automatically change to htc_ime keyboard? I've been searching google for a bit now, but came up empty handed. I understand this would probably lag the rotate a bit, but that doesn't bother me much.
That would be ideal... but no way to do it as of yet.
One can only hope, cross his fingers, or learn how to program I guess XD
rickyzone said:
Hey, I'm probably about to smell like noob here but; Is there any way to have the phone actually change input method when rotating? For example, when portrait have swype, but when rotating to landscape, have it automatically change to htc_ime keyboard? I've been searching google for a bit now, but came up empty handed. I understand this would probably lag the rotate a bit, but that doesn't bother me much.
Click to expand...
Click to collapse
There was a previous discussion about this possibility. The answer is no, it's not possible.
Are you saying that there's NO way to switch input methods through the Android API?
Pretty sure it's a security issue about not lettins apps change keyboards.
Well that sucks, but I guess they know best. I see the security issue, if an app allowed a change in keyboard, they could easily make a key logger app or something. I am a little sad about this though, but a work around would be a keyboard app that in itself switched methods when rotating... I don't know, it's a possibility.
I use the droid 3's physical keyboard almost exclusively. I also keep the keyboard set to stock multi-touch keyboard, and I have autocorrect turned on. But here's the thing.
I want it to only correct things like dont -> don't, i -> I, shouldnt -> shouldn't, etc. It does most of these, but it also corrects everything else, thinking that I'm using a glass keyboard and am thus prone to making many mistakes. But that's not the case. In fact, when I notice a typo, I usually prefer to correct it myself rather than trying to rely on autocorrect. I only want it to add in apostrophes and things of the like.
Anybody know of something to change this?
It's a thought, but you could use Smart Keyboard to auto-correct the physical keyboard and set it up the way you like with the dictionary. The prediction is really good once you break it in.
folks
my accuracy with both the build-in google keyboard and swype is not what it has been with other phones and I do have long fingers. Anybody else noticed that and found a solution with another keyboard type? Anybody moved to standard typing instead of gesture?
Thx
sam008 said:
folks
my accuracy with both the build-in google keyboard and swype is not what it has been with other phones and I do have long fingers. Anybody else noticed that and found a solution with another keyboard type? Anybody moved to standard typing instead of gesture?
Thx
Click to expand...
Click to collapse
I find myself doing a mix of both... and for me it's a toss-up between SwiftKey and the stock Google keyboard, the main difference being available themes, really.
I have noticed a difference in accuracy as well, but I think it's because of the size of the device. It's probably just going to take some getting used to. Try SwiftKey, you can reduce or increase the size of the keyboard.
I have this issue as well.. With small words I'm fine but longer words .. Terrible!