Database Develop

SetCPU/JuiceDefender advantage?

Is there any advantage to using these programs? I have both installed, but I'm not seeing too much of an increase in battery life. I've been unplugged since around 7am, and I'm down to 71% battery. Here are my settings below. Please chime in if I am doing something wrong, or if you have seen any advantage to using these programs. BTW - JuiceDefender says my battery is at x1.07, which seems awful low since I've seen people in the x2
SetCPU:
Main: 1000/400 | on demand
Charging/Full: 1000/800 | conservative
Battery < 50%: 800/400 | on demand
Battery < 20%: 400/400 | on demand *
Screen off: 200/200 | power save
*I notice when I'm on this setting, the phone becomes almost unbearably slow. Slow unlocking, slow wake up, and sometimes slow performance
JuiceDefender:
Timeout: N/A
Schedule: Enable data for 1m every 15m
Night: N/A
Battery: Keep data disable while below 15%
Traffic: Leave data enabled while > 50kb/15s
Peak: N/A
Apps: N/A
Screen: Leave data enabled while screen unlocked
Location: N/A
GPS off, Wifi off (most of the time, cause I cant seem to get a lock at work), and the only widgets I have on my screen are:
Google Search
Google Buzz
Maps
Abduction (game)
Google Talk
DoubleTwist
Power Manager
SetCPU
Beautiful Widgets (smaller home) - updates every 2 hours, but doesn't even seem to get the correct weather outside

When I had my phone set up well (prior to my stock i9000 flash) i was getting 1.79 better battery life.

The Most Power Efficient Kernel

So I'd like to gather some data to see which is the most battery efficient kernel.
To eliminate variances with 3G / Wifi / Brightness / ROMs / Battery size, I'd like to look at only the CPU power consumption, which is really the only thing a kernel changes. (That relates to power efficiency anyway.)
Now, how do we do this? Essentially we want to measure the power used by the CPU compared to the load placed on it.
Going to "Battery Use" we can see various %s that break down what uses what battery. And tapping on "Android System" leads to a screen with the "CPU Total" time. I believe this is a pretty accurate measurement of the amount of load the CPU has been placed under.
Now that we can find the load placed on it, we need to find how much power the CPU drew. Simply multiplying the "Android System"% by "Total time since unplugged" will give essentially how many minutes of power the CPU took up.
Now, dividing load by power consumed should give us, in effect, the "power efficiency."
For example, my numbers are:
10h 20m since unplugged. = 620 min
Android System: 11%
CPU Total: 7m 15s = 7.25 min
So, Android System used (620m)(11%) = 68.2 minutes of power.
Load = 7.25 min.
Load / Power = 7.25 / 68.2 = 0.10627
Step by Step-
1. Find time since unplugged. Find "Android System"%. Find CPU Total time.
2. Time since unplugged * "Android System"% = Power
3. CPU Total time = Load
4. Load / Power
5. Post along with kernel =]
If you guys are interested in doing a test, please:
Have the kernel flashed for at least 24 hours before doing the test. And have at last one complete discharge cycle. (Some say kernels need to "settle")
Set to 998/245, governor to on-demand. (Use SetCPU)
For HydraKernal, please go into Advanced and change Sampling Rate = 20000. Up Threshold = 95. Ignore Nice Load = 0, Powersave Bias = 0.
Run as long as possible (as low % as possible), and then do the calculation.
Please post:
Kernel
Load / Power ratio. (5 decimal places)

Adrynalyne's Battery.zip Kernel:
DQed. On-demand freezes.
Adrynalyne's Battery.zip Kernel(AOSP):
Hydra's SS Undervolt:
0.086993
KingKlick BFS #5:
KingKlickAOSP BFS #2:
Koush's Test:
0.68333
Stock:
Stock (Koush's):
Virtuous Custom Kernel:
PS Ordered alphabetically xD
PPS Higher is better. (More load for less power)

gmichaelow said:
Now that we can find the load placed on it, we need to find how much power the CPU drew. Simply multiplying the "Android System"% by "Total time since unplugged" will give essentially how many minutes of power the CPU took up.
Now, dividing load by power consumed should give us, in effect, the "power efficiency."
Click to expand...
Click to collapse
Where do you factor in the CPU frequency and voltage?

Doesn't it matter what max speed and governor we use.
I think we should all test w/ a max of 998MHz using the "on demand" with NO custom profile. (since every kernel/phone can do this)
Or, am I wrong?

daftlush said:
Doesn't it matter what max speed and governor we use.
I think we should all test w/ a max of 998MHz using the "on demand" with NO custom profile. (since every kernel/phone can do this)
Or, am I wrong?
Click to expand...
Click to collapse
The CPU clocks down when you turn the screen off (that's why music sometimes will skip shortly afterwards). Tasks that are using CPU time while the processor is clocked down (and using less voltage) will obviously take longer, but overall use less power (because of the lower voltage).
Some kernels have Conservative as the default governor; how would switching the profile to On Demand represent those kernels accurately?

If ur battery life sux, and you are on the latest radio, flash back to 07.28. I did that last night and have over 60% battery left 24hrs later.
Thanks jermaine151!

Ah, thanks for the feedback, I thought I might be forgetting something. Stock speed for anyone testing.
But I don't think the governor will matter. Conservative will take longer to scale up, and will have a lower CPU Total time, but will also have a lower power draw.
So I think the ratio will hold. In any case, if we get enough testers, we'll see xD

gmichaelow said:
But I don't think the governor will matter. Conservative will take longer to scale up, and will have a higher CPU Total time, but will also have a lower power draw.
Click to expand...
Click to collapse
Fixed it for you.
Higher CPU time but lower draw is not what your equation assumes.

larsrya8 said:
Fixed it for you.
Higher CPU time but lower draw is not what your equation assumes.
Click to expand...
Click to collapse
Ah, you sir are right.
How about we run everything exactly as the kernels come?
So basically, no using SetCPU. I think it's a reasonable assumption that the dev would make the kernel use whatever they thought best.
Perhaps in the future there will be room for a test with SetCPU, but for now, run everything w/o SetCPU.
Hmm, to remove OC variable, no OCed Hydras. Only SS undervolt.
How's that?

gmichaelow said:
How's that?
Click to expand...
Click to collapse
If 6 minutes of CPU time on one kernel isn't the same as 6 minutes of CPU time on another kernel (On Demand vs Conservate, etc), I don't know how you can compare the two using CPU time. I also don't have a different metric in mind

larsrya8 said:
If 6 minutes of CPU time on one kernel isn't the same as 6 minutes of CPU time on another kernel (On Demand vs Conservate, etc), I don't know how you can compare the two using CPU time. I also don't have a different metric in mind
Click to expand...
Click to collapse
No no, that's exactly what we are comparing! =]
We want to see how much power 6 minutes of CPU time is on various kernels, out of the box.
Sure, we're removing the aspect of SetCPU tweaking, but this will give an "out of the box" benchmark.
The whole point is that two kernels are going to perform differently. The question is which will come out ahead!

Not every Kernel has Conservative (koush.test and koush.test2) but i think all have on-demand.
Ultimately, we should compare all the kernels at different max speeds with all governors, but let's see if we can start with 998MHz on demand.
Also, I think it best to use SetCPU. We need to set/limit variables and SetCPU is the best way to do that.

daftlush said:
Not every Kernel has Conservative (koush.test and koush.test2) but i think all have on-demand.
Ultimately, we should compare all the kernels at different max speeds with all governors, but let's see if we can start with 998MHz on demand.
Also, I think it best to use SetCPU. We need to set/limit variables and SetCPU is the best way to do that.
Click to expand...
Click to collapse
This. Okay, so it's settled (mostly). 998MHz on-demand. But what about the min setting? Do you think all the min should be set to 245? Because adryalyne's kernels can have 128 as min.

gmichaelow said:
This. Okay, so it's settled (mostly). 998MHz on-demand. But what about the min setting? Do you think all the min should be set to 245? Because adryalyne's kernels can have 128 as min.
Click to expand...
Click to collapse
Yeah, 245 since every kernel has it.

daftlush said:
Yeah, 245 since every kernel has it.
Click to expand...
Click to collapse
All right, it's ALL settled now.
998/245. On-demand. And let the testing begin! =]
(Unless there's anything else?)

koush.test2: 245 min, 998 max, on-demand.
3h 15m since unplugged. = 195 min
Android System: 4%
CPU Total: 5m 20s = 5.33 min
So, Android System used (195m)(.04) = 7.8 minutes of power.
Load = 5.33 min.
Load / Power = 5.33 / 7.8 = .6833
I didn't "have the kernel flashed for at least 24 hours before doing the test. And have at last one complete discharge cycle" because I have never read that "kernels need to settle."

daftlush said:
koush.test2: 245 min, 998 max, on-demand.
3h 15m since unplugged. = 195 min
Android System: 4%
CPU Total: 5m 20s = 5.33 min
So, Android System used (195m)(.04) = 7.8 minutes of power.
Load = 5.33 min.
Load / Power = 5.33 / 7.8 = .6833
I didn't "Have the kernel flashed for at least 24 hours before doing the test. And have at last one complete discharge cycle" because I have never read that "kernels need to "settle."
Click to expand...
Click to collapse
Haha, yeah okay. Going up. Using 5 decimal places though =]

Great thread.. I hope we get tons of data soon..

Do you at the very least have the phone in airplane mode? There are several things under the "Android System" heading; on CyanogenMod for instance, Account and Sync Settings, Google Backup Transport, Network Location, etc are listed. What if Accounts and Sync fires up during one (and only one) of your kernel tests? Or Google Backup Transport? Or a weather widget requests your phone's location?
I notice you're using the percentage that Android System used, but you're not comparing it to any of the items that don't use CPU time (like the Display). Android System's percentage is going to change a lot if the Display (or WiFi, or GPS, or the Cell Radio, or a combination, etc) consumed 10% vs 80% of your battery. And if you're doing this on a Sense ROM, the percentages listed under Battery Use are wildly inaccurate anyway.
You're gathering data without knowing what that data even means.
But I'm done; just wanted to ensure that anyone who stumbles upon this thread (like TylerD004) aren't lead to believe that your results were derived scientifically, or are in any way accurate or useful

larsrya8 said:
Do you at the very least have the phone in airplane mode? There are several things under the "Android System" heading; on CyanogenMod for instance, Account and Sync Settings, Google Backup Transport, Network Location, etc are listed. What if Accounts and Sync fires up during one (and only one) of your kernel tests? Or Google Backup Transport? Or a weather widget requests your phone's location?
I notice you're using the percentage that Android System used, but you're not comparing it to any of the items that don't use CPU time (like the Display). Android System's percentage is going to change a lot if the Display (or WiFi, or GPS, or the Cell Radio, or a combination, etc) consumed 10% vs 80% of your battery. And if you're doing this on a Sense ROM, the percentages listed under Battery Use are wildly inaccurate anyway.
You're gathering data without knowing what that data even means.
But I'm done; just wanted to ensure that anyone who stumbles upon this thread (like TylerD004) aren't lead to believe that your results were derived scientifically, or are in any way accurate or useful
Click to expand...
Click to collapse
Hmm, I understand what you're saying. You think that, because some people will use use their phones more heavily one day than the other, that the data will be inconsistent?
I'm going to disagree. Because if I use my phone more, then I will have greater Load, but ALSO use greater Power. Thus, I believe the ratio will remain the same.
You pointed out that "Android System"'s % will wildly vary, but I think that's okay. It doesn't matter how much power anything non-CPU related uses, because that's not what we're measuring. I believe
(Time since unplugged) * (Android System %)
will always reflect how much power the CPU used, independent of anything non-CPU related. Sure, "Android System"% may be knocked down if "Cell Standby" sucks up like 50%. But a decreased (%) and an increased (time since unplugged) will come out the same I think.
Do correct me if I'm wrong?

Saving Battery Life

I have been making some changes to my Nexus One lately because I was having some battery life/drain problems.
Here is my current setup:
ROM: MIUI 1.11.11
Kernel: Tiamat_N1-v4.1.0
Radio: 5.12.00.08
WiFi Sleep Policy set to Never
Brightness is Automatic
Not that many apps installed; no rogue apps
I just listen to music, browse the internet, and occasionally play games. (Not 3D games that require a lot of resources, just casual stuff)
No, I have not calibrated my battery yet- I'll worry about it later.
Does anybody have some tips for how to help increase my battery life? Perhaps another kernel is better? etc
All help appreciated. If you have a question, feel free to ask and I'll get back to you ASAP.

You should change brightness from automatic because automatic will constantly work in the background to check if the screen needs to be brighter/dimmer.
Also get setcpu and use this basic setup:
Main Settings:
Scaling: On Demand
Max: 998
Min: 256
Profiles:
Screen off -> Scaling = On Demand, Max = 576, Min = 256
If you're listening to music while your screens off, you may want to bump up the Max to 614 for the screen off profile if you're experiencing slowness, if not keep it at 576.
That should help your battery last at least a 10% more relatively speaking.

Blue Sleep Fix ON/OFF Script with Discharge Rate Analyzer [04 Aug 2014]

“Bluesleep” is a wakelock error in the Bluetooth system which prevents Android devices from entering deep sleep, thus shortening battery life in sleep mode.
This error also affects wifi.
Wakelock: A kernel mechanism for Android power management. When a thread holds a wakelock, the kernel will refrain from entering a low-power state.
Click to expand...
Click to collapse
According to XDA threads (see References), Bluesleep Fix (BSF) greatly improves battery life on CM9 and CM10 ROMs by allowing your device to truly enter deep sleep.
BSF dates back to mid-2012 perhaps earlier. So I think most of the newer Atrix ROMs already incorporate BSF or some variation of it.
However my CM10 SuperLite V8 ROM does not (yet ). Also BSF may not be well known to all users. Or they may want to know how to quantify the improvement in battery life, if any that BSF yields.
So I tested BSF extensively using my new BSF ON/OFF script “bsf.sh” I developed on SuperLite and found that BSF greatly reduces battery discharge rate in sleep mode.
Link: http://www.mediafire.com/view/wqrhb9isx4rvjdh/bsf.sh
Features
My BSF script allows users to set BSF ON/OFF at run time and can be invoked via Script Manager, Terminal Emulator, ADB or other suitable app. There is no need to enter recovery, flash and reboot; however reboot is required for Android to recognize the modified permissions. My handy BSF ON/OFF script allows quick switching back to the legacy “root-only” permissions should BSF cause any adverse effects.
My BSF script also analyzes battery discharge rate by first time stamping the percentage charge level at launch. The difference in charge divided by dwell time T between launches yields estimated discharge rate in % per hour. Since the percentage “charge” is output as a whole number, and since two charge states are required to estimate rate, the uncertainty due to limited resolution is approximately 2/T % per hour. Thus for a dwell time of, say T=8 hours, this uncertainty is 2/8 = 0.25 % per hour.
Demo
BSF OFF
BSF ON
BSF NOOP (print usage instructions and current state)
Instructions
BSF ON/OFF can be launched many different ways. Like the demo, the method given here invokes ScriptManager (SManager) which is included in some CM10 ROMs including SuperLite. You must have root.
Push bsf.sh to internal or external memory, for example: /sdcard/Download
Launch SManager and select Menu > Advanced > Configuration > Home directory. Enter {path-to-bsf.sh} and “Select this directory”
At SManager command window, enter “sh bsf.sh”.
In the Argument field, enter 1 (for BSF ON), 0 (for BSF OFF) or blank to show current state
Press “Su” button to get superuser then press “Run”.
Once bsf.sh is launched, SManager stores all entered parameters as defaults for the next launch.
A reboot is required for the system to recognize the modified permissions.
When bsf.sh is launched with an argument of 1 or 0, battery statistics are printed and the estimated discharge rate is displayed in the right-most field. Negative sign indicates that the device was discharging on average during the past cycle.
BlueSleep Fix Technical Description
BSF is employed by setting the “setuid” bit (set user ID upon execution) via the UNIX command “chmod”. The setuid bit is an access rights flag that, when set, allows other entities (users, programs or apps) to run an executable with the permissions of that executable’s owner. For example:
chmod 04755 /system/xbin/hcitool
chmod 04755 /system/xbin/hciconfig
chmod 04755 /system/xbin/hcidump
Click to expand...
Click to collapse
The following legend shows how to interpret the bits and the corresponding permissions:
0: Indicates that following bits are octal
4: setuid ON
7 (binary 111): read-write-execute for owner (and others with setuid ON)
5 (binary 101): read-execute for group
5 (binary 101): read-execute for other
Click to expand...
Click to collapse
When you flash a ROM, the updater-script inside the ROM zip sets permissions for various files:
Code:
set_perm_recursive
sets permissions of a directory or set of directories and all files and folders within them. Syntax:
Code:
set_perm_recursive(uid, gid, dirmode, filemode, dir1, dir2 …)
where
uid = user id
gid = group id
dirmode = permission to set to directories contained within the specified directory
filemode = permission to set to files contained within the specified directory
dirX = directory to set permission on
Click to expand...
Click to collapse
In the following case:
Code:
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin")
the files are owned by root (numerically “0”) and the setuid bit is not set. Thus only root has elevated privileges. However when BSF is invoked, the setuid bit “s” is set and replaces the “x” (execute) bit for the owner (root), thus allowing apps to run Bluetooth executables with the same permissions as root ...
Code:
cd /system/xbin; ls -ld hci*
-rwsr-xr-x root shell 67144 2008-08-01 05:00 hciconfig
-rwsr-xr-x root shell 116564 2008-08-01 05:00 hcidump
-rwsr-xr-x root shell 35704 2008-08-01 05:00 hcitool
Performance Testing
I ran numerous BSF ON/OFF tests on CM10 SuperLite. Dwell times between consecutive launches of bsf.sh were generally 8 to 10 hours. The following results show estimated battery discharge rate in sleep mode: Display OFF, phone signal ON, WiFi switch ON, Bluetooth switch OFF and charger unplugged:
BSF OFF: 2.4% - 3.0% per hour
BSF ON: 0.6% - 1.0% per hour
Click to expand...
Click to collapse
With BSF OFF the average discharge rate was 2.7% per hour. However with BSF ON the average discharge rate was only 0.8% per hour. For example, after 12 hours of sleep time, I have an average 23% more charge with BSF ON:
(2.7 – 0.8) % per hour x 12 hours = 23% (sleep mode)
Click to expand...
Click to collapse
Operational test results: Starting from full charge, 56% charge still remains after 24 hours, including 8 hours of sleep and 16 hours of combined low-to-moderate use + sleep.
Final Thoughts
Newer ROMs may already have BSF. But for CM10 SuperLite, I have demonstrated that with BSF, battery discharge rate in sleep mode is reduced by 70% or more. Now I get almost two days of battery life with low to moderate use. Based on these results, I plan to roll BSF into my next version of SuperLite.
References
BSF Diagnosis: http://www.droidxforums.com/forum/d...sleep-fix-all-ics-roms-enable-deep-sleep.html
BSF Discussion: http://forum.xda-developers.com/showthread.php?t=1817424
Credits
Th3Bill (http://forum.xda-developers.com/member.php?u=4480697), author of bluesleep_fix based on settings from olegfusion. Thanks Bill

Thank you for sharing this, my doubt is:
¿How can I know if any particular ROM has BSF ON? (in case of AtrICS or CM10 from epinter)¿Only trial and error?, AtrICS has for me terrible battery duration.
Best regards

[KERNEL][TMO][TW5.0][06/22/2015] KT-SGS6 - OE3 - KTweaker

Ktoonsez presents:
{
"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"
}
​
KT-SGS6 kernel features
•Must have a S6 model G920F and G920I and G920S and G920T and G925F and G925I and G925S and G925T
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•Over Clocking
•Under Clocking
•KTweaker app for kernel control
•KTweaker Widgets
•KTmonitor app to watch your cpu cores current speed
Click to expand...
Click to collapse
KTweaker Shop and profile help, plus previous versions can be seen here (thanks to LuigiBull23):
http://forum.xda-developers.com/tmo...nel-kt-sgs6-builds-variants-ktweaker-t3107867
Touchwiz Lollipop 5.0 VERSION:
06.22.2015: http://bit.ly/1Jf6B2n
Click to expand...
Click to collapse
KTweaker Shop and profile help, plus previous versions can be seen here (thanks to LuigiBull23):
http://forum.xda-developers.com/tmo...nel-kt-sgs6-builds-variants-ktweaker-t3107867
Sources can be found here:
https://github.com/ktoonsez/KTSGS6
What you can expect to get benchmark wise with a good CPU OC'd:

Change Log 05.18.2015
1. Add some more protection on hotplugging for phones that are not fully shutting down screen and still register touch while screen is off, causing reboots.
2. Making unified version now, so pay attention that the file name is now changed. There is still seperate version for the S6 and S6 Edge, and also Sprint needs a special due to radical differences from the GSM versions.
3. KTweaker: Added new 3 options prompt when restoring a profile. Instead of a yes/no question to apply, it now gives you the 3 options of: "Apply restored profile with its voltage", "Apply restored profile with my voltage", "Do not apply it"
Change Log 05.12.2015
1. The wait is over for ktoonservative governor!!!!!!!!!!!!!!!!!!!!!!!!
2. ktoonservative governor supports hotplugging for some amazing battery life and still smoooooooooth.
3. Shorten internal kernel name so Antutu wont crash on some phones.
4. LED Fade mode code added.
5. LED fade mode fade up time to set how long it takes to fade in.
6. LED fade mode fade down time to set how long it takes to fade out.
7. Disable LED start hour to allow a start time of when LED are NOT active.
8. Disable LED stop hour to allow a stop time of when LED are NOT active.
9. Disable LED always option to disable LEDs all together.
10. Built with Linaro official 4.9 with -O3 optimizations
11. Added ktoonsified v1 profile made by myself and Luigibull, you can get it in the KTweaker shop in KTweaker app. BE SURE TO LOAD YOU STOCK VOLTAGE TABLE AFTER APPLYING!!!!!!!
Change Log 05.02.2015
1. Added UC and OC steps for both CPU's. Little now ranges from 200-1600 and big ranges from 200-2496. Be sure to adjust voltages accordingly, the UC and OC steps may not work properly for your binned CPU without tweaking the voltage!!!!!!!!!!!!!!!!!
2. Included patch to insure deep sleep is NOT lossed
2. KTweaker 9.3
3. Cleaned up some FC issues
4. GPU screen is now fully functional for all items
5. "Get Phone Information" screen was pretty'd up and added CPU "Time in State" gride for both little and big cpus including Deep Sleep and Total up Time items.
6. OTA is now functional.
7. KTweaker Shop for Profiles is now functional. Only 1 profiles which is the stock settings.
8. Change Log item in KTweaker is now functional.
Change Log 04.29.2015
1. Add voltage control for little and BIG CPU's. Thanks to AndreiLux for pointing me to the right files.
2. Added ondemand and conservative governor.
3. Added CPU Min/Max control for BIG CPU
4. Added ability to tweak governor adjustments.
5. GPU governor selection is working, dont mess with Min/Max yet.
Change Log 04.19.2015
1. First build, things are just getting started
2. Min/Max will look weird upon open KTweaker the first time, just slide the Min and Max bars to what you want, this is only setup for the SMALL CPU.
3. So far you can only control the SMALL CPU which is the cpu that ranges from 400-1500Mhz
4. Control over Scheduler.
5. Control over governor for SMALL CPU.
6. Kernel is setup for SELInux Permissive
7. Lots of dmesg spam removed.
8. Dont bother setting other items in KTweaker just yet since things are just getting started.
9. As with all custom kernels since the S4, you may need to find "securestorage" line in build.prop and change from true to a false if you have trouble with wifi remembering your password after reboots.
10. If you have trouble with S-Health after installing custom kernels, Force Stop it and clear cache/data for the app, that will usually take care of it.
11. Please post a "dmesg" after running the kernel for 10-15 minutes and you have let the phone go into deep sleep at least once so I can remove more dmesg spam.
12. ENJOY the awesome!!!!!!!!!!!!!!!

ktoonservative explained:
Any item with the word cycle in it refers to how many sampling_rate's have occured. A 22 ruffly equates to 1 second for a sampling_rate of 45000
block_cycles_offline_screen_off =1
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is OFF.
block_cycles_offline_screen_on = 11
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is ON.
block_cycles_online_screen_off = 11
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is OFF.
block_cycles_online_screen_on = 3
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is ON.
block_cycles_raise_screen_off = 11
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is OFF.
block_cycles_raise_screen_on = 3
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is ON.
button_boost_screen_off_core_1 = 1
When this item is a 1, it will turn on the core #1 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_1 = 1
When this item is a 1, it will turn on the core #1 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_2 = 1
When this item is a 1, it will turn on the core #2 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_2 = 1
When this item is a 1, it will turn on the core #2 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_3 = 1
When this item is a 1, it will turn on the core #3 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_3 = 1
When this item is a 1, it will turn on the core #3 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_4 = 1
When this item is a 1, it will turn on the core #4 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_4 = 1
When this item is a 1, it will turn on the core #4 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_5 = 1
When this item is a 1, it will turn on the core #5 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_5 = 1
When this item is a 1, it will turn on the core #5 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_6 = 1
When this item is a 1, it will turn on the core #6 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_6 = 1
When this item is a 1, it will turn on the core #6 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
button_boost_screen_off_core_7 = 1
When this item is a 1, it will turn on the core #7 when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
button_boost_screen_on_core_7 = 1
When this item is a 1, it will turn on the core #7 when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_hold_cycles = 22
How many sampling_rate cycles need to occur before going out of CPU/GPU boost mode
cpu_load_adder_at_max_gpu = 0
When set to higher than zero, this will add to the actual CPU load to create a perceived higher load when an app is using alot of GPU but not CPU.
cpu_load_adder_at_max_gpu_ignore_tb = 0
When set to 1, this will ignore cpu_load_adder_at_max_gpu during touch/button boost. When set to 0 cpu_load_adder_at_max_gpu will be used all the time.
disable_hotplug = 0
When this item is a 1, it disables hotplugging so all cores stay on full time. 0 lets all cores turn on and off when needed.
disable_hotplug_bt = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while paired to a bluetooth device and doing bluetooth activities like playing music, transfering files.... 0 doesn't do anything extra to the cores when doing bluetooth functions.
disable_hotplug_chrg = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while charging the device. 0 doesn't do anything extra to the cores while charging.
disable_hotplug_media = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while playing music or movies. 0 doesn't do anything extra to the cores while music or movies are playing.
down_threshold_screen_off = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is OFF.
down_threshold_screen_off_hotplug_1 = 40
A percentage of CPU utilization that needs to occur before the core #1 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the core #2 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_3 = 50
A percentage of CPU utilization that needs to occur before the core #3 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_4 = 55
A percentage of CPU utilization that needs to occur before the core #4 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_5 = 60
A percentage of CPU utilization that needs to occur before the core #5 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_6 = 65
A percentage of CPU utilization that needs to occur before the core #6 is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_7 = 70
A percentage of CPU utilization that needs to occur before the core #7 is taken offline while screen is OFF.
down_threshold_screen_on = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is ON.
down_threshold_screen_on_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the core #1 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_2 = 40
A percentage of CPU utilization that needs to occur before the core #2 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_3 = 45
A percentage of CPU utilization that needs to occur before the core #3 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_4 = 50
A percentage of CPU utilization that needs to occur before the core #4 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_5 = 55
A percentage of CPU utilization that needs to occur before the core #5 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_6 = 60
A percentage of CPU utilization that needs to occur before the core #6 is taken offline while screen is ON.
down_threshold_screen_on_hotplug_7 = 65
A percentage of CPU utilization that needs to occur before the core #7 is taken offline while screen is ON.
freq_step_lower_screen_off = 8
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is OFF.
freq_step_lower_screen_on = 2
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is ON.
freq_step_raise_screen_off = 1
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is OFF.
freq_step_raise_screen_on = 5
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is ON.
ignore_nice_load = 0
If this value is 1, the system will ignore "Nice" processes when deciding to scale up or down. Nice processes are used by the IO scheduler to designate a low-priority process. Ignore nice load basically tells a governor to disregard processes with higher nice values.
lockout_hotplug_screen_off_core_1 = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_on_core_1 = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_off_core_2 = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_on_core_2 = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_off_core_3 = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_on_core_3 = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_off_core_4 = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_on_core_4 = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_off_core_5 = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_on_core_5 = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_off_core_6 = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_on_core_6 = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_off_core_7 = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_hotplug_screen_on_core_7 = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_changes_when_boosting = 0
If this value is 1, all CPU changes to all cores will be ignored while executing a touch/button boost. If 0 all cores will be allowed to scale and hotplug.
no_extra_cores_screen_off = 1
When set to a 1, this option keeps all extra CPU cores offline while the screen is OFF. 0 lets it hotplug them on and off as needed
sampling_rate = 45000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is ON.
sampling_rate_min = 10000
READ-ONLY value that specifies the lower value that "sampling_rate" and "sampling_rate_screen_off" will accept.
sampling_rate_screen_off = 45000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is OFF.
super_conservative_screen_off = 0
With the screen OFF: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items.
super_conservative_screen_on = 0
With the screen ON: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items to create a smooooooth UI experience.
touch_boost_cpu_cl0 = 1200000
The Mhz that you want the online CPU's to jump to when the screen is touched for the the LITTLE CPU (Cluster 0).
touch_boost_cpu_cl1 = 1600000
The Mhz that you want the online CPU's to jump to when the screen is touched for the the BIG CPU (Cluster 1).
touch_boost_core_1 = 1
When set to a 1, this option turns on the core #1 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_2 = 1
When set to a 1, this option turns on the core #2 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_3 = 0
When set to a 1, this option turns on the core #3 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_4 = 0
When set to a 1, this option turns on the core #4 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_5 = 0
When set to a 1, this option turns on the core #5 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_6 = 0
When set to a 1, this option turns on the core #6 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_core_7 = 0
When set to a 1, this option turns on the core #7 when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_gpu = 424
This value specifies what Mhz the GPU should jump to when the screen is touched.
up_threshold_screen_off = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is OFF.
up_threshold_screen_off_hotplug_1 = 55
A percentage of CPU utilization that needs to occur before the core #1 is put online while screen is OFF.
up_threshold_screen_off_hotplug_2 = 60
A percentage of CPU utilization that needs to occur before the core #2 is put online while screen is OFF.
up_threshold_screen_off_hotplug_3 = 65
A percentage of CPU utilization that needs to occur before the core #3 is put online while screen is OFF.
up_threshold_screen_off_hotplug_4 = 70
A percentage of CPU utilization that needs to occur before the core #4 is put online while screen is OFF.
up_threshold_screen_off_hotplug_5 = 75
A percentage of CPU utilization that needs to occur before the core #5 is put online while screen is OFF.
up_threshold_screen_off_hotplug_6 = 80
A percentage of CPU utilization that needs to occur before the core #6 is put online while screen is OFF.
up_threshold_screen_off_hotplug_7 = 85
A percentage of CPU utilization that needs to occur before the core #7 is put online while screen is OFF.
up_threshold_screen_on = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is ON.
up_threshold_screen_on_hotplug_1 = 50
A percentage of CPU utilization that needs to occur before the core #1 is put online while screen is ON.
up_threshold_screen_on_hotplug_2 = 55
A percentage of CPU utilization that needs to occur before the core #2 is put online while screen is ON.
up_threshold_screen_on_hotplug_3 = 60
A percentage of CPU utilization that needs to occur before the core #3 is put online while screen is ON.
up_threshold_screen_on_hotplug_4 = 60
A percentage of CPU utilization that needs to occur before the core #4 is put online while screen is ON.
up_threshold_screen_on_hotplug_5 = 60
A percentage of CPU utilization that needs to occur before the core #5 is put online while screen is ON.
up_threshold_screen_on_hotplug_6 = 60
A percentage of CPU utilization that needs to occur before the core #6 is put online while screen is ON.
up_threshold_screen_on_hotplug_7 = 60
A percentage of CPU utilization that needs to occur before the core #7 is put online while screen is ON.

Can I test?

mikeyinid said:
Can I test?
Click to expand...
Click to collapse
Here you go man. This is just a test of mostly stock kernel, we are testing for Cell service, Wifi and deep sleep since that seems to be a common problem for anything custom on this device, so make sure you are getting deep sleep first before flashing:
Also, I really need that post your snuck on, lol. U know how to let me take that post over?
http://bit.ly/1ESQRPi

haha crap, i didnt realize you had just posted. i think a mod can switch it over to you, or just delete it.

mikeyinid said:
haha crap, i didnt realize you had just posted. i think a mod can switch it over to you, or just delete it.
Click to expand...
Click to collapse
All taken care of by my good friend @kennyglass . Flash the kernel and let me know what happens please

ktoonsez said:
All taken care of by my good friend @kennyglass . Flash the kernel and let me know what happens please
Click to expand...
Click to collapse
Flashed it, phone is deep sleeping. WiFi works, data works, usb works. no issues stand out yet.

mikeyinid said:
Flashed it, phone is deep sleeping. WiFi works, data works, usb works. no issues stand out yet.
Click to expand...
Click to collapse
Awesome. Use my app called KTweaker and open it up. Its a slide menu app like Play Store so slide from far left to the right to open the menu and click on "Utilities" then "Generate a dmesg" and post the file for me so I can kill all the dmesg spam and speed this beeach up

thanks man, glad to see you here i remember using your kernel during my s4 days
flashed it and its working great! just one thing. KTweaker is crashing upon starting the app

guaneet said:
thanks man, glad to see you here i remember using your kernel during my s4 days
flashed it and its working great! just one thing. KTweaker is crashing upon starting the app
Click to expand...
Click to collapse
Thanks man. Do you have root? Do you know how to get dmesg's and logcat's from your PC so I know whats crashing it if there is root installed already?

It crashes for me as well, flashed it with the XtreStroLite ROM.
Edit: Just noticed this page.
Yes, I do have root.
No, I don't know. Mind telling me how? I do have Windows and Ubuntu.
Edit2: No longer crashes after flashing the latest kernel.
Thanks!

Paradoxumical said:
It crashes for me as well, flashed it with the XtreStroLite ROM.
Click to expand...
Click to collapse
That doesnt help, look at my post above.

ktoonsez said:
Thanks man. Do you have root? Do you know how to get dmesg's and logcat's from your PC so I know whats crashing it if there is root installed already?
Click to expand...
Click to collapse
yeah i have the devices root with twrp, I wiped cache as well. i forgot how to get dmsg and logs from PC sorry. let me do some research and see what i can muster up

guaneet said:
yeah i have the devices root with twrp, I wiped cache as well. i forgot how to get dmsg and logs from PC sorry. let me do some research and see what i can muster up
Click to expand...
Click to collapse
Try redownloading, just updated source to OCV and changed a few flags, not sure if it will KTweaker, probably not but worth a shot.

wow, awesum to see you over here, man!
I'd be glad to test, but I have the s6Edge, not the S6, and the phones are just a bit different, and I've already bricked my phone once this week!

wase4711 said:
wow, awesum to see you over here, man!
I'd be glad to test, but I have the s6Edge, not the S6, and the phones are just a bit different, and I've already bricked my phone once this week!
Click to expand...
Click to collapse
Lol, ya, completely different phone :highfive:

ktoonsez said:
Awesome. Use my app called KTweaker and open it up. Its a slide menu app like Play Store so slide from far left to the right to open the menu and click on "Utilities" then "Generate a dmesg" and post the file for me so I can kill all the dmesg spam and speed this beeach up
Click to expand...
Click to collapse
I'll be glad to test this for you on the stock ROM with no mods and Deep Sleep *working*. I've searched everywhere for the stock kernel to revert back to in case of issues... No luck, any tips where to find it besides Samsung Opensource?
Edit nevermind, I'll make a backup, duh...

So I just flashed the file from the OP
"KT-SGS6-LP5.0-TW-G920T-04.17.2015.zip"
And it seems like it didn't actually flash. The kernel under info is still 3.10.61-4351281 built on March 27th.
Anybody else seeing this too? Looked in the ZIP and there's a boot.img, along with two modules. The update script looks right. Any ideas?
EDIT: redownloaded, this time the file is a different one, larger 13.5MB vs 11.9MB - this file includes KT Monitor and Tweaker. However, the kernel version is still the same as the old file (with a build date of 3/27)

Yep, I flashed the same OP link and check under about phone, same thing as stated above but the ktweaker app is installed sooo?? Assuming this is expected, I don't see any change in voice calling, wifi, lag etc.. Feels exactly the same so thats good.
Now, everytime I try to open Ktweaker it closes,cleared cache/data etc but no luck..??