Database Users

(CM7/MIUI) Screenstate, Governor and Threshold Control Script

Hi Folks,
For those who are interested, I have modified the 90screenstate_scaling script used in Zach's (and now Glitch's) kernel for use with other CM7 compatible kernels. The aim is to create a very simple script that can easily be read, modified and improved upon by non-coders, such as myself.
I have retained only the code that will read the screen state, set the governor appropriately and set the scaling threshold, giving users complete control over the scheduling behavior of their CM compatible kernel.
I am not a coder and all credit goes to FloHimself and zacharius.maladroit for the original content. all I have done is (hopefully) simplify the script and make it easy for non-specialists to read.
If you would like to try it out, copy the script in to /system/etc/init.d and modify the values to your liking. If you are already on Zach's kernel there is nothing new here, as you already have this script.
The script currently includes kernel defaults from Glitch for the smartass governor, from Zach for the conservative and ondemand governors, a few experimental settings, and of course, the ability to modify them yourself.
If you add anything or make any modifications (particularly in relation to your specific usage pattern) you would like to share, please post them and I will update this thread. If you make modifications, comment them appropriately and explain your usage pattern for which the settings work best so that people know if it would work for them.
The experimental conservative settings that I have made (that are currently in use on Glitch kernel) for the screen off state are designed to aggressively keep the frequency very low, almost like a 100mhz frequency cap, while still allowing them to scale up under considerable load. They are (hopefully) ideal for background screen off behaviour such as listening to music, exercise applications or aggressive sync and push/pull email behavior (like in an office).
The experimental smartass settings are designed to test the hypothesis that quick downscaling may cause as many lags as as slow scaling up behavior. The goal is to create a more linearly scaling version of smartass which is slower to upscale or downscale (only a matter of milliseconds difference). These are still under testing.
With one of the main reasons for using smartass as a single governor, the min/max frequencies for the screen on/off state no longer applicable with the governor changing in relation to the screen state, I have moved to ondemand settings, which may have battery implication while the screen is on, but they are VERY smooth.

*subscribes*
we could probably make conservative governor more aggressive
with the settings that laststufo used on his kernel but I'm not sure if it would scaled up fast enough if you used e.g. some DSP settings on sound while the screen is off
worth as shot
if I don't forget it - I'll post the settings later

Subscribes too
I like the idea and the simplicity of this. And with Zach's help, also known as "F*ckin scripts master" (almost a private joke ), it can only be great.

I'm a big fan of simple, though as a user of Arch Linux on the desktop I have no choice (BSD style init scripts a boot - beautiful simplicity)!
It's great you lads are watching this! Hopefully the thread will grow in to something, even if it is just an sandbox for users to experiment with the settings they prefer. If nothing else, hopefully you guys get some useful info!

I just added a bit of an experimental version that moves away from the default smartass values.
I am hypothesizing that the very accasional lags in the smartass governor might be related to the governor scaling down too fast, rather than it not scaling up fast enough.
I changed the default down threshold from 40 to 35 and the default up threshold from 60 to 65. Hopefully this will scale up and down a little more linearly and this will make the GUI even smoother. I am still testing this theory at the moment, but thought I might post it (on the first post) if anyone wanted to have a go.

well.heeled.man,
you need to test your conservative settings while the screen is on
they're way too aggressive (at least the up threshold, down threshold may be ok)
also the freq_step at 10% should be at least at 15%
if we compare it with laststufo's kernel (he almost had 100 MHz steps everywhere: 100, 200, 400, 600, 800, 900, 1000 MHz)
so that needs to be compensated to get smoother & similar behavior
I'll take a look & see how the new smartass settings work out
my new conservative settings are:
echo "76" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold # 50 # 76 # 76
echo "30" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold # 35 # 12 # 30 (higher will lead to noticable lags) # 35
echo "15" > /sys/devices/system/cpu/cpufreq/conservative/freq_step # more aggressive ramping up (50)
this currently keeps the cpu between 100-200 MHz while playing MP3s for me (screen off) - mostly 200 afaik right now
but I'll try your conservative settings, too, when I find time - let's see how they are in terms of "smoothness" (I'm sure they're not too usable with the GUI but could be great for background tasks while the screen is off)

Hi Zach, indeed, I would say that the conservative settings are completely unusable with the screen on. I would not recommend these with the screen on.
However, with music (DSP manager too) GPS and Cardio Trainer all running (my cycle home), it seems to work fine (screen off). Every km, Cardio trainer speaks the time taken over the music (two audio streams). With many kernels this becomes slow, or slurred, but sounds perfect with these settings.

well.heeled.man said:
Hi Zach, indeed, I would say that the conservative settings are completely unusable with the screen on. I would not recommend these with the screen on.
However, with music (DSP manager too) GPS and Cardio Trainer all running (my cycle home), it seems to work fine (screen off). Every km, Cardio trainer speaks the time taken over the music (two audio streams). With many kernels this becomes slow, or slurred, but sounds perfect with these settings.
Click to expand...
Click to collapse
awesome !
so it still raises the frequency when needed ?
100 -> 200 (or more)
you checked via e.g. CPU Spy ?
thanks !

Yes, it still goes up when needed (confirmed via CPU Spy), but it needs to be really pushed. It seems like good behaviour in the screen off state.
EDIT: something in the region of a 66%/33% 100/200mhz split at these settings.

I am struggling to confirm that my settings are being applied as I would like in the screen off state. I can read off the values in /sys/devices/system/cpu(/cpu0)/cpufreq/conservative if I manually set conservative in Pimp My CPU with the screen on, but the behaviour seems at odds with the values i.e. not as laggy as one would suspect.

As (a variation of) this script are now used in Glitch's too, I have changed the comments to allow people to very easily see which settings are from kernel devs (which should probably be left alone should you wish to return to their defaults) and experimental settings (which I would suggest you change, if you change any). If you want to use parts of it in Zach's, I would suggest cutting and pasting the experimental part into the appropriate part of Zach's script as overwriting any part of it would remove much of his additional functionality.

This is great guys - thanks for this

With one of the main reasons for using smartass as a single governor, the min/max frequencies for the screen on/off state, no longer applicable with the governor changing in relation to the screen state, I have moved to ondemand settings by default. This may have battery implication while the screen is on, but they are VERY smooth.

wrong spot

screenstate_scaling_V49.zip
that's the current version of my screenstate_scaling script that I offer as an option with Neo 17 r7
most of the stuff moved into the S98system_tweak script that now is shipped with the kernel

[Q] Advice on my Nook's current softwares/settings

Looking for some advice as I am still pretty noob-ish. I apologize in advance if this thread is out-of-bounds in any way; every search for answers that I've conducted always seem to beat-around my questions. Any advice will be thanked ASAP, even if you can shoot me a url to the advice I need that would be awesome. If it appears that I'm on top of things that would be great to know as well. Thanks in advance!
I'm running CM7.1.0 Encore Signed emmc with Tiamat v4.1.0 kernel; using Ram Manager Pro for optimization in lieu of task killers, Nook Tweaks for CPU stepping and voltage management, "Antivirus Free" for virus protection, "Battery Calibration" to monitor/obtain max charge (~4200 mV), and "Set DNS" for faster web-based loading. I've also disabled Android Cell-Standby Services through ADB and removed useless apps such as camera and voice apps using Root Explorer. My biggest questions are as follows:
1. Am I running the best kernel for speed and battery saving?
2. What are good voltage settings for better battery conservation (currently on default voltage settings)?
3. Is there really a need for a virus protection, and if so is there something better than what I have?
4. Is there any settings that I should know about for "Set DNS" (didn't change settings, just installed and activated it)?
5. Are there any other technical ways to adjust battery consumption (have to charge every night under normal use)?
I keep telling myself that I'm probably good to go, but I want to be certain that I've been as thorough as I can be. If anyone does something differently with great results please feel free to advise! As I said before, any advice or even just urls that help with my questions will be thanked. Can't wait to discuss this more!

vessamj said:
Looking for some advice as I am still pretty noob-ish. I apologize in advance if this thread is out-of-bounds in any way; every search for answers that I've conducted always seem to beat-around my questions. Any advice will be thanked ASAP, even if you can shoot me a url to the advice I need that would be awesome. If it appears that I'm on top of things that would be great to know as well. Thanks in advance!
I'm running CM7.1.0 Encore Signed emmc with Tiamat v4.1.0 kernel; using Ram Manager Pro for optimization in lieu of task killers, Nook Tweaks for CPU stepping and voltage management, "Antivirus Free" for virus protection, "Battery Calibration" to monitor/obtain max charge (~4200 mV), and "Set DNS" for faster web-based loading. I've also disabled Android Cell-Standby Services through ADB and removed useless apps such as camera and voice apps using Root Explorer. My biggest questions are as follows:
1. Am I running the best kernel for speed and battery saving?
2. What are good voltage settings for better battery conservation (currently on default voltage settings)?
3. Is there really a need for a virus protection, and if so is there something better than what I have?
4. Is there any settings that I should know about for "Set DNS" (didn't change settings, just installed and activated it)?
5. Are there any other technical ways to adjust battery consumption (have to charge every night under normal use)?
I keep telling myself that I'm probably good to go, but I want to be certain that I've been as thorough as I can be. If anyone does something differently with great results please feel free to advise! As I said before, any advice or even just urls that help with my questions will be thanked. Can't wait to discuss this more!
Click to expand...
Click to collapse
Sounds like a good setup. You may experience market issues by removing cell service and camera, some apps may not show up. My question is how did you get tiamat's kernel to run on the nook?

bdcrim said:
Sounds like a good setup. You may experience market issues by removing cell service and camera, some apps may not show up. My question is how did you get tiamat's kernel to run on the nook?
Click to expand...
Click to collapse
I'd like to know that as well......

I used Tiamat's latest Evo NON SBC Kernel ( http://tiamat-dev.com/tiamat_evo/ ). After downloading I installed the zip through Clockwork (after wiping both caches) in boot-recovery and I'm guessing it's working fine... what issues have there been with Tiamat's before?
-XDA Premium on CM7 Nook Color

vessamj said:
I used Tiamat's latest Evo NON SBC Kernel ( http://tiamat-dev.com/tiamat_evo/ ). After downloading I installed the zip through Clockwork (after wiping both caches) in boot-recovery and I'm guessing it's working fine... what issues have there been with Tiamat's before?
-XDA Premium on CM7 Nook Color
Click to expand...
Click to collapse
No issues reported, because the only kernels around this forum are Barnes and Noble source. Let us know how the battery life is. Not to question your integrity, but did it stick, showed up in settings, about tablet?

That's a great point. It didn't stick. All seemed well when I installed it but I guess the long pause on the next reboot was from the system restoring the last kernel I had. After looking around some more I came to realize that in order to have control of CPU stepping with Nook Tweaks you must have Dalingrin's 2.6.29 OC Kernel 09/01/11 (http://coachz.inetpro.org/~dalingrin/nook/kernels/090111/) or later. So that's fixed.
Meanwhile my battery is only good enough that I have to charge it at the end of every day under normal use, sometimes earlier.
After that, my list of questions fall to:
1. What are good Nook Tweaks voltage settings for better battery conservation (currently on default voltage settings)?
2. Is there really a need for a virus protection, and if so is there something better than what I have?
3. Is there any settings that I should know about for "Set DNS" (didn't change settings, just installed and activated it)?
4. Are there any other technical ways to adjust battery consumption (have to charge every night under normal use)?
-XDA Premium on CM7 Nook Color

vessamj said:
That's a great point. It didn't stick. All seemed well when I installed it but I guess the long pause on the next reboot was from the system restoring the last kernel I had. After looking around some more I came to realize that in order to have control of CPU stepping with Nook Tweaks you must have Dalingrin's 2.6.29 OC Kernel 09/01/11 (http://coachz.inetpro.org/~dalingrin/nook/kernels/090111/) or later. So that's fixed.
Meanwhile my battery is only good enough that I have to charge it at the end of every day under normal use, sometimes earlier.
After that, my list of questions fall to:
1. What are good Nook Tweaks voltage settings for better battery conservation (currently on default voltage settings)?
2. Is there really a need for a virus protection, and if so is there something better than what I have?
3. Is there any settings that I should know about for "Set DNS" (didn't change settings, just installed and activated it)?
4. Are there any other technical ways to adjust battery consumption (have to charge every night under normal use)?
-XDA Premium on CM7 Nook Color
Click to expand...
Click to collapse
Sounds like your battery drains about normal. I lose around 12 to 15% per hour, always have. I have tweaked the voltage some, but did not see much of a result. There is is no need for virus protection that I am aware of. I have not seen a single thread on that issue (I have been around this forum for a year)
I can't advise on any DNS settings. You may want to play with the voltage some and see if that makes any difference on battery life. By the way, there is an updated kernel in the development forum in MiRaGe's kang build. Look for it in the OP. Also his build, for me, is the fastest and most responsive that I have used. Good luck.

bdcrim said:
Sounds like your battery drains about normal. I lose around 12 to 15% per hour, always have. I have tweaked the voltage some, but did not see much of a result. There is is no need for virus protection that I am aware of. I have not seen a single thread on that issue (I have been around this forum for a year)
I can't advise on any DNS settings. You may want to play with the voltage some and see if that makes any difference on battery life. By the way, there is an updated kernel in the development forum in MiRaGe's kang build. Look for it in the OP. Also his build, for me, is the fastest and most responsive that I have used. Good luck.
Click to expand...
Click to collapse
Thanks for the advice... I'll look up the kernel and see how it goes.

1) There's some voltage stuff listed here
2) I don't use any, it seems to me like most malware is centred around phones anyway. I just use Droidwall to block internet access for anything shady-lookin'. LBE lets you block more permissions, or CM7 will too, but with no SIM, no mobile data, no GPS, there is just not as much to be concerned about on the nook . Basically, being aware of what Permissions are, and checking them, should keep you safer than relying on a faceless, profit-motivated company.
www.theregister.co.uk/2011/11/21/mobile_security_dust_up/
4) If you're interested, Tasker can be used to under/overclock any app. So, your flashy game will run at 1200, your simple text reader at 800, and so on.

selection16 said:
1) There's some voltage stuff listed here
2) I don't use any, it seems to me like most malware is centred around phones anyway. I just use Droidwall to block internet access for anything shady-lookin'. LBE lets you block more permissions, or CM7 will too, but with no SIM, no mobile data, no GPS, there is just not as much to be concerned about on the nook . Basically, being aware of what Permissions are, and checking them, should keep you safer than relying on a faceless, profit-motivated company.
www.theregister.co.uk/2011/11/21/mobile_security_dust_up/
4) If you're interested, Tasker can be used to under/overclock any app. So, your flashy game will run at 1200, your simple text reader at 800, and so on.
Click to expand...
Click to collapse
Thanks! I'm definitely gonna purchase Tasker now, as I've been looking at it for a while... and I'll check out the voltage and the security links for sure.

selection16 said:
1) There's some voltage stuff listed here
2) I don't use any, it seems to me like most malware is centred around phones anyway. I just use Droidwall to block internet access for anything shady-lookin'. LBE lets you block more permissions, or CM7 will too, but with no SIM, no mobile data, no GPS, there is just not as much to be concerned about on the nook . Basically, being aware of what Permissions are, and checking them, should keep you safer than relying on a faceless, profit-motivated company.
www.theregister.co.uk/2011/11/21/mobile_security_dust_up/
4) If you're interested, Tasker can be used to under/overclock any app. So, your flashy game will run at 1200, your simple text reader at 800, and so on.
Click to expand...
Click to collapse
Would you be willing to share a profile for 4) as this is exactly what i am trying to do with no luck thus far. Thank you.

gsutton said:
Would you be willing to share a profile for 4) as this is exactly what i am trying to do with no luck thus far. Thank you.
Click to expand...
Click to collapse
This is where I got the info;
http://tasker.wikidot.com/cpu-profiles-governor-frequency-control

[Guide][Tweaks] The Complete Guide For Maximum Battery Life V2.1 - Updated 7.10.13

Last update: 7.10.13
{
"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"
}
This is the complete guide of how to handle your battery in the most efficient way possible.(GB/ICS/JB version).​
This guide refers to Android users in general (Samsung, HTC etc..) in addition to SGS2 users.
ROOT: Yes.
ROM: Any rom will do.
Kernel: Siyah/Dorimanx is preferred but any other will be fine.
Human features: Patience
After an extensive research regarding 'how Android OS works' and reading hundreds of pages (yes 1000 pages in 1 thread) in XDA regarding topics such as: BBS (BetterBatterStats), MagicConfig by geko95gek, Kernel Info, Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs by droidphile etc, I have come to conclusion that there is currently no better configuration than mine.
I almost don't have wakelocks, during the night (7 hours sleep) I have between 3-4% drain which is really good, of course, you can get better drain ,for example, 1 % during a whole night BUT users like that turn off their data connection OR switch to airplane mode, I really don't like doing that but of course you could do that too and enjoy your 1% drain.
Before I wrote this guide I tried these configurations in 5 different infinite sgs2 mobile phones of my friends and Nexus devices, they all were blown away from the results they experienced from their battery.
I wrote this guide because XDA users have helped me a lot in all the aspects of Android, so now I can help the XDA community too.
Last update:7/10/13
Step 2 updated with solutions on the go.
Step 3 is now LBE version 5 compatible.
Step 4 updated for Dorimanx users as well.
Faq Updated
Post #1​
Wakelocks: What is it ?
Monitoring the wakelocks
LBE security manager: internet permissions & prevent apps to be put in cached after a restart
ExTweaks/STweaks & governors - Siyah/Dorimanx kernel users ONLY!
Undervolting & Governors
Post #2​
Freezing google/Samsung apps using Titanium Backup Pro
Screen Brightness
Accounts & sync
Fast Dormacy - Should/Can I disable it ?
Battery calibration - Should I do it ?
Network/operator modem support - How to tell if your modem meet your network standards
Variance
Learning to read the battery graph
Post #3​FAQ
When you're done with the guide please do come back and share your results with us.
I'll try to simplify things as much as I can so the common user could understand.
Let's begin,
1. Wakelocks: What is it ?
When you develop an app in Android there are options for you (as a developer) to let the app start during a different time or a different change, sometimes it is really essential, for example our build in Alarm clock(Also: Widget/Music player), we need it to start the alarm in a specific time thus this process is important and it will open up by "it self".
Counter example is a simple game or a weather app, we only use it once in a while and after we use it we don't need the process anymore so we close it, but most of the time the developer add all sort of commands to start the process even when we don't use this exact process, for example if we boot the device/click on the media app button the app will go into cached processes (System settings->Applications->Running->Click on cached processes), but let's say it's an app we use once a week or a game we play once a week, there is no need to put this app in the cached processes (since it consumes the battery) so this is why we would like to close this option.
Notice – When you open an app and close it the process is still in the cached processes because if you open it again, it will open in a sec (since it's in the cached processes)and that’s a good and efficient thing, but if you close it from the cached processes you will only make things worse because when you open it AGAIN the Android OS will AGAIN, put the app in the cached processes and this is yet again will consume the battery.
How to tell if you can turn off or not in an app/game:
Basically the idea is this,
If we are talking about an app that the whole very existence is to do things by it self (Playing songs/Setting alarms/Auto-commands apps) then of course we won't turn anything off.
If we are talking about a type of apps that their whole process is to do something particularly which will take place only when we open the app (Bar-code scanner/Weather app/Shazam/Office apps/GPS apps/Games so of course we will turn everything off.
If we are talking about ROOT apps so I suggest not to touch anything.
First thing you will do is to download Gemini App Manager 2.6.0, this app will handle these wakelocks and as we already mentioned will give us full control over 'when to put/not to put the app in the cached processes/running services'.
DON'T UPDATE TO VERSION 2.7 - THE NEW VERSION HAS NO WORKING EXPERT MODE ! ! !
After you downloaded the app, open it,
Hit the option touch key (left to the home button) and go to 'Expert Mode', you will find there, all the applications your phone contains. What we are looking for is the orange icon the says 'AUTO' under each app:
once you find an app/game with this icon, think, and ask yourself "Do I need this app/game to open up by it self?" (See the examples with the clock app above).
If your answer is "NO!" (90% of the cases the answer is no-read above when the answer is YES), then press this app/game for about 2-3 seconds, a window will open and choose 'ConfigAutorun (root)'.
A new window will appear with all sort of commands: On package added, on app widget update, After boot etc, as you can tell the name of the command does what it says for example: 'On package added' -> if you added a package to the app, the app will be put in cached process.
Change to OFF all the commands:
and there you go, this app will never fool around!
2. Monitoring the wakelocks:
Download the app: BBS
BetterBatteryStats aka BBS: Why do I need this app ?
After you managed to finish step number 1, you can now install BBS on your system.
Once your done open it and choose partial wakelocks, we will focus on this section.
Charge your device to 100% and when it reaches 10% or so, open BBS hit the options touch key and choose 'Dump to file':
this will generate a .txt file with all the apps/games that did wake your phone and caused drains.
"BUT HEY I DON'T UNDERSTAND ANYTHING FROM THIS FILE AND THIS APP IS HARD TO UNDERSTAND!!!", first you need to relax and go to the BBS thread BBS, the developer is kind enough to let you put the file there and he will look it over and tell you what is the main problem you should focus, and decide if to remove the app or maybe change something in the setting of the app.
If you want to learn about this log file and understand it better just read the thread (like I did) it contains more than 1000 pages, so after 10-20 you will have some clue about this app.
Remember, this is the BEST application that can track your battery drains and tell even if your kernel is waking up the phone, just dig in BBS and you will see, there is no other alternative than BBS, remember that and don't ask for a substitute.
Q: How can I solve BBS wakelocks on the go ?
A: Get in here.
Also, if you have EventLog wakelocks here is the solution:
Download System Tuner. open the app and go to 'Startups' and look for 'Google service framework' and over there disable both 'checkin.EventLogService'.
Be advice EventLogService wakelocks only happens with stock Samsung ROMS.
ALSO, read the FAQ.
3. LBE security manager: internet permissions & prevent apps to be put in cached after a restart: version 5+
We all know that every time we go to the inet (not via wifi) we are starting to see an immediate battery drain.
The best way is to install a firewall app (which is MUCH more than that btw and it's free) that will control our inet pipe.
The user zagzag99 was kind enough to translate the latest version (4) of that app (Notice that in Play store it's version 3 ONLY) get it here: LBE Security
After you installed the app,
Tap on More -> Permissions -> All apps
Now you are looking at all your apps/games (including system app by tapping on 'Download' on the left and choosing 'System'), by clicking on one of the app/game you would see the permissions the app wants from your phone, if it is a game that you play offline then why does this game want to go online? More-than that, why the game wants to access my call records!?
This is why you won't allow it and eventually you'll close the inet pipe and the rest for each app/game you don't want to go online or even get your precious information.
After your done we will now deal with the auto start issue.
Repeat step a, and choose a random app, as you can see the first option in every app is 'On boot permissions' so you can turn it off or back on.
Now, this is very important, I only say it once, if you see an app/game that you don't even use or use once a week 'turn it off', but if you see an app/game that you use most of the time leave it as it is, why ? Obviously you didn't read step number 1.
4. ExTweaks/STweaks& governors - Siyah/Dorimanx kernel users ONLY! **Unless you can undervolt with your kernel**
Download STweaks, if you want to understand what each command/line does please read up: Here or you can just do what I tell you to and enjoy better battery.
First of all I want to thank geko95gek who inspired me a lot regarding STweaks .
Open STweaks,
CPU tab:
MAX OC FREQUENCY: 1000000Khz
CPU_UV tab:
You can undervolt here or in setCPU (See step 5).
Be advise #1: for some reason Siyah V6b5 doesn't save the changes after reboot BUT setCPU does.
Be advise #2: Dorimanx users are good to go.
GPU tab: - SGS2 users input - Different devices try to lower 1 step back.
Siyah steps:
GPU FREQ STEP1: 54Mhz
GPU FREQ STEP2: 108Mhz
GPU FREQ STEP3: 160Mhz
GPU FREQ STEP4: 200Mhz
GPU FREQ STEP5: 267Mhz
GPU VOLTAGE LEVEL1: 850mV
GPU VOLTAGE LEVEL2: 900mV
GPU VOLTAGE LEVEL3: 950mV
GPU VOLTAGE LEVEL4: 1050mV
GPU VOLTAGE LEVEL5: 1150mV
Dorimanx steps: (Basically the default)
GPU FREQ STEP1: 108Mhz
GPU FREQ STEP2: 160Mhz
GPU FREQ STEP3: 200Mhz
GPU FREQ STEP4: 267Mhz
GPU FREQ STEP5: 267Mhz
GPU VOLTAGE LEVEL1: 900mV
GPU VOLTAGE LEVEL2: 950mV
GPU VOLTAGE LEVEL3: 1000mV
GPU VOLTAGE LEVEL4: 1050mV
GPU VOLTAGE LEVEL5: 1150mV
You're DONE!
5. Undervolting& Governors:
Be advise: If your kernel doesn't support undervolting move to the next step, but I recommend to use a kernel that has support because when the phone is in deep sleep or on 200mhz (when you're not using it) you could save a lot of battery.
Be advise #2:I am going to recommend the use of setCPU and STweaks (Siyah/Dorimanx kernel only - if you don't have siyah you can do this step also as long as your kernel support undervolt), a lot of people wouldn't recommend the use of these apps together since they MIGHT conflict with each other, BUT if you will go through this step and read carefully it wouldn't be a problem in fact, it will work just fine
Download setCPU, if you want the latest version you can buy it in the Play store (support the developer).
Version 2.2.4 would be fine too, if you want to understand what each governor means and what is cfq please read up: Here and Here or (if you’re a lazy ass user) you can just do what I tell you to and enjoy your battery:
Open setCPU,
Main screen:
change to 200-1000 Mhz (it should be like it since you already changed it in ExTweaks) and tick 'Set on boot', also make sure 'ondemand' and 'ROW/CFQ' are chosen as governor/io :
Profiles:
Make a new profile and choose 'Add Condition -> Screen On/Off' and choose 'Screen off' and save.
Hit next and choose 200-500Mhz, tick 'Set the CPU governor' and choose 'conservative'.
Choose priority 50.
This profile will make sure while the screen is off there won't be any jumps to high frequencies.
Make another new profile and choose 'Add Condition -> Battery level' and choose '10%' and save.
Hit next and choose 200-800Mhz, tick 'Set the CPU governor' and choose 'conservative'.
Priority is 49.
This profile will let you squeeze the last 10% of the battery like they were 20% but the UI will lag.
Tick those profiles and tick 'Enable Profiles' at the bottom.
Results of step a & b :
Voltages Screen: (Only supported kernels)
Be advice: This stage is the most exhausting, annoying and irritating stage you could ever find but in the end it's worth every second.​Since we put a range of 200-900Mhz we will focus on these frequencies only (of course if you decide to put the range between 200-1200Mhz you will focus on them only).
We will scroll down and look for 200Mhz, 1st white row represent the default mV that Samsung has put in order to max UI, and 2nd white row represent your mV change,but we are smarter than old Samy so we will start to change.
200Mhz – Is usually between 825-875mV it varies between each phone (each phone has different ROM/Kerenl)
So you ask yourself, which mV should I choose?
Well my friends, that’s the 1 million dollar question, let's say you chose 850mV:
Touch the 200Mhz and change it to 850mV afterwards hit the 'Right icon' next to the save icon
if your phone is still working and didn't get stuck go back to the 'MAIN' tab and choose 200-200Mhz (yes exactly like that) and then we will go to the 'INFO' tab, scroll down and choose 'Stress test':
if 'Sress Test' ran for about 4-5 mins and everything is still working, you can stop it by pressing the back key and it means we can continue to the next stage.
Download Stability Test
Open the app and choose Classic stability test – this will ensure the test of only the 200Mhz frequency.
If after step b&c your phone is still working that means that the undervolt you chose is working great. (It doesn't mean that your phone won't freeze-it might), you can undervolt more and see what is your limit.
Do the same process to all the frequencies, of course if you're in 500Mhz you choose the main profile (setCPU) 300-300Mhz in order to test only this frequency.
When you're done, change back in setCPU'MAIN' tab to 200-1000Mhz, go back to Stability test and now choose Scaling Stability Test, let it run for 10-20mins, if there are no errors you're good to go.
Play with the phone for few days, if it hasn't frozen go to setCPU 'VOLTAGES' tab and tick at the bottom 'Set On Boot'.
Notice: My recommendation is to set on boot in the end of the process because if you choose a really low MV your phone might be stuck in an endless loop, thus you tick 'set on boot', only, if you are sure your system is stable.
Final Result:
[img=http://imageshack.us/thumbnmail.png]
My voltages (SGS2 Device):
200Mhz – 850mV
500Mhz – 925mV
800Mhz – 975mV
1000Mhz – 1075mV
Notice: This undervolt method is the most aggressiveness method around, if you want the easy way and you have Siyah kernel you can open ExTweaks/STweaks and in the "Undervolting" choose -25 or -50, this will undervolt ALL the frequencies together with minus 25 or 50, if your brave you can try 75.
My method gives you a specific voltage to each frequency, in 200mhz you can have minus 75mV while in 500mhz minus 50mv, this will give you the best undervolt system.​
Continued on next post...

6. Freezing google/Samsung apps using Titanium Backup Pro:
If you didn't buy the app yet, well, you’re an idiot: Titanium Backup Pro or you can use a free substitute (though I never tried it) Root Uninstaller
After you bought the app, open it and go to 'Backup/Restore' tab:
in there, you can see all your apps/games AND system apps, we will be focusing on the system apps.
NOTICE: If you're using CM rom you can skip this step since they did hell of a job in removing all Samsung/Android bloat-ware.
Our main goal is to freeze processes that common users don't use and don't even know they have, I won't write all the list of the apps you should freeze but I will write all the apps you will freeze that are consuming your battery like a *****:
Email 4.0 – this is stock mail full of bugs and infinite loops that go online and check for mail, if you don't have gmail account please use a 3rd party app like AquaMail/MailDroid that will give you minimum bugs for the check interval.
Exchane Service 3.1 – Belongs to Email 4.0
Kies via Wi-Fi – I wouldn't say it consumes your battery but it's an unsecured protocol by Samsung, use a 3rd party app like AirDroid
Maps – If you're not using it FREEZE THIS APP ASAP! If you do use I suggest unfreezing every time you need it and freeze again when you're not using it (sorry).
MAPService – Belongs to Maps.
Samsung Account – Do I really need to explain? (Including all the Samsung hubs and chats and whatever they come up)
SecPhone 1.0 – If you're using a different launcher rather than TW you can freeze it.
Software Update – We don't need it, we flash our ROMS
Street View – belongs to Maps.
Talk – I find that even if I freeze it (gtalk) it's still waking the phone so your choice.
Talkback – Samsung try to overtake Whatsapp.
Wi-Fi Direct & Wi-Fi sharing & Wi-Fi sharing manager – you don't need it.
Of course if you're using stock ROM you have A LOT of freezing to do, you can use this thread and of course this amazing list
Or you can Google for more apps that are safe to remove.
7. Screen Brightness:
If you don't know, the most battery consuming part of the phone is the screen.
Go to 'System Settings -> Display -> Brightness' and choose 'automatic brightness'.
For the users that want to maximize even more (YES WE WANT EXTREME!!) try to lower the brightness as low as you can, 20-30%.
Recently I've noticed that there are new apps that you adjust screen brightness by each pixel and a lot more, you can Google that, but I prefer to be able to see things crystal clear.
8. Accounts & sync:
Everyone is recommending, in order to save battery, to go to 'System settings -> Accounts and sync' and to turn it off, of course it will save A LOT of battery, but, if you have a gmail account and you want to be notified as soon as you get an email,you can't turn it off.
What you can do is:
Hit your @gmail.com account, and 'untick' everything except 'Sync Gmail', this will assure that you will get your emails via PUSH (PUSH is the most battery efficient protocol - at real time):
Don't forget to sync your contacts/calender once in a while or before you flash a rom.
If you don't want to get your emails instantly then remove your gmail account and download a 3rd party app like MailDroid/AquaMail and set interval for every hour or every 4 hours, this will assure that there will be absolute no wakelocks but only every 1 hour or 4 ( as you chose).
If you choose to keep auto sync there is one disadvantage:
If you don't have a good reception 'sync' option will go completely crazy and keep asking to go online and sync your email (since you're on PUSH) but it won't be able to, since you don't have a good reception and it will go like this in an infinite loop till you have a decent reception and as you can already understand while your screen is off, the phone is awake and trying to sync, so keep that in mind.
9. Fast Dormacy - Should/Can I disable it ?
First of all you need to understand that not every network/operator support FD (Fast Dormacy).
My network doesn't support FD thus if I'll disable or enable it, it wouldn't make any different, in fact if you disabled it and you think your battery is now "OMG FUKCING AMAZING" this is just a placebo effect, and yes I am 110% positive.
How do I check if my network support this tweak ?
The user JIMMYMCGEE from xda made an amazing guide you need to follow (in fact it's a video clip - which is easier).
She first explain what is FD and afterwards explains how to check if you have FD and if you do, how it can save you battery.
Follow this guide and all his steps here.
NOTICE: If the app that shows you your network stats (service mode) doesn't work and only opens your dialer, this is what you need to do:
This is the code for the service mode, write it in the dialer:
*#*#197328640#*#*
When you'r in the Service mode screen, hit: Debug screen->Basic Information and here you go, service mode.
Interested in more info regarding FD ? you can read what I have already read in here.
10. Battery Calibration - Should I do it ?
The answer is simple, if you are using ICS/JB you don't have too because every time you charge the battery to 100% all your data and stats are deleted and the service begins to collect info again from the beginning you can read all about it here and here.
As you can see for ICS/JB users it's a myth nothing more.
If your using GB then you do have to calibrate your battery, there are 2 methods:
Charge your phone untill you have reached 100% boot into recovery and delete battery stats ('Advance -> Delete battery stats').
Download battery calibration app and follow the steps that are mentioned in the 'Description' of the app and in the app.
11. Network/operator modem support - How to tell if your modem meet your network standards
CM USERS DON'T USE THIS STEP IT WILL BREAK YOUR RIL AND YOU WILL HAVE NO RECEPTION
Every network/operator support a specific version of modem, this means that if you will use their modem, 90% of the time your reception will be solid without any disconnections, if your modem doesn't support, then you will sure have disconnections which will lead into more battery drains (no receptions=phone will search for antennas even though there is one).
Notice: There is a chance that even though you have or don't have their modem you might have or might not have disconnections (confused ? me too.)
How to check:
Download GetRIL, Open the app and see if your RIL/Baseband (aka modem) is matching, if they are (written in green), your good to go and you can remove the app.
If they are not, here is what you need to do:
Under 'Baseband' you have 'recommended':
You can see that LQ6 & LPB are supporting my network, we will now tap this:
and look for LPB & LQ6, after we found it we will choose it and tap: 'Download & install'.
When your done restart your phone and check again (GetRIL) that now your modem is now supporting by your network, if so, remove the app.
12. Variance:
Play store app: Hit the option touch key and untick - 'Notifications' & 'Google AdMob Ads'
When the 'notification' is on, the app is consistently connecting to the server and checking for new versions.
When 'Google AdMob Ads' is on, the app is always checking your behavior and reporting back to the Google server.
'System settings -> Location services' untick everything.
'System settings -> back up and reset' untick 'Back up my data' and 'Automatic restore'.
NOTICE: I didn't apply this step for my own device since it only saves 5% battery more or less and it's a service I use, think, if you need it or not,
WiFi users: 'System settings -> Wi-Fi -> Advance -> Keep Wi-Fi on during sleep' choose - 'Only when plugged in'.
This will close the Wi-Fi connection when you turn off your screen.
Keep in mind that after you finished using your BT turn it off, since I have specific times I use the BT I use AutomateIt, it's a great app that can control even silent modes.
Don't use Facebook app, it drains your battery the most, instead add a shortcut in the desktop for facebook.com link and go to facebook via this link, it looks exactly the same as the app since Android users don't have a native facebook app yet.
Don't use live wallpaper
Don't use widgets
Don't use Haptic Feedbacks
Never ever use Task Killer or 'Clear memory' - Android has it’s own task killer that works better than your 'decision making' brain.
Screen time out - Don't forget to set it
No reception = major battery drains - use airplan mode.
Use Nova launcher or better code efficient luanchers.
Use ad-blocking app in order to prevent unnecessary network usage in downloading ads, I recommand using AdFree - Open the app and choose: 'Boot Normally' and afterwards choose 'Download& Install hosts', when your done restart your phone.
Always charge your phone untill it shows 100% and charge it only if it is below 20-30%
Automatic Date & Time option -> untick
13. Learning to read the battery graph:
This is the final step, come back to this step after you're done with all 12 steps, reading the FAQ (Post #3) and you lost at least 70% of your battery since you charged it.​
So you’re here, go to 'System settings -> Battery' and hit the graph bar.
At the bottom you can see 'Screen on' and 'Awake' we will focus on these lines.
Our goal is to achieve 100% overlap between these 2 lines, meaning, when the screen is on, the phone will be awake and when the screen is off we don't want the phone to be awake since we don't use the phone (unless we are-downloading a file).
For example if you see a blue line in the Screen on bar I would like to see at the same time the EXACT size and width in the Awake bar if not, that means we have wakelocks so we need to go to step number 2 again and see who is waking up our phone.
It's really hard to achieve a 100% overlap between these 2 bars, even for me.
Example of a minor wakelock (squared in red):
For conclusion:
You need to be able to get a MINIMUM 3 hours screen time (System settings - >battery - >screen) if not, you're doing something completely wrong.
From my experience you can't get more than 3.5 hours screen time over total use of MORE than 24 hours uptime (Maximum up time I got with the phone is 4 days with almost 3 hours screen time and 1 hour of calls.), however, if you play non-stop with your mobile, from the time you unplugged it, you will get more then 4-5 hours screen time EASY over 5-16 hours uptime:
But of course most of the users don't "act" like that and most of them just "lose" battery over uptime when screen is off.
From my vast experience with battery usage, this is it, either your get 3 hours screen time over moderate usage (long uptime-2 days +) or you get 4-5 hours screen time with aggressive use (short uptime-16 hours top).
Don't let anyone tell you different.​
• This is it for now, this thread will be updated with new tweaks and methods every now and then.
• Please, if you have any questions regarding this thread write them in this thread ONLY and don't send me a private msg.
• I love constructive criticism, so if you have any thoughts or you found a mistake (even in my grammer) PLEASE send me a private msg.
Credits and many thanks to:
droidphile – His amazing articles and threads regarding most of my steps, you helped me a lot!
geko95gek – Who inspired me a lot regarding ExTweaks.
JIMMYMCGEE - FD knowledge and guide.
If I forgot anyone please do let me know
If you love this article please do hit the Thanks button and rate this thread 5 stars,also you can hit the "Newsworthy Thread" in the first post if you think this article should get a higher exposure.
If you really appreciate this article you can always buy me some weed - makes me think clearly
Thank you.

FAQ:
Q: Which ROM and kernel you're using ?
A: I am using Wanam ROM (latest version) and Siyah kernel (latest kernel also) CM10.1.3 and Dorimanx 9.41.
After trying all sort of ROM's I can say that the most stable and reliable ROM's are Samsung based ROM's.
I am now recommending CM10.1.3 stable ONLY!
Q: After the tweaking and following your entire guide, does the UI will lag/Games will stuck or freeze/App will run slowly ?
A: Regarding the UI you might feel a little lag (if you were using stock frequencies and voltages) or you might not feel any lag (depends on your launcher), If you install Nova Launcher and use it instead of the TW you won't feel any lag since the Nova launcher is code efficient.
Regarding the apps, you won't feel any lag unless it's a graphic app or design/CAD app (even this is questionable).
Regarding the games, you won't feel any lag in most of the games, I played a lot of games for example Dead Trigger/Galaxy on fire 2/Shadowgun/Samuraio II and few more, I didn't feel any lag or what so ever, though I did feel that the loading steps took 1-2 more minutes.
Q: The most used (or 2nd) most used service/app in BBS is 'AuidoOut', how can I minimize it ?
A: You can minimize the 'Audioout' by unticking: 'System settings -> Sound' , under System, untick them all.
Plus, in the same window click on "Vibration intensity' and put 'Vibrate on screen tap' on the lowest (0).
Q: I keep getting "Shell have been granted superuser permissions" over and over again and it drains my battery, is there a solution ?
A: It's a known problem with SuperUser, install SuperSU give it root permissions via superuser, go to app info of superuser hit "Force Close" and afterwards hit "Disable", now SuperSU will handle your root privilege.
Q: I froze Secphone.apk and now I am having weird issues what should I do ?
A: Obviously you're an idiot since I specifically wrote next to SecPhone.apk: If you're using a different launcher rather than TW you can freeze it.
So don't freeze Secphone.apk if you are using TouchWiz launcher which is the official launcher by Samsung.
Q: How can I tell if my phone is going into Deep sleep and activates the setCPU profiles ?
A: In setCPU go to 'Info' tab and tap 'Time In State', you will find a pie chart, if your a common user-that most of the time his screen is off-, you should see that 200mhz has the biggest chunk, if it's not the case then check BBS what is waking your device.
Q: After installing Gemini App Manager I am unable to install/uninstall any app, what should I do ?
A: You are probably using Screen Filter app, for some reason the install button become unresponsive, disable Screen Filter when you need to install something and enable it again afterwards - Thanks Ryther.
Q: How can I solve BBS wakelocks on the go ?
A: Get in here.
Also, if you have EventLog wakelocks here is the solution:
Download System Tuner. open the app and go to 'Startups' and look for 'Google service framework' and over there disable both 'checkin.EventLogService'.
Be advice EventLogService wakelocks only happens with stock Samsung ROMS.
More to follow.

Great work dude. You gave me some good tips
Sent from my GT-I9100 using Tapatalk 2

gb.yolo said:
Great work dude. You gave me some good tips
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your positive feedback.

Thanks
I can confirm getting about 3~4 hours of screen time at most during 16~24 hours of usage.
I noticed you wrote something about SetCPU working on stock kernel ... in my experience it does not work even if some people claims so.
SetCPU might be able to change between a limited amount of Governors, but setting Min and Max doesn't work even it looks so (I used some other tool to confirm this). I only tried this on rooted Stock GB, but I think it will be the same on ICS.

Does this work on jb rom?
Sent from my GT-I9100 using xda app-developers app

good tips
Thanx

Ben101 said:
Does this work on jb rom?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
It work on any rom

Mittaa said:
Thanks
I can confirm getting about 3~4 hours of screen time at most during 16~24 hours of usage.
I noticed you wrote something about SetCPU working on stock kernel ... in my experience it does not work even if some people claims so.
SetCPU might be able to change between a limited amount of Governors, but setting Min and Max doesn't work even it looks so (I used some other tool to confirm this). I only tried this on rooted Stock GB, but I think it will be the same on ICS.
Click to expand...
Click to collapse
Thank you for confirming though you could get more.
and I didn't say what you wrote, I specifically wrote:
If your kernel doesn't support undervolting move to the next step
Click to expand...
Click to collapse
Ben101 said:
Does this work on jb rom?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I didn't try with JB, but I'd love if you could follow each step and report back with results, in my opinion it should be the same.
soso_soso said:
good tips
Thanx
Click to expand...
Click to collapse
Thank you for the feedback, please do try all the steps and report back for success.

great tutorial, thank you for your effort!
I followed the steps but I can't find this one in LBE security:
"c.After your done go to the first window (swipe your finger right to go to the first screen)
d.Choose 'Speed boost -> Auto-Start' you will see all the apps that will be put in the cached process EVERY restart you make to your phone, now, this is very important, I only say it once, if you see an app/game that you don't even use or use once a week 'Disallow' it, but if you see an app/game that you use most of the time leave it as it is, why ? Obviously you didn't read step number 1.
"

trikpa said:
great tutorial, thank you for your effort!
I followed the steps but I can't find this one in LBE security:
"c.After your done go to the first window (swipe your finger right to go to the first screen)
d.Choose 'Speed boost -> Auto-Start' you will see all the apps that will be put in the cached process EVERY restart you make to your phone, now, this is very important, I only say it once, if you see an app/game that you don't even use or use once a week 'Disallow' it, but if you see an app/game that you use most of the time leave it as it is, why ? Obviously you didn't read step number 1.
"
Click to expand...
Click to collapse
Thank you for your positive feedback, please do come back with results and post them here.
As you can see in the picture, this is the first screen you see when you open up LBE,2nd raw is 'Speed Boost' just click it and it will show you new buttons, there you choose 'Auto-Start.
EDIT:
I have added pictures to the main thread for most of the steps and marked in red the specific step.

I got confused because in my app it says phone accelerate instead of speed boost
anyway, I'm using these mods since this morning so it is too early to say anything factual about battery life, but I think it is much better...
usually I would have about 60 or less % left at this time of day...

trikpa said:
I got confused because in my app it says phone accelerate instead of speed boost
anyway, I'm using these mods since this morning so it is too early to say anything factual about battery life, but I think it is much better...
usually I would have about 60 or less % left at this time of day...
Click to expand...
Click to collapse
Perhaps you downloaded even newer version than mine but I can see you figured it out.
If you used to get 60% and now it's 76%, of course this is an amazing change.
Don't forget to check your screen time before you charge it and make sure it's minimum 3 hours (if the total up-time is above 24 hours).
If you did follow all the steps and did everything as I wrote, I suggest to get into Recovery mode -> Advance -> and reset battery indicators.
or wait 1-2 charges and the battery meter is supposed to acclimate.

hyperbolic said:
From my experience you can't get more than 3.5 hours screen time over total use of MORE than 24 hours uptime
Click to expand...
Click to collapse
Well is that so?

Nice thread, but Gemini app manager block on "updating information" sometimes :x

MrMarques01 said:
Well is that so?
Click to expand...
Click to collapse
I saw really few users like your self that actually got that time, but I had never got more then 3.5-4 hours max screen time on uptime for more then 24 hours.
I even did EXACTLY what these users told me with their exact config (from 3 different users) but again, I got only 3.5-4 hours screen time max.
So this is my conclusion.
Kigsuha said:
Nice thread, but Gemini app manager block on "updating information" sometimes :x
Click to expand...
Click to collapse
Thank you.
Yea that's an annoying bug that is happening from time to time.
Just exit the app and open it again.

hyperbolic said:
I saw really few users like your self that actually got that time, but I had never got more then 3.5-4 hours max screen time on uptime for more then 24 hours.
I even did EXACTLY what these users told me with their exact config (from 3 different users) but again, I got only 3.5-4 hours screen time max.
So this is my conclusion.
Thank you.
Yea that's an annoying bug that is happening from time to time.
Just exit the app and open it again.
Click to expand...
Click to collapse
I found solution, it only happens when after taping "config autorun (root)" and switching fast thing to off.
So i have to wait :cyclops:

Kigsuha said:
I found solution, it only happens when after taping "config autorun (root)" and switching fast thing to off.
So i have to wait :cyclops:
Click to expand...
Click to collapse
Sometimes you just wait for too long but if you have patience for that..

hyperbolic said:
Last update:29/9/12
[*] If after step b&c your phone is still working that means that the undervolt you chose is working great. (
Click to expand...
Click to collapse
hyperbolic what do you mean by step b&c ?
There just core1 sucessful
core2 sucessful
Ram sucessful

[GUIDE] Tips for Getting the Most from Your Custom Kernel

These tips are based in my study and experience of using different programs and techniques to get solid and stable performance from custom kernels. It's a long read, but a good read if you really want to minimize heat and maximize performance. This information works on any custom kernel that can be used with Synapse. This guide is aimed at beginner and intermediate users who are interested in custom kernel settings but don't know where to start. These are the most commonly optimized settings on Android.
***DVFS Rule #2 is exclusive to Samsung devices (so if you don't have a Samsung device don't use it!)***
Rule 1: What works for some won't work for others - This has always been the most important rule of custom kernels. One person using Barry Allen governor, overclocked to 3.07 GHz, and not using intelliplug will never hit 70C while your phone using those same settings might immediately cause the phone to reboot. All synapse changes made to a device must be tested by you to ensure compatibility for your hardware. Some of you may be curious, if this is the case, why Google would have everyone use the interactive governor by default? I would respond to you that they originally assigned everyone to OnDemand while they worked to make a better and more compatible Interactive governor. But as you know there are a LOT of governors out there and knowing what is best for your device is to read and to test it. The good news is that once you find something that works well you can stick with it as long as you own the device.
Rule 2: DVFS (Dynamic Voltage and Frequency Scaling) Disabler - This is mentioned in a few threads, but requires a repeat. Samsung uses DVFS to contol your CPU frequencies and voltage levels. This isn't an issue when you're running a stock kernel because it works in conjunction with MP-Decision to decide on the proper frequency level. When you're running emotion kernel you don't want DVFS to control anything. You want it to let Faux's Intellithermal work together with the kernel routines to shut down cores it doesn't need.
R2 Part 1: If your phone is running hot: Install Xposed, download Wanam Xposed (enable the module), Open Wanam, click "Advanced" menu, Uncheck "Enable TouchWiz DVFS" and reboot.
R2 Part 2: Following the reboot open Synapse, scroll over to CPU Drivers scroll down and put a checkbox in "Enable Intelli-hotplug", leave the rest alone, and click the check mark at the top of the screen to save changes. Scroll over one more screen to "Thermal" and put a check in the box, "Enable or Disable Intelli Thermal Control" and leave the settings below as they are unless you know what you are doing.
Note: The phone will be still be warm for awhile, but if you give the phone a break and allow the heat to dissipate it should run cooler and more consistently with the added bonus of shutting down 3 out of the 4 cores unlike MP-Decision which always leaves 2 cores live. After doing this if you are noticing performance loss or stuttering it's time to find a new governor that makes the most of these settings. Which leads me to Rule 3....
Rule 3: Choosing a new governor - This part is going to require some reading on your part, but I can assure you that it is worth your time. This guide http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957 by @gsstudios is OUTSTANDING (please thank him while you are there) and carries a LOT of information about the governors and other performance informations. So find something you like from the guide descriptions to try out and leave it in place for 24 hours or more as long as you aren't experiencing excessive lag or reboots. If it performs well under normal usage the next step is to watch battery life. There won't be a single governor that does everything perfectly, but finding something that fits your needs is key. And it's OKAY if you decide to stick with Interactive, it is a very well made governor and many are based off of that design, but I equate it to finding a good pair of shoes. Lots of things will protect your feet from the ground, but shoes that you enjoy and work well make all the difference in the world.
NOTE: You can use Antutu for stability testing but do not pick a new governor and then run benchmarks and expect top score unless you chose the performance governor. Antutu specifically maxes out your device voltage and frequency to see what the device can handle which is not what intelliplug is for. If you are following this guide benchmarks are the least of your concerns.
Rule 4: Don't forget your Scheduler - Believe it or not, everything runs off of your phone storage. So using an optimized scheduler for you device could make great strides in battery and performance improvements. Unlike choosing a governor, you can absolutely benchmark your flash memory to find out which scheduler works best for you. I only use one and I am going to shamelessly plug it here: I use Android Tuner to benchmark my flash speed with different schedulers and it works great for me. How it works:
Note:To help with choosing where to start with schedulers you can use the guide I linked to above which will give you an idea of what to use. That guide has an exceptional amount of information about how these types of schedulers work and what you should use for getting what you want from your phone. What follows is my advice for testing benchmark write performance and those steps are completely optional, but it never hurts to see how your device does with your chosen scheduler.
R4 Part 1: Launch Android Tuner, from the main menu accept root, acknowledge that root is powerful, scroll all the way to the far left screen, choose "SD Card Read Speed", click "Benchmark in the center, and then notice at the top you have /storage/emulated/0 which is your faster internal memory (which you should optimize first) and then /storage/ExtSdCard which you can benchmark second.
R4 Part 2: When you are ready to benchmark choose your "I/O Scheduler" from the drop down menu and click "Run". Your results will be listed with the fastest read-ahead size on the left and the speed at which it read on the right. Higher = Better -- Then you would choose the other test size (10MB in my case) and you see which readahead value is the fastest for those files. If you manage to get a readahead that the 100MB and 10MB test highest values are the same, then you've won the lottery. Since that is almost impossible try to remember what your top 5 fastest are and choose the one that performs well in both tests. If you want to keep testing and check other schedulers for raw read speed just switch them at the top and re-run both tests.
After you've found which scheduler gives you the performance you want, go back to Synapse, scroll to "I/O" tab, and adjust pick your scheduler and readahead value, and finally click the check mark to apply it.
Rule 5: Undervolting (IMO) does more harm than good - I'll let you Google it but it follows the rule of diminishing returns. You might be running Synapse and are able to undervolt 75mV and still cruise through menus and apps like it's no problem. But I promise you at some point the CPU is going to call for that voltage you starved it of and it will reboot. It's not a matter of if it will happen, but when it will happen. This comes down to your personal silicon and I do not recommend undervolting at all. Other more advanced users may disagree with me, but for the average user there are better ways to save battery and negate heat than starving your CPU and GPU at a kernel level. Especially with DVFS disabled.
And that's all I have for you. These tips work for any custom kernel that uses Synapse to manage their settings. I've personally test my setup with Emotion and the kernel we are not to speak of on XDA. If you like the idea of getting the most out of your device then a custom kernel might be for you, but it requires a lot of patience. If you just need something that works I definitely recommend the stock kernel because they really did a good job with the Lollipop release of our kernel.
I hope this helps some of you and I hope that everyone can take something away from this guide. Feel free to let me know if this helped you in some way or if you need some guidance on the topic. I'll do my best to backup my claims with proper research and documentation.
Thanks
Google - For research help and a great phone OS
Linux - The foundation of this OS
gsstudios - For his outstanding guide and work on researching this information (Definitely hit 'Thanks' on his post)
Note 4 ROM and Kernel Devs - we are very lucky to have a lot of great devs for our device; their work is appreciated and gives me something to write about
XDA and their members - where I've learned most everything about one of my favorite operating systems

Ho to get your battery life back.

Dear OP2 friends,
HUGE DISCLAIMER:
Below setup works for MY use and needs. If you are like me it will work for you too, if not go find information somewhere else and don't complain "I cannot get the same results" or things like that. It takes common sense and experience to achieve and understand below info. If you don't have common sense, I pity you, if you don't have experience it's OK. If you are polite and follow the XDA rules I don't mind answering your well structured questions, and maybe others don't mind too, there are a lot more experienced people on XDA than me.
If your question is related to any of the apps/threads mentioned below, please go to that (app) thread, that's why I have put the info right there, one click away.
battery life is something we all want to be endless, well we can't have that, but at least we can improve it from a certain point.
This is what I have been doing for the past weeks and the results are incredible, that's why I decided to share them.
First of all sharing this information is ambiguous because it's somewhat device and user dependent especially how people use it and what apps are installed.
I know that but I believe with the right approach you can get the same results as me, hopefully even better, on the OP2 and possibly other device as well.
I have 148 apps installed at the moment and sometimes even more than 200. If you control your apps properly there is no limit to the amount of apps installed related to battery life.
There are numerous threads on improving battery life out there already so please check out those threads first.
Extreme battery threads:
https://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
https://forum.xda-developers.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588
You can also post your BBS logs there, please don't do that in this thread as I will not investigate them.
Most useful info is already out there so I would appreciate it to go look there first before cluttering this thread. If not I will close this thread.
Let's get started:
improving battery life on Android is (unfortunately) always a combination of things, there is no 1-push button (yet).
In this case I use the following:
- privacy guard (baked in almost any Nougat ROM)
- custom kernel (I use Boeffla: original thread here, I use the Linaro version from ZaneZam)
- Greenify (original thread here)
- Wakelock blocker (built in ROM) + WakeBlock app (optional, original thread here)
- Alarm Blocker (built in ROM)
- Doze apps
- BetterBatteryStats (for finding your excessive wakelocks, thread here)
Obviously you have to be rooted to implement all of this.
The ROM of my choice is RR unofficial.
I like it because of the functionality and features but I believe any ROM with the above features should be able to achieve the same results.
Speaking of results, below screenshots are from my last cycle before writing this thread. One charge got me almost through 3 full days (66 hours).
I fully charged in the afternoon, got through the evening and the first night, then got through the full second day and night, then got through another full day and night and charged only again in the next morning.
If your still following, those are 66 hours of straight juice...
EXPLANATION: There is ALWAYS a tradeoff between SOT (screen on time) and how long your battery will last in one cycle. On my below cycle you can see that I have "only" 4 hours of SOT but almost 3 days of battery life. That is light usage.
If I would use my phone more (more SOT) the battery life cycle would have been significantly shorter. If you complain to me that you "only" have 24hrs of battery life but you show me a SOT of 7-8 hours, I would consider that great battery life! It's all relative...
I have never used one battery cycle from 100% to 0% in one go so I don't know the max SOT I would get with my setup. I would guess around 6.5-9 hours depending on the activity (gaming <=> ebook reading, mobile data <=> wifi, ...). It's all relative...
The screenshots in the bottom of the post might bring clarity for you.
See the following posts for more explanation.
Thanks to:
@nicesoni_ash
@Lord Boeffla
@ZaneZam
@oasisfeng @GioBozza @chamonix
@ssrij @The Peterle

Privacy Guard:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I enable this for all user apps because I don't want any app keeping the system awake. I even have this enabled for some system apps like:
Calendar storage
Google play services
Google play store
Google app
cLock
I mostly disable all locations (if it's not a location dependent app), keep awake, run in background and even start at boot (if the app doesn't need to start on boot) toggles.
Again, use your common sense to figure out if a app needs to run on boot (for example, youtube doesn't need to run on boot, tasker does for starting up along with the system boot).
obviously some system apps need to run in the background for example cLock or calendar storage otherwise your weather and calendar will not update...
You can also configure all the apps on a gradual basis. You let the privacy guard as is on clean install an if you see excessive wakelocks from a certain app, you start blocking it one by one.

Custom kernel:
I use Boeffla config app with always the latest version of his kernel compiled by ZaneZam (Linaro 6 version).
The latest as of the time writing this thread is LOS14.1-beta14 in combination with config app 2.4.34.
I use profile IMPULSE TUNED V3.0, no lags, good performance and crazy battery life.
Screenshots of my minor changes, the rest is identical to the stock IMPULSE TUNED V3.0 profile.

Greenify:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I Greenify a lot of apps, as much as I can basically, even system apps.
I cannot give too much advice on this part so please go to the Greenify thread to ask related questions. For me it's mostly a hit and miss and right now my config is a big hit.
If you want to know if you can Greenify a particular app you can ask me.
Configuration below in screenshots.

Wakelock Blocker (+ WakeBlock app):
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I personally think this feature is essential in getting good battery life so I'm glad it's integrated in the ROM of my choice (since we don't have xposed yet).
In combination with the WakeBlock app it basically works like Amplify on Xposed, but ROM integrated.
This part is the hardest to explain because it's different for most users. On the screenshots below you can find most of my blocked wakelocks (without losing functionality).
The procedure to block wakelocks is the same as all the other parts explained above and below:
Let your system run for some hours/days (essential!).
After that, trough BBS you can find your excessive wakelocks and through wakelock blocker you can block them completely. If you don't want to completely block the wakelocks you can use the WakeBlock app to put a timer like in Amplify for Xposed, for example I want wakelock x to run every 9999 milliseconds....

Alarm blocker:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
Another essential feature for keeping your device under control.
I block a lot of alarms (without losing functionality) so get ready...

Doze apps:
I use Force Doze from the Playstore to put my device in Doze mode as soon as the screen goes off.
Naptime is an alternative but I find it to generate too many wakelocks (sometimes up to 19 per hour).
I might change this app once in a while if there are better alternatives that come up.
Anyway Force Doze will work for now.

reserved. will add some advices.

CounterC said:
Doze apps:
I use Force Doze from the Playstore to put my device in Doze mode as soon as the screen goes off.
Naptime is an alternative but I find it to generate too many wakelocks (sometimes up to 19 per hour).
I might change this app once in a while if there are better alternatives that come up.
Anyway Force Doze will work for now.
Click to expand...
Click to collapse
Lesser wakelocks means not necessarily lesser drain, good example is definitely the very first lines from this Thread of an old friend from galaxy s3 lte times, he implemented microG on his device and achieved lesser wakelocks but no significant impact on his battery life(see here), what I want to point out is that this equation (more wakelocks - more battery drain) isn't so simple unfortunately, even if true for most of the time, regarding to franco's naptime, I personally made very good experience with this app in combination with his custom kernel, I think especially in this combination it's absolutely recommended..
Furthermore some inspiration about battery life a wonderful guide with plenty of useful information, the absolute majority is generally valid, so don't get confused by the i9305 tag...
Sent from my OnePlus 2 using XDA Labs

Sam Nakamura said:
Lesser wakelocks means not necessarily lesser drain, good example is definitely the very first lines from this Thread of an old friend from galaxy s3 lte times, he implemented microG on his device and achieved lesser wakelocks but no significant impact on his battery life(see here), what I want to point out is that this equation (more wakelocks - more battery drain) isn't so simple unfortunately, even if true for most of the time, regarding to franco's naptime, I personally made very good experience with this app in combination with his custom kernel, I think especially in this combination it's absolutely recommended..
Furthermore some inspiration about battery life a wonderful guide with plenty of useful information, the absolute majority is generally valid, so don't get confused by the i9305 tag...
Click to expand...
Click to collapse
Good point Sam, that's why I always say check BBS first if it's actually a wakelock, then treat it properly (disable or time-lapse it).

Overnight drain

does blocking the *alarm* wakelock cause the system to reboot!?

aditya_pan said:
does blocking the *alarm* wakelock cause the system to reboot!?
Click to expand...
Click to collapse
No, not with me.