CARBON KERNEL
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
R1
Bricked_hotplug
custom governors (conservative , ondemandplus , intelliactive, smartass, optimax, wheatley, n more )
new power management mode PowerSuspend for deep sleep fixes
frandom add
kernel mode NEON
LCD KCAL Color Calibration
Double Tap 2 Wake
Sweep 2 Wake+Sweep 2 Sleep
Multi Core Power Saving
Faux Sound 3.8
RAM management n optimization
Underclock upto 96 Mhz
dynamic fsync
simple algorithm for GPU from faux123
latest Linaro 5.1.1 (UBER) used for the build with full -o3 optimizations
R2
msm_hotplug and brick_hotplug (msm_hotplug enabled by default)
added state notifier
added USB fast charging
GPU overclock upload 650 Mhz
GPU underclocked to 100 Mhz
Franco Thermals added back with fixes
added governors
abyssplugv2
adaptive
badass
dancedance
darkness
hyper
intelliactive
intellimm
lazy
lionheart
nightmare
ondemandplus
optimax
pegasusq
slim
smartmax
smartmax_eps
uberdemand
wheatly
I/O schedulers added
BFQ
SIO
ZEN
FIOPS
VR
TRIPNDROID
Multicore powersaving enabled to aggressive by default
Added 10 new TCP cong
Used SaberMod 6.0 with -O3 optimizations
and much more check my github for more details
https://github.com/tarunkapadia93/android_kernel_xiaomi_armani/tree/cm-12.1
R3 :
compatible with CM R7 n Nameless R3 n the other lastest builds (that means no SystemUI FC any more )
based of caf kernels by @rebelos
few fixes
led notification light fixed
R4 BETA FINAL:
back to bricked hotplug with proper tuning this time
rebased of armani-dev kernel
video recording issue solved
dt2w & s2s+s2w added
new governor
same list of i/o
gpu max clock too 533Mhz (i dont see a real good scaling at 650 Mhz i m working on this part so pls wait)
R5:
Compiled with Linaro 4.9.4 Cortex A7 (Thanx to Christopher83)
O3 Optimizations
MultiROM support aka Kexec Patched
Works with Both KK n LP Roms
Hotplugs
Intelli_plug
Bricked_Hotplug aka MSM_MPDecision
MSM_Hotplug
Alucard_Hotplug
Governors
Intellidemand
Intellimm
Alucard
Hyper
Impulse
Pegasusq
Nightmare
Intelliactive
Yankactive
Smartmax
Zzmove
I/O Sched
BFQ
FIOPS
SIO
Zen
Vr
TripNdroid
CPU Overclock to 1.7Ghz
GPU Overclock to 590 Mhz
Double Tap 2 Wake
Simple Thermal Driver by @SultaXDA
Dynamic Fsync
Kcal Updates
Faux Sound
Much more
KNOWN BUGS :
LED NOT BLINKING SOMETIMES N STAYS SOLID
How to Install :
Boot into recovery
Wipe cache
Wipe dalvik cache
Flash kernel
Reboot and enjoy!
*use Kernel auditor(best) or Aero Kernel Control (full native sysfs best if you know what you are doing) to activate or tweak with kernel settings
## NOTE ##
After Flashing any Kernel Or Rom let you Phone Cool down to normal temp before you start using it. Pls dont complain the phone is heating n lagging. Flashing n things have heavy CPU usage so if will Heat.
Disable "Enable per-app Profile" if you are running benchmarks like Antutu
Downloads
Carbon kernel downloads
CARBON_KERNEL_LP_KK_25092015_1734.zip - 8.29 MB
its can be flashed on all aosp and cm based roms
Thanx to everyone with helped me all the dev who i cherry-picked from thanx alot :angel:
XDA:DevDB Information
[KERNEL] [25/9] [LP][ KK] Carbon Kernel R5, Kernel for the Xiaomi Redmi 1S
Contributors
Tarun93, fellow kernel dev (kD a.k.a thewisenerd, zeroblade1984, LuffyXDA, armani-dev )
Source Code: https://github.com/tarunkapadia93/android_kernel_xiaomi_armani
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R5
Stable Release Date: 2015-09-25
Current Beta Version: R4 BETA Final
Beta Release Date: 2015-06-19
Created 2015-01-23
Last Updated 2015-09-25
Setting n tweaks
daily use settings
governor = alucard
i/o scheduler = BFQ
cpu = 300 min 1689 max
Alucard Hotplug
gpu mac clk = 450
DT2W will drain battery so think before you tweak around with the kernel n end up telling me your kernel is giving me **** Battery packup
Faux Sound
dont complaint if sound distorts at loud profile
loud profile is mean for full size cans (headphones) n similar things where you need a little more power
dont switch it on if you are using IEM (in-ear earphones) or normal earphones
i normally keep a setting of
digital output gain = 3
analog output gain=5
Hope that this clears some questions n helps you guys :fingers-crossed:
msm_mpdecision
show-p1984 said:
What is msm_thermal?
What is msm_mpdecision?
100% kernel based multi core decision! (should cpu1/2/3 be online or not?)
This replaces your /system/bin/mpdecision binary which is renamed by the installer to mpdecision_bck.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic
delay = time between checks
pause = if something else plugs in the cpu, fall asleep for 10000ms
max_cpus_online_susp = if the screen is off, how many core should be active when the screen is off
enabled = enable(1) or disable(0) mpdecision. This does not affect max_cpus_online_susp
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (300000)
If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)
Hot plug thresholds (aka now it gets 'complicated')
This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
Since we can't unplug cpu0 this is '0'.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
etc...
Some values are:
NwNs_Threshold: 12, 0, 25, 20, 32, 28, 0, 35
TwTs_Threshold: 140, 0, 140, 190, 140, 190, 0, 190
Where the position and function of the number equals the result of the above explained formula.
(all times are in ms)
If you want to see the mpdecision magic happening:
Code:
adb shell
cat /proc/kmsg | grep 'MPDEC'
mpdecision's input event boost, aka project butter
This will boost your min cpu speed if you touch the screen or press a button and gives you full control.
In those events the min cpu freq will be risen to a predefined value (look below) on every online cpu. This boosts overall reaction times and smoothness a lot. (works similar to the qcom mpdecision binary)
Configuration files:
[email protected]:/sys/kernel/msm_mpdecision/conf # ls | grep boost
boost_enabled
boost_freqs
boost_time
All of them work like the usual sysfs files, except one special case:
boost_freqs will list all frequencies from cpu 0 to cpu x. Cpu 3 and any following cpu will share one frequency.
To change those frequencies echo the cpu number + the frequency in khz.
Example: To change the boost freq of cpu3 (and 4,5,6,7,8, etc) the echo would look as follows:
Code:
echo "3 960000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
for cpu0:
Code:
echo "0 960000" > /sys/kernel/msm_mpdecision/conf/boost_freqs
Defaults:
Code:
cat /sys/kernel/msm_mpdecision/conf/boost_freqs
960000
960000
729600
576000
Why do I have no WLAN?
Due to this kernels very high optimization settings it is too big for our boot.img with WLAN included into the kernel, so it is built as a module. That means it needs to be inserted into the kernel upon boot up, which needs to be automated for maximum comfort.
Click to expand...
Click to collapse
enabling n disabling a hotplug is simple
1 = enabled
0=disabled
to disabling a hotplug here is a example via terminal
Code:
echo "0" /sys/kernel/msm_mpdecision/conf/enabled
you can use third party apps too to make it a macro
i like aero kernel control available in the playstore
goto misc settings
tap "+" sign
navigate to the path you want n set the parameter as a macro
msm_hotplug
enabling n disabling msm_hotplug
/sys/module/msm_hotplug/enabled
other parameters
/sys/module/msm_hotplug/
msm_mpdecision
enabling n disabling the msm_mpdecision
/sys/kernel/msm_mpdecision/conf/enabled
other parameters
/sys/kernel/msm_mpdecision/conf/
intelli_plug
enabling n disabling the intelli_plug
/sys/module/intelli_plug/parameters/intell_plug_active
other parameters
/sys/module/intelli_plug/parameters/
MAKE SURE YOU DISABLE THE OTHER HOTPLUGS BEFORE YOU ENABLE ONE
if you enable intelli_plug make sure bricked_hotplug and msm_hotplug are disabled
if you enable msm_hotplug make sure bricked_hotplug n intelli_plug are disabled
bricked_hotplug is enabled by default as i feel its the best daily driver for max sot n battery life without compromising on performance
The zip adds module insertion to your ramdisk, if that fails for some reason the wlan module cannot be inserted.
if
Code:
adb shell lsmod
doesn't show this:
Code:
tun 14701 0 - Live 0x00000000
cifs 275399 0 - Live 0x00000000
bcmdhd 2964650 0 - Live 0x00000000 (C)
Then something went horribly wrong.
Chances are that I broke it and this should never happen.
One post in the issue tracker will probably fix it with the next release
You can restore wlan for your current bootup by executing:
Code:
adb shell
su
insmod /system/lib/modules/bcmdhd.ko
Thanks. Downloading. Gonna try asap. Will leave feedback.
bhu1 said:
Thanks. Downloading. Gonna try asap. Will leave feedback.
Click to expand...
Click to collapse
which rom are you trying it out on ??? pls mention the ROM if you can guys
Tarun93 said:
which rom are you trying it out on ??? pls mention the ROM if you can guys
Click to expand...
Click to collapse
Flashed it on cm11 RC16 for now, everything seems swift and smooth for now. Gonna leave more feedback soon on CM11 RC16.
Tomorrow I'll move to carbon RC6, will provide more feedback then.
Now, I'm gonna go and play around with the settings. Heh.
---------- Post added 24th January 2015 at 12:07 AM ---------- Previous post was 23rd January 2015 at 11:35 PM ----------
So, I played around with some settings and I found a bug. Sweep2Sleep (Also Sweep2Wake) isn't properly implemented, neither is it working nor are its settings proper. https://app.box.com/s/q58sztnn0y8eizuu0go99jlizyngnn3m
Edit : So, I tried the wake settings in trickster mod and when I selected s2w+s2s then s2s is working but s2w is just not working, I tried swiping in many ways, many many times but Its just not working. Also, if u select just s2s then it just reverts back to s2w+s2s probably because s2s isn't working.
I did a standard test I do with all kernels that I try (I have tried all the latest versions of all kernels that are currently available), I close every app that is running in background using greenify, CPU is set to 1.6ghz - 300 MHz, intelliplug (eco mode disabled in urs, no other has eco mode, I use mp-decision on those which doesn't have intelliplug), on demand governer, GPU set at Max (550 on urs and beast kernel and 450 on others) and I play a 720p hevc video, on ur kernel i was getting the smoothest playback among all (It was lagging for the least amount of time, same lag times as beast kernel, so might be just cause of OCd GPU). But in any case, currently this kernel is the best performing and feature rich kernel available. Period.
I'll try other settings (especially eco mode), and will leave further feedback soon.
Thanks, I await further updates. Loving the increasing amount of kernels on our forums.
bhu1 said:
Flashed it on cm11 RC16 for now, everything seems swift and smooth for now. Gonna leave more feedback soon on CM11 RC16.
Tomorrow I'll move to carbon RC6, will provide more feedback then.
Now, I'm gonna go and play around with the settings. Heh.
---------- Post added 24th January 2015 at 12:07 AM ---------- Previous post was 23rd January 2015 at 11:35 PM ----------
So, I played around with some settings and I found a bug. Sweep2Sleep (Also Sweep2Wake) isn't properly implemented, neither is it working nor are its settings proper. https://app.box.com/s/q58sztnn0y8eizuu0go99jlizyngnn3m
Edit : So, I tried the wake settings in trickster mod and when I selected s2w+s2s then s2s is working but s2w is just not working, I tried swiping in many ways, many many times but Its just not working. Also, if u select just s2s then it just reverts back to s2w+s2s probably because s2s isn't working.
I did a standard test I do with all kernels that I try (I have tried all the latest versions of all kernels that are currently available), I close every app that is running in background using greenify, CPU is set to 1.6ghz - 300 MHz, intelliplug (eco mode disabled in urs, no other has eco mode, I use mp-decision on those which doesn't have intelliplug), on demand governer, GPU set at Max (550 on urs and beast kernel and 450 on others) and I play a 720p hevc video, on ur kernel i was getting the smoothest playback among all (It was lagging for the least amount of time, same lag times as beast kernel, so might be just cause of OCd GPU). But in any case, currently this kernel is the best performing and feature rich kernel available. Period.
I'll try other settings (especially eco mode), and will leave further feedback soon.
Thanks, I await further updates. Loving the increasing amount of kernels on our forums.
Click to expand...
Click to collapse
Hey plz comment on the battery life, SOT also.... Thnx
bhu1 said:
So, I played around with some settings and I found a bug. Sweep2Sleep (Also Sweep2Wake) isn't properly implemented, neither is it working nor are its settings proper. https://app.box.com/s/q58sztnn0y8eizuu0go99jlizyngnn3m
Edit : So, I tried the wake settings in trickster mod and when I selected s2w+s2s then s2s is working but s2w is just not working, I tried swiping in many ways, many many times but Its just not working. Also, if u select just s2s then it just reverts back to s2w+s2s probably because s2s isn't working.
Click to expand...
Click to collapse
This is what happens when you don't read the phuxking documentation.
thewisenerd said:
This is what happens when you don't read the phuxking documentation.
Click to expand...
Click to collapse
What do u mean by 'Documentation' ? If u inferring that I didn't read the OP, then I'll inform that I properly read it before flashing the kernel, it says nothing about this. I did notice that the feature list says 'Sleep 2 Sleep' instead of 'Sweep 2 Sleep' but nothing else. What am I missing here, buddy ?
bhu1 said:
What do u mean by 'Documentation' ? If u inferring that I didn't read the OP, then I'll inform that I properly read it before flashing the kernel, it says nothing about this. I did notice that the feature list says 'Sleep 2 Sleep' instead of 'Sweep 2 Sleep' but nothing else. What am I missing here, buddy ?
Click to expand...
Click to collapse
S2w work from bottom left to right,while s2s work from bottom right to left
press thanks if i helped you
Hsmetric181 said:
S2w work from bottom left to right,while s2s work from bottom right to left
press thanks if i helped you
Click to expand...
Click to collapse
I know that, S2W isn't working in any case.
Great Work.
Using this kernel currently with CM R16, everything is working fine.
Battery life is excellent for me. After nearly 15h - there is still 72% battery left. Usage: Screen on: 30 min, Wifi, Bluetooth always enabled.
Only thing so far is that Netflix is not working, but this might be totally Rom related, as it was also not working with the orginal kernel.
bhu1 said:
I know that, S2W isn't working in any case.
Click to expand...
Click to collapse
only s2w wouldnt work s2s n s2w both with be enable together
Thanks for this kernel tarun...really a great one...every thing works awesome...just by using trickstar mod...and this kernel is working for me on PAC latest nitly...just have to flash kernel comparability patch updated!!! Lol
little warm
is this only for me or not, but i feel little warm when using this kernel on carbon. and thats make battery reduce faster.
justian said:
is this only for me or not, but i feel little warm when using this kernel on carbon. and thats make battery reduce faster.
Click to expand...
Click to collapse
fir the first start yes it is let it cool down for a while n you are good to go it wont heat there after
is this working on Mokee 4.4.4 Nightly?
I cant turn the zram off. If i turn it off and save it emidiately gets turned on again. Am i doing something wrong?
everything is working for me guys.
bhu1 said:
I know that, S2W isn't working in any case.
Click to expand...
Click to collapse
S2W is also working properly for me. I am on CM11 RC16.
Tarun93 please mention the settings for best battery and best performance separately please coz I play games a lot and I want to get max battery when I'm not gaming .
Related
This kernel is based on teamhacksung's kernel, with updated Linux base to 3.1.10
Kernel working for Teamhacksung build 13 to 17 (+ nightlies) and also ICSSGS RC3/4.
Features:
- Brain **** cpu-scheduler (BFS) (this should be much faster than the default cpu scheduler) will be back later
- 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)
- 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
- Swap/Zram support
- Zcache, Cleancache and Frontswap
- 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
Changelog and FAQ in post 2
Click to expand...
Click to collapse
Many of the features (like Live_OC) require NSTools, which can be found at market for free.
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=26621026&postcount=5272 (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
I try to support this kernel as good as possible, but due to family and university, I do not have much time, so please be kind, if it takes a little bit longer till I will answer your questions.
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
If you like my work, please donate to me
Devil2 kernel up now:
http://devil.haxer.org/ many thanks to SysTem-X
http://rootaxbox.no-ip.org/divers/ many thanks to Rootax
Changelog:
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)
you can change ram setting by doing (or use command center or similar):
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
- 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
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
- added zcache
- added frontpage
- added cleancache
- added fudgeswap (thanks to ezterry and faux123)
we will add in fudgeswap as long as its less then the free swap
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
Click to expand...
Click to collapse
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
activate automatic:
echo 1 > /sys/devices/virtual/misc/devil_idle/bus_limit_automatic
deactivate automatic
echo 0 > /sys/devices/virtual/misc/devil_idle/bus_limit_automatic
permanet on:
echo 1 > /sys/devices/virtual/misc/devil_idle/bus_limit_enable
permanet off
echo 0 > /sys/devices/virtual/misc/devil_idle/bus_limit_enable
Click to expand...
Click to collapse
- compiled with swap support
- added stratosk's smooth_ui to lulzactive governor (activated by default)
activate:
echo 1 > /sys/devices/system/cpu/cpufreq/lulzactive/smooth_ui
deactivate
echo 0 > /sys/devices/system/cpu/cpufreq/lulzactive/smooth_ui
with this feature enabled, cpu freq jumps up to max freq, by touching the screen.
Click to expand...
Click to collapse
- 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)
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
- added the possibility to set freq limits while screen off (min and max freq)
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 puth here are all "stock" freq (without live_oc level) multiplied with 1000. live_oc values get applied automatically.
Click to expand...
Click to collapse
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.
till now, the tunables have to be changend by:
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
(this can be done by setting the up_threshold_min_freq to 100.
for ondemand, this also disables the additional jump to the responsivenss freq)
Click to expand...
Click to collapse
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)
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, so it should be ok ), default is off, 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 make this settings apply after reboot, select them from recovery --> devil --> misc
- 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)
to change the vibrator intensity on the fly, you have to do the following:
Code:
echo [B]value [/B]> /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 [B]value [/B]> /etc/devil/vibrator (where value is between 20000 and 43640)
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
(can be changend in recovery, devil menu --> performace --> liveoc,
or by (this won't stay after reboot):
Code:
echo 1 > /sys/devices/virtual/misc/liveoc/selective_oc (selective mode)
echo 0 > /sys/devices/virtual/misc/liveoc/selective_oc (normal mode)
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.
activate fast charge:
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
deactivate fast charge
Code:
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
- 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
Questions and Answers:
Q: What are BFS and CFS?
A: The Brain **** Scheduler (BFS) is a task scheduler designed for the Linux kernel in August of 2009 as an alternative to the Completely Fair Scheduler and the O(1) scheduler.[2] BFS was created by veteran kernel programmer Con Kolivas.[3]
The objective of BFS, compared to other schedulers, was to provide a scheduler with a simpler algorithm, that did not require adjustment of heuristics or tuning parameters to tailor performance to a specific type of computation workload. The BFS author asserted that these tunable parameters were difficult for the average user to understand, especially in terms of interactions of multiple parameters with each other, and claimed that the use of such tuning parameters could often result in improved performance in a specific targeted type of computation, at the cost of worse performance in the general case.[4] BFS has been reported to improve responsiveness on light-NUMA (non-uniform memory access) Linux mobile devices and desktop computers with fewer than 16cores.
Q: Is BLN is not working for sms?
A: It is working, but you have to disable "turn screen on" in your sms app.
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: 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: Which CPU governor is the best for use with Deep Idle?
A: As Ezekeel stated, one should use LAZY
What about init.d support?
This looks great, exactly what I wanted. Testing now, will report back.
update: everything installed perfectly, running well. Still testing stability.
Thank I will test it right now
.:Crack:. said:
What about init.d support?
Click to expand...
Click to collapse
no, it is not working.
DerTeufel1980 said:
no, it is not working.
Click to expand...
Click to collapse
Might want to look at Glitch's Sources for that
Edit:
https://github.com/GlitchKernel/Glitch
Getting a lot of soft resets. Screen goes black, I'm kicked back to lock screen, and everything slowly gets loaded back into RAM.
Everything standard, no tweak, deep sleep activated (and modded framework flashed).
Camera Zoom
Great kernel! , Deep idle working fine
However it looks like either the kernel or the framework patch broke camera zoom
How to see if Deep Idle is working? I flashed the zip and enabled, after 20minutes it still show only Idle in stats.
darristan said:
How to see if Deep Idle is working? I flashed the zip and enabled, after 20minutes it still show only Idle in stats.
Click to expand...
Click to collapse
Enable it with nstools
great kernel one of the best. any chance of deep idle fix for ICS rom rc3? =) haven't found it yet
Sent from my GT-I9000 using xda premium
jelle2503 said:
great kernel one of the best. any chance of deep idle fix for ICS rom rc3? =) haven't found it yet
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i will talk to onecosmic later. he has to change it in sources, because scheichuwe was not abled to modify his framework-res.apk
DerTeufel1980 said:
This kernel is based on teamhacksung's Linux kernel 3.08 for i9000 only.
Features:
- Brain **** cpu-scheduler (BFS) (this should be much faster than the default cpu scheduler)
- SIO scheduler (default)
- V(R) scheduler (maybe even faster than SIO, can be set as default by using NSTools for example)
- 337 mb Ram available (720p recording working)
- Voodoo Sound and Voodoo Color (Voodoo Color will be replaced by Pawit's color adjustment with coming build 14, because it will also contain gamma manipualtion)
- Neldar's BLN (for blinking, BLN Pro App needs to be used, known issue: After blinking for the specified time, leds turn off)
-Ezekeel's Live_Oc (I recommend not to go higher than 115% because of overclocked GPU)
- Ezekeel's Deep Idle V2 (you have to flash the attatched modded framework-res.apk, to make this fully working, because ICS is preventing Bluetooth to really shut down)
- many other small features and improvements
For enableling Deep Idle or using Live_OC, you have to use NSTools, which can be found at market for free.
Don't flash the modded framework-res.apk on Onecosmic's rom!
It is taken from perka, and only working for teamhacksung's build.
I try to support this kernel as good as possible, but due to family and university, I do not have much time, so please be kind, if it takes a little bit longer till I will answer your questions.
Many Thanks to:
Teamhacksung
Zacharias.maladroit
Onecosmic
ytt3r
TK Glitch
Ezekeel
scheichuwe (he modded the framework-res.apk)
...
sources:
https://github.com/DerTeufel
Click to expand...
Click to collapse
sorry,differences between the two files are only led and bln?and never undertsnad if deep idle is enabled on stock kernel of pawtip,beacuse my battery life it's ok..
Please read what you quoted. All answers are there.
Specifically:
- Ezekeel's Deep Idle V2 (you have to flash the attatched modded framework-res.apk, to make this fully working, because ICS is preventing Bluetooth to really shut down).
Please READ before posting.
That's a nice kernel. Deep sleep 100% wow!!...great job, mate.
Very, very good..
my wifi dosnt work, the on and off button just keeps flashing on and off constantly, tried flashing several times, even clean wipe and no luck, i also get a random offset every time i install teamhacksung ics, the offset is always different
Funkstar De Luxe said:
Getting a lot of soft resets. Screen goes black, I'm kicked back to lock screen, and everything slowly gets loaded back into RAM.
Everything standard, no tweak, deep sleep activated (and modded framework flashed).
Click to expand...
Click to collapse
Maybe you should wipe caches. I released the kernel 2 days ago in German forum, for stability testing, and no one reported this before
@silitek: this is a bug of CPU spy, due to liveoc. I have to fix this in the next version.
Sent from my I9000 running Android 4.03
Funkstar De Luxe said:
Please read what you quoted. All answers are there.
Specifically:
- Ezekeel's Deep Idle V2 (you have to flash the attatched modded framework-res.apk, to make this fully working, because ICS is preventing Bluetooth to really shut down).
Please READ before posting.
Click to expand...
Click to collapse
I mean,without flash deep idle framework,kernel work like pawtip one for battery?
thiskar said:
my wifi dosnt work, the on and off button just keeps flashing on and off constantly, tried flashing several times, even clean wipe and no luck, i also get a random offset every time i install teamhacksung ics, the offset is always different
Click to expand...
Click to collapse
The random offset is a new google security feature. Nothing to worry about. It SHOULD be different each time, 'cos it's random innit...
This kernel is based on teamhacksung's kernel, with updated Linux base to 3.0.42
This kernel is working with every ICS based Rom
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
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
Download link and changelog can be found here:
http://www.hellybean.com/ics.html
Click to expand...
Click to collapse
Kernels with VC in the name are coming with Voodoo Color
Changelog:
newer changelog can be found here:
http://www.hellybean.com/ics.html
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
further changelog updates only on the website
Known issues:
- virtual buttons in cwm recovery not working
i9000(b) specific:
nothing
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
why new thread?
damn it, I'm on CM7....
and I want to try your kernel!
CM7 seems to be the stables and fastest for now :\
A very good changelog
I'll give a try when it's done.
@orenzah : Did you try CM9 or SlimICS (for example) ?
Because, I think ICS is really stable for daily use.
For the new thread, I think it's because, now it's Devil3 and not Devil2 anymore.
salem94 said:
A very good changelog
I'll give a try when it's done.
@orenzah : Did you try CM9 or SlimICS (for example) ?
Because, I think ICS is really stable for daily use.
For the new thread, I think it's because, now it's Devil3 and not Devil2 anymore.
Click to expand...
Click to collapse
because it is devil3, i wanted to have a third post for infos, and the other already got really big...
what is it zram?
{
"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"
}
you're the best Teufel!
dawidk750i said:
what is it zram?
Click to expand...
Click to collapse
ZRam
Zram is better or swap ?
Scheduler
I just flashed Devil3, thanks. Question though - in devil 2, my scheduler was SIO by default, as listed in the feature list, and I always left it like that. After flashing devil3, it's now CFQ. I haven't run benchmarks yet or anything, but noticed the feature list for Devil3 still says SIO by default. Is the default now changed to CFQ? I'm not sure which is the best scheduler to run - CFQ, SIO or VR? I will benchmark, just wanted to hear recommendation as well.
Tx!
- Goatblaster
wow new thread
thx for the update for the best kernel
---------- Post added at 04:05 PM ---------- Previous post was at 04:02 PM ----------
Goatblaster said:
I just flashed Devil3, thanks. Question though - in devil 2, my scheduler was SIO by default, as listed in the feature list, and I always left it like that. After flashing devil3, it's now CFQ. I haven't run benchmarks yet or anything, but noticed the feature list for Devil3 still says SIO by default. Is the default now changed to CFQ? I'm not sure which is the best scheduler to run - CFQ, SIO or VR? I will benchmark, just wanted to hear recommendation as well.
Tx!
- Goatblaster
Click to expand...
Click to collapse
IMHO sio is the best in real life and benchmarks
there is no need for an updated devil.json file right?
salem94 said:
A very good changelog
I'll give a try when it's done.
@orenzah : Did you try CM9 or SlimICS (for example) ?
Because, I think ICS is really stable for daily use.
For the new thread, I think it's because, now it's Devil3 and not Devil2 anymore.
Click to expand...
Click to collapse
yup, i tried both of them...
slim was faster, but I keep feel something is missing... on smothness and stabling... like temple run is working smother on CM7 with glitch and I can reach such of those freq's of course, another thing it's seems that the battery drain is better on CM7...
if things were changed in the last weeks than maybe I will give another shot
dawidk750i said:
Zram is better or swap ?
Click to expand...
Click to collapse
well its difficult to tell: swap kills the SD card eventually (NAND is not meant to do continuous re-writes) , ZRam uses only RAM (so its safe for SD) but generates more CPU usage...
didicola said:
there is no need for an updated devil.json file right?
Click to expand...
Click to collapse
no need, the last one works perfectly!
Coming from Semaphore I'm not quite sure where to select the appropriate memory config for the 391 MB version (there used to be seperate versions available to download but now it's just one version). Can't find it in neither NS Tools or Recovery.
There's also one big issue I'm facing regarding video playback. 720p video playback with the 378 MB kernel is not working at all, with both MoboPlayer (w/ codec) nor the stock player, and that's an MP4 file at that (so no codec should even be required). Any help on that?
Also, Any over clock of any sort (live OC or not), renders MoboPlayer useless and it crashes in the first couple of seconds when I open a video file and it reboots.
Still, props for developing this kernel as I do find it to be slightly faster than Semaphore.
didicola said:
there is no need for an updated devil.json file right?
Click to expand...
Click to collapse
if u want to use cc u still need it
---------- Post added at 04:59 PM ---------- Previous post was at 04:54 PM ----------
ballsofsteel said:
Coming from Semaphore I'm not quite sure where to select the appropriate memory config for the 391 MB version (there used to be seperate versions available to download but now it's just one version). Can't find it in neither NS Tools or Recovery.
There's also one big issue I'm facing regarding video playback. 720p video playback with the 378 MB kernel is not working at all, with both MoboPlayer (w/ codec) nor the stock player, and that's an MP4 file at that (so no codec should even be required). Any help on that?
Also, Any over clock of any sort (live OC or not), renders MoboPlayer useless and it crashes in the first couple of seconds when I open a video file and it reboots.
Still, props for developing this kernel as I do find it to be slightly faster than Semaphore.
Click to expand...
Click to collapse
bro did u read the OP
- 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)
just go to data/local/devil and creat text file called bigmem then open it if u want Xl ram just type 1 and save file then reboot then u will have 391 ram with patched libs for 720p
new thread?
dhurk said:
new thread?
Click to expand...
Click to collapse
Because now its devil3
Gesendet von meinem GT-I9000 mit Tapatalk 2
dhurk said:
new thread?
Click to expand...
Click to collapse
For heaven's sake, READ THE previous page!
Yes, a new Thread, obviously, & Derteufel already answered why
We don't want a thread full of repeat posts
Hey,
DerTeufel thank you so much for your sense 4.0 kernel!!
Cheers,
[KERNEL][13/09/13][306|188v4][3.xx][AOSP & SENSE4][S2W][GAMING][BATTERY][UV]XM-Kernel
Please read and follow the notes and installation instructions.
They are not there for fun.
{
"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"
}
Features:
Quad 1.5GHz
MPDECISION from showp1984
CPU Hard Cap (Your max freq setting will be respected)
CPU UV Interface
[email protected]
Separate 2D/3D OC Interface
EMC OC Interface
LP Core OC
Audio Min. Freq. Interface
NTFS R/W
GPU UV Interface
Sweep2Wake
DoubleTap2Wake
Fast Charge
Governors: powersave,pmc,conservative,smartmax,ondemand,touchdemand,gaming,interactive,performance
I/O schedulers: noop,sio,row,deadline
Optimized gaming and battery life (1,2,3,4,5)
USB Mass Storage (On most Sense ROMs, you need Lyapota mod pack for this. Except Viper, it works on Viper out of the box.)
MHL (Only on Sense and old AOSP ROMs)
Differences between AOSP and Sense versions:
BLN
Sense: Auto-BLN on every ROM.
AOSP: Support for CM's BLN function.
Touchscreen calibration control
Sense: Auto-switch by switching governors
AOSP: Disabled
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelog:
Beta:
#306
Rebuilt with Linaro 4.8 -O3. Should give more performance with better battery life.
#305
smartmax updates from maxwen.
#304
Disable JRCU, according to maxwen it caused lockups.
#303 cpu clock changes reverted.
Switching governors will no longer update calibration control.
Touch-screen updates(S2W,DT2W) from maxwen.
Variant info added back.
#303
Included maxwen's double-tap to wake (needs sysfs enable), and inner CPU clock changes.
#302
Included maxwen's fixes for freq. locks and LP mode switch with OC.
#301
Default UV removed.
#300
AOSP Audio fixed.
#299
Replaced 640MHz with 620MHz in freq table to be compatible with LP OC.
#298
Imported maxwen's CPU code to hopefully solve freq-lockups for everyone, and a few other things, so:
Added switchable LP OC to 620MHz.(Needs to be enabled through sysfs)
Added sysfs interface to configure audio min. freq.
#296
DriveDroid support.
#295
RIL boost removed again
#294
PMC values updated.
Touchscreen calibration control enabled via sysfs. (Thx maxwen)
On Sense calibration control will change with governor: gaming/interactive->off for best gaming experience, smartmax/pmc->on to prevent call bug.
#293
RIL Boost added back, as it was not the reason of freq. lock.
CPU related things are at #285. (I'm afraid of saying this again, but this should fix the frequency issue)
Smartmax (and so do PMC) updated to latest version.
#291
RIL Boost removed. Hopefully this will prevent frequency lockups.
#290
Frequency weirdness around 475MHz should be fixed now.
#289
Fixed min.freq stuck at 475MHz.
Fixed PMC ideal freq.
#288
Panel back to stock.
Wi-Fi back to stock.
Possible solution for screen not turning on from maxwen.
#286
Panel update reverted.
Suspend updates from maxwen.
#285
Old wi-fi driver.
Smartmax fixes from maxwen.
Previously introduced high freq usage fixed.
#283
Suspend/resume updates from maxwen and trip.
Panel update from trip.
#282
Wi-Fi config updates from kozmikkick.
#281
Added maxwen's fix to prevent high freq. spikes.
#280
Backlight brightness and BLN unlinked again.
#279
Smartmax boost duration fix. (Thx maxwen)
Auto-BLN defaults to much lower button brightness.
Backlight brightness value will limit BLN too.
Wi-Fi fix from kozmikkick. (Thx to trip also)
#274
Reverted video updates, as worse performance reported.
#273
Auto-BLN fixes.
Throttling from 80°C.
Video driver updates from trip.
Sleep/Resume updates from maxwen.
#268
Removed sustain_load from interactive/gaming.
Reduced default readahead size to 128KB.
UMS fixed.
#266
Added back Auto-BLN.
Added interface to configure maximal backlight brightness. (See the bottom of this post) (Requested by Tabtoub)
For UMS you need to disable USB debugging first. This will be fixed in next version.
#262
Rebased on 188v2, with everything important added back. This means (changes from #259):
More performance.
Less heat.
More stability.
LP Core max freq. back to 475MHz.
Stock freq. table. Stock UV table.
SCHED_MC is back. (Group task to cores option in Trickster)
8 step DVFS table.
Old releases:
#259
DVFS Table and so OC Interfaces(GPU/2D/EMC) reduced to 6 steps.
#257
Performance and stability improvements.
Low LP Core freqs reduced for better battery.
DVFS Table and so OC Interfaces(GPU/2D/EMC) reduced to 6 steps.
25MHz removed as it caused too much lag.
Another try to fix touchscreen unresponsiveness.
Auto-BLN won't change your button backlight settings.
#252
UV fixes.
Auto-BLN configurable. (See the bottom of this post)
#250
Fixed min. freq. and some other weird bug, introduced in the last update.
#249
Auto-BLN now only included in Sense build. +Some fixes.
Kernel updated to 3.18 base. (Only the sleep code changed)
Some task scheduler tweaks. (May fix alarm bug)
PMC updated to v7 interactive.
2D & 3D clocks synced by default for better performance.
#247
Initial version of Auto-BLN. (Back Light Notification will work automatically on every ROM.)
#243
CPU Throttling level lowered to 80°C.
Stock ondemand added back, if some ROM defaults to it.
Core<->CPU possible difference raised to stock 300mV. (This can cause less heat, more stability, but slightly less fps)
Another try to fix "can't answer call" bug on sense.
Some driver updates from Nvidia.
Included pabx's headphone tweak for AOSP users.
#241
UV should work for everyone now.
CPU<->Core voltage difference raised to 250mV. (See more about this in the Notes section)
New algorithm written for picking the lowest but still statisfactory core voltage. -> Less heat.
Min. possible CPU voltage reduced to 600mV.
Min. possible Core voltage reduced to 800mV.
Enabling GPU(core) UV will no longer result in unlocking GPU<->Core voltage relation.
Shared clock between emc and mpe from Trip for more bandwith.
Lock mpe to 3D clocks, again for more bandwith.
#235
EMC (Memory Controller) OC Interface. (See the bottom of this post)
Support for Viper UMS.
51MHz added for incompatible ramdisks, and 600MHz removed.
PMC Tuneable.
Another try to fix "can't answer call".
#232
Separate kernel for AOSP and SENSE based ROMs. (Trying to solve the "can't answer call" bug on Sense)
AOSP version def. ramdisk is CM10.1(nightly), Sense def. ramdisk is my modified Ordroid 13.0
Audio min freq. bug fixed.
Wi-Fi driver reverted to 3.14.
#227
CPU and CORE VDD brought closer for more stable performance.
Default RamDisk: Ordroid 13.0. Should be good for any sense ROM. Please try to use this without repacking on sense ROMs, or else you will lose these tweaks. (But I can't promise that it would work for yours too.)
RamDisk changes:
Disabled pnpmgr. -> Fix for facebook cap resetting, and 25MHz resetting to 100Mhz.
Removed some crazy boot time settings, locking to quad-core, or 1-core depending on some things.
Removed defaulting to ondemand.
(I suggest every sense ROM developer to do the same.)
#226
Performance bottleneck fixed.
Added Shan89's Performance May Cry smartmax tweaks as "pmc" governor.
#224
LP core OC'd to 500MHz, thus it can be used more, saving more battery.
Min. freq lowered to 25MHz, save more battery if we don't need any performance.
Freq table set to nice and round frequencies.
Benchmark scores on CPU will be lower. I didn't find the actual reason for that, but in every day usage and gaming wise this won't have any effect.
#217
Optimized memory functions.
Some video driver changes for MHL. (Needs test from sense guys)
#212
AHB and IOMMU driver reverted...it caused worse battery and more heat for me.
#211
A lot of scheduler optimizations and fixes, that help a lot in gaming. (Thx Metallice)
#210
Added Tegra AHB driver. (Thx kozmikkick & Metallice)
Updated IOMMU driver. (Thx kozmikkick)
Lowered 2D max. freq to stock again.
#207
Separate CPU DVFS table per variant is back for stability, with only minor UV.
#206
Performance bottleneck fixed.
A little more voltage on cpu. (~25mV)
Different DVFS Table for Variant 0.
#200
A little UV back on core. (25-50mV depending on clock)
Default Variant 3 freq. table. (So you might not be able to UV that much, and of course clear tuner app data.)
GPU min. clock is 247 again.
Small fixes.
Default ramdisk is CM10.1 Beta 10.
#198 (Still alpha)
Core clocks changed to safer values.
Seems to fix interactive/gaming issue.
#197(Quite much change...it's better to call this alpha version then.)
Interactive and gaming governors seem to quad-lock this to max freq...better not use them.
"Redesigned" DVFS table. Now every HOX will use 1 table(Variant1's) regardless of anything. -> Clear tuning app data
New Wi-Fi driver. (Thx kozmikkick)
Internal Core clock limit disabled(for GPU OC).
Small fixes from upstream.
GPU OC Interface back to 8 clocks.
GPU min. freq is at 267.
Pre-UV on CPU removed.
Pre-UV on Core removed.
Default readahead size is 4096KB.
#192
Previous lag should be fixed.
Added kernel changes for CM B10 BLN. (But repack needed)
#191
Better CPU spinlock handling. (A little faster and less overhead)
Spearate 3D and 2D OC Interface. (See the bottom of the post)
Video drivers is the same as #106.
Gaming governor added.
Interactive tweakable again.
Click to expand...
Click to collapse
Stable:
188v4
Added button_brightness interface.
Added PMC governor.
Added Auto-BLN, but disabled by default.
188v2
--Changes since #188>
AOSP Ramdisk: CM10.1 B10.
Sense Ramdisk: Ordroid 13. Should work for the most sense ROM.
Added gaming governor.
MHL fixed.
Viper UMS fixed.
--<Changes since #188
Better synced the core freqs. Should solve some issues, and even less heat.
Interactive is providing much better gaming now, as we have don't have to avoid heat that much.
Fastcharge doesn't need replug to be activated. (Thx to maxwen)
EMC(memory) ratio changed. (Thx to kozmikkick)
Switched to JRCU.
Boot freq is at 1300MHz. You can change that to lower of higher with your favorite tuner app, preferably Trickster Mod.
Some unnedded high boosts lowered to be more battery friendly.
Some cherry-picks from maxwen.
GPU OC and GPU UV interface added. (These are only for experts and brave warriors. For more information see the bottom of this post).
Please from now on use Trickster Mod to change anything. (Don't forget to accept the changes in the top right corner!)
Video drivers close to stock. MHL should work on stock, and in older AOSP ROMs(with ICS blobs).
Smartdimmer disabled by default. For enabling it, see the bottom of this post.
UMS works on stock ROMs with lyapota's modpack. (Thanks for n3o for the kernel part, and Zulake for testing)
Voltage control interface changes. (more info, even more info)
Audio min. freq is at 204MHz
Implemented proper voltage control. You NEED to clear the data of the apps that can change voltages to let them reset the default values!
S2W register threshold increased to prevent loss of touch on buttons.
Disabled Gentle Fair Sleepers
Added arm topology awareness patch and enabled arch power management
GPU min. freq. lowered to 247MHz for stability.
LED backlight fix. (Faster wake, thx to Thoemy)
Added TouchDemand governor per request.
ROW optimizations. Should be even smoother.
Switch to fget_light in do_fsync() -> Less overhead in fsync -> More battery, more speed.
Added ROW I/O scheduler and set as default.
Added smartdimmer from trip.
Disabled optimized RWSEM algorithm. (Possible cause of freezes)
Variant info on sysfs introduced. (/sys/kernel/debug/t3_variant, cpu_process_id is your variant. Reworked from faux's code.)
Various fixes/optimizations, mostly from faux's n4 kernel. (more info on github)
Little longer boost for smartmax.
Global input boost cap from maxwen.
Driver updates & other kernel fixes. (See github for more information)
USB Mass storage fix.
CIFS Support.
SIO added.
Better compression. (Smaller kernel size)
#106
GPU OC to 520MHz.
Driver updates from Nvidia.
Smartmax grovernor from maxwen. (It should be better for battery life, now this is the default)
Lower LP voltage from TripNRaVeR.
Fix LP lockup.
Fix for errors when trying to change governors on some ROMs.
SW AES optimized. (~30-50% faster)
HW Accelerated AES enabled.
Frequency lockup fixed.
Some other fixes from n3o and lord.
Replaced stock hotplug algorithm with MPDECISION. (Thx to showp1984 for the code).
Some fixes from maxwen.
Proper Hard Cap. Now it will be kept during suspend/resume.
Voltage Control.
Introducing CPU Hard Cap - Restoring after suspend is not working yet. For that use SetCPU "On Screen Unlock" profile.
Updated Touchscreen driver(Now should work for everyone)
Voltage Control
Volume wake
USB Fast charge
A few optimization for better gaming.
CPU tuning works
Fix for multitouch that S2W broke
Added Sweep2Wake
Working CPU hotplug and everything else
GCC optimizations (Compiled with linaro 4.7)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Notes/Issues/User guide:
The absolute stable version is 188v4, please consider anything above as a beta.
Use smartmax for daily/battery and gaming for performance/gaming.
If you want extra battery, and you are ready to give up smoothness for it, then use "pmc" governor, more info here.
If you want even more performance then you can use interactive or ondemand with gaming boost.
If you have hiccups in music, use interactive there too.
If too much heat generated during games, cap your CPU to 1-1.2GHz, the performance difference will be minimal, also a safe undervolt (25-50mV) should help a lot.
About UV: CPU VDD should be close to Core VDD, by default there is a 100-300mV(depending on kernel) lock between them. Core minimal voltage is 950 at default. This means even if you set 100mV to any freq, it won't go below 650-850. And this also means, if you UV your GPU, while you have CPU UV, CPU UV that seemed stable can become unstable.
So if you plan on UVing GPU, you should UV that first, and CPU only after that.
I'm not responsible for any damage, this kernel might cause.
Thanks to pabx, maxwen, n3ocort3x, tbalden, kozmikkick, showp1984,TripNRaVeR and everyone who contributed to this kernel.
There might be a 1sec delay after wake one sense roms, before the screen processes touches. It's a S2W thing, if you don't want it, disable S2W.(See below)
Here is an awesome guide about how to get the maximum out of your phone, both in battery and performance
Auto-BLN Issues:
Green led might stuck after removing from charger if there is an unseen notification. Just check the notification to solve.
Green led might not come up after a finished charge.
BLN will not work while charging the phone.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
AOSP Installation:
Repack!
Install modules from recovery (Install the zip)
Wipe dalvik cache. Yes, it's important, the versions could have some binary level differencies (from different compiler options) which can lead to unknown behaviour with old dalvik code.
Erase fastboot cache
Flash kernel image with fastboot
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Sense Installation:
Install modules from recovery (Install the zip)
Wipe dalvik cache. Yes, it's important, the versions could have some binary level differencies (from different compiler options) which can lead to unknown behaviour with old dalvik code.
Erase fastboot cache
Flash kernel image with fastboot
If you have problems with some functions not working on your ROM, then repack. Otherwise it's not needed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Download:
Latest beta releases for Sense5/CM11
Beta releases / Mirror / Mirror #2
Stable releases:
188v4 AOSP
188v4 Sense
188v2 AOSP
188v2 Sense
#106
Repacks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Configuring kernel parameters:
S2W Configs:
Turn off:
Code:
echo "0" > /sys/android_touch/sweep2wake
Or you can download "Sweep2Wake-Widget" from Google Play.
Button panel locks to s2w after this distance:
Code:
/sys/android_touch/s2w_register_threshold
Screen turns on/off after this distance:
Code:
/sys/android_touch/s2w_min_distance
Direction independent(1 - Yes, 0 - No):
Code:
/sys/android_touch/s2w_allow_stroke
DoubleTap2Wake Configs:
Turn on:
Code:
echo "1" > /sys/android_touch/s2w_allow_double_tap
Activate fast charge:
Code:
echo '1' > /sys/devices/platform/htc_battery/fast_charge
Enable smartdimmer:
Code:
echo "1" > /sys/devices/tegradc.0/smartdimmer/enable
To get your variant:
Code:
cat /sys/kernel/debug/t3_variant
(Or see it in a root explorer)
cpu_process_id is your variant.
3D Tuning:
If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '520 520 520 520 492 484 380 247' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
If you want to set them at boot, use an init script. Here is one. Just copy to /system/etc/init.d and set the permissions to executable by everyone with a root explorer. (Thx to Byrana)
Here is a flashable script that will work on newer kernels too for everyone. It also enables fast_charge. (Thx again Byrana)
2D Tuning:
If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '520 520 520 520 492 484 380 247' > /sys/devices/system/cpu/cpu0/cpufreq/two_d_oc
You should NOT OC this higher than 3D.
EMC Tuning:
If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '667 667 667 667 408 408 408 408' > /sys/devices/system/cpu/cpu0/cpufreq/emc_oc
If you want to OC let's say to 800MHz:
Code:
echo '800 800 800 800 667 667 408 408' > /sys/devices/system/cpu/cpu0/cpufreq/emc_oc
Auto-BLN Control:
Interface:
/sys/class/leds/button-backlight/auto_bln
Values:
0: BLN OFF/Green led ON
1: BLN ON/Green led ON
2: BLN ON/Green led OFF
Example:
Turn off Auto-BLN:
Code:
echo '0' > /sys/class/leds/button-backlight/auto_bln
The changes will apply from the next notification.
Backlight button brightness:
Interface:
/sys/class/leds/button-backlight/button_brightness
Values:
0-255: 0 is off, 255 is the maximum possible.
Example:
Code:
echo '50' > /sys/class/leds/button-backlight/button_brightness
The changes will apply from the next backlight turn on.
GPU Voltage control:
If you want to enable this you should write '1' to /sys/devices/system/cpu/cpu0/cpufreq/gpu_voltage.
In command line that is:
Code:
echo '1' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_voltage
After that you need to restart your voltage control app (Trickster Mod).
Now you will see the GPU frequencies multipled by 1000 to separate them from the CPU frequencies. So you will see 520000MHz, etc.
Be advised that there are a really few HOX's that can handle more UV on Core, than the preset 50.
Also incrasing your Core voltage over 1300mV is NOT ADVISED AT ALL. Almost everything uses this voltage on your motherboard.
If you want to enable the values at boot, you need an init script that enables it, so later Trickster mod or anything can set them.
LP OC:
Interface:
/sys/module/cpu_tegra/parameters/enable_lp_oc
Values:
0: LP OC OFF
1: LP OC to 620MHz
Example:
Turn on LP OC:
Code:
echo '1' > /sys/module/cpu_tegra/parameters/enable_lp_oc
Audio Min. Freq.:
Interface:
/sys/module/snd_soc_tlv320aic3008/parameters/audio_min_freq
Example:
Change audio min. freq. to 204MHz:
Code:
echo 204000 > /sys/module/snd_soc_tlv320aic3008/parameters/audio_min_freq
Save settings:
If you want any of the above settings saved, you can use iba21's recovery package.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Battery life:
Source:
GitHUB
BitBucket
DONATORS
(Thank you)
fantomster,evo1rs,71nh0,dsonex,Lextermina(3),Byrana,97_3,glen.ricky,Whiskey103,damanrico,RiceDie(3)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
github link is broken
BTW: take a look at my fixes in cpufreq.c
At least governor switching for all cpus is fixed there
REPACKS(Click)
If your ROM is not in the list, then you should repack yourself, or wait until there is a repacked version out.
You can use this tool to repack the kernel: [TOOL]One X One Click v1.9 then please upload it to d-h.st:
username: xmrepacks
password: xmrepacks
For file name use the following: xm_kernel_<num>_<rom>.img or xm_kernel_<num>_<rom>.zip if you include the modules, for example: xm_kernel_95_viper336.img
And for description use the following: XM-Kernel #<num> for <rom>, for example: XM-Kernel #95 for Viper 3.3.6
Tick to Make it public.
I'm trusting you, that you won't upload anything else than repacked XM-kernels. Please don't fail my expectations.
There is an alternative link for repacked boot images, thanks to Whiskey103: http://www.whiskey103.nl/Onex_kernels/index.php?dir=xm/Repacked/
TODO:
Release the next stable version.
Benchmark results (Antutu only for now)
#111(beta) With CyanogenMod 10.1 beta3
TO TELL OTHERS I DIDNT GET HIRE SCORE IN LATER RELEASES.I DONT KNOW WHY.
Xmister said:
As I see, it depends on faux's OC code. I don't want to implement that yet.
Click to expand...
Click to collapse
The fix for governor switching has actually nothing to do with OC
So you can just use that without any OC - which we dont really need on HOX+
The only OC I have is enabling of 4x1.7Ghz
maxwen said:
The fix for governor switching has actually nothing to do with OC
So you can just use that without any OC - which we dont really need on HOX+
The only OC I have is enabling of 4x1.7Ghz
Click to expand...
Click to collapse
I will look into it tomorrow then. Thanks.
You did good job.A little suggestion. Show the version and features on title.I even didn't know you update to #11even#12until get in here^_^
Re: [KERNEL][07/02/13][3.1.10][AOSP]XM-Kernel
Anyone tested this on CM10.1 without repack?
Sent from my Venom Infected One X
nice to see another one here welcome to our world :highfive:
on icj 1.7 wlan is on but not connect to my router
Re: [KERNEL][07/02/13][3.1.10][AOSP]XM-Kernel
Wow! Another kernel, another good day Cheers dev!
Sent from my One X running Blade v4.7.0. At a mere 217 MB, with tons of AROMA Mods and tweaks, this, is what you want.
rafkin said:
on icj 1.7 wlan is on but not connect to my router
Click to expand...
Click to collapse
Hi,
did you check your mac address ? and the rules on your router ?
1.6.9/cm10.1/aosp all fine without WiFi issue.Maybe it's ROM problem.
tmotard said:
Hi,
did you check your mac address ? and the rules on your router ?
Click to expand...
Click to collapse
no mac filter or other secruity only wpa2 protect
Re: [KERNEL][07/02/13][3.1.10][AOSP]XM-Kernel
JohnYang1997 said:
1.6.9/cm10.1/aosp all fine without WiFi issue.Maybe it's ROM problem.
Click to expand...
Click to collapse
Should we repack n use on ICJ or just flash modules n kernel
sent on earth from 1x
Dont work on cm.And no need to repack to flash on 1.6.9/AOSP(tested myself)
You f#cking cool awesome
Re: [KERNEL][#18][07/02/13][3.1.10][AOSP]XM-Kernel
So I come after 4 hours and see a 18 ..super fast work man. ..
Sent from my HTC One X using xda app-developers app
Re: [KERNEL][#18][07/02/13][3.1.10][AOSP][S2W][520GPU]XM-Kernel
Why is there no activity on this thread !! The kernel is holding up awesome till now !! #12 repacked with tbaldens 3.1xkernel a3 with cm10.1 everything works like a charm !! Now gonna flash #18 ...please don't hold back from trying this kernel !! Its awesome !
Sent from my HTC One X using xda app-developers app
{
"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"
}
+Electroactive Kernel
FEATURES
Overclocking/underclocking options
Electroactive default CPU governor with dual-phase frequency, boost_sampling factor, and boostpulse
Many other popular CPU governors including UberDemand(Cl3Kener), Badass(Dennis Rassman), Impulse(neobuddy89), and much more.
MSM MP-Decision Hotplug
Full KCAL support
Bleeding-edge CAF updates
Full Gamma reverse engineering support
Synapse + script & runparts built-in
Optional improved Cpu optimization level 'l2' and bus overclocking
Power Aware CPU Scheduling
Partial-Resume
Full voltage control
Wake gestures
Kernel Samepage Merging
CPU Deferred Timers
Msm-Thermal-X thermal driver
Optional sweep2wake and doubletap2wake
Optional USB fastcharge
Optional backlight dimmer
Kernel compressed with LZ4-r127, GZIP for faster boot times
Several I/O controls with ROW as default
Optional cooler color
Advanced color and gamma control
Power-efficient workqueues ported from 3.18 mainstream - improves power efficiency
3.4.x updates and fixes from upstream
Build with optimized Toolchains
Use Android device as USB keyboard/mouse
Full -O3 & graphite and -pthread support
Optional max screen off frequency at 1190 MHz
Charge light support
Optional disable fsync
Enhanced TCP with wifi and network enhancements
Optimized AES, SHA1, and RWSEM
OTG flash drive support FAT32
NTFS r/w, CIFS, and exFAT support
Fastest ZRam backported from Linux 3.18 kernel
Enhanced LMK
Tuned virtual memory
MultiROM support
init.d support
/dev/frandom support
DriveDroid compatible
electroactive.conf support
F2FS support
Linaro enhancements
Thermal throttling control: elexcool, extracool, and stockcool options
Compatible with TricksterMOD, Device Control, Kernel Tweaker, Franco Display Control and FauxSound Control, and Synapse Kernel manager
Vibration strength tunable
FSTRIM built-in kernel
NOTES & INFORMATION
Electroactive governor
The Electroactive CPU governor has been created to get some of the best balances between battery life and performance that you will see on a device. It is a hybrid class governor, using a unique way to merge the best of both interactive and ondemand. It includes some extra additions and enhancements to be more battery saving than interactive governor and some boost tunes and additions that allow better power management and performance in games as well as better power saving when in normal use. CPU boost, graphics boost, fast_start deep_sleep and detection features are built in as well as 300 MHz clock speed in suspend. This governor performs extremely well in games, normal use, battery performance, and just about everything. Some tunables available in the governor:
boostpulse: Immediately boost speed of all CPUs to hispeed_freq for min_sample_time, after which speeds are allowed to drop below hispeed_freq according to load as usual.
boosted_sampling_down_factor: This custom made parameter's set default setting will give several 0.4 second bursts of full throttle CPU to programs. It's about the time that user interface has to produce some meaningful response to your input so to feel smooth, especially while gaming. Besides better responsiveness, this setting will also give better overall speed to many programs which often interchange high CPU demand with IO waits and then suffer because the CPU governor too eagerly throttled down the frequency during those waits.
default_freq_boost_time: this is the default time that the CPU will spend in 'boost mode' before scaling down to normal frequencies, such as when in normal use.
ui_sampling_rate: when you touch the screen, the sampling rate changes temporarily to whatever you set it to.
down_differential: After spending sampling_down_factor*sampling_rate micro seconds at maximum frequency on high load, governor samples the load again to calculate an approximate targeted frequency to scale-down-to which should not trigger up_threshold in the next sample. (Triggering up threshold may cause jumping to max frequency again). Max_load_freq is checked against (up_threshold - down_differential) * current frequency. If found to be smaller, CPU is scaled down to a target frequency as described above. Down_differential also act as the factor to prevent aggressive scale down. Higher value of down_differential corresponds to delayed scaling down.
two_phase_frequency: Two-phase is a battery saving technique where even during max cpu frequencies, there are still gaps of inactivity so instead of running @ max frequency all the time, the two phase will alternate between busy/idle phase. Accepts four frequency values separated by comma, for cores 0, 1, 2, and 3.
input_event_min_freq: takes four values separated by comma. These are the input boost frequencies for cores 0, 1, 2, and 3.
input_event_timeout: this is the length of time in milliseconds that the input boost will be active (default 500). Setting this to 0 disables input boosting.
powersave_bias: this parameter takes a value between 0 to 1000. It defines the percentage (times 10) value of the target frequency that will be shaved off of the target. For example, when set to 100 -- 10%, when ondemand governor would have targeted 1000 MHz, it will target 1000 MHz - (10% of 1000 MHz) = 900 MHz instead. This is set to 0 (disabled) by default. When AMD frequency sensitivity powersave bias driver -- drivers/cpufreq/amd_freq_sensitivity.c is loaded, this parameter defines the workload frequency sensitivity threshold in which a lower frequency is chosen instead of ondemand governor's original target. The frequency sensitivity is a hardware reported in a value between 0 to 100% that tells software how the performance of the workload running on a CPU will change when frequency changes.
ignore_nice_load: this parameter takes a value of '0' or '1'. When set to '0' (default), all processes are counted towards the 'cpu utilisation' value. When it's set to '1', the processes that are run with a 'nice' value will not count aka ignored in the overall usage calculation. This is useful if you are running a CPU intensive calculation 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.
freq_for_responsiveness: up threshold considered for sampling load is up_threshold_at_min_freq. Also during the part where CPU is at maximum load frequency, governor need to find the optimal frequency as the next frequency - which should not trigger up_threshold in the next sampling. When such a frequency_next is found to be a) less than freq_for_responsiveness b) will not trigger down_threshold in the next sample, then the optimal frequency is set to freq_for_responsiveness.
Electroactive Configuration File
Kernel defaults are used to build a configuration file, based off of elementalx's original config file. The config file is found at /etc/electroactive.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere).
If settings are not sticking:
Make sure you have busybox installed correctly and updated to the latest version
Make sure the file permissions for /sbin/electroactive.sh are set to execute.
Check to see if any scripts or apps are interfering with your settings.
To execute the script file:
Install Terminal Emulator from the Play Store if you haven't already and open it.
In the emulator type: "su" and press enter
Type: "cd sbin" and press enter
Type: "sh electroactive.sh" and press enter
The values should now be applied, with no need to reboot
As always, you can also edit the values using the Synapse app or reboot to apply.
fsync
fsync can be disabled if you're looking for the last ounce of performance. If you disable it however there is a slight risk of data loss if your phone shuts off unexpectedly before the filesystems are synced.
Max screen off frequency
The default max screen off frequency is 1190MHz, which is a good balance between limiting the voltage/frequency and the time required to complete tasks while the screen is off. This can be changed manually at /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
NTFS and exFAT support
This is for anyone who wants to use OTG cable to connect a USB stick or portable hard-drive formatted with Microsoft's NTFS or exFAT filesystems. (Useful for installing and transporting files from your device) You will need Stickmount or a similar app
F2FS support
F2FS support is built into the kernel. No need to flash any other support patches before installing Electroactive.
Color preset
Some users complain that the Nexus 5 screen has too 'warm' colors, so there are two color presets: stock and slightly cooler. You can edit /etc/electroactive.conf to change the setting on boot.
/sys/module/mdss_dsi/parameters/color_preset
0 = stock color
1 = slightly cooler color
Sweep2wake (flar2)
Sweep2wake allows you to turn on your phone by swiping your finger across the screen. There are four sweep actions that will work
Gesture........Value
Sweep right......1
Sweep left........2
Sweep up.........4
Sweep down....8
Add up the values for each gesture you want to enable and put the total in /sys/android_touch/sweep2wake. For example, to enable all gestures, the value is 15 (1+2+4+8). To enable sweep right, sweep left and sweep up, the value is 7 (1+2+4)
/sys/android_touch/sweep2wake
Doubletap2wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping anywhere on the screen. This causes significant battery drain, so you choose at your own choice if you want it enabled or not. You can edit /etc/electroactive.conf to change the setting on boot.
/sys/android_touch/doubletap2wake
0 = disabled
1 = enabled (bottom of screen only)
2 = enabled (full screen)
Sweep2Sleep
Sweep2Sleep allows you to put the device to sleep by sweeping your finger across the navigation bar area. You can choose different directions to swipe. Unlike Sweep2wake, this does not cause any battery drain. You can edit /etc/electroactive.conf to change the setting on boot.
/sys/android_touch/sweep2sleep
0 = disabled
1 = sweep right
2 = sweep left
3 = sweep left or right
Backlight dimmer
Backlight dimmer allows you to adjust the LCD screen brightness lower than is possible with stock. You can edit /etc/electroactive.conf to change the setting on boot.
/sys/module/lm3630_bl/parameters/backlight_dimmer
0 = disabled
1 = enabled
USB fast-charge
This will allow you to charge at a faster rate when connected to a USB port. The default limit for USB ports is 500ma, this increases it to 900ma. This only works on laptops/desktops/any computer but not the phone's charger. You can edit /etc/electroactive.conf to change the setting on boot.
MSM Thermal-X Driver Options
MSM Thermal-X will throttle your cpu speed to keep it cool and unleash it if the cpu has cooled down enough. The input-event boost will temporarily boost the cpu frequency to prevent any lag while not hogging up battery.
Check /sys/kernel/msm_thermal/conf/ for the thermal configuration
allowed_max_high = highest threshold (phase 3)
allowed_max_low = remove the throttling if we cooled down to this (clr_thrshold)
allowed_max_freq = max frequency if throttled (limit)
[...]mid[...] = same as above, just for phase 2
[...]low[...] = Lowest threshold (phase 1)
check_interval_ms = how often shall we check? (sampling rate)
shutdown_temp = if we reach this shut down the device!
MSM MP-Decision Hotplug Options
MP-Decision Enabled
Enables/Disables the hotplug. On disabled the backup cpu-control will be stock Qualcomm mp_decision
# 1 for enabled
# 0 for disabled
echo "1" > /sys/kernel/msm_mpdecision/conf/enabled
Touch Boost
Touch-boost will temporarily raise cpu_min to a frequency determined by an mp_decision algorithm.
# 1 for enabled
# 0 for disabled
echo "1" > /sys/kernel/msm_mpdecision/conf/boost_enabled
Idle Frequency
If the first core is below this frequency, then don't plug the other cores.
echo "300000" > /sys/kernel/msm_mpdecision/conf/idle_freq
EcoMode
Ecomode tries to limit cores to just 2 unless there is a very heavy workload in which cores 3 and 4 are temporarily brought online and won't kick on until both CPUs are maxed out then it will allow for all 4 cores to come temporarily online.
echo "99" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_4
StrictMode
Strict mode functions so only 1 CPU tries to be online at first before bringing up cpu1 and cpu2 online.
echo "85" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_2
echo "99" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_4
Max CPUs online
Max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore).
echo "4" > /sys/kernel/msm_mpdecision/conf/max_cpus
Min CPUs online
Min cpus to be online, cannot be < 1.
echo "1" > /sys/kernel/msm_mpdecision/conf/min_cpus
Screen-off Single core
If the screen is off, don't plug in cpu1/2/3. Additionally: Unplug all cpus except cpu0 when screen is turned off.
echo "1" > /sys/kernel/msm_mpdecision/conf/scroff_single_core
Pause
If something else plugs in the cpu, i.e. CPU-Governor or Thermal, fall asleep for <#>ms.
echo "10000" > /sys/kernel/msm_mpdecision/conf/pause
StartDelay
Time until mpdecision starts to work.
echo "20000" > /sys/kernel/msm_mpdecision/conf/startdelay
Delay
Time between checks.
echo "130" > /sys/kernel/msm_mpdecision/conf/delay
Hot plug thresholds
This formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
Since we can't unplug cpu0 this is '0'.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
echo "#" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_X
echo "#" > /sys/kernel/msm_mpdecision/conf/twts_threshold_X
etc...
Some values are:
NwNs_Threshold: 12, 0, 25, 20, 32, 28, 0, 35
TwTs_Threshold: 140, 0, 140, 190, 140, 190, 0, 190
Where the position and function of the number equals the result of the above explained formula (all times are in ms).
INSTALLATION
If you come from another kernel, dirty-flash your ROM first without wiping any data
If you are an F2FS user, flash the F2FS support patch found below
Flash Electroactive kernel in recovery
Reboot
*F2FS users:
THIS KERNEL USES YOUR RAMDISK, it will just modify it on the fly while flashing. These changes are so to not create any incompatibilities with ROMs or other kernels. Some things to consider when using F2FS:
Use F2FS in only r/w partitions (/data and /cache).
F2FS in /system does not make any difference and requires selinux to be set to permissive, and Electroactive kernel is enforcing by default, although you can change this in the .config file found in /etc/electroactive.conf, but is still not recommended.
DOWNLOADS
Android M Preview/2
Electroactive-N5-3.10-M
Android 5.1/5.1.1
Electroactive-N5-2.50
Please consider a donation to support the Electroactive Kernel Project, and support for more devices.
Donors Hall of Fame
Send me a PM or email me if I didn't add you after you donated and I'll add you to the list
- danmaman
- Chirag7
- Zidane23
XDA:DevDB Information
Electroactive Kernel, Kernel for the Google Nexus 5
Contributors
Electrex
Source Code: https://github.com/Electrex/Electroactive-N5
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 2.50/3.10
Stable Release Date: 2015-08-09
Current Beta Version: 2.52
Beta Release Date: 2015-09-27
Created 2015-04-10
Last Updated 2015-09-27
Changelog:
August 9, 2015 - Electroactive-N5-2.50/3.10-M
-MSM-Thermal-X input/output control, 3-phase, inputboost
-MSM MP-Decision Hotplug
-Electroactive CPU Governor Revision 2
-Set FIOPS default io scheduler
-Add Zen io scheduler
July 21, 2015 - Electroactive-N5-2.45/3.05-M
-MSM-Thermal-X
-KSM-Kernel Samepage Merging
-CPU Deferred-Timers
-Power Efficient Workqueues
-Cortex-A15 target architecture overhauls
-Merge Android M Prev2
-Linux 3.4.108
-Resolve some memory leak issues, more like a band-aid until Google gets their game up
-Fix performance regression in vfs
-push readahead value to 512 kb
-Back to ROW i/o scheduler w/change of params
-Revert PM-Suspend Freeze to prevent processes from running when device is idle.
-Add suspend_again mechanism to Partial Resume
-linaro-4.9.4 toolchain
-Remove android logger
-Use Android device as USB keyboard/mouse
June 29, 2015 - Electroactive-N5-2.40/3.00-M
-CPU Power Aware Scheduling
-Partial-Resume Framework
-Merged android M sources
-Fix cpu sticking issue
-Introduce PM Suspend Freeze
-Remove compiler warnings to prevent any issues in installation
-Re-add fsync control
-Add GPU sysfs reporting in pwrctrl
-Add 8974 support for enabling GPU GDHS
-Use new global screen-off detection variable
-Electroactive cpu governor: Introduce powersave-bias
-Greatly improve memory access performance
-Skip sensor_ind wakeup source activation via sysfs to prevent wakelocks
June 2, 2015 - Electroactive-N5-2.10
-Major Update. Getting close to second major release.
-More chrome fixes, should be almost completely gone. General UI speed-up and smoothness optimizations.
-Memory leak issue fixes, a bit better memory efficiency.
-Fix issues with any previously installed kernel files not being removed/reappearing after installation.
-Battery life issues with wake-locks and screen power consumption are fixed, GPU and CPU drivers updated.
-2 different versions of kernel: TC-DEF and TC-TEST. Only differences are the compiler toolchains and GCC. Try both and report which is better. TC-DEF uses the default old style build compiler and TC-TEST uses the new test compiler.
-Update advanced color control
-Kernel sources updated back to 3.4.107 from 3.4.0, some backports from Linux 3.18+ kernel sources.
-F2FS Support Built-In to ramdisk. No need to flash any F2FS support patch before installing kernel.
-More focus on optimization.
May 19, 2015 - Electroactive-N5-2.00
-Kernel Rebased
-Removed unneeded/unwanted commits and left all the good stuff in new base
-Add deeper incremental overclocking up to 2.95 GHz. Still boots at stock frequency
-Min CPU frequency down to 96 MHz, options for 192 and 249 MHz. Still boots at stock frequency
-Built with -O3 CFLAGS Makefile variables for extreme optimization
-Add MultiROM support
-exFAT support built-in to kernel rather than a module
-Add some speed and stability updates
-Add additional thermal driver settings
May 14, 2015 - Electroactive-N5-1.56
-Add sanity check to avoid unregistering the driver twice (therefore preventing kernel panic)
-Add optimized SHA-256/224
-Update kernel sources to linux 3.4.107
-Move VFP init to an earlier boot stage
-CAF sound codec driver
-Fix voltage tables and scripts
-Specifically modified PVS voltage tables per each unique device. Stock voltages now set
differently depending on your CPU binning.
-Update msm-kernel sources to android-5.1.1_r0.10
-Update Documentation & arch to 3.4.104
-Fix SMD packet sync loss issue
-lmk tune up
-Fix kernel script errors
-Chrome freeze issues gone
-Overclocking up to 2.9 GHz (experimental)
-Min CPU frequency down to 96 MHz
-Can have different frequencies for each CPU core
-Ramdisk updated to be more compatible and better performance on more ROMs
-FSTRIM now built-in: trims /data and /cache to discard any unused data blocks on boot, no more lag (only f2fs)
April 30, 2015 - Electroactive-N5-1.47
-optimize memory allocation in check_partition()
-Fix changes not applying on boot
-Add electroactive.sh script support
-Thermal throttling set to Cooler by default for less heat
April 25, 2015 - Electroactive-N5-1.45
-Add Optimax governor and Electrodemand
-NEW GOVERNOR: Electroactive (Hybrid: Interactive + Ondemand) with two-phase frequency and over 20 tunables
-Fix kernel, governor, and cpu tables. More .config functionality
-Stability improvements
-Synapse integration built-in
April 17, 2015 - Electroactive-N5-1.40
-More options in the .config file. Customize ALL hotplug settings
-Fix hotplug compatibility issues
-Update clock vote for improved performance
-Removed some unneeded governors
-Stability improvements
-First major release
April 11, 2015 - Electroactive-N5-1.35
-Add new improved default hotplug: Intelli_Plug, (much more added features and functionality)
-Update kernel sources to 3.4.106 from Kernel.org
-O3 graphite and -pthread optimizations/improvements
-LZ4 compression for much faster boot times
April 9, 2015 - Electroactive-N5-1.30
-Initial release
-Use UBERTC Compiler for kernel
-Add fixed PCI i/o mapping
Just hit the thanks button, he doesn't bite your finger. Try it.
Thanks!
Feature Requests
If anyone wants any feature requests, please post them in the feature requests tab at the top of the page. I will try my best to add the most features that I can without sacrificing stability or performance.
Seems stable und fast so far, pretty good work ... A few governors for my taste to much, but the default one is a beast
Bricked Cataclysm
---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------
I really like ElementalX as a base
Bricked Cataclysm
Notechis said:
Seems stable und fast so far, pretty good work ... A few governors for my taste to much, but the default one is a beast
Bricked Cataclysm
Click to expand...
Click to collapse
Thanks,
If you have any features you want me to add to my kernel them feel free to ask.
Everything is fine, unleashed kernel uses alucard hotplug, this would be an unique feature
Bricked Cataclysm
Notechis said:
Everything is fine, unleashed kernel uses alucard hotplug, this would be an unique feature
Bricked Cataclysm
Click to expand...
Click to collapse
Uses Intelli_Plug much more tunables and configurations
Electrex said:
For now I am using the msm_sleeper hotplug. In the future there should be a new one.
Click to expand...
Click to collapse
Good to know that msm_sleeper is a hotplug... I think u missing the all thing.
Hi Electrex,
1st thanks for your awesome work!
2nd your kernel is ukm compatible? (or trickster or elementalx app?)
Tia!
Trickster works fine but due to the config file you did not need such apps
Bricked Cataclysm
idkidk said:
Hi Electrex,
1st thanks for your awesome work!
2nd your kernel is ukm compatible? (or trickster or elementalx app?)
Tia!
Click to expand...
Click to collapse
Yes, in the description, I posted all of the compatible kernel managers. I'll put them here too, as my OP is a bit cluttered:
Compatible with ElementalX Kernel app, TricksterMOD, Device Control, Kernel Tweaker, Franco Display Control, FauxSound Control, and Synapse Kernel manager.
You can also edit the .config file in /etc folder without an app to change kernel settings.
Electrex said:
Yes, in the description, I posted all of the compatible kernel managers. I'll put them here too, as my OP is a bit cluttered:
Compatible with ElementalX Kernel app, TricksterMOD, Device Control, Kernel Tweaker, Franco Display Control, FauxSound Control, and Synapse Kernel manager
Click to expand...
Click to collapse
My apologies. I see, thanks!
Kudos!
Hello,
This is a really nice piece of work, the responsiveness is excellent and battery life is great! Using stock settings. Has all the features i need.
Thank you for sharing your work with us!
Ok so does it work on cm 12 based roms? Blisspop and all?
i'm using "Semaphore Manager" is that okay??
maybe i'm missing on features.
kingserpent said:
Ok so does it work on cm 12 based roms? Blisspop and all?
Click to expand...
Click to collapse
Yes, it works on any 5.1 Lollipop ROM and ONLY 5.1 lollipop versions. Do not use this build for earlier versions of lollipop.
Your kernel is blazing fast and rock solid the last days. Cool project
Bricked Cataclysm
I agree. Great work!
If anybody is interested, I build my first own kernel for Nubia Z17 Lite (NX591J). It is based on stock Nubia kernel published HERE and compiled using Linaro toolchain (from verison 0.1.62 up).
It is compatible with Global (Geekbuying) stock ROM and Chinese stock ROM and NubiaPixel. It is not compatible with LineageOS.
I added multiple features into the kernel, but settings (like governor tunables) are mostly stock, so it is up to you to customize them to your needs using tools like Kernel Adiutor.
FEATURES:
based on stock NX591J kernel
built using Linaro 6.4 toolchain (stock was GNU 4.9) - improved speed and smoothness
added governors (blu-active, interactivex, conservative)
added schedulers (zen, fiops, sioplus)
disabled MSM_PERFORMANCE (stock hotplugging driver)
added 3rd party CPU hotplug drivers (msm_hotplug, Intelliplug) - msm_hotplug enabled by default, but it can be disabled to get more smoothness at cost of some battery life
enabled cpuboost with support for input, wakeup and hotplug boost
USB fast charge support (0.9A on USB data link instead of just 0.5A, disabled by default)
added westwood network TCP congestion angorithm
reading CPU voltages
state notifier support
some minor tweaks
INSTALLATION:
Copy the kernel IMG file to internal memory
Reboot to TWRP recovery
(Optional) Backup your Boot partition
Select Install - Install Image - select the IMG file and check Boot
If you had magisk installed, you need to re-install it again
Reboot
Factory reset should not be needed.
DOWNLOAD:
Version 0.1.62 at Mega
Version 0.1.36 at Mega
TWEAKING:
You can use Kernel Adiutor or any other tool to tweak the settings. Personally, I am using the following values:
CPU governor for all CPUs: blu_acttive
CPU hotplug: disabled
IO scheduler: zen, read-ahead 256kB, rotational/IO Stats/Add Random: disabled
governor settings for little cores:
go_highspeed_load 92
hispeed_freq 1017600
target_loads 92
above_hispeed_delay 30000
fastlane 0
governor settings for big cores:
go_highspeed_load 95
hispeed_freq 1190400
target_loads 95
above_hispeed_delay 40000
fastlane 0
CPU boost:
interval: 40ms
input interval: 300ms
sync treshold: disabled
input boost core 1-4: 806 MHz
input boost core 5-8: 883 MHz
Wakep boost: enabled
Hotplug boost: disabled
big cores 7 and 8 disabled (if I don't need top performance)
Thermal:
Core Control: Enabled
VDD Restriction, Temperature Throttle: Disabled
Virtual memory:
dirty_ratio: 40
dirty_background_ratio: 15
swappiness: 0
vfs_cache_pressure: 10
Z-RAM: 0 + Magisk module Swap Torpedo to get rid of ZRAM (we don't need to compress RAM and use swap when we have 6 GB of it)
With those, I am getting smooth performance and no heating, up to 2 days of battery life. Antutu still scores at 105k (geekbuying stock had only 85k).
Click to expand...
Click to collapse
Note: I am not responsible about any damage of any kind that this kernel may cause.
If you are looking for the latest stock ROM for this phone, Global version can be found HERE (1.05) and Chinese ROM HERE (2.06) (version numbering is different than global ROM; tip - if the download speed is too slow from China, try a VPN extension...I used Hoxx VPN into Singapore and the download speed went from 30 KB/s to 5 MB/s)
KERNEL?
Zjh0094 said:
KERNEL?
Click to expand...
Click to collapse
Yes. What exactly are you asking for?
Great job. Installed on the global firmware 1.05. Thanks again.
lapist said:
Yes. What exactly are you asking for?
Click to expand...
Click to collapse
There is no requirement that I am different from your device. I can't try this wonderful thing.
If you need anything else to be added to the kernel, like your favorite governor of f2fs support, just let me know and I can add it
Zjh0094: I have no idea what are you talking about....
lapist said:
If you need anything else to be added to the kernel, like your favorite governor of f2fs support, just let me know and I can add it
Zjh0094: I have no idea what are you talking about....
Click to expand...
Click to collapse
My device is NX563J can brush into this kernel
F2FS is a good suggestion but he doesn't make much difference in ufs2.1
Zjh0094 said:
My device is NX563J can brush into this kernel
F2FS is a good suggestion but he doesn't make much difference in ufs2.1
Click to expand...
Click to collapse
Yes, I see...this is not kernel for NX563J
Actually our Z17 Lite has eMMC 5.1 storage, not UFS like regular Z17, so F2FS could make sense.
lapist said:
Yes, I see...this is not kernel for NX563J
Actually our Z17 Lite has eMMC 5.1 storage, not UFS like regular Z17, so F2FS could make sense.
Click to expand...
Click to collapse
Yes, eMMC5.1 needs F2FS very much.
@lapist does these kernel also includes the tweeks from here?
Nikolaosf said:
@lapist does these kernel also includes the tweeks from here?
Click to expand...
Click to collapse
No, the file init.qcom.post_boot.sh is in system partition (not in the kernel) and it overrides the CPU settings, so it can't be included in kernel. But you can change the CPU settings also thru Kernel Adiutor.
For example switching to blu-active governor and ensuring that CPU min/max frequencies are set properly should be enough for the beginning.
lapist said:
No, the file init.qcom.post_boot.sh is in system partition (not in the kernel) and it overrides the CPU settings, so it can't be included in kernel. But you can change the CPU settings also thru Kernel Adiutor.
For example switching to blu-active governor and ensuring that CPU min/max frequencies are set properly should be enough for the beginning.
Click to expand...
Click to collapse
Oh i see! Simply i download the adiutor and try to find the blue active! I will try to...what about battery life after the new kernel?
Nikolaosf said:
Oh i see! Simply i download the adiutor and try to find the blue active! I will try to...what about battery life after the new kernel?
Click to expand...
Click to collapse
Battery life depends mainly on your governor and hotplug settings ? With my values, I still have around 50% of the battery left in the evening after light to medium use. I am using Blu-active governor and I am still experimenting with msm-hotplug settings - too much power saving brings lags, so I am looking for balance between smoothness and battery efficiency.
In general, I think that this kernel has a bit shorter battery life than stock with the same governor settings, but it feels considerably smoother.
If you want to have your changes made in Kernel Adiutor permanent, don't forget to enable applying them on boot. For me applying on boot sometimes didn't happen, but it would help if you convert Kernel Adiutor to system app. I am using App Systemizer module from Magisk for that.
Is there any news about the kernel for Lineage from HighwayStar_ru?
KomatoZZZnik said:
Is there any news about the kernel for Lineage from HighwayStar_ru?
Click to expand...
Click to collapse
No, no reply from him. I see in his profile that he was active today, but he didn't answer...
Hey @lapist ! I am using the kernel but I would like to go back to the international rom settings as far as cpu and thermal throttling. I couldn't find the stock files, can you please share them ?
Crisvendetta said:
Hey @lapist ! I am using the kernel but I would like to go back to the international rom settings as far as cpu and thermal throttling. I couldn't find the stock files, can you please share them ?
Click to expand...
Click to collapse
Why would you want to go back to Geekbuying's settings? Isn't it better to tweak the settings in blu_active or interactive governor according to your needs?
lapist said:
Why would you want to go back to Geekbuying's settings? Isn't it better to tweak the settings in blu_active or interactive governor according to your needs?
Click to expand...
Click to collapse
I just don't want my phone overheating, can't find some proper settings, the ones from the global rom were good enough. Thanks
Crisvendetta said:
I just don't want my phone overheating, can't find some proper settings, the ones from the global rom were good enough. Thanks
Click to expand...
Click to collapse
When does the overheating happen? I am personally using blu_active governor with the following values:
governor settings for little cores:
go_highspeed_load 92
hispeed_freq 1017600
target_loads 92
above_hispeed_delay 30000
fastlane 0
governor settings for big cores:
go_highspeed_load 95
hispeed_freq 1190400
target_loads 95
above_hispeed_delay 40000
fastlane 0
CPU boost:
interval: 40ms
input interval: 300ms
sync treshold: disabled
input boost core 1-4: 806 MHz
input boost core 5-8: 883 MHz
Wakep boost: enabled
Hotplug boost: disabled
CPU hotplug disabled
big cores 7 and 8 disabled (if I don't need top performance)
With those, I am getting smooth performance and no heating, up to 2 days of battery life. Antutu still scores at 105k (geekbuying stock had only 85k).
If your phone overheats during gaming, you can just try lowering max frequency for big cores, although the phone throttles the CPU on high temperature automatically...
To get back to stock values, you would need to restore them from backup...
EDIT: I added my settings into the first post.
Hi, I am interested in increase in frequency of GPU. It would be desirable to learn whether there is any opportunity for increase in frequency of GPU approximately to ~ 800MHz (for Geekbuying 1.05)?