Database Users

Deep sleep question.

Just one simple question. When phone is in deep sleep, the cpu's running speed is the min frequency I choose from the cpu settings or a default lower one?
I use smart ass 2 with min at 768 and max at 1516 . So in deep sleep my phone is running at 768?
Thanks in advance...
Sent from my Huawei u8800 using XDA Premium App

spirosbond said:
Just one simple question. When phone is in deep sleep, the cpu's running speed is the min frequency I choose from the cpu settings or a default lower one?
I use smart ass 2 with min at 768 and max at 1516 . So in deep sleep my phone is running at 768?
Thanks in advance...
Sent from my Huawei u8800 using XDA Premium App
Click to expand...
Click to collapse
Not 100% sure but freq is minimum as it can be. And if cpu is not used no metter is freq 10000MHZ or 300Mhz it uses almost the same power. But when cpu is in use freq is important to power usage. Freq management is good not because it lowers freq but because it lets use lower freq on things that is not require hi freq. so it saves LITTLE LITTLE BIT of power. In idle mode (deep sleep) no meter what freq is.
But i still don't understand the need of governor. It's good only in cases where you overclock cpu but if don't - i don't see why it should be used.
PS Use app called CPU SPY it shows on what freq your cpu is being used and how much of the time.

Thanks! I use CPU SPY and it says tha about 60% or more is in deep sleep, 15%-25% is at 768 and the rest higher, which seems to be a good thing. But my phone still lasts for about 10-15 hours with normal use.
So i thought that maybe my min 768 frequency drain a lot of battery.
To clear things up a bit I use latest oxigen rom+latest franco kernel+zram+Juwe ram script...

Actually deep-sleep state is a special state supported by your phone MCU. In this state, a lot of functionality (therefore a lot of logical gates) are disabled thus MCU consumes very low power compared to normal functioning states. The thing about a CPU/MCU is when it is running even if there are no work to do no code to process, it has to run some command. While idle it must run NOOP (no-operand / no operation) command or do something equally unnecessary like counting a not required number. But in deep sleep mode, MCU actually stops working except for core functions to keep your phone going on.
Think about it this way, in a normal working state, CPUs most basic functionality is to read a command from memory, execute it and proceed to the next command to continue. Thus, in an operating system or a single purpose embedded software, CPU/MCU has to execute a "do nothing" command when you have no job to give it. But even a "do nothing" command need all of the MCU/CPU resources to be kept readily available. If you're sure that you have absolutely no job for your MCU/CPU to do, what you can do is to tell it to go and sleep fr a while until you wake it up again. In sleep, MCU/CPU can shut down a lot of its support systems like math processing, external memory access, graphics related functions (if any), even IO outputs. Depending on your CPU/MCU, this means until an interrupt occurs or a special sub system wakes it up, most of the sub-systems within your MCU/CPU thus may be millions of transistors will not be working so, your CPU/MCU will not consume as much power.
In layman's terms, deep-sleep state is a special state that shut down most of your MCU in your phone, thus while crippling it by removing its ability to function, making sure that it doesn't consumes much power. So OS (Android) (with the help of some additional hardware) controls when your MCU will sleep and under what circumstances it will wake. So it shuts down the engine -so to speak- when you're not using it for long terms and saving fuel rather than leaving your car on idle.
Hope this helps..

Thanks t_d_z. That is also how I imagined things...
But what is wrong with my battery which today, for example, went 33% down in 5 hours with 68% (from cpu spy) in deep sleep, without wi-fi on.
As i said above, I use latest oxigen rom+latest franco kernel+zram+Juwe ram script+smarass2 governor...
I also calibrated my battery by wiping battery stats, like i read in a post.
I have read in an other forum that if you use smartass (I use smartass2) or ondemand (I think...) governors, the governor is learning your habits and after a week you see the difference. Is that true?
Finally, can you guys who have "good" battery life, post your settings? (By settings I mean: rom, kernel, governor with cpu parameters, how you use the phone and everything else you think is important).
Thanks again...

I get about two days of battery life. I use Oxygen without any modifications. CPU is min. 245 (or something like that with 200, I dunno now) and max. is 800. Wifi is always on when I am home.
Try installing Oxygen-r1 and use it with a full battery, do not change anything and do not install too many apps. There will be apps that just won't stop running (like BBC or CNN app), I do not install those. Then you will see how long your battery lasts. If you just write some messages throughout the day and call somebody for 1-3 hours you should get about 2 days.
Then install your apps and test it again - maybe your apps are the problem.

spirosbond said:
Thanks t_d_z. That is also how I imagined things...
But what is wrong with my battery which today, for example, went 33% down in 5 hours with 68% (from cpu spy) in deep sleep, without wi-fi on.
As i said above, I use latest oxigen rom+latest franco kernel+zram+Juwe ram script+smarass2 governor...
I also calibrated my battery by wiping battery stats, like i read in a post.
I have read in an other forum that if you use smartass (I use smartass2) or ondemand (I think...) governors, the governor is learning your habits and after a week you see the difference. Is that true?
Finally, can you guys who have "good" battery life, post your settings? (By settings I mean: rom, kernel, governor with cpu parameters, how you use the phone and everything else you think is important).
Thanks again...
Click to expand...
Click to collapse
Look not at cpu spy but in battery usage to find out what drains your battery. And i can tell All roms are kinda lame in terms of battery, except CM7. In deep sleep it takes about 7% of battery in 10hours. I tried all roms but non of them was so efficient. But latest franco kernel (which i think even more improves cm7 rom) does not support cm7 right now, so i've attached older version if you would like to test cm7+franco kernel.
With normal usage of 50 sms and 30minutes of calls and sometimes wi-fi to download few apps and 20minutes on easy games my battery lats about 18hours. Whan only sms it lasts 30hours. depends how long lcd is on

Well, I'm not an expert on smart phone OSes but I'm an expert on embedded systems and micro controllers. If the designers are not really stupid (which I'm sure they are not) all the peripherals gets suspended when the main CPU goes to deep sleep mode. So, it is almost impossible for the phone to consume much power in deep sleep state. Most likely your phone consumes that power the rest of the time when it is not in sleep mode. I agree with Tommixoft, you should use battery usage info rather than CPU spy to find what drains your battery. Also, here is a quick check list about what consumes power :
1. Screen, especially when it is brightly lit
2. GSM network (Even when you're not talking to phone, GPRS/Edge/3G network communications drains almost as much power)
3. Wireless network
4. GPS
As an additional note, if your phone is not going to sleep mode regularly try to uninstall applications that have "prevent phone from sleeping" security setting.
Hope this helps, and of course there are a lot of more experienced people in the forum that knows about the details of the kernel so they might provide additional info.
Regards,
---------- Post added at 05:15 PM ---------- Previous post was at 05:10 PM ----------
Oh I forgot to tell the MOST important thing, 768MHz is way too high a value to set as minimal frequency. Try to set it 245. I use 122 MHz and it work pretty well. Don't forget, when you need the CPU power, the governor will provide it for you.

[GUIDE] SGS2+Android can be power efficient - One successful configuration

1. Abstract
2. Approach
3. Baseline configuration and results
4. References
5. Disclaimer
1. Abstract
Initially I was quite dissapointed with the battery life of the Samsung Galaxy S II i9100 with Android 2.3.4 out of the box. Coming from the Symbian world Nokia E71 I have been used to 6-7 days without recharging, while on SGS2 I got barely 1.5 days of normal usage. I started to optimize, and felt that the hardware is very capable for power saving, but the software is not optimized. After turning off all synchronization, going thru every program settings to switch to manual sync, switching to 2G network (EDGE in my area), turning off WiFi/Data/GPS/Background data I've got a busy day full of meetings at work (didn't touch the phone apart from 2 incoming calls and a few notes) and only 10% decrease of battery for 24h (100%->90%) which is amazing by itself. But I wanted to optimize more.
I have heard that other things like Custom ROM, freezing of system applications, task killers, Under Volting (UV), Under Clocking (UV) would help me too, but I was about to discover which one really helps in real use.
One lazy Sunday like today while being a bit sick allowed me to conclude an experiment of how far did I get in optimizing the power usage for a "baseline configuration" - WiFi/Data/GPS/Background data off, 2G network, all possible sync to manual - and the results are astonishing.
2. Approach
The approach to optimize the battery life is only one - PUT IT TO SLEEP AND DON'T LET IT AWAKE.
Having read a ton of articles on xda-developers.com and other places I have concluded that the strategy for optimizing includes these major steps:
2.1. Get a clean baseline Custom ROM where much of the "bloatware" is removed, so you have less to optimize - optional step but it helps to do it
This probably helps although not necessary. I'm not sure if the stock ROM will allow you to put custom kernels which will be needed in the next steps to optimize further.
But in any case you need to be at least "rooted" to apply some of the advice - either via a rooted kernel like CF-Root [8], or via an exploit like the DooMLoRD'a zergRush exploit [7].
2.2. Optimize the screen-on time
This is up to how frequently you use the phone
What you can optimize is to set a default "conservative" CPU Governor profile from 200MHZ to 1200MHz for regular usage - nothing really special, it's only slower on jumping to high frequencies.
If you have a kernel like RedPill Kernel [9] you can add an additional In-Call profile with "conservative" CPU Governor from 100MHZ to 800MHz - while you talk and phone to the ear it idles at 100MHz, but if you start a let's say Notes taking application, or go to turn on Bluetooth it will be snappy enough. Same holds true for listening to music or listening to books - but it's up to your imagination how to set a 100MHz profile in this case (maybe via Tasker). Have in mind that the 100MHz setting may be unstable on some phones because it's not standard, but mine is absolutely fine with that setting.
For setting the CPU profiles software like Voltage Control [5] (paid version for many profiles) is used.
CPU Governor "conservative" is crucial so you don't instantly jump to the highest frequency as it happens with the default "ondemand" governor (or its clones).
You can choose an I/O Scheduler appropriate for your CPU Governor based on the MagicConfig article in my references [14].
People also say that the following helps and I use it: turn off button LED lights, darker wallpapers, auto-rotation disabled, auto brightness on (I have to see the screen after all).
If you use kernel like RedPill Kernel [9] the button LED lights are undervolted by default, so you can leave them "on for 1.5s" for example.
If you have a Custom ROM like CheckROM Revolution HD V6 [10] with JKay Deluxe Settings you can set a Dark or Darker auto brightness profile - also usable to some extent.
One article in my references [12] also gives the power drain in milliwatts (mW) for each hardware device - go read it and you will understand how much the Amoled Display (Average - 370mW), LED lamp next to camera (1.3W), Camera (700mW), Bluetooth and GPS (110 to 180mW) etc. hardware actually consumes.
2.3. Optimize the screen-off time
2.3.1. Analyze Wakelocks
Wakelocks indicate when some application prevents the phone from going to sleep for some time. It does not necessarily mean that it does something significant at that time, and may be only a bad application design. Some applications really like to hold wakelocks periodically during the day for no reason, even if set to Manual sync etc. Examples of such applications are Facebook, 3G Watchdog... You milleage may vary but you can be sure that this hurts your battery life a lot. Any such application can be frozen with Titanium Backup or uninstalled if it's not a system application. Both count and total duration of the wakelocks are important.
BetterBatteryStats [1] has a screen to debug Partial Wakelocks and Kernel Wakelocks. You can also obtain the raw information via the console command "cat /proc/wakelocks".
2.3.2. Analyze Alarms
Alarms are a way to start jobs in the system at a predefined time. Many applications set alarms to get awaken and check/poll something before sleeping again. You should note that firing an Alarm is not necessarily connected to having a Wakelock - you can see many alarms firing but very few wakelocks. The problem is that too many applications set too many alarms for no reason. These activities also hurt your battery life a lot. Examples of such applications are Google Maps (at least for me)... As long as I have another GPS application with offline maps, I've simply frozen Maps with Titanium Backup. Another example was let's say Social Hub, but as long it was firing once per 24h, I didn't bother to touch it.
BetterBatteryStats [1] has a screen to debug Alarms which requires Root access. You can also obtain the raw information via the console command "dumpsys alarm".
2.3.3. Analyze Network Connections
If you get lost in the Wakelocks and Alarms, you can help yourself by checking what connections are kept alive while Internet is connected. OS Monitor [3] has a Connections screen which is equivalent to "netstat". This is also a good indicator what may be drawing unnecessary battery and respectively freeze/uninstall. In my case I can point that I've discovered that K-9 Mail had a bug with IMAP accounts - if I connect to an IMAP account set to manual/poll sync once, it keeps a connection open forever, until you restart or kill the process, but for POP3 account there is no problem... Being aware of such things really help with the battery life.
2.4. Optimize deep idle and sleep time
This is the most important goal in this article - how to get into deep idle/sleep and stay there, because this is the only real way to save energy on such a powerful device
CPU Spy [2] can show you how much time you spend in deep idle/sleep - with my baseline testing I've managed to get 99% deep idle/sleep which is amazing - only if the manufacturers gave us the phones in this state and we can build on that...! But it's the other way round.
Unfortunately the sleep mode on the stock kernel and the CF-Root kernel is not too deep. Entropy512 in my references [15] describes the following modes of idle/sleep:
IDLE - clock is gated but power remains (does not eliminate any static power consumption)
AFTR - clock is gated, CPU core power removed, cache power remains - this eliminates a great deal of static power consumption - cannot be entered if second core is active
LPA - AFTR + removal of cache power - cannot be entered if second core is active
IDLE is entered if the CPU is expected to be free for 4 msec (40 msec stock)
AFTR is entered if the CPU is expected to be free for 10 msec (disabled stock)
LPA is entered if the CPU is expected to be free for 40 msec (40 msec stock)
This compares to suspend, aka deep sleep, which takes around 150 msec to enter and 650 msec to resume, and the CPU must be at 800 MHz (or at least have enough voltage to support 800 MHz operation) during this time. Entering suspend/resume is very costly in terms of power due to heavy interrupt load.
Unfortunately my knowledge ends here, but flashing a kernel like RedPill [9] with Power Saving features and patches enabled improved the deepness of the idle/sleep very significantly, let's say 2 fold compared to the stock kernel. Sleep is entered faster and with more savings.
2.5. Optimize the modem/baseband
If all the points above are done, you can consider some savings from trying to flash newer modem/baseband compatible with your Custom ROM for better power savings during Calls and Data transmission. I did not get deep into this yet, but it's rather a big Voodoo, because the contents of the various modems are not public and you can only read feedback like "works very good for me" and "totally awful", which is not very scientific. Initially you can try staying with your original modem or the one provided by the Custom ROM, and optimize the previous points.
2.6. Optimize other stuff
2.6.1. Under Volting - will probably help, but for every frequency you need to choose voltages that are not too low to keep the phone stable. You can try the UV profile from the MagicConfig article from my references [14].
2.6.2. Under Clocking - I consider trying to use 100MHz useful for some scenarios, but only as an additional profile. After all the phone is very powerful and snappy to cripple it with 100MHz-1000MHz profile as default.
2.6.3. Automatic Task Killers - absolutely worthless peaces of software [16]. Android OS is good at power saving. It is very power saving conscious actually, of course combined with capable to sleep hardware. The only reason to kill a process is if it locked on holding some resource/connection forever, and OS Monitor [3] can kill it.
2.6.4. Battery charging - charge the battery as frequently as you want, but be sure to not keep it constantly on high charge (90-100%) [18], as long as this is not a good state for storage. Making bigger cycles helps to maintain better battery life. Some sources say cycling from 0% to 100% is not optimal [17], but from my experience through the years this way also works good for battery longevity, and maintaining small loss of capacity. I can give an example of losing up to 10% of battery capacity per year compared to design capacity with this method. You can view such statistics in Power Management tools in Lenovo ThinkPads etc.
Note that the battery indicator has some tweaks around 100% so consider the following:
- When charging for me it hops from 98% straight to 100%. If you disconnect now, it drops to 98% again, and this is what other people complain from too. Just wait some more time and it will charge to real 100% to have more battery life.
- The indicator stays at 100% longer than at any other value. So when testing, always test from the same baseline, e.g. always charge to 100% before comparing results.
3. Baseline configuration and results
CheckROM Revolution HD V6 PDA XWLA4 (Android 2.3.6) + modem XXKI4 (was XWKL1 but changed for no reason) + kernel RedPill 1.3.
WiFi/Data/GPS/Background data/Auto-rotation/Button LED lights - OFF
Any type of Sync or Polling - OFF/MANUAL, using local Contacts and local Calendar
Widgets - AccuWeather.com on MANUAL and Today view from Calendar.
Network: 2G (EDGE in my area)
Background and lock screen: Dark wallpapers
CPU default profile: conservative 200MHz-1200MHz
CPU in-call profile: conservative 100MHz-800Mhz
Because I don't want to wait a full day for the statistics, I'll post now for 8 and 12 hours, and tomorrow add for 24 hours.
(See the attached images, because I'm not sure how to embed them in the text)
4. References
[1] BetterBatteryStats XDA Edition - http://forum.xda-developers.com/showthread.php?t=1179809
[2] CPU Spy - https://market.android.com/details?id=com.bvalosek.cpuspy
[3] OS Monitor - https://market.android.com/details?id=com.eolwral.osmonitor
[4] Titanium Backup (paid version) - http://matrixrewriter.com/android/
[5] Voltage Control - https://market.android.com/details?id=com.darekxan.voltagecontrol
[6] Android Terminal Emulator by Jack Palevich - https://market.android.com/details?id=jackpal.androidterm
[7] DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit) - http://forum.xda-developers.com/showthread.php?t=1321582
[8] CF-Root Kernel - http://forum.xda-developers.com/showthread.php?t=788108
[9] RedPillKernel_Rev1.3 - http://forum.xda-developers.com/showthread.php?t=1288850
[10] CheckROM Revolution HD V6 - http://forum.xda-developers.com/showthread.php?t=1312240, http://checkrom.com/
[11] Premium Dark Wallpapers - http://forum.xda-developers.com/showthread.php?t=1474798
[12] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks - http://forum.xda-developers.com/showthread.php?t=1369817
[13] Getting the Most out of the Battery on your Android device - http://softbanksucks.blogspot.com/2011/10/getting-most-out-of-your-battery-on.html
[14] MagicConfig for UV and CPU Governor + I/O Scheduler combinations - http://forum.xda-developers.com/showthread.php?t=1466017
[15] Entropy512 explained CPU idle states - http://forum.xda-developers.com/showpost.php?p=23252902&postcount=17
[16] Android Task Killers Explained - http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
[17] Li-Ion Battery Charge Cycles, Voltages and Storage analysis - http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
[18] IBM/Lenovo recommendations on Li-Ion battery treatment - http://forum.xda-developers.com/showpost.php?p=23258191&postcount=19
5. Disclaimer
Paid apps are mentioned here for clarity. You can of course find an alternative if such exists. Free (no ads) versions of software were listed where possible.
Needless to say that all advice here must be applied only under your own responsibility.

Results at 25h usage: The battery indicator has dropped down to 94%.
However it's a bit hard to predict how much is it going to last this way as long as after initially staying at the value "100%" the indicator decreases a bit faster.
See attached screenshots.

Thanks for the detailed post but i still don't understand why people insist on having a smart phone and then turning off any good feature in it to get 2 days of work out of it.

Agent_Adodas said:
Thanks for the detailed post but i still don't understand why people insist on having a smart phone and then turning off any good feature in it to get 2 days of work out of it.
Click to expand...
Click to collapse
That depends if you dont want xxxx app running every day why run it and why let it connect on a daily basis . Its a Smartphone not a dumbphone that controls the user .Nothing in the Smartphone design says hey guy you are really uncool if you don't have everything turned on .
I turn on what i want when i want but then again i am not sad enough to live my life on facebook .
jje

there's nothing wrong with killing background tasks that eats your battery, but to me it looks funny to turn off WIFI, 3G, Sync or polling.
anyway, that's what i think, other people may think different and will prefer to save on battery life.

Agent_Adodas said:
there's nothing wrong with killing background tasks that eats your battery
Click to expand...
Click to collapse
:facepalm:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Unless you love using terribly coded apps.

This is a Baseline - my initial starting position. Yeah I don't feel cool for running tons of unneeded stuff Actually after 15 hours of uptime I feel pretty bad and a slave of the charger.
I hope to tell more people in a single post what can be optimized, stripping off any superstition, voodoo and some pointless beliefs circulating in the web
I don't say "do like me", but instead what a great hardware SGS2 + core Android software actually seems to be
Please also note I didn't limit myself to 1000MHz, do not recommend reducing voltages etc... the struggle is to put the software in control, not to cripple the experience.
Additionally, I have WiFi at work, at home, at the gym, and between them I'm driving... for that reason I don't need unlimited data. And for new mails I actually get SMS and know when to fetch the mail. If it's important I can turn on the data as well. On business trips abroad there is no unlimited data anyway too - only WiFi at the office and at the hotel. So there are different scenarios...

Serious Observations Bro!
Must say, very clear,simple and awesome way to put together things...will try this out and post again!
Thanks a ton bro! Love the efforts and for helping us out!

Great tips mate... I knew many of them before but i will not use them so much.. I have a feeling that it criples my phone... Limiting my usage of the phone... Instead i have a custom rom,custom kernel ,an extra standard battery,car charger...
I even tryed once to apply most of your tips but they gave me a couple of hours extra batt life. My problem is network signal coverage-edge is fine(but who can surf on egde ?!? ) ,3g and hspda signal is not so good (i travel a lot by car all over my country) and the phone keeps trying to get better network signal and uses more battery...
So most of your tips work if u want to criple your phone and if ur network has great coverage...
Sent from my GT-I9100 using XDA

Using a slow scaling cpu governor defeats the purpose of battery savings. You want something that will scale up fast and scale down just as fast. That way the task gets completed quicker and the cpu can go back to an idle state faster.
Slower governors take longer to complete a task and that uses more battery.
I rather OnDemand complete something in 2 seconds jumping immediately to 1.2Ghz than Conservative in 4 seconds scaling it's way up each step and then scaling back down slowly.
Sent from my GT-I9100 using Tapatalk

Elisha said:
Using a slow scaling cpu governor defeats the purpose of battery savings. You want something that will scale up fast and scale down just as fast. That way the task gets completed quicker and the cpu can go back to an idle state faster.
Slower governors take longer to complete a task and that uses more battery.
I rather OnDemand complete something in 2 seconds jumping immediately to 1.2Ghz than Conservative in 4 seconds scaling it's way up each step and then scaling back down slowly.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Not true if I'm typing notes. Ondemand will struggle to take me on high frequency, while I'm browsing the texts... Do you need high frequency when reading forums?
Actually I have no problem to play Asphalt 6 and Angry Birds on 1200MHz with this setup

It takes you more cpu cycles to get Asphalt or Angry Birds fully loaded with Conservative than it would with OnDemand.
And you have to remember we have dual-core cpus. It's to your benefit to get both cores scaled up faster to finish the task.
You don't notice this as much because the difference is probably in the milliseconds. But Conservative is more of a power hog than OnDemand.
Sent from my GT-I9100 using Tapatalk

Wow, thats massive and informative! Too good job Sir! Hats Off!

Elisha said:
It takes you more cpu cycles to get Asphalt or Angry Birds fully loaded with Conservative than it would with OnDemand.
And you have to remember we have dual-core cpus. It's to your benefit to get both cores scaled up faster to finish the task.
You don't notice this as much because the difference is probably in the milliseconds. But Conservative is more of a power hog than OnDemand.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Agree. All that advice is mostly targeted to battery conscious people, this is not a gaming setup There is no one best configuration for all.
It's also not about what exact values to choose, but what approach to take for battery life improvement.

Can't wait to run a UV kernel once the sources drop. That there helps quite a bit to conserve battery.
Sent from my GT-I9100 using Tapatalk

I know pretty much all of this already but it's a useful guide for noobs for sure.
I don't bother anymore with SetCPU or any of that anymore and to be honest it's had little or no impact on battery life which is still excellent.

gingingingin said:
0: IDLE - CPU not clocked
1: AFTR - something not totally clear to me, but an alternative way to IDLE the CPU - ARM Off Top Running with L2 cache keeping its state
2: IDLE+LPA - IDLE + DEEP IDLE - also some parts of hardware are powered down
3: AFTR+LPA - AFTR + DEEP IDLE
Click to expand...
Click to collapse
These are not deep sleep states. Deep sleep is also known as "suspend" - where almost the entire system is shut down.
These are CPU idle states, which allow the core to save power even when the system is "running". They take significantly less time and energy to enter, but save less power. Also, there are only three of them - IDLE, LPA, AFTR. See arch/arm/mach-s5pv310/cpuidle.c in the kernel source for more details.
As an example, with kernels that have the cpuidle backport from the Tab 7 Plus:
IDLE is entered if the CPU is expected to be free for 4 msec (40 msec stock)
AFTR is entered if the CPU is expected to be free for 10 msec (disabled stock)
LPA is entered if the CPU is expected to be free for 40 msec (40 msec stock)
There are some rules that can cause lower states to be entered even if the cpuidle governor chooses LPA or AFTR. (cpuidle governor has nothing to do with cpufreq governor).
Your descriptions of the states are pretty close to what I understand them to be:
IDLE - clock is gated but power remains (does not eliminate any static power consumption)
AFTR - clock is gated, CPU core power removed, cache power remains - this eliminates a great deal of static power consumption - cannot be entered if second core is active
LPA - AFTR + removal of cache power - cannot be entered if second core is active
The above are why 100 MHz is pointless on our device, and in my experience, actually can increase power usage. The achievable voltage difference between 100 MHz and 200 MHz is insignificant for most peope, and if the voltages for two frequencies are the same, it's better to run at the higher frequency and drop into AFTR/LPA to shut off core power more often. The PDF linked from Ezekeel's post at http://forum.xda-developers.com/showthread.php?p=21785924#post21785924 is a useful read on this topic, especially section 6. While it's fairly old, most of the concepts remain valid. For this reason, 500 MHz also doesn't consume much more power than 200 for a given fixed amount of load due to having the same voltage stock as 200 (however, it does increase some internal clocks I believe, leading to slightly increased power) - so when the screen is on I have it set to 500 MHz minimum.
This compares to suspend, aka deep sleep, which takes around 150 msec to enter and 650 msec to resume, and the CPU must be at 800 MHz (or at least have enough voltage to support 800 MHz operation) during this time. Entering suspend/resume is very costly in terms of power due to heavy interrupt load, which is involved in 90% of complaints about high "Android OS" battery usage on Gingerbread. However I believe from some of the testing I've run that improved cpuidle greatly reduces this penalty.
With the improved cpuidle patch, even when I use the Wake Lock app to hold a permanent wakelock for testing purposes, my standby drain is only 1.5%/hour or so. When not holding a wakelock, 0.5%/hour on wifi is easily achievable. It gets much worse at my desk at work, where the signal is weak and the cell radio eats huge amounts of power - there it's around 1%/hour.
Edit: As to task killers - all of the people saying "task killers are worthless" talk about memory management only. The fact is, unfortunately, that there are some crappy apps out there that use too much CPU or hold insanely long wakelocks that you just have to use occasionally. Facebook is still the #1 example here - Facebook is a major battery hog, therefore when you're done with it, you must kill it with fire. However, NEVER use an autokiller and never use it for memory management!

Regarding battery charging, I wonder have you read this article before : batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries (please add http)
The fact seems to be completely opposite from your theory in 2.6.4.
Sent from my GT-I9100 using xda premium

Not sure, the battery article is a bit doubtful. For me at least the testing sequence is strange:
1. Charging current of 1C is a bit high, to say the least. Quick chargers have never been optimal for any type of batteries.
2. Discharge current of 1C is huge and far from being realistic for a mobile phone.
Also if we interpret the results it becomes that at 10% DoD we get 4700 small cycles, which is close to 100% DoD with 500 big cycles... Actually the results are in favor of the 100% DoD.
Of course my interpretation can be wrong, but so far I have got the opposite idea of that.
For practical purposes I can give an example of a Nokia Li-Ion battery thoroughly fully discharged and for 2 years it retained at least 80% capacity. I'd estimate the number of cycles to be 120-150.
On my current laptop the ThinkPad Panasonic battery was always almost completely discharged via settings, attaching screenshots. At 328 cycles and 3.5 years since first use it retains 88% of the design capacity. This is quite a good achievement for a tortured battery I'd say
Note: See the advice/sentence written in the top box by my good old IBM manufacturer (now Lenovo). "... battery deterioration may occur faster if the battery is constantly charged at 100%. Lowering the charge thresholds ... will help increase its lifespan". These guys know their job... I think their sentence almost surely relates to storage though. Storage at 50% is much better than storage at 100% charge. There is room for interpretation again.
Note: This is my second battery on this laptop, the first one Sanyo was a bit worse with the same treatment (maybe older technology) and after 2 years its electronics suddenly failed, while at around 150 cycles.

Entropy512 said:
The above are why 100 MHz is pointless on our device, and in my experience, actually can increase power usage. The achievable voltage difference between 100 MHz and 200 MHz is insignificant for most peope, and if the voltages for two frequencies are the same, it's better to run at the higher frequency and drop into AFTR/LPA to shut off core power more often.
Click to expand...
Click to collapse
First of all, thanks for the detailed explanation of the states.
I remember from the school/uni that the power used is proportional to the frequency. If we have static consumption in the chip it will not be affected by changing the frequency, but the dynamic part of the consumption is essentially doubled when running on 200MHz compared to 100MHz. I don't know the ratio dynamic_consumption:static_consumption for my chip, but it may be around 1:1.
The formulas were something like that: http://forums.anandtech.com/showthread.php?t=119229

[Q] How can i save my battery at M4?

Things that i did for my battery
lower brightness
sync off
gps off
about voltages,
lagfree / sio
min 100 / max 800
no live oc & deep idle on
yet, still i lost approximately 8~10% / hour
i really dont what's my problem

Maybe you have a wakelock?

I set a cpu profile for screen off at 400mhz, 1075mV. Matrix kernel seems to be the best for battery life, as well....you may wish to try it out I run overclocked @1200mhz with my screen off profile, and it gets me through an entire day with normal use...when I plug it in at night I usually have 10-15% battery left

[KERNEL TESTS] [ICS] [AOKP/AOSP/cm9] [SIYAH|NEAK|THORAVUKK|NETCHIP|FLUXI|ABYSS]

ICS KERNEL TESTS - AOKP/AOSP/CM9
Netchip | Siyah | N.E.A.K | Thoravukk | Abyss | Fluxi​
This thread is only intended for reference purposes to those using AOSP/AOKP/CM9 ROMS
Purpose
I conducted these tests in order to help all users of AOSP/AOKP/CM9 ROMS to have a reference base when flashing a custom kernel. In no way am I supporting you to do so and I will not be held accountable of any wrong doing resulting from your part. I know it's sounds harsh, but do not jump out there flashing kernels if you do not have the minimal knowledge about how things work. I will be posting up a few links to other informative threads in order to help everyone (a.k.a noobs) These tests are done through my own will and I spend quiet a lot of time writing these results in a presentable manner so everyone could benefit from this. If you do not like the way I do my tests or would like to share some improvements, please do so in a respectable manner. If you cannot follow this simple rule, I strongly advice you not to use this thread as a reference and I suggest you do your own test which would satisfy and meet your requirements.
How to flash a kernel?
There are different ways of flashing a kernel, but the one I use is through CWM, because I do not trust ODIN, simple as that.
Step 1: Download Kernel Cleaning Script if your coming from a different kernel and flash it before flashing the new kernel. If it's just an upgrade of the same kernel, wipe cache and dalvik before flashing.
*Using a Cleaning Script is not mandatory to flash a new kernel, it is just recommended to use it to make sure modules and such are cleaned for a fresh installation
Step 2: Flash desired kernel.
Step 3: Wipe Cache and Dalvik once kernel is done flashing.
Step 4: Reboot System.
*Hint: If you're having fc right after boot, reboot into recovery mode and try fixing permissions. It happened to me once, and after fixing permissions everything went back to normal.
How to flash back to stock kernel?
Step 1: Extract "boot.img" from ROM zip file
Step 2: Rename "boot.img" to "zImage"
Step 3: Place zImage in Internal Storage
Step 4: Use CWM app and flash "zImage" as kernel
If you're unsure of this method and do not want to try it because you're scared of doing something wrong, I'll post a flashable one for you upon request.
Kernel Cleaning Script
**Use these scripts at your own discretion**
GS2WiperV1.6
Does the following: (Bold are changes since V1.5)
1. Wipes cache+dalvik cache
2. Saves all current startup scripts to /sdcard/init.d_backup
3. Removes Voltage Control and NSTools startup scripts (only if saved as init.d, and not as a service) along with specific Siayh startup scripts from /system/etc/init.d
4. Removes old kernel-specific files (currently Void, Andoidmeda, Siyah and NEAK are cleared)
5. No longer removes modules (/system/lib/modules) as this can affect certain ROMs
6. Removes old CPU settings from /sys/devices/system/cpu
7. Removes /data/user.log
8. Re-wipes cache+dalvik cache
Samsung Ultimate Kernel Cleaning Script ICS 2.6.4
Does the following:
Formatting cache partition
Wiping Dalvik-Cache
Deleting old kernel settings files ** [only GT-i9000]
Cleaning up old Modules
Formatting cache for Security Purpose
Wiping Dalvik-Cache for Security Purpose
Cleans after Kernels:
Thoravukk KERNEL
Abyss KERNEL
CF-Root
FLUXI Kernel
N.E.A.K. Kernel
Ninphetamine
Phenomenal
RedPillKernel
SiyahKernel
SpeedMod
Void.echo
Credits to:
Hawker - My GS2 Kernel Cleaning Scripts (WIper V1.6)
buster041284 - Samsung Ultimate Kernel Cleaning Script ICS
You guys made it easy for us! Thanks for your hard work guys!
________________________________________
You don't play too many games?
You use your phone mainly for texting, calling, browsing, twitter, facebook, XDA and other small stuff?
You want to save battery?
Then here's some good battery optimized settings.
Lulzactive Settings - Battery Optimized
Governor/Scheduler: Lulzactive/VR
Lulzactive Tweaks:
inc_cpu_load: 90%
pump_up_step: 2
pump_down_step: 2
screen_off_min_step: 500MHz
up_sample_time: 28000
down_sample_time: 40000
debug_mode: 0
Voltage Tweaks:
200Mhz - 825 mV
500Mhz - 950 mV
800Mhz - 975 mV
1000Mhz - 1050 mV
1200Mhz - 1150 mV
GPU Tweaks
2 Step:
133 - 850 mV
267 - 950 mV
3 Steps
100 - 850 mV
160 - 900 mV
267 - 950 mV
Want to save even more battery:
200MHz-1000MHz
or
200MHz-800MHz
________________________________________
Currently Testing:
On Hold
Testing Soon:
Vanilla RootBox JB + Stock
Vanilla RootBox JB + Siyah
Completed Tests:
- HyDrOG3N 14.04 + N.E.A.K 2.0.2x (Completed - April 17)
- HyDrOG3N 14.04 + Thoravukk 2.28 (Completed - April 18)
- HyDrOG3N 18.04 + Siyah v3.1 rc6 (Completed - April 20)
- HyDrOG3N 18.04 + Netchip Stock Kernel (Completed - April 21)
- HyDrOG3N 18.04 + Siyah v3.1.2 (Completed - April 25)
- HyDrOG3N 27.04 + N.E.A.K 2.0.3x (Completed - May 1st)
- HyDrOG3N 27.04 + Thoravukk 2.50 (Completed May 2nd)
- HyDrOG3N 05.05 + Abyss 1.6b (Completed May 7)
- HyDrOG3N 05.05 + Fluxi XX.01 RC3 (Completed May 8)
- HyDrOG3N 12.05 + Netchip (Stock) (Completed May 14)
- HyDrOG3N 12.05 + Fluxi XX.01 RC4 (Completed - May 16)
- HyDrOG3N 12.05 + Abyss v2.0 (Completed - May 18)
Bajee Scale(ºB): (Will be implemented Soon)
0-50 = Stay away from this!
51-70 = Could be better, keep looking.
71-80 = Not bad, I like it.
81-90 = Damn, I'm impressed.
91-100= Why isn't everyone using this!
Thanks to Definitus for the scale idea.
Press Thanks If this thread was useful.​
If your downloading the xxTweaker app that I translated, I'm not asking for any donations, just press thanks to show your appreciation.

Test Results - HyDrOG3N + Siyah + Fluxi
HyDrOG3NICS + Siyah + Fluxi
​
Test Results - HyDrOG3N 12.05 + Fluxi XX.01 RC4
Rating: 95 ºB
Fluxi ICS Kernel
Original Thread
XDA Thread
Governor/Scheduler Used: On Demand/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday May [email protected]~10PM
Woke up: Tuesday May 15 @ 8AM (WiFi + Data was on throughout the night)
Usage: Regular usage + Twitter +Tapatalk + Games + Instagram
Phone died: Wednesday May 16 @ 2:21AM
Screen On Time: 6h 13min (6h15min when phone died)
Type of usage:
- WiFi ON (Disconnected once when I went out)
- Data ON (Always ON)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (250+ texts)
- ~ 30 minutes talk time
- Google + (~5 mins)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)*
- Instagram (Used 5-6 times)
- Osmos HD (5 mins)
- Angry Birds Space (10 mins)
- Youtube (1 Movie Trailer)
As expected, this kernel came up to the highest expectations I had. Implementation of Touch Presets is probably one of the best thing Fluxi did for this release. Bringing in new BLN/LED functions was really nice to see, but it's too bad I don't use BLN (due to wakelock) and LED fadeout is really nice but I didn't use it for this test. So for the bad things now, I had one (1) reboot.. Unfortunately true but to recomfort you guys: It was only a soft reboot. So for that reason, I couldn't post CPU SPY and BBS screenshots as they get reset after any boot. Once again, I will highly suggest this kernel to all users. I realized that after posting results for HyDrOG3N 05.05 + Fluxi XX.01 RC3, lot of users jumped in and started using Fluxi. The translated app might of helped too, who knows. But I'm glad everyone knows that Fluxi exists out there and is doing really well with battery and performance. So I'll take this time to thank Fluxi for this amazing kernel, Paradoxxx because he got swagg beyond my understanding with amazing HyDrOG3NICS releases, xator91 for opening a thread for this kernel on XDA, KS_Ho for testing out my translated xxTweaker app and finally all the subscribers of this thread.
How to install translated xxTweaker for RC4
1) Unzip file and transfer net.fluxi.xxTweaker-1-0.3.2_signed.apk to internal storage
2) Uninstall the original xxTweaker
3) Install net.fluxi.xxTweaker-1-0.3.2_signed.apk from internal storage
4) You should now have xxTweaker in English
5) Create empty file: /data/.notweaker (Should stop autoupdate)
xxTweaker Settings:
General
Idle Mode: AFTR + LPA
SCHED_MC: Disabled
Screen
Brightness/Gamma: -5
Touch Presets: xxKernel Gingerbread
BLN
No BLN (But I gotta say, Breathing effect is really amazing)
Led time out: 1 second (No Fadeout effect)
CPU
Max Suspend: 400
Min Suspend: 200
Hotplug settings: 75%UP/30%DOWN/Dynamic Hotplug
Bus Frequency: Voltage table(1050, 950, 950)
GPU
100(850) 160(900) 267(950)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time
{
"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"
}
Test Results - HyDrOG3N 05.05 + Fluxi XX.01 RC3
Rating: 95 ºB
Fluxi ICS Kernel - Original Thread Link
Governor/Scheduler Used: OnDemand/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday May [email protected]~10PM
Woke up: Tuesday May 8 @ 8AM (WiFi + Data was on throughout the night)
Usage: Regular usage + Twitter +Tapatalk + Games
Phone died: Tuesday May 8 @ 10:05PM
Screen On Time: 6h 12min (6h14min when phone died)
Type of usage:
- WiFi ON (Disconnected twice when I went out)
- Data ON (If I receive MMS and Data is OFF, it drains battery by attempting to download MMS. So from now on, Data will be on for all my tests)
- AutoSync ON (Google Services, Twitter)*
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (250+ texts)
- ~ 45 minutes talk time
- Google + (~15 mins of usage)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)*
- Instagram (Opened a few times)
- Draw Free
- Osmos HD
- Angry Birds Space
- Youtube (3 movie trailers)
Wow, seriously, this kernel just blew me away with its performance and battery. It's been a while since I've seen a kernel with this much of customization with it's own app. Unfortunately, this is a kernel made in Germany, so the app that comes with the kernel for customization was in German only. So I took the liberty of decompiling the apk, translating the string.xml, recompiling it and finally testing it on my phone. I omitted to translate one or two words, but the translated app works like a charm! You could download it from the first Post of this thread. Just make sure you hit Thanks when downloading. By the way, this kernel does not have lulzactive governor, so I used OnDemand for the test. For all those following all my tests, I think this might be my favorite kernel for now. I highly suggest for everyone to try this.
How to install translated xxTweaker
1)Unzip file and transfer xxtweaker_signed.apk to internal storage
2)Uninstall the original xxTweaker
3)Install xxtweaker_signed.apk from internal storage
4)You should now have xxTweaker in English
xxTweaker Settings:
General
Idle Mode: AFTR + LPA
SCHED_MC: Disabled
Screen
Brightness/Gamma: -5
BLN
No BLN
Led time out: 1 second
CPU
Max Suspend: 400
Min Suspend: 200
Hotplug settings: 75%UP/30%DOWN/Dynamic Hotplug
Bus Frequency: Voltage table(1050, 950, 950)
GPU
100(850) 160(900) 267(950)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU spy, BBS
Test Results - HyDrOG3N 18.04 + Siyah v3.1.2
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1200MHz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 24 @~6:30 PM
Woke up: Friday April 25 @ 8 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (200 texts +)
- ~ 50 minutes talk time
- Google + (~10 mins of usage)
- Tapatalk (All day)
- Browsing (Once or twice for a few mins)
- Camera (3 Photos + 1 Video)
- Osmos HD ~20 mins
- Angry Birds Space ~10 mins
- Youtube (2 videos ~3 mins/each)
- Netflix (TV show: Lie To Me 45 mins)
Phone died: Friday April 25 @ 17:10 PM
Screen On Time: 4h 11 min (4h 20 min when phone died)
Hey guys, I've been a little busy these days, but here I am with new results. Yup much lower than the one before but I have a pretty reasonable explanation. First of all, last Siyah's test with rc6, I only had 17hours of run time and this time I had 23 hours. That's because I didn't have the opportunity to use my phone much today (except for texting and tapatalk) since I was busy with some things of my own. During my study break, I played a little bit of Osmos HD, which is a game I bought on Play Store while it was on special for 0.49$ and I gotta say, it's pretty addictive at times (Specially when you're tired of studying) But I did end up using the phone a lot more at the very end when I was really bored and started watching a show on Netflix(which drastically killed the battery). Once I was done watching the show, I received a phone call from a friend and talked for almost an hour which also decreased the battery by a few %. Overall, I am very satisfied by the amount of time this phone actually stayed on after all these usage. I don't think this time the screen time actually mattered due to the fact that it was balanced out with 23 hours of run time. Unfortunately I couldn't post up CPU Spy or BBS, because this morning I had a random fc with my camera app and the phone had to be rebooted, so CPU Spy and BBS stats were reset.. Very strange but it only occurred once. I changed two things during this test: I noticed my lulzactive settings were giving me a little bit of lag at times. It wasn't big at all, just small lag, but I didn't like that, So i switched to these lulzactive settings and it got much better. (Values changed are in red)
Lulzactive app by Tegrak (Play Store)settings:
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)
*** For better results: Boot into CWM> Kernel specific settings> battery profile and reboot. I froze Voltage Control Extreme with TB. Then used "Rom control >Performance>Voltage Control" for CPU UV. ExTweaks for everything else + lulzactive app for tweaking
*** Mounting Points haven't changed with HyDrOG3N-ICS and Siyah v3.1.2: /emmc=external /sdcard=internal ***
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart and Screen Time
Test Results - HyDrOG3N 18.04 + Siyah v3.1 rc6
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1000MHz) (100MHz/160MHz/267MHz)
CPU UV: None (under clocked CPU instead)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 19 @~9 PM
Woke up: Friday April 20 @ 9 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (150 texts +)
- ~ 35 minutes talk time (Had a phone interview + few calls)
- Google + (~15 mins of usage)
- Tapatalk (Used the most)
- Browsing (Not much today)
- Camera (2 pictures)
- Temple Run ~15 mins
- Angry Birds Space ~10 mins
- Youtube (4 videos ~3 mins/each)
Phone died: Friday April 20 @ 2:10 PM
Screen On Time: 7h 10 min (7h 13 min when phone died)
I did not expect this combination of ROM+Kernel to kill the other two, seriously didn't . Ever since there was a battery drain on previous version, I was convinced Siyah v3.1 rc6 wouldn't perform as much. As you could see in the screenshots, the hours of CPU SPY and hours of battery chart do not correspond. Why? Explanation: I turned on the Torch Light through the Power Button in order to answer a question on HyDrOG3N's thread. But after doing that, I kept having "TORCH_WAKE_LOCK" and it wouldn't go away, hence keeping my device awake. So I decided to do a "hot boot" through an app in order to conserve battery stats/cpu spy time and make that wakelock go away. Cpu Spy kept it stats, but Android's battery chart did not(but the wakelock disappeared). So in reality I had 17h44min of run time and not 17h16 as displayed. So carrying on, I did not heavily used my phone but I used it like I normally would use. I think what made the difference this time was to tweak Lulzactive. I used the Lulzactive app by Tegrak (Play Store) and tweaked it to these settings:
inc_cpu_load = 90
pump_up_step = 1
pump_down_step = 2
up_sample_time= 50000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)
Screen off min step is 4 because of available range. That means, when screen off, cpu usage shouldn't go over 500MHz frequency step.
1400= 0
1200= 1
1000= 2
800= 3
500= 4
200= 5
*** For better results: Boot into CWM> Kernel specific settings> battery profile and reboot. I froze Voltage Control Extreme with TB. Then used "Rom control >Performance>Voltage Control" for CPU UV. ExTweaks for everything else + lulzactive app for tweaking
I want tho thank Gokhanmoral for his nonstop effort in order to eliminate battery drain and I think he really achieved that with Siyah v3.1 rc6 Keep up the good work mate!!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time and CPU SPY

Test Results - HyDrOG3NICS + N.E.A.K
HyDrOG3NICS + N.E.A.K + Abyss
​
Test Results - HyDrOG3N 12.05 + Abyss 2.0
Abyss ICS Kernel - Original Thread Link
Governor/Scheduler Used: AbyssPlug/SIO
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(950mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday May 17 @~2:45AM
Woke up: Monday May 17 @ 9AM (WiFi+Data was on throughout the night)
Usage: Regular usage + Twitter + Instagram +Tapatalk
Phone died: Friday May 18 @ 1:30 AM
Screen On Time: 5h 43min
Type of usage:
- WiFi ON (Disconnected 3 times when I went out )
- Data ON
- AutoSync ON (Google Services, Twitter, Friendcaster)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of texting (200+ texts)
- ~ 30 minutes talk time
- Tapatalk (Used a lot)
- Twitter Usage: All day (Auto sync)
- Instagram (Used once)
- Draw Free
- Youtube (2 small clips)
This kernel was very good as I expected it would be. Due to lot of demands for me to try Abyssplug instead of Lulzactice, I decided to give it a go and it seems like this governor has the proper tweaks in order to keep performance and also save battery. So during this test, it was a regular usage of phone. There was a fair load of cpu when playing Draw Free but except that, it was minimal processes. I had to disconnect WiFi twice since I went out and I don't leave my WiFi on when I go out. So i didn't have any reboots or fc this time and it was a very pleasant and smooth experience. Only issue I had was Gmail draining my battery overnight with a 20min wakelock, but I'm sure that didnt affect the battery that much. I guess that's it for Abyss Kernel. Hope this could serve as a reference and if you got any questions about AbyssScript or anything kernel related feel free to ask.
Abyss settings in recovery mode:
Enabled AFTR+LPA
Enabled Hotplug
Disabled sched_mc
Disabled BLN
Installed Abyss script
S90abyss script file modification as follows:
GPU Clock:
GPU_STEP_LOW=100
GPU_STEP_MIDDLE=160
GPU_STEP HIGH=267
GPU Voltage:
GPU_VOLT_LOW=850000
GPU_VOLT_MIDDLE=900000
GPU_VOLT_HIGH=950000
*You could modify abyss script through a root enabled file explorer by going to /system/etc/init.d/ and editing "s90abyss" file. I used ES File Explorer. Make sure you give root access to the file explorer and don't forget to mount /system. You could always pull the file to your computer and edit it there if it's easier for you.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS
Test Results - HyDrOG3N 05.05 + Abyss 1.6b
Abyss ICS Kernel - Original Thread Link
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (100MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday May 6 @~3AM
Woke up: Monday May 6 @ 9AM (WiFi+Data was on throughout the night)
Usage: Regular usage + Twitter + Instagram +Tapatalk
Phone died: Monday May 7 @ 1:35 AM
Screen On Time: 5h 24min (5h31min when phone died)
Type of usage:
- WiFi ON (Disconnected once when I went out to the movies)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h (No More Facebook)
- High amount of texting (200+ texts)
- ~ 25 minutes talk time
- Google + (~5-10 mins of usage)
- Tapatalk (Used a lot to keep track of XDA and Hydro Forums)
- Twitter Usage: All day (Auto sync)
- Instagram (Used twice)
- Draw Free
- Youtube (2 movie trailers)
One of the best kernel I have tried so far. Really smooth, no reboot, no fc! I really don't care if I only got 5:24min of screen time (which is quiet a lot for some people), I had a good 22 hours of usage. The only low point with this kernel, it will give some hard time to noobs because you have to know how to use scripts, set permissions etc.. Everyone could easily learn if you put your mind to it. So it was a normal day of usage today for me, lots of texting, Tapatalk and twitter. The settings I used for Abyss are displayed below and they're really easy to be applied. If you need help setting it up, don't hesitate to post on this thread or pm me. I will do my best to answer you the fastest I can if not, there's always someone around to answer you in here.
Abyss settings in recovery mode:
Enabled AFTR+LPA
Enabled Hotplug
Disabled sched_mc
Disabled BLN
Installed Abyss script
S90abyss script file modification as follows:
GPU Clock:
GPU_STEP_LOW=100
GPU_STEP_MIDDLE=160
GPU_STEP HIGH=267
GPU Voltage:
GPU_VOLT_LOW=850000
GPU_VOLT_MIDDLE=900000
GPU_VOLT_HIGH=950000
*You could modify abyss script through a root enabled file explorer by going to /system/etc/init.d/ and editing "s90abyss" file. I used ES File Explorer. Make sure you give root access to the file explorer and don't forget to mount /system.
Lulzactive Settings
Lulzactive app by Tegrak - Play Store
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 3 (500mhz)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU spy, BBS
Test Results - HyDrOG3N 27.04 + N.E.A.K 2.0.3x
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Monday April 30 @~1 PM
Woke up: Tuesday May 1st @ 8 AM (WiFi was on throughout the night)
Usage: Regular usage + Twitter
Phone died: Tuesday May 1st @ 1:04 PM
Screen On Time: 5h 04min (5h11min when phone died)
Type of usage:
- WiFi ON (Disconnected twice when I went out)
- AutoSync ON (Google Services, Twitter)
- Auto Brightness ON
- Bluetooth OFF
- GPS (Used for 20 Mins)
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h (No More Facebook)
- High amount of texting (150+ texts)
- ~ 20 minutes talk time
- Google + (~5-10 mins of usage)
- Google Maps Navigation (~20 mins)
- Tapatalk (Used a lot to keep track of thread)
- Twitter Usage: All day (Auto sync)
- Draw Free (~10-15 mins of usage)
Here you go guys, another test with latest HyDroG3NICS 27.04 + N.E.A.K 2.0.3x. Good results overall due to the usage throughout the day. Unfortunately, I experienced one(1) freeze when I had 13% left and as you guys know, that causes the CPU SPY and BBS stats to get erased if rebooted, so no cpu spy/bbs screenshots this time, sorry . Except that, I was satisfied with this release and how smooth scrolling was. BLN apps works but of course, it will be a wakelock, so I did not use it during the test but I tested it before I started. I modified led_timeout to 500(0.5sec) because 1000(1sec) is too long for me and also UV CPU/GPU. No more freezes with BBS and I also used NEAK Configuration app to Enable AFTR Idle Mode and Lulzactive app for my tweaking. I guess this concludes the test. If you have any questions don't hesitate to post on this thread, I will try my best to respond in a timely manner. By the way, I started using Twitter now so that's why there's 4% of twitter. If you want to follow me or ask me questions there, you guys are always welcome. @bajee11
Lulzactive app by Tegrak (Play Store)
inc_cpu_load = 90
pump_up_step = 2
pump_down_step = 2
up_sample_time= 28000
down_sample_time= 40000
screen_off_min_step= 3 (500mhz)
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time
Test Results - HyDrOG3N 14.04 + N.E.A.K 2.0.2x
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(925mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday April 15 @~11 PM
Woke up: Monday April 16 @ 8 AM (WiFi was on throughout the night)
Usage: Used phone throughout the day but not maximal use. (Had to study for exam)
Type of usage:
- WiFi ON (except when i was in school for 3 hours: 3G was activated at that time)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of texting
- ~ 10-15 minutes talk time
- Google + (~5-10 mins of usage)
- Tapatalk (Used a lot to keep track of thread)
- Browsing
- Camera (~10-15 pictures)
Back to Bed: Tuesday April 17 @ 1 AM
Woke up: Tuesday April 17 @ 7 AM (yes only had 6 hours of sleep , kinda got used to it with exams period)
Phone died: Tuesday April 17 @ 8:40 AM
Screen On Time: 4h 45min (4h50min when phone died)
Overall, this combination of ROM+Kernel was really impressive to experiment with, performance and battery wise. Although I had some random freezes when charging the phone, but I later found out BetterBatteryStats RC2 was the cause of it. Uninstalled it, and everything worked flawlessly. N.E.A.K 2.0.3 soon to be released and promises a lot of improvements with HyDrOG3n and expected to solve freezing issue.
I'll gladly accept any comments I receive from anyone. If you think this test is not representative/unfair/fake please share your thoughts. This was only done for reference purposes, so whoever wants to use it, do so. HyDrOG3N-ICS is an amazing ROM and Para's enormous input and effort, made all this possible. Let's not forget Simone201 and his amazing N.E.A.K kernel, which seems to be pretty optimized with our ROM and built to save battery without sacrificing performance. So what's the moral of the story? Get your Swag On!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY.

Test Results - HyDrOG3NICS + Thoravukk + Netchip (Stock)
HyDrOG3NICS + Thoravukk + Netchip (Stock)
​
Test Results - HyDrOG3N 12.05 + Netchip (Stock Kernel)
Governor/Scheduler Used: OnDemand/SIO
CPU/GPU (200MHz-1200MHz) (66MHz/160MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 66MHz(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Sunday May 13 @~11AM
Phone died: Monday May 14 @4:01 AM (Went to sleep late)
Screen On Time: 6h 25 min (~6h 28 min when phone died)
Type of usage:
- WiFi ON (During the whole test- Except when I went out)
- Data ON (Always)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of Texting (250 texts +)
- ~ 35 minutes talk time*
- Tapatalk (Used a lot of course)
- Browsing
- Twitter
- Youtube (~10 mins)
Here's another test guys. One of the best releases of HyDrOG3NICS so far with excellent performance and battery life. Scrolling was smooth and very touch responsive. I realized that having more frequency is actually better for me (I was thinking the opposite before, Less the Better). Just like in Fluxi and Abyss, having a lot of frequency steps allows the usage of multiple steps according to the needs of the CPU. Instead of being stuck with 5 steps we now have 11 steps (Assuming your using 200-1200). But it all breaks down to the governor and how it will use those frequencies. This is where UV comes in handy, if you could lower voltage for these extra frequency steps, you could minimize battery consumption. It won't be enormous but it'll still help. This kernel is really an amazing work and the device tweaking app integrated with the system is simply amazing. Yes, there are still a few bugs, but nothing major to refrain us from using all the features. The only issue I had, was with the backlight staying on forever. But of course, that's not a big deal by now, Everyone knows how to disable them by changing values of led_timeout. So I made a few flashable scripts to change the values. They're available on OP.(Disable, 1 secoond and 3 seconds). I know this time I only had 17 hours of runtime but that's because I used a lot of data when I went outside this time, mainly for Instagram, Youtube and Browsing. I could say, I had a really busy day with my phone.
The On Demand included with stock kernel has these tweaks as default and they are very battery oriented.
On Demand Tweaks (Default):
up_threshold= 85 (You could always increase this to 90% or 95% to save even more battery, but it might lag)
sampling_rate= 100000
sampling_down_factor= 1
down_differential= 5
Hotplug enabled(Default):
loadh= 80
loadl= 30
loadh_scroff= 1000
loadl_scroff= 80
So when cpu load is more than 80% second core is activated and when cpu load goes below 30% the second core is deactivated. The other two values, I have to ask Netchip, because 1000 seems off for scren off values.
AFTR+LPA enabled (Default)
enable_mask= 3 , which stands for AFTR+LPA
If you want to save an extensive amount of battery and you're not a heavy CPU usage I suggest you underclock your CPU from 1200 to 1000 or even 800 for some. This might result in some FCs for some or even reboot, but it really depends of each person. I suggest you give it a try.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS
Test Results - HyDrOG3N 27.04 + Thovarukk 2.50
Rating: 80 ºB
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 500(950mv) 800(975mv) 1000(1050mv) 1200(1150mv)
GPU UV: 100(850mV) 160(900mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Wednesday May 2nd @~3:30 PM
Phone died: Thursday May 3rd @3:28 AM
Screen On Time: 5h 20 min (5h 23 min when phone died)
Type of usage:
- WiFi ON
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Friendcaster Refresh Rate: 1h
- High amount of Texting
- ~ 15 minutes talk time
- Google + (~10 mins of usage)
- Twitter (throughout the day)
- Tapatalk
- Youtube (3 videos of ~4mins/each)
- Draw Free (45 mins) Got carried away with this
Really good results with Thoravukk 2.50 but unfortunately I had two random reboots. I did not investigate the cause of the boot since I was too busy with other stuff these days, but it happened once when I openned Twitter and the other time, when opening BBS. The kernel itself is really stable if we do not take into consideration these reboots and still keeps up with the high standard of saving up battery. Of course, my lulzactive settings actually play a big role in battery saving but the kernel itself is not bloated with too many features which actually makes it interesting and very battery friendly. So this concludes the test, hope this helped you guys. More tests to come!!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time.
Test Results - HyDrOG3N 14.04 + Thovarukk 2.28
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200mhz-1200mhz) (133mhz/267mhz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(925mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1125mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Tuesday April 17 @~10:30 PM
Woke up: Wednesday April 18 @ 8 AM (WiFi was on throughout the night)
Type of usage:
- WiFi ON (WiFi was off when i was out, 3G Activated)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting
- ~ 20 minutes talk time
- Google + (~15-20 mins of usage)
- Tapatalk
- Browsing (Several times during the day)
- Camera (~5 pictures + 2 Videos)
- Temple Run ~10 mins
- Cut The Rope ~15 mins
- Youtube (3 videos of ~4mins/each)
Phone died: Wednesday April 18 @ 8:30 PM
Screen On Time: 5h 50 min (5h 59 min when phone died)
This combination of ROM+Kernel was more impressive than the previous test I did with N.E.A.K. 2.0.2x . Only disadvantage with this kernel was to use so many frequency steps, which I find reduces battery time. (yup battery could of lasted even more if it weren't for all these frequency changes.) But this issue has been fixed in version 2.30 (released today) with the typical frequencies of 100, 200, 500, 800, 1000, 1200, 1400 and 1600. Unfortunately, I couldn't screenshot CPU SPY this time due to my carelessness: I tried testing a script on Script Manager but it froze and had to reboot phone. For that only reason, CPU SPY had a reset and results were no longer representative. Another big thanks to Para for his amazing Swag and Pingpong for his battery optimized Thoravukk Kernel.
Once again I'll gladly accept any comments I receive from anyone. If you think this test is not representative/unfair/fake please share your thoughts. This was only done for reference purposes.
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time.
Test Results - HyDrOG3N 18.04 + Netchip (Stock Kernel)
Governor/Scheduler Used: Lulzactive/VR
CPU/GPU (200MHz-1200MHz) (133MHz/267MHz)
CPU UV: 200(825mv) 300(850mV) 400(875mV) 500(950mv) 600(925mV) 700(950mV) 800(975mv) 900(1000mV) 1000(1050mv) 1100(1100mV) 1200(1150mv)
GPU UV: 133(850mV) 267(950mV)
^^USE SETTINGS ABOVE WITH CAUTION, WHAT WORKS FOR ME MIGHT NOT WORK FOR YOU ^^
Test Start: Thursday April 20 @~10:30 PM
Woke up: Pulled an all-nighter to study for exam (fml) (WiFi was on throughout the night)
Type of usage:
- WiFi ON (During the whole test)
- AutoSync ON
- Auto Brightness ON
- Bluetooth OFF
- GPS OFF
- Network Location ON
- Be Weather Refresh Rate: 1h
- Facebook Refresh Rate: 1h
- High amount of Texting (200 texts +)
- ~ 10 minutes talk time
- Tapatalk (Used a lot)
- Browsing (Not much)
- Youtube (20-25 videos ~3 mins/each)
- Updated new version of Facebook (Battery killer!! Update installs FB Messenger + Camera)
Phone died: Friday April 20 @4:46 PM
Screen On Time: 7h 29 min (~7h 35 min when phone died)
Trying to keep my tests representative and due to some useful feedback I received from users, I'm going to UV CPU/GPU like I did for my first two tests. (I didn't do it for Siyah, sorry guys) When I started using this kernel, I right away noticed the difference in smoothness. It's been so long I actually used the stock kernel that I even forgot how it felt like. Unfortunately, I had some issues with UV and my usual settings wouldn't work and I was getting random freezes right after boot so I had to add up +25mV for 500MHz/1200MHz. I still applied my Lulzactive app settings and I will be doing so in all my future tests as well. So now for the results: since I was studying for my exam and wasn't using my phone much, I decided to take a few breaks here and there to play games and I left YouTube ON for a long time in order to listen to music.(I have music on my phone but I needed an app that would consume battery) So as you guys read above, I didn't sleep all night... stupid me should of studied earlier instead of fooling around with my phone Lol.. But I still managed to send more than 200 text messages.(Got into a serious texting convo in the middle of the night with one of my friends )
So let's talk about screen time now.. DAMN, 7h29!! HOW DID I DO THAT? well let me tell you something: DON'T TRY THIS AT HOME! because you most probably wont reach close to 7hrs because we all use our phones differently and I get these crazy screen hours because I don't do hardcore cpu usage. As you guys could notice, most of the time, my phone joggles between 200MHz-500MHz. Other frequencies are being used as well duhh, but not as much as these two. I had some issue with deep sleep due to F#@[email protected]^% Facebook update that kept my phone awake for no reason and some how MMS as well! Well yea, I've been sending a lot of pictures through text/mms but it's weird that it actually stayed on for such a long time. But everything went back to normal after a point and MMS stopped messing with my Deep Sleep. That's right, don't mess with my Deep Sleep! Okay enough with the jokes, I guess it's time to conclude this test. A++ Loved the battery life. Those rumors were actually true: Stock is Amazing. Shock of the day: I rushed to take screenshots of my screen before walking into my examination room because my battery was at 1%!! I figured it would die during my exam of 3 hours. This beast stayed alive till I was done my exam and even let me take more screenshots, browse and post about it on this thread!!! Hats off S II, your too cool for me. Hope you enjoyed the review and if you didn't laugh at my lame jokes, I'll make sure you do in my next review
Lulzactive app by Tegrak (Play Store)
inc_cpu_load = 90
pump_up_step = 1
pump_down_step = 2
up_sample_time= 50000
down_sample_time= 40000
screen_off_min_step= 11 (500mhz)
Tricky stuff: GPU UV is not available through Voltage Control extreme and obviously you can't use ExTweaks. So I had to use init.d script. I used the same script I had for my led_timeout, since backlight value was only "2". That value is really useless because it feels like your phone is having a seizure everytime your trying to touch the soft keys and "Hold back to kill" does not work with that value. So I changed it to 500, and added GPU frequencies of 133/267 with 850mv/950mv. Also used Lulzactive app for tweaking. One thing I didn't check with this test: AFTR+LPA. Don't know if it's default or not. Have to check that next time.
I want tho thank Netchip for his effort and input in creating a remarkable kernel. I believe someone said he was only 12 yrs old. So Netchip, if you really are 12, FML!! You're [email protected]#$% awesome bro!! Nop, I didn't forget you Para! You guys make a nice team, seriously.. Keep up the good work!
* I only have the original standard battery supplied by Samsung. No extended battery was used during any of my tests.
Thanks it if this post was useful
Attached below are the screenshots of Battery Chart, Screen Time, CPU SPY, BBS

Great work dude... I'll keep on this track.. will subscribe to this!!
Sent From Galaxy S II BEAST

U know what... even we will get another kernel with superb battery back up n more. . Coming soon.. from Dorimanx .. see my signature..
Sent From Galaxy S II BEAST

Can't wait for Siyah's results
From my calculations according to the teaser that you PM'd me, I am guessing a screen on time of around 6 hours 30 minutes

Nice to see all your results in one thread. Curious to see your Siyah 3.1RC6 results!
I'm on NEAK, so from the looks of it I'm on the "worst" one Not that your NEAK results are bad.
Btw, again I'm amazed how people with a stock 1650mAh battery get better batterylife then myself with the 2000mAh. Do you use whatsapp?

XDA mark said:
Nice to see all your results in one thread. Curious to see your Siyah 3.1RC6 results!
I'm on NEAK, so from the looks of it I'm on the "worst" one Not that your NEAK results are bad.
Btw, again I'm amazed how people with a stock 1650mAh battery get better batterylife then myself with the 2000mAh. Do you use whatsapp?
Click to expand...
Click to collapse
No i dont. I basically use a lot of fb, google+, tapatalk, youtube, browser a little and lots and lots of texting.

Nice thread! Nicely done.
Sent from my i9100. No HyDrOG3NICS? No SWAGG..

Paradoxxx said:
Nice thread! Nicely done.
Sent from my i9100. No HyDrOG3NICS? No SWAGG..
Click to expand...
Click to collapse
Thanks mate, I appreciate it!

Cool.. exactly what i was looking for..

Why did you underclock for Siyah? I mean, from what I've read, underclocking just decreases battery life as it takes longer for the task to be completed...

darkgoon3r96 said:
Why did you underclock for Siyah? I mean, from what I've read, underclocking just decreases battery life as it takes longer for the task to be completed...
Click to expand...
Click to collapse
Most tasks I do, do not require high amount of CPU usage, except for my games. Which I don't play that often. So a range from 200-1000 is actually enough for my usage.

Rc6 results soon?
Sent from my GT-I9100 using XDA

Dark Emotion said:
Rc6 results soon?
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
its up

Insane Siyah results! ****ing insane! Sorry for my language but this is crazy xD
One question: did you still have a smooth experience with those Lulzactive settings? No lags when swiping, everything fast and like it should be?
I tried Lulzactive on GB, but it really start lagging and ruins the experience (if you tweak it to much towards battery)

XDA mark said:
Insane Siyah results! ****ing insane! Sorry for my language but this is crazy xD
One question: did you still have a smooth experience with those Lulzactive settings? No lags when swiping, everything fast and like it should be?
I tried Lulzactive on GB, but it really start lagging and ruins the experience (if you tweak it to much towards battery)
Click to expand...
Click to collapse
I did experience a small lag while scroling in Tapatalk, but somehow that lag wasn't there while scrolling through system settings. I figured it's because Tapatalk is a beta version. But you're right, I really tweaked it towards battery and there is that small lag which is barely noticeable. You guys could reduce the tweak towards performance/battery with this:
inc_cpu_load = 90
pump_up_step = 4
pump_down_step = 1
up_sample_time= 10000
down_sample_time= 40000
screen_off_min_step= 4 (500mhz)

Wow dude! Amazing Siyah results! Gokhan really is a genius, great battery life with easily the most features
By the way, what font did you use in Siyah's battery testing?

darkgoon3r96 said:
Wow dude! Amazing Siyah results! Gokhan really is a genius, great battery life with easily the most features
By the way, what font did you use in Siyah's battery testing?
Click to expand...
Click to collapse
Sansation Regular

[Q] [I9505] [GAMING] What is the best rom for games ?

I'm searching for the perfect gaming rom
For me a gaming rom need to have good performance and great battery life.
I tried a lot of rom but didn't find the perfect one.
Please share your experience (rom, kernel, settings) which make you stay with.

Well, I'm using the GPE rom by Danvdh. I'm running the default kernel that comes with the rom (Googy-Max kernel)
It seems to perform pretty well.
I underclocked the CPU to 1242 (1.2 GHz) and it seems to be running GTA San Andreas (on default settings) and The Walking Dead just fine and without any issues like stuttering and slowdowns.
I could get about 2 hours playing those games on battery before the battery dies (But the phone is only a couple of moths old, so the battery isn't worn out). This of course is just an assumption as I generally don't let the phone go below 50% or 20%.
I've disabled the button backlight and vibrations. Set the screen brightness to the lowest setting (adaptive brightness off). Turned off GPS.
Turn off wifi and mobile networks if you want maximum battery while gaming (duh). Heck, you might as well turn off the radio if you want to maximize battery while gaming, (put it in airplane mode) cuz that eats the most juice (aside from the screen).
CPU Governor: Intelliactive
I/O Scheduler: FIOPS
GPU Governor: OnDemand
Every other option in the STweaks app is set to default.
Also, make sure there are only a few background apps running.