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?

supposed solution to heat during gaming .

i want to discuss the overlock or underlocking the cpu
so whats the effect on heat generated ????
overlock increase heat or dcrease heat ??
and is undervolting helps to decrease heat generated from the processor ??
many tests mentioned that overlock 1.6 is stable and undervolting scale (200-800) is also stable but non of the testers mentioned the heat effect all are reporting for stability and speed
i suffer from heat during hd games and i know it is normal but i dont want the phone to get hot during gaming i closes the game after around 30 minutes due to this problem

If you want to reduce heat during gaming, then you need to change the 1.2GHz speed (level 0) down to either 1.0GHz or 800MHz. Changing the Level 1 to Level 4 speeds won't solve your problem since your CPU will be at full speed Level 0 during gaming.

Sleepycat3 said:
If you want to reduce heat during gaming, then you need to change the 1.2GHz speed (level 0) down to either 1.0GHz or 800MHz. Changing the Level 1 to Level 4 speeds won't solve your problem since your CPU will be at full speed Level 0 during gaming.
Click to expand...
Click to collapse
srry i dont understand what will make the processor return to full speed 1.2 during gaming ?? if i set it to 1000 or 800 ???

Sleepycat3 said:
If you want to reduce heat during gaming, then you need to change the 1.2GHz speed (level 0) down to either 1.0GHz or 800MHz. Changing the Level 1 to Level 4 speeds won't solve your problem since your CPU will be at full speed Level 0 during gaming.
Click to expand...
Click to collapse
No that's just bull****. Go play around a few games and have CPU Spy running and after a gamsing session check the CPU states, rarely does a game go over 800MHz and most of the time spent is on 500MHz for most games. There aren't any games out there that need the computational power of higher frequencies and that's why their time-in-state is procentually so low.
If you really want to reduce heat, then you need to undervolt your GPU which right now is only possible with a Tegrak compatible kernel, which is frankly speaking out of date, or you wait a few weeks until the Ninphetamine team finishes GPU voltage control interface and then more kernels will be able to implement that.
While undervolting with Tegrak I was running 160MHz/750mV 266MHz/750mV full stable (default voltage 950/1000mV, 750 was minimum configurable). It was running full stable and while on default the back of the phone would get really hot, while undervolted it was just warm to the touch.

AndreiLux said:
No that's just bull****. Go play around a few games and have CPU Spy running and after a gamsing session check the CPU states, rarely does a game go over 800MHz and most of the time spent is on 500MHz for most games. There aren't any games out there that need the computational power of higher frequencies and that's why their time-in-state is procentually so low.
If you really want to reduce heat, then you need to undervolt your GPU which right now is only possible with a Tegrak compatible kernel, which is frankly speaking out of date, or you wait a few weeks until the Ninphetamine team finishes GPU voltage control interface and then more kernels will be able to implement that.
While undervolting with Tegrak I was running 160MHz/750mV 266MHz/750mV full stable (default voltage 950/1000mV, 750 was minimum configurable). It was running full stable and while on default the back of the phone would get really hot, while undervolted it was just warm to the touch.
Click to expand...
Click to collapse
so is there any effect on device performance ????
after undervolting the hd games performs properly as stock ?? and without heat ?? if yess i will root now and see what can i do
and how can i know that my kernel is tegrak compatible ?? it is kg2

Changing voltage has no effect on performance unless you undervolt into unstable values and make it crash. Stock should be compatible with Tegrak (I think???). Just check out the free app in the market. The stupid thing is you need to pay for the full version to get GPU control and that's why it's unpopular, so maybe it's just better to wait for Ninphetamine GPU control in a couple of weeks or soonish and have it for free and get a good kernel to go with it.

AndreiLux said:
Changing voltage has no effect on performance unless you undervolt into unstable values and make it crash. Stock should be compatible with Tegrak (I think???). Just check out the free app in the market. The stupid thing is you need to pay for the full version to get GPU control and that's why it's unpopular, so maybe it's just better to wait for Ninphetamine GPU control in a couple of weeks or soonish and have it for free and get a good kernel to go with it.
Click to expand...
Click to collapse
thanks bro
but i think i have small thing that confuse me undervolting is different from downlock ??
and what is the relation between them ??? i think certain volt will give related amount of "Mhz" ?? is that right ??? so set cpu is the same effect as tegrak or what ??
srry im new to android

xdafun4all said:
thanks bro
but i think i have small thing that confuse me undervolting is different from downlock ??
and what is the relation between them ??? i think certain volt will give related amount of "Mhz" ?? is that right ??? so set cpu is the same effect as tegrak or what ??
srry im new to android
Click to expand...
Click to collapse
Tegrak, basically gives you more options such as GPU clocking and custom tweaks. SetCPU is ok, but I just use it for controlling clock speeds. Also, you can set oc'ing, max at 2GHZ, but you have to play around with stuff.

Use a very thin case and you'll never notice.
Sent from my GT-I9100 using XDA App

AndreiLux said:
No that's just bull****. Go play around a few games and have CPU Spy running and after a gamsing session check the CPU states, rarely does a game go over 800MHz and most of the time spent is on 500MHz for most games. There aren't any games out there that need the computational power of higher frequencies and that's why their time-in-state is procentually so low.
Click to expand...
Click to collapse
Sure. I just fired up Plants vs Zombies, which is not the world's most demanding Android game and played 1 quick game, taking about 10 minutes. While playing, the back of the phone just where the camera is became warm through the phone case! Tell me why I have the phone running at 1200MHz for such a big portion of time if my post is just bull****. This was also the Last Stand level, where you get a pause in the middle of the attacks to replant.
{
"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"
}

Sleepycat3 said:
Sure. I just fired up Plants vs Zombies, which is not the world's most demanding Android game and played 1 quick game, taking about 10 minutes. While playing, the back of the phone just where the camera is became warm through the phone case! Tell me why I have the phone running at 1200MHz for such a big portion of time if my post is just bull****. This was also the Last Stand level, where you get a pause in the middle of the attacks to replant.
http://img825.imageshack.us/img825/5459/sc20110829170728.png
Click to expand...
Click to collapse
35% of time on full speed does not equal all the time on full speed like you said in your first post. It's still 50% on either 800 or 500MHz like I said. And you took a bad example as I dont even know if PvsZ is even using properly the GPU, and then might use only the CPU. Go play Gameloft HD games which are the most demanding atm and max CPU ratio to the rest falls down.

AndreiLux said:
35% of time on full speed does not equal all the time on full speed like you said in your first post. It's still 50% on either 800 or 500MHz like I said. And you took a bad example as I dont even know if PvsZ is even using properly the GPU, and then might use only the CPU. Go play Gameloft HD games which are the most demanding atm and max CPU ratio to the rest falls down.
Click to expand...
Click to collapse
so what ??? at the end undervolting will help or not ???
i need it for hd games
and if the cpu need to be at 50% of time so it need to use 1200 mhz 50 of time so if we fixed it to 800 or 1000 or 500 this will affect performance

no heat issues
I have ninphetamine kernel, underclocked to 800 and undervolted, I haven't noticed any heat issues since then when playing games and noticed no slow downs. Games tried: HeavyGunner, Zenonia 3. Also no heat issues anymore when playing flash video in a browser.

wslfung said:
I have ninphetamine kernel, underclocked to 800 and undervolted, I haven't noticed any heat issues since then when playing games and noticed no slow downs. Games tried: HeavyGunner, Zenonia 3. Also no heat issues anymore when playing flash video in a browser.
Click to expand...
Click to collapse
but sorry these games are not using graphics as eternal legacy or asphalt 6 hd or fast 5 hd

really it works
i rooted then set cpu then put the values 200-800 and asphalt 6 worked around 20 minutes no heat at all only slight warm
and the benchmark only decresed from 3300 to 2750

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.

Share your Voltage Settings here!

Hey everyone, I figured we deserved to have this thread as I hadn't seen one yet. I'm forever trying to tweak and adjust my voltages on my NS4G and I just wanted to see what everyone else was running and with what degree of success.
List your ROM/Kernel combo and your OC/OV/UV settings!
Currently:
CodenameAndroid 1.4.0
Matr1x v17.5 cfs
1300/400 SavagedZen
Deep Idle on.
@1.3GHz - 1430mV
@1.2GHz - 1350mV
@1GHz - 1280mV
@800MHz - 1205mV
@400MHz - 1030mV
...Stability tests are ongoing.

Rom: MIUI 2.3.9 (ICS)
Kernel: Matrix 17.5
Live OC: 105
Min: 210
Max: 1050
Voltage: All stock voltages dropped by 25
Scheduler: Deadline
Deep Idle: On
The voltages being dropped immensely helps battery life. I get at least 12 hours with heavy use and about a day and a half with light use.
Sent from my Nexus S 4G using xda premium

Almost same..
http://forum.xda-developers.com/showthread.php?t=1335429

Undervolting doesn't actually help the battery :$.... Well by much anyways. If it does it will be like a 2% difference... Instability doesn't seem worth it for 2%
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged

309041291a said:
Undervolting doesn't actually help the battery :$.... Well by much anyways. If it does it will be like a 2% difference... Instability doesn't seem worth it for 2%
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged
Click to expand...
Click to collapse
I always doubted bedalus claims on the matter (and even communicated with him through PM).
Time permitting, I'd like to do some tests myself about undervolting, because I am pretty sure it has an impact.
Anyway, my settings are in my signature.
polobunny said:
For those interested, I spent the night yesterday testing out ARM voltages on my phone that were absolutely stable but hopefully under the stock ones to save more battery.
Had a look at morfic's git for a good idea, so thanks to him.
Might not work on your phone, so use at your own risk.
100MHz 875mv (75mv under stock)
200MHz 875mv (75mv under stock)
400MHz 900mv (150mv under stock)
800MHz 1125mv (75mv under stock)
1000MHz 1225mv (25mv under stock)
Click to expand...
Click to collapse
Some people have a problem with 400MHz at 900, 950mv seems good for anyone though.

AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900

lolokman said:
AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900
Click to expand...
Click to collapse
What's the battery like? And I believe the matrix kernel is already Undervolted by default.
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (100 - Noop)
v6 Supercharged

Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app

gear.h34d.2012 said:
Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
On-screen time? With a screen
Nexus S (GSM i9020a)
AOKP (Milestone 4)
Air Kernel (3.45)
OC 800/100 (Lionheart)
Live OC (110 - Noop)
v6 Supercharged

lolokman said:
AOKP milestone 4
mart1x cfs v18.0
both settings have been run for days without reboot
setting no.1
840/100 smartassv2 noop
selective liveoc 105
freq arm int
840 1075 950
400 950 950
200 850 950
100 850 900
setting no.2
1000/100 smartassv2 noop
freq arm int
1000 1150 1000
800 1050 950
400 950 950
200 850 950
100 850 900
Click to expand...
Click to collapse
Interestingly I'm able to undervolt quite a lot more than I've ever been able to using this smartassv2/ noop setup. I'm not sure what it is but anytime I'd try to under volt matrix v18 any below stock I'd get reboots but with this setup I'm close to the values you've set and it's been stable so far. Its not undervolted as heavily and I don't have liveoc enabled at the moment. I'm just enjoying the ability to under volt it to where it is at the moment.
Sent from my Nexus S using Tapatalk

Currently using Franco kernel 1.2 and I dropped the stock voltages by 50(I was feeling a bit adventurous). Getting pretty nice battery life and stable(no reboots yet).
Sent from my Nexus S using Tapatalk 2 Beta-2

polobunny said:
I always doubted bedalus claims on the matter (and even communicated with him through PM).
Time permitting, I'd like to do some tests myself about undervolting, because I am pretty sure it has an impact.
Anyway, my settings are in my signature.
Some people have a problem with 400MHz at 900, 950mv seems good for anyone though.
Click to expand...
Click to collapse
Not sure if lower voltages, would make for less amp/wattage draw,
Sent from my Nexus S 4G using Tapatalk

what exactly is the difference between arm and int voltage? and what should i drop? both?
i have been undervolting with the internal voltage controle of aokp and this only drops int voltages //edit: After taking a second look, it seems like its arm thats changing...

I've dicked around with undervolting since my Evo days, and honestly, it does nothing for battery life. Multiple kernel developers - not to mention bedalus's tests - confirm this.
Undervolting seems useful only for providing an excuse for futzing with your phone. Any power savings are likely anecdotal or psychological.

i start from now the undervolitng , i chek and after i post my expirience .

gear.h34d.2012 said:
Just got over 1 day of battery dropping all stock voltages by 25.
Codename 1.5.5
Matr1x 18.0 cfs
1200/200 lazy
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
{
"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"
}
There it is.

gear.h34d.2012 said:
There it is.
Click to expand...
Click to collapse
I bet your phone was on idle most of the time.

currently running with these voltage settings:
freq arm int
1200 1350 1125
1000 1225 1075
800 1075 1000
400 950 1000
200 875 975
Governor:SmartassV2
Scheduler:noop
mix/max:200/1200
Rom:Codename Android 3.6.0
Kernel:AirKernel 65fps+BlueColor HBM #211
no reboots so far, but i feel that i've not reached the down-limit point! especially for 1000mhz freq

i'm default

please give me description about voltages.

NeatRom + Siyah Kernal. Optimization for Better Battery

Disclaimer alert: I am in no way responsible for any damage inquired while performing any of the changes listed below. If you are not comfortable with tweaking your device please feel free to use built in option in Siyah's Kernal. This is just an option and it is something I have tried on my phone with success. I am not using a stock battery, but rather a 2000MAH.
I have NeatRom Lite V1.1 + Siyah Kernal (Slick Sale) installed on my phone. This was created by Sale (his work on this rom is increadible). Samsung's stock kernal has been replaced by Siyah's kernal SGS2v.3.3.2. This version has touch CWM which makes flashing fun. To tweak the kernal, I installed ExTweaks (from the market. Extweaks has the option for battery, performance and defualt settings (these are enabled after a donation). This same settings can be performed in recovery. Siyah has the kernal tweaked for optimization for battery and performance. You can select this in recovery (scrolling down to kernal specific options and the choosing either battery or performance) and it will be impleted during boot up.
However if you feel bold you can tweak the kernal using Ex Tweaks. These are my settings below ( they are by no means a rule of thumb)
Note. I have noticed that the screen consumes most of the power from the battery. If you are able to reduce your screen brightness to about 40% instead of being at automatic, you will get additional time on your phone.
SETTINGS (CPU):
GENTLE_FAIR_SLEEPERS = On
ARCH_POWER = On
CPU Hotplug = Default
CPU IDLE Mode = AFTR + LPA (default)
Smooth Scaling Level = 800Mhz
SCHED_MC = 2
CPU Undervolting = -50mV
CPU Step Count = 18 (All available)
Default CPU Governor = pegasusq
Default CPU Scheduler = sio
Scaling Max Freq = 1000Mhz
Scaling Min Freq = 200Mhz
SETTINGS (GPU freq):
GPU Freq Step 1 = 66Mhz
GPU Freq Step 2 = 133Mhz
GPU Freq Step 3 = 267Mhz
SETTINGS (GPU voltages):
GPU Voltage Level 1 = 800mV
GPU Voltage Level 2 = 850mV
GPU Voltage Level 3 = 900mV
SETTINGS (other):
Screen settings stock.
Vibration intensity = 2
Touchmovesensitivity =5 pixel
Min_BL =30
Min_Gamma=1
Max_Gamma=24
Other setting without undevolting.
SETTINGS (CPU):
GENTLE_FAIR_SLEEPERS = On
ARCH_POWER = On
CPU Hotplug = Default
CPU IDLE Mode = AFTR + LPA (default)
Smooth Scaling Level = 800Mhz
SCHED_MC = 2
CPU Undervolting = No undervolting
CPU Step Count = 18 (All available)
Default CPU Governor = pegasusq
Default CPU Scheduler = sio
Scaling Max Freq = 1000Mhz
Scaling Min Freq = 100Mhz
SETTINGS (GPU freq):
GPU Freq Step 1 = 40Mhz
GPU Freq Step 2 = 133Mhz
GPU Freq Step 3 = 267Mhz
SETTINGS (GPU voltages):
GPU Voltage Level 1 = 800mV
GPU Voltage Level 2 = 850mV
GPU Voltage Level 3 = 900mV
SETTINGS (other):
Screen settings stock.
Vibration intensity = 3
Touchmovesensitivity =5 pixel
Min_BL =40
Min_Gamma=0
Max_Gamma=24
Please note Geko95gek has three different settings and it should work if you are in the mood for an adventure.
Download Links.
NeatRom Lite
Siyah Kernal
ExTweaks (Google play Store)
Useful sources
Geko95gek http://forum.xda-developers.com/showpost.php?p=26755476&postcount=850
Droidphile's article http://forum.xda-developers.com/showthread.php?t=1369817
Special thanks and credit to the following:
Sale (awesome rom and excellent support)
Gokhamoral (great kernal)
Geko95gek (examples of tweaks)
Droidphile (Write up of governors).
Sample shorts of my usage.
{
"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"
}

Thank you!
Siyah is a fantasic kernel and I am thrilled with it

My last post on battery and consumption using the latest NeatRom Lite with Siyah's kernel was based on my extended battery (2000mAh). This time around, I decided to try it with stock battery. As suspected the results were just as amazing. I want to point out that I maintained the same tweaks ad settings. Once again Sale has created a clean and exciting ROM.
Before sun raise
Am sure I could have gotten another 5 hours or more with this ROM. Great combination NeatRom Lite and Siyah's Kernel
Sent from my GT-I9100 using Tapatalk 2

Interesting post but I must say that on mine the kernel included with neatrom is at least as good for me as an all rounder (balance between performance and battery) as I've yet found.
Not trying to rubbish the results btw, but for me I've followed a lot of these guides for different kernels and at best the difference is small and at worst introduces bugs.
Happy with neat from though very good!

I was always using NEAT Rom without any UC/OC modifications and it was already GREAT.
Inspired from your Post I decided to give undervolting a try...
I have latest NEAT Rom UHLPS Lite and use the Settings with undevolting;
the absolute great batterylife has increased over again! Wuha!
Also the performance is nearly the same as before (feels exactly the same as before!)
So in my opinion the combination of NEAT Rom, Siyah Kernel and your settings for undervolting are amazing!
Thanks Sale for this absolute superb Rom!
Thanks Gokhamoral for the great Kernel!
and thank you red.hat for the inspiration and this lovely guide for underclocking!
My experience:
Tweaked settings, charged battery to 100%, used it now for 26 hours, made some calls (about 30min), wrote some sms,
used Wifi for about 35min for surfing and the battery is still at 89% !!!

Battery saving tweaks
Thanks to red.hat's hospitality, you can find on this thread my battery friendly configs. They are based on NeatromLite stock based roms and Siyah custom kernels. Exceptionally I prepare tweaks also for other kernels (eg philz) when Siyah kernels are not available/ready for particular Neatrom releases.
Beneath you can find my work which I've done so far.
MANY40'S BATTERY FRIENDLY CONFIGS COLLECTION:
What is the battery friendly config? In short, it's a set of battery saving tweaks which can be divided into two groups: kernel tweaks and rom tweaks.
1. Kernel's tweaks (scripts + Stweaks profile - they tweak some kernel's tunables like CPU/GPU freq, CPU/GPU voltages, CPU governor and other parameters)
2. Rom's tweaks (OS sound/vibration/screen/motion/animation/comms/location/sync etc settings + freezed system apps list + wakelocks advices + some others)
DISCLAIMER:
A. Everybody can try it but not necessarily it will work for everybody like it works for me.
B. Remember that our phones' hardware is not 100% identical.
C. Make nandroid backup before trying this
D. If any tweak causes freezes, restore your nandroid backup.
I. SIYAH KERNELS:
1. <Siyah 6.0 beta5 + Neatrom 4.X JB 4.1.2>
2. <Siyah 6.0 beta4 + Neatrom 4.X JB 4.1.2>
3. <Siyah 5.0.1 + Neatrom ICS 4.0.3/4.0.4>
4. <Siyah 4.1.5 + Neatrom ICS 4.0.3/4.0.4>
II. PHILZ KERNELS:
1. <PhilZ-CWM6 4.X + Neatrom 4.X JB 4.1.2>
Enjoy!

Many40 said:
Thanks, great proposal. I am not new on this subject doing similar things for myself but if you don't mind I would have one question (I couldn't find the answer up to now) and one remark:
Question: You posted two different settings: first one with min FRQ 200 MHz and second one 100 MHz. Did you do that intentionally? Do you know what freq is better for battery saving? I red somewhere that on 100MHz phone consumes more power than on 200MHz. So according to your konwlegde/exeprience what is better - I am using 100MHz as you can see from my signature.
Click to expand...
Click to collapse
Both frequencies were tried to see the benefits of one over the other. I didn't find much difference. Through my research I found some people prefer 100 MHz and others 200MHz. How is 200MHz working out for you.
Remark: Here are my considerations about SHED_MC. I am not using this option (SHED_MC=0) because in my opinion if CPU hotplug is set, enabling SHED_MC doesn't make really sense (Sched_mc aims to schedule tasks between multiple cores in the CPU and if sched_mc = 2 = load balancing, then to make sense dual core shoud be set instead of hotplugging. But it would rather help to utilize both cores more effectively than save more battery. Moreover then AFTR+LPA couldn't be hit when 2nd core is on). The same opinion shares droidphille who gave me short answer on that in his thread.
This is theory, but maybe real life brings something different? Have you tested both?
Regards
Click to expand...
Click to collapse
I haven't tested both, but you have raised a good question and I'll have to look into it. Siyah's default setting for battery optimization has SCH_, also set at 0. However a couple of examples I saw on xda has it at 2. I'll make changes tomorrow and set how that goes. Could you share droidphille reaponse
Sent from my GT-I9100 using Tapatalk 2

red.hat said:
Both frequencies were tried to see the benefits of one over the other. I didn't find much difference. Through my research I found some people prefer 100 MHz and others 200MHz. How is 200MHz working out for you.
Click to expand...
Click to collapse
Tested both (but on sammy stock rom) and also didn't notice any difference.
I haven't tested both, but you have raised a good question and I'll have to look into it. Siyah's default setting for battery optimization has SCH_, also set at 0. However a couple of examples I saw on xda has it at 2. I'll make changes tomorrow and set how that goes. Could you share droidphille reaponse
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, of course. I started thinking about that after red geko95gek's MagicConfig. He also proposed SCHED_MC=2. So I asked him about the reason but he didn't respond so decided to ask droidphille. This was his answer:
"@Many40
Let's say enabling sched_mc on Galaxy S2 Exynos 4210 is completely pointless. Hotplugging is well handled by stand hotplug/legacy hotplug. Two logics trying to do same thing is always bad. It's like having two antivirus software on PC or like freq_step and smooth scaling trying to do similar stuff in ondemand based governors.
Sched_mc = 1 = Assymmetrical loading of cores. This can hinder race to idle (talking about AFTR here).
sched_mc = 2 = load balancing. When hotplugging knows when and how to hotplug In and Out second core, there's no need of another logic to do the same and cause conflicts. If you're using forced dual core mode, this may have some benefits. I never tested myself.
conclusion: let shed_mc=0 as long as you're using hotplugging. If you're on dual core mode (remember aftr/lpa can not be hit when second core is On), try sched_mc=2. However i don't think load balancing can save battery. It may utilize both cores effectively."

I've done a few tests on the NEAT ROM with stock kernel and with Siyah and on the settings given here.
I wouldn't recommend these settings if you ever want to play games, the Antutu benchmark froze at the graphical portion but did finish the benchmark with a overall score of about half of what it did with the stock kernel (6226 v 3489). Quadrant wouldn't even finish.
Even when I reset Siyah back to its own defaults, the benchmarks are coming in at around 10 - 15% slower than stock.
They may be good for saving battery but to me its like having a Porsche, and then de-tuning it to half the power to save petrol.
Not trolling, just trying to offer another perspective.

tameracingdriver said:
I've done a few tests on the NEAT ROM with stock kernel and with Siyah and on the settings given here.
I wouldn't recommend these settings if you ever want to play games, the Antutu benchmark froze at the graphical portion but did finish the benchmark with a overall score of about half of what it did with the stock kernel (6226 v 3489). Quadrant wouldn't even finish.
Even when I reset Siyah back to its own defaults, the benchmarks are coming in at around 10 - 15% slower than stock.
They may be good for saving battery but to me its like having a Porsche, and then de-tuning it to half the power to save petrol.
Not trolling, just trying to offer another perspective.
Click to expand...
Click to collapse
Yes this is a battery saving setting not for gaming. I used these settings because I can't charge my battery all day so I am using this. However, I if you need performance you can change the i/o scheduler to crq, no scaling of leave at default which 1200 MHz or just use Siyah's kernel performance option in kernel settings.
There are times when driving a Porsche requires a slow speed.
Sent from my GT-I9100 using Tapatalk 2

I've flashed Neatrom with Siyah kernel last night. Did a full charge and I am now monitoring my battery usage.
During the night I've lost 2% charge with wifi and data switched off, which i think is very good.
But now, after a total of just over 12h, the battery sits at 42%, of which the screen was on for 1h 40min and wifi for about six hours.
Is this the normal usage, or at least expected? Or is there still plenty of room for improvement?
By the way, I can't undervolt my CPU to -50mV - it causes freezes. -25 seems okay.

PakkaZA said:
I've flashed Neatrom with Siyah kernel last night. Did a full charge and I am now monitoring my battery usage.
During the night I've lost 2% charge with wifi and data switched off, which i think is very good.
But now, after a total of just over 12h, the battery sits at 42%, of which the screen was on for 1h 40min and wifi for about six hours.
Is this the normal usage, or at least expected? Or is there still plenty of room for improvement?
By the way, I can't undervolt my CPU to -50mV - it causes freezes. -25 seems okay.
Click to expand...
Click to collapse
Did you use the same setting as above. I have mine on without Wi-Fi and through normal use I am at 97%.
Give thanks if I have helped you. Sent via Tapatalk on my S2- i9100

Here is the link to the kernal for S2. It has somewhere Cfs tweaks included.
http://www.gokhanmoral.com/gm/2012/07/08/siyahkernel-s2-v3-3-3/
Give thanks if you have been helped.
sent via HP touch pad with Tapatalk

for 3.3.3c which setting?

qqqqqq0 said:
for 3.3.3c which setting?
Click to expand...
Click to collapse
Hello still working on a great setting. Try the second settings above but set sch_ to 0, CDs tweaks art Linux kernal. It is what I have been using so far.
Give thanks if you have been helped.
sent via HP touch pad with Tapatalk

hi what specific of neatrom should i get and also siyah kernel v3.3.3?

miedy12 said:
hi what specific of neatrom should i get and also siyah kernel v3.3.3?
Click to expand...
Click to collapse
Any version of NeatRom is fine. I personally like uhlps lite. It is fast and responsive. You can combine it with Jkay's deluxe and ics domination
Give thanks if I have helped you. Sent via Tapatalk on my S2- i9100

thanks yes ive downloaded the latest rom posted on july 1/ the kernel is siyah kernel 3.2.2 so it is ok for this? and then i just going to set your undevolt or flash the new 3.3.3?

Scaling Max Freq = 1000Mhz so this is 1000000mhz
Scaling Min Freq = 200Mhz and this is 200000
i am correct?
hi im confused there all i can see is the minimum og 100000 and in min frequency its 20000? it is correct? help also. in sch_med i cant choose to put it on 2 help. and also i set my kernel in cmw at battery

miedy12 said:
Scaling Max Freq = 1000Mhz so this is 1000000mhz
Scaling Min Freq = 200Mhz and this is 200000
i am correct?
hi im confused there all i can see is the minimum og 100000 and in min frequency its 20000? it is correct? help also. in sch_med i cant choose to put it on 2 help. and also i set my kernel in cmw at battery
Click to expand...
Click to collapse
The min Freq is 100MHz and the max is 1000Mhz. The sch_med and hotplug perform the same function so you can leave at 0. But if you want to you can slide it to 2.
Give thanks if I have helped you. Sent via Tapatalk on my S2- i9100