Originally Posted by mkasick (Post 11751509)

Alternate "timer delay" patch:

Also attached is an alternate patch that supercedes the original. It allows for runtime configuration of the keypad_timer delay via a sysfs exported timer_delay variable.

The current delay may be read with:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
and a new delay may be set with:

Code:
echo N > /sys/devices/platform/s3c-keypad/timer_delay
where N is the delay in jiffies.

A delay of "1" yields the shortest timer, and the most responsive keypad possible, whereas a delay of "256" (1 second) (in most kernels) is the longest allowed. At that point the keyboard is already useless since any keypress results in either repeated characters or the "alternate character popup".

In most kernels (where HZ=256), the default delay is "7" (27 ms), which is the same as the original patch and DI18. A delay of "16" (63 ms) approximates the behavior of stock EB13/EC05.

Basically, the delay is the minimum amount of time one must hold a key down for a keypress to register. It's also the maxmimum time the kernel believes a key is "held down" after it's let go. For example, with a delay of "7" one must hold a key down for 27 ms to register as pressed, and no-more-than 55 ms later does the key register as being released.

Or for a better example, with a delay of "128" one must hold a key down for half a second, and once registered, the key is "held down" for an additional half a second. Which almost guarantees an application-level repeated keypress or the alternate character popup.

Ideally one would start with a delay of "7" and reduce by one until the timer is fast enough for your typing rate that you no longer have dropped keypresses. Although many folks will find that a delay of "7" is fast enough for them.

Mirror link (does not require forum login):
Original patch: epic_keypad_timer_fix-EB13.diff
Timer delay patch: epic_keypad_timer_delay-EB13.diff

Originally Posted by theimpaler747 (Post 12711947)

Even though most customs roms now have the wonderful keyboard patch posted by mkasick here, I've found that almost all of them still drop keys. But, with some experimenting, I believe I've found the perfect value to set the key timer at :)

If you want to make these settings stick at boot, flash my handy dandy zip attached to this post. :D Credit to the method goes to user_none. If you flash and still get occational dropped keys, it's because you're a typing beast. Flashing the speed demon version should fix it 100% for you :D

If you want to do it manually, or try it out first, use the command below:

• Download terminal emulator from the market
• Open it up
• Code:

  ---

  su
echo 5 > /sys/devices/platform/s3c-keypad/timer_delay

  ---

• Should be good! Marvel in the ability to type as fast and accurately as you'd like on the Epic's keyboard :)

If this Impaled tip has helped you, toss me a thanks :)

Need a how-to? Big thanks to qbking77 for this video guide! :D

Originally Posted by dumpringz (Post 2090141)

Wirelessly posted (Samsung Epic : Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; SGH-T959V Build/FROYO) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

just want to thank those such as gten, darren, & others that helped me out through my epic related issues & questions in the past 8 months. I'm done with sprint & obviously the epic. while many of u love the device, its keyboard is a failure which is the main reason I got it. all 9 I've been through had the input issue, my sisters has the input issue, every demo has the issue & every supposed fix didn't work .. I'm a believer that u folks that claim not to have issue r in denial because u stand behind the device because u own it or use swype n don't care. . not y I'm done but just had to get that last bit of epic hate off my chest lol ... seriously tho thanks to all those that assisted me over the months. now I'm on a very similar device, galaxy s 4g or w.e the hell its called . . if the test drive goes well ill keep it

Originally Posted by gTen (Post 2090176)

But anyways, wish you luck with your new Galaxy device! (I am presuming the Vibrant 4G?)