Database Users

[7/09][TW][AOSP]Share Your Nemesis2all's Kernel Settings

Q&A:
What is Overclocking??
Overclocking is running the cpu, and possibly other system components like memory, faster than the speed for which it was rated. It's not something to take lightly as it's something that actually can physically damage the phone.
What is Undervolting?
If you are performing CPU intensive tasks, you reap the most benefit from the UV kernel because it needs less power to run at 1 GHz (or whatever the maximum clock speed is set to for that kernel).
If you spend alot of time idling, for instance reading interspersed by web requests, you are spending most of your time at the minimum clock speed. With the stock kernel, that is set to 0.1 GHz. With a UV kernel, the minimum clock needs to be set to something higher to keep the CPU running.
What in the hell is BFS/CFS???
CFS: Completely Fair Scheduler - The original process scheduler. CFS is better for multitasking, BFS is better for user interactions
BFS: Brain F**k Scheduler - The updated and improved process scheduler of CFS. The scheduler is designed to offer low latency when used interactively
What in the hell is Noop/SIO/Others???
NO-OP: This scheduler only implements request merging.
SIO: Simple I/O Scheduler - SIO is like a lighter version of deadline but it doesn't do any kind of sorting, so it's aimed mainly for random-access devices (like SSD hard disks) where request sorting is no needed (as any sector can be accesed in a constant time, regardless of its
physical location).
CFQ: Completely Fair Queueing - The CFQ scheduler has always tried to divide the bandwidth of each block device fairly among the processes performing I/O to that device; the time-sliced version goes further by giving each process exclusive access to the device for a period of time.
BFQ: Budget Fair Queueing - BFQ is a proportional share disk scheduling algorithm, based on CFQ, that supports hierarchical scheduling using a cgroups interface
{
"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"
}
BFQ vs CFQ
Slowest task's bw (MB/s) Fastest task's bw (MB/s)
-------------------------------------------------------------------
BFQ (2 files) 9.81 +/- 0.47 9.95 +/- 0.43
CFQ (2 files) 8.61 +/- 0.67 11.92 +/- 0.44
-------------------------------------------------------------------
BFQ (5 files) 4.29 +/- 0.10 4.31 +/- 0.09
CFQ (5 files) 4.01 +/- 0.17 5.24 +/- 0.14
__________________________________________________________________________________________________________________________________
The voltage settings are going to be differ by each of us, but sharing some of your settings will help the "New" or any people to find their stable settings.
Ex:
Kernel Type: TW/AOSP
OTB version: 1.1b/1.2b/etc
Scheduler: cfq/bfq/sio/Noop/Deadline/etc
Settings: Highest to Least
7/09
ASOP
OTB 2.6.35.13 CFS 0704
BFQ
1500: -0
1400: -0
1300: -0
1200: -50
1000: -75
800: -75
400: -100
200: -100
100: -125

bfq scheduler, clocked to 1120 Mhz
1120 : -25
1000 : -25
800 : -50
600 : -50
400 : -75
200 : -125
100 : -150
Stable for 36hrs

1400 - 50
1300 - 50
1000 -50
800-0
400- 50
200 - 50
100 - 200
Noop also
Thoes are my settings test settings as of today so far so good XD
Sent from my SCH-I500 using XDA App

CFQ Scheduler
1200 - 0
1000 - 25
800 - 25
600 - 50
400 - 50
200 - 50
Still testing more aggressive settings but this has been 100% stable for me.

SIO scheduler. Clocked at stock 1000 Mhz
1000 : -75
800 : -75
600 : -75
400: -75
200: -125
100: -150
Testing for stability now, but it seems to be working great for now.

Its kinda weird but when I first flash the OTB I am not able to run voltages as low as I can after a few hours. Makes no sense to me but whatever.
My 100% of the time fail safe settings are:
1300 -75
1200 -25
1000 -50
800 -50
400 -75
200 -75
100 -75
With the above its always been perfect. Now as aforementioned after a short while I can adjust to these following voltages:
1300 -75
1200 -50
1000 -75
800 -75
400 -100
200 -125
100 -125
But again oddly if I try testing these right after a fresh kernel install I get some kind of freeze/lock up issue.
As always YMMV and truly you need to find what is stable for your own phone and the only way to do that is thru individual testing.
In terms of the scheduler I was mostly using cfq since OTB came out for voltage control but I have played with SIO and BFQ. IMO there is not a tangible difference

So what is the difference between the different schedulers? I see some people use SIO and some use CFQ. Is there a place I can go to read up on the differences?

xceebeex said:
So what is the difference between the different schedulers? I see some people use SIO and some use CFQ. Is there a place I can go to read up on the differences?
Click to expand...
Click to collapse
From the community rom thread:
http://forum.xda-developers.com/showpost.php?p=13209379&postcount=247

saps said:
From the community rom thread:
http://forum.xda-developers.com/showpost.php?p=13209379&postcount=247
Click to expand...
Click to collapse
Awesome, thanks. It is hard to find information in that thread with it being so long now
So BFQ is "supposed" to be the best, but it is one of those things where YMMV I am assuming.

BFQ Scheduler
1300 -75uv
1200 -50uv
1150 -50uv
800 -75uv
400 -75uv
200 -100uv
100 -150uv
Running good for a day!
Will update as I go.

xceebeex said:
Awesome, thanks. It is hard to find information in that thread with it being so long now
So BFQ is "supposed" to be the best, but it is one of those things where YMMV I am assuming.
Click to expand...
Click to collapse
Yeah YMMV always. In quadrant tests I get the highest IO scores with sio actually. Mind you its just a few dozen points higher which translates into just a few points higher overall. But it is consistently just a tad bit better than bfq and cfq which are dead end on my phone. After using cfq the past week Im currently on bfq since supposedly thats the one to have. In the end I believe it makes little difference

saps said:
Yeah YMMV always. In quadrant tests I get the highest IO scores with sio actually. Mind you its just a few dozen points higher which translates into just a few points higher overall. But it is consistently just a tad bit better than bfq and cfq which are dead end on my phone. After using cfq the past week Im currently on bfq since supposedly thats the one to have. In the end I believe it makes little difference
Click to expand...
Click to collapse
For general purpose phone use CFQ and BFQ are best, SIO is non time critical and only suitable for single purpose imbedded applications such as dedicated flash controllers where latency had much less importance than data throughput.
If audio and video causing hangs or stutters then CFQ or BFQ are absolutely required.

how are the stock settings on this kernel? UV? how much?
if i don't change anything is it a stock kernel or is there some inherent changes already built in?

saps said:
Its kinda weird but when I first flash the OTB I am not able to run voltages as low as I can after a few hours. Makes no sense to me but whatever.
My 100% of the time fail safe settings are:
1300 -75
1200 -25
1000 -50
800 -50
400 -75
200 -75
100 -75
With the above its always been perfect. Now as aforementioned after a short while I can adjust to these following voltages:
1300 -75
1200 -50
1000 -75
800 -75
400 -100
200 -125
100 -125But again oddly if I try testing these right after a fresh kernel install I get some kind of freeze/lock up issue.
As always YMMV and truly you need to find what is stable for your own phone and the only way to do that is thru individual testing.
In terms of the scheduler I was mostly using cfq since OTB came out for voltage control but I have played with SIO and BFQ. IMO there is not a tangible difference
Click to expand...
Click to collapse
I used these settings and have only had one freeze up (when using the camera and clicking on the preview tab). Thing FLIES.

I actually underclocked mine a little to 800. I prefer the battery life I guess.
800-50
600-75
400-75
200-125
100-125
Battery life still wasn't great lol
I switched over to a Peanut Butta Jelly Time kernel though at the moment to test that out.

gevis said:
I actually underclocked mine a little to 800. I prefer the battery life I guess.
800-50
600-75
400-75
200-125
100-125
Battery life still wasn't great lol
I switched over to a Peanut Butta Jelly Time kernel though at the moment to test that out.
Click to expand...
Click to collapse
Make sure after you find the voltage profile you like you reset the batt stats after you fully charge the battery
Sent from my SCH-I500 using XDA Premium App

Since i can not post in the DEV forum yet:
Thanks for this ROM, I upgraded from SC 2.9.2 and i am blown away by this fantastic, well built and fast ROM!
So once again thank all of you for all of your hard work!

saps said:
Make sure after you find the voltage profile you like you reset the batt stats after you fully charge the battery
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
thanks for that... didn't think about that

Anybody have updates with V1.3 they can share?

I use:
800-75
600-75
400-75
200-75
Underclocked, but the phone is still pretty snappy, and the battery life is awesome. My phone doesn't like 100mhz so I only go down to 200. Now what is this about wiping batt stats?

Glitch kernel - LiveOC / Custom Voltage - HOW-TO - Settings sharing

LiveOC and Custom Voltage guide by TkGlitch
for Glitch kernel V14
{
"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"
}
Warning!
Overclocking is dangerous and is meant only for experienced users!​
1- Introduction :
The "normal" overclocking system on SGS til now was the addition of some frequency steps past the stock 1GHz step. V13 kernel was using 7 overclocked steps
to push the maximum selectable speed to 1.7GHz.
In V14, less overclocked steps are present, but you can still overclock to 1.7GHz if you want (and if your phone is able to do it), and even up to 2.25GHz as a maximum.
You will need NSTools to use LiveOC and custom Voltage features in Glitch kernel V14.
To begin with, I'll explain you some basic things you have to know.
2- Clocks :
The CPU speed is the result of a bus speed and a multiplier.
Bus speed is linked to and equal to GPU and RAM speed.
The multiplier is per step and hardcoded by the kernel developer.
It does look like that : CPU speed = bus speed x multiplier.
Here are my values in V14 :
1500 MHz = 200 x 7.5
1400 MHz = 200 x 7
1300 MHz = 200 x 6.5
1200 MHz = 200 x 6
1000 MHz = 200 x 5
800 MHz = 200 x 4
400 MHz = 200 x 2
200 MHz = 200 x 1
100 MHz = 100 x 1
LiveOC gives you the access to direct and on-the-fly bus overclocking by 1% steps (150% being the maximum available). I'll say it again : BUS overclocking !
Though, it'll overclock the bus on all the steps at the same time, for the same percentage.
We'll talk about that later.
So if I want to overclock my 1GHz step to 1.1GHz, I'll have to select 1GHz as max frequency, and push LiveOC to 110%.
My bus speed beeing overclocked by 10% will give the following :
220 x 5 (1GHz multiplier) = 1100 MHz.
If you want to go higher than 1.5GHz, it's the same :
Set 1500 MHz as maximum frequency (for example), and push LiveOC. Let's say to 110%. You will get the following :
220 x 7.5 (1.5GHz multiplier) = 1650 MHz.
Pushing it to 114% will give 1710 MHz (228MHz bus) and so on, up to 150% giving 2250 MHz running an inachievable 300MHz bus.
SINCE V14 BETA 6, 100, 200 and 400 MHz steps won't be affected by LiveOC. It should help to stabilize your overclock in most cases.
3- The limits :
THE MAIN LIMIT AND PHONE KILLER IS HIGH TEMPERATURE. WARM IS OK, HOT IS TOO HOT. DON'T PLAY STUPID.
Obviously, so much control over the bus speed, frozen til now to what the kernel developer set, will also give you the ability to find the limits of your chip.
The main clocking limit is generally the RAM, corrupting itself when the bus speed is too high. And since the GPU uses the RAM as well, it'll become crashy too. That's why I have decided to add some steps with a bigger multiplier, to lower the bus for a higher CPU frequency.
The bus speed limits for you will be anywhere between 240 and 270 Mhz, depending on your device potential (higher and lower exists but rare).
Average is 240 MHz.
The CPU speed limits will be anywhere between 1300 and 1800 MHz (higher and lower exists but rare as well).
Average is 1400 MHz.
With that in mind, I wouldn't go too far past 130% (giving 260MHz bus speed).
4- The sweet spot :
What you want when overclocking is to get the best balance for each part. Since the bus is linked to RAM and GPU, you obviously want it as high as possible for gaming, video playing, web browsing etc. (even more now with GPU acceleration in Android 4.0+). Though, as you know already if you've read this guide til now, all steps in V14 are using the stock 200MHz frequency.
So what to do if I want a lower CPU speed with a higher bus/GPU speed ? Simple ! Just select a lower frequency step as starting point.
Let's say we want 250 MHz bus speed, so we'll use 125% LiveOC :
Using 800MHz step, you'll get 1GHz.
Using 1GHz step, you'll get 1.250GHz.
Using 1.2GHz step, you'll get 1.500GHz.
Using 1.3GHz step, you'll get 1.625GHz.
Using 1.4GHz step, you'll get 1.750GHz.
Using 1.5GHz step, you'll get 1.875GHz.
5- The issues :
With a new overclocking system obviously comes some new problems related to it.
With the ability to fine tune the frequencies, you'll find that some frequencies are buggy somewhat, giving low performances. For example, using 115% Live OC with the 1.3GHz step will give some poor performances, when 114 and 116% won't. It could be a NSTools issue, but I think it has more to do with the hardware. It's well known that on CPUs some frequencies or even frequency ranges can be buggy, unstable, or slow. If you encounter that, try to add or remove a percent to LiveOC.
As said earlier, LiveOC will overclock the bus for all steps at the same time by the same amount of %.
Knowing that, you'll have to adapt your voltages for all the frequencies to stay stable, and this for any sensible change on LiveOC percentage.
6- Custom Voltage :
What would be LiveOC without Custom Voltages ?!
I did add leakage values to Glitch kernel features when I saw that some phones were overclocking much better with the right balance between ARM and Int voltages, depending on the phone, with very different results. The leakage value was basically that : balance between the two.
Well, as you probably know if you did read the changelogs, you have now the capacity to overvolt/undervolt both the ARM voltage (the CPU voltage you know well already), and the Int (internal) voltage. The last one is the voltage going to the GPU/memory controller, and will need to be tweaked accordingly to your phone.
As a starting point, here are the Int voltage values I was using for each leakage, adapted for V14 new frequency table :
HIGH LEAKAGE :
1500 : 1.225
1400 : 1.200
1300 : 1.175
1200 : 1.150
1000 : 1.125
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
MEDIUM LEAKAGE :
1500 : 1.200
1400 : 1.175
1300 : 1.150
1200 : 1.125
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
LOW LEAKAGE :
1500 : 1.175
1400 : 1.150
1300 : 1.125
1200 : 1.100
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
Of course, using LiveOC will force you to change these voltages accordingly.
Here are some advices about this :
- Try to stay around 1.225 - 1.250V for your highest frequencies;
- Try not to ever go past 1.300V if you don't want to kill your phone quickly;
- Be VERY gentle when tweaking it as it is VERY sensitive;
- Try to follow a more or less linear curve for Int voltage on OC frequencies;
- Going below 1.000V on 100MHz step will generally kill stability with no battery gain.
This guide may change depending on my decisions related to the Glitch kernel development, or to polish / add things to it.
Thanks to Ezekeel from Nexus S section for these awesome tools.
LiveOC : http://forum.xda-developers.com/showthread.php?t=1288015
Custom Voltages : http://forum.xda-developers.com/showthread.php?t=1331610
23/01/2012 - UPDATED TO REFLECT V14-B1 CHANGES.
09/02/2012 - UPDATED TO REFLECT V14-B3 CHANGES.
24/03/2012 - UPDATED TO REFLECT V14-B6 CHANGES.

Reserved. Just in case.

Awesome, this new LiveOC system really is something else.

Thanks Glitch. This is a really great and comprehensive guide from which many people will benefit.

Bow to tk-glitch. new year gift by glitch .

My 'love' oc value is 110% with Max over clock to 1320 MHz and min to 110 MHz and governed on on demand.
I didn't touched arm voltages
My int voltages are as follows:-
Max- 1225
1400-1200
1304-1175
1200-1125
1000-1100
800-1075
400-1050
200-1025
100-1000
Phone is pretty damn stable on these frequencies , I was facing some instability earlier but not now. Phone is dancing on my fingers, but will this effect battery a lot. Tk-glitch did I did it correctly or anything else have to be done??

@BHuvan goyal : Looks good to me

Tk-Glitch said:
@BHuvan goyal : Looks good to me
Click to expand...
Click to collapse
Will test at different frequencies from time to time and will report here once build 12 comes out as build 11 has some minor problems. Btw I accidentally went up to 150% and screen started to display weird lines ( horizontal ) and phone rebooted but that's bound to happen as I know that was at maximum.

As said, the bus limits are around 250 MHz for most phones, so with 150% pushing it to 300 MHz (and even more on the 1.3GHz step) your device will instantly freeze or crash
~ 130% is around the hardware limits

So what is the best method to save energy? Lower int and/or arm voltages?
"- Going below 1.000V on 100MHz step will generally kill stability with no battery gain."
Does it makes sense to lower arm voltage on 100mhz if >1V int causes instability?

Underclock and lower ARM voltage (both). If you only lower voltage, or only underclock, the gains will be poorer.

I just want to undervolt (same performance, lower energy consumption), but I'm not sure how to find the lowest arm and int voltages.
Frist int, then arm? I guess balance is the problem^^
just testing, not stable:
100-1000mhz, 100% live OC; int 1000/1000/1000/1000/1050; arm 850/875/1000/1175/1250
100-1000mhz, 100% live OC; int 1000/1000/1000/1000/1050; arm 800/800/950/1125/1200
frist arm, then int.. for tomorrow

reborn90 said:
I just want to undervolt (same performance, lower energy consumption), but I'm not sure how to find the lowest arm and int voltages.
Frist int, then arm? I guess balance is the problem^^
just testing:
100-1000mhz, 100% live OC; int 1000/1000/1000/1000/1050; arm 850/875/1000/1175/1250
100-1000mhz, 100% live OC; int 1000/1000/1000/1000/1050; arm 800/800/950/1125/1200
Click to expand...
Click to collapse
First arm, then int.

Thanks for the amazing kernel and the OC/UV options to puch our silicon to it's limits!
Question...
f.e.
I can change Max CPU freq to 1200 MHz with no other adjustments to voltage or Live OC and system is totally stable (can even go all the way to 1300 MHz without changing voltages, stable)
or
I can change Live OC Value to 115 % with no other adjustments to voltage and Max CPU freq set to 800 and system is totally stable. (CPU will be 920 MHZ and GPU 230 MHz)
but
When I change both to let say Live OC Value to 115 % and CPU freq set to 1000
the system becomes unstable (CPU will be 1150 MHz and GPU 230 MHz)
So I can run my CPU at an even higher freq then 1150 MHz totally stable but not together with Live OC (separately also totally stable). What's the catch? I even tried 114 % 116% 113% but can't get it stable together (separately no problem). Also some suggestions on voltage settings (Int) would be nice to see... Thanks again
-Sam-

@SamHaLeKe :
As you guessed, it's probably the Int voltage causing problems. Push it a bit (let's say 0.050V), and see if it's any better. It's obviously not the CPU freq causing problem, but more probably the bus freq. BTW, stock ARM voltage for 1GHz could be too low for 1150MHz, so pushing it a bit, towards 1.3V, should help too.
Good luck.

Tk-Glitch said:
@SamHaLeKe :
As you guessed, it's probably the Int voltage causing problems. Push it a bit (let's say 0.050V), and see if it's any better. It's obviously not the CPU freq causing problem, but more probably the bus freq. BTW, stock ARM voltage for 1GHz could be too low for 1150MHz, so pushing it a bit, towards 1.3V, should help too.
Good luck.
Click to expand...
Click to collapse
Thanks for the quick answer. The strange thing is that separately it's working perfectly fine without changing any voltages. Like I said, separately I can go all the way to 1200 MHz CPU freq without changing ARM voltage and system is totally stable (I have a good silicon...). So there is no need to push my voltage for 1150 MHz and I already tested that option. Also bus freq is working fine separately but not together with changing CPU freq. Adding voltage for bus freq makes it even unstable, while it is working stable when changing bus freq separately on default Int. voltages. Very strange but will sertainly do more testings and find the sweet spot....
Thanks again
-Sam-

I noticed a strange behavior when I was testing a new frequency. For example 400mhz:
min 100mhz max 400mhz, stock int V; the phone freezes with >1V if I try to wake it from idle, but it passes every stress test (performance gov.) with >1V..

SamHaLeKe said:
Thanks for the quick answer. The strange thing is that separately it's working perfectly fine without changing any voltages. Like I said, separately I can go all the way to 1200 MHz CPU freq without changing ARM voltage and system is totally stable (I have a good silicon...). So there is no need to push my voltage for 1150 MHz and I already tested that option. Also bus freq is working fine separately but not together with changing CPU freq. Adding voltage for bus freq makes it even unstable, while it is working stable when changing bus freq separately on default Int. voltages. Very strange but will sertainly do more testings and find the sweet spot....
Thanks again
-Sam-
Click to expand...
Click to collapse
Default voltage is higher @ 1.2 than @ 1GHz. It won't magically change because you did use LiveOC.
reborn90 said:
I noticed a strange behavior when I was testing a new frequency. For example 400mhz:
min 100mhz max 400mhz, stock int V; the phone freezes with >1V if I try to wake it from idle, but it passes every stress test (performance gov.) with >1V..
Click to expand...
Click to collapse
To get one isolated step stable is one thing, to get it stable with others is another story. Nothing strange in that, it's as old as the world of clocks ^^

please share your settings which is good in performance.... Im already blurred...
Sent from my GT-I9000 using Tapatalk

DaxIΠFIΠITY said:
please share your settings which is good in performance.... Im already blurred...
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Try the once that I use, first page 5 or 6th post. My phone is blazing fast.

Defy Overclock. I can't go above 1000mhz

I'm on PVL-StockPlus based on 4.5.1-134_DFP-231. I came here by restoring PVL-StockPlus system over 4.5.1-134_DFP-231 modded by walter.
I have 4.5.3-109_DPP-11 kernel (I still here from MS2Ginger 3.0, that I had before these two).
Now, the problem is that I can't set custom overclock values. The cpu clock moves between 300mhz-600mhz-1000mhz regardless any overclock.conf setting.
Here is my overclock.conf
Code:
enable 1
load_all 1
scaling 2
clk1 300
clk2 600
clk3 850
clk4 1100
vsel1 20
vsel2 30
vsel3 45
vsel4 62
con_up_threshold 80
con_down_threshold 20
con_freq_step 5
con_sampling_rate 160000
int_min_sample_rate 50000
ond_up_threshold 86
ond_sampling_rate 50000
smt_min_cpu_load 20
smt_max_cpu_load 80
smt_awake_min_freq 200000
smt_sleep_max_freq 200000
smt_up_min_freq 1000000
smt_wakeup_freq 1000000
smt_ramp_up_step 200000
EDIT: The problem isn't go above 1000mhz, is with any setting. I try lowering vsel3 and vsel4 below 1000mhz and any cpu monitor shows 300-600-1000 frecuencies. I can't manage frecuencies and vsels. It's stuck at 300-600-1000.

EtaCarinae said:
I'm on PVL-StockPlus based on 4.5.1-134_DFP-231. I came here by restoring PVL-StockPlus system over 4.5.1-134_DFP-231 modded by walter.
I have 4.5.3-109_DPP-11 kernel (I still here from MS2Ginger 3.0, that I had before these two).
Now, the problem is that I can't set custom overclock values. The cpu clock moves between 300mhz-600mhz-1000mhz regardless any overclock.conf setting.
Here is my overclock.conf
Code:
enable 1
load_all 1
scaling 2
clk1 300
clk2 600
clk3 850
clk4 1100
vsel1 20
vsel2 30
vsel3 45
vsel4 62
con_up_threshold 80
con_down_threshold 20
con_freq_step 5
con_sampling_rate 160000
int_min_sample_rate 50000
ond_up_threshold 86
ond_sampling_rate 50000
smt_min_cpu_load 20
smt_max_cpu_load 80
smt_awake_min_freq 200000
smt_sleep_max_freq 200000
smt_up_min_freq 1000000
smt_wakeup_freq 1000000
smt_ramp_up_step 200000
EDIT: The problem isn't go above 1000mhz, is with any setting. I try lowering vsel3 and vsel4 below 1000mhz and any cpu monitor shows 300-600-1000 frecuencies. I can't manage frecuencies and vsels. It's stuck at 300-600-1000.
Click to expand...
Click to collapse
Have you tried setVsel, good overclocking tool, worked for me on every rom.
defy @ 1200mHz 64vSel...

are you using recovery for overclocking, if yes then make sure that the first option is set to ENABLE or it will only use stock settings.also try setvsel.
Sent from my MB525 using xda premium

Watch this post http://forum.xda-developers.com/showthread.php?t=1645086
Sent from my MB526 using XDA

Battery Optimized on S3 with Siyah Kernel

Battery Optimazatin
Disclaimer alert: I am in no way responsible for any damage inquired while performing any of the changes listed below. This is just an option and it is something I have tried on S3 i9300 international version with success. Results will vary depending on your device
I have NeatRom Lite v1.1 + Siyah Kernal installed on my phone. Samsung's stock kernal has been replaced by Siyah's kernal SGS3v.1.8.4. To tweak the kernal, I installed STweaks (from the market).However if you feel bold you can tweak the kernal using STweaks and also tweak the governor (I am using peqasusq as my defualt governor). Additional tweaks for performance and gamers are avaliabe to Siyah S3 i9300 thread (http://forum.xda-developers.com/showthread.php?t=1709686). Governor tweaks can be performed either via a script in init.d or by SetCPU. I assume kernels with peqasusq can be tweaked with the settings below ( have not tried it out yet). These are my settings below ( they are by no means a rule of thumb). Note if you experience reboots while UV CPU ( try -50Mv or -75Mv).
STweaks settings can now be saved using a STweaks Profiles app by Droidphile (http://forum.xda-developers.com/showthread.php?t=1179809)
Battery Saving Tips
The screen causes excessive battery drain. You will need to reduce your screen brightness to about 30-40% instead of being at automatic.
Disable hepatic feedback
Use a dark back ground. Using a live wall paper wil also drain your battery
Turn WiFi off
GPS or location by network off ( use GPS only when needed)
There are other factors that affect battery consumption on your phone, these includes AutoSync Mail, apps like facebook, Whatsapp, Google + and Maps. You can disable auto sync feature for your gmail or get a better email app. Autostarts App can be used to disabe certain apps from autostarting. Cautiously disable apps, if in doubt don't touch it.
To get an idea of what is causing battery drain (Wakelocks), I suggest downloading Better Battery from the play store (Paid app) and view a dumpfile after 1-4 hours of your phone on idle. Once you have BBS you can determine what you want to disable or enable. If you need additional help reading the file you can head over to BBS thread (http://forum.xda-developers.com/showthread.php?t=1179809)
How to use Autostarts
Once you have this app, you can prevent some of the programs/operations from auto starting even when not in use.
Select the meu option and choose group by application
You can go down the list of apps and disable the notorious apps that you find running during auto starts (Maps, Google+, Facebook, Whatsapp). Here is Karpfenhai's example of how to disable Maps.
I have also disabled apps that auto start when connection changes, power disconnections. Disable apps or background operations can be enabled anytime.
Please note, some might cause havoc when disable do this with caution.
STweaks Settings
Quad Core Setting
SETTINGS (CPU):
CFS (Settings) GENTLE_FAIR_SLEEPERS = On
CPU IDLE Mode = IDLE+ LPA (default)
SCHED_MC = 0
CPU Undervolting = -100mV ( -75 if your phone freezes or reboots)
Max CPU Lock = Quad Core mode
Default CPU Governor = pegasusq
Scaling Max Freq = 1200Mhz
Scaling Min Freq = 200Mhz
SETTINGS (GPU freq):
GPU Freq Step 1 = 108Mhz
GPU Freq Step 2 = 160Mhz
GPU Freq Step 3 = 266Mhz
GPU Freq Step 4=300Mhz
GPU Freq Step 5=333Mhz
SETTINGS (GPU voltages):
GPU Voltage Level 1 = 825mV
GPU Voltage Level 2 = 850mV
GPU Voltage Level 3 = 875Mv
GPU Voltage Level 4 = 900mV
GPU Voltage Level 5 = 925MV
GPU Thresholds
GPU Threshold 1 Up = 70
GPU Threshold 2 Down =60
GPU Threshold 2 Up=70
GPU Threshold 3 Down=55
GPU Threshold 3 Up=80
GPU Threshold 4 Down=65
GPU Threshold 4 Up=80
GPU Threshold 5 Down=75
SCREEN
Touch Boost Level =600MHz (If there is lag try 700MHz)
Default CPU Scheduler = sio/Deadline
Init.d Tweaks
echo "80" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold
echo "60000" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate
echo "2" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor
echo "5" > /sys/devices/system/cpu/cpufreq/pegasusq/down_differential
echo "10" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_step
echo "10" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_up_rate
echo "20" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_down_rate
echo "300000" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_for_responsiveness
echo "50" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold_at_min_freq
echo "400000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_1_1
echo "300000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_2_0
echo "400000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_2_1
echo "300000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_3_0
echo "1000000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_3_1
echo "400000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_4_0
echo "150" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_1_1
echo "150" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_2_0
echo "250" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_2_1
echo "200" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_3_0
echo "400" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_3_1
echo "300" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_4_0
echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/io_is_busy
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/max_cpu_lock
note script is only for quad core settings, if used for dual core may cause fast battery drain
Click to expand...
Click to collapse
Dual Core Settings This will should give you more battery savings
SETTINGS (CPU):
CFS (Settings) GENTLE_FAIR_SLEEPERS = On
CPU IDLE Mode = IDLE+ LPA (default)
SCHED_MC = 0
CPU Undervolting = -100mV ( -75 if your phone freezes or reboots)
Max CPU Lock = Dual Core mode
Default CPU Governor = pegasusq
Scaling Max Freq = 1000Mhz
Scaling Min Freq = 200Mhz
SETTINGS (GPU freq):
GPU Freq Step 1 = 108Mhz
GPU Freq Step 2 = 160Mhz
GPU Freq Step 3 = 200Mhz
GPU Freq Step 4= 266Mhz
GPU Freq Step 5=300Mhz
SETTINGS (GPU voltages):
GPU Voltage Level 1 = 825mV
GPU Voltage Level 2 = 850mV
GPU Voltage Level 3 = 875Mv
GPU Voltage Level 4 = 900mV
GPU Voltage Level 5 = 925MV
GPU Thresholds
GPU Threshold 1 Up = 70
GPU Threshold 2 Down =60
GPU Threshold 2 Up=70
GPU Threshold 3 Down=55
GPU Threshold 3 Up=80
GPU Threshold 4 Down=65
GPU Threshold 4 Up=80
GPU Threshold 5 Down=75
SCREEN
Touch Boost Level =600Mz (If you experience a lags try 700Mhz)
Default CPU Scheduler = sio/Deadline
Click to expand...
Click to collapse
Images
{
"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"
}
Special thanks to
Siyah for the kernel
Droidphille for correcting my initial governor tweaks
Sale for Neat Rom
Click to expand...
Click to collapse

I prefer to sell my phone and go through all this hassle
Sent from my GT-I9300 using Tapatalk 2

tarif said:
I prefer to sell my phone and go through all this hassle
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
It is really not as bad as you think. Give it a try

I will try it in a while and will post how it goes. Thanks mate. Keep up the good work

Thx for this interesting post ...but instead of just Uv all frequencies I did uv on each frequencies manually and stress it with set cpu to see if its stable for example im runing 1.4Ghz at 118750mv and can go up to 1.6 Ghz at just 126200mv very stable since I did 25min of stress test on setcpu and since 2days im runing at this speed with that voltage with no problem at all and of course with Siyah kernel
If you guys are interested and I can post all my current voltages at each frequencies
Cheers
Sent from my GT-I9300 using xda premium

G4neStarT said:
Thx for this interesting post ...but instead of just Uv all frequencies I did uv on each frequencies manually and stress it with set cpu to see if its stable for example im runing 1.4Ghz at 118750mv and can go up to 1.6 Ghz at just 126200mv very stable since I did 25min of stress test on setcpu and since 2days im runing at this speed with that voltage with no problem at all and of course with Siyah kernel
If you guys are interested and I can post all my current voltages at each frequencies
Cheers
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
The good thing about this thread is that it is created to share ideas. So feel free to share your settings with everyone. I stressed mine using glbench mark from google play. This settings seemed to work out well without any crashes or SOB . Siyah uses a different mehod so the UV values are not set on boot up. However, the new kernel has the option of uv for any step you want at boot.
Sent from my GT-I9300 using Tapatalk 2

Thanks mate
Enviado desde mi GT-I9300 usando Tapatalk 2

Hi I tried the settings you said above with Siyah 1.8.6 but the phone warmed too! very much! to just use WhatsApp or Kik messenger programs that are not demanding much processing.
I went back to the settings of Stweaks defaut and everything returned to normal.
As for the expense, I have 24 hours of use, 3 hours of screen and 34% of battery.
Very good too, right?

hooliganx said:
Hi I tried the settings you said above with Siyah 1.8.6 but the phone warmed too! very much! to just use WhatsApp or Kik messenger programs that are not demanding much processing.
I went back to the settings of Stweaks defaut and everything returned to normal.
As for the expense, I have 24 hours of use, 3 hours of screen and 34% of battery.
Very good too, right?
Click to expand...
Click to collapse
Strange but I didn't get any of that with my phone. Which of the settings did you use?
Sent from my GT-I9300 using Tapatalk 2

Hi Red Hat,
I'm not having a go (I'm a fellow red), and I know you're trying to help, but steps 1-5 are all complete non starters for me.
What's the point in buying a phone like this if you're going to turn off a bunch of the best functionality? Might as well go and buy something cheaper that doesn't have those functions...

seems a hell of a lot of hassle to go through to get worse battery life than i get at the moment. Just use a stock rom with siyah set at lulzactive and deadline profiles gets me 1d 7 hours with 5 hours screen time. Fine for me.

To avoid this hassle I have bought a spare battery.
Sent from my GT-I9300 using xda premium

skimminstones said:
seems a hell of a lot of hassle to go through to get worse battery life than i get at the moment. Just use a stock rom with siyah set at lulzactive and deadline profiles gets me 1d 7 hours with 5 hours screen time. Fine for me.
Click to expand...
Click to collapse
Ok guys, I am sharing my findings and what I have done to obtain good battery life. This is not a standard or a rule of thumb. For starters, I use my phone a lot and can barely get through a 24 hour day without a needing a charge. So I came up with this and it worked well for me. This is based on what I read from Droidphile and sample from Siyah kernel's battery tweaks. This is my second thread on the issue and it worked well on S2. If you are getting better battery life please share with the rest of us as it will only enable others and myself to learn.
Thanx for the feed back.
Rabangus said:
Hi Red Hat,
I'm not having a go (I'm a fellow red), and I know you're trying to help, but steps 1-5 are all complete non starters for me.
What's the point in buying a phone like this if you're going to turn off a bunch of the best functionality? Might as well go and buy something cheaper that doesn't have those functions...
Click to expand...
Click to collapse
Functionality wise the phone does the same thing it did when I purchased it. Using autostart allows you to stop programs that run in the back ground without when you don't need them. Think of it as an extra hall monitor
Sent from my GT-I9300 using Tapatalk 2

Ehm ehm..! Excuse me!!
I don't know why your guys feeling like getting a good battery life is difficult in this awesome device!
Ultimate rom 7.1 with persues kernel thats all! Nothing much or less than this.
Sent from my GT-I9300 using xda premium

To all my friends wishes of a Happy, Healthy, Successful and a Peaceful New Year

skimminstones said:
seems a hell of a lot of hassle to go through to get worse battery life than i get at the moment. Just use a stock rom with siyah set at lulzactive and deadline profiles gets me 1d 7 hours with 5 hours screen time. Fine for me.
Click to expand...
Click to collapse
wanam's deodexed stock+siyah set with with lulzactive (using droidphile's script) and deadline had given me 2-3% discharging during 11-12 hours sleep whilst any operation resulted in quicker battery drain. With same settings incroporated to Ultima 7.1 the operation-time battery drainage seems to be slowed down with same deep sleep drain.

Will it work well in cm10.1?
Enviado desde mi Tamagotchi usando Tapatalk

kylesinho21 said:
Will it work well in cm10.1?
Enviado desde mi Tamagotchi usando Tapatalk
Click to expand...
Click to collapse
It should work as long as you are running a Siyah kernel (for the stweaks setting) or pegasusq governor. Please try it and post it your results.
Sent from my GT-I9300 using Tapatalk 2

thanks you man!! i'll try it!! :good:

thekoRngear said:
wanam's deodexed stock+siyah set with with lulzactive (using droidphile's script) and deadline had given me 2-3% discharging during 11-12 hours sleep whilst any operation resulted in quicker battery drain. With same settings incroporated to Ultima 7.1 the operation-time battery drainage seems to be slowed down with same deep sleep drain.
Click to expand...
Click to collapse
is there a reason you're quoting my post while saying this?

Share your Pimp My Z1 / FauxClock Settings-Thread!

A lot of users wanted / requested someone to start a topic of this kind - and voila, here it is:
The Official & Dedicated Thread about sharing your each and specific FauxClock / Pimp My Z1 / Performance Control App / Trickster Mod / -Additional App Name- settings to other users so they can try out either some settings that gives god holy battery life or monstrous performance from the Ferrari manufacturers themself!
Just for making the posts easier to read and understand for the less experienced / knowledged users - Write your posts with includings settings in a classic, lined way - Like this;
- What app are you using..
- Which ROM are you on..
- Which kernel are you on..
- What CPU frequencies are you using..
- Your specific CPU governor..
- Your specific IO Scheduler..
- Your specific GPU governor..
- What GPU frequencies are you using..
- Any color calibration tuning you want to share..
- Any Multi Core Power saving tunetable enabled (0 / 1 / 2?)..
- Which hotplug driver are you on?
- Intelliplug ECO-Mode - On or Off?
- Etc etc.. You get the point hopefully..
Any selfmade / specific favourite init.d scripts? Post them below so other users can get the pure enjoyment to try them out?
Please.. Note this point below;
Post a Screenshot of your total average battery life + Total Screen-On-Time so people can debate / hail / criticize / award / dislike and coment if it's good or bad total battery performance!
OBS!! If you are using any init.d scripts - share them either here, in your post or in a uploaded ZIP / RAR file so other ones can give them a try and see if it extends either performance or battery life for them!
I hope this thread can be made into a sticky - so everything about "SHARE YOUR APP SETTINGS" can be collected into one, overall and single thread, instead of being misplaced all over this Xperia Z1 subforum. Keep it clean and tight <- Good words that a friend told me, and this is a golden rule on massive sites like XDA-Developers with thousand of new threads / posts everyday.
Sharing is Caring - so Happy Sharing, my fellow friends!
Regards,
Destroyedbeauty @ XDA
> OBS! NO SPAM, OFFTOPIC OR BULL**** POSTS IN THIS THREAD - THEY WILL BE REPORTED ASAP!!! <

Finally. Will post on V22 once it is out.

App: Pimp My Z1
ROM: Paranoid Android 4.4 beta-1
Kernel: Pimped kernel for CM Roms, light version
Frequencies: Min 300 / Max 1728
Governor: Smartass V2
Scheduler: row
Additional: power suspend and dynamic file sync
Have been running this for two days, awesome battery life. I hope it is OK that I post settings for an AOSP ROM.
Feel free to ask any questions.
{
"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"
}
Skickat från min Xperia Z1 via Tapatalk

ekanix20 said:
I hope it is OK that I post settings for an AOSP ROM.
Click to expand...
Click to collapse
Of course! As long you're adding something of a value and still is staying on topic - you can add what you want to the topic and subject!

App: Trickster Mod
Rom: Ihackers v4.1 minimal
Kernel: DoomLord v21
Max/Min freq: 300-1.9ghz
Governor: intelliactive
Scheduler: Deadline, 1024 Buffer
Intelliplug activated, powersaving 1
Zram activated
Fsync activated
Voltage at 750mh for 300mhz
Great battery life so far with this Setup!
Up to 4 1/2 hours screen on time, everything running find and snappy!
Sent from my C6903 using XDA Free mobile app

Okey, it's time for me to post my full set-up / configuration also then.. Here it is;
- App: Pimp My Z1
- ROM: Deodexed & Tweaked Stock .757
- Kernel: Doomkernel v21
- CPU Frequencies - MIN: 300 Mhz / MAX: 1728 Mhz
- CPU Governor: Intellidemand
- IO Scheduler: Deadline
- GPU Governor: MSM_CPUFREQ
- GPU Frequencies - MIN: 27 Mhz / MAX: 320 Mhz
- Color Calibration - Red: 255, Green: 235, Blue: 250
- Sony White Balance Control - Red; 15, Green: 40, Blue: 25
- Power Managment:
- Multi-Core Power Savings: 0
- Hotplug Driver: Intelliplug
- Intelliplug ECO-Mode: On
- Power Suspend: On
- Dynamic File Sync: On
- Readahead (eMMC): 1024
- Entropy Contribution: Off
- Vibrator Intensity: 0
Additional tweaks / scripts that I am using; See attached ZIP file for my specific battery saving script!
Results: I am at 15% battery juice left after 1 day, 1 hour and 41 minutes since last charge and total Screen-On-Time of 5 hours and 6 minutes!

e30luismi said:
install script battery?
Click to expand...
Click to collapse
Do not spam the threads about same thing! What do you mean by "install script battery"? Lord.

e30luismi said:
install script battery?
Click to expand...
Click to collapse
Place this script inside your init.d folder (/system/etc/init.d) and give script and init.d 0777 permissions and reboot for it taking full action!
So.. KEEP THIS THREAD ON TOPIC OR I'LL REQUEST IT TO BE LOCKED!!!
Sent from my C6903 using XDA Premium 4 mobile app

My battery 27% with 2h 10min screen , config destroyed rom pure stock v2 mode stamine on

e30luismi said:
thx
Click to expand...
Click to collapse
e30luismi said:
My battery 27% with 2h 10min screen , config destroyed rom pure stock v2 mode stamine on
Click to expand...
Click to collapse
And you thought those posts was adding anything of a value to the thread?
Sent from my C6903 using XDA Premium 4 mobile app

e30luismi said:
sorry,
Click to expand...
Click to collapse
Please, stop spamming non-value posts.
Reporting now!
Sent from my C6903 using XDA Premium 4 mobile app

Fauxclock + DoomKernel v21
CPU Governor: Intelliactive min300 max1958 tweaked with these settings:
above_hispeed_delay = 20000
boost = 0
boostpulse = (null)
boostpulse_duration = 80000
go_hispeed_load = 60
hispeed_freq = 1497600
io_is_busy = 0
min_sample_time = 200000
sampling_down_factor = 1
sync_freq = 960000
target_loads = 90
timer_rate = 20000
timer_slack = 80000
two_phase_freq = 1728000,1728000,1728000,1728000
up_threshold_any_cpu_freq = 1497600
up_threshold_any_cpu_load = 90
Intelliplug on, eco mode on, touch boost off, screen off frequency set at 652800, sio schedulers!
Enjoying great battery life and performance :good:

dedei said:
Fauxclock + DoomKernel v21
CPU Governor: Intelliactive min300 max1958 tweaked with these settings:
above_hispeed_delay = 20000
boost = 0
boostpulse = (null)
boostpulse_duration = 80000
go_hispeed_load = 60
hispeed_freq = 1497600
io_is_busy = 0
min_sample_time = 200000
sampling_down_factor = 1
sync_freq = 960000
target_loads = 90
timer_rate = 20000
timer_slack = 80000
two_phase_freq = 1728000,1728000,1728000,1728000
up_threshold_any_cpu_freq = 1497600
up_threshold_any_cpu_load = 90
Intelliplug on, eco mode on, touch boost off, screen off frequency set at 652800, sio schedulers!
Enjoying great battery life and performance :good:
Click to expand...
Click to collapse
Some questions..
1. Are you on any custom ROM or stock .757 / .761 firmware?
2. No wakelocks from FauxClock app? < Please check and verify with Greenify and BBS apps..

Destroyedbeauty said:
Some questions..
1. Are you on any custom ROM or stock .757 / .761 firmware?
2. No wakelocks from FauxClock app? < Please check and verify with Greenify and BBS apps..
Click to expand...
Click to collapse
Stock 757, phone has been up for 15h with x86 wakelocks from fauxclock
right now I'm on 3h11m of screen on time and I still have 39% of juice!
Enviado de meu C6903 usando Tapatalk

Destroyedbeauty said:
Place this script inside your init.d folder (/system/etc/init.d) and give script and init.d 0777 permissions and reboot for it taking full action!
So.. KEEP THIS THREAD ON TOPIC OR I'LL REQUEST IT TO BE LOCKED!!!
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do you do this? I understand moving it to a certain folder but I've never used init.d
I'm on iHackers v2 stock rooted not unlocked bootloader yet, Please explain how I can achieve what you have done in more details.

JayGB2011 said:
How do you do this? I understand moving it to a certain folder but I've never used init.d
I'm on iHackers v2 stock rooted not unlocked bootloader yet, Please explain how I can achieve what you have done in more details.
Click to expand...
Click to collapse
You can't do that with a locked bootloader.
Enviado de meu C6903 usando Tapatalk
---------- Post added at 02:34 AM ---------- Previous post was at 02:34 AM ----------
e30luismi said:
active ksm??
Click to expand...
Click to collapse
If that was directed towards me, no lol I never enabled it
Enviado de meu C6903 usando Tapatalk

My turn...
- App: FauxClock
- ROM: Tweaked Stock .757
- Kernel: Doomkernel v19
- CPU Frequencies - MIN: 300 Mhz / MAX: 1728 Mhz
- CPU Governor: Intellidemand
- CPU Hotplug: Intelliplug
- IO Scheduler: Deadline
- GPU Governor: Simple_ondemand
- GPU Frequency: MAX: 200 Mhz Lazinesss: 4 Ramp Treshold: 6
- Power Managment:
- Hotplug Driver: Intelliplug
- Intelliplug ECO-Mode: On
- Power Suspend: On
- Dynamic File Sync: On
- I/O Scheduler (eMMC/SDCard): sio / row
- Readahead (eMMC/SDCard): 1024/512
- Entropy Contribution: Off
- ZRAM Swap: Off
- Intelli-KSM: Enabled (Standard settings)
Results:
SCREEN ON about 2 hours
300 MHz ~ 20% of time
Deep Sleep ~ 65% of time
Overall graph
As you see some app did not close correctly and GPS was ON about hefty 8 Hours so i think the score isn't so bad at all.
ps. got 2 email accounts with POP Push and Google+ which produces most wakelocks, next time will switch off both and will see the difference...

@all
Bump! Thread seems to be dead, pretty strange because this topic was requested for avoid off topic posts, and then people seems to ignore it.
To lazy to use proper discussion threads, maybe?
Sent from my Xperia Z1 using XDA Premium 4 mobile app

Yeah, i'v been waiting for a good balance settings to be posted because mine stays on 1497 and 1728 most of the time even with light apps..

dedei said:
Yeah, i'v been waiting for a good balance settings to be posted because mine stays on 1497 and 1728 most of the time even with light apps..
Click to expand...
Click to collapse
Pm me!