[Sprint Samsung Galaxy Note II] ffolkes:
It's Thanksgiving, the time when everyone enjoys holiday cheer while deving for their phone alone, and talking to their dog. Oh wait, that's just me. :P

I recently went back to TW to flash a PRL, and was surprised how fluid and responsive the UI was. I spend so much time worrying about battery life, I thought it might be interesting to concentrate on performance. They have a touchbooster keeping the CPU at 1400 MHz, and all 4 cores online when your finger is on the screen. No wonder the UI is so fluid. I opted out of that months ago because I figured it was just wasteful, but I think there is merit to it after all. So, rather than have a holiday, I decided to implement my own version based on Samsung's. :P

Plasma kernel 2.04b2 - 4.3 / 4.4 (automatically installs r3p2 video drivers)

- Possible bugfix for unresponsive touchscreen after wake

- Dual-stage touchbooster

New options on the Screen tab of STweaks

Touch Booster

The touch booster engine is divided into two stages; primary and secondary (relaxed). Primary mode takes effect first and is meant to apply aggressive performance settings, then secondary mode takes over and applies less aggressive settings after the defined delay has been met. Secondary mode will then persist for as long as there is a finger on the screen. Both modes offer adjustable frequency and minimum-core-count locks. Primary mode also sets the memory/internal bus to 440/220 Mhz (max), which is released when secondary mode takes over. The goal of all of this is to get your frequency and/or core count high enough to make interactions fluid. Then while your finger is still down and doing something (scrolling perhaps), you no longer need full power, since by then the governor should have had the opportunity to scale up and handle things from then on. However, just in case that doesn't happen, we want to enforce a floor on freq and/or core count, which is what secondary mode does.

[Touch Booster Frequency] - This is the frequency the CPU will be boosted to when a touch is initially detected (primary mode). Goal: Without a booster, by the time the governor samples the system load the user will have noticed lag. So boost to a high frequency as soon as possible. Default: 1000 MHz.

.

[Touch Booster Minimum Cores] - While the touch booster is in primary mode, this many cores will be kept online. 0 (or 1) will disable this setting. Default: 0 cores.

.

[Touch Booster Relax Delay] - After the touch booster has been activated in primary mode, a secondary (aka relaxed) mode will be appled after this delay for as long as a finger is held down. Default: 300 ms.

.

[Touch Booster Relax Frequency] - While in secondary (relaxed) mode, this frequency will be held for as long as there is still a finger on the screen. Goal: The primary booster has already boosted to a high frequency, and by now the governor should be able to accurately take over. However, we dont want to completely stop the touch booster yet because the user is still touching the screen. This feature may be disabled, in which case the boosted frequency will stay as it was set in primary mode (relaxed core count will still work though). Default: 600 MHz.

.

[Touch Booster Minimum Cores While Relaxed] - While the touch booster is in relaxed mode, this many cores will be kept online. When set to 0, cores will remain as they were set in primary mode (i.e. if primary mode brought cores online, leave them on during relaxed mode). When this is set to 1, effectively no extra cores will be brought online and the min limit will be released, as the device always has at least 1 CPU on anyway (i.e. if primary mode brought cores online, turn them off during relaxed mode). Default: 1 core (aka no additional cores).

.

[Touch Booster Duration] - After all fingers are off the screen, the touch booster will remain active (linger) for this much longer. Default: 100 ms.

.