I have a stock sidekick 4g and I was able to reproduce this behavior on my friend's Samsung Galaxy. Some people have complained about randomly dropping keys but it's not random at all.
Steps to reproduce:
1) Go to the home screen with hardware keyboard out.
2) Type "test" quickly
3) "tst" appears in the search box (or some other letters get dropped)
I can do this 9/10 times.
While the phone is loading the search widget, it drops keystrokes. It happens in other places: market search, texting while the phone is doing something in the background, etc.
I don't have any trouble hitting multiple keys or the same key twice really fast. If the search box is up and the phone isn't thinking, all of the keys I hit make it into the box. Both phones run FroYo.
Question: How do I fix this? Can it be fixed? Is this a well-known problem?
Related
Starting a couple of days ago, the hardware keyboard on my Fuze started randomly repeating keys: I'll be typing along and suddenly a character will insert itself a number of times. It seems to happen once every 30-50 keystrokes on average.
I'd write it off as a busted keyboard and take it back to the store for an exchange, but it doesn't feel like a hardware issue. For one thing, whatever key it is always repeats 6, 7, or 8 times. Keyswitch bounces in my experience generally insert fewer spurious characters than that. For another thing, there's no pattern that I can discern to which keys repeat; a hardware problem usually affects one particular key or key grouping.
What I'm seeing looks more like the key release event is being delayed until after the long-press repeat processing takes over; then the release event fires within a fairly narrow timing window. If I watch the screen as I'm typing, I see exactly what I would see if I held the key down: I get one character, then after a short pause, I get 5-7 more of them. This started happening about the time I installed AE Buttons Plus; however, I've uninstalled that and the problem persists. (However, uninstalling often doesn't undo all the registry changes that were made, so AEBP could still be the culprit, I suppose.)
I'm probably going to hard reset tomorrow when I have some free time so I can play around some more with the GPS starting from a clean slate, and that will give me a chance to test whether AEBP is, in fact, responsible. In the meantime, does this sound at all familiar to anyone? Any suggestions for what I might look at in the registry?
A quick update on this: I have verified that AE Buttons Plus is, in fact, responsible for the repeating keys. I set the new key that was added for the PTT button to "Do not touch" in AEBP and soft reset. I have had no repeating keys since then.
I have emailed the author, describing the problem, but I haven't heard back from him yet. I'm hoping that he can either fix AEBP or suggest some workaround to prevent the repeating keys. The short_PTT.lnk/long_PTT.lnk solution recently presented here works fine, but it only gives two assignments, while AEBP can do three (or four, if you can live with the Home button doing the same thing as the single-press PTT button).
If I hear anything encouraging, I'll post again. Otherwise, people should use the shortcut approach for remapping the PTT button.
Q: Why do I frequently end up going to a quick search when I hit the home or back keys?
I have a stock Capitvate running 2,1-update1 / i897UCJH7. FWIW, I'm using the Swype keyboard. I have a number of apps installed. This unit seems perfect in every way (GPS and everything else) except for the following:
Frequently, when I press either the "home" or "back" key, I end up looking at the keyboard and a "Quick Search Box" rather than the home screen or the previous screen. That's not right but even worse, it often appears I am in a loop; pressing either key again frequently does not take me back a screen or to the home screen.
This may be associated with Vlingo. If I force stop Vlingo, the problem is decidedly less frequent but it still occurs. Vlingo tech support will only say their program should run on any Eclair unit although they do not specifically support the Captivate.
I have disabled all of the search options on the phone thinking search is popping up by design. I suppose I could uninstall Vlingo for a final test but I thought if I stopped the program that would eliminate it from consideration.
Maybe I'm missing something somewhere and I'd appreciate your helping me figure out what it is. Thanks in advance.
= Ron
If you do full reset and run the phone with no apps installed and it still occurs, it is the phone and you should exchange it for a new one. Others have experienced this, and many times the only recourse is replacing the phone.
restore it first
I had that happen on one that got lost. I thought it was from staying in my pocket and stuff pressing up against the buttons and wearing them out.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi everyone
I first dismissed this error as another manifestation of the N1's touch screen drawbacks; but since I owned the Nexus S, the same error reappears, and it’s driving me nuts:
All signs point to the fault being caused by the Gingerbread keyboard. This is how you reproduce it:
1) Use more than one keyboard layout / input language
2) Type anything, switch to the first symbols keyboard
3) Hit any key from the symbols keyboard, and afterwards, directly the space bar
4) The keyboard switches back to letter mode, all good up to now
5) Hit the symbols button again
6) The input language automagically changes to the adjacent one, the keyboard switches back to ABC mode
Suffice to say, this is quite an annoyance. There’s a workaround, though: this doesn’t happen if you hit the ABC key before hitting space, but that’s not how I expect my keyboard to work.
Is anyone else able to reproduce this issue, and if yes, does anyone know how to fix this? Unfortunately, extensive research throughout last week didn’t bring back any usable results.
Thanks for your help!
thenoo said:
Is anyone else able to reproduce this issue, and if yes, does anyone know how to fix this? Unfortunately, extensive research throughout last week didn’t bring back any usable results.
Thanks for your help!
Click to expand...
Click to collapse
Hey!
this happens also on my Nexus S...really disappointing (
I played around in the Keyboard settings but couldn't find a way to fix this (unless you remove multiple languages....but that's not the point :S).
Hello!
I'm experiencing some problems with my o2 Touch Pro.
Hardware buttons on the bottom of the phone (d-pad, home, back, call, end call) are not working properly (they work fine only 20% of the time, it's random i guess).
When i press "call" button, device responds as if i pressed the "left" button. It's very annoying. The circle used to zoom in, and out around the "enter" button is problematic as well. It zooms - but but in a very chatoic way - a bit of of zoom in, then zoom out, another zoom in. Functions are just messed up.
Another time, it's all working...
How can i fix it? Is it a hardware problem?
I'm using the Energy Rom - titanium version.
Thanks for your help in advance...
Honestly, if you can't deal with it, get another device. Either that or stick with the stock ROM, less problematic (you can also keep the full function of the d-pad) but then again it may introduce other issues. Someone mentioned this being more a hardware than a software issue. Since I cannot reproduce this on my at&t Fuze, that is all I can suggest on my end.
I get some of that with my fuze; mostly, the d-pad doesn't read gestures properly. If I run compact heaps (from sk tools) periodically, it helps. Soft resetting obviously helps as well. I think it's more of a hardware issue. My problems have definitely gotten worse over time. You can also check out this tool (from an HTC test rom dump; can't remember where I got it). It's a debugger for the d-pad. At least you can see how accurately the button presses and gestures work.
Thanks.
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.