yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] red.hat:
Try this thread for Siyah kernel, everyone is friendly and helpful.

http://xdaforums.com/showthread.php?t=1747754

NeatRom + Siyah Kernal. Optimization for Better Battery
[Galaxy S II General] ritvik93:
Hey Geko!

I was thinking of rooting my phone and flashing siyah kernel on stock rom + your magic config, since i only get about 2 hours screen time :/ with moderate usage. I am just a bit concerned about the undervolting . Will UV by any means reduce the gaming performance? Since i mainly only play games on my phone. Ooh and can this setup induce lag in day to day usage?

edit: Does this magic config hold for siyah 5.0.1 also or there are some differences?
[Galaxy S II General] galaxys2Tav:
This guide never gets old mate, you know i like how good you are with saving me battery over all of our phones. Think this needs to be bumped as well as it works with a lot of kernels even newer ones ;)
[Galaxy S II General] 84tdan:
Using now stock clock speeds. 100mhz - 1200mhz. But with Magic configs voltages and bfq/ondemand combo. CPU Spy says that deep sleep is not being used. Maybe thats the cause for my battery drain last night (went from 40% to 0% in 8hours of standby).

By the way, what are the stock voltages and clock speeds (for CPU & GPU)?
[Galaxy S II General] XDA mark:
Sounds like your phone didn't deep sleep for those 44 minutes. Because normaly you should have lost 0%... ok, maybe 1-2% MAX with 3G on. Search on XDA for BetterBatteryStats and download that app, look what is causing wakelocks.
[Galaxy S II General] CamoGeko:
This is what you should experience if you keep your phone in idle guys....

I took the phone off charge this morning after flashing a XXKI3 modem in recovery. Then I went out, after 2 hours that's what I had lost. Nothing!

Today I will add stock voltages to the OP as they seem to be highly requested.

I think they are:

100 - 1000

200 - 1000

500 - 1050

800 - 1150

1000 - 1250

1200 - 1350

1400 - 1400

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II General] pepe2909:
Hello,

Can use your configuration for an older version of siyah kernel, for example v2.6.4 ?

Thanks !
[Galaxy S II General] kpyhere:
I have read about Screen undervolting in this thread:

http://xdaforums.com/showthread.php?t=1351191

Is it possible to control, like controlling the cpu voltage ? :D
[Galaxy S II General] Simba501:
It should be fine, but your mileage may vary. For example, undervolting values I can run successfully on one version, don't necessarily translate well to another version. If you experience a SOD or lockup, raise the voltages by 25mV incrementally until you don't experience the issue.
[Galaxy S II General] CamoGeko:
Hi mate,

I don't really see any issue with that, try it and let me know how you get on. :)

Hmm, I doubt that it's a good idea mate. I've heard doing that can permanently damage the colour balance, contrast, saturation....etc..

Don't know if that's true but try it at your own risk dude.
[Galaxy S II General] kpyhere:
My qwestion was HOW to do it :)
[Galaxy S II General] CamoGeko:
No idea mate, if you find the method. Please do let me know. ;)
[Galaxy S II General] Entropy512:
Just reduce your brightness, achieves the same result without throwing off color balance and gamma curves like undervolting the power supply of the screen does.

The end result of both is the same - less energy going into the screen pixels.

Undervolting the screen LDO can only be done in the kernel - and it also means that undervolting the screen may be WORSE for power consumption because the screen power supply is on a linear LDO type regulator, not an efficient "buck" type regulator like the CPU is. Reducing brightness PWMs the pixels (turning them on and off rapidly) - reducing the controller voltage reduces total display power consumption, but since that regulator is an LDO, it also reduces the regulator efficiency! So to get a given brightness, undervolting the screen will likely consume MORE power, since PWMing the pixels is efficient and dropping an LDO voltage output is not.
[Galaxy S II General] mobs84:
Here you go. I have attached the stock voltage settings.

Default I/O - SIO

Governor - On Demand

*** Anytime if anyone wants to revert to stock settings, just remove the boot settings from voltage controller and restart the mobile, post restart, whatever settings that shows up in VC is the stock settings*** If you have VC extreme, then save that as the default profile :)
[Galaxy S II General] janreiviardo:
Hi everyone. I just want to share this script I created. It has both andreilux's gpu settings and magicconfig by geko. Though the undervolt in the script is higher so it is a bit more aggressive and if it runs fine on your phone. It will give you the best battery life on Siyah 2.6.11. Goodluck

Just flash the zip like usual.

Some Notes:

It is recommended that you remove boot settings especially if you have the start up service boot by voltage control. Though this script will execute later than boot vc if you have it. It is still better that you just remove any boot settings done on vc.
[Galaxy S II General] UpInTheAir:
Thanks, saved me the effort to try :cool:

Used NotePad++ to change the CPU freq back to Geko's and kept andreilux GPU config. VC app shows all settings have "stuck" on boot (which is good), but noticed the GPU & Charging "Low Power State" is 'greyed out' to 100 MHz/800mV. If I move the 100mHz and then discard changes, it changes to 40Mhz 'greyed out'.

Initially, don't seem to have any problems, but is the above any issue (as maybe VC doesn't know there are 3 GPU steps)?
[Galaxy S II General] janreiviardo:
Tried going to GPU and changing low power state and discharging changes changes to 40mhz. I don't see it greyed out though. May be bec of the theme I'm using. Anyways there shouldnt be any problem as that gpu settings are geko's mc stocks.
[Galaxy S II General] UpInTheAir:
Maybe my terminology "greyed out" was incorrect. When discard changes, changes to 40 from 100.

Don't see any issue yet, have a few quadrant runs and stress tests with no problems :)

Cheers
[Galaxy S II General] pikachu01:
smartassV2 has a screen off profile. It's the sleep ideal frequency ;)

When screen is off, the ideal frequency will be used most of the time.

screen off profile is a profile that is activated when screen is off. Isn't that the correct definition for what smartassV2 and lulzactive is doing?

Only Siyah's ondemand has a screen off profile (via OndemandX). All other ondemand doesn't have that :)

---------- Post added at 04:34 PM ---------- Previous post was at 04:28 PM ----------

Also, undervolting should follow this guide:

http://xdaforums.com/showthread.php?p=18549017

CTRL-F for "undervolt".

It's better than assigning arbitrary values that could cause SODs/bootloop your device or not optimally undervolting your CPU when you can have more than that.

FYI, my undervolt setting:

200MHz: 875mV

500MHz: 875mV

800MHz: 975mV

1000MHz: 1075mV

1200MHz: 1175mV

Pretty conservative, as the voltages are +25mV more than the stable values I've tested. No SODs or bootloop so far.
[Galaxy S II General] jermitano:
nice one sir jan!at last the combo...
[Galaxy S II General] elms327:
sir gek, are these the confirmed stock voltages of our device?
[Galaxy S II General] CamoGeko:
Great to see you here mate. :)

Thanks for posting a link to your undervolting guide, I will add it to the OP a bit later.

I have to disagree with you about the arbitrary values. The values I provide have been tested and deemed safe to use on over 500 SGS2s. I'm not saying that there isn't a chance of incompatibilities but after such a long testing process it's safe to say that they work on 98% of SGS2s out there. Without the need for voltage adjustments of course.

Undervolting can be a proper headache, and there is no reason why the benefits can't be gained by just punching in settings that have been pre-tested for you.

These a stock voltages for my device. :)

Each CPU is slightly different and therefore stock voltages can vary. Best way to find your stock values is remove VC boot settings then reboot your phone. Stock values of your CPU will then be shown.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II General] pikachu01:
Yup. :)

Still, I can see there are a few people who encountered SODs. Hence why UV values should best be based experimentation and testing. :)
[Galaxy S II General] conan3000:
Could someone give the best siyahv6.0b5 settings for my SS S2 I9100? :D
[Galaxy S II General] CamoGeko:
Anyone still using this guys?
[Galaxy S II General] MikiGry:
[MENTION=3301438]geko95gek[/MENTION]

I dont think so. All kernels mentioned in first posts are already outdated and dead.
[Galaxy S II General] CamoGeko:
Hmm okay thanks.

I might pick up a cheap i9100 to carry on with these configs.
[Galaxy S II General] MikiGry:
[MENTION=3301438]geko95gek[/MENTION]

Good idea. Try to install latest Dori and show us your best configs.
[Galaxy S II General] CamoGeko:
I will take a look into it.

Until I get one its probably best to close this thread.

Thanks for your awesome support guys! Never thought it would take off the way it did, if any of you wish to follow me you can find me in the OnePlus X and Nexus 4 forums! Oh and don't be shy, send me a PM.

UPDATE (Nov 2018): I am now residing in the Essential Phone, Samsung and OnePlus forums. If any of you have these devices feel free to look me up. :)

Camo.
[Galaxy S II General] CamoGeko:
There has been a couple yeah, stragenly though when the testing was done privately over the last 3 months or so there was only one occurrence of a SOD.

Anyways I think it's safe to say that the voltages I specify in the OP can be the lowest possible ones of many SGS2 devices out there. If problems do occur then all that needs to be done is adjustment of all voltage range +25. Really, it can't get simpler than that.
[Galaxy S II General] UpInTheAir:
Totally agree, simple. As you previously said, your provided settings are a base / starter, and users can go on from there.

Cheers :)
[Galaxy S II General] pikachu01:
Well, there is also the thing when people's phone can go lower than that (saving more battery). Hence why, using the method I've posted, you'll get the best for your phone. :)
[Galaxy S II General] UpInTheAir:
Yep agree too (no not fence sitting ;))

Maybe OP can add that link to post #1 for new users? Would help them out to fine tune.

Cheers
[Galaxy S II General] h3llboy911:
That's what I have been saying.
[Galaxy S II General] manmad:
ill try this, lets hope it works ^^
[Galaxy S II General] s2dh:
So far I am really impressed....

my battery would normally last up to about 14 hours (I use my phone a lot ;-)

With these tweeks I seem to get over a day, even managed 1d 4 hours...

(I also run green power, gave up on juice defender because there is far to many options).

But so far loving the settings....
[Galaxy S II General] droidphile:
Actual definition should be "a profile that has a max cap on frequency during screen off state." Isn't that why many users use a 'self-made' screen off profile for a governor that hasn't. The only thing the while loop does it to hard limit the max frequency during screen off. In that sense, i stay corrected. SmartassV2 does not have a screen off profile. It spends most of the time in or under sleep_ideal_freq but if the load demands, the freq can go upto max_freq.

Other governors which has built in suspend profile like ondemandx, lulzactive or whatever, does cap the max freq. Even the original Smartass had a suspend profile with freq cap. But not smartassV2.

Moreover, use of lowest frequencies during screen-off state doesn't help much. (This is exactly the reason why wheatley governor was born).

Because using a lower frequency, CPU needs to spend more time to do a work, hence time spend on idle state(not normal idle, but deep idle modes like AFTR & LPA) will be less.

Same work can be done in a shorter time by higher frequency, and hit deep idle soon thus spending more time on lpa or aftr. (LPA & AFTR are part of same state in all gingerbread kernels for i9100 exynos, nevertheless...)

This is applicable especially for lowest freq 100mhz.

So hitting the lowest frequency rapidly when screen is off need not save more power.
[Galaxy S II General] CamoGeko:
No need to hope mate, it's been proven that it works. :)
[Galaxy S II General] pikachu01:
Umm, there's no official definition for a screen off profile. Not sure how you deciced to have a commonly sounding general term such as a screen off profile to include frequency cap.

Screen off profile is a screen off profile. I.e. a profile that activates when the screen is off.

And yes, capping frequency while screen is off can be deterimental, hence smartassV2 was created so that frequency can be favored to a lower frequency. It can, if a high load is detected, scale to the frequency alloted that can handle the task then quickly go back to the lower frequency (which is idle in this case).
[Galaxy S II General] :
Have to agree with Pikachu here. The sole reason i have been using smartassv2 is due to the screen off profile already implemented in the governor. Hence why when someone asked i mentioned to him about it.
[Galaxy S II General] droidphile:
If there's no official explanation for 'screen-off profile', then i can use it to convey the fact that there is no screen-off cap frequency in smartassV2 right? :) Because all the other governors that has a screen-off/suspend profiles does have a cap for freq.

What users in their screen-off profile or governors in the inbuilt screen-off profile should do is to increase the min freq used during screen off to favor spending more time on deep idle.

Something like 100-1400 during screen-on and 200-500 during screen-off.

800 need not be required for screen-off tasks for two reasons.

i) Voltage considerably increases at 800mV

ii) 500 mhz is enough for music playing+supporting apps without stuttering.
[Galaxy S II General] :
You two make valid points all round and it is hard to decide if the actual governor has a screen off profile or not. I say it does cause phone sleeps like a baby when idle. And from few people i spoke to who have been using the governor and who have more knowledge than me actually state that it has in fact a screen off profile hence why no need to set up an extra in setcpu:) can we ask the creator of the governor if there is one or not or check on the sources of it?
[Galaxy S II General] Simba501:
It's a debate of semantics. Both are right.

Sent from my Galaxy Tab 10.1
[Galaxy S II General] kingofthebraves:
I noticed my bln doesn't worn with the acheduler. I hace them on but it says dusabled by scheduler. How do I make bln work together with this config? I'm on siyah 2.6.11 ty!
[Galaxy S II General] droidphile:
You can conclude these:

SmartassV2 and lulzactive has a screen-off profile as in, there is difference in the way CPU is scaled during screen-on and screen-off state.

Only difference between suspend profiles of the two: Entire frequency range is available for smartassV2 during screen-off state. But luzactive will not use frequencies above screen_off_min_step during screen-off. However, by rapidly scaling down to sleep_ideal_freq, smartassV2 makes sure it uses lower frequencies during screen off.

If you want more details, you can ask Erasmux and Tegrak, the authors of smartassv2 and lulzactive respectively. (Both are members of xda) :)

And here are the sources, from Siyah bitbucket.

for SmartassV2

for Lulzactive
[Galaxy S II General] :
Thanks Droidphile.:) Much appreciated. No harm in learning is there:)
[Galaxy S II General] pepe2909:
I tried your configuration on siyah kernel v2.6.4, bfq/ondemand with 200/1000, and and works well, thank you :)
[Galaxy S II General] Zimaia:
Hi geko95gek and everybody else that are making this thread a must follow!!

My point is i actually don't need more than 1 day of battery because even if the battery last more than that i'm going to charge it anyway every day.

So can someone point me a config settings to push a little bit more from my phone performance even if it compromise the battery?? Like i said i only need a 1 day battery life.

Thanks a lot for some guide about this
[Galaxy S II General] CamoGeko:
That's easy, use 200Mhz - 1400Mhz with my config, noop + conservative governor and you will have great performance.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II General] lolcoelho:
Can anyone help me?

I have the full version and when I save the processor to be between 100 and 800 mhz I lose the settings when I restart my phone, I tried to uninstall and use the free version but every time I lose the settings of the processor already saved the boot (the 2 options) and still not saved.

does anyone have a suggestion?
[Galaxy S II General] :
Yes. Wait for the phone to load up first and wait for a couple of minutes before going into Voltage control and checking
[Galaxy S II General] XDA mark:
Im on 2.6.7 and all is good for me too.

Geko, you have tested all the version of Siyah right (with your config)? Can you recomand: 2.6.7 or 2.6.11? One of the reasons Im kind of not flashing .11 is that it includes that battery/charging tweak:

"set topoff current in battery driver to 100mA (stock value is 200mA) to ensure that the battery is fully charged before the charger circuit stops charging. Your 100% level will be a bit higher than before."

I saw some people posting that this tweak could have negative effect on yor battery. I also read in a thread (dont remember which one, it was one of the big threads with guides and info) that if you have this tweak "dont charge to full 100% to often if you love your battery". I paid 30 euro's for this extended battery, wouldn't want anything to happen. Also I wouldn't want for the battery to explode or something and to wake up in a burning room xD I put my phone in the charger everynight so it charges to 100% every night (and stays in the charger for a long time even after its fully charged, until I wake up).

So:

-2.6.11 better then .7? (In which terms? Batterylife, performance?)

-Is that topoff current to 100mA tweak something I should be worried about?

Kind regards ;)
[Galaxy S II General] poochewer:
Its crazy to worry about that battery tweak! Beleive me there is nothing in the slightest to worry about in that tweak.

Not to mention that even if it did do something to your battery, they cost peanuts to replace!

Just think about it, the cost of a new battery is less than what you spend a month on phonecalls!
[Galaxy S II General] :
Flash 2.6.11. Follow the guide that Geko gives. Do not go for that extra tweak and let the magic configuration by Geko work its magic. I am using my own setup of course but not using that extra tweak and could not be happier with both performance and battery life. But again that is down to your choice i can only give you my opinion based to what i am using. And near enough mine and Gekos setup is the same
[Galaxy S II General] mekhonte:
Dude you're already killing your battery!
[Galaxy S II General] UpInTheAir:
CWM S91voltctrl Magic Tweaks "Stock" + AndreiLux GPU

For those that wish to use Geko95Gek "stock" in combo with AndreiLux GPU settings, please find CWM flashable attached. I have been running this all morning with no issues :cool: So credit to all those that have had input into the settings, kernel, Voltage Control app and script. Thanks.

Very similar to XDA member janreiviardo, except script cleaned up 'slightly' and 'missing' GPU voltage added for first step, as well as the less aggressive Geko95Gek clock voltages. ;)

ondemand BFQ

200-1200MHz

1450 1300 1200 1100 1000 950 900 900

GPU 40 133 267

90% 25% 90% 40%

GPU voltages 800000 800000 950000

This was created from an existing Voltage Control app script and ammended to suit. :)

Make sure any conflicting scripts are removed from init.d folder and Voltage Controll app "Remove boot settings" before flashing. No need to touch any VC app settings, as may override the script. ;)

Voltage control app will not currently show all 3 GPU power states and voltages, but you can check with terminal or with root explorer app;

cat /sys/class/misc/gpu_clock_control/gpu_control

cat /sys/class/misc/gpu_voltage_control/gpu_control

I cannot yet get "cat /sys/class/misc/gpu_voltage_control/gpu_control" to work in terminal (don't know why), but the 3 GPU voltages are showing in "/sys/class/misc/gpu_voltage_control/gpu_control" folder. Any ideas ??...........
[Galaxy S II General] rexboy:
I do the same, didnt realise it was not good for the battery. Just assumed with these modern day Li-ion batteries it didnt make much difference. I assumed they had a built in chip of some sort to prevent overcharge or revert to some kind of trickle charge, so cheers for the tip.

On a side note, flashed to Siyah 2.6.11 and applied all the voltage settings etc as per first posts and phone was fine screen on, but when off, literally lost 1% every couple of minutes so within 1 hr lost went from 3/4 charged to flat. No way that could be right so restored a prior CWM backup few days prior and did it all over again.

Dont know why but this time the settings worked great for me. 100% at 9am, light - moderate use and by 6pm its on 91%, thats crazy for me. Normally over 9hrs regardless of use it would of lost 30%+ so cheers for the settings.
[Galaxy S II General] gr8hairy1:
It's not the 'charging' that is bad for it. As they do have a chip that prevents over-charging. It's the battery being kept at 100%. From 80% to 100% (roughly) lithium ion batteries are In a higher state of activity. That leads to shortened life span, the closer to 100% the stronger the effect. That doesn't mean immediate damage. But leaving the phone plugged in for extended periods of time on a regular basis will undeniably shorten the life span.

Sent from my páhhōniē
[Galaxy S II General] droidphile:
Few facts and fun about Lithium-ion battery

Turning off the device and charging will help uninterrupted reach of threshold voltage and gauge will be able to determine correctly the correct saturation current to end the charge. (normally, 3% of the rated current).

Do not charge when it's too hot or too cold

Li-ion battery need

not

be fully charged to 100%. Partial charge is better.

The charge-notification (sound or screen-on) need not always indicate accurate full charge

Li-ion battery does not trickle charge

If kept at fully discharged state for longer time, it can harm the protection circuit so apply a little charge immediately after full discharge.

Battery lasts longest during 20% to 80% and during cool temperatures compared to counter-conditions

Detailed reading here and here.
[Galaxy S II General] UpInTheAir:
Thanks, useful useful info, but battery charging and care is really nothing to do with Magic Tweaks....
[Galaxy S II General] droidphile:
I know :)

But last few posts were about fully charging battery and stuff.
[Galaxy S II General] XDA mark:
Thanks for all the information guys! This is why I love XDA :)

Im going to flash 2.6.11, like people say I shouldn't worry about that included battery tweak.
[Galaxy S II General] UpInTheAir:
Its all appreciated anyway. :)
[Galaxy S II General] pepe2909:
Turkbey rom v 30.1 + siyah kernel 2.6.4 ( bfq/ondemand + 200/1000 )+ data background+sync enable, gsm mode+data on, display off over night, with your magic configuration.
[Galaxy S II General] blk15:
Great to see you've created a thread on your configs geko!!!

Been using your configs since around v1 and it has always provided me with the best battery life & performance. Keep up the good work :)
[Galaxy S II General] CamoGeko:
Great combo by the sounds of it. Not surprising really that you're getting fantastic results.

Yeah, had to do it mate. Too much demand haha :p

Thanks very much for your testing in the early days.
[Galaxy S II General] pepe2909:
I tried version noop/conservative with 200/1400 but the battery discharges faster :(
[Galaxy S II General] CamoGeko:
Try it with 200-1000 or 200-1200, should still be very smooth and save a bit of battery. It's what I'm using right now.