[TWEAK](SIYAH/REDPILL/N.E.A.K.)MagicConfig for VC & NOW for ExTweaks(GB/ICS)
MagicConfig (previously "mycfg")
Universal UV tweak to help you easily get an great improvement in battery life, Gingerbread and Ice Cream Sandwich Compatible!
First step for any Undervolting beginner.
Due to receiving endless requests few months back for me to post my "MagicConfig" for SiyahKernel and as I'm typing this right now I still have to send out 20+ PMs every single day on this subject. So I have finally decided to make a thread for it, now it can be discussed and found here without needing to contact me.
Obviously I only wanted to do this after extensive "real world" testing myself and MagicConfig's initial user's confirmation that it works astonishingly well, since then it has been picked up and loved by many many users more. IT TOOK ME OVER 4 MONTHS TO MAKE SURE THIS CONFIG WOULD BE COMPATIBLE WITH ALMOST ALL SGS2s. HOWEVER, PLEASE READ THE WHOLE POST CAREFULLY BEFORE TRYING TO APPLY THESE SETTINGS.
Now, what you will find below is not a script of any kind so there is no need to download or flash anything. All you need to do is simply input these values into Voltage Control app which can be downloaded free from the Market.
I have done my best to test the configuration and to my knowledge it should work on most of Galaxy S2 devices out there. It is designed to bring balance between smoothness and battery life, I have spent over 3 months (since the betas) going through all of SiyahKernel releases to find the perfect combinations of Schedulers and Governors that are included within each release of the Kernel. If you do have issues or if you needed to make alterations of any kind to make it work for you (not including reducing voltages further), please report this here. Thank You.
*** N.E.A.K. Kernel only allows highest frequency of 1200Mhz ***
*** RedPill Kernel can't handle these voltages on some devices, if you get freezes or reboots please raise all voltages by +25mV ***
114Mhz low / 267Mhz high
*** Latest SiyahKernel v2.6.13 doesn't allow step of 114Mhz, please use 133Mhz instead ***
* OTHER INFO:
Mainly at the moment I just stick to NOOP + ONDEMAND on N.E.A.K. 2.0.4x, running CyanogenMOD 9 and CPU at 200Mhz - 1000Mhz.
As I always say though, these voltage settings are a safe stable base and could be tweaked to your liking once you get experienced with undervolting.
Also can I ask you kindly not to post this config in any other threads, instead if someone asks for it then just direct them to this thread please. Thanks!
* SCREENSHOTS (this is what it should look like after all parameters are set):
That's about it. If you want to save even more battery juice then just reduce the highest CPU frequency down to 1000Mhz or even 800Mhz.
Also, I found that having the lowest frequency set to 200Mhz improves smoothness quite a bit and doesn't impact battery too much, of course it's also slightly more stable. Potentially, this can conserve even more battery life.
Do not have multiple CPU / Voltage configuration apps installed at the same time, you will most likely get conflicts.
If you start having issues (screen going black, freezes or reboots then raise all voltages by +25mV) then everything should work as normal. If it doesn't, then raise by another +25mV.
Enjoy the smoothness everyone. As always, feedback is greatly welcomed and is very helpful to others. Thank you!
* FURTHER INFO:
I know that time will come when you will want to use Lulzactive governor which can be tweaked to your liking using the Lulzactive app. Here is a thread by Stifler69 which has some excellent settings which you can start with: http://forum.xda-developers.com/show....php?t=1525048
*** gokhanmoral (for creating such a wonderful Kernel, you are the man!)
*** pongster and hyperdroid team (the Kernel is so amazing that it feels like I'm taking a trip to see how far the rabbit hole goes!)
*** simone201 (this new lightweight kernel you created is so awesome, it's a perfect pairing with CheckROM and my MagicConfig!)
*** xan (for making Voltage Control so compatible with Siyah and RedPill, that GUI is a treat to use, so easy!)
*** stifler69 (for being really helpful to others all around the Galaxy S2 forum section and providing good battery saving Lulzactive app settings!)
*** all Siyah users (those that requested my config in the early stages and reported feedback, you have really made it what it is today!)
FINAL WORDS, PLEASE READ:
IF YOU HAVE TESTED THIS CONFIG AND RECEIVED EXCELLENT BATTERY LIFE AND SMOOTH PERFORMANCE LIKE THE OTHER 900+ USERS, THEN ALL I ASK IS THAT YOU RATE THE THREAD 5* STARS AT THE TOP OF THIS PAGE AND CLICK THANKS BELOW THIS POST.
ALSO IT HELPS NEW USERS IF YOU PUT A LINK TO THIS THREAD IN YOUR SIGNATURE, THEN THEY CAN EASILY FIND IT AND RECEIVE THE SAME IMPROVEMENTS AS YOU ARE GETTING FROM IT.
This is to inform you that your settings are excellent.
Have tested them on Siyah 2.6.7 /2.6.8 and 2.6.9 with Omega B&B 10.2 rom and, it works wonderfull on all.
Very smooth and very little battery drain.
For information battery drain during night time over an 8 hours period (Wifi/Data/Background Data on off) is less than 2%.
I even got 0% during one night (battery level at 35% at 12 pm and still at 35% at 08:00 am);
"So i tested out your config, and oh my do i get amazing battery life! whenever i go to school id have it drain down to about 92% after my first class which was roughly 1 hour and 35 minutes, and thats without touching it, this time it only went down to 98% and that was with music playing too some of the time! Thanks man! i read about your 0.3.1 config, whens that coming out? lol"
...btw im using ur config right now on 2.6.9...and with the kernel settling in im experiencing phenomenal batt life...2 hrs watching mkv film/screen on 6hrs/3g-h+ 8hrs/20 mins call/6hrs wifi/download game data (almost 1gb)...18hrs and still have 40% juice on it...
More feedback for you geko. Been using your magic config for about a week now and my phone has been as smooth as a ken doll.
I use bfg and ondemand 200Mhz - 1000Mhz plus all your voltages with the exception 200Mhz I use 875mv as it causes me no issues.
Getting around 48hrs uptime (from 24hrs - 32 hrs) which means the battery saving is great (and if I cared about the environment greener also)
Since yesterday i'm using last siyah with settings from first post on noop-conservative combo with only difference that I set max to 1200..indeed those values make a huge difference on battery drain and also phone is stable like a rock!(omega 10.2 ROM)
Thanks a lot :thumbup:
Just would like to say thanx and i found this thread most useful, i was using siyah kernels before i went over to trying ics roms and i got amazing battery life out of my phone from following thid thread...
As you can see in the screenshot I was on 50% battery at that time, so by the power of addition we can conclude that 6+ hours screen time is very much possible and isn't a myth.
Recent kernel comparison report:
Massive thanks to It_ler for conducting the following comparisons (28-02-2012), please read the whole report carefully to avoid unnecessary questions.[/SIZE][/U][/B][/CENTER]
Results for SpeedMod / Phenomenal / N.E.A.K. / Siyah / RedPill / stock kernels
Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.
For all custom kernels, I was running on Frankenstein XWLA4 ROM (Modem: XXKL1).
For stock kernels, I was running on the corresponding stock ROM.
Always using the Samsung's standard / stock 1650mAh battery.
For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.
For N.E.A.K. I tested VR schedule, Lulzactive governor, only enabled sched_mc and the rest unchanged defaults.
For RedPill kernel, I tested completely default settings (deadline / ondemand) without any change.
For RedPill (MC, noop/conservative), I tested geko95gek's MagicConfig v0.3.1 settings with noop / conservative on 200-1200 MHz (no UC or OC, only recommended/safe UV).
For RedPill (MC, dealine/sleepy), I tested geko95gek's MagicConfig v0.3.1 settings with deadline / sleepy on 200-1200 MHz (no UC or OC, only recommended/safe UV).
For RedPill (sio/conservative) kernel, I tested completely default settings, only changed io sched to sio and governor to conservative.
Just tested RedPill rev1.3 with different io sched / governor combinations (and geko95gek's MagicConfig), and added its results.
Here are my current results:
Benchmarks (in Performance governor if available)
Quadrant Standard (3rd run)
Night use (wifi, synch, Talk and Skype on)
RedPill v1.3 (sio/conservative): Battery loss of 0,72% per hour, Awake: 4,8%, Deep sleep: 93%
Phenomenal 4.0 Extreme: Battery loss of 0,82% per hour, Awake: 5,6%, Deep sleep: 93%
SpeedMod K2-21: Battery loss of 0,86% per hour, Awake: 6,0%, Deep sleep: 93%
RedPill v1.3 (MagicConfig, deadline/sleepy): Battery loss of 0,94% per hour, Awake: 6,5%, Deep sleep: 92%
XWLA4: Battery loss of 0,95% per hour, Awake: 9,2%, Deep sleep: 90%
RedPill v1.3: Battery loss of 1,00% per hour, Awake: 6,3%, Deep sleep: 92%
XILA2: Battery loss of 1,09% per hour, Awake: 6,5%, Deep sleep: 91%
XWKK5: Battery loss of 1,09% per hour, Awake: 11,6%, Deep sleep: 88%
RedPill v1.3 (MagicConfig, noop/conservative): Battery loss of 1,25% per hour, Awake: 8,8%, Deep sleep: 89%
N.E.A.K. v1.3.3: Battery loss of 1,28% per hour, Awake: 9,2%, Deep sleep: 90%
XWKK2: Battery loss of 1,44% per hour, Awake: 9,9%, Deep sleep: 89%
Siyah v2.6.12: Battery loss of 1,52% per hour, Awake: 9,6%, Deep sleep: 89%
Mixed (day and night) usage (*)
RedPill v1.3 (sio/conservative): Battery loss of 1,76% per hour, Wifi: 100%, Awake: 15,8%, Deep sleep: 84%, Screen: 9,7% => loss*(1-screen): 1,59%
SpeedMod K2-21: Battery loss of 1,91% per hour, Wifi: 100%, Awake: 16,7%, Deep sleep: 83%, Screen: 10,2% => loss*(1-screen): 1,72%
RedPill v1.3: Battery loss of 2,02% per hour, Wifi: 100%, Awake: 16,5%, Deep sleep: 83%, Screen: 10,3% => loss*(1-screen): 1,81%
RedPill v1.3 (MagicConfig, noop/conservative): Battery loss of 2,05% per hour, Wifi: 100%, Awake: 18,8%, Deep sleep: 81%, Screen: 10,5% => loss*(1-screen): 1,83%
Phenomenal 4.0 Extreme: Battery loss of 2,05% per hour, Wifi: 100%, Awake: 18,6%, Deep sleep: 81%, Screen: 9,8% => loss*(1-screen): 1,85%
RedPill v1.3 (MagicConfig, deadline/sleepy): Battery loss of 2,15% per hour, Wifi: 100%, Awake: 20,5%, Deep sleep: 79%, Screen: 10,0% => loss*(1-screen): 1,94%
XWLA4: Battery loss of 2,19% per hour, Wifi: 100%, Awake: 19,6%, Deep sleep: 80%, Screen: 10,2% => loss*(1-screen): 1,97%
XILA2: Battery loss of 2,42% per hour, Wifi: 100%, Awake: 18,2%, Deep sleep: 81%, Screen: 9,0% => loss*(1-screen): 2,20%
XWKK2: Battery loss of 2,37% per hour, Wifi: 81,9%, Awake: 17,4%, Deep sleep: 82%, Screen: 5,9% => loss*(1-screen): 2,23%
XWKK5: Battery loss of 2,58% per hour, Wifi: 96,1%, Awake: 19,5%, Deep sleep: 80%, Screen: 9,0% => loss*(1-screen): 2,35%
Siyah v2.6.12: Battery loss of 2,94% per hour, Wifi: 100%, Awake: 23,3%, Deep sleep: 76%, Screen: 10,5% => loss*(1-screen): 2,63%
N.E.A.K. v1.3.3: Battery loss of 3,05% per hour, Wifi: 100%, Awake: 24,3%, Deep sleep: 75%, Screen: 11,4% => loss*(1-screen): 2,70%
(*) In order to get a value, which allows to compare test results with different screen on times for mixed usage battery tests, I tried to „normalized“ the battery loss per hour with the following formula:
loss*(1-screen): battery loss in % (per hours) * (100% - screen on time in %)
So, it would be the battery loss in % (per hour) for the screen off time.
That is how a kernel with the same battery loss per hour will get a better/lower value, if it has more screen on time. (And the other way round.)
RedPill rev1.3 has got best battery savings with sio/conservative on my phone, even without any additional UC/UC, etc.
Subjectively, it feels a little bit laggy/not as smooth as in other combinations (e.g. sio/hyper).
So, my first impression of this kernel was proven: Very stable kernel which is highly configurable to fit every demand - for performance and battery life.
Thanks again pongster for that great kernel.
And thanks to geko95gek for his MagicConfig which gave me enough confidence to test out some UV, io sched and governor changes.
Looking forward to test new versions of that kernel ...
When writing an app with performance in mind, you most likely want to write it native code using the … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?