If you get blank screen on wake up set default min cpu to 380
USB Fast Charge
xz compression (source)
Linaro funroll loop opti
2/11/2013 - v3.6
• Patched up to Linux 3.0.63
• BFQ v6
2/4/2013 - v3.5
• Patched Linux to 3.0.62
• ROW v4 IO scheduler
• Backport ROW to 3.0 - (faux123)
• Update BFQ to v5r1
• Update Linaro toolchain
1/5/2013 - v3.2
• Wheatley governor
• Zen I/O Scheduler
• Update BFQ to v5
• Patch linux to 3.0.57
• Update updater script
11/17/2012 - v3.0
• Patched up to Linux 3.0.53
• Update zcache and zram - (faux123)
• Add Google snappy compression / decompression and set to default
• Patched up to 3.0.51 - (Coolexe, cjoliver)
• Topology drivers - http://patches.linaro.org/project/linux-arm-kernel/
• Optimized CRC32 algorithm
• Advanced screen off profile for mpdecision - (cjoliver)
• CPU Alignment fix
• Badass Governor with GPU control - showp1984
• Update Linaro toolchain - http://releases.linaro.org/
• Disable ROW IO Scheduler
• Adjust vfs cache pressure
• Enabled USB OTG - Yes, I forgot about this :eek:
• Other minor tweaks and fixes
• Expose kblock_scheduled_delayed_work()
• task_times() explosion avoidance for tasks with > 2^32 accrued ticks
• sched,rt: fix isolated CPUs leaving root_task_group indefinitely throttled
• sweep2wake -> naming fix
• Linaro -O3 Optimized
• Fix -O3 compile errors (me - Chad G - Agrabren - Showp1984)
• Implement ck1 patchset - (Ziggy)
• Add -Ofast Linaro flag to config
• Ziggy's sysfs vdd interface - You can now see voltages in Antutu CPU master
• Ziggy's LagFree
• Ziggy's Smartass v2
• Update LZO zram - Now as fast as Google's snappy zram but with better compression - (faux123)
• zram - default back to LZO
• Remove Google snappy zram in favor of LZO - Better compression
• Removed a bunch of governors for battery testing (SavagedZen, Lionheart, Intellidemand, Scary, Lulzactive, Wheatley, Pegasusq, Lazy)
• Add ROW I/O Scheduler - Unstable WIP - (faux123)
• Optimized AES and SHA1 routines - (David McCullough)
• MHzx8 bandwidth - (Coolexe)
• 3-phase throttling with sysfs added to thermal managment - (Coolexe)
• User configurable sweep2wake coordinates - (cjoliver)
• Fix thermal management (me - faux123)
• Tweak deadline io scheduler for better performance on Android - (faux123)
• Sched fixes - (faux123)
• Generic xchg-based implementation for ARMv6+ - (faux123)
• Dynamic sync control
• Fix bug due to buffer overrun
• Fix Max speed on boot up
• Lower display panel voltages - Help with battery life
• Everything else from 1.0.0
• Snapdragon and Linaro optimizations
• Google's snappy zram compression / decompression
• USB Fast Charge v3.1 - (yank555)
• Sweep2Wake 3 button (menu, back, search) - (Coolexe)
• Set default speeds min @ 192 MHz max@ 1516 MHz
• CPU OC up to 1.944 MHz
• L2 Cache up to 1566 MHz
• CPU based alignment handling
• Vdd table interface
• GPU OC 2D @ 266 MHz 3D @ 320MHz (Chad G)
• Glitch free GPU frequency changing
• SLQB Memory Allocator - default
• SLUB optimizations
• Kernel based mpdecision - (Coolexe)
• Kernel based thermal managment - (Dodava)
• vfp neon optimization
• Disable GENTLE_FAIR_SLEEPERS
• Lower vfs cache pressure and made configurable
• Tweaked audio buffers for Beats
• Lowmemkiller and fugeswap
• Lower camera flash to 5%
• USB OTG
• USB headset detection
• Enable dynamic LED brightness
• AC charging for unknown chargers
• Prevent aliased request from starving I/O
• Optimized ARM RWSEM algorithm
• Use glibc version of lib: script
• Use glibc version of lib: memcopy
• Use git implementation of SHA-1
• Increase min /max readahead buffers
• Add optimization levels to config
/sys/kernel/fast_charge/force_fast_charge == 1 to enable this feature // 0 to disable this feature (default)
from your pc:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
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.
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.
- Working great
- takes screen shot when swiping to sleep
- takes screen shot when swiping to sleep
- Doesn't work great
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
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...
for governor tweaks
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. Sysfs included.
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. Sysfs included.
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.
I/O Scheduler Info
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.
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.
Reduction in number of cpu cycles used is proportional to drop in performance.
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.
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.
When system is overloaded, set of processes that may miss deadline is largely unpredictable.
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.
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
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.
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.
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.
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.
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.
Simple, so reliable.
Minimized starvation of requests.
Slow random-read speeds on flash drives, compared to other schedulers.
Sequential-read speeds on flash drives also not so good.