Database Develop

[KERNEL][AOSP | 4.2.2][DUAL-BOOT] Greenblob 1.1.1 LTS

{
"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"
}
Credits to codeworkx for the base aosp kernel!
Features:
More shedulers
row I/O scheduler
sio I/O scheduler
vr I/O scheduler
More governors
cpufreq_smartass2
cpufreq_lagfree
cpufreq_pegasusq
cpufreq_lazy
cpufreq_lulzactive
cpufreq_minmax
cpufreq_abyssplug
cpufreq_wheatley
cpufreq_scary
cpufreq_HYPER
Updated to linux kernel 3.1.0 -rc1
Dualboot support
Brightness adjustments for darker screen settings (good in low light conditions)
Synced with latest codeworkx fixes
Undervolting support
USB fastcharge support
Cleaned up arm source
Compiled with hard float instead of soft float
Greenblob 1.1.72 LTS (Changelog):
Added added row I/O scheduler
Added added sio I/O scheduler
Added added vr I/O scheduler
Upgraded from 3.0.72 to 3.1 -rc1
500 commits FTW! Happy changelogging on git
Greenblob 1.1.1 LTS (Changelog):
Updated kernel from 3.0.36 to 3.0.72 (We´re now on latest linux 3.0.x releases)
Updated ~700 commits (20 Github pages lool). Those are from 3.0.36 to 3.0.72
Hopefully working now on latest cm nightly (working here on my chameleon os)
Go for changelog on github!
Greenblob 1.1 LTS (Changelog):
Fixed auto reboot in recovery
Fixed rebooting during backup in recovery
Fixed some governor stuff
Updated dualboot
Greenblob 1.0 LTS (Changelog):
Added governors
Added 'long-time-support'
DevPrev 6.3 (Changelog):
Added usb fastcharge
Added undervolting support
Default cpu speed at 300mhz
Synced latest changes from cm repo
DevPrev 6.0 (Changelog):
fixed cpu staying at 600mhz
added DualBoot support (Credits to chuandinh for the method. Its the same as Galaxy Note 2 uses)
All dualboot related questions please visit the dualboot thread!!
DevPrev 5.2 (Changelog):
restart after quitting coding kernel
adjusted gamma values for smartphone usage in dark light
wifi driver update
mhard float instead of msoft float
cpu frequency change based on screen on/off
touchkey timeout 2 seconds
cleaned up arm source
TWRP for now - I was just trying something, will revert to cwm soon
Important:
There are no other features than mentioned in the changelog. I restarted the kernel and I think I wont add OC etc. This kernel is not ready yet but damn stable and fast. No need to oc anything (my opinion).
For brightness (gamma) adjustment: You will notice a heavy brightness drop between lowest and lowest +1 step brightness. The one before the lowest was the lowest brightness that comes with normal cm kernel. I will make a better transition between the last two steps within the next update.
DevPrev 5 (Changelog):
Now compatible with cm10.1
Some bugfixes
New control app now on google play!
DevPrev 2 (Changelog):
Updated to latest codeworkx sources
Added undervolting support
Added usb fast charge mode support
Readded 1.2Ghz slot
Greenblob kernel control:
This is the official app to control all features of Greenblob kernel (for now available on Galaxy S2G, visit XDA for infos).
But most features can also be used on any other device! (Ok, not any but for a big number).
You can:
- Change status of tweaks
- Cpu OC
- GPU OC
- Change voltage
Installation:
As usual: Flash the flashable .zip in cwm. Only working on aosp jellybean roms!
Download:
Download here

FAQ:
How do i change voltage?
Use the latest version of setcpu, leantweaks, cputuner, or your ROM's built-in tools.
Do i need to wipe dalvik/cache?
In general there's no need, but it doesn't hurt so if you have time go ahead. Posted Image I don't wipe.
What's the variable on the GPU OC?
The kernels GPU is now set to stock 307Mhz by default. You can adjust that by using Variable GPU OC (see a separate FAQ entry below).
When you go from say 307 to 512Mhz, you will not experience near double performance increase. Due to the factors outside the GPU module (ie. memory bandwidth limitation), you can't truly OC the GPU. In fact, most people can't tell the difference between 307, 384 and 512. Nenamark2 will roughly give you the following scores: 307/25fps, 384/28fps, and 512/31fps.
Some of you have seen the note from Colin, the Google kernel engineer, not to OC the GPU because using the OV_UV voltage slot will drain the battery. Greenblob kernel uses the same voltage for both OV and OV_UV slots. So there's no danger of battery drain there.
My phone doesn't seem to be deep-sleeping, what gives?
(assuming you checked in the right place like cpuspy) In terms of deep-sleep, there's not a whole lot going on in the kernel. It works or it doesn't - and I can assure you that I test every release (well almost every release) for deep-sleep before I release.
19 out of 20 times it's either 1) some sort of background process that's preventing your phone from going into deepsleep, or 2) something's misconfigured in your ROM, or both. Also connecting to USB will prevent phone from going into deepsleep.
I'm having unusual battery drain - help!
First of all, our i9100g (AS every Smartphone ^^) has very poor battery life while in active use. It's downright horrible while screen is on - screen is definitely the main culprit and there's not a whole lot I can do about that.
Custom undervolting can help or can hurt. This is mainly due to SmartReflex (class1.5) which auto-calibrates the ideal voltages for you. In fact, with SR you don't really need to use the custom undervolting feature for frequencies other than the 2 lowest. It does a great job calibrating higher frequencies. I personally don't touch it.
The "notrim" versions are an exception because I had to disable SR1.5 for the trim override to work. There's no auto-calibration going on there. Feel free to mess with custom undervolting on the notrim versions.
Now, if you've already accepted the horrible battery life while screen is on, but have questions about battery drain while idle - read the next question.
I'm having unusual battery drain while screen is off, or phone is sleeping - help!
First, let's find out if you're phone is going into deep-sleep. Install CPUSpy, unplug phone, turn off screen, and leave the phone alone for 5-10min. Turn the screen back on, launch CPUSpy, and see if you see an active entry for Deep Sleep. If so congratulations - read on.
If you've determined that your phone is not entering deepsleep by using the above method, read my entry above that says "My phone doesn't seem to be deep-sleeping". I've heard that removing SDM.apk helps as well as rebooting the phone. Also try turning your bluetooth on and off, and launching camera app and closing it.
If you've determined that your phone is entering deepsleep fine but still feel like battery drains, read the next question.
I'm having unusual battery drain while phone is in deep-sleep - help!
First make sure you are absolutely positive that deep sleep is working (read the previous question).
While on my kernel *and* connected to Wifi, you shouldn't drain more than 2% battery per hour *average* while in deep sleep (based on 5-8 hour continuous deep sleep). With wifi turned-off, my guess is probably no more than 3-6% per hour, depending on signal strength.
tip 1: If above is not happening for you, first charge the phone all the way and reboot. Let things settle a bit - give it a day or so. If you're using Battery Monitor Widget (which is not accurate for gnex), things should eventually settle between -2mA and -60mA per sample.
tip 2: Install BetterBatteryStats and look at which wakelocks dominate. Google search for names of the wakelocks to see how you can fix them.
tip 3: http://checkthis.com/d87t
If nothing seems to help, you can try the "notrim" version, but stick to speeds between 350 and 1350 (don't use OC slots). The notrim version has SR1.5 disabled which could help for those of you with drain issues on my other kernels.
What is SmartReflex?
SmartReflex performs continuous dynamic voltage scaling around the nominal operating point voltage according to silicon characteristics and operating conditions.
My stable and experimental builds will have SR Class 1.5 enabled by default.
You can disable SR via sysfs
How do I use Variable GPU OC?
You can use Lean Tweaks by Jake, or use the built-in "oc" script. Both leantweaks and my oc script will create an init.d script so the setting sticks at boot. My "checkt" script will also show the current GPU max speed. Note that 512MHz will probably not work for everyone.
307Mhz (stock) is set default by the kernel.
Open Terminal, and type for stock speed of 307Mhz: oc gpu 0
for 384MHz: oc gpu 1
for 512Mhz: oc gpu 2
FAQ partly taken from leankernel! I changed the important parts for us! Thanks to them! http://forum.xda-developers.com/showthread.php?t=1790675​

An app for variable gpu oc is already in progress! For now please read the FAQ​

Great work fuss. It says gnex somewhere in op btw.
Sent from my GT-I9100G

Such a Fast Releas

iXanza said:
Great work fuss. It says gnex somewhere in op btw.
Sent from my GT-I9100G
Click to expand...
Click to collapse
Thanks ^^ I changed it
And I also changed the battery life expectation
Sent from my GT-I9100G using xda app-developers app

Thanks for sharing，that works great.

any chance to get this kernel for stock rom..?
Sent from my GT-I9100G

+100 for the awesome Kernel !
Sent from my GT-I9100G using Tapatalk 2

First of all, WELCOME BACK FUSS.. Back with bang I can say. New Kernel and it's more powerful, efficient and features. WOW. You Rock. Thank you fuss :beer:
Sent from my GT-I9100G using Tapatalk 2

Is it safe to install with latest cm10 nightly?
Sent from my GT-I9100G using Tapatalk 2

ottomatteseo said:
Is it safe to install with latest cm10 nightly?
Sent from my GT-I9100G using Tapatalk 2
Click to expand...
Click to collapse
Yes
Sent from my GT-I9100G

iXanza said:
Yes
Sent from my GT-I9100G
Click to expand...
Click to collapse
Thnx
Sent from my GT-I9100G using Tapatalk 2

hi fuss, welcome back to XDA, i though you will disappear for long time :laugh::laughim joking)
and BIG THANK TO YOUR NEW WORKS Greenblob
may i flash it to codebox 1.9.0? any suggest to flash?(im still using codebox whatever it no longer support:good: because it is awesome)

IloveXDA512 said:
hi fuss, welcome back to XDA, i though you will disappear for long time :laugh::laughim joking)
and BIG THANK TO YOUR NEW WORKS Greenblob
may i flash it to codebox 1.9.0? any suggest to flash?(im still using codebox whatever it no longer support:good: because it is awesome)
Click to expand...
Click to collapse
Flash GreenBlob through CWM
Sent from my GT-I9100G using Tapatalk 2

My phone freezed in the instance i got to the menu. Now it boot loops when i has reached the lockscreen. What should i do now?

I've just installed it. I see in recovery version is now 6.0.1.9 is it still using blob crap for android? Thanks
Sent from my GT-I9100G using xda premium

kernel from the sky =) =) big big thanks fuss!!!!! =) =) what a speed!!!!! =P

cesco73 said:
kernel from the sky =) =) big big thanks fuss!!!!! =) =) what a speed!!!!! =P
Click to expand...
Click to collapse
Sorry thats FUSS not sky
Sent from my GT-I9100G using Tapatalk 2

im sorry to said that, but im still having the reverting back of the freqency....
any idea? ><??

[APP]LGP880 Booster v1.5.1 (ROOT)

This application was tested on JB (Android 4.1.2) and requires "root" permissions.
None of the settings are permanent. Default values will be restored when you restart your phone.
Download link: http://www.tazetaze.com/?dl_id=8 (53 KB)
LG Optimus 4X decreases CPU frequency after battery temperature reaches 43 °C to cool the device.
If you play a game for a long time, battery temperature reaches 43 °C rapidly and the game starts to lag because of frequency decrease.
This application sets the Tegra3 "temp_throttle_skin", CPU governor and GPU frequency values according to your preferences when you switch "Boost" on.
So you can play games with higher frequencies and more CPU cores without being effected by the heat increase.
Boost Preferences
Temperature threshold (temp_throttle_skin) value can be set to 46, 48 or 50 °C.
CPU governor value can be set to interactive (default), ondemand or performance.
GPU frequency (3D and 2D) value can be set to 200 MHz (default value), 330 MHz, 380 MHz or 416 MHz.
Your device may feel hotter than before after you set "Boost" on and play a game for a long time.
Other Functions
It's possible to see the CPU usage and frequency by setting the "Show CPU Usage" switch on. This has the same effect as enabling "Show CPU Usage" setting from the hidden menu.
If you enable "Unlimited Temp. Charging", you can continue to fast charge even if slow charge is activated because of high temperature.
New function: If you set "Keep Brightness" switch to "On", LCD brightness will be kept at the level you specify at the "LCD Brightness" preference. Temperature rise will not lower the brightness.
"Keep Brightness" function does not work properly for high temperature conditions.
Although brightness seems to stay at the level you specify in the notification tray, it is actually decreased when temperature rises.
This side effect occurs only when you play games for a long time with high temperature levels.
Please follow the new versions of "Tegra Overclock" application for a proper way of avoiding LCD brightness cutter.
Click to expand...
Click to collapse
WARNING
Use at your own risk.
Turn "Boost" off after you play your game.
Battery will drain faster when CPU governor is set to "performance".
Overheating may damage your phone hardware.
The code to change CPU governor was taken from the "No-frills CPU" project. Thanks to Luca Santarelli for making his project open source.
Shell commands to change GPU frequencies was taken from the "Tegra Overclock" application.
{
"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"
}
Release Notes
v1.5.1
If the kernel supports GPU frequency higher than 416 MHz, this maximum frequency can be selected in the GPU Frequency preference.
v1.5.0
"Keep Brightness" switch was added. Now you can keep brightness at the level you want regardless of phone temperature.
Note: This function requires that "Brightness Service" keeps running. If you kill the service with a task killer application, brightness will not be kept.
v1.4.0
"ondemand" CPU governor option was added to preferences.
Current CPU temperature is displayed under "Temperatures" section.
Minor user interface changes.
v1.3.0
"Unlimited Temp. Charging" functionality was added.
v1.2.3
Minor bug fixes
416 MHz was added to GPU frequencies list
v1.2.1
"echo 'Y' > /sys/module/tegra3_clocks/parameters/detach_shared_bus" command was added to program startup to prevent crashes that happened when GPU frequency was set.
v1.2.0
GPU frequencies for Boost can be set from "Boost Preferences" section.
v1.1.0
Temperature threshold and CPU governor values for Boost can be set from "Boost Preferences" section.
v1.0.0
First release

FC on kholk's CM10.1, ups!

I think this is for stock kernel only.

just a small tip from me, use more than 48°C for skin temp. i'd suggest at least 50.
'cause the throttle will kick in even before the temp_throttle_skin value is reached.
also performance gov is not the very best choice IMO. it produces too much heat, 'cause it would be enough to run @ 800MHz (or another freq, just as an example)
But nice work anyways

laufersteppenwolf said:
just a small tip from me, use more than 48°C for skin temp. i'd suggest at least 50.
'cause the throttle will kick in even before the temp_throttle_skin value is reached.
also performance gov is not the very best choice IMO. it produces too much heat, 'cause it would be enough to run @ 800MHz (or another freq, just as an example)
But nice work anyways
Click to expand...
Click to collapse
Thanks for your precious comments.
So you recommend to set 50 °C for temp_throttle_skin, no change for CPU governor and 800 MHz for maximum CPU frequency.
Is that right?

postacik said:
Thanks for your precious comments.
So you recommend to set 50 °C for temp_throttle_skin, no change for CPU governor and 800 MHz for maximum CPU frequency.
Is that right?
Click to expand...
Click to collapse
He was more suggesting another governor - interactive is fine, in my opinion.

someth1ng said:
He was more suggesting another governor - interactive is fine, in my opinion.
Click to expand...
Click to collapse
Interactive is the default CPU governor and is fine on JB but it really helped to boost games on ICS.
Maybe I can make CPU governor change optional.

New version (v1.1.0) was released.
CPU governor and threshold temperature settings can be adjusted under the "Boost Preferences" section.

Thanks for your precious comments.
So you recommend to set 50 °C for temp_throttle_skin, no change for CPU governor and 800 MHz for maximum CPU frequency.
Is that right?
Click to expand...
Click to collapse
partly yes
- I'd use at least 50°C for temp_throttle_skin.
- CPU gov, maybe ondemand, it "likes" higher frequencies --> good for gaming
- and no, please do not cap the freq it was an example of what is bad at performance governor. (800MHz actually needed, but it is forced to keep @1.7/1.5GHz)
but you could increase the min freq during gaming to 500MHz or something. that way the quad core stays online and doesn't change to LP mode. this can slightly improve the performance a bit

Can you suggest if i should add gpu frequency change option for boosting as in the Tegra Overclock application?
I would be glad if you have an optimum gpu frequency to play notoriously lagging games without any problems.
Some of my friends suggest setting gpu frequency to 416 mhz to play need for speed and real racing. Is that the right frequency?
Sent from my LG-P880

Nice idea..
Great idea for our 4X! :good:
will test it soon..
But, i think this should be moved to themes and apps..

New version (v1.2.0) was released.
Now you can set GPU frequencies to use for Boost mode.

Can a moderator move this thread to "themes and apps" section if that's the right place for an application?

postacik said:
Can you suggest if i should add gpu frequency change option for boosting as in the Tegra Overclock application?
I would be glad if you have an optimum gpu frequency to play notoriously lagging games without any problems.
Some of my friends suggest setting gpu frequency to 416 mhz to play need for speed and real racing. Is that the right frequency?
Sent from my LG-P880
Click to expand...
Click to collapse
well, the N7 uses 416 by default. this should be a pretty good value, regarding performance AND battery.
if you want more battery life, i'd suggest 330 MHz.
for really, really hardcore gaming 520 (564/600) MHz. but this will cause heat, too...
postacik said:
Can a moderator move this thread to "themes and apps" section if that's the right place for an application?
Click to expand...
Click to collapse
i'm on it

New version (v1.2.1) was released.
A missing setting caused the phone to freeze in version 1.2.0.
This problem was solved in v1.2.1.
Please uninstall v1.2.0 and install v1.2.1 to avoid crashes.

force close on rooted ICS when opening.

Emmanuel2000 said:
force close on rooted ICS when opening.
Click to expand...
Click to collapse
Which version? Since I have stock JB installed I don't have a chance to test it on ICS.

postacik said:
Which version? Since I have stock JB installed I don't have a chance to test it on ICS.
Click to expand...
Click to collapse
United Emirates
ICS 4.0.3 V10E Open AME
rooted with stock rom.

Emmanuel2000 said:
United Emirates
ICS 4.0.3 V10E Open AME
rooted with stock rom.
Click to expand...
Click to collapse
Can you try again with the attached apk?

where can i get latest version??
---------- Post added at 06:39 PM ---------- Previous post was at 06:25 PM ----------
postacik said:
Please do not use version 1.2.0. It makes the phone freeze when Boost switch is clicked. Install v1.2.1 instead.
Release Notes
v1.2.1
"echo 'Y' > /sys/module/tegra3_clocks/parameters/detach_shared_bus" command was added to program startup to prevent crashes that happened when GPU frequency was set.
v1.2.0
GPU frequencies for Boost can be set from "Boost Preferences" section.
v1.1.0
Temperature threshold and CPU governor values for Boost can be set from "Boost Preferences" section.
v1.0.0
First release
Click to expand...
Click to collapse
Where can i get latest downloads??
the link given is downloading old ver......

[KERNEL]Huawei Ascend P6S / P7 K-Tuned Kernel

Ascend P6S / P7 K-Tuned Kernel​Hello! Finally I decided to make a new thread for kernel with description of all features.
So, here they are:
CPU Governors:
PegasusQ
AbyssplugV2
Optdemand
Interactive
Impulse
Pwrctrl_hotplug default
I/O Schedulers:
CFQ
Deadline
ROW
Noop
FIOPS default
TCP Congestion:
HTCP
Reno
BIC
CUBIC
Westwood+ default
Upstreamed to 3.0.101 version
SELinux permissive for 5.1.1
LZ4 kernel & ramdisk compression
Backport random from kernel 4.0 branch
ExFAT version updated from 1.2.5 to 1.2.9
F2FS support
Fixed 5.1.1 GPU performance regression bug
USB Fast Charge
Intelli-Plug
Asynchronous Fsync
CPU overclock: enabled 1996MHz CPU frequency and 1795MHz for P6S
CPU undervolting
GPU overclock: enabled 700MHz GPU frequency for P6S
GPU undervolting
Adjusted stock CPU & GPU governor thresholds for better performance
DoubleTap2Wake
Sweep2Sleep
init.d support
set_immutable binary removed from ramdisk for 4.4.2
Speed up system startup
Now more detail about some features:
Governors
PegasusQ
Governor from Samsung with hotplug support. Perhaps, the most tunable and flexible one.
Parameters description:
sampling_rate: the interval with which governor will be carried out. Less value - better responsiveness, but at the same time, more load for CPU by governor itself.
sampling_down_factor: amount of iterations governor will stay at highest frequency before go down.
up_threshold: load threshold in % above which CPU frequency will be increased.
up_threshold_at_min_freq, freq_for_responsiveness: at frequency lower than freq_for_responsiveness will be used up_threshold_at_min_freq threshold - provided for better responsiveness.
down_threshold: load threshold in % below which CPU frequency will be decreased.
freq_step: step of frequency encrease in % from maximum frequency.
hotplug_freq_*: high and low frequency thresholds for making decision about hotplug of each core.
For clarity, it looks like this:
Code:
static int hotplug_freq[4][2] = {
{0, 1596000},
{208000, 1795000},
{416000, 1996000},
{624000, 0}
};
In this array left column is frequency at which core will be disabled; right column - frequency at which will be enabled next core.
hotplug_rq_*: analogous parameters set (array), defining queue task length for making decision about hotplug of each core.
Code:
static int hotplug_rq[4][2] = {{0, 50}, {50, 100}, {100, 150}, {150, 0}};
For example, second core will be disabled after reaching 208MHz frequency and amount of tasks must be less than 50;
third core will be enabled after reaching 1795MHz frequency by second core and amount of tasks more than 100.
cpu_up_rate: amount of governor iterations cpu should stay at defined frequency for enabling next core.
cpu_down_rate: amount of governor iterations cpu should stay at defined frequency for disabling last active core.
down_differential: defines load in % which must be less than up_threshold to go to lower frequency.
hotplug_lock: lock amount of active cores.
min_cpu_lock: limits min value of enabled cores.
max_cpu_lock: limits max value of enabled cores.
up_nr_cpus: defines how many cores to enable at a time.
AbyssplugV2
Based on Conservative, has hotplug support. Pluses: pretty simple, hence doesn't load CPU by himself. Frequency increases sequentally, after reaching max frequency - enables next core. And vice versa. Minuses: often enables / disables cores (what in itself is energy intensive).
Distinctive parameters:
up_threshold_hotplug: load threshold in % above which will be enabled next core.
down_threshold_hotplug: load threshold in % below which will be disabled last active core.
boost: load threshold above which frequency will be increased through step (for exaample., from 208000 immediately on 624000)
Optdemand
Governor by Hisilicon, based on Ondemand. Backported from Honor 4X/4C. Distinctive feature is each frequency has its own thresholds to go to higher or lower frequency.
Distinctive parameters:
go_hispeed_load, hispeed_freq: after exceeding go_hispeed_load threshold, CPU goes immediately to hispeed_freq frequency.
up_thresholds, down_thresholds: above and below load thresholds for each frequency. For clarity:
Code:
static unsigned int operating_points[7][3] = {
/* kHz up_threshold down_threshold */
{208000, 60, 0},
{416000, 60, 30},
{624000, 70, 40},
{798000, 80, 50},
{1196000, 85, 50},
{1596000, 90, 60},
{1795000, 95, 70},
{1996000, 100, 80},
};
For example, for frequency 624MHz, if load will go below 30%, will be calculated new lower frequency according to new load value; if load will go above 70% - frequency will be increased.
boost: frequency will be increased to hispeed_freq
bostpulse_duration: duration of boost in microseconds.
Interactive
Google's gold standard governor. Updated to 3.4 kernel branch
Impulse
Based on Interactive governor. Good responsiveness.
USB Fast Charge
Increases charge current when connected to USB. It has sense only when connected to USB 3.0
Can be enabled by writing "1" into /sys/kernel/fast_charge/force_fast_charge file or by third party applications.
Disabled by default
Intelli-Plug
Hotplug driver for governors not supporting hotplug.
Activated and deactivated automatically depending on chosen governor.
Parameters are in /sys/module/intelli_plug/parameters
nr_possible_cores: max cores affected by driver.
nr_run_profile_sel: has several profiles :
0: balance default
1: performance
2: conservative
3: eco
4: eco extreme
screen_off_max: max frequency at screen off.
touch_boost_active: enables additional core at screen touch disabled by default
CPU undervolting
Undervolting values can be set for each frequency individually. Regulator has step 8mV starting from 700mV. I've got such stable values:
{
"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"
}
But you should start from higher values. I've made a test: CPU locked at frequency 1795MHz, RAR creates archive with 4 threads in 10 minutes. Average CPU temperature during this time was 56.124 degrees, with undervolting average temperature became 51.119 degrees. I.e. average temperature became lower for 5 degrees which means less power consumption.
Comparative graph:
GPU undervolting
Since I couldn't find any common used sysfs interface and applications supporting it, you can make it using script (see init.d spoiler).
My stable values are:
Code:
160: 860 -> 700
266: 860 -> 732
355: 876 -> 764
533: 956 -> 860
700: 1052 -> 924
But most probable, you will have troubles with such values, try to find suitable for your own.
3DMark Ice Storm Extreme showed average temperature decrease from 61.587 to 55.502 degrees.
Comparative grapth:
DoubleTap2Wake
Screen on by double tap on it. Has two parameters in /sys/android_touch
doubletap2wake: enables dt2w. Possible values are:
0: disabled default
1: active at all screen
2: active at top half
3: active at bottom half
4: active at navbar
dt2w_duration: Since I couldn't implement waking up device from deep sleep by irq from touch panel, so kernel doesn't go to deep sleep when dt2w is active, I added parameter defining how long dt2w stays active after screen off. After this duration dt2w becomes inactive and kernel can go into deep sleep.
Sweep2Sleep
Swipe on navbar for screen off. Can be enabled by writing "1" into /sys/android_touch/sweep2sleep file. Disabled by default.
s2s_length: swipe length in dots. By default, equal to 25% of screen width.
init.d
For executing scripts at startup, put them in /system/etc/init.d folder and set permissions to 0755
Several scripts examples (doubletap2wake, sweep2sleep, fast_charge, gpu_undervolting): View attachment scripts.rar
Scores
For correct governors switching I recommend to use Kernel Adiutor
It also lets to manage IO schedulers, TCP congestion, fast charge, CPU undervolting.
Requirements:
Unlocked bootloader
TWRP
Installation:
Just install zip-archive from TWRP
Download:
View attachment K-Tuned_kernel-4.4.2.zip
View attachment K-Tuned_kernel-5.1.1.zip
Source: Github
Updates:
31.10.2016
CVE-2016-5195 "Dirty COW" fixed.
Now CPU voltage values take effect right after frequency changes.
30.07.2016
Adjusted voltages for overclocked frequencies due to cases of appearing stability issues on some devices.
15.05.2016
Removed GPU undervolting applying at booting due to some users had stability issues. Now for GPU undervolting use init.d script individually.
Adjusted governor thresholds.
Reduced min online CPUs from 3 to 2 when screen is on for stock pwrctrl_hotplug governor.
Regards,
Kostyan_nsk

Battery is better from stock kernel??
Version lollipop compatible?

roxkiller said:
Battery is better from stock kernel??
Click to expand...
Click to collapse
for me it is the same if you set dt2w to 3 minutes
roxkiller said:
Version lollipop compatible?
Click to expand...
Click to collapse
just download K-Tuned_kernel-5.1.1.zip
if someone want to set dt2w and s2s without init.d can use this apk made by Printusrzero http://forum.xda-developers.com/asc...ap-to-wake-t3036327/post62542196#post62542196

Thank you so much! I've been waiting for ages for a kernel which isn't only for emui 2.3

I'd installed kernel 5.1.1 ktuned on my P7 B852 and it's continuously restarts. Anyone had a kernel stock for TWRP?

What is your preferred setting?
Mine:
GOVERNOR: Impulse
CPU : maximum frequency 1596mhx
I/O : fiops with 128kb readahead
INTELLIPLUG :disabled
I discovered that with Intelliplug enabled, my phone has some glitches.....
With the settings above i get 50-60% battery when i go home, 8-10 pm
What are your settings ?

leleallof said:
I'd installed kernel 5.1.1 ktuned on my P7 B852 and it's continuously restarts. Anyone had a kernel stock for TWRP?
Click to expand...
Click to collapse
Someone else tried it on P7?

Installed with cwm on B861. Working, but I see no difference.

@Kostyan_nsk kernel comes overclocked, when I try to select the default clock and start the cell with the standard clock is not, always coming back to overclock, so I went back to stock kernel

@roxkiller, just set "Apply on boot" in Kernel Adiutor after limiting max. cpu frequency and enable Kernel Adiutor in Startup Manager, so KA will aplly your settings after reboot.
And btw, if you didn't notice, cpu voltage at 1996MHz is the same as at 1795MHz, therefore I doubt that power consumption will noticably increase relatively to 1795Mhz frequency...

I have set the cpu undervolting according to your recommandation. Today , i received a message on whattsap , when i picked up the phone to read it, the phone was already rebooting. It enter the system but saying no root available !!!
Rebooted the phone again, all ok.

kye04 said:
I have set the cpu undervolting according to your recommandation.
Click to expand...
Click to collapse
It is not a recommendation, it's just my stable values as "play around" point.

@Kostyan_nsk it would be possible to compile a version without overclock ? I and perhaps most people do not like under / overclock the device, just heating up ... or pack the kernel to the option selected remain in next boot?

Kostyan what are you settings?

Updated version and details in first post.

Kostyan_nsk said:
Updated version and details in first post.
Click to expand...
Click to collapse
Thank you for the update. Has the screen glitches bug found in the P7 been resolved in this release?

jordi-chant said:
Thank you for the update. Has the screen glitches bug found in the P7 been resolved in this release?
Click to expand...
Click to collapse
+1
I really want to try it on my p7

As my memory serves me right, this issue was solved a few months ago. But you better have to ask P7 owners about it.

I thought the problem was solved for 720p but with 1080p there were still glitches?

720p never had glitches at all.

Pure Nexus/Elementalx : CPU Throttling (Low Battery)

I am running the latest version of Pure Nexus, with the latesst version of the Elementalx Kernel. I have also installed the EX Kernel Manager. This is my first attempt at a custom kernel and it is working very well.
The only 'issue' I am having or the last hurtle I am trying to get over is the CPU throttling at low battery power. I haven't done extensive testing but in the small amount of testing I have done it seems that when the phone gets around 40%, the Max CPU speed reported in the EX Kernel Manager drops to 1958MHz, with all the cores still enabled. It will remain that way until I charge up the phone above approx 40%, and at that point it will go back to 28800MHz (max value).
I have tried this https://forum.xda-developers.com/nexus-6/development/mod-disable-throttling-battery-low-t3440814 but it doesn't seem to work for me.
Is there a way to achieve this through Elementalx itself. I believe if I change the CPU Gov. to Performance the CPU returns to its maximum value of 28800 MHz even under 40% but using the Elementalx Gov. yields such a good mix of performance and battery life I would rather keep it.
Any thoughts or suggestions welcome.
Thanks.

Just looking at it again...... I'm hitting a max CPU frequency of 1985 MHz earlier than expected. It has happened at 50% battery usage. I can also confirm that changing the Gov. to Performance will up the CPU to the expected, max, value of 2880MHz.

I have discovered a couple things..... First, throttling, from the posts I have read means ' Throttling is turning cores off at lower percentages and keeping frequencies down, not at regular.' So the issue that I am experiencing is not throttling entirely as I have all 4 cores working throughout the battery range. What I do have happening and want to resolve is the Max CPU value, in Ex Kernel Manager changing from 28800 MHz, which is the maximum CPU frequency I have set, to 1958 MHz when the device battery drops below approximately 45%. Second... Changing the CPU Gov., while the battery is under 40% (1958MHz), will increase the CPU frequency back to 28800MHz until the phone drops another battery percentage, which will trigger the underclock (1958Mhz).

EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.

nemanja066 said:
EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.
Click to expand...
Click to collapse
Phone was at 43% and running at an underclocked speed of 1958 MHz. Made the changes in EXKM to the Mode file and enabled the 'Apply on Reboot'. Rebooted the phone. Once booted took a look at EXKM and the CPU speed was still underclocked at 1958 MHz. Check the Temp and it was at 45. Checked EXKM and the CPU temp threshold is set for 60. Didn't change the ofc value. I don't want to disable the thermal as I don't want to damage the hardware accidentally. I also couldn't find the value. It isn't in the Mode file. Where could I find that? Is the ofc file required as well to allow this method to work?
I will continue to tinker.
Thanks for the reply and your help.

ofc= of course. [emoji12]
For me, work ok, only edited thermal conf file (cpufreq, hotplug, gpu threshold 100 threshold clear 99). Please wait some time to.phone cooling down (sleep phone 10-15 minutes) and open EX Manager and see again. Sometimes does not change max freq value at the begining. At least, i had this situation.
Sent from my Nexus 6 using Tapatalk

nemanja066 said:
ofc= of course. [emoji12]
Click to expand...
Click to collapse
Lol! Oops.....
For me, work ok, only edited thermal conf file (cpufreq, hotplug, gpu threshold 100 threshold clear 99). Please wait some time to.phone cooling down (sleep phone 10-15 minutes) and open EX Manager and see again. Sometimes does not change max freq value at the begining. At least, i had this situation.
Click to expand...
Click to collapse
Thanks for the reply. I'm getting closer. I am able to run at 28800 Mhz until 20% battery life and then it underclocks to 1958 MHz on all cores. This is definitely a step forward. Below are the three sections you referred to, CPUFreq, HotPlug, and GPU. This is the modified file. My understanding of what this configuration accomplishes is that at 5% battery power the CPU will throttle back (underclock) to conserve battery power. Unfortunately this isn't happening.... yet.
Any other ideas on why this isn't working as expected? Is there another part of the file that needs to be changed?
Also is there a resource that explains what each line in these files do? I couldn't locate one.
Thanks!
:good:
sampling 5000
[BAT-SOC-CPUFREQ]
algo_type monitor
sensor soc
sampling 5000
thresholds 95
thresholds_clr 94
actions cpu
action_info 2649000
[BAT-SOC-HOTPLUG]
algo_type monitor
sensor soc
sampling 5000
thresholds 90 92
thresholds_clr 89 91
actions hotplug_3 hotplug_2
action_info 1 1
[BAT-SOC-GPU]
algo_type monitor
sensor soc
sampling 5000
thresholds 88 90 95
thresholds_clr 89 89 94
actions gpu gpu gpu
action_info 600000000 389000000 300000000

@monteie2016
I find your shamu thermal conf file a bit strange. I have a pure nexus and elementalx and it's not like that. All you need to edit in this file (with text editor) is set the thresholds to 100 a thresholds_clr at 99.
Thresholds is the battery percentage at which the throttling occurs (at 0% (100-thresholds))
Thresholds_clr is the battery percentage at which the throttling clear (at 1% (100-threshold_clr)).
In practice, this will never happen because in that time your device is already dead.
I will upload a screenhoot of EXKM dashboard to see max freq in my case when battery was bellow 20%. It's stay on 2.6 Ghz.

Can you also post the CPU, GPU, and hotplug values. I would like to see how yours is configured.
Thanks
:good:

monteie2016 said:
Can you also post the CPU, GPU, and hotplug values. I would like to see how yours is configured.
Thanks
:good:
Click to expand...
Click to collapse
Also, I have an older version of the elementalX 4.23 as you can see on screenshot (with july security patches) , because the PureNexus rom does not have august and september kernel patches.
Here is SS thermal conf:
[emoji106] [emoji482]
{
"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"
}
Sent from my Nexus 6 using Tapatalk

Couple of things...... Above you are showing me a status from EXKM at 62% battery. I don't have and underclock issue anywhere between 100% and 20%. When the battery life drops below 20% is where I get the issue (Underclocks to 1958Mhz from 2880Mhz).
Here is what my file looks like
sampling 5000
[BAT-SOC-CPUFREQ]
algo_type monitor
sensor soc
sampling 5000
thresholds 100
thresholds_clr 99
actions cpu
action_info 2649000
[BAT-SOC-HOTPLUG]
algo_type monitor
sensor soc
sampling 5000
thresholds 100 100
thresholds_clr 99 99
actions hotplug_3 hotplug_2
action_info 1 1
[BAT-SOC-GPU]
algo_type monitor
sensor soc
sampling 5000
thresholds 100 100 100
thresholds_clr 99 99 99
actions gpu gpu gpu
action_info 600000000 389000000 300000000
I should also mention that I have disabled BCL, /sys/devicds/qcom,bcl.39/mode and changed the value to disabled.
I have attached two images. One is the battery at less than 20% and what I am seeing for CPspeed (underclock) and the other is above 20%.

Off topic thoughts @monteie2016
What you had asked for was posted in the previous post. The additional information was provided additionally. But you jumped on the extra info. And not one time in this thread have you "thanked" (thumbs up) the only person who had been trying to help you.

I did thank nemanja066 for his post on 20th September 2017, 04:51 PM (thanks button in thread) and my reply on September 23rd had a thanks and a thumbs up.
Also is there a resource that explains what each line in these files do? I couldn't locate one.
Thanks!
:good:
Click to expand...
Click to collapse

[emoji106] No throttling yet.
I will post SS for battery bellow 15%, too.
Sent from my Nexus 6 using Tapatalk

@monteie2016
Looks like a bug with the aroma installer. Try again with flashing kernel in recovery and then in aroma set max freq cpu to 3033MHz. After flashing, reduce the frequency to the desired one in EXKM. After that, it might be fine, and the freq can be reduced only due to the increase in temperature, which is quite OK. When the phone cools down, freq will go back to the old value. If all this fails, then I do not know what to do next.

nemanja066 said:
@monteie2016
Looks like a bug with the aroma installer. Try again with flashing kernel in recovery and then in aroma set max freq cpu to 3033MHz. After flashing, reduce the frequency to the desired one in EXKM. After that, it might be fine, and the freq can be reduced only due to the increase in temperature, which is quite OK. When the phone cools down, freq will go back to the old value. If all this fails, then I do not know what to do next.
Click to expand...
Click to collapse
Thanks for the information. I will take a look at it later. Got busy doing other things
:good:

nemanja066 said:
EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.
Click to expand...
Click to collapse
Hello, just curious if you can specify the file location of the thermal config file? Thank you for your help.

ozzmanj1 said:
Hello, just curious if you can specify the file location of the thermal config file? Thank you for your help.
Click to expand...
Click to collapse
/system/etc/thermal-engine-shamu.conf
Sent from my Nexus 6 using Tapatalk

[Guide][Discussion] Advanced Interactive Governor Tweak/Config - Kirin 970 CPU

As all we know, our phone has one of the newest & most powerful CPU in the market : Kirin 970
together with a huge 4000mAh battery, this phone theoritically should deliver an extremely good battery life. And from what i experienced, this phone perform quite admirably.
That being said, when being compared to other flagships in the market (as can be seen here : https://www.youtube.com/watch?v=lXp-4QyJpmo), Mate 10 still fall short to the like of Oneplus 5 which actually has a smaller battery,
biggest factor that might affect that result , aside from the screen resolution difference, is of course, software & kernel optimisation,
in an attempt to get a better battery life out of this device, but without impacting performance, i remember one of the guide made by @soniCron i used to stumbled upon few years ago. This Guide give a very detail insight on how to optimize the interactive governor on almost any device/any kernel/any rom (as long as you have root), and thats what i gonna try to apply to our device - if you want to check the guide yourself : HERE
so i take a look into Huawei Mate 10 Kernel Sources to see the voltage values being used by this processor for each frequency step. And here's the table :
{
"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"
}
from that table, we can see which frequencies are using most power, and where is the most jump in voltage usage happen when switching between frequency.
Higher voltage jump will cost more power, means less battery life.
in conclusion, i found few frequencies which are unfavorable, which is
A53 CPU :
1210Mhz - because it use same power (850000µV) as 1402Mhz, so we better use 1402Mhz instead for better performance with same power cost
1556Mhz - same story, it use same power (950000µV) as 1690Mhz
and
1844Mhz - it use most power, but since this is the top freq, we can neglect it
A72CPU :
1018&1210Mhz - use same power (780000µV) as 1364Mhz, so we better off jump directly to 1364Mhz
1498Mhz - same case, it use same amount of juice (900000µV) as 1863Mhz
and
2362Mhz - it use most power, but since this is the top freq, we can neglect it
_____________________________________________________________________________________________________________________________________________________
Now we take into account of the minimum frequency needed to ensure smooth task (if you dont know what am talking about, read the GUIDE i mention in my opening paragraph) :fingers-crossed:
For Mate 10, i've found the best frequency is as following :
Idle = 509MHz
Scrolling = 1018MHz (Use Chrome browser to scroll Facebook in desktop mode)
Video = 1402MHz (Play 1080p*60fps videos in Youtube app)
App load = 1690MHz (Use any app really)
High load = 1844MHz (Max out just in case)
Using the formula take from soniCron guide, i tried calculate optimum CPU load (this will be used as target load config) config for each frequencies
If you want to see the formulas :
Code:
We want to determine 2 values for every available clock rate: the maximal efficient load and the minimal efficient load. To make this determination, we need to bust out our calculators. (Or spreadsheets!)
For the maximal efficient load, we want to correlate a load value no higher than 90% of a given clock rate before it would be more efficient to jump to the next clock rate–to avoid overwhelming a particular rate while avoiding premature jumps to the next. For this value, we calculate it as:
(clock rate * 0.9) / next highest clock rate
For example, the maximal efficient load for 600Mhz on the Nexus 5X would be caluclated as:
(600000 * 0.9) / 672000 = 80.36% (rounded and normalized: 80)
For the minimal efficient load, we want to correlate a load value at which anything higher would be better served by a higher clock rate. To calculate this:
(1 - next highest clock rate / clock rate) * -1
For example, the minimal efficient load for 600Mhz on the Nexus 5X would be calculated as:
(1 - 672000 / 600000) * -1 = 12.00% (rounded and normalized: 12)
with this config, logically speaking we want to make the Governor to favour the "best" frequencies above, and minimize the usage of unfavourable freqs.
A53
Code:
509Mhz : 45
1018Mhz : 76
1210Mhz : 15
1402Mhz : 81
1556Mhz : 8
1690Mhz : 82
1844Mhz : 90
A72
Code:
682Mhz : 60
1018Mhz : 19
1210Mhz : 13
1364Mhz : 81
1498Mhz : 24
1652Mhz :12
1863Mhz : 80
2093Mhz : 12
2362Mhz : 90
Now that we already get the optimum number, time to apply it
Use your favorite Kernel Manager, in my case, am using Kernel Adiutor, and go to CPU Config - CPU Governor Tunables and input these value (am using Hawktail profile from soniCron thread, as it seems it work best for most of devices, and i already do trial & error with some other value like timer rate as well ) :
A53 (LITTLE)
Code:
go_hispeed_load: 99
above_hispeed_delay: 20000 509000:60000 1018000:25000
timer_rate: 28000
hispeed_freq: 509000
timer_slack: 80000
target_loads: 98 509000:45 1018000:76 1210000:15 1402000:81 1556000:9 1690000:82 1884000:90
min_sample_time: 30000
boost: 0
boostpulse_duration: 80000
A72 (BIG)
Code:
go_hispeed_load: 99
above_hispeed_delay: 20000
timer_rate: 20000
hispeed_freq: 1863000
timer_slack: 80000
target_loads: 98 682000:60 1018000:18 1210000:12 1364000:81 1498000:24 1652000:12 1863000:80 2093000:12
min_sample_time: 20000
boost: 0
boostpulse_duration: 80000
Now you can test it. Do full charge and use it normally, see whether you can see the improvement or not,
Hopefully it helps you as it seems to help me (you can expect no less than 7Hrs to 10 Hrs SoT, am quite heavy user myself, with 2 WhatsApp account and 1 LINE account constantly active. YouTube & Gaming at least hour/day as well). Discussion is more than welcome here, as these are considered an initial calculations that still yet to furtherly fine tuned for our CPU.

I'm not comfortable doing this on my phone yet, but I'm looking forward to hearing from people who are!

Results so far :

Used it and didnt notice any issues. Performance was perfect.
However, I just updated so I lost root.
Does anyone know if I can just root again without wiping stuff or not?

markvd90 said:
Used it and didnt notice any issues. Performance was perfect.
However, I just updated so I lost root.
Does anyone know if I can just root again without wiping stuff or not?
Click to expand...
Click to collapse
Try this one : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-root-preserve-user-data-t3716547

@otonieru
Isn't it Min Sample Rate value for Small Cores too extreme (30 000)?
On my Kirin960 I use Min Sample Rate valuse on Big and Small Cores at 90 000 and everything is still smooth, I am not gaming though. Huawei on Kirin960 uses Min Sample Rate at 80 000 stock...
Also I am turning on the Fast Ramp Down for Big Cores and Small Cores.
But my setting are more battery oriented and still I don't loose smoothness mate.

Tried the settings on my Mate 10. I see noticeable improvement on battery and performance. I haven't noticed any issue so far. Thanks for sharing.

This thread is underrated, therefore bump.
Tweaked my CPU settings a few days ago, and the difference in battery life is very noticeable, without any obvious loss of performance or fluidity.
Not gonna talk about numbers, because every single user has a different usage scenario, but if you are interested, I recommend you to at least try it, there's nothing to lose.
I can't understand why biggest OEM's won't put a bigger emphasis on optimizations of the existing, rather than on user unfriendly "innovations".

otonieru said:
I am using Hawktail profile from soniCron thread
Click to expand...
Click to collapse
Are you talking about Hawktail from here? https://androidfilehost.com/?w=files&flid=96527
Hawktail, Hawktail1.1 or Hawktail1.2 ?

badmania98 said:
Are you talking about Hawktail from here? https://androidfilehost.com/?w=files&flid=96527
Hawktail, Hawktail1.1 or Hawktail1.2 ?
Click to expand...
Click to collapse
I can say, none of it.
The base is hawktail indeed, but a mix of all those three + an adaptation to suit our 970 cpu better
You can go to sonicron thread to read more about each specific governor parameter and the hawktail profile itself

ytgbg said:
@otonieru
Isn't it Min Sample Rate value for Small Cores too extreme (30 000)?
On my Kirin960 I use Min Sample Rate valuse on Big and Small Cores at 90 000 and everything is still smooth, I am not gaming though. Huawei on Kirin960 uses Min Sample Rate at 80 000 stock...
Also I am turning on the Fast Ramp Down for Big Cores and Small Cores.
But my setting are more battery oriented and still I don't loose smoothness mate.
Click to expand...
Click to collapse
Well, it could be, but maybe not as well, LoL
I didnt really set those number to be a really battery oriented, as this phone already have huge battery to begin with, so even small improvement can do bigger impact.
i tried bigger number, but found it stutter a bit (at least to my liking) so, those are numbers that serve me best.
But of course everyone can re-tweak it to their liking

otonieru said:
I can say, none of it.
The base is hawktail indeed, but a mix of all those three + an adaptation to suit our 970 cpu better
You can go to sonicron thread to read more about each specific governor parameter and the hawktail profile itself
Click to expand...
Click to collapse
So, I have to download hawktail profile and modify it according to your values. Where do I copy the file and how I load it in Kernel Adiutor?
or
I have to modify the interactive governor with these values?

badmania98 said:
So, I have to download hawktail profile and modify it according to your values. Where do I copy the file and how I load it in Kernel Adiutor?
or
I have to modify the interactive governor with these values?
Click to expand...
Click to collapse
No no no, no need to download anything
You can simply input the governor value in the kernel adiutor. You need donate version btw.

On a new profile or over the interactive governor?

badmania98 said:
On a new profile or over the interactive governor?
Click to expand...
Click to collapse
Over the interactive,
Then you can save it as user custom profile

Done. Lets see the result.

applied it and now charging the phone. however one doubt tho. im using kernel adiutor as a user app and applied these settings. will these settings stay even if EMUI closes the kernel adiutor? (not talking about reboot since after reboot the profile needs to be applied again(?))
already selected kernel adiutor to run in background btw.

Saadkhalid786 said:
applied it and now charging the phone. however one doubt tho. im using kernel adiutor as a user app and applied these settings. will these settings stay even if EMUI closes the kernel adiutor? (not talking about reboot since after reboot the profile needs to be applied again(?))
already selected kernel adiutor to run in background btw.
Click to expand...
Click to collapse
It will stay until reboot even if you uninstall Kernel Adiutor. Just dont apply any setting that will affect CPU, like battery saver etc
It best to allow Kernel Adiutor to launch automatically, ignore batt optimisation and run in the background though.

otonieru said:
It will stay until reboot even if you uninstall Kernel Adiutor. Just dont apply any setting that will affect CPU, like battery saver etc
It best to allow Kernel Adiutor to launch automatically, ignore batt optimisation and run in the background though.
Click to expand...
Click to collapse
thanks. can i just turn power saver on from battery setting and then apply these values? just curious.