[HTC EVO 3D] MikeC84:
USB Fast Charge

/sys/kernel/fast_charge/force_fast_charge == 1 to enable this feature // 0 to disable this feature (default)

from your pc:

adb shell

echo 1 > /sys/kernel/fast_charge/force_fast_charge

exit

from a terminal app on your device:

echo 1 > /sys/kernel/fast_charge/force_fast_charge

or to create a script:

just add echo 1 > /sys/kernel/fast_charge/force_fast_charge to the script

Check out Chad's app that let's you control fast charge.

https://play.google.com/store/apps/details?id=com.incredicontrol

Sweep2Wake

http://www.youtube.com/watch?v=jri2BMQHHrs

echo 0 > /sys/android_touch/sweep2wake

This will disable the sweep2wake.

Other options are.

0 for disabled.

1 for enabled.

2 for enabled with backlight.

cm9 - Working great

Sense 3.6 - takes screen shot when swiping to sleep

Sense 4 - takes screen shot when swiping to sleep

Miui Sense - Doesn't work great

Configurations:

Start button -> /sys/android_touch/sweep2wake_startbutton -> HOME, MENU, BACK

End button -> /sys/android_touch/sweep2wake_endbutton -> SEARCH, BACK, MENU

If u want ur s2w start from MENU button then

echo MENU > /sys/android_touch/sweep2wake_startbutton

and s2w end at SEARCH button then

echo SEARCH > /sys/android_touch/sweep2wake_endbutton

CPU OC

Not all phones can handle 1.9! You may experience reboots if set too high, just lower until no more reboots, every phone is different...

Over clocking the CPU may drain the battery faster than if you were are at stock clock speed.

Underclock for better battery life...

Battery / Performance build.prop edits

ro.ril.disable.power.collapse=1

pm.sleep_mode=1

debug.performance.tuning=1

debug.composition.type=hw

debug.sf.hw=1

persist.android.strictmode=0

persist.sys.use_dithering=1

persist.sys.ui.hw=true

persist.sys.purgeable_assets=1

ro.com.google.networklocation=0

ro.kernel.android.checkjni=0

ro.config.nocheckin=1

ro.vold.umsdirtyratio=20

dalvik.vm.checkjni=false

dalvik.vm.execution-mode=int:jit

video.accelerate.hw=1

windowsmgr.max_events_per_sec=240

profiler.force_disable_err_rpt=1

profiler.force_disable_ulog=1

Governor Info

Look here for governor tweaks

BadAss Governor

Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 918Mhz and therefore stay cool and will use less power. To trigger a frequency increase, the system must run a bit @ 918Mhz with high load, then the frequency is bumped to 1188Mhz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 1-2 seconds, depending on the load your system is experiencing)

Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1188Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.

Lagfree

Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.

SmartassV2

Version 2 of the original smartass governor from Erasmux. Another favorite for many. The governor aims for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.

I/O Scheduler Info

Noop

Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives). Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.

Advantages:

Serves I/O requests with least number of cpu cycles. (Battery friendly?)

Best for flash drives since there is no seeking penalty.

Good throughput on db systems.

Disadvantages:

Reduction in number of cpu cycles used is proportional to drop in performance.

Deadline

Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.

Advantages:

Nearly a real time scheduler.

Excels in reducing latency of any given single I/O.

Best scheduler for database access and queries.

Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.

Like noop, a good scheduler for solid state/flash drives.

Disadvantages:

When system is overloaded, set of processes that may miss deadline is largely unpredictable.

CFQ

Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.

Advantages:

Considered to deliver a balanced i/o performance.

Easiest to tune.

Excels on multiprocessor systems.

Best database system performance after deadline.

Disadvantages:

Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.

Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.

BFQ

Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.

Advantages:

Believed to be very good for usb data transfer rate.

Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)

Considered an accurate i/o scheduler.

Achieves about 30% more throughput than CFQ on most workloads.

Disadvantages:

Not the best scheduler for benchmarking.

Higher budget assigned to a process can affect interactivity and increased latency.

SIO

Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.

Advantages:

Simple, so reliable.

Minimized starvation of requests.

Disadvantages:

Slow random-read speeds on flash drives, compared to other schedulers.

Sequential-read speeds on flash drives also not so good.

V(R)

Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.

Advantages:

May be best for benchmarking because at the peak of it's 'form' VR performs best.

Disadvantages:

Performance fluctuation results in below-average performance at times.

Least reliable/most unstable.