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!
Related
Q&A:
What is Overclocking??
Overclocking is running the cpu, and possibly other system components like memory, faster than the speed for which it was rated. It's not something to take lightly as it's something that actually can physically damage the phone.
What is Undervolting?
If you are performing CPU intensive tasks, you reap the most benefit from the UV kernel because it needs less power to run at 1 GHz (or whatever the maximum clock speed is set to for that kernel).
If you spend alot of time idling, for instance reading interspersed by web requests, you are spending most of your time at the minimum clock speed. With the stock kernel, that is set to 0.1 GHz. With a UV kernel, the minimum clock needs to be set to something higher to keep the CPU running.
What in the hell is BFS/CFS???
CFS: Completely Fair Scheduler - The original process scheduler. CFS is better for multitasking, BFS is better for user interactions
BFS: Brain F**k Scheduler - The updated and improved process scheduler of CFS. The scheduler is designed to offer low latency when used interactively
What in the hell is Noop/SIO/Others???
NO-OP: This scheduler only implements request merging.
SIO: Simple I/O Scheduler - SIO is like a lighter version of deadline but it doesn't do any kind of sorting, so it's aimed mainly for random-access devices (like SSD hard disks) where request sorting is no needed (as any sector can be accesed in a constant time, regardless of its
physical location).
CFQ: Completely Fair Queueing - The CFQ scheduler has always tried to divide the bandwidth of each block device fairly among the processes performing I/O to that device; the time-sliced version goes further by giving each process exclusive access to the device for a period of time.
BFQ: Budget Fair Queueing - BFQ is a proportional share disk scheduling algorithm, based on CFQ, that supports hierarchical scheduling using a cgroups interface
{
"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"
}
BFQ vs CFQ
Slowest task's bw (MB/s) Fastest task's bw (MB/s)
-------------------------------------------------------------------
BFQ (2 files) 9.81 +/- 0.47 9.95 +/- 0.43
CFQ (2 files) 8.61 +/- 0.67 11.92 +/- 0.44
-------------------------------------------------------------------
BFQ (5 files) 4.29 +/- 0.10 4.31 +/- 0.09
CFQ (5 files) 4.01 +/- 0.17 5.24 +/- 0.14
__________________________________________________________________________________________________________________________________
The voltage settings are going to be differ by each of us, but sharing some of your settings will help the "New" or any people to find their stable settings.
Ex:
Kernel Type: TW/AOSP
OTB version: 1.1b/1.2b/etc
Scheduler: cfq/bfq/sio/Noop/Deadline/etc
Settings: Highest to Least
7/09
ASOP
OTB 2.6.35.13 CFS 0704
BFQ
1500: -0
1400: -0
1300: -0
1200: -50
1000: -75
800: -75
400: -100
200: -100
100: -125
bfq scheduler, clocked to 1120 Mhz
1120 : -25
1000 : -25
800 : -50
600 : -50
400 : -75
200 : -125
100 : -150
Stable for 36hrs
1400 - 50
1300 - 50
1000 -50
800-0
400- 50
200 - 50
100 - 200
Noop also
Thoes are my settings test settings as of today so far so good XD
Sent from my SCH-I500 using XDA App
CFQ Scheduler
1200 - 0
1000 - 25
800 - 25
600 - 50
400 - 50
200 - 50
Still testing more aggressive settings but this has been 100% stable for me.
SIO scheduler. Clocked at stock 1000 Mhz
1000 : -75
800 : -75
600 : -75
400: -75
200: -125
100: -150
Testing for stability now, but it seems to be working great for now.
Its kinda weird but when I first flash the OTB I am not able to run voltages as low as I can after a few hours. Makes no sense to me but whatever.
My 100% of the time fail safe settings are:
1300 -75
1200 -25
1000 -50
800 -50
400 -75
200 -75
100 -75
With the above its always been perfect. Now as aforementioned after a short while I can adjust to these following voltages:
1300 -75
1200 -50
1000 -75
800 -75
400 -100
200 -125
100 -125
But again oddly if I try testing these right after a fresh kernel install I get some kind of freeze/lock up issue.
As always YMMV and truly you need to find what is stable for your own phone and the only way to do that is thru individual testing.
In terms of the scheduler I was mostly using cfq since OTB came out for voltage control but I have played with SIO and BFQ. IMO there is not a tangible difference
So what is the difference between the different schedulers? I see some people use SIO and some use CFQ. Is there a place I can go to read up on the differences?
xceebeex said:
So what is the difference between the different schedulers? I see some people use SIO and some use CFQ. Is there a place I can go to read up on the differences?
Click to expand...
Click to collapse
From the community rom thread:
http://forum.xda-developers.com/showpost.php?p=13209379&postcount=247
saps said:
From the community rom thread:
http://forum.xda-developers.com/showpost.php?p=13209379&postcount=247
Click to expand...
Click to collapse
Awesome, thanks. It is hard to find information in that thread with it being so long now
So BFQ is "supposed" to be the best, but it is one of those things where YMMV I am assuming.
BFQ Scheduler
1300 -75uv
1200 -50uv
1150 -50uv
800 -75uv
400 -75uv
200 -100uv
100 -150uv
Running good for a day!
Will update as I go.
xceebeex said:
Awesome, thanks. It is hard to find information in that thread with it being so long now
So BFQ is "supposed" to be the best, but it is one of those things where YMMV I am assuming.
Click to expand...
Click to collapse
Yeah YMMV always. In quadrant tests I get the highest IO scores with sio actually. Mind you its just a few dozen points higher which translates into just a few points higher overall. But it is consistently just a tad bit better than bfq and cfq which are dead end on my phone. After using cfq the past week Im currently on bfq since supposedly thats the one to have. In the end I believe it makes little difference
saps said:
Yeah YMMV always. In quadrant tests I get the highest IO scores with sio actually. Mind you its just a few dozen points higher which translates into just a few points higher overall. But it is consistently just a tad bit better than bfq and cfq which are dead end on my phone. After using cfq the past week Im currently on bfq since supposedly thats the one to have. In the end I believe it makes little difference
Click to expand...
Click to collapse
For general purpose phone use CFQ and BFQ are best, SIO is non time critical and only suitable for single purpose imbedded applications such as dedicated flash controllers where latency had much less importance than data throughput.
If audio and video causing hangs or stutters then CFQ or BFQ are absolutely required.
how are the stock settings on this kernel? UV? how much?
if i don't change anything is it a stock kernel or is there some inherent changes already built in?
saps said:
Its kinda weird but when I first flash the OTB I am not able to run voltages as low as I can after a few hours. Makes no sense to me but whatever.
My 100% of the time fail safe settings are:
1300 -75
1200 -25
1000 -50
800 -50
400 -75
200 -75
100 -75
With the above its always been perfect. Now as aforementioned after a short while I can adjust to these following voltages:
1300 -75
1200 -50
1000 -75
800 -75
400 -100
200 -125
100 -125But again oddly if I try testing these right after a fresh kernel install I get some kind of freeze/lock up issue.
As always YMMV and truly you need to find what is stable for your own phone and the only way to do that is thru individual testing.
In terms of the scheduler I was mostly using cfq since OTB came out for voltage control but I have played with SIO and BFQ. IMO there is not a tangible difference
Click to expand...
Click to collapse
I used these settings and have only had one freeze up (when using the camera and clicking on the preview tab). Thing FLIES.
I actually underclocked mine a little to 800. I prefer the battery life I guess.
800-50
600-75
400-75
200-125
100-125
Battery life still wasn't great lol
I switched over to a Peanut Butta Jelly Time kernel though at the moment to test that out.
gevis said:
I actually underclocked mine a little to 800. I prefer the battery life I guess.
800-50
600-75
400-75
200-125
100-125
Battery life still wasn't great lol
I switched over to a Peanut Butta Jelly Time kernel though at the moment to test that out.
Click to expand...
Click to collapse
Make sure after you find the voltage profile you like you reset the batt stats after you fully charge the battery
Sent from my SCH-I500 using XDA Premium App
Since i can not post in the DEV forum yet:
Thanks for this ROM, I upgraded from SC 2.9.2 and i am blown away by this fantastic, well built and fast ROM!
So once again thank all of you for all of your hard work!
saps said:
Make sure after you find the voltage profile you like you reset the batt stats after you fully charge the battery
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
thanks for that... didn't think about that
Anybody have updates with V1.3 they can share?
I use:
800-75
600-75
400-75
200-75
Underclocked, but the phone is still pretty snappy, and the battery life is awesome. My phone doesn't like 100mhz so I only go down to 200. Now what is this about wiping batt stats?
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
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?
Thank to @DooMLoRD, we have a powerful customized kernel allowing to improve the user experience with our Z2.
Current version: DooMKernel (v11)
This is the place to share and to discuss about our settings (allowed by DooMKernel). Please don't flood the kernel thread with such information, the right place is here.
First, it must be emphasized that the best tools to enable and tune the settings allowed by DooMKernel are:
- Fauxclock
- FauxSound
However, you can use others tools (such as Pimp my Z1, ...) and your feedback using these alternate tools will be welcome.
Currently, I use these Fauxclock settings (Updated sections in red - 13 Oct 2014):
- CPU Clock:
Min freq.: 300 MHz
Max freq.: 2.458 GHz (overclocked, see FAQ in post #2 for enabling overclocking permanently)
Governor: Intelliactive
- CPU Hotplug: Intelliplug - Profile: balanced - Touch boost enabled, or mpdecision for better perf. (see FAQ in post #2)
Intelliactive + Intelliplug = good performances +, very good battery life +++
Intelliactive + mpdecision = good performances ++, good battery life ++
Lagfree + mpdecision = very good performances +++, good battery life +
- Voltage tuning: -12 mV
Beyond this value, my device crashes (not necessarily the same for all devices). Stability can be tested with StabilityTest or Antutu benchmark.
Reducing the Votage is interesting for power saving and thermal management.
From a few reports, you could be 100% stable up to -48 mV.
- Thermal manager: Intellithermal (recommended by Faux)
Better than Thermald for 4K recording (look at my tests here)
Temperature threshold freq.: 70°C (158°F)
Temperature threshold core: 80°C (176°F)
- GPU manager: msm-adreno-tz - 578 MHz
Try these settings for great GPU performance!! And please give feedback.
- Sheduler I/O (eMMC & SDCard): row
- Readahead size (eMMC & SDCard): eMMC: 2048 - SD: 4096
- Colour / Gamma: not tested
- Memory manager:
VFS cache enabled
Automatic mode for writeback delay: enabled
- Same Page Merge: Intelli-KSM enabled
- FastCharge:
Battery Temperature Throttling: on
Battery throttle cpu frequency: 2457600
Fastcharge options: disabled - not tested
Currently, I use these FauxSound settings:
- Preset Profile: Quality
- Speaker gain: does not work
That's all. All is working perfect for me.
Compared to stock settings, about 2000 points are won on the Antutu Benchmark Score.
These settings will be updated and discussed in this post from your future reports.
FAQ:
- How to enable CPU overclocking permanently ?
Open Fauxclock,
go to fastcharge,
enable "Battery temperature throttling"
search "Battery throttle cpu frequency" & set it there up to "2457600",
activate "set on boot",
go back to cpu/hotplug,
set cpu at max,
and reboot.
Thanks to @MysticEnforcer for this tip.
- You experience lags listening eXistenZ modded Walman+sound enhancements ?
Use CPU hotplug mpdecision.
I find my phone freezes on boot when I use the intelliactive governor with sio.
Sent from my HTC One X using Tapatalk
KrisPerry said:
I find my phone freezes on boot when I use the intelliactive governor with sio.
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
That's strange... What rom do you use?
nreuge said:
Update of my settings: voltage tuning set from -48 mV to -24 mV for stability issues. Seems stable at -24 mV but needs confirmation.
Antutu benchmark is a good test to verify stability.
Click to expand...
Click to collapse
for me initially -72 mV was working but not stable... for now -60 mV is mostly stable, with a rare random reboot here or there
DooMLoRD said:
for me initially -72 mV was working but not stable... for now -60 mV is mostly stable, with a rare random reboot here or there
Click to expand...
Click to collapse
I was nearly stable at -36 mV with a rare random reboot here or there. Now, it's seems I'm 100% stable at -24 mV and I saw elsewhere that another user was stable at -48 mV. No luck for me... Anyway, all that confirms that each device behaves differently.
Stable at - 36
Sent from my D6503 using Tapatalk
If you want to get rid of micro stutter, try using one of the following cpu governors:
Lagfree, Smartass V2 or Lionheart
Games, launchers, Chrome etc. became much more responsive since I've switched.
Gesendet von meinem D6503 mit Tapatalk
deezid said:
If you want to get rid of micro stutter, try using one of the following cpu governors:
Lagfree, Smartass V2 or Lionheart
Games, launchers, Chrome etc. became much more responsive since I've switched.
Gesendet von meinem D6503 mit Tapatalk
Click to expand...
Click to collapse
have you done any specific governor tweaks?
can you share them with us?
DooMLoRD said:
have you done any specific governor tweaks?
can you share them with us?
Click to expand...
Click to collapse
No, didn't modify them.
There are laggy governors like: Ondemand, Interactive, Conservative, Intellidemand etc. and fast ones: Performance (no good solution), Lionheart, Smartass V2, Lagfree.
Just try it. Made my phone fly. Games like Temple Run Oz and Asphalt 8, which were unplayable before are working fine since I've using another governor (currently Lionheart). Feels like a Nexus 5 or HTC M8 now. Much better than stock!
Thanks for your great work!
Gesendet von meinem D6503 mit Tapatalk
I think I'll share my settings. This is not for those who expect ultimate power from their Z2's. I'm not a gamer, so this settings are for browsing the web and focused on battery performance.
Here we go:
Underclocked to 1728 ghz, governor intelliactive
CPU Hotplug: mpdecision (there's nothing we can do about that )
Voltage: -24 mV
Thermal: Intellithermal, frequency throttle 70 C, Core throttle: 65 C, all cores throttled
GPU: msm-adreno-tz 578 mhz, gpu rendering: on
I/O Schedulers: SIO for internal and external, cache 1024
Memory manager: Clear VFS cache after boot, rest on stock
Same Page merge: Intelli-KSM enabled
Low Memory Kill: why do i need those with 3gigs of ram?
FastCharge: Battery throttling: throttle at 50 C of bettery - throttle to 1267200
Battery lasts from 7am to 10pm with heavy use - 40% left. Stamina mode on all the time. Screen with auto brightness.
I'm using fauxClock. Smooth UI, fast browsing, no stuttering, fullhd camera works like charm. I'm not using 4k recoding and I haven't tested it.
Stable at -60 mv..
Sent from my D6503 using XDA Premium 4 mobile app
Is it better to turn mpdecision on or leave it off? I read somewhere that mpdecision overwrites the cpu governor settings.
GiGi. said:
Is it better to turn mpdecision on or leave it off? I read somewhere that mpdecision overwrites the cpu governor settings.
Click to expand...
Click to collapse
It's better to turn it on as there is no alternate manager for the moment.
amon87 said:
GPU: msm-adreno-tz 578 mhz, gpu rendering: on
Click to expand...
Click to collapse
How you turn on the GPU Rendering?
From Developer Options? Force GPU Rendering?
amon87 said:
GPU: msm-adreno-tz 578 mhz, gpu rendering: on
Click to expand...
Click to collapse
TheoDores said:
How you turn on the GPU Rendering?
From Developer Options? Force GPU Rendering?
Click to expand...
Click to collapse
In your opinion, what advantage is there in turning on GPU rendering?
I had tried it with my old Xperia T, but I hadn't noticed any difference...
deezid said:
No, didn't modify them.
There are laggy governors like: Ondemand, Interactive, Conservative, Intellidemand etc. and fast ones: Performance (no good solution), Lionheart, Smartass V2, Lagfree.
Just try it. Made my phone fly. Games like Temple Run Oz and Asphalt 8, which were unplayable before are working fine since I've using another governor (currently Lionheart). Feels like a Nexus 5 or HTC M8 now. Much better than stock!
Click to expand...
Click to collapse
@DooMLoRD
I've done several tests comparing different governors in term of power consumption. My screen was off and I was listening to music with Walkman.
Results (discharging rates):
Intelliactive: -2%/h
Lagfree: -3%/h
Lionheart: -4%/h
Smartass v2: -12%/h (big issue: freq. always at max)
So, Lagfree and Lionheart are probably more performant than Intelliactive (based on Ondemand) and more suitable for gamers but they are far more power hungry. So, this must be considered before choosing a governor.
There is patently an issue with Smartass v2.
nreuge said:
I've done several tests comparing different governors in term of power consumption. My screen was off and I was listening to music with Walkman.
Results (discharging rates):
Intelliactive: -2%/h
Lagfree: -3%/h
Lionheart: -4%/h
Smartass v2: -12%/h (big issue: freq. always at max)
So, Lagfree and Lionheart are probably more performant than Intelliactive (based on Ondemand) and more suitable for gamers but they are far more power hungry. So, this must be considered before choosing a governor.
There obviously an issue with Smartass v2.
Click to expand...
Click to collapse
Have seen the same, Smartass V2 is buggy and keeps the frequency at maximum (just like performance governor does).
Lagfree seems to be the best compromise, it works pretty well in games.
Gesendet von meinem D6503 mit Tapatalk
deezid said:
No, didn't modify them.
There are laggy governors like: Ondemand, Interactive, Conservative, Intellidemand etc. and fast ones: Performance (no good solution), Lionheart, Smartass V2, Lagfree.
Just try it. Made my phone fly. Games like Temple Run Oz and Asphalt 8, which were unplayable before are working fine since I've using another governor (currently Lionheart). Feels like a Nexus 5 or HTC M8 now. Much better than stock!
Thanks for your great work!
Gesendet von meinem D6503 mit Tapatalk
Click to expand...
Click to collapse
Very hard on battery though
Sent from my D6503 using Tapatalk
deezid said:
Have seen the same, Smartass V2 is buggy and keeps the frequency at maximum (just like performance governor does).
Lagfree seems to be the best compromise, it works pretty well in games.
Gesendet von meinem D6503 mit Tapatalk
Click to expand...
Click to collapse
KrisPerry said:
Very hard on battery though
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
I think that Interactive should be good for games and not too power hungry. However, presently, it seems incorrectly parametirized: using it, I can hear few scratching noises listening to music in Walkman (and also with Ondemand)!! I'll see what I can do.
Hi guys, I'll make this short and sweet. A few years ago, I stumbled on this little guide for the Interactive governor, which made a lot of changes in CPU scaling and has spread to many devices.
To make a long story short, OEMs usually ramp up your CPU to more than what is needed to ensure smooth performance. This guide, changes that by ramping up your CPU to the minimum amount needed to get the same effect. The result? Lower frequencies used equals more power saved without impacting performance.
It's like a car race. If you take on a tight corner at high speed, you go in fast but you still need to slow down or risk crashing. But if you decelerate to just the right speed, you consume less energy while ensuring not much of your acceleration is sacrificed in the process.
This will be the best time to release this thread because we now have our voltage values from the kernel source, which provides the real change in these tweaks.
Calculations and stuff
We take the voltage values, and see what gives the highest jump when switching frequencies.
Code:
1401 MHz to 1689 MHz = 5v increase
1958 MHz to 2016 MHz = 75v increase
We don't care about the small increase, as they are negligible. The real drains are in the huge jumps in voltage.
So, we have the following frequencies with large differences when they jump:
652 MHz = 75v
1036 MHz = 70v
1843 MHz = 70v
1958 MHz = 75v
Then, we take into account the minimum frequency to ensure smooth tasks:
Idle = 652 MHz
Scrolling = 1036 MHz (Use Chrome browser to scroll Facebook in desktop mode)
Video = 1401 MHz (Play 1080p*60fps videos in Youtube app)
App load = 1843 MHz (Use any app really)
High load = 2016 MHz (Max out just in case)
I will be skipping explaining all the formulas and maths but you're welcome to check them out in the original thread and refer it to our frequencies + voltage
CPU Load:
652 MHz = 57
1036 MHz = 67
1401 MHz = 75
1689 MHz = 9
1843 MHz = 85
1958 MHz = 87
Soooo what now?
I'll be taking their Hawktail profile, as it seems to work the best. Any newer profile from that thread is built specifically for the Nexus 5x.
You should use a kernel manager app to implement these values, I recommend Kernel Adiutor Mod if you want free, or you can pay for EXKM made by one of the more senior developers in XDA.
Code:
go_hispeed_load: 95
above_hispeed_delay: 0
timer_rate: 60000
hispeed_freq: 652800
timer_slack: 480000
[B]target_loads: [/B] 80 652800:57 1036800:67 1401600:22 1689600:84 1804800:83 1958400:87
min_sample_time: 0
ignore_hispeed_on_notif: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
Hopefully it helps you as it seems to help me. Discussion is more than welcome here, as these are just rough calculations that isn't fine tuned yet for our CPU.
Additionally, open a terminal emulator app and type these:
Code:
su
stop perfd
This will prevent the Qualcomm binaries from taking over the CPU scaling and leave it up to the governor instead.
Can you make an exkm loadable profile for absolute noobs like me .
Sent from my Redmi Note 4 using Tapatalk
dastan4eva said:
Can you make an exkm loadable profile for absolute noobs like me .
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I hope this works. Rename .txt to .HT.
I'll test and report back
Hi, these settings apply to both the little and the big cluster or just one of those?
Sent from my Redmi Note 4 using Tapatalk
antimatter.web said:
jesus christ
Hi, these settings apply to both the little and the big cluster or just one of those?
Click to expand...
Click to collapse
Why the heck did you have to quote the entire thing? Remove it.
And these settings will apply on both, the kernel doesn't support per CPU
AutumQueen92 said:
Why the heck did you have to quote the entire thing? Remove it.
And these settings will apply on both, the kernel doesn't support per CPU
Click to expand...
Click to collapse
Sheesh, mind your tone, would you?
Sent from my Redmi Note 4 using Tapatalk
Going back on topic: These settings seem pretty great! Currently off the charger for 47 hours with +5 hours SOT and 30% left! LOS 14.1 with autumnQueen92 kernel tweaks. All radios active too [emoji106] [emoji15]
{
"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 Redmi Note 4 using Tapatalk
antimatter.web said:
Going back on topic: These settings seem pretty great! Currently off the charger for 47 hours with +5 hours SOT and 30% left! LOS 14.1 with autumnQueen92 kernel tweaks. All radios active too [emoji106] [emoji15]
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Sounds good. What was your previous SOT like?
Well, before that I had the Helio X20 variant and it would rarely last 24 hours with ~6 hours SOT.
With the Snapdragon variant on miui 8.2.5.0 global I got about 8 hours SOT over 36 hours. I then switched to LOS. 14.1 after a single cycle. This certainly seems to be an improvement in both standby and in-use consumption.
Sent from my Redmi Note 4 using Tapatalk
May be error in this line 80 652800:57 1036800:67 1401600:75 1689600:8 1843200:85 1958400:87, as i think it must be 1689600:80, or i'm wrong?
alexeei said:
May be error in this line 80 652800:57 1036800:67 1401600:75 1689600:8 1843200:85 1958400:87, as i think it must be 1689600:80, or i'm wrong?
Click to expand...
Click to collapse
Nope, it's correct. It'll be more efficient to skip that frequency instead since the voltage jump isn't high.
And one more question, we need apply part "su stop perfd" every time after reboot or it's need once?
alexeei said:
And one more question, we need apply part "su stop perfd" every time after reboot or it's need once?
Click to expand...
Click to collapse
You can disable perfd using ex kernel manager latest, but i use mi5 i dont know if same like reno4
alexeei said:
And one more question, we need apply part "su stop perfd" every time after reboot or it's need once?
Click to expand...
Click to collapse
Each time you reboot.
go_hispeed_load: 95
above_hispeed_delay: 0
timer_rate: 60000
hispeed_freq: 652800
timer_slack: 480000
target_loads: 80 652800:57 1036800:67 1401600:75 1689600:9 1843200:85 1958400:87
min_sample_time: 0
ignore_hispeed_on_notif: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
@AutumQueen92 after applying these values kernel adiutor shows Max CPU frequency 1689Mhz
Sent from my Redmi Note 4 using Tapatalk
antarix said:
go_hispeed_load: 95
above_hispeed_delay: 0
timer_rate: 60000
hispeed_freq: 652800
timer_slack: 480000
target_loads: 80 652800:57 1036800:67 1401600:75 1689600:9 1843200:85 1958400:87
min_sample_time: 0
ignore_hispeed_on_notif: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
@AutumQueen92 after applying these values kernel adiutor shows Max CPU frequency 1689Mhz
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Can you set the max to 2016 MHz? I've never heard of this problem before, so I'm not sure why it's behaving this way. Could be a problem with the app itself.
antarix said:
go_hispeed_load: 95
above_hispeed_delay: 0
timer_rate: 60000
hispeed_freq: 652800
timer_slack: 480000
target_loads: 80 652800:57 1036800:67 1401600:75 1689600:9 1843200:85 1958400:87
min_sample_time: 0
ignore_hispeed_on_notif: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
@AutumQueen92 after applying these values kernel adiutor shows Max CPU frequency 1689Mhz
Click to expand...
Click to collapse
May be you make some error, apply in Kernel adiutor also, and max frequency same as it was-2016mhz
antarix said:
go_hispeed_load: 95
above_hispeed_delay: 0
timer_rate: 60000
hispeed_freq: 652800
timer_slack: 480000
target_loads: 80 652800:57 1036800:67 1401600:75 1689600:9 1843200:85 1958400:87
min_sample_time: 0
ignore_hispeed_on_notif: 0
boost: 0
boostpulse_duration: 0
align_windows: 1
use_migration_notif: 1
use_sched_load: 0
max_freq_hysteresis: 0
@AutumQueen92 after applying these values kernel adiutor shows Max CPU frequency 1689Mhz
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Open kernal auditor > Thermal > disable VDD restriction .
You r good to go
AutumQueen92 said:
I hope this works. Rename .txt to .HT.
Click to expand...
Click to collapse
How do you use this .HT file, with EX Kernel Manager?