Database Users

Battery Optimized on S3 with Siyah Kernel - Galaxy S III General

Battery Optimazatin
Disclaimer alert: I am in no way responsible for any damage inquired while performing any of the changes listed below. This is just an option and it is something I have tried on S3 i9300 international version with success. Results will vary depending on your device
I have NeatRom Lite v1.1 + Siyah Kernal installed on my phone. Samsung's stock kernal has been replaced by Siyah's kernal SGS3v.1.8.4. To tweak the kernal, I installed STweaks (from the market).However if you feel bold you can tweak the kernal using STweaks and also tweak the governor (I am using peqasusq as my defualt governor). Additional tweaks for performance and gamers are avaliabe to Siyah S3 i9300 thread (http://forum.xda-developers.com/showthread.php?t=1709686). Governor tweaks can be performed either via a script in init.d or by SetCPU. I assume kernels with peqasusq can be tweaked with the settings below ( have not tried it out yet). These are my settings below ( they are by no means a rule of thumb). Note if you experience reboots while UV CPU ( try -50Mv or -75Mv).
STweaks settings can now be saved using a STweaks Profiles app by Droidphile (http://forum.xda-developers.com/showthread.php?t=1179809)
Battery Saving Tips
The screen causes excessive battery drain. You will need to reduce your screen brightness to about 30-40% instead of being at automatic.
Disable hepatic feedback
Use a dark back ground. Using a live wall paper wil also drain your battery
Turn WiFi off
GPS or location by network off ( use GPS only when needed)
There are other factors that affect battery consumption on your phone, these includes AutoSync Mail, apps like facebook, Whatsapp, Google + and Maps. You can disable auto sync feature for your gmail or get a better email app. Autostarts App can be used to disabe certain apps from autostarting. Cautiously disable apps, if in doubt don't touch it.
To get an idea of what is causing battery drain (Wakelocks), I suggest downloading Better Battery from the play store (Paid app) and view a dumpfile after 1-4 hours of your phone on idle. Once you have BBS you can determine what you want to disable or enable. If you need additional help reading the file you can head over to BBS thread (http://forum.xda-developers.com/showthread.php?t=1179809)
How to use Autostarts
Once you have this app, you can prevent some of the programs/operations from auto starting even when not in use.
Select the meu option and choose group by application
You can go down the list of apps and disable the notorious apps that you find running during auto starts (Maps, Google+, Facebook, Whatsapp). Here is Karpfenhai's example of how to disable Maps.
I have also disabled apps that auto start when connection changes, power disconnections. Disable apps or background operations can be enabled anytime.
Please note, some might cause havoc when disable do this with caution.
STweaks Settings
Quad Core Setting
SETTINGS (CPU):
CFS (Settings) GENTLE_FAIR_SLEEPERS = On
CPU IDLE Mode = IDLE+ LPA (default)
SCHED_MC = 0
CPU Undervolting = -100mV ( -75 if your phone freezes or reboots)
Max CPU Lock = Quad Core mode
Default CPU Governor = pegasusq
Scaling Max Freq = 1200Mhz
Scaling Min Freq = 200Mhz
SETTINGS (GPU freq):
GPU Freq Step 1 = 108Mhz
GPU Freq Step 2 = 160Mhz
GPU Freq Step 3 = 266Mhz
GPU Freq Step 4=300Mhz
GPU Freq Step 5=333Mhz
SETTINGS (GPU voltages):
GPU Voltage Level 1 = 825mV
GPU Voltage Level 2 = 850mV
GPU Voltage Level 3 = 875Mv
GPU Voltage Level 4 = 900mV
GPU Voltage Level 5 = 925MV
GPU Thresholds
GPU Threshold 1 Up = 70
GPU Threshold 2 Down =60
GPU Threshold 2 Up=70
GPU Threshold 3 Down=55
GPU Threshold 3 Up=80
GPU Threshold 4 Down=65
GPU Threshold 4 Up=80
GPU Threshold 5 Down=75
SCREEN
Touch Boost Level =600MHz (If there is lag try 700MHz)
Default CPU Scheduler = sio/Deadline
Init.d Tweaks
echo "80" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold
echo "60000" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate
echo "2" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor
echo "5" > /sys/devices/system/cpu/cpufreq/pegasusq/down_differential
echo "10" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_step
echo "10" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_up_rate
echo "20" > /sys/devices/system/cpu/cpufreq/pegasusq/cpu_down_rate
echo "300000" > /sys/devices/system/cpu/cpufreq/pegasusq/freq_for_responsiveness
echo "50" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold_at_min_freq
echo "400000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_1_1
echo "300000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_2_0
echo "400000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_2_1
echo "300000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_3_0
echo "1000000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_3_1
echo "400000" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_freq_4_0
echo "150" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_1_1
echo "150" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_2_0
echo "250" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_2_1
echo "200" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_3_0
echo "400" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_3_1
echo "300" > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_rq_4_0
echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/io_is_busy
echo "0" > /sys/devices/system/cpu/cpufreq/pegasusq/max_cpu_lock
note script is only for quad core settings, if used for dual core may cause fast battery drain
Click to expand...
Click to collapse
Dual Core Settings This will should give you more battery savings
SETTINGS (CPU):
CFS (Settings) GENTLE_FAIR_SLEEPERS = On
CPU IDLE Mode = IDLE+ LPA (default)
SCHED_MC = 0
CPU Undervolting = -100mV ( -75 if your phone freezes or reboots)
Max CPU Lock = Dual Core mode
Default CPU Governor = pegasusq
Scaling Max Freq = 1000Mhz
Scaling Min Freq = 200Mhz
SETTINGS (GPU freq):
GPU Freq Step 1 = 108Mhz
GPU Freq Step 2 = 160Mhz
GPU Freq Step 3 = 200Mhz
GPU Freq Step 4= 266Mhz
GPU Freq Step 5=300Mhz
SETTINGS (GPU voltages):
GPU Voltage Level 1 = 825mV
GPU Voltage Level 2 = 850mV
GPU Voltage Level 3 = 875Mv
GPU Voltage Level 4 = 900mV
GPU Voltage Level 5 = 925MV
GPU Thresholds
GPU Threshold 1 Up = 70
GPU Threshold 2 Down =60
GPU Threshold 2 Up=70
GPU Threshold 3 Down=55
GPU Threshold 3 Up=80
GPU Threshold 4 Down=65
GPU Threshold 4 Up=80
GPU Threshold 5 Down=75
SCREEN
Touch Boost Level =600Mz (If you experience a lags try 700Mhz)
Default CPU Scheduler = sio/Deadline
Click to expand...
Click to collapse
Images
{
"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"
}
Special thanks to
Siyah for the kernel
Droidphille for correcting my initial governor tweaks
Sale for Neat Rom
Click to expand...
Click to collapse

I prefer to sell my phone and go through all this hassle
Sent from my GT-I9300 using Tapatalk 2

tarif said:
I prefer to sell my phone and go through all this hassle
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
It is really not as bad as you think. Give it a try

I will try it in a while and will post how it goes. Thanks mate. Keep up the good work

Thx for this interesting post ...but instead of just Uv all frequencies I did uv on each frequencies manually and stress it with set cpu to see if its stable for example im runing 1.4Ghz at 118750mv and can go up to 1.6 Ghz at just 126200mv very stable since I did 25min of stress test on setcpu and since 2days im runing at this speed with that voltage with no problem at all and of course with Siyah kernel
If you guys are interested and I can post all my current voltages at each frequencies
Cheers
Sent from my GT-I9300 using xda premium

G4neStarT said:
Thx for this interesting post ...but instead of just Uv all frequencies I did uv on each frequencies manually and stress it with set cpu to see if its stable for example im runing 1.4Ghz at 118750mv and can go up to 1.6 Ghz at just 126200mv very stable since I did 25min of stress test on setcpu and since 2days im runing at this speed with that voltage with no problem at all and of course with Siyah kernel
If you guys are interested and I can post all my current voltages at each frequencies
Cheers
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
The good thing about this thread is that it is created to share ideas. So feel free to share your settings with everyone. I stressed mine using glbench mark from google play. This settings seemed to work out well without any crashes or SOB . Siyah uses a different mehod so the UV values are not set on boot up. However, the new kernel has the option of uv for any step you want at boot.
Sent from my GT-I9300 using Tapatalk 2

Thanks mate
Enviado desde mi GT-I9300 usando Tapatalk 2

Hi I tried the settings you said above with Siyah 1.8.6 but the phone warmed too! very much! to just use WhatsApp or Kik messenger programs that are not demanding much processing.
I went back to the settings of Stweaks defaut and everything returned to normal.
As for the expense, I have 24 hours of use, 3 hours of screen and 34% of battery.
Very good too, right?

hooliganx said:
Hi I tried the settings you said above with Siyah 1.8.6 but the phone warmed too! very much! to just use WhatsApp or Kik messenger programs that are not demanding much processing.
I went back to the settings of Stweaks defaut and everything returned to normal.
As for the expense, I have 24 hours of use, 3 hours of screen and 34% of battery.
Very good too, right?
Click to expand...
Click to collapse
Strange but I didn't get any of that with my phone. Which of the settings did you use?
Sent from my GT-I9300 using Tapatalk 2

Hi Red Hat,
I'm not having a go (I'm a fellow red), and I know you're trying to help, but steps 1-5 are all complete non starters for me.
What's the point in buying a phone like this if you're going to turn off a bunch of the best functionality? Might as well go and buy something cheaper that doesn't have those functions...

seems a hell of a lot of hassle to go through to get worse battery life than i get at the moment. Just use a stock rom with siyah set at lulzactive and deadline profiles gets me 1d 7 hours with 5 hours screen time. Fine for me.

To avoid this hassle I have bought a spare battery.
Sent from my GT-I9300 using xda premium

skimminstones said:
seems a hell of a lot of hassle to go through to get worse battery life than i get at the moment. Just use a stock rom with siyah set at lulzactive and deadline profiles gets me 1d 7 hours with 5 hours screen time. Fine for me.
Click to expand...
Click to collapse
Ok guys, I am sharing my findings and what I have done to obtain good battery life. This is not a standard or a rule of thumb. For starters, I use my phone a lot and can barely get through a 24 hour day without a needing a charge. So I came up with this and it worked well for me. This is based on what I read from Droidphile and sample from Siyah kernel's battery tweaks. This is my second thread on the issue and it worked well on S2. If you are getting better battery life please share with the rest of us as it will only enable others and myself to learn.
Thanx for the feed back.
Rabangus said:
Hi Red Hat,
I'm not having a go (I'm a fellow red), and I know you're trying to help, but steps 1-5 are all complete non starters for me.
What's the point in buying a phone like this if you're going to turn off a bunch of the best functionality? Might as well go and buy something cheaper that doesn't have those functions...
Click to expand...
Click to collapse
Functionality wise the phone does the same thing it did when I purchased it. Using autostart allows you to stop programs that run in the back ground without when you don't need them. Think of it as an extra hall monitor
Sent from my GT-I9300 using Tapatalk 2

Ehm ehm..! Excuse me!!
I don't know why your guys feeling like getting a good battery life is difficult in this awesome device!
Ultimate rom 7.1 with persues kernel thats all! Nothing much or less than this.
Sent from my GT-I9300 using xda premium

To all my friends wishes of a Happy, Healthy, Successful and a Peaceful New Year

skimminstones said:
seems a hell of a lot of hassle to go through to get worse battery life than i get at the moment. Just use a stock rom with siyah set at lulzactive and deadline profiles gets me 1d 7 hours with 5 hours screen time. Fine for me.
Click to expand...
Click to collapse
wanam's deodexed stock+siyah set with with lulzactive (using droidphile's script) and deadline had given me 2-3% discharging during 11-12 hours sleep whilst any operation resulted in quicker battery drain. With same settings incroporated to Ultima 7.1 the operation-time battery drainage seems to be slowed down with same deep sleep drain.

Will it work well in cm10.1?
Enviado desde mi Tamagotchi usando Tapatalk

kylesinho21 said:
Will it work well in cm10.1?
Enviado desde mi Tamagotchi usando Tapatalk
Click to expand...
Click to collapse
It should work as long as you are running a Siyah kernel (for the stweaks setting) or pegasusq governor. Please try it and post it your results.
Sent from my GT-I9300 using Tapatalk 2

thanks you man!! i'll try it!! :good:

thekoRngear said:
wanam's deodexed stock+siyah set with with lulzactive (using droidphile's script) and deadline had given me 2-3% discharging during 11-12 hours sleep whilst any operation resulted in quicker battery drain. With same settings incroporated to Ultima 7.1 the operation-time battery drainage seems to be slowed down with same deep sleep drain.
Click to expand...
Click to collapse
is there a reason you're quoting my post while saying this?

Related

Right i am not going to bore you with long ass intros or long essays on how to do this and how to do that. All i did was share my results on a thread and people started messaging me about my settings and what configurations i use. So i will make it all simple for you. I am opening a thread so you can see what settings i am using and use it as a guide and adjust them or use my own settings if you want to get the best out of your battery and enjoy more your baby. Plus this thread is for you guys to stop private messaging me as i am getting loads of messages and hardly have time to reply to you all.​
First off and call it a disclaimer if you want, what WORKS on my phone might not work for yours. So as i said above, use my settings if you want, but if you have problems then tweak them to an effect your phone runs smoothly. Infact with my settings you get the balance of both worlds, Performance and battery life. But let me say this i am just providing you guys with my settings and what works for me. Now if you get any problems or errors which you should not do not come here crying as i have not forced these settings on anyone. The below settings are for people like myself who do not know how to use a script to tweak a governor, and by having this app makes life a lot easier and by me helping with my settings i hope it can provide the balance of good battery life and performance to people.
I know Geko95gek has his MagicConfig thread and my thread is different to his, as my thread is just to help people with the Lulzactive app settings and give them a guide on how to start and use it and how to get the best out off it. His is more to do with voltages of cpu and GPU. You can use his MagicConfig and use my Lulzactive apps settings if you want. Big shout out to him for his magic.
Please also follow the bottom link for a bit more in depth info on a How to guide for undervolting.(many thanks to Eric-filth)
http://forum.xda-developers.com/showthread.php?t=1532999
Anyway here are the settings that i use and please use as a guide:
Lulzactive app Settings:
inc_cpu_load: 75%
pump_up_step: 3
pump_down_step:2
screen_off_min_step: 4,@200MHz
up_sample_time: 50000
down_sample_time: 30000
debug_mode: 0
Setting up your Lulzactive app with your configurations:
To be able to use the above settings as already stated you need the Lulzactive application were it can be found here:https://play.google.com/store/apps/details?id=com.tegrak.lulzactive&hl=en.
Once you have installed it then you need to have Voltage Control which i recommend or any other cpu tuner program installed on your phone like(SetCpu, NoFrills, Tegrak OC) to be able to set lulzactive governor as default.
Once you have done that then go ahead and input my settings or your own. The exact way i have it laid out, is the same on the app.
Once you have done inputting the settings always make sure you have SET ON BOOT ticked.
Come out of the app and reboot. Wait for the phone to load up properly then go back into the application to make sure the settings have been set up properly and stayed. And that is it. :
​
Voltage Control Configuration:
*Governor: Lulzactive (of course)
*Scheduler: VR - Noop
Voltages​
1200Mhz - 1150mV
1000Mhz - 1050mV
800Mhz - 1000mV
500Mhz - 950mV
200Mhz - 900mV
100Mhz - 850mV​​
GPU Control​Low power state - High power estate​114Mhz - 950mV / 267Mhz - 1050mV​
Now i will present to you settings that you can use with a different governor and scheduler. Call this Rock Solid Config v1.1 if you like.​
Voltages
1200Mhz - 1175mV
1000Mhz - 1100mV
800Mhz - 975mV
500Mhz - 950mV
200Mhz - 850mV
100Mhz - 850mV​
GPU Control:​Low Power state: 133Mhz - 900mV
High Power State: 267Mhz - 1000mv
Scheduler: Noop
Governor: Conservative
Misc Tweaks: Ext4 Boost- Sched_Mc​
So there you have it. Those are my settings that i use currently with NEAK kernel and work like a charm for me. Feel free to use my configuration if you like but please consider that everyones phone is different. So feel free to use mine as a guide and either feel free to undervolt more if you like or if you find that you are getting freezes then up the steps by either 25mV or 50mv
Feel free to post your results here as i would like to know if my settings work or not and also your battery results to show if my settings actually do something towards your battery.
Just a few thanks in order as well i think:
Simone201: for his awesome kernel and configurator.
Tegrak: For his awesome lulzactive app(makes my life alot easier to tweak it this way instead of scripts)
Gokhanmoral: just for his siyah kernel and i have all the time in the world for that guy as he is a legend in my eyes
Geko95gek: for being just a crazy ass Yoda and providing everyone with his MagicConfig
GC and LeoMar75: For the awesome rom
So_ony: cause i have to say it was her idea behind this brainchild of a thread.
Droidphile: For his awesome thread regarding all the information you need regarding kernels
And to you all who keep pestering me for my settings this thread is for you guys.

Information on misc tweaks, plus my favorite governors and schedulers i recommend
Abit more info regarding what are the misc options in the NEAK configurator application. (Many thanks to Droidphile for all the information)
Q. "What are these modes: IDLE, LPA and AFTR?"
A. Between screen off and deep sleep states, there are some idle modes supported by cpuidle driver. They are IDLE aka Normal Idle, LPA aka Deep Idle and AFTR aka ARM Off Top Running. Race to idle by CPU is implemented for power management.
In IDLE state, CPU is not clocked anymore, but no hardware is powered down.
In deep idle (LPA),a state after IDLE, again, the cpu is not clocked anymore like we guessed but some parts of hardware are powered down. Deep idle brings in real power savings and there is no need of putting a hard limit to frequency during screen-off; using a screen-off profile. (Good practice is to use a governor with built in screen off profile, than using an user-configured screen-off profile by putting a hard limit on frequency). Deep idle is not used when device is entering deep sleep and also when device is woken from suspend/deep sleep. While entering/exiting DEEP IDLE, CPU is set statically to SLEEP_FREQ and is not clocked below or above until it exits this state.
AFTR is a patch to support Top=Off mode for deep idle. Level 2 cache keeps it data during this mode.
We can have IDLE or AFTR modes with LPA enabled or disabled. (Obviously it is not possible to have IDLE and AFTR together)
Values:
0: IDLE
1: AFTR
2: IDLE+LPA
3: AFTR+LPA
Q. "What idle modes are recommended for power saving? How do i change it"?
A. Recommended for power saving is to enable AFTR and LPA, ie value 3
Example:
echo "3" > /sys/module/cpuidle/parameters/enable_mask
Q. "What is sched_mc?"
A. Linaro team invented sched_mc or Schedule Multi Core to make process scheduling multi-core aware. ie, utilize both cores wisely to save power and balance performance. Even though sched_mc is sort of an alternative to cpu hot plugging, we can use sched_mc with the default hot plug mode.
Possible Values:
0 : No power saving load balance, default in our exynos4210 Soc.
1 : Fill one thread/core/package first for long running threads. In our single-CPU dual-core device, multithreading does not come into picture, so load balancing is almost redundant to hotplugging.
2 : Also bias task wake-ups to semi-idle CPU package for power savings. (Bias new tasks to cpu1 if cpu0 is mostly filled with running tasks). This is 'overloading' CPU0 first.
Q. "What value is recommended for sched_mc?"
A. 1) If you find advantages to sched_mc, use sched_mc=1 for a possible battery saving. Anyhow since load-balancing is reduntant on hotplugging, it may not have any advantage on exynos chip.
2) For performance use 2. But do remember that loading CPU0 and leaving CPU1 can not do justice to hitting deep idle states sooner since second core can not enter deep idle. So extra performance or no performance, value 2 will drain some more battery, in the context of delayed didle.
3) To do justice to hotplugging, use value 0.
Example:
echo "0" /sys/devices/system/cpu/sched_mc_power_savings.
Schedulers that i recommend to use. Again massive thanks to Droidphile for the information.
Noop
Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives). Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.
V(R)
Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
Advantages:
May be best for benchmarking because at the peak of it's 'form' VR performs best.
Disadvantages:
Performance fluctuation results in below-average performance at times.
Least reliable/most unstable.
Governors that i recommend to use. Information again by Droidphile.
Lulzactive:
This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency.
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.
Conservative:
A slower Ondemand which scales up slowly to save battery. The conservative governor is based on the ondemand governor. It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization. However, the conservative governor increases and decreases CPU speed more gradually. Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle. Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency. The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization. For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source. Tweaks comes from 1) Knzo 2) Morfic. The original idea comes from Netarchy. See here. The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
Lionheart goes well with deadline i/o scheduler. When it comes to smoothness (not considering battery drain), a tuned conservative delivers more as compared to a tuned ondemand.
Do not forget to enable the Lionheart tweaks you must have Conservative governor enabled through the configurator application and then select Lionheart tweaks
Links
*N.E.A.K kernel:
http://forum.xda-developers.com/showthread.php?t=1411788
*Droidphile thread regarding more info about governors and schedulers and more tweaks
http://forum.xda-developers.com/showthread.php?t=1369817
*Ext4 Optimization information
http://kernelnewbies.org/Ext4
*N.E.A.K Configurator App.
https://play.google.com/store/apps/details?id=com.neak.NEAK_Configurator
*If you want to try alternative settings from mine and try settings near stock default go to the following thread by Geko95gek and check his great thread out.
http://forum.xda-developers.com/showthread.php?t=1466017

And your voltage conttol settings??
Tapatalk on SGSII (Powered by CheckROM RevoHD V6, SiyahKernel 2.6.12 + MagicConfig 0.3.1, Modem KI4)

edwardeutsch said:
And your voltage conttol settings??
Tapatalk on SGSII (Powered by CheckROM RevoHD V6, SiyahKernel 2.6.12 + MagicConfig 0.3.1, Modem KI4)
Click to expand...
Click to collapse
start with the MagicConfig mate. That should be good enough.

Great thread to start tweaking with Lulzactive governor. Should make life easier for a lot of people, gives them the opportunity to gain extra battery juice without too many headaches.

geko95gek said:
Great thread to start tweaking with Lulzactive governor. Should make life easier for a lot of people, gives them the opportunity to gain extra battery juice without too many headaches.
Click to expand...
Click to collapse
Thanks mate. And with your magic config people can have the best of both worlds. Shame we can't merge the two...Anyway thanks mate much appreciated for your kind words

Why pump up 4 steps? For performance or? The rest of the settings i can see the meaning in, but why pump up four steps?
Else, awesome thread! God starting point for many!

Pennywice said:
Why pump up 4 steps? For performance or? The rest of the settings i can see the meaning in, but why pump up four steps?
Else, awesome thread! God starting point for many!
Click to expand...
Click to collapse
Thanks mate...For performance yes but also if you see the other settings you will see they are leaning more towards the battery side. Hence why i wanted to go for a balance between the two if that makes sense. I will be trying different settings and i will provide screenshots of my results and will provide the settings for each result i do.

Stifler69 said:
Thanks mate. And with your magic config people can have the best of both worlds. Shame we can't merge the two...Anyway thanks mate much appreciated for your kind words
Click to expand...
Click to collapse
i see you have listen to me and you have opened a new thread nice mate

so_ony said:
i see you have listen to me and you have opened a new thread nice mate
Click to expand...
Click to collapse
check OP

Stifler69 said:
check OP
Click to expand...
Click to collapse
oh how cute thanks hehe =) geko didn't answer my email :/
your description is short but everything is described very well !

so_ony said:
oh how cute thanks hehe =) geko didn't answer my email :/
your description is short but everything is described very well !
Click to expand...
Click to collapse
any ideas on how to get this thread going please let me know..and glad you liked my OP

so_ony said:
oh how cute thanks hehe =) geko didn't answer my email :/
Click to expand...
Click to collapse
So sorry for the delay. Please feel free to punish me.

I want understand one thing sorry my noobless.
What magic have in magicConfig from geko?
Enviado do meu nokia 3320 modificado por laboratório usando Tapatalk

great...now something to use when im on check and neak...nice work stiffy!!!

Good work Stifler, im trying your magic configuration and it Owns..!! Just right now im experiencing a little more battery drain against just the +conservative+lionheart+ext4+AFTR config.
Ill give it some days with full charge and check.

Stifler69 said:
Anyway here are the settings that i use and use as a guide:
Lulzactive app Settings:
inc_cpu_load: 95%
pump_up_step: 4
pump_down_step:1
screen_off_min_step: 4,@200MHz
up_sample_time: 20000
down_sample_time: 40000
debug_mode: 0
Click to expand...
Click to collapse
Out of curiosity what are the default Lulzactive settings on NEAK 1.4 compared to those above???

Those lulzactive setting seem to be replicated from ThunderBolt! ain't it. Down to the last setting :/

pikachu01 said:
Those lulzactive setting seem to be replicated from ThunderBolt! ain't it. Down to the last setting :/
Click to expand...
Click to collapse
Hey mate. Actually I have never seen you around on any posts sharing these settings or even opened thunderbolt scripts to see how you tweak lulz governor. I have nothing but for respect for you Pika as I see how great you thread is and how popular your scripts are. These settings that I am using are a start up from me from playing around with the app and sharing my findings with friends. If it brings offence to you I will bring it down. But I swear to you I have never used your scripts as one I do not how to use them and two I prefer apps to do the work for me as I hate to many scripts in my phone. I would love your help here if possible on what to help people though

eric-filth said:
I want understand one thing sorry my noobless.
What magic have in magicConfig from geko?
Enviado do meu nokia 3320 modificado por laboratório usando Tapatalk
Click to expand...
Click to collapse
well just take a look at his thread my friend. his voltage control settings are shared nearly by 700 users on xda and have reported nothing but good stuff from it. i do not want to share my settings as i Undervolt quite heavy so my settings would not work with most on here. so i used his thread for people who would ask for settings apart from my lulz app ones.
jermitano said:
great...now something to use when im on check and neak...nice work stiffy!!!
Click to expand...
Click to collapse
Thanks mate. first post settings are just a start up. i will be trying different settings with different kernels and still use Lulzactive as i want to show people my results and they can choose what settings to go for. i will always post a little review as well so users can decide which one to go for.
Honchay said:
Good work Stifler, im trying your magic configuration and it Owns..!! Just right now im experiencing a little more battery drain against just the +conservative+lionheart+ext4+AFTR config.
Ill give it some days with full charge and check.
Click to expand...
Click to collapse
You would get a bit of drain my friend but again it is all about how you have your phone setup and what settings in VC you are using. but hope the settings have some benefit for you though
kersey said:
Out of curiosity what are the default Lulzactive settings on NEAK 1.4 compared to those above???
Click to expand...
Click to collapse
not sure mate.

Disclaimer alert: I am in no way responsible for any damage inquired while performing any of the changes listed below. If you are not comfortable with tweaking your device please feel free to use built in option in Siyah's Kernal. This is just an option and it is something I have tried on my phone with success. I am not using a stock battery, but rather a 2000MAH.
I have NeatRom Lite V1.1 + Siyah Kernal (Slick Sale) installed on my phone. This was created by Sale (his work on this rom is increadible). Samsung's stock kernal has been replaced by Siyah's kernal SGS2v.3.3.2. This version has touch CWM which makes flashing fun. To tweak the kernal, I installed ExTweaks (from the market. Extweaks has the option for battery, performance and defualt settings (these are enabled after a donation). This same settings can be performed in recovery. Siyah has the kernal tweaked for optimization for battery and performance. You can select this in recovery (scrolling down to kernal specific options and the choosing either battery or performance) and it will be impleted during boot up.
However if you feel bold you can tweak the kernal using Ex Tweaks. These are my settings below ( they are by no means a rule of thumb)
Note. I have noticed that the screen consumes most of the power from the battery. If you are able to reduce your screen brightness to about 40% instead of being at automatic, you will get additional time on your phone.
SETTINGS (CPU):
GENTLE_FAIR_SLEEPERS = On
ARCH_POWER = On
CPU Hotplug = Default
CPU IDLE Mode = AFTR + LPA (default)
Smooth Scaling Level = 800Mhz
SCHED_MC = 2
CPU Undervolting = -50mV
CPU Step Count = 18 (All available)
Default CPU Governor = pegasusq
Default CPU Scheduler = sio
Scaling Max Freq = 1000Mhz
Scaling Min Freq = 200Mhz
SETTINGS (GPU freq):
GPU Freq Step 1 = 66Mhz
GPU Freq Step 2 = 133Mhz
GPU Freq Step 3 = 267Mhz
SETTINGS (GPU voltages):
GPU Voltage Level 1 = 800mV
GPU Voltage Level 2 = 850mV
GPU Voltage Level 3 = 900mV
SETTINGS (other):
Screen settings stock.
Vibration intensity = 2
Touchmovesensitivity =5 pixel
Min_BL =30
Min_Gamma=1
Max_Gamma=24
Other setting without undevolting.
SETTINGS (CPU):
GENTLE_FAIR_SLEEPERS = On
ARCH_POWER = On
CPU Hotplug = Default
CPU IDLE Mode = AFTR + LPA (default)
Smooth Scaling Level = 800Mhz
SCHED_MC = 2
CPU Undervolting = No undervolting
CPU Step Count = 18 (All available)
Default CPU Governor = pegasusq
Default CPU Scheduler = sio
Scaling Max Freq = 1000Mhz
Scaling Min Freq = 100Mhz
SETTINGS (GPU freq):
GPU Freq Step 1 = 40Mhz
GPU Freq Step 2 = 133Mhz
GPU Freq Step 3 = 267Mhz
SETTINGS (GPU voltages):
GPU Voltage Level 1 = 800mV
GPU Voltage Level 2 = 850mV
GPU Voltage Level 3 = 900mV
SETTINGS (other):
Screen settings stock.
Vibration intensity = 3
Touchmovesensitivity =5 pixel
Min_BL =40
Min_Gamma=0
Max_Gamma=24
Please note Geko95gek has three different settings and it should work if you are in the mood for an adventure.
Download Links.
NeatRom Lite
Siyah Kernal
ExTweaks (Google play Store)
Useful sources
Geko95gek http://forum.xda-developers.com/showpost.php?p=26755476&postcount=850
Droidphile's article http://forum.xda-developers.com/showthread.php?t=1369817
Special thanks and credit to the following:
Sale (awesome rom and excellent support)
Gokhamoral (great kernal)
Geko95gek (examples of tweaks)
Droidphile (Write up of governors).
Sample shorts of my usage.
{
"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"
}

Thank you!
Siyah is a fantasic kernel and I am thrilled with it

My last post on battery and consumption using the latest NeatRom Lite with Siyah's kernel was based on my extended battery (2000mAh). This time around, I decided to try it with stock battery. As suspected the results were just as amazing. I want to point out that I maintained the same tweaks ad settings. Once again Sale has created a clean and exciting ROM.
Before sun raise
Am sure I could have gotten another 5 hours or more with this ROM. Great combination NeatRom Lite and Siyah's Kernel
Sent from my GT-I9100 using Tapatalk 2

Interesting post but I must say that on mine the kernel included with neatrom is at least as good for me as an all rounder (balance between performance and battery) as I've yet found.
Not trying to rubbish the results btw, but for me I've followed a lot of these guides for different kernels and at best the difference is small and at worst introduces bugs.
Happy with neat from though very good!

I was always using NEAT Rom without any UC/OC modifications and it was already GREAT.
Inspired from your Post I decided to give undervolting a try...
I have latest NEAT Rom UHLPS Lite and use the Settings with undevolting;
the absolute great batterylife has increased over again! Wuha!
Also the performance is nearly the same as before (feels exactly the same as before!)
So in my opinion the combination of NEAT Rom, Siyah Kernel and your settings for undervolting are amazing!
Thanks Sale for this absolute superb Rom!
Thanks Gokhamoral for the great Kernel!
and thank you red.hat for the inspiration and this lovely guide for underclocking!
My experience:
Tweaked settings, charged battery to 100%, used it now for 26 hours, made some calls (about 30min), wrote some sms,
used Wifi for about 35min for surfing and the battery is still at 89% !!!

Battery saving tweaks
Thanks to red.hat's hospitality, you can find on this thread my battery friendly configs. They are based on NeatromLite stock based roms and Siyah custom kernels. Exceptionally I prepare tweaks also for other kernels (eg philz) when Siyah kernels are not available/ready for particular Neatrom releases.
Beneath you can find my work which I've done so far.
MANY40'S BATTERY FRIENDLY CONFIGS COLLECTION:
What is the battery friendly config? In short, it's a set of battery saving tweaks which can be divided into two groups: kernel tweaks and rom tweaks.
1. Kernel's tweaks (scripts + Stweaks profile - they tweak some kernel's tunables like CPU/GPU freq, CPU/GPU voltages, CPU governor and other parameters)
2. Rom's tweaks (OS sound/vibration/screen/motion/animation/comms/location/sync etc settings + freezed system apps list + wakelocks advices + some others)
DISCLAIMER:
A. Everybody can try it but not necessarily it will work for everybody like it works for me.
B. Remember that our phones' hardware is not 100% identical.
C. Make nandroid backup before trying this
D. If any tweak causes freezes, restore your nandroid backup.
I. SIYAH KERNELS:
1. <Siyah 6.0 beta5 + Neatrom 4.X JB 4.1.2>
2. <Siyah 6.0 beta4 + Neatrom 4.X JB 4.1.2>
3. <Siyah 5.0.1 + Neatrom ICS 4.0.3/4.0.4>
4. <Siyah 4.1.5 + Neatrom ICS 4.0.3/4.0.4>
II. PHILZ KERNELS:
1. <PhilZ-CWM6 4.X + Neatrom 4.X JB 4.1.2>
Enjoy!

Many40 said:
Thanks, great proposal. I am not new on this subject doing similar things for myself but if you don't mind I would have one question (I couldn't find the answer up to now) and one remark:
Question: You posted two different settings: first one with min FRQ 200 MHz and second one 100 MHz. Did you do that intentionally? Do you know what freq is better for battery saving? I red somewhere that on 100MHz phone consumes more power than on 200MHz. So according to your konwlegde/exeprience what is better - I am using 100MHz as you can see from my signature.
Click to expand...
Click to collapse
Both frequencies were tried to see the benefits of one over the other. I didn't find much difference. Through my research I found some people prefer 100 MHz and others 200MHz. How is 200MHz working out for you.
Remark: Here are my considerations about SHED_MC. I am not using this option (SHED_MC=0) because in my opinion if CPU hotplug is set, enabling SHED_MC doesn't make really sense (Sched_mc aims to schedule tasks between multiple cores in the CPU and if sched_mc = 2 = load balancing, then to make sense dual core shoud be set instead of hotplugging. But it would rather help to utilize both cores more effectively than save more battery. Moreover then AFTR+LPA couldn't be hit when 2nd core is on). The same opinion shares droidphille who gave me short answer on that in his thread.
This is theory, but maybe real life brings something different? Have you tested both?
Regards
Click to expand...
Click to collapse
I haven't tested both, but you have raised a good question and I'll have to look into it. Siyah's default setting for battery optimization has SCH_, also set at 0. However a couple of examples I saw on xda has it at 2. I'll make changes tomorrow and set how that goes. Could you share droidphille reaponse
Sent from my GT-I9100 using Tapatalk 2

red.hat said:
Both frequencies were tried to see the benefits of one over the other. I didn't find much difference. Through my research I found some people prefer 100 MHz and others 200MHz. How is 200MHz working out for you.
Click to expand...
Click to collapse
Tested both (but on sammy stock rom) and also didn't notice any difference.
I haven't tested both, but you have raised a good question and I'll have to look into it. Siyah's default setting for battery optimization has SCH_, also set at 0. However a couple of examples I saw on xda has it at 2. I'll make changes tomorrow and set how that goes. Could you share droidphille reaponse
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, of course. I started thinking about that after red geko95gek's MagicConfig. He also proposed SCHED_MC=2. So I asked him about the reason but he didn't respond so decided to ask droidphille. This was his answer:
"@Many40
Let's say enabling sched_mc on Galaxy S2 Exynos 4210 is completely pointless. Hotplugging is well handled by stand hotplug/legacy hotplug. Two logics trying to do same thing is always bad. It's like having two antivirus software on PC or like freq_step and smooth scaling trying to do similar stuff in ondemand based governors.
Sched_mc = 1 = Assymmetrical loading of cores. This can hinder race to idle (talking about AFTR here).
sched_mc = 2 = load balancing. When hotplugging knows when and how to hotplug In and Out second core, there's no need of another logic to do the same and cause conflicts. If you're using forced dual core mode, this may have some benefits. I never tested myself.
conclusion: let shed_mc=0 as long as you're using hotplugging. If you're on dual core mode (remember aftr/lpa can not be hit when second core is On), try sched_mc=2. However i don't think load balancing can save battery. It may utilize both cores effectively."

I've done a few tests on the NEAT ROM with stock kernel and with Siyah and on the settings given here.
I wouldn't recommend these settings if you ever want to play games, the Antutu benchmark froze at the graphical portion but did finish the benchmark with a overall score of about half of what it did with the stock kernel (6226 v 3489). Quadrant wouldn't even finish.
Even when I reset Siyah back to its own defaults, the benchmarks are coming in at around 10 - 15% slower than stock.
They may be good for saving battery but to me its like having a Porsche, and then de-tuning it to half the power to save petrol.
Not trolling, just trying to offer another perspective.

tameracingdriver said:
I've done a few tests on the NEAT ROM with stock kernel and with Siyah and on the settings given here.
I wouldn't recommend these settings if you ever want to play games, the Antutu benchmark froze at the graphical portion but did finish the benchmark with a overall score of about half of what it did with the stock kernel (6226 v 3489). Quadrant wouldn't even finish.
Even when I reset Siyah back to its own defaults, the benchmarks are coming in at around 10 - 15% slower than stock.
They may be good for saving battery but to me its like having a Porsche, and then de-tuning it to half the power to save petrol.
Not trolling, just trying to offer another perspective.
Click to expand...
Click to collapse
Yes this is a battery saving setting not for gaming. I used these settings because I can't charge my battery all day so I am using this. However, I if you need performance you can change the i/o scheduler to crq, no scaling of leave at default which 1200 MHz or just use Siyah's kernel performance option in kernel settings.
There are times when driving a Porsche requires a slow speed.
Sent from my GT-I9100 using Tapatalk 2

I've flashed Neatrom with Siyah kernel last night. Did a full charge and I am now monitoring my battery usage.
During the night I've lost 2% charge with wifi and data switched off, which i think is very good.
But now, after a total of just over 12h, the battery sits at 42%, of which the screen was on for 1h 40min and wifi for about six hours.
Is this the normal usage, or at least expected? Or is there still plenty of room for improvement?
By the way, I can't undervolt my CPU to -50mV - it causes freezes. -25 seems okay.

PakkaZA said:
I've flashed Neatrom with Siyah kernel last night. Did a full charge and I am now monitoring my battery usage.
During the night I've lost 2% charge with wifi and data switched off, which i think is very good.
But now, after a total of just over 12h, the battery sits at 42%, of which the screen was on for 1h 40min and wifi for about six hours.
Is this the normal usage, or at least expected? Or is there still plenty of room for improvement?
By the way, I can't undervolt my CPU to -50mV - it causes freezes. -25 seems okay.
Click to expand...
Click to collapse
Did you use the same setting as above. I have mine on without Wi-Fi and through normal use I am at 97%.
Give thanks if I have helped you. Sent via Tapatalk on my S2- i9100

Here is the link to the kernal for S2. It has somewhere Cfs tweaks included.
http://www.gokhanmoral.com/gm/2012/07/08/siyahkernel-s2-v3-3-3/
Give thanks if you have been helped.
sent via HP touch pad with Tapatalk

for 3.3.3c which setting?

qqqqqq0 said:
for 3.3.3c which setting?
Click to expand...
Click to collapse
Hello still working on a great setting. Try the second settings above but set sch_ to 0, CDs tweaks art Linux kernal. It is what I have been using so far.
Give thanks if you have been helped.
sent via HP touch pad with Tapatalk

hi what specific of neatrom should i get and also siyah kernel v3.3.3?

miedy12 said:
hi what specific of neatrom should i get and also siyah kernel v3.3.3?
Click to expand...
Click to collapse
Any version of NeatRom is fine. I personally like uhlps lite. It is fast and responsive. You can combine it with Jkay's deluxe and ics domination
Give thanks if I have helped you. Sent via Tapatalk on my S2- i9100

thanks yes ive downloaded the latest rom posted on july 1/ the kernel is siyah kernel 3.2.2 so it is ok for this? and then i just going to set your undevolt or flash the new 3.3.3?

Scaling Max Freq = 1000Mhz so this is 1000000mhz
Scaling Min Freq = 200Mhz and this is 200000
i am correct?
hi im confused there all i can see is the minimum og 100000 and in min frequency its 20000? it is correct? help also. in sch_med i cant choose to put it on 2 help. and also i set my kernel in cmw at battery

miedy12 said:
Scaling Max Freq = 1000Mhz so this is 1000000mhz
Scaling Min Freq = 200Mhz and this is 200000
i am correct?
hi im confused there all i can see is the minimum og 100000 and in min frequency its 20000? it is correct? help also. in sch_med i cant choose to put it on 2 help. and also i set my kernel in cmw at battery
Click to expand...
Click to collapse
The min Freq is 100MHz and the max is 1000Mhz. The sch_med and hotplug perform the same function so you can leave at 0. But if you want to you can slide it to 2.
Give thanks if I have helped you. Sent via Tapatalk on my S2- i9100

Alright, below this, I will include an almost full guide to setting up STweaks (for those who do not want to use the provided profiles)
The CPU section contains the frequencies and voltages that you want to run at.
200mHz is the minimum speed, 1800mHz is the maximum speed. You can change these to affect your overall performance or battery life. Mine is currently set to 200mHz minimum, 1800mHz maximum. I have seen no hit on battery life at all (might be miniscule.)
Now for the Voltages.. Each and every person will have a different set of voltages, as every CPU will be a little bit different. You can manually set your frequency to a certain level, use a CPU stress testing app (stability test) and drop the voltage by SMALL increments until you start to lose stability (system crashes, app force closes, etc.) I usually go UP one voltage step over the borderline stable voltage. I will post my voltages, but take caution, as my voltages are set pretty low compared to stock values on the kernel.
1800mHz - set to 1200000 uV or 1.2 volts.
1704mHz - set to 1175000 uV or 1.175 volts.
1600mHz - set to 1112500 uV or 1.1125 volts.
1500mHz - set to 1100000 uV or 1.1 volts.
1400mHz - set to 1062500 uV or 1.0625 volts.
1300mHz - set to 1025000 uV or 1.025 volts.
1200mHz - set to 1000000 uV or 1 volt.
1100mHz - set to 975000 uV or 0.975 volts.
1000mHz - set to 962500 uV or 0.9625 volts.
900mHz - set to 937500 uV or 0.9375 volts.
800mHz - set to 912500 uV or 0.9125 volts.
700mHz - set to 887500 uV or 0.8875 volts.
600mHz - set to 862500 uV or 0.8625 volts.
500mHz - set to 837500 uV or 0.8375 volts.
400mHz - set to 812500 uV or 0.8125 volts.
300mHz - set to 800000 uV or 0.8 volts.
200mHz - set to 787500 uV or 0.7875 volts. * BE CAREFUL WITH THIS ONE, it can cause your device to lock up when the screen is off, and need a battery pull if the voltage is too low.
CPU Scaling Section - This controls how your device will turn up the speed when it needs to.
Governor - This contols how the device will respond overall (power management, sleep, etc.) I will keep mine set to the Pegasusq governor unless I am running a benchmark, in that case, use perfomance (which locks the device to full speed and all 4 cores online)
Sampling Rate - how often the device will 'think' about changing the CPU speed. I have mine set to 15000 uS (15 milliseconds) so it is more responsive.
Sampling Down Factor - This enables you to create 'lag' when the device is at full speed, so it doesn't jump down frequencies when you don't want it to. I leave mine at default 1 sample, because I see no need for this.
Up Threshold - When a core hits this % utilization at a set frequency, then it will scale up to the next frequency. I have mine set to 96%, so the device will scale up slower and more reliably (keep in mind it makes this decision every 15 milliseconds.)
Down Differential - When the device scales down, (drops frequency) it must get below this % utilization to scale down ( UP THRESHOLD minus DOWN DIFFERENTIAL ) I have mine set to 5%, so it drops frequency at or below 91% utilization.
Frequency for Responsiveness - This helps keep the device smooth at lower frequency, and when the frequency is below the set spot, it will use a DIFFERENT up threshold so the device scales up faster and doesn't lag. My frequency setting is 500mHz, and the up threshold for it is set at 70%.
Frequency for Fast Down - this sets the frequency at which the device can use aggressive down scaling, much like the opposite of frequency for responsiveness. I have mine set to 1400mHz, and the up threshold is set to 98%, so the device only scales up if it really needs to.
Frequency Step - This applies to the Fast Down setting, and whenever the device gets above 98% utilization, then it will increase the frequency by a SET percentage of the maximum frequency. So if you set 10%, and are have 1800mHz max, it will increase to the closest step that adds 180mHz. I have mine set to 6%, so it increases by 108mHz.
The up threshold and frequency step decrease confuse me for this, but I have the up threshold set to 2%, and the frequency step set to 3%.
I didn't touch the flexrate settings, as everything else should control this area.
CPU Hotplug - This section will control how the device turns its cores on and off.
CPU Up Rate - How many samples you want to take until a core decides to turn on. (Sampling rate times your setting) I have mine set to 12, so if the conditions are correct, it takes 180 milliseconds to turn a core on.
CPU Down Rate - How many samples you want to take until a core decides to turn off. (Same thing as CPU up rate) Mine is set to 10, so it takes 150 milliseconds to turn off a core if it isn't being used.
Core Upbring Count - How many cores you want to bring online when the conditions are right. Mine is set to 1, I'm sure more will increase performance and hurt battery life.
Configuration Overrides - These can set you device to always have a certain amount of cores online, I don't use them (leave at 0.)
Hotplug Conditionals - These perameters are set to control when the cores turn on and off. Below are MY values
Hotplug 1 Core to ONLINE (make 2 cores online) - 600mHz
Hotplug 2 Cores to OFFLINE (make 1 core online) - 500mHz
Hotplug 2 Cores to ONLINE (make 3 cores online) - 700mHz
Hotplug 3 Cores to OFFLINE (make 2 cores online) - 600mHz
Hotplug 3 Cores to ONLINE (make 4 cores online) - 800mHz
Hotplug 4 Cores to OFFLINE (make 3 cores online) - 700mHz
The rest of this section, I left at DEFAULT values, because I did not understand them.
GPU - This section controls the frequencies and voltages of your GPU.
Maximum Frequency - How high you want your GPU to clock to, mine is set to 733mHz.
Minimum Frequency - How low you want your GPU to clock to, mine is set to 108mHz.
Up Threshold - Like the CPU setting, the percentage of utilization you achieve before the GPU scales up. Mine is set to 90%.
Down Differential - When you want your GPU to scale down lower, (Up threshold minus down differential.) Mine is set to 10%, so when the GPU hits 80% utilization on a speed, it drops to a lower frequency.
Utilization Timeout - Basically is the sampling speed of the GPU (how fast you want it to make decisions to change speed.) Mine is set to 25 milliseconds.
Voltages - Test these the same way as the CPU, get a GPU stress testing app, and set a certain frequency. When you see artifacts or glitches on your screen, then the voltages are too low. Below are MY values.
54mHz - 800mV
108mHz - 800mV
160mHz - 900mV
266mHz - 925mV
350mHz - 975mV
440mHz - 1025mV
533mHz - 1050mV
640mHz - 1075mV
733mHz - 1125mV
800mHz - 1150mV (This clock speed proved to be slightly unstable at 1175mV, though still usable)
I/O section - These values/settings control how your device writes/reads things from the SD card, or internal storage.
I left both of my storage schedulers at ROW but you can change them and play around. I believe that deadline is the best for overall performance, but can be unstable sometimes.
I/O Read Ahead - These control the cache file on the internal/external storage. I have my internal set to 1536kB, and external set to 2048kB, because those values gave me overall good write/read speeds.
Dynamic Fsync - From what I know, this helps keep the data from being corrupted by creating a buffer between data being written and the storage. Correct me if I'm wrong. I kept it enabled.
The entire audio section is pretty self explanatory, and I'm getting tired of typing all of this, so if you need help, PM me or comment.
Again, take this entire post with caution. What works with my device, may make yours unstable. I only provided mine to give you a baseline, my values offer good performance and battery life anyways. Feel free to correct any of my errors by PM or comment, and I will gladly change my post to accommodate for my errors........
Creditx Goes To - CW ||

Great guide man!
Can I suggest you BOLD each features like this,
Governor - This contols how the device will respond overall....
Otherwise it's hard to read in one big block.
Or you could just separate them.
Good job:good:

Kremata said:
Great guide man!
Can I suggest you BOLD each features like this,
Governor - This contols how the device will respond overall....
Otherwise it's hard to read in one big block.
Or you could just separate them.
Good job:good:
Click to expand...
Click to collapse
Done....

Here's my more performance oriented settings. Averages 19500 on Antutu, and 7400 on Quadrant Standard (Advanced version adds 1000 to score) This doesn't lag at all between screens, animations, etc. The only lag I've seen is when my apps rarely crash.
CPU Max - 1800mHz
CPU Min - 200mHz
Voltages from OP
Pegasusq governor
Sampling Rate - 15000uS
Sampling Down Factor - 1
Up Threshold - 90%
Down Differential - 10%
Frequency for Responsiveness - 600mHz
Up Threshold @ Min Freq - 60%
Frequency at Fast Down - 1400mHz
Up Threshold at Fast Down - 94%
Frequency Step - 25%
Up Threshold Differential - 5%
Frequency Step Decrease - 10%
Flexrate Enabled - 700mHz, 10000uS
CPU Up Rate - 8 samples
CPU Down Rate - 10 samples
Core Upbring Count - 1
*Default Configuration Overrides*
1 Core to Online - 300mHz
2 Cores to Offline - 200mHz
2 Cores to Online - 400mHz
3 Cores to Offline - 300mHz
3 Cores to Online - 500mHz
4 Cores to Offline - 400mHz
*Runqueue Depths*
1 Core to Online - 155
2 Cores to Offline - 155
2 Cores to Online - 250
3 Cores to Offline - 250
3 Cores to Online - 340
4 Cores to Offline - 340
CPU Online Load Bias - 2 cores
CPU Online Bias Up Threshold - 50%
CPU Online Bias Down Threshold - 30%
GPU Max - 640mHz
GPU Min - 160mHz
Up Threshold - 85%
Down Differential - 5%
Utilization Timeout - 25ms
Voltages from OP
Internal/SD Card Schedulers - SIO
Internal/SD Card Read Ahead - 2048kB
Dynamic FSync - Enabled

Detailed guide
I have found this guide very detailed and useful. Thanks for taking your time to make this thread.

krishelnino said:
I have found this guide very detailed and useful. Thanks for taking your time to make this thread.
Click to expand...
Click to collapse
If I've done something you Appreciate, please hit the ":good:THANKS" button

hellDr0id said:
If I've done something you Appreciate, please hit the ":good:THANKS" button
Click to expand...
Click to collapse
Same for you. lol

Kremata said:
Same for you. lol
Click to expand...
Click to collapse
:good:

You copy all this from the thread i created yesterday under the Help section? LOL Nice try...

ahkiongkc said:
You copy all this from the thread i created yesterday under the Help section? LOL Nice try...
Click to expand...
Click to collapse
trolled Nice try
I've just bump this thread with Creditx LOL ::::...
. . . .. People should take a look at this!
And yea for ua kinda info i didnt even know about your thread so Pls dont spam lol

hellDr0id said:
trolled Nice try
I've just bump this thread with Creditx LOL ::::...
. . . .. People should take a look at this!
And yea for ua kinda info i didnt even know about your thread so Pls dont spam lol
Click to expand...
Click to collapse
It's funny how when you try to make a nice thing and help people there is always one to come and try to discredit. I have the same problem with my recovery guide.

Kremata said:
It's funny how when you try to make a nice thing and help people there is always one to come and try to discredit. I have the same problem with my recovery guide.
Click to expand...
Click to collapse
Here thing is totally different, what I know about your recovery guide is no one gave you discredit. When you publish any guide on public forum, sure someone will put their ideas and only that way discussion goes on. Basically public forum is meant for such things. I have wrote many guides having million viewership, thousand thanks, still people suggest me when something better they found, and I love to exchange idea, but it's ultimately you have to decide which one is better. We should have to remain open to discuss on topic we have created.
As far as my comments have concerned, I have discussed point to point why I found other thing is better, if you targeting that then better if you show some nice point to make me convince on your point of view rather complaining to other post. If you targeting else I am sorry.
Does you feel anyone have troll on your post?
I don't think so.
Sent from my GT-N7100 using xda premium

dr.ketan said:
Here thing is totally different, what I know about your recovery guide is no one gave you discredit. When you publish any guide on public forum, sure someone will put their ideas and only that way discussion goes on. Basically public forum is meant for such things. I have wrote many guides having million viewership, thousand thanks, still people suggest me when something better they found, and I love to exchange idea, but it's ultimately you have to decide which one is better. We should have to remain open to discuss on topic we have created.
As far as my comments have concerned, I have discussed point to point why I found other thing is better, if you targeting that then better if you show some nice point to make me convince on your point of view rather complaining to other post. If you targeting else I am sorry.
Does you feel anyone have troll on your post?
I don't think so.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Hmm I also don't think so. .
Sent from my GT-N7100 using xda premium

what Kernel is the best one to use for longer battery time and smoothness and over clocking

youngblood68 said:
what Kernel is the best one to use for longer battery time and smoothness and over clocking
Click to expand...
Click to collapse
I Highly recommend ....
Go for Perseus Kernel you'll love it . . .
Sent from my GT-N7100 using xda premium

Nice explanation about all the options in stweaks, thanks for that, sadly my CPU won't accept voltages as low as yours. Only I think your GPU voltages are a little high, some of them are even slightly higher than the default values, why is this?
Sent from my GT-N7100 using Tapatalk 2

pimjai said:
Nice explanation about all the options in stweaks, thanks for that, sadly my CPU won't accept voltages as low as yours. Only I think your GPU voltages are a little high, some of them are even slightly higher than the default values, why is this?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
GPU voltages are perfect mate ...
all voltages are low compared to Default
Here's screen shotx
{
"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"
}
Sent from my GT-N7100 using xda premium

Did OP literally just copy and paste this from the other subforum? what the

ungraph said:
Did OP literally just copy and paste this from the other subforum? what the
Click to expand...
Click to collapse
Wtf... :banghead:
Are you a idiot or something like that ?
Or you know everything about stweaks :lol:
Ohh I thik you didn't like that people's specially noob know more about tweaking and all .... that's why u pointing out on copy paste. ...
Unfortunately I love sharing so I shared this post also. .....

i think you are copied from others post.
http://forum.xda-developers.com/showthread.php?t=2079311
http://forum.xda-developers.com/showthread.php?t=2079311&page=10

A lot of users wanted / requested someone to start a topic of this kind - and voila, here it is:
The Official & Dedicated Thread about sharing your each and specific FauxClock / Pimp My Z1 / Performance Control App / Trickster Mod / -Additional App Name- settings to other users so they can try out either some settings that gives god holy battery life or monstrous performance from the Ferrari manufacturers themself!
Just for making the posts easier to read and understand for the less experienced / knowledged users - Write your posts with includings settings in a classic, lined way - Like this;
- What app are you using..
- Which ROM are you on..
- Which kernel are you on..
- What CPU frequencies are you using..
- Your specific CPU governor..
- Your specific IO Scheduler..
- Your specific GPU governor..
- What GPU frequencies are you using..
- Any color calibration tuning you want to share..
- Any Multi Core Power saving tunetable enabled (0 / 1 / 2?)..
- Which hotplug driver are you on?
- Intelliplug ECO-Mode - On or Off?
- Etc etc.. You get the point hopefully..
Any selfmade / specific favourite init.d scripts? Post them below so other users can get the pure enjoyment to try them out?
Please.. Note this point below;
Post a Screenshot of your total average battery life + Total Screen-On-Time so people can debate / hail / criticize / award / dislike and coment if it's good or bad total battery performance!
OBS!! If you are using any init.d scripts - share them either here, in your post or in a uploaded ZIP / RAR file so other ones can give them a try and see if it extends either performance or battery life for them!
I hope this thread can be made into a sticky - so everything about "SHARE YOUR APP SETTINGS" can be collected into one, overall and single thread, instead of being misplaced all over this Xperia Z1 subforum. Keep it clean and tight <- Good words that a friend told me, and this is a golden rule on massive sites like XDA-Developers with thousand of new threads / posts everyday.
Sharing is Caring - so Happy Sharing, my fellow friends!
Regards,
Destroyedbeauty @ XDA
> OBS! NO SPAM, OFFTOPIC OR BULL**** POSTS IN THIS THREAD - THEY WILL BE REPORTED ASAP!!! <

Finally. Will post on V22 once it is out.

App: Pimp My Z1
ROM: Paranoid Android 4.4 beta-1
Kernel: Pimped kernel for CM Roms, light version
Frequencies: Min 300 / Max 1728
Governor: Smartass V2
Scheduler: row
Additional: power suspend and dynamic file sync
Have been running this for two days, awesome battery life. I hope it is OK that I post settings for an AOSP ROM.
Feel free to ask any questions.
{
"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"
}
Skickat från min Xperia Z1 via Tapatalk

ekanix20 said:
I hope it is OK that I post settings for an AOSP ROM.
Click to expand...
Click to collapse
Of course! As long you're adding something of a value and still is staying on topic - you can add what you want to the topic and subject!

App: Trickster Mod
Rom: Ihackers v4.1 minimal
Kernel: DoomLord v21
Max/Min freq: 300-1.9ghz
Governor: intelliactive
Scheduler: Deadline, 1024 Buffer
Intelliplug activated, powersaving 1
Zram activated
Fsync activated
Voltage at 750mh for 300mhz
Great battery life so far with this Setup!
Up to 4 1/2 hours screen on time, everything running find and snappy!
Sent from my C6903 using XDA Free mobile app

Okey, it's time for me to post my full set-up / configuration also then.. Here it is;
- App: Pimp My Z1
- ROM: Deodexed & Tweaked Stock .757
- Kernel: Doomkernel v21
- CPU Frequencies - MIN: 300 Mhz / MAX: 1728 Mhz
- CPU Governor: Intellidemand
- IO Scheduler: Deadline
- GPU Governor: MSM_CPUFREQ
- GPU Frequencies - MIN: 27 Mhz / MAX: 320 Mhz
- Color Calibration - Red: 255, Green: 235, Blue: 250
- Sony White Balance Control - Red; 15, Green: 40, Blue: 25
- Power Managment:
- Multi-Core Power Savings: 0
- Hotplug Driver: Intelliplug
- Intelliplug ECO-Mode: On
- Power Suspend: On
- Dynamic File Sync: On
- Readahead (eMMC): 1024
- Entropy Contribution: Off
- Vibrator Intensity: 0
Additional tweaks / scripts that I am using; See attached ZIP file for my specific battery saving script!
Results: I am at 15% battery juice left after 1 day, 1 hour and 41 minutes since last charge and total Screen-On-Time of 5 hours and 6 minutes!

e30luismi said:
install script battery?
Click to expand...
Click to collapse
Do not spam the threads about same thing! What do you mean by "install script battery"? Lord.

e30luismi said:
install script battery?
Click to expand...
Click to collapse
Place this script inside your init.d folder (/system/etc/init.d) and give script and init.d 0777 permissions and reboot for it taking full action!
So.. KEEP THIS THREAD ON TOPIC OR I'LL REQUEST IT TO BE LOCKED!!!
Sent from my C6903 using XDA Premium 4 mobile app

My battery 27% with 2h 10min screen , config destroyed rom pure stock v2 mode stamine on

e30luismi said:
thx
Click to expand...
Click to collapse
e30luismi said:
My battery 27% with 2h 10min screen , config destroyed rom pure stock v2 mode stamine on
Click to expand...
Click to collapse
And you thought those posts was adding anything of a value to the thread?
Sent from my C6903 using XDA Premium 4 mobile app

e30luismi said:
sorry,
Click to expand...
Click to collapse
Please, stop spamming non-value posts.
Reporting now!
Sent from my C6903 using XDA Premium 4 mobile app

Fauxclock + DoomKernel v21
CPU Governor: Intelliactive min300 max1958 tweaked with these settings:
above_hispeed_delay = 20000
boost = 0
boostpulse = (null)
boostpulse_duration = 80000
go_hispeed_load = 60
hispeed_freq = 1497600
io_is_busy = 0
min_sample_time = 200000
sampling_down_factor = 1
sync_freq = 960000
target_loads = 90
timer_rate = 20000
timer_slack = 80000
two_phase_freq = 1728000,1728000,1728000,1728000
up_threshold_any_cpu_freq = 1497600
up_threshold_any_cpu_load = 90
Intelliplug on, eco mode on, touch boost off, screen off frequency set at 652800, sio schedulers!
Enjoying great battery life and performance :good:

dedei said:
Fauxclock + DoomKernel v21
CPU Governor: Intelliactive min300 max1958 tweaked with these settings:
above_hispeed_delay = 20000
boost = 0
boostpulse = (null)
boostpulse_duration = 80000
go_hispeed_load = 60
hispeed_freq = 1497600
io_is_busy = 0
min_sample_time = 200000
sampling_down_factor = 1
sync_freq = 960000
target_loads = 90
timer_rate = 20000
timer_slack = 80000
two_phase_freq = 1728000,1728000,1728000,1728000
up_threshold_any_cpu_freq = 1497600
up_threshold_any_cpu_load = 90
Intelliplug on, eco mode on, touch boost off, screen off frequency set at 652800, sio schedulers!
Enjoying great battery life and performance :good:
Click to expand...
Click to collapse
Some questions..
1. Are you on any custom ROM or stock .757 / .761 firmware?
2. No wakelocks from FauxClock app? < Please check and verify with Greenify and BBS apps..

Destroyedbeauty said:
Some questions..
1. Are you on any custom ROM or stock .757 / .761 firmware?
2. No wakelocks from FauxClock app? < Please check and verify with Greenify and BBS apps..
Click to expand...
Click to collapse
Stock 757, phone has been up for 15h with x86 wakelocks from fauxclock
right now I'm on 3h11m of screen on time and I still have 39% of juice!
Enviado de meu C6903 usando Tapatalk

Destroyedbeauty said:
Place this script inside your init.d folder (/system/etc/init.d) and give script and init.d 0777 permissions and reboot for it taking full action!
So.. KEEP THIS THREAD ON TOPIC OR I'LL REQUEST IT TO BE LOCKED!!!
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do you do this? I understand moving it to a certain folder but I've never used init.d
I'm on iHackers v2 stock rooted not unlocked bootloader yet, Please explain how I can achieve what you have done in more details.

JayGB2011 said:
How do you do this? I understand moving it to a certain folder but I've never used init.d
I'm on iHackers v2 stock rooted not unlocked bootloader yet, Please explain how I can achieve what you have done in more details.
Click to expand...
Click to collapse
You can't do that with a locked bootloader.
Enviado de meu C6903 usando Tapatalk
---------- Post added at 02:34 AM ---------- Previous post was at 02:34 AM ----------
e30luismi said:
active ksm??
Click to expand...
Click to collapse
If that was directed towards me, no lol I never enabled it
Enviado de meu C6903 usando Tapatalk

My turn...
- App: FauxClock
- ROM: Tweaked Stock .757
- Kernel: Doomkernel v19
- CPU Frequencies - MIN: 300 Mhz / MAX: 1728 Mhz
- CPU Governor: Intellidemand
- CPU Hotplug: Intelliplug
- IO Scheduler: Deadline
- GPU Governor: Simple_ondemand
- GPU Frequency: MAX: 200 Mhz Lazinesss: 4 Ramp Treshold: 6
- Power Managment:
- Hotplug Driver: Intelliplug
- Intelliplug ECO-Mode: On
- Power Suspend: On
- Dynamic File Sync: On
- I/O Scheduler (eMMC/SDCard): sio / row
- Readahead (eMMC/SDCard): 1024/512
- Entropy Contribution: Off
- ZRAM Swap: Off
- Intelli-KSM: Enabled (Standard settings)
Results:
SCREEN ON about 2 hours
300 MHz ~ 20% of time
Deep Sleep ~ 65% of time
Overall graph
As you see some app did not close correctly and GPS was ON about hefty 8 Hours so i think the score isn't so bad at all.
ps. got 2 email accounts with POP Push and Google+ which produces most wakelocks, next time will switch off both and will see the difference...

@all
Bump! Thread seems to be dead, pretty strange because this topic was requested for avoid off topic posts, and then people seems to ignore it.
To lazy to use proper discussion threads, maybe?
Sent from my Xperia Z1 using XDA Premium 4 mobile app

Yeah, i'v been waiting for a good balance settings to be posted because mine stays on 1497 and 1728 most of the time even with light apps..

dedei said:
Yeah, i'v been waiting for a good balance settings to be posted because mine stays on 1497 and 1728 most of the time even with light apps..
Click to expand...
Click to collapse
Pm me!

My settings for the CPU is performance for both

smarannss said:
My settings for the CPU is performance for both
Click to expand...
Click to collapse
If you want help, you'll have to give MUCH more details about Boeffla settings, phone settings, apps you're using and general phone usage behaviour. Such as: WiFi or mobile data? Do you play power hungry games? Do you have lots of apps running in the background that use data or keep the CPU active? Do you use Xposed with Amplify/Greenify/etc.? Which governor do you use? What are your hotplug settings (i.e. CPU cores activated)? On what frequencies do your CPUs run?

vonotny said:
If you want help, you'll have to give MUCH more details about Boeffla settings, phone settings, apps you're using and general phone usage behaviour. Such as: WiFi or mobile data? Do you play power hungry games? Do you have lots of apps running in the background that use data or keep the CPU active? Do you use Xposed with Amplify/Greenify/etc.? Which governor do you use? What are your hotplug settings (i.e. CPU cores activated)? On what frequencies do your CPUs run?
Click to expand...
Click to collapse
Governor: Performance/ Standard for both A57 and A53
Scheduler : Deadline
Readhead Buffer : 2048
Phone usage : Just whatsapp facebook, basically general useage..
Wifi : on all day, Data : when away from wifi ( about 20 mins in a day)
Games : Not one, phone heats up
Background Apps : Not sure But generic apps I have been using
Xposed : yes greenifed most apps except messenger, whatsapp
GPU Governor : msm - adreno-tz
CPU Frequency : 1766 (A57) hotpulg min 2 max 4
CPU Frequency : 1555 (A53) hotpulg min 4 max 4
TIA

smarannss said:
Governor: Performance/ Standard for both A57 and A53
Scheduler : Deadline
Readhead Buffer : 2048
Phone usage : Just whatsapp facebook, basically general useage..
Wifi : on all day, Data : when away from wifi ( about 20 mins in a day)
Games : Not one, phone heats up
Background Apps : Not sure But generic apps I have been using
Xposed : yes greenifed most apps except messenger, whatsapp
GPU Governor : msm - adreno-tz
CPU Frequency : 1766 (A57) hotpulg min 2 max 4
CPU Frequency : 1555 (A53) hotpulg min 4 max 4
TIA
Click to expand...
Click to collapse
My bet is on the performance governor, as it always keeps the CPUs at max. frequency. This is a total waste of power and probably also the reason why your phone gets hot. Try Interactive (standard or battery unless you absolutely need the performance setting) or Impulse instead. Also, consider throttling the CPU frequency two to four steps for each cluster, and consider using only two cores on each cluster as you don't need all that power for general use.
You do know that you can set up different profiles in the Boeffla Config app, for different usage scenarios? For example, I have three profiles: for general use, for gaming, and for power saving when the battery gets low. This way, I can gradually control how much power I get and therefore also how much battery is used.

So you mean to say change the hotPlug to 2 to 4 ..?
And about the interactive mode, I was using it initially but I had keyboard lag so changed to performance...
Will try impluse and get back with the results..
Pretty much newbie in this .. so i am sorry to bother u

smarannss said:
So you mean to say change the hotPlug to 2 to 4 ..?
And about the interactive mode, I was using it initially but I had keyboard lag so changed to performance...
Will try impluse and get back with the results..
Pretty much newbie in this .. so i am sorry to bother u
Click to expand...
Click to collapse
You don't get keyboard lag from using the Interactive governor, no way.
Impulse is more on the battery saving side as compared to Interactive, and in Boeffla Interactive comes with multiple different settings that allow you to further fine-tune it to your liking. So imho, you can't go wrong with Interactive.
Don't be sorry, we're all here to learn and to share knowledge

vonotny said:
You don't get keyboard lag from using the Interactive governor, no way.
Impulse is more on the battery saving side as compared to Interactive, and in Boeffla Interactive comes with multiple different settings that allow you to further fine-tune it to your liking. So imho, you can't go wrong with Interactive.
Don't be sorry, we're all here to learn and to share knowledge
Click to expand...
Click to collapse
I saw a few posts related to this for OnePlus 2 and changed to interactive and battery Extreme.. I had a keyboard lag when I am using whatsapp when i shift from keyboard to smileys..
I am also using Synapse ....
And can u share me the settings that you are using ..

smarannss said:
I saw a few posts related to this for OnePlus 2 and changed to interactive and battery Extreme.. I had a keyboard lag when I am using whatsapp when i shift from keyboard to smileys..
I am also using Synapse ....
And can u share me the settings that you are using ..
Click to expand...
Click to collapse
So you were on battery extreme when the lag happened? Well, try battery, standard and performance as well and see what's best for you.
I'm currently experimenting with different settings. Right now, for general use I have
A53:
Governor: Interactive - Battery
Frequency: 384-960 MHz
Hotplug: 2 cores
A57:
Governor: Interactive - Battery
Frequency: 384-1344 MHz
Hotplug: 2/2
GPU:
Governor: msm-adreno-tz
Frequency: 27-450 MHz
It's a bit laggy especially on transitions, so I'm not sure if I'll stick to it. Also, stand-by time on mobile data doesn't really improve this way. Depending on whether I can get a bit more screen-on-time using this configuration, I'll decide whether to stick with it or not.
But in general, with Interactive - Standard and the default CPU and GPU configurations, you technically can't go wrong.

Cool I will check on this for the a couple of days and get back with results
Cheers

Stop messing with Kernel Settings. Kernel dont cause Battery drain. Use Better Battery Stats and find out which app is causing your drain. And stop using Greenify. It doesnt help much. In most cases it makes things worse.

update : 1 hr 41 mins SOT with 41% battery left...
I will uninstall the Greenify and check . Will also install BBS.
I noticed a battery drop when my location was on . I dont have any location intensive apps .

Even with battery extreme, i dont have lag with keyboard. Turn on your touch boost and set it to at least 768Mhz
No wonder you get 2Hrs SOT. Performance governor was only meant for benchmark, LoL
On impulse (A53) and Interactive extreme (A57)
My average SOT is 7Hrs, maxed at 9Hrs when my LTE reception at it best.
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
smarannss said:
update : 1 hr 41 mins SOT with 41% battery left...
I will uninstall the Greenify and check . Will also install BBS.
I noticed a battery drop when my location was on . I dont have any location intensive apps .
Click to expand...
Click to collapse
Google Play Services itself is a location intensive app. =b
Keep your greenify, but optimize it use.
Also install amplify and powernap,
And AppOpXposed to disable the keep awake permission from Google Play Services
Check my post on Battery Life thread for details.

Scherzengel said:
Stop messing with Kernel Settings. Kernel dont cause Battery drain. Use Better Battery Stats and find out which app is causing your drain. And stop using Greenify. It doesnt help much. In most cases it makes things worse.
Click to expand...
Click to collapse
otonieru said:
Even with battery extreme, i dont have lag with keyboard. Turn on your touch boost and set it to at least 768Mhz
Click to expand...
Click to collapse
otonieru said:
No wonder you get 2Hrs SOT. Performance governor was only meant for benchmark, LoL
On impulse (A53) and Interactive extreme (A57)
My average SOT is 7Hrs, maxed at 9Hrs when my LTE reception at it best.
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
Google Play Services itself is a location intensive app. =b
Keep your greenify, but optimize it use.
Also install amplify and powernap,
And AppOpXposed to disable the keep awake permission from Google Play Services
Check my post on Battery Life thread for details.
Click to expand...
Click to collapse
Update : No difference yet ,willing to experiment
Will check your post on battery
I have turned off the keep awake thingy on AppOpXposed for google Play Services ..
I did check BBS for any abnormal apps causing troubles but did not find any ... is there any thing that I need to look at in particular

Post some Screenshots of BBS statistics and maybe a BBS log file.
For testing here is my Config with Boeffla Kernel:
Governor Impulse Standard for both.
A53 max frequenzy is 1200 everything else untouched.
I/O is Zen with 2048 Read-Ahead
Hotplug is standard. A53: 4-4 A57: 2-4
GPU is 27-510
Touchboost is 1200 too.
Gives me 6-8 SOT.

Scherzengel said:
Post some Screenshots of BBS statistics and maybe a BBS log file.
For testing here is my Config with Boeffla Kernel:
Governor Impulse Standard for both.
A53 max frequenzy is 1200 everything else untouched.
I/O is Zen with 2048 Read-Ahead
Hotplug is standard. A53: 4-4 A57: 2-4
GPU is 27-510
Touchboost is 1200 too.
Gives me 6-8 SOT.
Click to expand...
Click to collapse
BBS ScreenShots

smarannss said:
BBS ScreenShots
Click to expand...
Click to collapse
This is Screenshots of my Kernel Tweaks ... I dont know much what happens here [ newbie]

smarannss said:
This is Screenshots of my Kernel Tweaks ... I dont know much what happens here [ newbie]
Click to expand...
Click to collapse
Screen Shots of Battery

Update the Kernel!!!!!!!!!! Beta 18 is out and you are on Beta 4. No wonder your system runs like crap. If you updated let it run for a few days and post again. And pls turn of this Battery extreme stuff ... And use standard hotplug Settings: 4-4 on A53 and 2-4 on A57.

Scherzengel said:
Update the Kernel!!!!!!!!!! Beta 18 is out and you are on Beta 4. No wonder your system runs like crap. If you updated let it run for a few days and post again. And pls turn of this Battery extreme stuff ... And use standard hotplug Settings: 4-4 on A53 and 2-4 on A57.
Click to expand...
Click to collapse
Download the beta18 file and flash right??

For all of those who are on the latest Kernel Version i packed my config into Boeffla Kernel profiles so you can use them easily.
The Boeffla-Impulse-Performance has the BCL driver and the possibility for the ROM to turn down Cores of the Big Cluster switched off. Gives me better Performance and i didn't recognized any big loss in Battery.
The Boeffla-Impulse-Battery has all set to stock logic. Gives maybe a bit more Battery.
Have fun with it.
ps.: Don't be afraid if your Screen Color changes. I made little changes in the Color settings. If you don't like them, you can always switch these values back to standard.