yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] mekhonte:
deadline/sleepy for smoothness and noop/conservative for battery life.
[Galaxy S II General] GJ123:
Yeah I thought the same, but do you feel a lot of difference in smoothness?
[Galaxy S II General] It_ler:
Hmm ... just applied MagicConfig v0.3.1 settings on RedPill rev1.3 with Noop/Conservative and had a BSOD after a while (about 2 hours of doing nothing) when shutting down the phone.

Phone showed black screen and did not recognize any key (not even long press Power button).

So, I had to pull out battery, put in after some seconds and restart the phone.

Now everything seems to be fine again.

Will keep an eye on it and report back after a full battery cycle.

Here are my latest test result without customizing (UV, UC, etc.) for different kernels => http://xdaforums.com/showpost.php?p=22676908&postcount=10080
[Galaxy S II General] mekhonte:
Only in some apps like 'message' you can tell it. try to open a long thread or send sms, in conservative it's a bit Laggy.
[Galaxy S II General] mekhonte:
If you have access to try l2tp vpn and see how it goes.
[Galaxy S II General] It_ler:
Is your post an answer or response to my quoted post?

Or is it just a mistake?

Sorry, I can not see any connection.

Maybe I misunderstand your comment.
[Galaxy S II General] mekhonte:
I wish I knew !!

I have problem with l2tp vpn. I am asking you: if you have access to l2tp vpn plz test it on redpill 1.3 and see whether you have that problem too or not.
[Galaxy S II General] It_ler:
Oh, that's what you are looking for.

Maybe you should ask this question in the RedPill kernel thread directly, as it is off topic here.

There you might get an answer sooner.

Good luck !
[Galaxy S II General] It_ler:
With RedPill rev 1.3 kernel, running on noop/conservative, MagicConfig v0.3.1 without UC or OC (200 - 1200 MHz with recommended/safe UV), my phone does not show a significantly different battery life.

I will try it again with deadline/sleepy and report back.

Maybe my phone needs a little bit more aggressive UV to show better battery savings ?!

Or RedPill rev 1.3 kernel has already too good battery life to see a significantly better battery life after undervolting ?!

P.S.:

No more issues with MagicConfig v0.3.1 after first reboot. Seem to be stable UV settings on my phone too.

Thanks geko95gek for sharing your config and your support and advise in the different threads !
[Galaxy S II General] Xroom01:
good job thanks
[Galaxy S II General] Jibreil:
People try SIO + hyper along with Magic Config - it gives great battery life minus the SOD or lags.
[Galaxy S II General] CamoGeko:
That combo works well too, I still need to test the battery consumption on it though.

Logged using an SGS2 type droid while floating in CM9 quadrant...
[Galaxy S II General] XDA mark:
I just wanted to say I am now using NEAK kernel (it's totaly awesome, btw) and the same setup I used on Siyah. So Geko's MagicConfig (+50mV as I always used, because my phone is stupid) works on NEAK.

Edit: Running conservative + noop
[Galaxy S II General] Lownita:
What governor/scheduler would give best performance with redpill kernel? :)
[Galaxy S II General] CamoGeko:
I'd say SIO + Hyper, no lags or slowdowns here.

Logged using an SGS2 type droid while floating in CM9 quadrant...
[Galaxy S II General] djclark25:
Thanks for the suggestions. Seem to work great.

Out of interest, what font do you use. That is exactly what I am looking for :)
[Galaxy S II General] CamoGeko:
That's AndreaS Hand Upright font. :)
[Galaxy S II General] benj9:
According to the name "hyper" I would guess the governor is better for speed than for battery life. Sorry for the question, I know there is somewhere a governor thread, but I am still confused cause the kernel makers just invent new names :)
[Galaxy S II General] CamoGeko:
I believe there is an explanation of the Hyper governor in the RedPill kernel thread. ;)
[Galaxy S II General] predr.ag:
Had similar question in mind thx.
[Galaxy S II General] jermitano:
im having freezes with this sched/gov combo...sio-sleepy works better buy noop-conservative works best for mine mate...
[Galaxy S II General] sid9922:
Yeah.. Noop+Conservative in NEAK kernel with geko's runs very smooth..(i even UV my setting a lil bit more)..
[Galaxy S II General] danielsf:
I really love this app, thank you. I really hope you carry on this apps support for ICS kernels (when the kernel source code is released, and we hopeful get some custom kernels :D) This app + ICS's 2d hw acceleration + this apps gpu control (overclock 2d graphics scaling frequency) = unfathomable ICS bliss :D
[Galaxy S II General] CamoGeko:
I shall be testing NEAK with my MagicConfig very soon, it will be added to the OP if I find it satisfactory.

Logged using an SGS2 type droid while floating in CM9 quadrant...
[Galaxy S II General] :
well get your lazy ass out of the cm9 galaxy and start coming back down to Gingerbread heaven and test the lite NEAK..it is a kernel worth trying out. Using it at the moment left everything stock apart from minor undervolting and this kernel works wonders....
[Galaxy S II General] sid9922:
+1

Ten char
[Galaxy S II General] CamoGeko:
Lol guys, hold your horses. This config initially was only supposed to be for Siyah. Anyways, I'll be jumping on the latest CheckRom after backing up my CM9 baby. Then real world testing will commence on NEAK hopefully later today.

Logged using an SGS2 type droid while floating in CM9 quadrant...
[Galaxy S II General] :
Well glad to have you Checked in;)
[Galaxy S II General] CamoGeko:
Not quite there yet, will be soon but really gonna hate wiping though. Lol :p

Logged using an SGS2 type droid while floating in CM9 quadrant...
[Galaxy S II General] mekhonte:
Flashed N.E.A.K 1.3.3x over siyah 2.6.7 for almost a day.it's too soon to judge battery life but I think it's even better than 2.6.7 or 2.6.9 but maybe not as sharp as siyah.below is undervolting that i'm using without any problem:

200 - 1000

1000: 1050mv

800: 950mv

500: 900mv

200: 875 mv

Noop+lulzactive
[Galaxy S II General] halkoliiteri:
Now testing N.E.A.K. 1.3.3 + Thunderbolt-scripts + MagicConfig v0.3.1 for Voltage Control -settings.

Gov: Ondemand

Scheduler: SIO

Voltages from MagicConfig (GPU-high is 1000mV because my phone doesn't handle 950mV@266Mhz)

Range: 200-1000Mhz

ROM: CheckRom RevoHD v6

Link to MagicConf: http://xdaforums.com/show....php?t=1466017

In normal use there are no any lags and everything works fine and very fast. Benchmarks gives naturally a little bit lower scores than default settings (for example Quadrant 3700p-->3100p), but who cares

No SOD's or FC's. Solid stable in my phone so far.

I'll report batterystats after few cycles Maybe this combo is the "Great One" in overall...
[Galaxy S II General] braudrist:
Is it normal the BUS frequency for 100 - 500MHZ is at 133MHz, 266MHz for 800MHz and 400MHz for 1000MHz+ ?
[Galaxy S II General] CamoGeko:
Yeah that is fine.

I usually have it like this:

100Mhz/200Mhz/500Mhz = 133 BUS, 800Mhz/1000Mhz = 266 BUS, Then anything higher is set at 400 BUS.
[Galaxy S II General] ogblaz:
Been using this voltage settings from the first page(except the max i left it at 1200) works great, battery is good will test it some more, thanks man
[Galaxy S II General] jermitano:
will be doing a parallel neak test too mate...just sucks that the promised released isnt there yet but ive been hearing a lot of positives so far for neak
[Galaxy S II General] XDA mark:
Have been on NEAK for two or three days (I have so much going on that I don't remember lol)

It's a pretty weird story for me though. Started using NEAK with the same settings I used on Siyah, your config + 50mV because my phone is handicaped xD

Anyway, I got freezes. No before you change your opinion of NEAK, let me explain. I always got the freezes while using the stock browser. I didn't realise that in the beginning, so I guesed NEAK can't handle the Magicconfig. I started adding 25mV to each CPU step and also GPU... still freezes once in a while, everytime in the browser.

Now after some talk with Stifler who is also using CheckROM V6+NEAK and got freezes only when using the browser, we kind of think it's connected to the fact that we use a browser mod (downloaded from the CheckROM kitchen app) for fullscreen and useragent tweaks. Leo from CheckROM said it couldn't cause these kind of problems, because the browser mod is a very basic and small tweak.

Now I don't know what's the deal with all of this, but once Stifler started using Dolphin browser he didn't get any more freezes. Other reactions from people in the NEAK thread indicate that they don't have freezes in the browser when NOT using the mod.

At the moment I am running stock NEAK voltages with conservative + noop and still using that browser with the mod. If it freezes again, it's clear it's got something to do with that. Because I just can't imagine my phone could handle undervolting on Siyah and not anymore on NEAK. Maybe I will try a day with Dolphin browser + MagicConfig, also a way to test if it's the stock browser or not.

Anyway it's nice you are going to check out this kernel... I hope it meets the "Geko requirements". It's really a nice kernel IMO.

Edit: see attactment lol. For my testing tomorrow haha
[Galaxy S II General] :
Yes i can vouch for what Mark has said. I am back using my old settings and yes i do UV very aggressively and since i have Dolphin browser i have not had any freezes since. And yes it is a gorgeous kernel and very happy with it..Try it out buddy
[Galaxy S II General] Lownita:
I am trying deadline+hyper on redpill and so far it looks good! I am still looking for smoothest performance possible :)
[Galaxy S II General] CamoGeko:
Running NEAK now with my CFG. NOOP + ondemand and loving it so far. Very low idle drain. :)

Thanks to mark and stifler for feedback.
[Galaxy S II General] californicated:
My phone freezed once while surfing. Apart from that there are no problems when watching videos, playing games, etc. Can it be due to UV?
[Galaxy S II General] sianzb0i:
Thats how i had it too :)
[Galaxy S II General] so_ony:
Hey Guys ;)

I used Siyah Kernel 2.6.9 with your config and had a little difference of your voltages but wanted to post my "life of Battery" :

1.I have the 2000 mAh Battery ;)

2. Using checkrom V6

* CPU:

*** Range 100Mhz - 1400Mhz ***

+ VOLTAGES:

100Mhz - 875mV => not in use because of same voltage as 200 mhz

200Mhz - 875mV

500Mhz - 925mv

800Mhz - 975mv

1000Mhz - 1075mV

1200Mhz - 1175mV

* GPU:

*** 114Mhz low / 267Mhz high ***

+ VOLTAGES:

800mV low

950mV high

=> my screens are lost because of doing a full wipe so sry for no pictures ;)

my battery use was :

using W-lan during the whole test , listening to Music 2Hrs, Using the Webbrowser using 3 Hrs, and Calling 1 Hr

=> 2 Days and 3 Hours :) i think a really good end of my test :)

i will go on with Neak Kernel now for testing !

Hope the screens are safe there for showing you my result
[Galaxy S II General] aceofclubs:
Did exactly what you suggested with siyah and voltage control.

Made a huge difference. About 1.5hrs more screen on time.

Previously used cfroot KK5 and setcpu to UV/UC and by 4.5 to 5 hours I'd be looking for a charger.

Thanks a million for this. I have smoother, better performance all round and what is a record for battery performance for me.

I'll be sticking to this setup for sometime now. Unless neak really is better.
[Galaxy S II General] so_ony:
i'll test the same as you now but with litlle differences of voltage use :)

it is a new kernel in the line up fpr battery efficient kernels. Hope it will us show a good result :)

---------- Post added at 11:28 AM ---------- Previous post was at 11:22 AM ----------

Hey ;)

i am using now the Neak Kernel for 3 Hours and i have no Problems with the Stock Browser ;) I am using Checkrom V6 , too but without the mods you have described for the browser in your text ;)
[Galaxy S II General] ole12:
I use NEAK kernel with heavy UV, i dont have any freeze with browser mod (useragent+fullscreen+glow)
[Galaxy S II General] XDA mark:
Currently results today with NEAK and magic config with dolphin browser:

No freezes at all. Super smooth, great battery life.

Dont know why some people get the freezes and some dont :P

Edit: Ok, looks like the freezes are gone... really should have happened by now if it was related to NEAK not being able to handle the undervolting. Haven't used the stock browser with the mod today, only Dolphin. So I kind of am concluding it's related to that... I really like Dolphin browser, but it's not as smooth as the stock one. Wish I could go back to using that one :(

Edit2: 7% left. At the moment 13 hours of standby, a little over 4 hours of screen time. Probably going to reach 14 hours and 4 and a half screen. It's pretty good, all though I have the 2000mAh battery. And I remember the time I had 15+ hours/5+ hours screen time and still 20+% left... that was on Foxhound 3.0 with Siyah 2.6.7 or .9.
[Galaxy S II General] It_ler:
FYI:

My latest kernel test results - especially added some tests with MagicConfig running on RedPill rev1.3 => http://xdaforums.com/showpost.php?p=22911850&postcount=10156

Although "conservative" UV doesn't have a significant difference for battery life on my phone with my "normal" usage, your MC thread inspired me to check out different voltages, io scheds and governors.

Thanks for that geko95gek !
[Galaxy S II General] so_ony:
this is how it should be ! Everyone is testing best settings, to show best results !

Thank your for your information and work ! even if i finished my test with NEAK kernel and post my results here i would start to test RedPill Kernel !
[Galaxy S II General] CamoGeko:
Its great that you guys are testing out various kernels and using my MagicConfig with them to see where it has the best effect. Thank you for that.

If we get enough data going here, I will try and get another post up beneath the OP and collate all this information there as well for benefit of others .

Logged using an SGS2 type droid while floating in CheckROM quadrant...
[Galaxy S II General] so_ony:
i have time for testing all this kernels now ;)

and your given thread was for me the way to know more about voltage settings so i read through that and now i'll take all the given kernels and will test them with voltage settings ;) i'll post after every battery test my results here + screenshots !

your post was the beginning of very usefull battery usage geko! Thank you for that! Very beautiful to see that we can save lots of battery with your information you have given to us !
[Galaxy S II General] annie42:
Hi guys, I flashed the script from this thread which contain magicconfig and the GPU tweak. The question is how do I remove it? I think it's an init.d script.

Thank you :)
[Galaxy S II General] so_ony:
What do you mean with "flashing the script" you have to do the settings in voltage control and if you wanna have to remove it just make the normal settings in voltage control or just flash the kernel new
[Galaxy S II General] UpInTheAir:
Edit: the above post suggestion won't work if script is flashed via CWM recovery. Because it's not enabled by a voltage control app script and has a 3rd GPU step enabled, and not seen voltage control.

1. Use a root file explorer such as ES File Explorer or Root Explorer and navigate to:

2. system/etc/init.d

3. Mount system r/w

4. Delete script

5. Reboot

:D
[Galaxy S II General] mekhonte:
My result from N.E.A.K 1.3.3x
[Galaxy S II General] mekhonte:
My result and configs from N.E.A.K 1.3.3x
[Galaxy S II General] 6pudu5:
Great guide! With Turkbey Rom V37 and RedPill kernel configured NOOP-CONSERVATIVE slightly lower as the battery is super recommended.
[Galaxy S II General] so_ony:
Hey ;)

I have already mentioned that i would test the NEAK Kernel 1.3.3x!

My results are seen in the Screenshots !

I used :

____

ROM : Checkrom V6

Kernel: NEAK Kernel 1.3.3x

_______

i used my phone at one night without wlan & data you see it in the picture ;)

normal use with wlan & data , whatsapp, browser, calling

result was about 2 Days and 4 Hours + (2-3 hours because of 15% Battery left;)

____

i have 15 % Battery in the end, so it want go for 2-3 hrs more but have to cancel the test because of going outside, so have to charge battery :)

______

Voltages:

* CPU:

*** Range 200Mhz - 1000Mhz ***

+ VOLTAGES:

200Mhz - 875mV

500Mhz - 925mv

800Mhz - 975mv

1000Mhz - 1075mV

___

Screens:
[Galaxy S II General] mekhonte:
How much of screen-on you got?

What's your battery capacity? 1650 or 2000 ¿
[Galaxy S II General] XDA mark:
How much screen time did you have? Without that info I can never conclude if it's good or bad battery life.

At the moment, my stats are:

-1 day and 16 hours standby time

-3 hours screen time total

-22% battery left.

I am now on vacation so I dont have 3G on at all, only wifi some times. That also helps battery life a lot off course :P
[Galaxy S II General] so_ony:
screen time was 5 hours and 23 minutes and i have the 2000mAh Battery ;) sorry for missing this information!
[Galaxy S II General] CamoGeko:
Nice one mate. I'm interested to know how are you finding NOOP + Conservative on NEAK?

At the moment I'm test driving NOOP + Ondemand on it since yesterday and all is smooth. Battery drain has been acceptable as well. Since I'm doing a real world test, I shall see what the improvement is once the kernel and ROM settles.

Logged using an SGS2 type droid while floating in CheckROM quadrant...
[Galaxy S II General] mekhonte:
I got 1 day and 2h

4.45 h screen on

45 min 2G and lots of sms

Been using Yahoo mail and Tapatalk

1650 battery

ROM Hyperdroid v6.1.17
[Galaxy S II General] XDA mark:
I find it ok. The phone is smooth as hell and all is well. See the attachment for my results.

I just put my phone in the charger and CPU spy stats are gone. Had about 86% deepsleep, and the rest spread over 200, 500 and 1200MHz mostly.
[Galaxy S II General] so_ony:
which voltage settings did you use?
[Galaxy S II General] sid9922:
@geko

Mate, noop+conservative on NEAK kernel was phenomenal..im running it 200-1000mhz.. 3g on when im outside and wifi when im at home..4 emails updating every 2hrs..1 and a half hr call..xda and youtube and opera mobile most of the time..i just UV -50mhz all steps..here are some screenshot..this is with stock 1650mah battery
[Galaxy S II General] UpInTheAir:
Thanks for the config, good starting point for UV. I'll see how it goes before and further changes (if any).

Cheers :)
[Galaxy S II General] radicalgel:
Great Work

Nice work mate. Great to finally see a thread with your base settings. These really helped when I started out with UV/OC. So here's a BIG thanks!!!

Anyone bringing negativity in to this thread should seriously get their head examined, considering geko is probably one of the most helpful guys on these forums. I've seen him answer questions from n00bs (some seriously dumb questions too) over and over, without ever being rude or losing his patience. That ain't easy.
[Galaxy S II General] lpsi2000:
I agree your assessment on the 100Mhz not saving much or any at all. I started disabling it 3 weeks ago.
[Galaxy S II General] droidphile:
Yes, i have the same opinion.

Second graph in this thread by Ezekeel, shows the difference between lower and higher frequency steps' battery consumption with and without LPA/deep idle. As it occurs, higher frequency supports race-to-idle better there :)

Again, "100 mhz bad compared to 200 mhz" depends on we're using lpa or not. (sched_mc=2 or 3).

Anyhow, since only first core can hit lpa, screen-off profiles with: different governor, hard limiting frequency, switching to single core mode, etc actually does a little harm than good by delaying for race-to-idle.
[Galaxy S II General] sid9922:
I lil noob question..so above posts only shows that 100mhz will consume more battery? Hmmm..right now im running 100-1000mhz..is it better to use 200-1000mhz instead?
[Galaxy S II General] Dark_Lord0122:
I gotta say that Geko did a really good job with it,

i am using his tweaks with lower'd voltages i get alittle over 6000 in antutu.
[Galaxy S II General] CamoGeko:
I'd have to agree with Entropy and droidphile mate, in my experience having it set 100Mhz doesn't really provide any noticeable battery life gains. I just haven't taken a look at any info proving this point before.

It's definitely making sense though, since the CPU doesn't have to go to 200Mhz as the next frequency when it scales up. It can go straight to 500Mhz (of course dependant on the governor you're using).

I guess its that illusion, having a lower number = better results.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II General] mekhonte:
Does conservative governor have built-in screen-off profile like ondemand?
[Galaxy S II General] :
No. smartassv2 has.. great governor:D and lulzactive have
[Galaxy S II General] sid9922:
So should i go along with 200mhz as the lowest step and 1000mhz as the highest mate?
[Galaxy S II General] :
yes pump it to 200. that is what i am using;)
[Galaxy S II General] XDA mark:
You can try that, yes. If you think the phone isn't fast enough, you can always change it to 1200 or higher.

Just to be clear (and no offence to geko): there isn't a secret configuration that turns your phone into a super-mega-god with a battery that will last you forever. It's all just common sense. If you set 200-1000MHz, your phone will last longer then if you set it to 200-12000MHz. But it will offcourse last even longer if you set it to 200-800MHz. Every person should see what he likes. Play around with these settings, till you reach your own "perfect configuration". I for example can't use these Undervolt settings, since my phone can't handle it. So I am trying it out out with 50 mV more on each CPU frecuency.

What Geko did is search (for a long period) which undervolting settings are the bottom line where almost everybody's phone will still function properly. While some people will hate (based on the name probably, they don't like the word magic in it) I think it's good Geko did this. I often wanted to ask how far I can undervolt before I reach the "from here on it's not sure anymore" barrier. Yes, you could lower 25mV each day. But that will take you a few days to find out the barrier. This way you know where to start.
[Galaxy S II General] :
You are right in what you are saying. But think about this though. Higher cpu means quicker process is being done. Lower the cpu means more time for the process being done. Hence why higher apps and scrolling seems faster were lower you have that extra second to wait when opening apps and sometimes get a bit of lag when scrolling through screens. Hence why i always leave stock cpu clock speeds:)
[Galaxy S II General] CamoGeko:
I'd say so yeah, it will improve smoothness and stability. :)

The range I give in the OP is so people can try it out, I'm sure difference becomes evident after a short use.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II General] XDA mark:
Hey I agree with you, I always use stock cpu clock speeds as well :)
[Galaxy S II General] :
i only started going back to 200 again when music started going all funny on me. And since i have done a Geko and started playing with settings and got my own little configuration going i have stuck by 200 as min from now on:) And like someone said being on 200 gives that tad bit of smoothness instead of the way if you was stuck on 100..something like that i think
[Galaxy S II General] shmic:
Big thanks Greko. Im using this settings now for 2 weeks, and im very satisfied. Since i am a noob this was very handy.

Keep a god work
[Galaxy S II General] CamoGeko:
You're welcome mate, I'm happy to know that you have excellent results just like everyone else. Thanks for the feedback. :)

PS. I am going to add the screenshots today in the OP to make the whole application of these settings easier to understand.
[Galaxy S II General] darkhorses:
+1 Nice tweak and now at last i have a decent battry life (running CriskeloRom V38 for the moment)