Database Users

Overclock widget = placebo

The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel

You might be right.
The only difference I can think of is with the widget people are using (I have not tried it) the under clocking happens the instant the screen turns off. Where as we have no idea when/how the standard under clocking happens, if it does at all.
I am waiting it out. If the under clocking widget is true, it will eventually become common knowledge on these forums. For now I have not seen anything that has convinced me and I fear if i tried it I would suffer from the placebo effect. The last thing I want is another app running in the background for no reason.

strung said:
The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel
Click to expand...
Click to collapse
I've noticed this as well. System Panel measures my CPU speed at around 245 Mhz when I'm just swiping through the home screen, but cranks up to 1 Ghz when the CPU usage approaches 100%.

Mecha2142 said:
I've noticed this as well. System Panel measures my CPU speed at around 245 Mhz when I'm just swiping through the home screen, but cranks up to 1 Ghz when the CPU usage approaches 100%.
Click to expand...
Click to collapse
Really? I wonder if that could explain some of the choppiness while scrolling around and general phone use.

I can confirm this with SetCPU's real time monitor. drops to 245 when not in use, and 1ghz when scrolling around

I think oc widget is better. I can choose a 5sec interval in which it checks to see if there are processes that need more CPU power.
I wonder what the intervals are in the stock unrooted OS
Oc widget def works for me, and I'm not just letting my phone sit as a paperweight, I'm using moderate to heavy everyday and the results for me are better.

Also, does the unrooted OS allow other frequencies besides 245 and 1ghz?
Oc widget runs mine in the 300s 500s 700s and 800s when needed
1ghz is not needed all he time when the screen is on. And I don't notice extra lag anywhere

And with 5sec intervals, the screen does not have be off to see 245. Just let it idle for 5 secs

I don't even think the OCwidget works. I mean it tries to set new values, and it thinks they succeed, but I think the new values are ignored by the kernel. For example, I tried to set min and max to 250 mHz and it still shot up to 1 GHz.
My apologies for being a debbie downer.

Here you go... can someone produce something similar with the stock OS unrooted
it does help.. even tho you see my battery between 81 and 79 lol... for me, the top 25% of battery life (from 100-75) goes by fast no matter what, but then it really holds good life afterwards.
{
"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"
}

strung said:
I don't even think the OCwidget works. I mean it tries to set new values, and it thinks they succeed, but I think the new values are ignored by the kernel. For example, I tried to set min and max to 250 mHz and it still shot up to 1 GHz.
My apologies for being a debbie downer.
Click to expand...
Click to collapse
The problem is we are all in the "i think" stage, so its pure speculation. Maybe the oc widget developer could help us out here.
I Do think the op should put a ? In the thread title to get more discussion on this, cuz there are some brilliant minds here at xda
Edit: I emailed the dev w this thread asking for his insite, hopefully he jumps in

Faith is a powerful force
if overclock widget really controlled the clock
1) Linpack scores would reflect that
2) mHz readings would reflect that
But... they don't

strung said:
The system already dynamically clocks the CPU
Don't believe? Install OSMonitor and look at the "Misc" tab
Notice the "ondemand" governor scaling the processor from 245000 - 998400 hZ
Leads me to believe CPU governing is already in the kernel
Click to expand...
Click to collapse
Sounds like you have a problem if your Evo is only running from 245 kHz to 998 kHz.

Minjin said:
Sounds like you have a problem if your Evo is only running from 245 kHz to 998 kHz.
Click to expand...
Click to collapse
How do you figure a problem? 998mhz is max.. u just poking fun at "hz"? lol

So with OSMonitor, do you see any current values besides 245 and 998?
here's mine with OC Widget and some of my defined frequencies... If it truly fluctuates to differents clocks like mine on the stock OS with NO root (please show screenies), i will resign as the OC Widget evo underclock believer until an overclock kernel is released and camera works .

I'm on stock OS with root
It indeed goes to all the freq's
sorry too lazy to screenshot
EDIT: oh and I uninstalled OC widget!

strung said:
I'm on stock OS with root
It indeed goes to all the freq's
sorry too lazy to screenshot
Click to expand...
Click to collapse
and no oc widget? thought i was headed somewhere lol

itsallsubliminal said:
How do you figure a problem? 998mhz is max.. u just poking fun at "hz"? lol
Click to expand...
Click to collapse
That would be 998 millihertz which would be even slower.
I may seem like I'm being pedantic and I wouldn't even mention it if this forum was for arguing about American Idol winners but this forum is by definition populated by geeks and otherwise smart individuals.
Regardless of what the app displays, the phone is operating at 245MHz to 998MHz. The capitalization of the H is official but I'm not that anal. Capitalizing the M means mega (1000000). Lower case means milli (1/1000).

Minjin said:
That would be 998 millihertz which would be even slower.
I may seem like I'm being pedantic and I wouldn't even mention it if this forum was for arguing about American Idol winners but this forum is by definition populated by geeks and otherwise smart individuals.
Regardless of what the app displays, the phone is operating at 245MHz to 998MHz. The capitalization of the H is official but I'm not that anal. Capitalizing the M means mega (1000000). Lower case means milli (1/1000).
Click to expand...
Click to collapse
ROFL!

email from OC Widget dev
here is what the dev (Billy Cui) wrote back to me about OC Widget and the Evo...
"Yes, most system support dynamically clocking, but you will still
benefit on using OCW, especially for save battery. And some system do
not running cpu full speed, and with OCW, you can force it run faster."
Makes sense, like i said about the update interval being adjusted with OCWidget.
comments?

[Q] Low Quadrant Scores

I know that this tool isn't a good indicator of performance... but when I see other people with the EVO getting 1200+ and I am at 800-900, I am starting to wonder if there is a setting wrong. My phone occasionally feels sluggish. Any idea's what the cause could be? using an AOSP rom with Tiamat Kernel
- Just realized I wasn't in Q&A forums Sorry! - please delete if needed

Stuke00 said:
I know that this tool isn't a good indicator of performance... but when I see other people with the EVO getting 1200+ and I am at 800-900, I am starting to wonder if there is a setting wrong. My phone occasionally feels sluggish. Any idea's what the cause could be? using an AOSP rom with Tiamat Kernel
Click to expand...
Click to collapse
Good question!
Ive always wondered why some score so low on good combos.
I'm on CM nightly rc3 build 18 with savgzen 1.0.0 cfs-havs and scoring very well
{
"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"
}

new quad you will get low scores
imho quad and all the other benchmark test mean nothing

CheesyNutz said:
new quad you will get low scores
imho quad and all the other benchmark test mean nothing
Click to expand...
Click to collapse
I agree when comparing to other phones... but 2 phones of the same model should get similar scores right?

Stuke00 said:
I agree when comparing to other phones... but 2 phones of the same model should get similar scores right?
Click to expand...
Click to collapse
Have you ran it off of a fresh reboot?
I find my best scores were when I rebooted let it sit for 3-5 min after reboot, and then fire it up.

Mark_in_Tulsa said:
Have you ran it off of a fresh reboot?
I find my best scores were when I rebooted let it sit for 3-5 min after reboot, and then fire it up.
Click to expand...
Click to collapse
Trying it again after the phones been on a few minutes.
I used to use SETCPU and I thought maybe that screwed things up

If you want to increase scores why don't you put your Max frequency at 1190 and min at 1190 with setcpu. High scores are a thing of the past.
~ d3rk

dirkyd3rk said:
If you want to increase scores why don't you put your Max frequency at 1190 and min at 1190 with setcpu. High scores are a thing of the past.
~ d3rk
Click to expand...
Click to collapse
That is with my CPU at 1190. I am not trying to get a high score, but a score my phone should be able to get, you know? I see someone with an EVO get 1500 and then I am thinking something is wrong with my phone... I have the same phone..

Stuke00 said:
That is with my CPU at 1190. I am not trying to get a high score, but a score my phone should be able to get, you know? I see someone with an EVO get 1500 and then I am thinking something is wrong with my phone... I have the same phone..
Click to expand...
Click to collapse
Putting stock in scores is foolish though. 936 does seem a Tad bit low for sure. My set up is cm7 #36, tiamat kernel 3.3.5, JIT on, setcpu 1113 Max, 422 min smartass governor. I just ran a linpack and got 37mflops and 1200 in benchmark. This is the same set up I usually run on any rom or kernel. I try not to clock so high because it just drains battery. My evo actually can perform flawlessly clocked at even 998mhz. The only thing I notice different is that scores change and I don't really take a performance hit. Underclocking is the new overclocking lol. My last suggestion would be to play around with different kernels to achieve what you desire. Try savage zen!
Edit: just ran these 2 test just for you right now. Same results and I'm using same kernel you are.
~ d3rk

Run, it once, and then run it again right after w/out quitting. The if you run it multiple times (at least on my phone), all subsequent scores are on par with the second one which is usually 1-300 more than the first. Won't mean anything any different, but at least you might get some higher scores.
Also, you might need to try some different kernel combinations as well as different clock speeds. Mine usually does fine at 998 sometimes even at 921, but if I go too high it will start to slow things down. If you're not getting good results at 1190, try backing it off one setting at a time and see if you can get improved scores.
As far as comparing to other phones, even of the same make/model, you can't really do that. As long as they're in the same ball park, within a couple hundred, you're probably OK. Every phone reacts differently.
It also depends on the version of quadrant. You def can't compare diff phones running diff versions. I usually don't use it to compare to other phones, just diff setups on my phone. I know if I'm getting 1200 avg and then I all of the sudden flash a ROM and kernel and can't break 800 that something is probably wrong.
The most important thing is how the phone feels though. The fact that you say it feels sluggish leads me to believe you might need to try a diff kernel or see if something is eating up your CPU. Also, when you're over clocking, the min clock speed can effect your scores just as much as the max speed.

Ya give savage a go.
Kernel CPU setting:
Ondemand governor
Min 245
Max 998
My Device scores high runs smooth battery drain not a problem.

I just tested mine and got 1326. With these settings.. CM7 Nightly 36 with 2.6.37.6-Tiamat -v3.3.5 kernal.
Governor - Conservative
Min - 384
Max 1036

Should I undervolt?

After reading this:
http://forum.xda-developers.com/showthread.php?t=2052496
I found I got the "faster" type. As I understand it, this means my cpu has less power/frequency needs, and so, because the stock kernel is configured to manage any of the possible cpu binnings, the settings are probably not the optimal ones for my particular unit. So, does this mean my phone is running at a higher voltage than it needs? Should I undervolt it? How?

While faster CPU binning does mean that you CPU can run more stable at a lower voltage, UV doesn't save you that much of battery.
Most of the battery goes to the screen. The least I have seen around is 50%. Then the next culprit is the radio. And you also have RAM, storage, etc. UV might give you around 1% more battery or so.
You can try UV if you want, but I don't think you need, or should do it.
Sent from my Nexus 4 using xda app-developers app

KyraOfFire said:
While faster CPU binning does mean that you CPU can run more stable at a lower voltage, UV doesn't save you that much of battery.
Most of the battery goes to the screen. The least I have seen around is 50%. Then the next culprit is the radio. And you also have RAM, storage, etc. UV might give you around 1% more battery or so.
You can try UV if you want, but I don't think you need, or should do it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Actually that's not the in my phone. I don't know what I'm doing wrong but AndroidOS, Google Services or MediaServer usually show up as the battery top drains. I have to say I'm on wifi most of the time and the screen time is usually around 1 hour per day. I'm using all the sync features, google now etc, so I I thought reducing the 384Mhz voltage would have some impact

hallucynogenyc said:
Actually that's not the in my phone. I don't know what I'm doing wrong but AndroidOS, Google Services or MediaServer usually show up as the battery top drains. I have to say I'm on wifi most of the time and the screen time is usually around 1 hour per day. I'm using all the sync features, google now etc, so I I thought reducing the 384Mhz voltage would have some impact
Click to expand...
Click to collapse
Presumably you're not talking about under volting, but under clocking?
Sent from my Nexus 4 using xda premium

No, I'm not. Looking at my cpu modes graph, it makes sense to me that reducing the voltage at which the cpu runs at 384mhz would reduce the consumption:
{
"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 Nexus 4 using Tapatalk 2

While it is debatable whether you will save any noticeable amount of battery by undervolting, I have found it to significantly reduce the heat produced by the CPU. Our SOC's are great undervolters, so I don't see any reason NOT to undervolt.
Sent from my Nexus 4 using Tapatalk 2

heat = energy, I highly doubt you can feel a difference in temperature but not in battery lol. How are you guys undervolting? I tried setCPU but it doesn't work, is a custom kernel needed?

KyraOfFire said:
While faster CPU binning does mean that you CPU can run more stable at a lower voltage, UV doesn't save you that much of battery.
Most of the battery goes to the screen. The least I have seen around is 50%. Then the next culprit is the radio. And you also have RAM, storage, etc. UV might give you around 1% more battery or so.
You can try UV if you want, but I don't think you need, or should do it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think the battery usage by the screen that is being reported includes more than just the amount of battery used to power the screen. Due to project butter, touching the screen ramps up the CPU to high frequencies, like 1026 - 1512 GHz, making the phone buttery smooth yet sucking the life out of it's battery. In other words, the screen usage includes its touch boost processing usage as well, which in its self is allot of usage. Basically, UV should improve battery life significantly.

Still noone tells me how to do it xD

hallucynogenyc said:
Still noone tells me how to do it xD
Click to expand...
Click to collapse
You need to install a custom kernel that allows undervolting then use an app such as system tuner to undervolt.
Mine shows as a nominal CPU and I could under volt quite a bit. Makes a nice difference to heat and battery life is noticeably better.
Sent from my Nexus 7 using Tapatalk 2

Okay, I thought rooting would be enough Honestly, I'm liking the stock kernel overall, what's the closest to stock kernel that allows undervolting I can find? If there's no such thing, what do you recommend me?
Thanks in advance

The easiest way, with the minimun amount of work, would be flashing motley kernel. UV by default and you faster binning CPU is fully accounted for.
http://forum.xda-developers.com/showthread.php?t=2021437
Trinity kernel also UV by default. He has his own website here
http://forums.derkernel.com/index.php/topic,47.0.html
Download the zip file, flash it in recovery, wipe cache/dalvik and you're good to go.
You can also try other kernel/ROM that support UV. Most likely you will need a control app.
Sent from my Nexus 4 using xda app-developers app

What's a good level to undervolt to I'm on faux's 001 have a nominal cpu and right now I'm -100 MV should I UV more? My phone is still completely stable at this level

mbucks911 said:
What's a good level to undervolt to I'm on faux's 001 have a nominal cpu and right now I'm -100 MV should I UV more? My phone is still completely stable at this level
Click to expand...
Click to collapse
Every phone can handle different uv levels, mine seems to be -150, and I have "fast" cpu. You can try higher but don't set the voltage to be "on boot" or else you'll get the bootloop or freeze.

[GUIDE] OnePlus One Uber Battery Savings Guide by oscarandjo

We all know that OnePlus One's 3100 mAh battery and ROM optimizations clearly has given the flagship killer the edge in battery life over its competitors.(puny yureka)
But there is always room for improvement.
Reddit user oscarandjo has published a great guide on various battery saving techniques.
The OnePlus One has a brilliant battery, it's a large battery combined with an efficient processor and that leads to great standby and screen on times. This is why the OnePlus One has one of the best battery lives of all of the current flagships.
There are of course many things you can do to make the battery better, most of these things involve turning useful features off. This guide isn't one where you disable all things that make a smartphone smart, instead it makes small changes that make a big difference.
Many of these methods require root, if you aren't rooted yet and are a technical person get it done ASAP using this guide
This guide doesn't include any basic methods like turning aeroplane mode on in poor signal areas, it's more technical methods.
Click to expand...
Click to collapse
First method is to cut down wakelocks
Second method is to block unnecessary apps location services
Third method is to undervolt your CPU
Fourth method is to use Greenify to auto hibernate apps
Fifth method takes some time, but makes a difference
Sixth method is Amplify
Final method is to hide adverts
Click to expand...
Click to collapse
Visit the thread on Reddit to get the step by step procedures.
Do give oscarandjo's thread an upvote.
{
"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"
}
​

All of these I already know but it seems like a good guide for people who are new to android.
Some more important things to consider are hotplugging and under clocking.
Underclocking obviously saves battery by reducing the max CPU clock speed and is much more effective than undervolting.
Hotplugging takes up the most battery depending on the type of hotplugging used.
MPDecision is Qualcomm's method of hotplugging and is aggressive but does not respect the max freq when its under clocked. You need MSMLimiter for it to work properly.
Intelliplug has multiple variants in which some allow you to set the min and max number of cores and others which have predefined profiles. Its fast but lags with dt2w.
Alucard hotplug seems the most efficient because stock settings allow for smoothness and battery savings.
My favorite is MSM MPDecision because it allows you to set the number of cores online at any time while respecting other parameters. I find that if you set a max and min of 2 cores online at any time and use the slim CPU governor with gboost disabled, under clocked to 1.5ghz, you get amazing screen on time with zero lag. Approximately an hour every ten percent while being smooth as butter.
Edit: hey @llcooljerry! Nice to see you here on xda for a change!
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!

abhi08638 said:
All of these I already know but it seems like a good guide for people who are new to android.
Some more important things to consider are hotplugging and under clocking.
Underclocking obviously saves battery by reducing the max CPU clock speed and is much more effective than undervolting.
Hotplugging takes up the most battery depending on the type of hotplugging used.
MPDecision is Qualcomm's method of hotplugging and is aggressive but does not respect the max freq when its under clocked. You need MSMLimiter for it to work properly.
Intelliplug has multiple variants in which some allow you to set the min and max number of cores and others which have predefined profiles. Its fast but lags with dt2w.
Alucard hotplug seems the most efficient because stock settings allow for smoothness and battery savings.
My favorite is MSM MPDecision because it allows you to set the number of cores online at any time while respecting other parameters. I find that if you set a max and min of 2 cores online at any time and use the slim CPU governor with gboost disabled, under clocked to 1.5ghz, you get amazing screen on time with zero lag. Approximately an hour every ten percent while being smooth as butter.
Edit: hey @llcooljerry! Nice to see you here on xda for a change!
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
Click to expand...
Click to collapse
Many thanks, what did you do with cpu boost driver? What are your settings if you have it enabled and which io scheduler?

abhi08638 said:
Edit: hey @llcooljerry! Nice to see you here on xda for a change!
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
Click to expand...
Click to collapse
Hey buddy I'm glad to be here. But i still lack the technical know how in most parts. I thought i will be able to learn and get the facts from experienced users in here.
The guide is kinda meant for all the new users who wants more out of the battery without much tinkering.
Thanks mate. I seriously will look more into under-clocking my one.
Well i did overclock my M14x laptop a few years back.
Cheers.

eefieboy12 said:
Many thanks, what did you do with cpu boost driver? What are your settings if you have it enabled and which io scheduler?
Click to expand...
Click to collapse
disabled CPU Boost driver because it'll cause lags with slim governor since its basically an on demand governor
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!

My better powersave CPU configuration for rooted users (Stock kernel)

Hello, I was recently playing around with the CPU settings in 3C CPU manager, and I noticed the default powersaver configuration isn't that good, compared to mine.
I am using the stock kernel.
Firstly, I noticed that the interactive governor is too sensitive for the A53 cores and it would cause the CPU frequency to jump up to the maximum very easily.
Secondly, I felt that based on my general day-to-day usage (heavy web browsing + some gaming), 4 cores are more than sufficient.
I played around with the ondemand governor and just set its powersave bias to 185, then took all the cores except cores 0, 1 and 4 offline (2x A53 + 1x A57).
I set the A53 cluster to run on the ondemand governor and the A57 core to run on the default interactive governor.
If you want, you can downclock the A53 cluster to 1.34 ghz after you disable pnpmgr, and you should be able to get 6.5 hours of heavy-usage SOT on the stock kernel with little to no lag at all, on a ROM that has Force GPU rendering on.
Do try it out and let me know of the results! :good: (don't forget to disable wakelocks for Google Play Services too)

this is reeeeally high powersaver, too much compromise, and there are people who reach that SOT without any mod

throcker said:
this is reeeeally high powersaver, too much compromise, and there are people who reach that SOT without any mod
Click to expand...
Click to collapse
Hmm... compared to the stock powersaver this actually gives higher scores in both single core and multi core benchmarks. I also have auto-brightness on. However, I get absolutely no lag and my usage is very heavy, almost all my SOT is web browsing on HSPA, with some gaming here and there. I'm open to suggestions though.
For comparison purposes, on the stock powersaver configuration (A53 only), I get 4 hours and 14 minutes of SOT at 1%.
Without downclocking on this configuration, I got 7h 6min of total time and 5h SOT from 98%.
{
"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"
}

throcker said:
this is reeeeally high powersaver, too much compromise, and there are people who reach that SOT without any mod
Click to expand...
Click to collapse
only way i could get that amount of SOT without any mods is if i disabled any and all data/signal and just sat at a picture all day

Which core is a53 cluster and which is a57?

acidspider said:
Which core is a53 cluster and which is a57?
Click to expand...
Click to collapse
0,1,2,3 are the little(A53) and 4,5,6,7 are the big one(a57)

Sorry but these setting were pretty much worthless here. the default settings in the LeeDroid Kernel are much better. Freezing Google Play Services just screwed up my contact list and didn't do much else.
applied your settings (phone was at 97%) went to thanksgiving dinner at my sisters never picked up the phone but about 3 times and made 2 phone calls less than 10min each and used almost 57% of the battery in 4 hours. I typically use about 40% battery in a full 9 hour day at work.

clsA said:
Sorry but these setting were pretty much worthless here. the default settings in the LeeDroid Kernel are much better. Freezing Google Play Services just screwed up my contact list and didn't do much else.
applied your settings (phone was at 97%) went to thanksgiving dinner at my sisters never picked up the phone but about 3 times and made 2 phone calls less than 10min each and used almost 57% of the battery in 4 hours. I typically use about 40% battery in a full 9 hour day at work.
Click to expand...
Click to collapse
freezing google play service breaks more then helps.. also stock settings are much better then any of these "powersaving " settings...actually amplify and greenify with donate app and xposed do help also a lot and using high accuracy mode for location.
but keeping the kernel settings at nearly stock, maybe just lower clocks for both clusters helps a lot.
the problem is, that in 5.x.x LITTLE.big SoCs aren't really optimized...so it will do much better with MM...and maybe when kernel devs are getting more knowledge about LITTLE.big so they could together tweak it more.

clsA said:
Sorry but these setting were pretty much worthless here. the default settings in the LeeDroid Kernel are much better. Freezing Google Play Services just screwed up my contact list and didn't do much else.
applied your settings (phone was at 97%) went to thanksgiving dinner at my sisters never picked up the phone but about 3 times and made 2 phone calls less than 10min each and used almost 57% of the battery in 4 hours. I typically use about 40% battery in a full 9 hour day at work.
Click to expand...
Click to collapse
DeeZZ_NuuZZ said:
freezing google play service breaks more then helps.. also stock settings are much better then any of these "powersaving " settings...actually amplify and greenify with donate app and xposed do help also a lot and using high accuracy mode for location.
but keeping the kernel settings at nearly stock, maybe just lower clocks for both clusters helps a lot.
the problem is, that in 5.x.x LITTLE.big SoCs aren't really optimized...so it will do much better with MM...and maybe when kernel devs are getting more knowledge about LITTLE.big so they could together tweak it more.
Click to expand...
Click to collapse
Oops... I meant disabling wakelocks for google play services :silly:
This has only been tested on the stock kernel...