[Sprint Samsung Galaxy Note II] ffolkes:
I've been working on a new idea...

Laggy keyboards are annoying, and often the weakest link in the balance between speed and battery life. For example, I can get by with really conservative settings, but once the keyboard starts to get laggy and choppy I'm forced to back off, even if all other aspects of usability weren't compromised. So, I added some tuneables to accurately control hotplugging in ZZMoove and did some testing. Ultimately I found that increasing the core count helped much more than increasing the frequency. This has led me to try to develop a "Typing Booster" that temporarily increases the core count while there are rapid touches on the bottom 1/3 of the screen (aka typing). IT ONLY WORKS WITH ZZMOOVE FOR NOW. As always, every aspect of it is customizable in STweaks (on the Screen tab).

.

Plasma kernel 2.03b1

.

New options on the Screen tab of STweaks

Typing Booster

[Minimum Cores Online While Typing] - To enable the typing booster, set this to the minimum number of cores you want online while typing. Note: You do not need to modify the additional settings below this one unless you want to. Since there is always at least one CPU core online, setting this to 1 will have no effect, and will disable the typing booster. You must set this to 2, 3 or 4 cores for it to be enabled. Default: Disabled (1 core).

.

[Time Between Each Tap] - The booster is triggered by taps in rapid succession on the bottom 1/3 of the display. This setting controls how fast you need to be tapping (aka typing) in order to trigger the booster. Goal: We want to eliminate false positives. If you are a very slow typer, set this higher - but setting it too high may trigger the booster when you are merely interacting with the screen, and setting it too low will require you to type at superhuman speeds to trigger. Default: 250ms.

.

[Minimum Number Of Taps] - The booster is triggered by taps in rapid succession on the bottom 1/3 of the display. This setting controls how many successive taps, each within the time threshold defined above, before the booster will activate. Goal: More false positive elimination. Think of this as how many letters you need to type before the typing booster activates. The lower this setting, the faster the booster will activate. Default: 3 taps.

.

[Booster Duration] - When the booster is enabled, it will persist for this many cycles (samples) of the CPU governor before automatically turning itself off. This varies for each governor, but each cycle is usually roughly equal to 100ms. Goal: Turn off the extra core(s) we turned on, now that typing has stopped. Default: 30 cycles (about 3 seconds).

.

.

New options on the ZZMoove Hotplug tab of STweaks

[Core Lock] - This locks the hotplugging logic to exactly this number of cores while the screen is on. This setting is mainly for debugging and experimentation. 0 disables this setting. Default: 0.

.

[Min Cores Online] - This limits how many cores the governor will allow to turn off while the screen is on. No less than this number of cores will be online at any time while the screen is on. This setting is mainly for debugging and experimentation. 0 disables this setting. Default: 0.

.

[Max Cores Online] - Renamed, was called Hotplug Limit before. This limits how many cores the governor will bring online while the screen is on or off. No more than this number of cores will be online at any time. This setting is mainly for debugging and experimentation. 0 disables this setting. Default: 0.

.