[Samsung Epic 4G Touch] rujelus22:
Screen Gestures (Making your own)

By default the kernel has 30 configurable gestures. 10 gesture come pre-setup and ready to go. These gestures can be configured through ExTweaks.

You can config the last 20 with you own init.d scripts. I will provide you a base with everything you need to get started, you will need to make what gesture you want and what you want them to do.

Screenshots for the first 10 pre-configured gestures

OK so to make your own, you will need to change the template init.d script I will provide at the bottom of the post. You will need to set what screen gesture you want. Those are set with this syntax

gesture_no:finger_no: (min_x|max_x,min_y|max_y)

then you will need to put in an action of what you want it to do when that gesture happens.

Here is what Gesture 1 looks like

# Gesture 1 - swipe 1 finger near the top and one near the bottom from left to right
1:1:(0|150,0|200) # Top Left
1:1:(330|480,0|200) # Top Right
1:2:(0|150,600|800) # Bottom Left
1:2:(330|480,600|800) # Bottom Right

#with the screen layout like this
# +---------------+
# |0,0 479,0|
# | |
# | |
# | |
# | |
# | |
# | |
# |0,799 479,799|
# +---------------+

#When a gesture is triggered it will run the command listed in it's section like this

if [ "$Gesture" == "1" ]; then
service call vibrator 2 i32 100 i32 0
fi

in that example when you trigger gesture 1 the screen will vibrate. In the template below, I have them all set to just vibrate. This way you can make sure your gestures work before applying any actions to them. I am not going to go that in depth on what all can be run through gestures. If you would like more info or ideas check this guide out Here. Once you have edited the file the way you like, put it back in the provided flashable zip and flash it to your phone.

Gestures Script Template

Template intructions: Extract /system/etc/init.d/usergestures to your desktop. Edit it as you see fit, then put it back into the zip and flash. :laugh:

Some governor info for you guys

Hyper:

The Hyper (formerly known as kenobi) is an aggressive smart and smooth, optimized for SGS2 getweakt and, based on the Ondemand, which was getweakt of Arighi and was equipped with several features of Ondemandx suspend imoseyon. (Added by sysfs, the settings suspend_freq and suspend Imoseyon's code) is the behavior of the hyper Ondemand if it is in action, very similar.

Lulzactive:

This governor is still fairly new and comes from tegrak. It is based on both the interactive and on the Smartass governor.

The slightly older version, if greater than or equal to 60% on their workload, the Governor scaled the CPU to the next level. When the workload was less than 60%, then the governor, the CPU scaled to the next lower level. And when the screen was turned off, then the CPU to the lowest scalable frequency has been locked.

The new version: This version includes three additional configurable parameters. inc_cpu_load, and pump_up_step pump_down_step. These parameters help the user to a greater degree of control. Thus, one can define abzuskalieren the threshold at which the Governor decides to or. You can also specify a certain number of frequency steps that should be skipped when querying.

Brazilianwax:

It is similar to the SmartassV2, only more aggressive scaling up, resulting in more power consumption and battery with it.

SavagedZen:

Another SmartassV2 governor. He achieved a good balance between performance and battery consumption, and is actually underestimated.

Lagfree:

Again, this is similar to the Ondemand governor. The main difference is that it is much battery friendly. The frequency is set to either soft or smooth down raised, unlike the Ondemand, the increase in inquiries rather equal to 100%, although not used. The Lagfree increases so gradually and no skips while the CPU frequency scaling. This also means that the Governor in acute severe power demand does not immediately rise to 100%, and thus to stuttering, such as can occur during video playback.

SmartassV2:

This is a revised version of the governor of erasmux Smartass. This governor is pursuing the goal of achieving an ideal frequency and attempts to achieve this aggressive and lose less aggressive. He uses different frequencies ideal for switching on and switching off the display. If the display is off, the governor scaled down very quickly (aggressive) and scale of the display when you turn quickly to up to 500 MHz. In contrast to the little brother Smartass, there is no limit on the frequency when the display is off. In this governor is also about a balance between performance and battery life.

Lazy:

This governor of Ezekeel is basically one based on the Ondemand, with the only additional parameter min_time_state, which maintains the minimum time of the CPU on a frequency before scaling up and down. These instabilities are due to rapid change in frequency, such as avoiding the Ondemand. The Lazy governor is indeed more inquiries than the Ondemand, but the frequency changes only after the min_time_state, which goes something like step by step (only 200 MHz, 300 MHz, then 400 MHz, etc.). What's more, the Lazy-governor of the house, turning off the display parameters (Screenoff_maxfreq) brings, that you can adjust what may be the highest frequency in MHz when switching off the display

Sleepy:

The Sleepy (formerly known as Solo) is an attempt to strike a balance between performance and battery power to create. It is based on the getweakten Ondemand of Arighi and is optimized for the SGS2. It may include imoseyon's Ondemandx with some tweaks Down_sampling and other features that set by the user through the sysfs of "echo" call. Sleepy is the behavior of Ondemandx when it is in action, very similar.

Interactive:

This governor is more of a faster Ondemand. Slightly faster and battery-friendly. Instead of regular requests in each interval as the Ondemand, determined as it scaled the Interactive when the CPU is woken from sleep. It is an intelligent optimization because of its stability Ondemand. This is the most popular governor in recent years.

Interactivex:

This is an interactive with profiles and wake-up is also battery friendly than interactive. It basically has the same performance as the Interactive, only with better battery performance

Scary:

This is one of the strangest governors. It is based on the Conservative, who is known for its slow scale, but in turn, have elements of Smartass, in turn, is known as one of the fastest skalierfähigen Governore. Some people report that they were fascinated by it. Just hearsay.

Ondemand:

The Ondemand governor is the default choice, due to its balanced settings that offer a good compromise between battery power and performance. However, he has no profile when you turn off the display (screen off sections) or for waking up the phone and respond to inputs with the same high jumps to perform.

Ondemandx:

This is actually a Ondemand governor, with the only difference is that he brings home from profiles of the switch off and switch on the display. The Governor was created in order to be more battery friendly. If the screen is off, the maximum frequency is set to 500 MHz. In spite of the fact that the Ondemand is present in many kernels as it is considered stable, the support of the Ondemandx far-reaching, because in spite of the fast switching frequency and thus has a low transition delay is just too friendly battery. In this play governor, unlike other Governorn, the I / O schedulers a major role.

Intellidemand:

The Intellidemand aka Intelligent Ondemand is another faux Governor, based on Ondemand. But believe some users, this is not a substitute for OC governor daemon. The original Intellidemand behaves differently depending on the GPU usage. If the GPU is really busy (games, cards, benchmarking, etc.) that behaves like the Ondemand. If the GPU is in "neutral" is (that is, claimed more moderate), limiting the maximum frequency of Intellidemand to save depends on the available frequencies in your device or your kernel to conserve battery power. This is known as browsing mode. We can also find some "traces" of the interactive governor. Frequency-scaling in the lower segment depends on the idle time of the CPU. Low idle-time (<20%) implies a reduction of the frequency-scaling of the current frequency. Frequency scaling reductions occurred in 5% increments from the current frequency.

In summary we can say that this is an intelligent Ondemand governor, who is limited by the browsing mode, the maximum frequency when the GPU is idle, and if the browsing mode is available, it behaves like the Ondemand if the GPU is not fully utilized. Even the Intellidemand not switch to the highest frequency when the screen is off.

Lionheart:

The governor is an optimized Lionheart Conservative governor and it also came from Knzo. It is tuned for extreme performance and responsiveness, unfortunately at the expense of battery power.

Performance:

This corresponds to the minFreq MaxFreq, exactly the reverse of the Great Power, which means that the performance governor getting the maximum frequency is set, forcing the battery to its knees. Is thus only be used for benchmarks.

Power Save:

This corresponds to the governor of MaxFreq minFreq. For everyday use, this governor is not recommended.

Conservative:

It is rather a slow of its kind and is more of a slower Ondemand, which scaled up slowly to preserve the battery. To illustrate an example to hand of the Ondemand. The Ondemand increased interactivity of the smartphone at a frequency up to MaxFreq. The Conservatives on the other hand does slow down by half, saving battery power, but at the expense of performance.

Userspace:

Here, individual settings instead of automatic defaults are set. Whether it works and how, apparently, no one knows. It's funny.

Wheatley

Here is a whole section on the wheatley governor

Sakuractive

Abyssplug

HotPlug

Pagasusq

Skywalker

info from here