Database Users

[Q] SetCPU tweaks for Droid X?

So just curious...anyone played around with the settings for "Advanced" on their DX? Wondering if anyone has found any values that work better and give better performance/battery life then leaving it as-is.
Not new to using SetCPU btw...been using it since I rooted/installed a custom ROM sometime last year.

JagoX said:
So just curious...anyone played around with the settings for "Advanced" on their DX? Wondering if anyone has found any values that work better and give better performance/battery life then leaving it as-is.
Not new to using SetCPU btw...been using it since I rooted/installed a custom ROM sometime last year.
Click to expand...
Click to collapse
I usually lower the sampling rate so that it checks itself more often... I also lower the up threshold to somewhere between 20%-35% so when the cpu load hits that percentage setcpu will tell the cpu to go "balls to the wall"...
"4. Advanced Tab
The Advanced menu allows you to tweak the finer aspects of certain CPU governors. It is only activated when you choose the ondemand or conservative governors.
Sampling Rate – An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down.
Up Threshold – Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up.
Down Threshold (conservative only) – Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU down.
Ignore Nice Load – If this value is “1,” the system will ignore “Nice” processes when deciding to scale up or down.
Powersave Bias (ondemand only) – Setting this value higher will “bias” the governor toward lower frequencies.
Choose the “Set on Boot” checkbox to apply advanced settings when the phone boots. This option is completely independent of the similar option in the Main tab."
Sources:
http://forum.xda-developers.com/showthread.php?t=505419
http://www.setcpu.com/

If you don't mind me asking what value do you change the sampling rate to? What kind of performance improvement to you see?
What rom you running btw?

CPUFreq Governor Info

A plethora of info on CPU governors (source):
CPU frequency and voltage scaling code in the Linux(TM) kernel
L i n u x C P U F r e q
C P U F r e q G o v e r n o r s
- information for users and developers -
Dominik Brodowski <[email protected]>
some additions and corrections by Nico Golde <[email protected]>
Clock scaling allows you to change the clock speed of the CPUs on the
fly. This is a nice method to save battery power, because the lower
the clock speed, the less power the CPU consumes.
Contents:
---------
1. What is a CPUFreq Governor?
2. Governors In the Linux Kernel
2.1 Performance
2.2 Powersave
2.3 Userspace
2.4 Ondemand
2.5 Conservative
2.6 Interactive
2.7 MinMax
2.8 SmartassV2
3. The Governor Interface in the CPUfreq Core
1. What Is A CPUFreq Governor?
==============================
Most cpufreq drivers (in fact, all except one, longrun) or even most
cpu frequency scaling algorithms only offer the CPU to be set to one
frequency. In order to offer dynamic frequency scaling, the cpufreq
core must be able to tell these drivers of a "target frequency". So
these specific drivers will be transformed to offer a "->target"
call instead of the existing "->setpolicy" call. For "longrun", all
stays the same, though.
How to decide what frequency within the CPUfreq policy should be used?
That's done using "cpufreq governors". Two are already in this patch
-- they're the already existing "powersave" and "performance" which
set the frequency statically to the lowest or highest frequency,
respectively. At least two more such governors will be ready for
addition in the near future, but likely many more as there are various
different theories and models about dynamic frequency scaling
around. Using such a generic interface as cpufreq offers to scaling
governors, these can be tested extensively, and the best one can be
selected for each specific use.
Basically, it's the following flow graph:
CPU can be set to switch independently | CPU can only be set
within specific "limits" | to specific frequencies
"CPUfreq policy"
consists of frequency limits (policy->{min,max})
and CPUfreq governor to be used
/ \
/ \
/ the cpufreq governor decides
/ (dynamically or statically)
/ what target_freq to set within
/ the limits of policy->{min,max}
/ \
/ \
Using the ->setpolicy call, Using the ->target call,
the limits and the the frequency closest
"policy" is set. to target_freq is set.
It is assured that it
is within policy->{min,max}
2. Governors In the Linux Kernel
================================
2.1 Performance
---------------
The CPUfreq governor "performance" sets the CPU statically to the
highest frequency within the borders of scaling_min_freq and
scaling_max_freq.
2.2 Powersave
-------------
The CPUfreq governor "powersave" sets the CPU statically to the
lowest frequency within the borders of scaling_min_freq and
scaling_max_freq.
2.3 Userspace
-------------
The CPUfreq governor "userspace" allows the user, or any userspace
program running with UID "root", to set the CPU to a specific frequency
by making a sysfs file "scaling_setspeed" available in the CPU-device
directory.
2.4 Ondemand
------------
The CPUfreq governor "ondemand" sets the CPU depending on the
current usage. To do this the CPU must have the capability to
switch the frequency very quickly. There are a number of sysfs file
accessible parameters:
sampling_rate: measured in uS (10^-6 seconds), this is how often you
want the kernel to look at the CPU usage and to make decisions on
what to do about the frequency. Typically this is set to values of
around '10000' or more.
show_sampling_rate_(min|max): the minimum and maximum sampling rates
available that you may set 'sampling_rate' to.
up_threshold: defines what the average CPU usage between the samplings
of 'sampling_rate' needs to be for the kernel to make a decision on
whether it should increase the frequency. For example when it is set
to its default value of '80' it means that between the checking
intervals the CPU needs to be on average more than 80% in use to then
decide that the CPU frequency needs to be increased.
ignore_nice_load: this parameter takes a value of '0' or '1'. When
set to '0' (its default), all processes are counted towards the
'cpu utilisation' value. When set to '1', the processes that are
run with a 'nice' value will not count (and thus be ignored) in the
overall usage calculation. This is useful if you are running a CPU
intensive calculation on your laptop that you do not care how long it
takes to complete as you can 'nice' it and prevent it from taking part
in the deciding process of whether to increase your CPU frequency.
2.5 Conservative
----------------
The CPUfreq governor "conservative", much like the "ondemand"
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered environment.
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
2.6 Interactive
---------------
The CPUfreq governor "interactive" is designed for latency-sensitive,
interactive workloads. This governor sets the CPU speed depending on
usage, similar to "ondemand" and "conservative" governors. However,
the governor is more aggressive about scaling the CPU speed up in
response to CPU-intensive activity.
Sampling the CPU load every X ms can lead to under-powering the CPU
for X ms, leading to dropped frames, stuttering UI, etc. Instead of
sampling the cpu at a specified rate, the interactive governor will
check whether to scale the cpu frequency up soon after coming out of
idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is very busy between exiting idle and
when the timer fires then we assume the cpu is underpowered and ramp
to MAX speed.
If the cpu was not sufficiently busy to immediately ramp to MAX speed,
then governor evaluates the cpu load since the last speed adjustment,
choosing th highest value between that longer-term load or the
short-term load since idle exit to determine the cpu speed to ramp to.
There is only one tuneable value for this governor:
min_sample_time: The minimum amount of time to spend at the current
frequency before ramping down. This is to ensure that the governor has
seen enough historic cpu load data to determine the appropriate
workload. Default is 80000 uS.
2.7 MinMax
---------------
The CPUfreq governor "maxmin" tries to minimize the frequency jumps by limiting
the selected frequencies to only two frequencies: either the min or the max
frequency of the current policy. The frequency is raised or lowered according
to the current load and the 'up_threshold' and 'down_threshold'.
Its parameters and implementation are similar to that of conservative.
It does not have the freq_step parameter as it jumps right from min to max
and vice-versa.
The sampling_down_factor, unlike conservative, will count the minimal number
of samplings since the last time we saw the 'up_threshold' load on the CPU.
Hence it is set to higher default and acts as a limiter not to do too many
frequency jumps without hurting the performance.
2.8 SmartassV2
---------------
The CPUfreq governor "smartassV2", like other governors, aims to balance
performance vs battery life by using low frequencies when load is low and
ramping the frequency when necessary, fast enough to ensure responsiveness.
The implementation of the governor is roughtly based on the idea of interactive.
The idle loop is used to track when the CPU has idle cycles. The idle loop will
set a relatively high rate timer to sample the load when appropriate, the timer
will measure the load since it was set and schedule a work queue task to do the
actual frequency change when necessary.
The most important tunable is the "ideal" frequency: this governor will aim
for this frequency, in the sense that it will ramp towards this frequency much
more aggresively than beyond it - both when ramping up from below this frequency
and when ramping down from above this frequency. Still, note, that when load is
low enough the governor should choose the lowest available frequency regardless
of the ideal frequency and similarly when load is consistently high enough the
highest available frequency will be used.
Smartass also tracks the state of the screen, and when screen is off (a.k.a
sleep or suspended in the terms of this governor) a different ideal frequency
is used. This is the only difference between the screen on and screen off
states. Proper tuning of the awake_ideal_freq and sleep_ideal_freq should
allow both high responsiveness when screen is on and utilizing the low
frequency range when load is low, especially when screen is off.
Finally, smartass is a highly customizable governor with almost everything
tweakable through the sysfs. For a detailed explaination of each tunable,
please see the inline comments at the begging of the code (smartass2.c).
Click to expand...
Click to collapse

Kernel][ICS] Devil3_1.1.0 [02/08/12] - Cappy

This kernel is based on teamhacksung's kernel, with updated Linux base to 3.0.38
This kernel is working with every ICS based Rom
Features:
- 378, 391 and 403 Mb Ram available (selectable in kernel, no need for a patch (403 mb breaks 720p) only reboot required)
- 2 different recoveries included (cmw touch recovery + twrp recovery (to use TWRP, just create a file named "twrp" at /cache))
- SIO scheduler (default)
- V(R) scheduler (maybe even faster than SIO, can be set as default by using NSTools for example)
- init.d
- Voodoo Sound and CM9 Color Adjusment / Voodoo Color (VC version)
- Devil Idle
- BLN V9 (thx to mialwe)
- USB Host mode driver (for more information about this, and for saying thanks to the guy, who ported this for our phone, please visit this thread: http://forum.xda-developers.com/showthread.php?t=1450298 )
-Ezekeel's Live_Oc
- Ezekeel's Deep Idle V2
- Touchwake
- vibrator intensity control (by mialwe)
- BLX (Batterie Life Extender, I don't think we need it, but maybe one feels better by using it )
- backports from Linux 3.2 and 3.3
- Swap/Zram support
- Zcache, Cleancache and Frontswap
- Uksm
- Fiops io scheduler
- Smooth_ui included to ondemand, conservative, smartass, lulzactive, lagfree and lazy governor (only one setting for activating/deactivating it in general)
- 3 cpu governor presets (smooth, normal, powersave) for ondemand, conservative, smartass, lulzactive, lagfree (only one setting for switching the mode in general)
- many other small features and improvements
Donwload and Changelog post 2
FAQ and known issues in post 3
Click to expand...
Click to collapse
Many of the features (like Live_OC) require NSTools, which can be found at market for free.
NEW:
Devil kernel Config: http://forum.xda-developers.com/showthread.php?t=1715383
Devil Kernel Manager: http://forum.xda-developers.com/showthread.php?t=1723222
Both Apps are really great. Please try on your own, which one you like more.
you still can use the previous methods of setting up the kernel:
Please also try this app http://forum.xda-developers.com/showthread.php?p=22430406, for setting many of the options which are only available with my kernel.
a pre configured file for use with command center can be found here: http://forum.xda-developers.com/showpost.php?p=27353078&postcount=240 (you have to remove .zip extension)
a good explination/example of how to use it, can be found here: http://forum.xda-developers.com/showpost.php?p=26301176&postcount=4842
if you don't like additional apps (or are having problems with command center), i recommend using this init.d script: http://forum.xda-developers.com/showpost.php?p=26683004&postcount=5346
Click to expand...
Click to collapse
Kernels with VC in the name are coming with Voodoo Color
oliva94 said:
IF the kernel zip name contains _JB_, THEN and only then you can use it IF you do NOT have datadata partition
ELSE if you HAVE datadata, then use one WITHOUT _JB_ in the name
if you use it otherwise, it will boot but system is eventually going to crash/not load due to partition table (thus blockdevice naming) mismach
Click to expand...
Click to collapse
Many Thanks to:
Teamhacksung
Zacharias.maladroit
Onecosmic
ytt3r
TK Glitch
Ezekeel
Eugene373
franciscofranco
Sunra
scheichuwe
perka
sztupy, for his great work, to get usb host mode driver
mialwe
stratosk
F4k for the idea to flash bigmem libs
...
sources:
https://github.com/DerTeufel
Click to expand...
Click to collapse
This kernel is also available for:
Captivate, Fascinate and Vibrant
Click to expand...
Click to collapse
Working on this kernel is taking many hours almost every day. With a small donation, you show me, that my work is appreciated by you.
If you like this kernel, please donate to me

Changelog:
changelog 02.08.2012:
- bug fix to bln, to prevent kernel panic in some situations (thx to thalamus)
- switched from deep_idle 2 to idle2 (also thx to thalamus)
- updated kernel to linux 3.0.38
- dockaudio sysfs for captivate and fascinate
- automated symlinking from data to system: if one wants to free up some space at /system, without removing an app completely, just copy it from /system/app to /data/sys-parts/app (create the folder if not there), and reboot. during reboot, the app from system gets deleted, and the app from /data/sys-parts/app gets symlinked to system. this is working for almost every app, but i don't recommend doing this with apps, needed for android to work (framework, media provider, settings,...)
IDLE2 can be enabled with the following command:
echo 0 > /sys/module/cpuidle/parameters/idle2_disabled
IDLE2 can be disabled with the following command:
echo 1 > /sys/module/cpuidle/parameters/idle2_disabled
Stats can be obtained from the standard cpuidle interface, which, for
IDLE2 is located at:
/sys/devices/system/cpu/cpu0/cpuidle/state*/time
where * = 1, 2, 3
changelog 25.07.2012:
- updated recovery (no "sdcard format"-bug anymore, external sd card is named correctly)
- vibrant: hopefully fixed froyo ril
- jellybean: galaxy s settings working now
changelog 22.07.2012:
This kernel is for use with ICS only, if you are looking for a kernel, running on teamhacksung cm10 build, visit my jellybean kernel thread[/url]
- updated kernal base to linux 3.0.36
- updated "block" to linux 3.3
- readded fiops io scheduler (kept cfq this time)
- updated cwm recovery to 6.0.1.0 (please create a new nandroid, because of possible incompatibilities between old/new recovery)
- compiled with linaro toolchain (gcc 4.7.1) and O3 compiler flags
- made uksm scan less often (save cpu time and power)
- at first boot: only delte init.d scripts created by other kernels
- increased usb write performance
- lowered ram and display voltages a little bit
- fixed some bugs related to devil settings (they should stick now after reboot, if set by one of the devil apps)
- support for scripts in /system/etc/shutdown.d (thx to Efpophis)
all scripts placed at /data/local/shutdown.d or /system/etc/shutdown.d get executed at shutdown/reboot
you can use this, to play a shutdown sound for example.
by default 00shutdown gets created, which plays a music file, when it is placed at one of these folders/places
/system/media/audio/ui/shutdown.ogg
/data/media/audio/ui/shutdown.ogg
Click to expand...
Click to collapse
- disabled some debugging options
- audio (and for fascinate: camera fixes) by Efpophis+
- patch for improving batterie life by CML
- nfts read/write driver built in (for use with usb host mode)
- reverted refreshrate_mod and gpu_oc mod, as both weren't working
changelog 18.06.2012:
- some changes to load balancing
- added ultra ksm (metioned by zach thx for this my friend)
- readded fiops io scheduler (still experimental and could cause instablilities)
- using snappy compression for zram now (2 times faster, but only 2% less compression)
- added the possibility to change zram size (at /data/local/devil/zram_size, with valid values: 50, 75, 100 and 150 (all in mb))
- fixed the applying of user_min/max freq after reboot
- vibrant: fixed gps
- fascinate: fixed nandroid in cwm recovery
what is ksm? http://en.wikipedia.org/wiki/Kernel_SamePage_Merging_(KSM)
uksm is more optimized and also working for single core systems. using this should give much better ram usage, but at the cost of more cpu usage
############# most probably not working (yet)##############
i have added seperate gpu oc from jt1134's galaxy_tab (to switch between 200 and 250 mhz), but i did not get any improvements in antutu...further tests needed
echo 1 > /sys/kernel/pvr_oc/pvr_oc (for 250 mhz)
echo 0 > /sys/kernel/pvr_oc/pvr_oc (for 200 mhz), no reboot needed
and also have changend default screen refreshrate from 60 to 56, with the possibility to change it:
echo 1 > /sys/kernel/refreshrate/enable (60 hz)
echo 0 > /sys/kernel/refreshrate/enable (56 hz)
######################################################
changelog 10.06.2012:
cwm recovery:
- fixed mounting of external sd card to pc
kernel:
- picked two commits from linux 3.0.32 (avoid a possible memory leak, small fix to ext4 driver)
fascinate:
- fixed wrong mount points
changelog 09.06.2012:
- updated Zram and Zcache from linux 3.3
- updated android binder driver from linux 3.3
- fixed restoring of backups within TWRP recovery
- added virtual buttons to cwm recovery (Attention: they still don't work!)
- call vol hack from tk glitch (take a look at init.d folder and edit the script to make changes to call vol hack)
- bigmem values get applied at first boot after power on (if there is a value at /data/local/devil/bigmem, 1 for 391 mb and 2 for 403 mb (the last one breaks 720p)
- prevent phantom key presses (from tk glitch)
changelog 24.05.2012:
- Smooth_ui included to ondemand, conservative, smartass, lulzactive, lagfree and lazy governor (only one setting for activating/deactivating it in general)
- 3 cpu governor presets (smooth, normal, powersave) for ondemand, conservative, smartass, lulzactive, lagfree (only one setting for switching the mode in general)
- no need for activating/deactivating of selective live_oc anymore --> just change target low and target high
- BLX back in
- fixes to devil idle to be more stable while in call
- 1,5 mb more ram (thanks to mialwe)
- added aroma filemanager to cwm recovery
- added fully working TWRP recovery optional to cwm recovery (to use TWRP, just create a file named "twrp" at /cache)
- added option to select ram config in kernel --> no need for flashing an other kernel to get more ram (thanks to stratosk)
- switched to new initramfs from stratosk and mialwe ( now there will be cmw zip and odin tar file of every kernel version)
- added possibility to use Zram instead of Swap
- no need for flashing/using special scripts to make swap/zram working anymore
- added zcache
- added frontpage
- added cleancache
- added fudgeswap (thanks to ezterry and faux123)
changelog 01.05.2012:
- all changes from cm9 stock kernel (including mount points option)
- some fine tuning to deadline and sio
- Devil Idle: limiting bus/ram/gpu speed to 100 mhz for 100-800 mhz cpu freq, while screen off (automatic mode) or always (permanet), both modes automatically reduce the int voltages of the affected freq by 50 mV
- compiled with swap support
- added stratosk's smooth_ui to lulzactive governor (activated by default)
- rest oc_value to 100 while screen off, and back when screen turns on (combined with devil idle automatic, can't be turn on/off without devil idle)
- added posibility for different voltages while screen off (also bundled with devil_idle, with default settings, stock arm voltages are applied, because of live_oc set to 100)
- added the possibility to set freq limits while screen off (min and max freq)
19.04.2012
- even better fix to selective live_oc (last one (in test kernel) generated some overhead)
- fixed sampling rate of ondemand and conservative (have ported mialwe's/stratosk's sleep multipliers)
- new tunables for ondemand and conservativ
sleep multiplier and tunables:
mialwe and stratosk had the great idea, to change the sampling rate of conservative and ondemand governor while display of. for this, he introduced the sleepmultiplier (in his case factor 3). this means, if you set sampling rate to 20000, it changes to 60000 while screen off, and back, when screen on.
for ondemand and conservative:
i have made this multipliers tunable. proper values are between 1 and 5, because one could want a higher multiplier while screen off, if sampling rate is very low while screen on (higher sampling rate means, less checking for work load --> better batterie, worse performance). with this tunables you get better batterie, without making the performance worse while screen on.
two other tunables: up_threshold_min_freq and responsiveness_freq
the first one is a very low threshold while on low freq (by default 40), to make the governor scale up faster, until the responsiveness_freq is reached.
the responsiveness_freq is set to 400000 (400 mhz) by default. while the freq is below this value, up_threshold is the same as up_threshold_min_freq, and freq jumps to responsiveness_freq, with skipping the freq between the actual one and the responsiveness_freq. (conservative governor does not jump up to this step)
responsiveness_freq can be set to values between 100000 and 1400000
up_threshold_min_freq can be set to the same values as the normal up_threshold.
not tunable: while screen off, up_threshold is set to 95, no matter your other settings, to save more batterie.
up_threshold_min_freq is disbaled by default for conservative governor
for lulzactive:
for this governor, i did similar things, but they are not tunable till now.
when screen off:
- inc_cpu_load is set to 90, and back to the original value, when screen turns on
- up_sample_time is set to 50000, and back to the original value, when screen turns on
- down_sample_time is set to 40000, and back to the original value, when screen turns on
other changes:
- fix to touchwake from ezekeel, and another fix from stratosk
- upstream fix to compass
- building for i9000B now, too (big thanks to F4k for the hints by pn )
- removed some typos from recovery
- removed some annoying "no's" and "yes" from recovery in misc menu
- fixed wifi mode switch (pm_fast is the one with better signal)
14.04.2012:
- new b versions (only stock ram) changend to 377 mb, VC version needs the 720p fix from my ftp server. cmc version already patched
13.04.2012:
- updated wifi driver
- added the possibility to switch between wifi PM_Fast and PM_Max mode (Pm_Fast = better signal, PM_Max = better batterie, default is PM_Max)
- user interface to disable fsync (this gives more performace, at the risk of data loss on a crash, taken from ezekeel, so it should be ok ), default is off, to be safe
- fixed voodoo color kernels (these have the VC in their names)
10.04.2012:
- added vibrator intensity control (by mialwe), presets can be changend in recovery
- stock ram version now available (348 mb ram), XL (390 mb), XL_bm (402 mb)
- removed 1080 mhz freq for now
- small correction to touchwake
- small correction to selective live_oc (now the low freq really are not live_oc'ed)
05.04.2012:
- fixed bug in selective live_oc, which caused the target high not taking affect to the highest freq, if highest freq equals target high
- fixed another bug in selective live_oc, which could lead to gpu crashes due to overclocking the ram, but not the cpu freq (for low steps)
- added a switch to change between "normal" and selective live_oc
by changing the live_oc mode while using it, live_oc value is set back to 100, to prevent strange things
- added possibility to set max. freq for boot (in recovery). This freq is set until init.d is executeted (it is automatically set to 1000 at this point, to make sure there are no conflicts with other cpu settings from users)
#Already in the last version, but i forgot about it:
- deep idle fixes from stratosk (many thanks)
- added possibility to underclock by using live_oc (limit is 90 now, which means lowering all freq and bus speed by 10%, to save more batterie when really needed)
03.04.2012:
For now there are three different RAM versions:
- stock mem kernel has 379 mb ram, everything working
- "slim ics" (XL) kernel comes with 390 mb, this is breaking playback of some high resolution videos
- XL_BM is coming with 402 mb ram, but breaking 720p
(while flashing the kernel, the modded rom files are also flashed, so you don't need to flash a new rom to get 379 or 390 mb)
-added new frequency: 1080 mhz (1100 does not like live_oc)
- fixed SmartassV2 for live_oc (after changing live_oc value, you have to change the smartass values, too, but then they automatically apply to the live_oc value (although you can only select 800 mhz in nstools (for example))
- touch recovery with custom devil menu (for some reason it takes a few seconds to load the first time, missing virtual keys is a warning, because there are no virtual keys yet)
-fast charge (thx to chad0989 for this), disabled by default.
you also can use the widget from chad (to place on homescreen) to toggle the fast_charge mode
https://play.google.com/store/apps/d...stchargewidget
Click to expand...
Click to collapse
while fast charge is activated you cannot connect as usb device
- added datafix script to init.d (this script is deactivated by deafult. to make it work, you have to creat a file named datafix and placed in /data/local/)
- reworking and cleaning many parts to get more ram, speed, and stability
05.03.2012:
- updated sio i/o scheduler to latest version
- small updates to ondemand and conservative governor from linux 3.2
- bettter performance for CFS kernel due to tuning and patches
- tuning to deadline scheduler
- better i/o performance
- changed bootlogo (probably not the last time )
28.02.2012
- finally working bln V9 (no need for LED2 anymore)
- fixed lockscreen freezes
- reverted memory tweaks, which could be the reason for lagging after using a day
- again wlan fixes from tk-glitch
- tweaked conservative and ondemand governor (conservative still is not too aggressive)
- added dm-cache again (who has removed this from my github? )
- improve usb signal quality
- xcaliburinhand's dock audio support (untested, do not have a dock)
- less debugging
- fixed kernel version not displayed under "about phone"
12.02.2012
- Added newest Fiops scheduler (tuned for more performance)
- When Gpu is active, min CPU freq is set to second lowest step
- fixes to live_oc and custom voltage
- default mount parameter NOATIME and NODIRATIME (faster)
- updated Wifi drivers (thanks to tk-glitch)
- tuned intellidemand for better performance
- removed some stuff (zram, swap, tweaks to cpufreq untill I know what was causing the instabilities of last build)
05.02.2012
- added Touchwake
- added BLX
- upgraded BLN from V8 to V9 (working for missed calls, blinking or static light, configurabel by using NSTools or BLN Pro App)
- added Intellidemand governor
- added mdnie settings to voodoo color version
- readded deep idle v2 again (I think it is the best/only working one, although
- version with CFS (instead of BFS) now also available (maybe better multitasking and batterie life, but slower)
- removed BFQ I/O Scheduler
- tons of smaller fixes and improvements
30.01.2012
-revert: Voodoo Sound now to be set with DSP Manager
29.01.2012
- Linux kernel 3.1.10
- Deep Idle from Eugene373 (always enabled, no stats)
- added BFQ v 3.1 I/O Scheduler
- Voodoo Sound now to be set with DSP Manager
- Zram (can be disabled by removing Zram file from init.d)
- Zcache and Cleancache (not working yet?)
- optimized rwsem algorithm
- USB Host V5
24.01.2012
- init.d support (the folder is not created by the kernel. You have to do it for yourself)
- Deep Idle V2 back in
- new Cpu governors: MinMax, Lagfree, Lulzactiv
- LED V2 (you can set blinking by using nstools, also working for missed calls in most cases (sometimes it is not working for missed calls, don't know why at the moment))
- Backlight Dimmer (only LED version): used to turn led backlight of, while screen is on, after defined period of time. Deactivating it, makes your backlight stay on all the time
- I/O-less dirty throttling completely backported from kernel 3.2
- Ext4 with 3.2 patches
- Proportional Rate Reduction for TCP - by Google
- USB Host V 4
19.01.2012
- Usb Host drivers integrated
- Cm9 Color adjustment
- Removed Deep Idle because of Bluetooth problems (hopefully it will come back, still testing)
16.01.2012:
- Updated Kernel basis to Linux 3.1.9
15.01.2012:
- fixed bug in cpu spy, caused by live_oc
- still using voodoo color for now, maybe two additional kernel versions tomorrow
Click to expand...
Click to collapse
files with .zip have to be flashed within recovery (twrp or cwm)
files with .tar can be flashed by using odin or heimdall (they are placed at the end of post 3)
ICS:
http://rootaxbox.no-ip.org/divers/ICS/ many thanks to Rootax
JellyBean (with default cm10 partition layout for use with teamhacksung's rom):
http://rootaxbox.no-ip.org/divers/jellybean/
http://devil.haxer.org/ many thanks to SysTem-X (not updatet yet)

Known issues:
- virtual buttons in cwm recovery not working
cappy specific:
- deep idle is causing some devices to not wake up again --> need to long press power button
Click to expand...
Click to collapse
How to:
you can change ram setting by doing the following ( to make these settings even stick after power off, you also have to echo the same value to to /data/local/devil/bigmem):
echo 1 > /sys/kernel/bigmem/enable (this gives you xl mem of 391 mb)
echo 2 > /sys/kernel/bigmem/enable (this gives you bm mem of 403 mb (this is breaking 720p))
echo 0 > /sys/kernel/bigmem/enable (this gives you cm9 default mem of 378 mb)
you have to reboot to make changes work
Click to expand...
Click to collapse
With setting this, your desired swap mode gets automatically applied at boot time. For swap, you have to create a swap partition at your external sd card before
echo 1 > /data/local/swap_use (for using swap partition on external sd card, you have to create this partition before)
echo 2 > /data/local/swap_use (for using Zram, no other modifications required)
you have to reboot to make changes active. You can't use swap and Zram at the same time
Click to expand...
Click to collapse
These are the settings for devil idle:
activate automatic:
echo 1 > /sys/devices/virtual/misc/devil_idle/bus_limit
permanent on:
echo 2 > /sys/devices/virtual/misc/devil_idle/bus_limit
deactivate
echo 0 > /sys/devices/virtual/misc/devil_idle/bus_limit_automatic
Click to expand...
Click to collapse
to set different voltages while screen off (this only is working, if devil idle automatic mode is activated)
this is an example, how to apply screen_off arm voltages:
echo 1450 1400 1350 1275 1075 975 875 800 > /sys/class/misc/customvoltage/arm_volt_screenoff
this way, it is possible to undervolt while screen off, but overvolt and overclock while screen on
for now, the int voltages can not be changend
Click to expand...
Click to collapse
set freq limits while screen off (min and max freq)
enable the limits:
echo 1 > /sys/devices/virtual/misc/devil_idle/user_min_max_enable
disable:
echo 0 > /sys/devices/virtual/misc/devil_idle/user_min_max_enable
set values to be applied if activated:
echo 100000 > /sys/devices/virtual/misc/devil_idle/user_min
echo 800000 > /sys/devices/virtual/misc/devil_idle/user_max
both are independent from devil_idle, and get applied when screen turns off
by default 100 and 1000 mhz are set.
values which can be put here are all "stock" freq (without live_oc level) multiplied with 1000. live_oc values get applied automatically.
Click to expand...
Click to collapse
to set responsiveness_freq, up_threshold_min_freq or sleep_multiplier for ondemand and/or conservative governor, you have to do it like this:
echo VALUE > /sys/devices/system/cpu/cpufreq/ondemand/VARIABLE_NAME
and
echo VALUE > /sys/devices/system/cpu/cpufreq/conservative/VARIABLE_NAME
example:
echo 400000 > /sys/devices/system/cpu/cpufreq/ondemand/responsiveness_freq
echo 50 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_min_freq
echo 5 > /sys/devices/system/cpu/cpufreq/ondemand/sleep_multiplier
up_threshold_min_freq is disbaled by default for conservative governor
(to disable it for ondemand you have to set up_threshold_min_freq to 100.
Click to expand...
Click to collapse
switch between wifi PM_Fast and PM_Max mode (Pm_Fast = better signal, PM_Max = better batterie, default is PM_Max)
echo 1 > sys/module/bcmdhd/parameters/uiFastWifi (pm_fast)
echo 0 > sys/module/bcmdhd/parameters/uiFastWifi (pm_max)
Click to expand...
Click to collapse
user interface to disable fsync (this gives more performace, at the risk of data loss on a crash, taken from ezekeel), default is on, to be safe
echo 1 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled (fsync enabled)
echo 0 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled (fsync disabled)
Click to expand...
Click to collapse
to set the values for vibrator intensity:
echo value > /sys/class/timed_output/vibrator/duty (where value is between 20000 and 43640)
if you want the changes to be applied at boot, you have to use one of the presets from recovery, use an init.d script, or:
echo value > /etc/devil/vibrator (where value is between 20000 and 43640)
Click to expand...
Click to collapse
activate fast charge: echo 1 > /sys/kernel/fast_charge/force_fast_charge
Click to expand...
Click to collapse
deactivate fast charge
echo 0 > /sys/kernel/fast_charge/force_fast_charge
you also can use the widget from chad (to place on homescreen) to toggle the fast_charge mode
https://play.google.com/store/apps/d...stchargewidget
Click to expand...
Click to collapse
while fast charge is activated you cannot connect as usb device
Click to expand...
Click to collapse
Questions and Answers:
Q: What the hell are all these governors?
A: here you should find the answer: http://forum.xda-developers.com/showthread.php?p=19846297
Q: What's a good setup for live_oc??
A: No one knows. Every phone is different. It seems like the folling setup is running well for some (many?) users. If you get reboots with it, you have to find the setup for yourself.
if you are satisfied with this configuration, please hit the thanks button of Crack: http://forum.xda-developers.com/showpost.php?p=22194160&postcount=1246
.:Crack:. said:
OK, these are mine. Rock stable
LiveOC 117% -> 1200 MHz -> 1404 MHz
Freq/ARM/Init
1200/1400/1150
1000/1325/1125
800/1250/1125
400/1025/1100
200/900/1100
100/875/1000
low freqs could possibly be tweaked harder but stability was my fist goal
Click to expand...
Click to collapse
Q: How can I set up swap?
A: Take a look at this thread: http://forum.xda-developers.com/showthread.php?t=1610835, and especially at this post:
http://forum.xda-developers.com/showpost.php?p=25578231&postcount=83
Q: What is Touchwake? Can you explain it?
A: With Touchwake, the touchscreen still recognices your fingers, after turning off (for a predefined time (NSTools)). For a detailed explenation, take a look at Ezekeel's thread: http://forum.xda-developers.com/showthread.php?t=1239240
Q: How can I make Voodo Color settings been saved after reboot?
A: You have to use Voodoo Pro App, because of changes between Gingerbread and ICS, and only the Pro app is updated till now.
Q: Which is the best IO Scheduler?
A: I think SIO and V(R) are the fastest.
Q: How can I enable DeepIdle/Live_Oc?
A: You have to use NSTools. You find it on market. It's free.
Deep Idle Questions:
Q: How can I activate the deep idle stats?
echo 1 > /sys/class/misc/deepidle/stats_enabled
Q: What's the meaning of TOP=Off and TOP=On when I look at the Deep Idle status?
A: When TOP=Off is used, the best powersaving state is used. TOP=ON will be shown, when bluetooth or gps are running.
Q: In Idle status I only see TOP=On. What's wrong here? I don't use Bluetooth or Gps.
A: You have to flash the modded framework-res.apk, because ICS does not fully deactivate bluetooth by default. Even if you never use it.
Q: Idle Stats only are showing Idle, but no Deep Idle. Why?
A: An App is preventing the use of Deep Idle. At first, you should try closing the cam, running in the background. Also rebooting should solve this problem.
Q: What is fudgeswap?
A:
Setting this to a very large positive number will indicate swap ought
to be fully used as free (and will slow the system down)
smaller numbers will allow you to put some pressure on SWAP without
slowing the system down as much.
small negitive numbers will allow the system to be faster at the same
minfree level.
default is 512 to give a very little bit of pressure to use some swap
but this can be modified at runtime via:
/sys/module/lowmemorykiller/parameters/fudgeswap

Very nice, was looking forward to this! Thanks (;
Sent from my ICS Cappy

This looks very promising, going to be keeping an eye on it for sure.
Herp derp Captivate XDA Premium App.

I've been waiting for this for so long. Thank you

I really hope, that everything is working, especially the touchkeys...
Then I can start to add more, in about 6 hours.
Gesendet von meinem GT-I9000 mit Tapatalk 2

I've been waiting to see this in the Captivate Forum

thanks for the new kernel any chance you can write up a post about what each of the tweaks do im still trying to wrap my head around all the terms here lol

Nice to have another kernel around. What is the highest OC on it?

shaolin95 said:
Nice to have another kernel around. What is the highest OC on it?
Click to expand...
Click to collapse
1,4GHZ is the max step you can choose
Kernel runs smooth, games run very well at 1,1GHZ Step with 110%LiveOC SmartassV2 and Deadline
Touchkeys are working fine too
Edit:
The min min step is 200mhz
cant change it to 100

kevinnol said:
1,4GHZ is the max step you can choose
Click to expand...
Click to collapse
That, and there's also selective LiveOC so you can probably max out your phone's capabilities. I haven't flashed yet, just going off of the OP.
Herp derp Captivate XDA Premium App.

I will give it a shot..is not a big deal to test it

Hey DerTeufel1980, you make me wait so long

kevinnol said:
1,4GHZ is the max step you can choose
Kernel runs smooth, games run very well at 1,1GHZ Step with 110%LiveOC SmartassV2 and Deadline
Touchkeys are working fine too
Edit:
The min min step is 200mhz
cant change it to 100
Click to expand...
Click to collapse
this is because of the min freq is set to 200, while the gpu is active...in most cases, this is, when your screen is on
please check cpu spy stats, to see, that 100 mhz also is used.
but, i am going to remove it, cause everyone can set 200 mhz as min, if he/she likes to.

In the Recovery are 3 different profiles, when i choose as example smooth profile what changes are made ?
Looked into the i9000 thread but cant find the answer

Testing
Testing with Doc's Master V11. So far, so good!
Thanks for your hard work!

kevinnol said:
In the Recovery are 3 different profiles, when i choose as example smooth profile what changes are made ?
Looked into the i9000 thread but cant find the answer
Click to expand...
Click to collapse
when you choose smooth, almost each governor is using more agressive profiles for better performance. if you choose powersave, the same, but more power, and with normal, the default governor settings are applied
it's for those of you, who don't want to search and try own settings (or at least, to get an idea, how to change some things)

Testing this out with my previous settings from Glitch, so far so good at 117% LiveOC on 1GHz step.
Herp derp Captivate XDA Premium App.

Will this kernel support call recording from the line? Many people missed that feature from old android 2.2.1

❦ Carenel ❦ 15th October ❦ 3 Battery Saving Editions ❦ Optimized Kernel Settings ❦

❦ Carenel ❦ 15th October ❦ 3 Battery Saving Editions ❦ Optimized Kernel Settings ❦
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashed every kernel under the sun and battery life still isn't meeting up to expectations?
Want to master kernel control apps but haven't got a clue where to begin or how each setting will effect your device?
Afraid of undervolting or underclocking in case your devices performance begins to lack or becomes somewhat unstable?
Kernel related dilemma? In need of urgent assistance?
Are those 'kernel blues' getting you down?
Nobody there to hold you through the night?
We're Carenel.
We give a F!ck about you & your I9100!
We are proficient and have heaps of experience playing around with numerous kernels, day-in, day-out. We want to pass that knowledge on to those who seek it!
Furthermore, please feel free to share what you know with one and other and help each other out as much as you can. We're not available 24hrs, but this thread is.
Together, let's create a tight-knit community where everybody feels welcome and nobody walks away disappointed.
We'll keep the thread free from bullsh!t, though if anyone has information so that we might expand/update/correct the thread, feel free to throw some our way. We welcome it with open arms, legs, mouths, asses, etc.​

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Recarenelmendations
(Customized Set-ups to Suit Your Needs)
Recommended Kernels: Dorimanx & Dream-IRC
Recommended App (Kernel & Voltages): ExTweaks
Stock 'n Roll
Stock Feel. Increased Battery Life.
CPU
Governors: Conservative
Frequencies: 200MHz-1200MHz
CPU Steps: 6 - (1200->100-6-Steps)
Smooth Scaling Level: 500MHz
Hotplug Mode: CPU Hotplug (default)
Load_H0: 65%
Load_L1: 50%
Min_RQ: 2
Load_RQ: 20
Rate: 100 jiffies
Freq_Min: 800000KHz
Max CPU Clock: Dual Core Mode
SCHED_MC: 0
Gentle_Fair_Sleepers: OFF
ARCH_POWER: ON
CPU Undervolting: No Undervolting - (Voltages applied through setCPU)
CPU Idle Mode: AFTR + LPA (default)
Deep-Sleep! CPU Governor: Conservative
GPU
Mali Touch Boost Level: Step3
GPU Freq Step1: 160MHz
GPU Freq Step2: 200MHz
GPU Freq Step3: 267MHz
GPU Voltage Level 1: 850mV
GPU Voltage Level 2: 950mV
GPU Voltage Level 3: 1050mV
GPU Threshold 1-Up: 60%
GPU Threshold 2-Down: 65%
GPU Threshold 2-Up: 70%
GPU Threshold 3-Down: 75%
GPU Threshold 3-Up: 80%
Screen
Min_BL: 10
Min_Gamma: 1
Max_Gamma: 20
LCD-Powersaving Mode: ON
Touch Screen Lock Freq: 500000MHz
Misc
Android Logger: OFF
I/O Scheduler: VR
zRAM: 300MB
Voltages - (Applied via any voltage control app)
200MHz (825mV), 500MHz (925mV), 800MHz (975mV), 1000MHz (1075mV), 1200MHz (1200mV)
Mystical Illusionary
Smoke & Mirrors. Battery + Performance. Flawless Victory.
CPU
Governors: ondemand
Frequencies: 200MHz-1000MHz
CPU Steps: 6 - (1200->100-6-Steps)
Smooth Scaling Level: 200MHz
Hotplug Mode: CPU Hotplug (default)
Load_H0: 70%
Load_L1: 65%
Min_RQ: 2
Load_RQ: 20
Rate: 100 jiffies
Freq_Min: 800000KHz
Max CPU Clock: Dual Core Mode
SCHED_MC: 0
Gentle_Fair_Sleepers: OFF
ARCH_POWER: ON
CPU Undervolting: No Undervolting - (Voltages applied through setCPU)
CPU Idle Mode: AFTR + LPA (default)
Deep-Sleep! CPU Governor: Conservative
GPU
Mali Touch Boost Level: Step2
GPU Freq Step1: 160MHz
GPU Freq Step2: 200MHz
GPU Voltage Level 1: 850mV
GPU Voltage Level 2: 900mV
GPU Threshold 1-Up: 70%
GPU Threshold 2-Down: 75%
GPU Threshold 2-Up: 80%
GPU Threshold 3-Down: 85%
GPU Threshold 3-Up: 90%
Screen
Min_BL: 0
Min_Gamma: 0
Max_Gamma: 15
LCD-Powersaving Mode: ON
Touch Screen Lock Freq: 500000MHz
Misc
Android Logger: OFF
I/O Scheduler: Deadline
zRAM: 300MB
Voltages - (Applied via any voltage control app)
200MHz (800mV), 500MHz (925mV), 800MHz (950mV), 1000MHz (1050mV), 1200MHz (1175mV)
How Low Can You Go?
Battery Maximization. Zero Calories.
CPU
Governors: Pegasusq
Frequencies: 200MHz-800MHz
CPU Steps: 15 - (1500->100-15-Steps)
Smooth Scaling Level: 200MHz
Hotplug Mode: CPU Hotplug (default)
Load_H0: 70%
Load_L1: 65%
Min_RQ: 2
Load_RQ: 20
Rate: 100 jiffies
Freq_Min: 700000KHz
Max CPU Clock: Dual Core Mode
SCHED_MC: 0
Gentle_Fair_Sleepers: ON
ARCH_POWER: ON
CPU Undervolting: No Undervolting - (Voltages applied through setCPU)
CPU Idle Mode: AFTR + LPA (default)
Deep-Sleep! CPU Governor: Conservative
GPU
Mali Touch Boost Level: Step2
GPU Freq Step1: 160MHz
GPU Freq Step2: 200MHz
GPU Voltage Level 1: 850mV
GPU Voltage Level 2: 900mV
GPU Threshold 1-Up: 80%
GPU Threshold 2-Down: 85%
GPU Threshold 2-Up: 90%
Screen
Min_BL: 0
Min_Gamma: 0
Max_Gamma: 10
LCD-Powersaving Mode: ON
Touch Screen Lock Freq: 300000MHz
Misc
Android Logger: OFF
I/O Scheduler: SIO
zRAM: Disabled
Voltages - (Applied via any voltage control app)
200MHz (800mV), 300MHz (825mV), 400MHz (850mV), 500MHz (925mV), 600MHz (925mV), 700MHz (950mV), 800MHz (950mV)
NOTE:
If you're feeling adventurous and fancy attempting a combination of settings for yourself to share with the rest of us, here's a general outline of what you need to know to get you started. Feel free to use my editions as a template if need be. If your 'personalized editions' make us happy, we'll add it to our lists and credit you for your hard work!
Many thanks!
Governors
BALANCED/FLEXIBLE
Ondemand
Lulzactive + (Lulzactive App)
Pegasusq
OndemandX
Hotplug
Userspace
Intellidemand
InteractiveX
SavagedZen
Wheatley
PERFORMANCE DRIVEN
Performance
Lagfree
Badass
Interactive
Lionheart
LionheartX
Smartass
SmartassV2
BrazilianWax
BATTERY FRIENDLY
Conservative
Scary
Sleepy
Lazy
Powersave
I/O Schedulers
BALANCED/FLEXIBLE
Deadline
BFQ
PERFORMANCE DRIVEN
VR
CFQ
BATTERY FRIENDLY
SIO
NOOP
Underclocking (CPU/GPU)
The stock CPU frequencies for the Galaxy SII are 200MHz-1200MHz. The stock GPU frequencies are 160MHz-267MHz. These however can be underclocked and in fact many actually do.
Advantages:
Better battery life.
Device stays cooler.
Theoretically increasing your devices lifespan.
Disadvantages:
Performance not meeting expectations.
Before deciding to underclock your CPU/GPU, you should always consider what you use your device for. If you don't play games that are GPU heavy, you might find that underclocking to 100MHZ-160MHZ will have no noticeable effect on performance. The same can be said for CPU underclocking. If you use your phone for general tasks that don't involve a heavy CPU load, dropping your maximum frequency down to 1000MHz or even 800MHz has no noticeable disadvantages.
Underclocking isn't risky and can only serve to provide better battery life, with the only occasional flaw being a dip in performance depending on the weight of performed tasks. The recommended method of finding which underclocking combination is best for you is just to play around with the settings until you find your perfect match!
REMEMBER THE FOLLOWING: If you're Governor and I/O Scheduler aren't optimized for performance, underclocking may lower performance to an unacceptable level. Please take this into consideration.
Undervolting (CPU/GPU)
Many folks will disagree that undervolting has a drastic effect on battery life; we disagree. EVERY LITTLE HELPS.
To put simply, 'mV' stands for the amount of battery the CPU/GPU consumes, per frequency. The higher the frequency, the more battery life your device consumes. So if every frequency step voltage was decreased by -100mV (at least), that's a lot of battery saved over time and we highly recommend it!
Advantages:
Better battery.
Device stays cooler.
Disadvantages:
If done correctly, there are no disadvantages to undervolting.
If you're looking to create your own customization's, our recommendation is to browse our 'Recarenelmendations' section above and use our undervolting values as a template. Each Galaxy device has been manufactured with slight differences, thus some are more capable of successfully operating under lower voltages levels than others. If you find yourself experiencing SOD's/Freezes/Lag/Reboots, we recommend you raising all our voltages up by +25mV until your device is stable. Once stability is found, begin playing with each voltage until it can be reduced no more (you should expect freezes, there's a 99.9% probability that they will occur.) Through trial & error, we can begin to understand your device better, pushing it to its limited, thus minimalism applied voltages & maximizing battery life whilst also reducing heat during heavy load times.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Kernel Cleaning
(Recommended when changing kernel)
Samsung Ultimate Kernel Cleaning Script ICS
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Kernel Control Apps
ExTweaks
setCPU
N.E.A.K Configurator Pro
Voltage Control
AnTuTu CPU Master Pro
Thoravukk Control
NoFrills
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Battery Saving Methods
Make sure that your data's off when your screen is off. (This option is available via AOKP Roms, otherwise use: Green Power)
Only use battery friendly apps; for instance we don't use Facebook as we've read that it actually drains A LOT of battery... we use Fast Pro for this same reason. (It also has a dark theme, which is good for battery.)
Uninstall unnecessary apps/system apps using Titanium Backup. I found this, this might deem knowledgeable: APK Removal List
Use Autostarts to disable apps and system apps from automatically starting-up in the background.
Use a darker wallpapers.
Apply a lower screen brightness for darker environments or use: Lux to intelligently control your screen brightness.
Use a dark theme, such as: Blue Infinitium
Sync only what you need. Nothing more, nothing less.
Be sure to use Betterbatterystats to determine what is keeping your phone awake when your screen is off & not deep sleeping.
Use Badass Battery Monitor to detect which apps/system apps inflict the largest drain. If you can target these rogue apps, you can uninstall or replace them.
Lastly, be intuitive. Be overly cautious about what might be sucking up your battery and eventually you'll get things right.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -​

Hi-Scores
Submitted by: hospital349
STOCK BATTERY - 1650 mAh
Music: 3.5 hours, Youtube: 15 mins, Vimeo: 10 mins, Chrome: 30-40 mins, Texts: 75-100, Phone Calls: 30 mins, Friendcaster: 10 mins, XDA: 15 mins, Games: 15 mins, Camera: 15 photos, Airdroid (PC to Android file transfer): 1gb+. Syncing: Chrome, Gmail, Haxsync, Dropbox. WiFi: 15 mins. H+/3g: Nearly always.
Note: (The small dip in the graph is when I had to replace a system file and set permissions. I was forced to restart my phone at this point. I have accounted for this.)​

Nice, amazing work mate. This will be very helpful for all NEAK users. Keep up the good work.

bajee11 said:
Nice, amazing work mate. This will be very helpful for all NEAK users. Keep up the good work.
Click to expand...
Click to collapse
Thanks buddy. I really appreciate your efforts. Constantly awaiting your next results.
It was your thread which initially triggered my interest in underclocking/volting to begin with.
Thanks for making an impact.

i still cant figure out where i can
Dynamic Hotplugging: Enabled
can you enlighten me?

Dimenxion said:
i still cant figure out where i can
Dynamic Hotplugging: Enabled
can you enlighten me?
Click to expand...
Click to collapse
Sure - it's located in the Misc Options section of the N.E.A.K. Config Pro App.
N.E.A.K. Configurator Pro App > Misc Options > Dual Core Settings > Dynamic Hotplug
I've adjusted the Lulzactive App Settings slightly, as I posted my old settings instead of the ones I'm currently using. Be sure to correct them on your device.
Enjoy!

Dimenxion said:
i still cant figure out where i can
Dynamic Hotplugging: Enabled
can you enlighten me?
Click to expand...
Click to collapse
2nd Core - Play Store Or NEAK Config Pro

thanks for the help!

Hello,
Thanks for sharing your experience with the others, that is great. I'm gonna check your config soon. But when I started using NEAK kernel and tried UV/UC I experienced many wakelocks (when unlocking lock screen the phone hanged).
I came back to default configuration (without UC/UV with Lulzactive/VR with default settings) but it didn't help. Only then that I disabled "Ext4 Boost", the hangs disappeared. Have you ever experienced this? Is it possible that Ext4 Boost caused this problem or maybe it helped by accident? I'm on XXLPS sammy rom.
__________________
Phone : i9100 Samsung Galaxy S II
Rom : XXLPS/NEAK 2.0.4
Apps: NEAK Configurator Pro, Tegrak Lulzactive 1.1, Voltage Control Extreme.

Many40 said:
Hello,
Thanks for sharing your experience with the others, that is great. I'm gonna check your config soon. But when I started using NEAK kernel and tried UV/UC I experienced many wakelocks (when unlocking lock screen the phone hanged).
I came back to default configuration (without UC/UV with Lulzactive/VR with default settings) but it didn't help. Only then that I disabled "Ext4 Boost", the hangs disappeared. Have you ever experienced this? Is it possible that Ext4 Boost caused this problem or maybe it helped by accident? I'm on XXLPS sammy rom.
__________________
Phone : i9100 Samsung Galaxy S II
Rom : XXLPS/NEAK 2.0.4
Apps: NEAK Configurator Pro, Tegrak Lulzactive 1.1, Voltage Control Extreme.
Click to expand...
Click to collapse
Interesting. You might be better off asking Simone about this one. Seems very strange because I haven't experienced problems since day one. Deep sleep is existent. Wakelocks are non-existent. I'm sure someone on the N.E.A.K. ICS thread will be able to help you.

Yeah, another thread about kernels! Me iz liking. You should post it at teamhydra
Sent from my i9100. No HyDrOG3NICS? No SWAGG..

Paradoxxx said:
Yeah, another thread about kernels! Me iz liking. You should post it at teamhydra
Sent from my i9100. No HyDrOG3NICS? No SWAGG..
Click to expand...
Click to collapse
Hahaha, I know. kernel overkill, right?
Thanks buddy. I appreciate your support.
I still intend to give Netchips kernel a whirl once you release the new update. It's been a while since I last used stock.
I'll be sure to add the thread to teamhydra shortly. Congrats on getting it up and running btw. Great work man.

voltage
hi
Voltages:
800(200), 925(500), 950(800), 1050(1000), 1175(1200)
what should i set 100 MHz to? 950?

frankey81 said:
hi
Voltages:
800(200), 925(500), 950(800), 1050(1000), 1175(1200)
what should i set 100 MHz to? 950?
Click to expand...
Click to collapse
Hey. My recommendation is not to use 100mhz at all, as it wouldn't be battery friendly. Especially because 200mhz is at 800mV, which is the lowest you can go.
You should set your CPU frequency at 200mhz-1200mhz for optimal performance and battery.
Be sure to follow my settings exactly, as they're stable. Even the slightest change might cause instability, unless you're sure you know what you're doing.

Nice done. Im using Siyah but my configs are similar to u so i can give u some question.
I often get around 5 hours of screen on time but i domt play game so I think it's equal.
Your CPu undervolt is amazing, i never thought of setting 200mhz to 800, it's insane, congrats dude
By the way, i only set lulz app cpu load to 75%, i think 90% is too high, but many people do so, so it.must be a reason, can u tell me why ?
By the wau,ur pump up and pump down step is 2 - 1, exactly like.mine , im just too confused about its rate, I set it to 35000, 25000, which of it do u think is best ?
Sent from my GT-I9100 using XDA

randomseasons said:
Nice done. Im using Siyah but my configs are similar to u so i can give u some question.
I often get around 5 hours of screen on time but i domt play game so I think it's equal.
Your CPu undervolt is amazing, i never thought of setting 200mhz to 800, it's insane, congrats dude
By the way, i only set lulz app cpu load to 75%, i think 90% is too high, but many people do so, so it.must be a reason, can u tell me why ?
By the wau,ur pump up and pump down step is 2 - 1, exactly like.mine , im just too confused about its rate, I set it to 35000, 25000, which of it do u think is best ?
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Thanks! Did you try these settings out by the way? (I would love to know if they work for Siyah kernel users.)
I was amazed too. I took a shot in the dark and was shocked and overjoyed that I could get 200mhz down to bare minimum. Very useful indeed!!
90% cpu load is the most I can go with my settings, anything over that freezes my phone. I used to set it to 60%, 70%, 80%... but I really just wanted to maximize battery life. From what I understand, 90% cpu load will restrict high CPU frequencies until they're REALLY needed, so 1000MHZ & 1200MHZ will only kick in at the last minute, (saving tons of juice). I haven't had any issues and would recommend that you definitely give 90% a try. Experimentation is the key.
I know I set my up_sample & down_sample to 20000us, 40000us - but it really is just about what works for you. If I drastically change either one, I'll get varying performances. They generally stay static, unless I have a major breakthrough or blindly test out a theory.
The only things that really change in my overall settings are: Voltages, Dynamic Hotplug Thresholds, GPU mV and perhaps the cpu load (in some situations).
Hope this helps you.

Hi, thanks for the settings info, getting great battery life similar to stock . Only thing I noticed is that wi-fi drops out quite frequently. Would that be anything to do with UV?

mario999 said:
Hi, thanks for the settings info, getting great battery life similar to stock . Only thing I noticed is that wi-fi drops out quite frequently. Would that be anything to do with UV?
Click to expand...
Click to collapse
Very doubtful dude. Haven't had problems my end. Was having some Wi-Fi problems on the previous version of N.E.A.K. (2.0.3), but they were all cleared up by 2.0.4.
Which ROM are you using? Could be a ROM issue? or even a possible compatibility issue between your current ROM and your internet router/modem?
Otherwise, I have no freakin' idea man. Very strange.

Great settings mate. Using this with my new 2000 mAh battery and HyDrOG3N-ICS 05.05. So far seems good and stable.

Slow phone after screen turn on and lockscreen (CyanogenMod 7.2 + sd-ext)

Hello everybody!
I'm having a strange problem: if i have the phone locked, with screen turned off for a while, in my pocket, when i turn it on again it is very slow. It takes about 30 seconds to come back to usual performance.
For example, if i unlock the phone and i go to SMS or WhatsApp, the keyboard (Swiftkey) it's so slow that i have to wait for every word to complete, before i can type another one.
After 30 seconds from the unlock the phone works ok.
The problem started when i've upgraded from CyanogenMod 7.1 to CyanogenMod 7.2 and i've created an sd-ext partition (in ext3 format, on a class 6 SD) to move there some apps.
I've got an HTC Desire HD.
I noticed the same problem when i was using a MIUI rom with the CPU Tuner app: i supposed that it slowed down too much the CPU when the screen was locked, so that it took a lot to come back to normal performances. But, now, i don't have that app installed and, looking ad Exaile 2 when i unlock my phone, it seems that CPU frequencies it's a 1 Ghz and even RAM usage is ok.
What could it be?
I have to wipe and install CM 7.2 from scratch?
Or could it be the sd-ext partition with apps on?
Thank you in advance!

Try installing set CPU or CPU Tuner again and set the CPU to something high when the phone is asleep. If that then works and it is no longer laggy try reverting it to a lower speed.

Not sure about the sd ext partition,, but yes, try a full wipe and install 7.2.
Sent from a dream.

Just change the governor. Governor is interactive by default i think.
Had the same problem after weeks i just changed governor to ondemand and everything was prefect.
Sent from my Desire HD using Tapatalk 2

Try installing set CPU or CPU Tuner again and set the CPU to something high when the phone is asleep. If that then works and it is no longer laggy try reverting it to a lower speed.
Click to expand...
Click to collapse
When i had it, i never configured because i am too lazy
I'll give a try, thanks!
Not sure about the sd ext partition,, but yes, try a full wipe and install 7.2.
Click to expand...
Click to collapse
I do not really want to, but i think too that could be a good test
Just change the governor. Governor is interactive by default i think.
Had the same problem after weeks i just changed governor to ondemand and everything was prefect.
Click to expand...
Click to collapse
Good tip!
My governor is "interactive" too, infact. I'm changin it to "ondemand".
Does anyone have a table that explain the difference between governors?

I'm on ARHD and the same started all of a dudden a few months ago. I had the same governor and settings for months without change and this still started. I changed governors (ondemand, smoothass, smartass, etc.) but it still happens sometimes. Not ver often but sometimes.

sberla54 said:
Good tip!
My governor is "interactive" too, infact. I'm changin it to "ondemand".
Does anyone have a table that explain the difference between governors?
Click to expand...
Click to collapse
Here you go
7. CPU Scaling Governors
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Click to expand...
Click to collapse
Here as well
CPUFreq governors in the Android Kernel
=======================================
+ performance
The CPUfreq governor "performance" sets the CPU statically to the highest frequency within the borders of scaling_min_freq and scaling_max_freq.
+ powersave
The CPUfreq governor "powersave" sets the CPU statically to the lowest frequency within the borders of scaling_min_freq and scaling_max_freq.
+ userspace
The CPUfreq governor "userspace" allows the user, or any userspace program running with UID "root", to set the CPU to a specific frequency by making a sysfs file "scaling_setspeed" available in the CPU-device directory.
+ ondemand
The CPUfreq governor "ondemand" sets the CPU depending on the current usage. To do this the CPU must have the capability to switch the frequency very quickly. There are a number of sysfs file accessible parameters: sampling_rate, show_sampling_rate_min, up_threshold, ignore_nice_load, sampling_down_factor.
+ conservative
The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour more suitable in a battery powered environment. The governor is tweaked in the same manner as the "ondemand" governor through sysfs with the addition of: freq_step & down_threshold
+ interactive
The CPUfreq governor "interactive" is designed for latency-sensitive, interactive workloads. This governor sets the CPU speed depending on usage, similar to "ondemand" and "conservative" governors. However, the governor is more aggressive about scaling the CPU speed up in response to CPU-intensive activity. The tuneable value for this governor are: min_sample_time & go_maxspeed_load
+ smartass (By [email protected])
The smartass governor is a complete rewrite of the interactive governor. CPU spends much more time at the lower frequencies for improved battery life. It gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
+ savagedzen (By [email protected])
SavagedZen is a governor based on the Smartass governor. With tweaks to paramaters which control how much and how fast cpu ramps up/down. Main difference versus Smartass is that cpu ramps down not in fixed steps, but based on cpu load heuristics, i.e. when cpu load falls below threshold (min_cpu_load), cpu immediately ramps down to a frequency derived from the measured load.
+ interactiveX (By [email protected])
Modified version of interactive with suspend code which locks at lowest clock speed when screen is off. Has a sleep+awake profile, meaning you don't need to set up manual profiles, it will lock at your minimum frequency during screen off
Click to expand...
Click to collapse

andreasy said:
I'm on ARHD and the same started all of a dudden a few months ago. I had the same governor and settings for months without change and this still started. I changed governors (ondemand, smoothass, smartass, etc.) but it still happens sometimes. Not ver often but sometimes.
Click to expand...
Click to collapse
Me too i didn't changed the governor, but in my case, a ROM upgrade and a sd-ext creation are some major changes that can affect performances...
l33ch0r said:
Here you go
Here as well
Click to expand...
Click to collapse
Thank you l33ch0r!
There doesn't seem to be much difference between "ondemand" and "interactive"; regarding to this documentation, "interactive" seems more quick.
Anyway, i've changed my governor to "ondemand" and i must say that all yesterday the phone has been fast and responsive. I'll keep you updated!
Thank you very much!