I'm running the stock ROM from Alltel. Lately my TP has been sucking when it comes to typing on the keyboard. Random keys at random times will stick and the spacebar is the only way for it to stop typing. When I press the delete key once, it will just sit there until I hit the spacebar. Then it will delete the letter and type a space.
I have restarted the phone and the problem persists. I'm thinking the keyboard is going out on me. I don't think it is the OS because the display keyboard works fine.
Any thoughts?
I have the same issues with lag and sticky keys.
I am using stock HTC Touch Pro ROM.
Pressing the center D-Pad button stops the sticky key,
then I need to clean up the mess.
David
Anybody else with this issue?
I found a solution. Press the spacebar real hard. Apparently there is a connection lead under it. Worked for me. KB has not gone crazy on me for over a week.
Related
Hello,
My Raphael 100 dpad buttons are not working in android roms!
I can't go 'back' or to 'home' in Android
"Home" button and "call" button act as navigation key (left)
"back" button and "call end" button act as navigation key (right)
I have tried numerous roms (neofroyo, thunderbolt, hercules, cbv2, cherrypie and more), even non-cwm roms (frx07, froyob v5, v6)
Non of them worked
I also tried with several different kernels (very old, old and new) but still same.
Does anyone have solution for this?
Haven't had that problem in a while but then again I haven't really played with XDAndroid about that long. Even still, never had that much of an issue. Usually I could just cycle the screen off then on and the problem was gone.
Is it possible that you are constantly sliding across the buttons? I know I can get it to go crazy after sliding across the buttons a few times...
No its completely not working only in android roms as if the keys are not mapped
I even tried FRX03 (which was working fine couple of months back in the time) but somehow the keys are not working now... really strange
That's a new issue to me. I take it the d-pad works in winmo but not after you boot into android? Have you filed a bug report yet?
Curious, does the screen react to touch?
Curious said:
Nope it doesn't light when I touch dpad
Click to expand...
Click to collapse
So the d-pad doesn't work in winmo or does it?
it works ! but will take full advantage of your d–pad, your driver must generate the proper virtual key codes ~ http://msdn.microsoft.com/en-us/library/bb821761.aspx
I have an annoying problem with my text input suddenly forcing All CAPS for no apparent reason. I am using the dock and this happens when I don't even have the caps lock button enabled. this sometimes happens if I choose to capitalise a letter using the shift> letter command, after doing this it seems that all text is capitalized. Sometimes I am able to switch off the caps by deleting to the previous sentence where things were normal, but sometimes this won't work.
I'm using SWIFTKEY TABLET X if that makes any difference. Incidentally the capitalisation stated when I typed the capital x just before when I was typing SwiftKey. The capitals would not switch off until I navigated back to some lower case text and typed some stuff, but before returning to where I left off.
Super frustrating and can't seem to resolve it. Not sure if this is a SwiftKey issue or something that others using stock honeycomb keyboard are experiencing?
All help appreciated.
I noticed that same thing. It happens after I come out of sleep. I thought it was the cover resting on the shift key, but it even happens with the dock open.
Pressing the shift key once seems to fix it. I've got a B8O dock with a B5O tablet. The only other non-stock thing I have is WiFi off in sleep. How about you?
Think of the keyboard on the dock as an extension of the software keyboard you are using. In this case, what's probably occurring here is that you're hitting shift twice, and therefore putting the software keyboard into Caps Lock. Just hit shift again to return it to normal. Also, it really is a good idea to switch your keyboard to the stock on when you have the tablet docked.
I doubt I was double shifting (anything like double clutching???), but I'll pay more attention to this.
I was using the standard keyboard. I'll try using the Asus keyboard and see if that resolves the issue.
Anyone still having issues with this?
I am still having the problems, although the shift thing does resolve it a lot of the time.
Shame that ASUS decided to do nothing about this..... REALLY grinds my gears that the vast majority of companies just take the cash and run, and leaving behind a product that could be so much more.
Thankfully we have XDA.
Anyone figured out any way to change the launch buttons on the dock? Since I don't ever use the stock browser this button has become useless.
I was curious about my Swype keyboard on my Galaxy.
I hit something by accident and the input keyboard area turned into a bunch of big buttons with arrows and direction on them.
Anyone know what this is or how to get it to show again?
I hit the return key fast before I realized it was too late. lol
Thanks.
koooba said:
I was curious about my Swype keyboard on my Galaxy.
I hit something by accident and the input keyboard area turned into a bunch of big buttons with arrows and direction on them.
Anyone know what this is or how to get it to show again?
I hit the return key fast before I realized it was too late. lol
Thanks.
Click to expand...
Click to collapse
Swype from the tips key (the one in the bottom left) to the SYM key (the one to the right of it) and you'll pull up a new set of inputs designed to help you navigate text.
for me the swype keyboard keeps freezing and i have to switch inputs to the regular keyboard, then back to swype to reset it. it will last for about a day then freezes up again. I'm running a stock rom on evo 3d. im planning on rooting and running a custom rom, but i was wondering if it happens to more than just my phone.
for as long as I've had my phone, which, of course, is as long as I've had it rooted, my messaging app has acted extremely odd.
Using the arrow keys and the back-space key causes strange, and often app-breaking, behavior. it seems to be registering the key presses in at least 2 other areas of the app. it always scrolls to the top of the conversation, it highlights conversations in the main message window, and it highlights options in the menus before I even have them open. it seems that the window that lists the conversations, as well as the options menu, are still listening to key presses, even when I'm writing a text. often, the arrow keys and the back-space key stop working all together until I back out of the text-input and re-open the keyboard. this happens litterally every time i write a text message, which is a lot.
all I want the arrow keys to do when I'm in a text field is move the cursor, not jump the highlight to the send button, not scroll through auto-complete options, not jump to the conversation window and scroll through individual texts, and certainly not control the selection of items in windows and menus that I don't even have open.
Also, when pressing 2 keys in quick succession, it often only registers one, TH, especially. I'd say its just registering the second press as a movement of the first contact point, istead of a second touch, like old laptop track-pads, but this device is more than capable of registering multi-touch. also, if you hold one key, and press another, the letter from the first appears on the second key for a brief second...
I'm using virtuous ville v.1.4.0 stock, but I've installed and uninstalled a couple other keyboard apps, can I re-install the stock ICS keyboard? is it a sense keyboard? is this happening to anyone else with this rom or with the 4.0.3 os?
thanks for your help
-Peter
god I miss my G1... stupid friggin slabs. this was the first, and will be the last phone that I ever buy without a real keyboard. this touch-screen only nonsense is ridiculous. it would be fast if it were possible to be accurate and keys weren't literally touching each other. why can't I tell it how much space I want between the keys, so I press nothing, instead of the wrong key? there would be no haptic feedback so I knew to press it again, and I wouldn't constantly be pressing the shift, space, and num keys, which the auto-correct doesn't account for in the slightest, instead of the A key or any of the bottom row of letters .I'm tired of sacrificing so much functionality just so phones can look slicker and break easier.
Don't know why it fails, sorry.... The stock ICS keyboard is not a sense keyboard, there is one on market looks like this one https://play.google.com/store/apps/....android.inputmethod.latin.ice_cream_sandwich
Or you could grab a keyboard from any CM9 or AOKP rom zip file, it's named Latin-IME.apk iirc. The jellybean keyboard is similar but nicer somehow, possible it works on ICS. Also SwiftKey is really good.
Thanks for the suggestions! I do, in fact, have a sense keyboard and I do need arrow keys, which the non-sense keyboards, including the jellybean apk don't seem to have. I still can't fathom why anyone would ever prefer these to a real keyboard and a d-pad... also, the jellybean keyboard still has the same trouble with TH's. has anyone here, who shares my frustration with soft keyboards, found a decent keyboard app?
I wish there were decent quality, mini keyboards, too. Wireless or micro-usb would both work, as I'd probably make a case to hold it with my phone. I've only seen a couple, and they're either too big to be practical, or poor quality.
I apologize for my negative attitude. this is just frustrating, as texting is my main form of communication, and I post to forums from my phone quite often, so typing is important to me.
thanks again
-Peter
This is what SwiftKey 3 looks like if you activate the arrows and the Holo theme... One month trial.
Anyone have an issue where the Samsung keyboard will stop responding to SwiftFlow, also known as "swiping"?
For example, sometimes when I want to input text, the Samsung keyboard appears, but instead of being able to swipe through letters, It will only detect "tapping" or the first letter I touch.
The simple fix is to hit the "back" button on the phone which will close the keyboard, then bring the keyboard back and SwiftFlow/Swyping will work again. The problem is I seem to be running into this a few times a day during heavy use, so it's obviously annoying when it happens.