Database Users

Effects of CPU Frequency and Screen Brightness on Power Consumption

I've recently been curious as to how much influence my chosen CPU frequencies and screen settings have on power usage. Of course, it is common knowledge that an overclocked processor requires more current and that our displays are power hungry, but how apparent is the difference? Is the relationship between these variables and battery consumption linear, or is the increase in power demand perhaps exponential?
In an effort to explore these questions, I set up a controlled test that logged CPU frequency and screen brightness against current usage. This data should not be assumed to directly apply to all Incredibles; I was looking for correlations rather than exact calculations on how much energy a specific setting uses.
Methods (go ahead and skip down to the findings section if this is too dry for you)
AMOLED Inc
Kernel: Chad's 2.6.37.1-incredikernel-gb-2272011
ROM: CyanogenMod 7 - Nightly #11
And not that it should matter, but someone will ask so...
Radio: 2.15.00.11.19
HBOOT: 0.92
Recovery: ClockworkMod 3.0.0.8
CPU frequencies were controlled using SL4A scripts and Tasker. Max frequency can be manipulated through /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq, so a single echo command is all that is needed to adjust it. I set up a rudimentary if/then script to bump up the max frequency one notch at a time, then used Tasker to execute this script every two minutes.
When Tasker would execute the script, it would also write an entry to a log file shared with CurrentWidget. This ensured that the CPU frequency was being noted between milliamp readings. Multiple readings were taken at each level, and entries that immediately preceded or followed clock changes were discarded in an effort to use the more stable readings at each frequency.
To control for other influences, all other phone services were disabled, including GPS, Wi-Fi, and Bluetooth. The phone was also placed in Airplane Mode so that reception was not a factor.
The CPU governor was set at "performance," ensuring that it remained at its max frequency. To task the CPU, I put together another simple script which just ran md5sum commands in a never-ending loop. Before recording data, I verified that this script was enough to load the CPU and cause it to scale up to max frequency when using other governors.
The full range of frequencies was tested at the screen's dimmest factory setting (20/255) as well as the screen's brightest setting (255/255). Additionally, a separate test was run with the CPU fixed at 576 MHz and Tasker periodically bumping up the screen brightness.
Findings
My data showed an almost perfect linear correlation between clock speed and power use, as well as brightness and power use.
I was a little surprised at how big of a difference I was able to find. With the screen at its dimmest setting, 128 MHz consumed ~80 mA while 1,113 MHz consumed more than 300 mA. For a stock Inc battery (1,300 mAh) that marks the difference between (over) 16 hours of runtime and less than 4.5 hours of runtime. Of course, anyone who has tested the limits of underclocking knows that the phone is utterly useless at 128 MHz.
The influence of brightness was less of a surprise. At a given CPU frequency, the average difference that I noted between min screen brightness and max screen brightness was ~118 mA.
{
"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"
}
I would love to be able to test every single combination of CPU frequency and screen brightness, but it would take hours, and I cannot keep my phone out of use for that long. I did generate some additional projections, however, based on the trends observed in the combined tests. I've added these projected points to the graph below, based on screen settings of 80/255, 140/255, and 200/255.
Shortcomings / questions for further exploration
Given the sterile nature of the data collection, I can't just make a blanket statement like "underclocking your max CPU to 883 MHz will yield an average of 15% more battery life over leaving it set to 998 MHz." As convenient as it would be to make such a claim, it ignores a number of realities. None of us are using 100% of our processor at all times, so a more accurate prediction of runtime would need to take the phone's resting behavior into account.
We should also consider that the CPU's frequency will affect the speed at which it can perform tasks. If you clock your processor too low, you may actually end up consuming more power since your phone will have to work longer (resulting in more wake time and more screen-on time).
A more technically inclined member may want to chart CPU frequencies against power usage, while also including some sort of performance benchmark. Such a matrix would offer users an even better model on which to judge the cost/benefit of over or underclocking. But even the simple testing which I've completed above takes a fair amount of time and keeps the phone from being otherwise used, so it's not a very convenient thing to test.
What I find most interesting about the data is the implication that a user who overclocks his CPU max to 1,113.6 MHz and sets his screen brightness to 80 could use less power than a user who underclocks his CPU max to 883 MHz but uses a brightness of 200.
The easiest takeaway, of course, is an illustration of why users experience such wildly different run times on the same rom/kernel setup. Again, this should come as no surprise, but skepticism should be exercised any time someone promises you that switching to a specific rom/kernel combo will guarantee you X hours of battery life.
[This work may be freely distributed for non-commercial purposes, as long as it is passed along unchanged and in whole, with credit to author and a link back to this XDA thread.]

Wow, this is a shocker. I guess I should kill the habit of using higher brightness and be less afraid to OC.

pianoplayer said:
Wow, this is a shocker. I guess I should kill the habit of using higher brightness and be less afraid to OC.
Click to expand...
Click to collapse
I notice you have an SLCD DInc. It's worth mentioning that mine is AMOLED and I don't know if the two have similar power usage across the brightness scale.

byrong said:
I notice you have an SLCD DInc. It's worth mentioning that mine is AMOLED and I don't know if the two have similar power usage across the brightness scale.
Click to expand...
Click to collapse
Wow, I didn't notice that. I guess you're right. I read somewhere that darker themes help on AMOLED and lighter themes are better for battery on SLCD. My theme is quite light so I think that makes my on the less-consuming side for the screen.

byrong, this is awesome data. Just what I needed to see, thank you. I have the exact same setup and have been trying to figure out the best cpu/brightness settings for my device. With seeing this data its helped me determine some of the values I was going back and forth on. Now I guess I'll have to wait and see how my battery holds up.

Excellent. Thanks for the data. Even if I never put any of that into use it's still fun for the nerdy part of me (most of it ) to know! Excellent data, and just goes to show how important screen brightness is over the CPU Speed. Most users would probably get better battery life if they spent more time darkening the screen than installing a CPU governing program haha.

Great info! Kinda knew this already but cool to see it all graphed out.

Thank you for the graphs! I have the SLCD... but I think the results would be similiar regardless of screen type, especially in real-world usage.

Awesome work. Gives me some ideas about using setcpu...

Chad give me more description... what new features are in the new kernel....
Sent from my ADR6300 using XDA App

Gorilla* said:
Chad give me more description... what new features are in the new kernel....
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Ummm? It will enable you easier entrance/exit from the matrix.
Nice work btw byrong.

Horay for empiricism!
Thanks for the legwork and for sharing. Impressive.
[I for one welcome our new Android overlords ::: DInc::SLDC::x.7.28::CWM3.0.0.8::CM7::chad's]

phaze one said:
Ummm? It will enable you easier entrance/exit from the matrix.
Nice work btw byrong.
Click to expand...
Click to collapse
Aren't we calling it "the Grid" now?
[I for one welcome our new Android overlords ::: DInc::SLDC::x.7.28::CWM3.0.0.8::CM7::chad's]

Byrong,
Fantastic write up as always..
I'm curious if you would care to do one on the effects of a task killer on battery life/CPU and RAM usage?
Since Android launched cupcake, I've been strongly opposed to the use of task killers, as Android handles processes much better than we do.. but I would love to see if fact can back up that opposition or if these apps truly don't cause any harm.
I'm just not nearly as amazing with words and data as you clearly are.
via Incredible Redemption

Man, I wish I hadn't just given my mom my DInc and instead played with it some more. I would love to help do some more long term tests to help with this.
That and seeing the variation for screen type, mine being an SLCD.
Sent from my TBolt using XDA

Thank you all for the kind words.
AdhvanIt said:
I'm curious if you would care to do one on the effects of a task killer on battery life/CPU and RAM usage?
Click to expand...
Click to collapse
Great idea.
I'm game, but I would have to think long and hard about how to design the testing parameters. In all likelihood, I'd need some suggestions / ideas from you guys to carry out such a test.
I would need recommendations on a reliable logging program for RAM, CPU Freq, and CPU Load.
Unlike most of my other power testing, I would not want to run such a test in Airplane mode. One of the reasons that people give for aggressive task-killing is shutting down processes that may be using data in the background. As such, I would need conditions that actually allowed an observable difference in data usage.
Since the phone won't be in Airplane mode, my controls take a big hit. During a test, for example, I might receive a lot of calls, texts, and emails, all of which will have a major impact on CPU, RAM, and battery. The cleanest solution I can see is running the test across multiple nights: X full nights without a task-killer and X full nights with one.
The other big question is how to set up the task killer. I.E. should I allow it to kill everything, or set up an exclusion list? I'm leaning towards the exclusion list, but then we have to decide what to exclude. We should also think of a designated interval for the task killer.
If you want to help me brainstorm these issues, I'm happy to discuss them right in this thread.
TodesEngeI said:
Man, I wish I hadn't just given my mom my DInc and instead played with it some more. I would love to help do some more long term tests to help with this.
That and seeing the variation for screen type, mine being an SLCD.
Sent from my TBolt using XDA
Click to expand...
Click to collapse
The beauty of this type of testing is that it can be done by any motivated individual, on any device that allows scaling of the CPU. If you already have that new TBolt of yours rooted, you should be able to recreate the tests on that. I'm sure fellow TBolt users would love to see your findings.

byrong said:
Thank you all for the kind words.
Great idea.
I'm game, but I would have to think long and hard about how to design the testing parameters. In all likelihood, I'd need some suggestions / ideas from you guys to carry out such a test.
I would need recommendations on a reliable logging program for RAM, CPU Freq, and CPU Load.
Unlike most of my other power testing, I would not want to run such a test in Airplane mode. One of the reasons that people give for aggressive task-killing is shutting down processes that may be using data in the background. As such, I would need conditions that actually allowed an observable difference in data usage.
Since the phone won't be in Airplane mode, my controls take a big hit. During a test, for example, I might receive a lot of calls, texts, and emails, all of which will have a major impact on CPU, RAM, and battery. The cleanest solution I can see is running the test across multiple nights: X full nights without a task-killer and X full nights with one.
The other big question is how to set up the task killer. I.E. should I allow it to kill everything, or set up an exclusion list? I'm leaning towards the exclusion list, but then we have to decide what to exclude. We should also think of a designated interval for the task killer.
If you want to help me brainstorm these issues, I'm happy to discuss them right in this thread.
Click to expand...
Click to collapse
SetCPU has a lot of the logging/current system information that you would need, including:
CPU frequency: Time in state for each freq
CPU load average
Total and available RAM
As well as a number of other things. Screenshots are attached below.
As for controls, I would think auto kill at screen wake is a commonly used setting. Or maybe go at 1/2 to one hour intervals...
If you're going to set up a blacklist within the task-killer, I would recommend not adding too much to it, as the exclusion of too many apps would alter test results. But certainly add any auto-updating widgets you have to it.
I think leaving data on is also appropriate for this test-there are a number of apps that will not start/update (mostly web based like twitter/facebook and such widgets) if there is no data connection.
Edit: Forgot to add images. Lol.

AdhvanIt said:
SetCPU has a lot of the logging/current system information that you would need, including:
CPU frequency: Time in state for each freq
CPU load average
Total and available RAM
Click to expand...
Click to collapse
The info tab in SetCPU is indeed helpful for more of a 'snapshot view', but I don't know of a way to make it log that information to a text file over time, do you?
Time in state is helpful, and can be accessed via:
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
But the problem is that it doesn't tell the story of when the CPU was scaling. It would be far more useful if I could plot CPU load and CPU freq over a time line, rather than just have averages or sums.
Same story with RAM: I want to be able to plot over the course of time.
AdhvanIt said:
As for controls, I would think auto kill at screen wake is a commonly used setting. Or maybe go at 1/2 to one hour intervals...
Click to expand...
Click to collapse
I like to automate my tests as much as possible, not only to (try to) remove myself as an influence, but so that I'm not tied to the phone for hours at a time, looking at a watch. If I did a screen on/off setting, it would require me to turn the screen on and off at select times, remaining consistent between tests.
So intervals would definitely be the way for me to go. I think I'll start a poll of some sort to get an idea of how most people set theirs.
AdhvanIt said:
If you're going to set up a blacklist within the task-killer, I would recommend not adding too much to it, as the exclusion of too many apps would alter test results. But certainly add any auto-updating widgets you have to it.
Click to expand...
Click to collapse
Agreed that I want to keep the exclusion list to a minimum. I will make this part of my poll as well. I don't want to create a strawman position by setting up the task killer to be more aggressive than anyone actually uses it. For example, I don't want to set it to kill Android OS, Launcher, etc, as that would just be excessive and probably does not reflect how anyone uses them.
This will be an extremely controversial one, and if I don't strike a delicate balance, people will be quick to throw out the data completely on the grounds of, "Well that's fine and all, but that's not how I use my Task Killer."
Thanks for helping me think this through.

byrong said:
The info tab in SetCPU is indeed helpful for more of a 'snapshot view', but I don't know of a way to make it log that information to a text file over time, do you?
Time in state is helpful, and can be accessed via:
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
But the problem is that it doesn't tell the story of when the CPU was scaling. It would be far more useful if I could plot CPU load and CPU freq over a time line, rather than just have averages or sums.
Same story with RAM: I want to be able to plot over the course of time.
I like to automate my tests as much as possible, not only to (try to) remove myself as an influence, but so that I'm not tied to the phone for hours at a time, looking at a watch. If I did a screen on/off setting, it would require me to turn the screen on and off at select times, remaining consistent between tests.
So intervals would definitely be the way for me to go. I think I'll start a poll of some sort to get an idea of how most people set theirs.
Agreed that I want to keep the exclusion list to a minimum. I will make this part of my poll as well. I don't want to create a strawman position by setting up the task killer to be more aggressive than anyone actually uses it. For example, I don't want to set it to kill Android OS, Launcher, etc, as that would just be excessive and probably does not reflect how anyone uses them.
This will be an extremely controversial one, and if I don't strike a delicate balance, people will be quick to throw out the data completely on the grounds of, "Well that's fine and all, but that's not how I use my Task Killer."
Thanks for helping me think this through.
Click to expand...
Click to collapse
Definitely makes sense to automate...
I'm not really sure of any way to log these things regularly unless you know how to set up a script and have it pull the logs every so often...
Agreed-It will likely get met with debate regardless, as it's always had its fanbase and its opposition. Not sure really how to get a good balance, but I think the polls are a good way to start.

Survey is up: http://www.surveymonkey.com/s/8GD2F2H
(Posted here to reach a wider audience: http://forum.xda-developers.com/showthread.php?t=1032456)
I decided to keep it as simple as possible, both to encourage more people to respond, and to simplify the collection of responses.

Flickering/Brightness/ Charging Permanent Fix

To the extent that flickering and low charging is related to Sony thermanager, here is the permanent fix for AOSP/CM based roms. While the idea of thermal manager is good and we should credit Sony for doing it, the implementation kind of s*cks. For example, the manager kicks in when CPU/GPU temperature rises to 44 degrees. Also, several triggers are set between 54-56 degrees. This is plain wrong, because 44, 50 and 55-56 are all perfect numbers for an active device and at these temperatures, thermal manager should not be active. I have adjusted trigger numbers so that there will be no mitigation until at least 60 and surprise surprise, all screen flickering is gone away....
Attached is thermanager.xml which should be put in /system/etc/ with 644 permissions. Reboot is required. UNZIP FIRST. Also, backup your current file just in case.
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..

Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1

sgspluss said:
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
Click to expand...
Click to collapse
Any touch issues related to thermanager kicking in early could be resolved. But lollipop has overheating issues related to art, which can't be solved by thermal management. That's why strictly speaking, lollipop has to be recalled. In my view it can't be fixed.

A little question
Hello optimumpro
I only need put the thermanager in the path system/etc to make it work? or need something else?. Sorry by the queastion I noob an recently I repair de display and touchscreen for my xperia z1 C6902 and a have the flickering problem.
Thanks for your help.

optimumpro said:
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Click to expand...
Click to collapse
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.

This works for me!
before flash this file, my Phone only receives 90ma from any changer, and now reciving 1080ma. Thanks a lot!
Room: Ressurection Remix
Android version: 5.1.1, Xperia Z1 C6943
Sent from my Xperia Z1 using XDA Free mobile app

Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
Sent from my C6903 using Tapatalk

agha_jo0n said:
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
View attachment 3434889
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I don't think that app is accurate tbh with the fix it says no higher than 300ma for me and my phone is charging pretty well I'm using 2100ma charger as well
Sent from my Xperia Z1 using Tapatalk

Sorry bro but i don't have this file in system /etc??? Wtf???

ninjasoft said:
Sorry bro but i don't have this file in system /etc??? Wtf???
Click to expand...
Click to collapse
You are probably on kitkat. If that's the case, you don't need thermanager. If you are on lollipop, look again, the files are not necessarily in alphabetical order...
And remember, this one is for custom roms: CM and/or AOSP based. I just looked at your signature, you have stock...

zhuoyang said:
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
Click to expand...
Click to collapse
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.

optimumpro said:
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
Click to expand...
Click to collapse
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?

zhuoyang said:
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
Click to expand...
Click to collapse
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.

optimumpro said:
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
Advantages of undervolting Android
Thank God for Android where we can easily modify and customize our lovely Android devices to the way we want. Being said this, undervolting is one of the biggest attraction for Android! Simply by undervolting an Android you will or might experience:
A longer battery life
More responsive smartphone
Less heat produced by the phone
Super-charge your Android to go further than what it can do (overclocking Android)
Click to expand...
Click to collapse
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
Note: UnderVolting is widely used as a cooling solution and in my opinion more effective than any other cooling solution available for free. Results can will show decrease in the temperature of smartphone. I recommend undervolting to anyone with enough confidence and knowledge to do so. The benefits easily outweigh the risks. I dont see why one shouldn’t do this for a cool and better smartphone experience.Undervolting will NOT compromise performance at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1956346
Undervolting is actually a very good thing for your smart phone when you do it correctly. Undervolting has one major positive effect on your CPU: it will extend the life of your processor by allowing it to do demanding things with lower heat generation
Click to expand...
Click to collapse

zhuoyang said:
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
http://forum.xda-developers.com/showthread.php?t=1956346
Click to expand...
Click to collapse
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.

optimumpro said:
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
Click to expand...
Click to collapse
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.

zhuoyang said:
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
Click to expand...
Click to collapse
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .

optimumpro said:
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
Click to expand...
Click to collapse
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?

zhuoyang said:
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
Click to expand...
Click to collapse
"I am not attacking you" Yes you were, I said that some bloggers don't know what they are talking about and you replied that I didn't know what I was talking about. Anyway, I accept your veiled apology.
Neither overvoltage nor undervoltage makes the phone cooler. There is an optimal regime for each cpu and if you go outside of it (in either direction), you are inviting trouble. You are not going to destroy your cpu by either under or over voltage, as there is protection in kernel. The phone runs cooler when cpu works less and the optimal regime causes the cpu work less. If you are reducing juice (voltage), you make cpu work longer, which results in overheating.
I gave you an example of performance governor to make a point that this is counterintuitive: while cpu is set at the higher frequencies, it actually performs the tasks and rushes to idle faster, which results in cooler condition. When the same cpu is set lower (and especially if it is under volted), it works longer, jumps to different frequencies, plugs/unplugs cores, which all contributes to overheating....

What is normal values for this phone ? I have diferent chargers, Samnsung - around 600mA, one HTC - around 400mA and another one with 200mA according to that app. Wich one should i use ? So far i used samsung one because it charges fast...2 hours or less, but the battery dies also fast ....so it may be because of the charger ?

[GUIDE] Tweaking Interacting Gov

Hey guys, Kyuubi10 back once again with another Guide.
I thought it might be useful to pop in a couple results of my trial and error for the HTC One M8.
Note: This is not scientifically, calculated accurate, but it's close enough, based on estimates.
After following these guides:
http://forum.xda-developers.com/showthread.php?t=2769899
https://vjnaik.wordpress.com/2015/06/25/kernel-tweak-interactive-governor-paramaters-rooted-phone/
I decided to make a summary guide of the above but with specific HTC One M8 values.
Since I agree with the idea of "race to idle" embodied in the Wheatley governor, I tried emulating that on the Interactive governor while also keeping it as efficient as possible.
Here are the values (all others not mentioned, leave default):
Code:
[B]above_hispeed_delay [/B]- 80000 2265600:10000
[B]go_hispeed_load[/B] - 95
[B]hispeed_freq[/B] - 1728000
[B]io_is_busy[/B] - 1
[B]min_sample_time[/B] - 10000
[B]target_loads[/B] - 45 729000:80 883200:50 1267000:85 1497600:50 1728000:90 1958400:50
[B]timer_rate[/B] - 10000
[B]timer_slack[/B] - 5000
"above_hispeed_delay" makes sure that longer time is spent on the frequency step 1.72Ghz, before quickly raising higher into max freq.
1.72Ghz is the most energy efficient frequency with a good performance, e.g. it will not cause lag during casual usage, while it uses minimal voltage.
If the load is too high for this frequency to handle, I set the time short once it's gone over this freq step so that it will not waste time before reaching max freq. Thus dealing with the issue asap.
Another important parameter is "target_load", with this I have defined that at each efficient freq step the load needed to overcome it would be higher than normal. But it would up-scale quickly when using non-efficient frequencies.
The other parameters I have set so that the frequency is lowered as soon as CPU load is finished, so that it will rush back to idle as quickly as possible.
The interesting thing about this set-up is that for general, non heavy usage, it basecally functions as if I have underclocked to 1.72Ghz, but when the CPU is truly pushed it reaches up to 2.5Ghz which is my Overclocked max freq value.
Thus both saving battery and providing high performance.
I have felt no lag, and it's been quite a smooth experience while I used this
Combined with using GPU rendering (found in developer settings), and Seeder, the over all usage is pretty good.
Battery usage has been very efficient and I have managed to squeeze out an extra hour or two using this.
I highly recommend it!
Hope I helped you guys... don't forget to press the thanks button if you also feel that I did!:good::good:

I noticed I have some governor settings left at 0 or blank. I did some quick googling, found some other tweaks for the M8 and the interactive governor. So I played around a bit, and I think the following would be useful to add to the above tweaks.
-----------------------
sampling_down_factor: 60000
sync_freq: 1036800
up_threshold_any_cpu_load: 65
up_threshold_any_cpu_freq: 1190400
boost: 0
boostpulse_duration: 80000
--------------------
Also of note there is not a entry for " io_is_busy " under the Interactive governor under ElementalX Sense kernel v6.03. I believe it's possible to modify the governor to add the function, if it's desired.
Hope this helps others.

nice one i read the links that you posted and follow the guides there also to tweak the interactive governor on the first link that you posted is really interesting he has updated that post also, i followed his guide inspired by your guide and i have been getting good results on my phone with battery and performance i mean almost no battery drain at all while my phone is idle. thanks for the help mate!

Plugged the settings into Yankactive on DU. Quick, freqs stay low when nothings going on, seems legit. I set my timer_rate higher tho, 10000 feels a little low, makes me think that the CPU will spend too much time polling loads.

SaskFellow said:
I noticed I have some governor settings left at 0 or blank. I did some quick googling, found some other tweaks for the M8 and the interactive governor. So I played around a bit, and I think the following would be useful to add to the above tweaks.
-----------------------
sampling_down_factor: 60000
sync_freq: 1036800
up_threshold_any_cpu_load: 65
up_threshold_any_cpu_freq: 1190400
boost: 0
boostpulse_duration: 80000
--------------------
Also of note there is not a entry for " io_is_busy " under the Interactive governor under ElementalX Sense kernel v6.03. I believe it's possible to modify the governor to add the function, if it's desired.
Hope this helps others.
Click to expand...
Click to collapse
Some of those actually make no difference. Since they are overruled by other perameters. E.g. up_threshold aren't used in interactive, since they follow target_load instead.
Sampling_down_factor on the other hand is overrulled by the timer features of interactive.
When you use ondemand, or conservative, sampling_down_factor is a fun parameter to play with, but not interactive.
While Sync_Freq I don't like using because it raises minimum frequency to its value...although temporarily, the timer features can already deal with CPU loads efficiently.
lil_kujo said:
nice one i read the links that you posted and follow the guides there also to tweak the interactive governor on the first link that you posted is really interesting he has updated that post also, i followed his guide inspired by your guide and i have been getting good results on my phone with battery and performance i mean almost no battery drain at all while my phone is idle. thanks for the help mate!
Click to expand...
Click to collapse
Great The links are important!! They are my sources, and often contain much more detail than what I use in my guides. I attempt creating a well ordered summary, but my sources are better if you don't mind reading loads.
I'm glad I could help
munkyvirus said:
Plugged the settings into Yankactive on DU. Quick, freqs stay low when nothings going on, seems legit. I set my timer_rate higher tho, 10000 feels a little low, makes me think that the CPU will spend too much time polling loads.
Click to expand...
Click to collapse
That's the idea. And never heard of Yankactive...but I'm gonna assume it's good lol.
And about time_rate, you are right, but you are also wrong.
There isn't a true right answer unless someone performs a scientific experiment in order to fully test which one is better.
But I'll explain why I put my one short... I want the frequencies returning to IDLE asap. While yes, you are right it's polling often, it also returns to idle much faster, rather than staying at higher frequency uselessly wasting battery.
I'll try to run some tests checking CPU load, if CPU load considerable lowers I'll come back and report.

Yankactive is Interactive with some under the hood tweaks, I believe, same tunables. I also looked at some documentation on Interactive and I think the target_loads have to be in ascending order based on load when paired with clock speeds, I'm gonna mess with them a bit and see what I get. Link

munkyvirus said:
Yankactive is Interactive with some under the hood tweaks, I believe, same tunables. I also looked at some documentation on Interactive and I think the target_loads have to be in ascending order based on load when paired with clock speeds, I'm gonna mess with them a bit and see what I get. Link
Click to expand...
Click to collapse
And no, target_loads has to be in ascending order based on FREQUENCY. You are applying load percentages to frequency ranges, therefore it is imperative that its the frequency defining the order.
e.g. 50 4:80 10:20 12: 50 means:
50% load before going to the next frequency step, until you reach frequency 4, then use 80% instead until frequency 10, then use 20% instead until 12, then use 50% until max frequency.
Feel free to play with them as much as you want, just make sure to keep the idea of using efficient frequency steps in mind.

Kyuubi10 said:
And no, target_loads has to be in ascending order based on FREQUENCY. You are applying load percentages to frequency ranges, therefore it is imperative that its the frequency defining the order.
e.g. 50 4:80 10:20 12: 50 means:
50% load before going to the next frequency step, until you reach frequency 4, then use 80% instead until frequency 10, then use 20% instead until 12, then use 50% until max frequency.
Feel free to play with them as much as you want, just make sure to keep the idea of using efficient frequency steps in mind.
Click to expand...
Click to collapse
Thank you for the knowledge dump, been scraping the barrel for weeks trying to figure out tunables!

munkyvirus said:
Thank you for the knowledge dump, been scraping the barrel for weeks trying to figure out tunables!
Click to expand...
Click to collapse
Hehe it's a pleasure.
It's a way I find to give back to the community, since I learn so much through it. I can try help make life easier for those who follow the same path I did.

Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?

Wow, this is awesome! I had the performance gov on, which just destroyed my battery. Now, I have a question for you!
What is your take on "Multicore Power Savings" ? I'm using a flarport kernel which has it set to aggressive by default. Should this be changed to anything else while using your gov settings? Thanks for any assistance!

lil_kujo said:
Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?
Click to expand...
Click to collapse
I have never heard of mpdecision having a battery saver mode XD
Would you please expand on that? Also tell me which tweaking app you are using?

Kyuubi10 said:
I have never heard of mpdecision having a battery saver mode XD
Would you please expand on that? Also tell me which tweaking app you are using?
Click to expand...
Click to collapse
It's in the ex app mate, it uses a less aggressive version of mpdecision to saver on battery power but I can't say that I noticed much improvement TBH.
Sent from my HTC One_M8 using Tapatalk

Anonaru said:
Wow, this is awesome! I had the performance gov on, which just destroyed my battery. Now, I have a question for you!
What is your take on "Multicore Power Savings" ? I'm using a flarport kernel which has it set to aggressive by default. Should this be changed to anything else while using your gov settings? Thanks for any assistance!
Click to expand...
Click to collapse
You had performance on?? You do realise that the perf gov basically keeps your CPU cores running on max frequency all the time right?
No wonder your battery was dying XD
Anyhoo....good thing you found my guide
Now, about multicore power savings, as usually with most things you will be compromising something to gain something else...always keep that in mind.
With MPS you'll be giving up some multitasking, in order to gain some battery savings.
Why (you may ask)?
Well, think about a to-do list, and for each list you have one person completing the tasks within that list. Let's say you have four lists and 4 people completing those tasks.
What MPS does is it takes as many tasks as possible and places them within a single list, for one person to do. At the end of the day that one person will have done a lot of work, while the other 3 will have done very little work. The drawback? The work was completed much slower, because only one person was doing it.
Why can MPS be good? It is the way it chooses which CPU to use to add the tasks to, it chooses CPUs which are already turned on, rather than turning a new one on.
The frequency voltages on each core range from the lowest of 775mV, to the highest of 1075mV. That's a 300mV increase in battery consumption between lowest frequency and highest. (Mind you, 1075 for me is an overclocked value, if you are not OC then it will be even less)
When CPU cores have nothing to do they get turned off....they don't idle at 775mV....they are literally off. Therefore around 0mV usage XD
If you get tasks which would have run on 2 CPUs at minimum frequency, using only 775mV each, and put them to run on only 1 CPU at MAX frequency at 1075mV, you still have about 400mV battery savings. Now lets say its something which would have used 4 CPUs, but you end up using only two.... then the battery savings double to 800mV.
Final answer...it depends on your tastes, what do you prefer most? Multitasking or battery saving.
Personally I keep it enabled, but not aggressive.
But if you really don't care about multitasking, you may as well leave it as aggressive.

lil_kujo said:
Hello kyuubi10 thanks for your help, would it be ok to change mp decision to battery saver mode ? Whats your take on that?
Click to expand...
Click to collapse
smeejaytee said:
It's in the ex app mate, it uses a less aggressive version of mpdecision to saver on battery power but I can't say that I noticed much improvement TBH.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Well, I use adiutor, so I don't have that option.
I am happy with my phone how it is (if it wasn't for the damned plug issues XD)
But @lil_kujo, as @smeejaytee said....he hasn't noticed much improvement.
So I'd trust his advice

Kyuubi10 said:
You had performance on?? You do realise that the perf gov basically keeps your CPU cores running on max frequency all the time right?
No wonder your battery was dying XD
Anyhoo....good thing you found my guide
Now, about multicore power savings, as usually with most things you will be compromising something to gain something else...always keep that in mind.
With MPS you'll be giving up some multitasking, in order to gain some battery savings.
Why (you may ask)?
Well, think about a to-do list, and for each list you have one person completing the tasks within that list. Let's say you have four lists and 4 people completing those tasks.
What MPS does is it takes as many tasks as possible and places them within a single list, for one person to do. At the end of the day that one person will have done a lot of work, while the other 3 will have done very little work. The drawback? The work was completed much slower, because only one person was doing it.
Why can MPS be good? It is the way it chooses which CPU to use to add the tasks to, it chooses CPUs which are already turned on, rather than turning a new one on.
The frequency voltages on each core range from the lowest of 775mV, to the highest of 1075mV. That's a 300mV increase in battery consumption between lowest frequency and highest. (Mind you, 1075 for me is an overclocked value, if you are not OC then it will be even less)
When CPU cores have nothing to do they get turned off....they don't idle at 775mV....they are literally off. Therefore around 0mV usage XD
If you get tasks which would have run on 2 CPUs at minimum frequency, using only 775mV each, and put them to run on only 1 CPU at MAX frequency at 1075mV, you still have about 400mV battery savings. Now lets say its something which would have used 4 CPUs, but you end up using only two.... then the battery savings double to 800mV.
Final answer...it depends on your tastes, what do you prefer most? Multitasking or battery saving.
Personally I keep it enabled, but not aggressive.
But if you really don't care about multitasking, you may as well leave it as aggressive.
Click to expand...
Click to collapse
Hah, thanks for the guide-- I am pretty well versed in task / resource allocation on multi-threaded systems, though
Main reason I was asking was because I haven't a clue what some of the values are on this interactive gov. Just wanted to make sure they didn't clash! I'll chance it to "Enabled" rather than "Aggressive," because a compromise between the two sounds the best
As for Performance gov-- default setting on this flarport kernel, didn't bother to check it until I noticed that any time a core was on, it was racing at 2.5ghz, even with nothing going on. Battery pretty much committed suicide

Anonaru said:
Hah, thanks for the guide-- I am pretty well versed in task / resource allocation on multi-threaded systems, though
Main reason I was asking was because I haven't a clue what some of the values are on this interactive gov. Just wanted to make sure they didn't clash! I'll chance it to "Enabled" rather than "Aggressive," because a compromise between the two sounds the best
As for Performance gov-- default setting on this flarport kernel, didn't bother to check it until I noticed that any time a core was on, it was racing at 2.5ghz, even with nothing going on. Battery pretty much committed suicide
Click to expand...
Click to collapse
LOL I suggest you change kernel asap! If the dev uses uses Performcance gov as his default he doesn't know what he is doing XD
And no, as far as I know governor tunables won't ever clash with MPS.

Thanks!

rjavc said:
Thanks!
Click to expand...
Click to collapse
You're welcome! Pleasure to help.
But I'd appreciate if you press the thanks button on the relevant posts which helped you. That's the XDA way :good::good:

Kyuubi10 said:
You're welcome! Pleasure to help.
But I'd appreciate if you press the thanks button on the relevant posts which helped you. That's the XDA way :good::good:
Click to expand...
Click to collapse
Hi mate, I wondered if I could ask your advice, I want to set interactive up on my maw Android TV box it's quad 1.5gb and I want maximum performance as its constantly plugged in, there is no battery so that's not an issue,
Sorry if you think this OT but I thought I'd ask you as you know the governor well, thank you in advance mate.
Sent from my HTC One_M8 using Tapatalk

Speed and Battery tweaks.

So I've been following this section for months and just got my a2017u 2 weeks ago. I'm rooted with tenfars tool still locked on b20. I've noticed in the last few weeks a tapering off of new and useful info for this phone and would really like to see what and where everyone is with it? LSpeed? Kernel Auditor? Or any tweaks that have helped either performance or battery life!!! Looking for anything to make this already great phone better!!! TIA

I have been using EX Kernel manager to tweak the settings as kernel auditor was not working properly with the big.LITTLE arrangement. I have upped the readahead value and underclocked the cpu to 1036mhz on the little cores and 1401 mhz on the big cores. working still as snappy and getting +2h SOT. I'm a heavy gamer and Asphalt 8 still plays as fluid as before, even better tbh due to less heating.
If you don't like to underclock, you could try these:
http://forum.xda-developers.com/htc-10/development/pnp-tweak-custom-butterfly-ghostpepper-t3431307

+2h? That's really good! I know overclocking can/could/might damage the CPU. Does underclocking have any of the same risks? I'm rooted and unlocked atm. So no warrenty anyway

aPexalpha said:
+2h? That's really good! I know overclocking can/could/might damage the CPU. Does underclocking have any of the same risks? I'm rooted and unlocked atm. So no warrenty anyway
Click to expand...
Click to collapse
Overclocking can't really harm anything. The excess heat might but it would take a long time and really high temps (you couldn't keep the device in your hands). The only thing you risk by overclocking is a system crash. Just reboot, lower the clock values and voilà ! So no, underclocking can't hurt anything. Overvolting however poses a real threat to the integrity of the components. It's quite the same thing as in computers (except for the heat, you don't always realize it's too hot in a computer).
That being said, is overclocking still even possible on smartphones nowadays ? Just for the fun of it because it's not needed in the least on the Axon 7 .
That's impressive results ! Not sure those hours are needed since the battery is doing well with the software power saver but still a good thing to know.

Still any extra sot is welcome. I'm not a gamer, don't really have any apps that truly need the full power of the sd820 so might give it a shot. Greenify does wonders for standby time.
Not sure if the built in 'intelligent country control' does anything tbh

I'm on my phone most of the day whether it be YouTube play music, texts,calls,etc.. I'm just hoping to find a balance between battery and my multitasking ADHD LOL

Nik2424 said:
I have been using EX Kernel manager to tweak the settings as kernel auditor was not working properly with the big.LITTLE arrangement. I have upped the readahead value and underclocked the cpu to 1036mhz on the little cores and 1401 mhz on the big cores. working still as snappy and getting +2h SOT. I'm a heavy gamer and Asphalt 8 still plays as fluid as before, even better tbh due to less heating.
If you don't like to underclock, you could try these:
http://forum.xda-developers.com/htc-10/development/pnp-tweak-custom-butterfly-ghostpepper-t3431307
Click to expand...
Click to collapse
Mine keeps switching back to 'normal' modes with CPU full on. Any idea how to fix that?

aPexalpha said:
Mine keeps switching back to 'normal' modes with CPU full on. Any idea how to fix that?
Click to expand...
Click to collapse
Yup, I had that problem too initially.
First, I made system changes persistent upon reboot by running this command in Terminal emulator(you can also use adb shell):
reboot disemmcwp
Secondly, you have to disable smart power in the quick toggles.
Once this is done, set your new max values, select the arrow next to it to make it applied on every boot and then reboot your device. It should work.
Note: Everytime you open the EX Kernel manager you will see the speeds jump to max for like 1 sec but if you actually check the cpu statistics you'll see that your settings are sticking and the max clock speed was just for everytime you open the app.

The smart power! I forgot that thing controls the CPU.
So that round arrow thing means apply on boot? I selected that, figured it meant something like that.
Cheers!

best battery rom

What is the best battery rom and your best SOT?

in my experience ; the best battery rom is eui 5.8.019s

I tested miui and battery was very correct in my opinion.

small eui v3 beta its good at the moment.

irfancan18 said:
small eui v3 beta its good at the moment.
Click to expand...
Click to collapse
How much sot?

zikam12 said:
How much sot?
Click to expand...
Click to collapse
5-5.30. Gaming, social media etc

I am currently using Miui 10 pro global V8.9.20 + Illusion kernel V3 which is giving me 5:30 hrs of screen on time completely bugless.
You can get the Illusion kernel only in the Le 2 Telegram channel posting link for the same you go & download kernel from there.
1. Le 2 telegram channel link for Kernel
https://t.me/LeEco_Le2 (click this link in your phone after installing telegram make an account , use Chrome or Opera browser only other browser don't redirect this link).
2. Miui 10 pro Global for Le 2 link Gdrive
https://drive.google.com/file/d/1gbspIBvM3EhBeapluGfZl-UECNB_fEeQ/view

Cannot get illusion kernel.
URL leads to error 500.
Could you share another link please ?
Thanks
Found here :
https://androidfilehost.com/?fid=673791459329070680

zikam12 said:
How much sot?
Click to expand...
Click to collapse
zikam12 said:
How much sot?
Click to expand...
Click to collapse
I have never got this much screen on time on the leeco le 2 (SD version) so I just had to share this with somebody... anybody really. Whomever has done better please feel free to share your awesome le 2 battery life with smallEUI, stock,or any other rom (doubtful).
So I just got 8 hours and 30 minutes of sot running smallEUI version 3 with illusion kernel v2.5. (Note: I used v2.5 because v3 uses lazy plug for CPU hot plugging which IMHO has far more battery drain than the stock Qualcomm core control) but I digress...
Anyways, I am a heavy gamer and frequently play real racing 3 for more than 1.5 hours in some days Today I decided to cut back and only played it for 25 minutes.This reduced gaming time enabled me to subject my phone to a more mixed use pattern. When I started I wasn't even looking to break any screen on time records but at around 21% battery remaining, I was at 7 hours SOT so I decided to keep using the phone normally until I ran it down to empty.
Here's some background to this achievement...
First off, I don't run anything on stock settings. I use a slimmed down EUI rom, a custom kernel to boot, and minor tweaks to the build.prop. I have done major tweaks to the custom kernel, use greenify in elevated mode, and block the recommended wakelocks on kernel adiutor app. I have also improved thermal thresholds to minimize throttling. When CPU thermal throttles, it leads to more power consumption because it has to stay on longer and use more CPU cycles to finish tasks that it could have completed much faster with high clock speed at the expense of negligible heating. I looked at the stock smallEUI thermal config and was shocked to find that the CPU starts throttling when it reaches temperatures as low as 38 degrees Celsius. (That's too low). The big cores are allowed to hot plug at a measly 40 degrees and at 42 degrees the system is allowed to turn off three of them. Only CPU 4, which is the first big core that controls the other 3 is exempted from being turned off due to this insanely low threshold. However, it doesn't escape the overall thermal tolerance which is set at 38-70 degrees. At which point, it will be doing just 883MHz before getting completely shut down! We all know (I hope we do) that big cores are generally more efficient at higher clock speed but someone must have missed the memo here. (Big cores are set to throttle down to 998MHz at just 50 degrees! Crazy, right). @iaureeel should look into this.
For monitoring, I use better battery stats xda edition, gsam battery monitor, and kernel adiutor overview page. I don't have WiFi so all data comes through 4G (the signal is usually above average to excellent) -- this phone has better reception than any other I've ever used ??
The usage:
Here's a summary of the notable things I did. You may browse the screenshots to see more.
First off: Games...
I played real racing 3 for around 25 minutes
Tried out a newly downloaded (on this same charge cycle) 3D game called war wings -- Around 20 minutes. Spoiler alert: it's awesome?
Starting with full charge and hammering the battery to about 15%, I can play real racing 3 for 4 hours non-stop.
Others:
I watched some YouTube over 4G for 30 minutes
I used brave to browse the web for just over an hour.
Side note: surface flinger showed up on BBS probably because I speeded up scrolling in build.prop. It shouldn't be this active but the power draw is probably not too significant.
How I did it
Recap of what enabled me to have this sot figure:
1. Optimized custom EUI-based ROM (smallEUI)
2. Custom kernel (heavily customizable and tweaked to kingdom come)
3. Greenify
4. Higher thermal tolerance for the CPU (it doesn't even get hot enough to be uncomfortable even at highest load. The plus for the battery here is that the CPU completes tasks much faster and then goes into a quick race to idle (thanks to a tweak I've added to blu_active governor for big cores)
5. No automatic brightness! I often get by with minimum brightness but when I need more I manually bump it up to 10-25%. 50 % is enough for me to comfortably use the phone outside. And not in direct sunlight because who can compete with the sun? Not any phone's display. THAT'S FOR SURE!
6. Cherry-picked build.prop tweaks
7. No Facebook, Instagram, Snapchat, and other naughty social apps that put your phone in a wakelock chockhold until its precious juice is depleted.
Conclusion:
I have never been one to hunt screen-on-time records (and wasn't in this case) but today has showed me a side of this phone that I didn't know existed. That's really good battery backup. I didn't think it was this easy but leeco did some clever things too in order to make it possible. First is charging the battery to 4.4 volts which increases charge holding capacity to 110% of the reference design. I don't recommend that you charge to 100% because it will be at the expense of battery life span. (Unless leeco uses a military grade battery like they do in the Coolpad cool 1 dual and LeRee le 3).
Another thing that helps is the inclination of EUI towards power saving. SmallEUI is even better because it saves power without hindering user experience. Notifications come on time and there is no stuttering even on stock everything.
Full disclosure: My phone is brand new(ish) at just one month old.
That's all for now... Check out the screenshots. As they say, the proof is in the pudding ?. There's a limit to the number of files I can attach so I've put the rest in a .zip file

twistyplain said:
I have never got this much screen on time on the leeco le 2 (SD version) so I just had to share this with somebody... anybody really. Whomever has done better please feel free to share your awesome le 2 battery life with smallEUI, stock,or any other rom (doubtful).
So I just got 8 hours and 30 minutes of sot running smallEUI version 3 with illusion kernel v2.5. (Note: I used v2.5 because v3 uses lazy plug for CPU hot plugging which IMHO has far more battery drain than the stock Qualcomm core control) but I digress...
Anyways, I am a heavy gamer and frequently play real racing 3 for more than 1.5 hours in some days Today I decided to cut back and only played it for 25 minutes.This reduced gaming time enabled me to subject my phone to a more mixed use pattern. When I started I wasn't even looking to break any screen on time records but at around 21% battery remaining, I was at 7 hours SOT so I decided to keep using the phone normally until I ran it down to empty.
Here's some background to this achievement...
First off, I don't run anything on stock settings. I use a slimmed down EUI rom, a custom kernel to boot, and minor tweaks to the build.prop. I have done major tweaks to the custom kernel, use greenify in elevated mode, and block the recommended wakelocks on kernel adiutor app. I have also improved thermal thresholds to minimize throttling. When CPU thermal throttles, it leads to more power consumption because it has to stay on longer and use more CPU cycles to finish tasks that it could have completed much faster with high clock speed at the expense of negligible heating. I looked at the stock smallEUI thermal config and was shocked to find that the CPU starts throttling when it reaches temperatures as low as 38 degrees Celsius. (That's too low). The big cores are allowed to hot plug at a measly 40 degrees and at 42 degrees the system is allowed to turn off three of them. Only CPU 4, which is the first big core that controls the other 3 is exempted from being turned off due to this insanely low threshold. However, it doesn't escape the overall thermal tolerance which is set at 38-70 degrees. At which point, it will be doing just 883MHz before getting completely shut down! We all know (I hope we do) that big cores are generally more efficient at higher clock speed but someone must have missed the memo here. (Big cores are set to throttle down to 998MHz at just 50 degrees! Crazy, right). @iaureeel should look into this.
For monitoring, I use better battery stats xda edition, gsam battery monitor, and kernel adiutor overview page. I don't have WiFi so all data comes through 4G (the signal is usually above average to excellent) -- this phone has better reception than any other I've ever used ??
The usage:
Here's a summary of the notable things I did. You may browse the screenshots to see more.
First off: Games...
I played real racing 3 for around 25 minutes
Tried out a newly downloaded (on this same charge cycle) 3D game called war wings -- Around 20 minutes. Spoiler alert: it's awesome
Starting with full charge and hammering the battery to about 15%, I can play real racing 3 for 4 hours non-stop.
Others:
I watched some YouTube over 4G for 30 minutes
I used brave to browse the web for just over an hour.
Side note: surface flinger showed up on BBS probably because I speeded up scrolling in build.prop. It shouldn't be this active but the power draw is probably not too significant.
How I did it
Recap of what enabled me to have this sot figure:
1. Optimized custom EUI-based ROM (smallEUI)
2. Custom kernel (heavily customizable and tweaked to kingdom come)
3. Greenify
4. Higher thermal tolerance for the CPU (it doesn't even get hot enough to be uncomfortable even at highest load. The plus for the battery here is that the CPU completes tasks much faster and then goes into a quick race to idle (thanks to a tweak I've added to blu_active governor for big cores)
5. No automatic brightness! I often get by with minimum brightness but when I need more I manually bump it up to 10-25%. 50 % is enough for me to comfortably use the phone outside. And not in direct sunlight because who can compete with the sun? Not any phone's display. THAT'S FOR SURE!
6. Cherry-picked build.prop tweaks
7. No Facebook, Instagram, Snapchat, and other naughty social apps that put your phone in a wakelock chockhold until its precious juice is depleted.
Conclusion:
I have never been one to hunt screen-on-time records (and wasn't in this case) but today has showed me a side of this phone that I didn't know existed. That's really good battery backup. I didn't think it was this easy but leeco did some clever things too in order to make it possible. First is charging the battery to 4.4 volts which increases charge holding capacity to 110% of the reference design. I don't recommend that you charge to 100% because it will be at the expense of battery life span. (Unless leeco uses a military grade battery like they do in the Coolpad cool 1 dual and LeRee le 3).
Another thing that helps is the inclination of EUI towards power saving. SmallEUI is even better because it saves power without hindering user experience. Notifications come on time and there is no stuttering even on stock everything.
Full disclosure: My phone is brand new(ish) at just one month old.
That's all for now... Check out the screenshots. As they say, the proof is in the pudding . There's a limit to the number of files I can attach so I've put the rest in a .zip file
Click to expand...
Click to collapse
could you pls share how did you custimize he kernel ? if you could pls upload your kernel auditor profile or photos.

yoguy said:
could you pls share how did you custimize he kernel ? if you could pls upload your kernel auditor profile or photos.
Click to expand...
Click to collapse
Here's my kernel adiutor profile.

yoguy said:
could you pls share how did you custimize he kernel ? if you could pls upload your kernel auditor profile or photos.
Click to expand...
Click to collapse
Could you please share me screenshots of ExKM or kernel aduitor and build.prop strings that you added. Btw, I want them for stock eui for 6 hrs SOT

sirnono said:
I tested miui and battery was very correct in my opinion.
Click to expand...
Click to collapse
i never see a rom very bad with battery like the miui's rom on le 2 , version after version and this problem is not fixed
,i dont know why
what's version you talking about ?

stock battery life
mid95 said:
in my experience ; the best battery rom is eui 5.8.019s
Click to expand...
Click to collapse
i am using it after installing custom rom on my phone but i am not getting same sot as i get before installing custom rom.
plz help me in this case, i locked bootloader of my phone too.

Hi
twistyplain said:
I have never got this much screen on time on the leeco le 2 (SD version) so I just had to share this with somebody... anybody really. Whomever has done better please feel free to share your awesome le 2 battery life with smallEUI, stock,or any other rom (doubtful).
So I just got 8 hours and 30 minutes of sot running smallEUI version 3 with illusion kernel v2.5. (Note: I used v2.5 because v3 uses lazy plug for CPU hot plugging which IMHO has far more battery drain than the stock Qualcomm core control) but I digress...
Anyways, I am a heavy gamer and frequently play real racing 3 for more than 1.5 hours in some days Today I decided to cut back and only played it for 25 minutes.This reduced gaming time enabled me to subject my phone to a more mixed use pattern. When I started I wasn't even looking to break any screen on time records but at around 21% battery remaining, I was at 7 hours SOT so I decided to keep using the phone normally until I ran it down to empty.
Here's some background to this achievement...
First off, I don't run anything on stock settings. I use a slimmed down EUI rom, a custom kernel to boot, and minor tweaks to the build.prop. I have done major tweaks to the custom kernel, use greenify in elevated mode, and block the recommended wakelocks on kernel adiutor app. I have also improved thermal thresholds to minimize throttling. When CPU thermal throttles, it leads to more power consumption because it has to stay on longer and use more CPU cycles to finish tasks that it could have completed much faster with high clock speed at the expense of negligible heating. I looked at the stock smallEUI thermal config and was shocked to find that the CPU starts throttling when it reaches temperatures as low as 38 degrees Celsius. (That's too low). The big cores are allowed to hot plug at a measly 40 degrees and at 42 degrees the system is allowed to turn off three of them. Only CPU 4, which is the first big core that controls the other 3 is exempted from being turned off due to this insanely low threshold. However, it doesn't escape the overall thermal tolerance which is set at 38-70 degrees. At which point, it will be doing just 883MHz before getting completely shut down! We all know (I hope we do) that big cores are generally more efficient at higher clock speed but someone must have missed the memo here. (Big cores are set to throttle down to 998MHz at just 50 degrees! Crazy, right). @iaureeel should look into this.
For monitoring, I use better battery stats xda edition, gsam battery monitor, and kernel adiutor overview page. I don't have WiFi so all data comes through 4G (the signal is usually above average to excellent) -- this phone has better reception than any other I've ever used ??
The usage:
Here's a summary of the notable things I did. You may browse the screenshots to see more.
First off: Games...
I played real racing 3 for around 25 minutes
Tried out a newly downloaded (on this same charge cycle) 3D game called war wings -- Around 20 minutes. Spoiler alert: it's awesome?
Starting with full charge and hammering the battery to about 15%, I can play real racing 3 for 4 hours non-stop.
Others:
I watched some YouTube over 4G for 30 minutes
I used brave to browse the web for just over an hour.
Side note: surface flinger showed up on BBS probably because I speeded up scrolling in build.prop. It shouldn't be this active but the power draw is probably not too significant.
How I did it
Recap of what enabled me to have this sot figure:
1. Optimized custom EUI-based ROM (smallEUI)
2. Custom kernel (heavily customizable and tweaked to kingdom come)
3. Greenify
4. Higher thermal tolerance for the CPU (it doesn't even get hot enough to be uncomfortable even at highest load. The plus for the battery here is that the CPU completes tasks much faster and then goes into a quick race to idle (thanks to a tweak I've added to blu_active governor for big cores)
5. No automatic brightness! I often get by with minimum brightness but when I need more I manually bump it up to 10-25%. 50 % is enough for me to comfortably use the phone outside. And not in direct sunlight because who can compete with the sun? Not any phone's display. THAT'S FOR SURE!
6. Cherry-picked build.prop tweaks
7. No Facebook, Instagram, Snapchat, and other naughty social apps that put your phone in a wakelock chockhold until its precious juice is depleted.
Conclusion:
I have never been one to hunt screen-on-time records (and wasn't in this case) but today has showed me a side of this phone that I didn't know existed. That's really good battery backup. I didn't think it was this easy but leeco did some clever things too in order to make it possible. First is charging the battery to 4.4 volts which increases charge holding capacity to 110% of the reference design. I don't recommend that you charge to 100% because it will be at the expense of battery life span. (Unless leeco uses a military grade battery like they do in the Coolpad cool 1 dual and LeRee le 3).
Another thing that helps is the inclination of EUI towards power saving. SmallEUI is even better because it saves power without hindering user experience. Notifications come on time and there is no stuttering even on stock everything.
Full disclosure: My phone is brand new(ish) at just one month old.
That's all for now... Check out the screenshots. As they say, the proof is in the pudding ?. There's a limit to the number of files I can attach so I've put the rest in a .zip file
Click to expand...
Click to collapse
Hi. Good day, please how can you help me? I just bought this but it is consuming battery. So I decided to check online for solutions and I found this site. please help me I don't know so much about phone, I just want to enjoy the phone without having to worry about the battery or the high temperature (hot) problem. Thanks.

Hi. Good day, please how can you help me? I just bought this but it is consuming battery. So I decided to check online for solutions and I found this site. please help me I don't know so much about phone, I just want to enjoy the phone without having to worry about the battery or the high temperature (hot) problem. Thanks.

twistyplain said:
I have never got this much screen on time on the leeco le 2 (SD version) so I just had to share this with somebody... anybody really. Whomever has done better please feel free to share your awesome le 2 battery life with smallEUI, stock,or any other rom (doubtful).
So I just got 8 hours and 30 minutes of sot running smallEUI version 3 with illusion kernel v2.5. (Note: I used v2.5 because v3 uses lazy plug for CPU hot plugging which IMHO has far more battery drain than the stock Qualcomm core control) but I digress...
Anyways, I am a heavy gamer and frequently play real racing 3 for more than 1.5 hours in some days Today I decided to cut back and only played it for 25 minutes.This reduced gaming time enabled me to subject my phone to a more mixed use pattern. When I started I wasn't even looking to break any screen on time records but at around 21% battery remaining, I was at 7 hours SOT so I decided to keep using the phone normally until I ran it down to empty.
Here's some background to this achievement...
First off, I don't run anything on stock settings. I use a slimmed down EUI rom, a custom kernel to boot, and minor tweaks to the build.prop. I have done major tweaks to the custom kernel, use greenify in elevated mode, and block the recommended wakelocks on kernel adiutor app. I have also improved thermal thresholds to minimize throttling. When CPU thermal throttles, it leads to more power consumption because it has to stay on longer and use more CPU cycles to finish tasks that it could have completed much faster with high clock speed at the expense of negligible heating. I looked at the stock smallEUI thermal config and was shocked to find that the CPU starts throttling when it reaches temperatures as low as 38 degrees Celsius. (That's too low). The big cores are allowed to hot plug at a measly 40 degrees and at 42 degrees the system is allowed to turn off three of them. Only CPU 4, which is the first big core that controls the other 3 is exempted from being turned off due to this insanely low threshold. However, it doesn't escape the overall thermal tolerance which is set at 38-70 degrees. At which point, it will be doing just 883MHz before getting completely shut down! We all know (I hope we do) that big cores are generally more efficient at higher clock speed but someone must have missed the memo here. (Big cores are set to throttle down to 998MHz at just 50 degrees! Crazy, right). @iaureeel should look into this.
For monitoring, I use better battery stats xda edition, gsam battery monitor, and kernel adiutor overview page. I don't have WiFi so all data comes through 4G (the signal is usually above average to excellent) -- this phone has better reception than any other I've ever used ??
The usage:
Here's a summary of the notable things I did. You may browse the screenshots to see more.
First off: Games...
I played real racing 3 for around 25 minutes
Tried out a newly downloaded (on this same charge cycle) 3D game called war wings -- Around 20 minutes. Spoiler alert: it's awesome?
Starting with full charge and hammering the battery to about 15%, I can play real racing 3 for 4 hours non-stop.
Others:
I watched some YouTube over 4G for 30 minutes
I used brave to browse the web for just over an hour.
Side note: surface flinger showed up on BBS probably because I speeded up scrolling in build.prop. It shouldn't be this active but the power draw is probably not too significant.
How I did it
Recap of what enabled me to have this sot figure:
1. Optimized custom EUI-based ROM (smallEUI)
2. Custom kernel (heavily customizable and tweaked to kingdom come)
3. Greenify
4. Higher thermal tolerance for the CPU (it doesn't even get hot enough to be uncomfortable even at highest load. The plus for the battery here is that the CPU completes tasks much faster and then goes into a quick race to idle (thanks to a tweak I've added to blu_active governor for big cores)
5. No automatic brightness! I often get by with minimum brightness but when I need more I manually bump it up to 10-25%. 50 % is enough for me to comfortably use the phone outside. And not in direct sunlight because who can compete with the sun? Not any phone's display. THAT'S FOR SURE!
6. Cherry-picked build.prop tweaks
7. No Facebook, Instagram, Snapchat, and other naughty social apps that put your phone in a wakelock chockhold until its precious juice is depleted.
Conclusion:
I have never been one to hunt screen-on-time records (and wasn't in this case) but today has showed me a side of this phone that I didn't know existed. That's really good battery backup. I didn't think it was this easy but leeco did some clever things too in order to make it possible. First is charging the battery to 4.4 volts which increases charge holding capacity to 110% of the reference design. I don't recommend that you charge to 100% because it will be at the expense of battery life span. (Unless leeco uses a military grade battery like they do in the Coolpad cool 1 dual and LeRee le 3).
Another thing that helps is the inclination of EUI towards power saving. SmallEUI is even better because it saves power without hindering user experience. Notifications come on time and there is no stuttering even on stock everything.
Full disclosure: My phone is brand new(ish) at just one month old.
That's all for now... Check out the screenshots. As they say, the proof is in the pudding ?. There's a limit to the number of files I can attach so I've put the rest in a .zip file
Click to expand...
Click to collapse
Hi. Good day, please how can you help me? I just bought this but it is consuming battery. So I decided to check online for solutions and I found this site. please help me I don't know so much about phone, I just want to enjoy the phone without having to worry about the battery or the high temperature (hot) problem. Thanks.

zikam12 said:
What is the best battery rom and your best SOT?
Click to expand...
Click to collapse
Hi. Good day, please how can you help me? I just bought this but it is consuming battery. So I decided to check online for solutions and I found this site. please help me I don't know so much about phone, I just want to enjoy the phone without having to worry about the battery or the high temperature (hot) problem. Thanks.

irfancan18 said:
small eui v3 beta its good at the mome
Click to expand...
Click to collapse
Hi. Good day, please how can you help me? I just bought this but it is consuming battery. So I decided to check online for solutions and I found this site. please help me I don't know so much about phone, I just want to enjoy the phone without having to worry about the battery or the high temperature (hot) problem. Thanks.

boyoo001 said:
Hi. Good day, please how can you help me? I just bought this but it is consuming battery. So I decided to check online for solutions and I found this site. please help me I don't know so much about phone, I just want to enjoy the phone without having to worry about the battery or the high temperature (hot) problem. Thanks.
Click to expand...
Click to collapse
I have THE Answering for You and ALL other Le Membershipper`s...
If you have a Smartphone, You have to CHANGE your Battery between 12 to 18 Month`s. If you are working in Office and you Use the whole Day Wireless Lan? Then, you have to change the Battery between 12 Month`s and every Year behing the change!
And Dubble 3M Band for the Displayframe you have to Buy also. Oh, IF, you want to Change your Battery then you NEED a HOT Gun Pistol with Minimum 110 Degrees! Heat Up the Frameside about 5-10 Millimeters and DON`T Lift it UP in the Roundings of the Edges! They are Breaking!!