Database Users

Interactive Vs Conservative Governor? CDMA Battery Life Tips

What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.

akaine2001 said:
What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Click to expand...
Click to collapse
Thank Samsung for breaking ondemand on every sgs phone.
Sent from my SCH-I500 using XDA App

Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...

akaine2001 said:
Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...
Click to expand...
Click to collapse
You are doing something wrong. Conservative is not choppy on my device and the CPU will always ramp up faster than a human being can judge the response time.
Sent from my SCH-I500 using XDA App

My phone makes it the entire day with heavy use, this means about 20 - 10 min phone calls one or two lasting 30 min, texting my wife all day at work, checking emails, and angry birds for at least 1 hour a day i love that game but I suck at it lol. Something that I found is that the phone will last almost an hour of being on the phone after it hits 0%. In my pocket it lasted 4 hours at 0% the day before yesterday. I thought maybe this is on purpose so you have more then enough time to make it to a charger. When I first downloaded angry birds I played it for three hours straight with the screen at full brightness (i always keep it at full brightness, looks prettier that way) I know it was three hourse because it was while i was waiting at the hospital I got there a little before 7 and wasnt called until 10. Overall I am very pleased with the battery life of this phone not so much with other aspects but battery life and lag never came into my mind as a complaint for this phone, except with all the stock touchwiz stuff.

As adrynalyne said, CPU's scaling changes faster than human's perception. It's your phone or setting that's having an issue.

4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.

I meant "reliable" not trailer.

I get about 5 hours of screen time with little voice calls on wifi.

I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge, having even made it to 44 hours on a very rare occasion and that's without setcpu profiles even set.

Wtf... my phone is brand spanking new and I get about 4ish hours of screen time on a full charge, with the lowest brightness + screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on.... wtf. This is running on conservative or interactive the whole time..... wtf!!! With wifi on and 0 extra screens or Widgets using launcher pro without animations... wtf!!!
Sent from my SCH-I500 using XDA App

+1... stock battery indicator is not accurate. Get the accurate battery mod.
soba49 said:
4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse

Terror_1 said:
I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge...
Click to expand...
Click to collapse
That's because you don't use your phone.
Go play NFS for 3 hours and get back to us.
MoShiBa said:
...screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on...conservative or interactive the whole time...
Click to expand...
Click to collapse
What's the screen filter app? Conservative and interactive? That's SetCPU?
I wouldn't worry about these guys coming in here saying they're getting 2 days of use either. They're not using the phone anywhere near as much as you. I've had 3 of these things and know 2 guys with them. They all got the same battery life. You don't see anyone posting any screenshots, do you?

Me and my gfs fascinate gets about same battery life in our apt and hers is still DI01 and i'm on DJ05... she has jts 11/16 kernel and i have the 12/21 voodoo5 and we get about the same battery life... dependent on how much we use the phone. .... so just use your phone, and charge it as necessary... its better for the type of battery we use anyways in our phones... **************************************************************************************closed.**************************************************************************************

will underclock provide realy more battery and reduce heat ?

hy there,
im on latest sokp rom on my g2 (d802)
i want to get more juice from my battery, so I setup my core setings at 1036 mhz max and minimum 300 mhz.
wil this provide me a lot off battery in real life and will it also reduce heat ? even if i watch hd movie or play graphical games

In theory yes it should but not as much as you think cause it will be offset because it will have to keep a higher frequency for a higher period of time. Temperature should be reduced a lot but keep in mind games will lag if they need the extra power

drivenby said:
In theory yes it should but not as much as you think cause it will be offset because it will have to keep a higher frequency for a higher period of time. Temperature should be reduced a lot but keep in mind games will lag if they need the extra power
Click to expand...
Click to collapse
hmm, well after i underclocked i played asphalt 8 for like 20 mins and game performance did not changed significantly. and i feel that the phone is now cooler then before when multitasking stuff.
is there also another way that can realy increase battery life besides underclocking.

abati said:
hmm, well after i underclocked i played asphalt 8 for like 20 mins and game performance did not changed significantly. and i feel that the phone is now cooler then before when multitasking stuff.
is there also another way that can realy increase battery life besides underclocking.
Click to expand...
Click to collapse
you also can try custom governors

Hey there, you may be suffering a placebo effect, it can give you a little extra juice, but in my opinion you get most of your battery with these 4:
1. Reduce timeout to 15sec.
2. Adjust screen brightness to be as low as possible (lux helps with this)
3. Eliminate vibrations of any kind (haptic feedback, notications that make your phone vibrate ex. whatsapp) and so on...
4. Data (Use Wifi if possible, 2g when you are not using your phone and airplane mode in some cases extend your battery for a lot too)
Don't expect to get more than 30 min of extra use changing your kernel configurations. ALTHOUGH if you are a heavy user (let us say, in this case, a heavy gamer) there are some kernel configurations you should check.
Also remember, if a task takes you 30min but only consumes 1 % per 30 min compared to doing the exact same task in 30seconds consuming the same 1% which one is worth it?
Phones hardware is way above the software we have available at this time, underclocking and undervolting is an option and you won't feel the difference but, as I've stated before, those are not the main issues of the battery drain.
I hope I've helped you out!

How to Squeeze your OPO battery!

As the title sugests one of the main goals for everyone who scrolls and uses his OPO either to avoid awkward situations, for work or simply to check social networks etc, you want to have the best GOD DAMN Battery life you can possibly squeeze from your 3.1k mAh battery !
I am not responsible for any damage to your phone. Read before downloading or posting in the thread. Proceed with caution if you have no experience.
So to start off, i'm already assuming you have your OPO rooted, which is a must for this guide.
So you can go for any custom ROM of your choosing as long as it supports the Kernel of your choosing.
Before trying to say which Kernel is best, i'd like to state that I have a really simple philosophy which is,If it ain't broke don't fix it, so I go with the AK Kernel because it never failed me, has a really good comunity to back it up and is the only tested kernel for the OPO in the UKM Thread.
( Don't worry i'll paste the links to all of these things that I'm speaking of )
After you got your Kernel up and going you're gonna download the UKM ( Universal Kernel Manager ), which will enable you to use Synapse on your device.
So now you have the Kernel and UKM, which means it's time to flash them all.
Now flash your UKM file and after installing it flash the Kernel and you should be set!
Once the Phone has booted, just make sure to download Synapse from the playstore. I wouldn't recommend changing the voltajes on your cpu because you can really **** your **** up which no one wants!
I'm running with this profile for over 3 months and it has done me wonders ( pics below )
Synapse Screenshots
This means your CPU will be running 1.3 GHz less about 80% of the time, the suspended Cpu frequency will be 300-400 MHz lower and the GPU which goes to an all time high of 578 MHz every time you install a new custom rom will be lowered to 200 MHz. This will result in about 40% more battery AT LEAST.
I don't have any photos showing my battery time because i'm a bit stupid, but the next week i'll try to screenshot my battery life and show you, however, I do know that i'm averaging about 6 hours SoT with both Wi-Fi and Data turned on 24/7.
Also a really good and must have App that goes really well with this is Leandroid which makes your Data shut off after X minutes of the device being disabled. If you feel you're device is running low on battery because of uknown sources, I advise you to download Wakelock Detector to check if there is something keeping your cpu ramping up when it shouldn't be.
This is not optimal for a 3.1k mAh battery but, keep in mind that the memory leak issue is still in the works and this is the best I could do in the given situation.
Another point I would like to focus before ending this post is the screen brightness. We all know that Android L stock Brightness control sucks ( if you don't now you do ), so I recomend using Lux Lite, which controls your screen brightness by adjusting it whenever it receives more or less light in the sensor, and it has worked wonders for me, it you're interested in a profile I will link mine
Now I won't bore more, I hope this "guide" was helpful to you and if you liked it don't be shy to press the thanks button.
Links
Kernel
UKM
Synapse
LeanDroid
Wakelock Detector
Lux lite
THIS DOES NOT WORK WITH OXYGEN OS

TL;DR - limit all your frequencies to 1/2 of what your phone is capable of.
Theoretically it makes sense. But in real world if you do some thinking - the phone would do task X in 5 seconds @ max frequency then go to sleep. If you limit the clock to half of the original value - it doesn't use 2 times less power, it uses slightly less than max. However, you are forcing it to do that task in 10 seconds @ half frequency before going to sleep. This means that it will use more power to achieve the same goal.
I would advice you to find a suitable governor rather than deliberately making your device slower than necessary.

nitrobg said:
TL;DR - limit all your frequencies to 1/2 of what your phone is capable of.
Theoretically it makes sense. But in real world if you do some thinking - the phone would do task X in 5 seconds @ max frequency then go to sleep. If you limit the clock to half of the original value - it doesn't use 2 times less power, it uses slightly less than max. However, you are forcing it to do that task in 10 seconds @ half frequency before going to sleep. This means that it will use more power to achieve the same goal.
I would advice you to find a suitable governor rather than deliberately making your device slower than necessary.
Click to expand...
Click to collapse
In all my runs with 2.5 GHZ and 1.2 GHZ I noticed a lot more difference running it with a lower clockspeed. ( 1- 1.30 hours more SoT )
I do know that the device requires more cycles to open an app while it's underclock however, i'm passing on what worked for me ( through some tests )

Hey can you tell me the procedure to flash on 05q??
I am trying to get good battery, now I am running franco kernel it does not give good battery. So if you can then please post the instructions.

Do you have root and recovery already installed?

Only 4 cores are used

Hello,
I have a peculiar problem with my OnePlus Two
The faster A57 cores don't get activated, I have tried using Antutu, played Asphalt 8 And NFS NL for hours.
But the cores just won't get triggered
I'm using A1 CPU tool to monitor the same.
Even CPU Z wouldn't show me any activity on the other 4 cores while Antutu was running.
Any ideas? It's brand new can be returned
Oxygen OS - 2.1.1
A2003_14_151011
Sent from my C6602 using XDA Free mobile app

Denhot said:
Hello,
I have a peculiar problem with my OnePlus Two
The faster A57 cores don't get activated, I have tried using Antutu, played Asphalt 8 And NFS NL for hours.
But the cores just won't get triggered
I'm using A1 CPU tool to monitor the same.
Even CPU Z wouldn't show me any activity on the other 4 cores while Antutu was running.
Any ideas? It's brand new can be returned
Oxygen OS - 2.1.1
A2003_14_151011
Sent from my C6602 using XDA Free mobile app
Click to expand...
Click to collapse
I just installed A1 CPU to verify your issue.
It shows cores 0,1,2,3,4 are used at 1344ghz for me as well.
When i check with synapse (i'm on AK kernel) it shows all cores are used.
I guess it's a limitation with A1 CPU tool. Try with other tool that supports such architecure.

I was sceptical on the same but, out of the box I remembered seeing 1777 MHz frequencies.
Thanks a lot
I shall try more tools and get back.
Though I think if you're on a different kernel and had the A1 CPU tool been correct it would be redundant, Because core allocation would be done on kernel level (in my knowledge).
Sent from my iPad using Tapatalk

I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?

jemcik said:
I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?
Click to expand...
Click to collapse
Hi Jemcik, hi Denhot!
I'm facing the same issues on my new device and it's definately not normal!
With a battery level of 19% I was not able to get the 4 A57 cores online, which results in lower system performance. Have you found a solution?
@Denhot!
Maybe we should rename the thread into: IS OPT PERFORMANCE REALLY DEPENDENT ON BATTERY STATUS AND IS IT A ROM FEATURE OR AN ISSUE!?
I think, one of the kernel devs should be able to answer this question.

ollimi1 said:
With a battery level of 19% I was not able to get the 4 A57 cores online...
Click to expand...
Click to collapse
It looks like some system configuration files with kernels activation policy have to be edited,
but I haven't found yet which files exactly.

jemcik said:
It looks like some system configuration files with kernels activation policy have to be edited,
but I haven't found yet which files exactly.
Click to expand...
Click to collapse
I've never experienced such a function!
CPU power depending on battery voltage!? 62k with full battery, 49k with 20% battery both with same CPU temps!
Hopefully not a general problem on our side with the motherboard Voltage Regulator or something.
Have you been to a kernel thread and asked this question? If not, I will ask this in AK's kernel thread. Maybe he knows more about it!

The 4 high performance cores will only be activated when needed. What app are you using to check the core usage? Every now and then you should see 2 of the high performance cores sometimes coming to life every now and then, with the other 4 power efficent cores being more busy. Use CPU-Z to check.
Due to the way Oxygen OS's stock kernel works, only 2 of the high performance cores will ever be active, alternating between the 4 cores in an attempt to keep the phone cool and not throttle as often. If you want all 4 high performance cores to be active as well as overclocking it back to its original speeds, you'll need to flash a custom kernel.

jemcik said:
I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?
Click to expand...
Click to collapse
Hi,
would like to share I don't have a similar experience, with NFS NL or Asphalt, phone was consistent with no lags even when it got unbearable to hold.
I as playing and simultaneously screen mirroring over to a TV.
Going from 65 to 25% over a long course.
I normally won't let my battery fall below 20%.
So the thing about Li-ion/pro is that as you go lower voltage decreases so to provide same power draw current increases.
Basically it would heat up faster.
That can be a reason combined with that their might be inbuilt measures to save battery like you said, nor as an engineer I would recommend you to stress your phone at those levels.
I can't explain the lag at 45%, didn't find it might try real racing 3 later to check.
Sent from my iPad using Tapatalk

trapistasajt said:
The 4 high performance cores will only be activated when needed. What app are you using to check the core usage? Every now and then you should see 2 of the high performance cores sometimes coming to life every now and then, with the other 4 power efficent cores being more busy. Use CPU-Z to check.
Due to the way Oxygen OS's stock kernel works, only 2 of the high performance cores will ever be active, alternating between the 4 cores in an attempt to keep the phone cool and not throttle as often. If you want all 4 high performance cores to be active as well as overclocking it back to its original speeds, you'll need to flash a custom kernel.
Click to expand...
Click to collapse
This is consistent with what I've noticed. The time It didn't, a simple reboot helped solve it and it hasn't occurred since.
Also these tools can't monitor the other cores, if you're rooted why not try synapse as helkat suggested
Sent from my iPad using Tapatalk

Denhot said:
This is consistent with what I've noticed. The time It didn't, a simple reboot helped solve it and it hasn't occurred since.
Also these tools can't monitor the other cores, if you're rooted why not try synapse as helkat suggested
Sent from my iPad using Tapatalk[/QUOTE
Thanks man!
I know how the S810 should work!
But I thought the performance issues have only to do with the temps. But now it seems it have also to do with the battery level.
It would be good if someone tries to reproduce the following to verify it:
1. One run Antutu benchmark with fully charged battery and room cool temps.
To be sure the conditions are the same, shut the display off for one or two minutes, than start display again, kill all recent apps and run Antutu test and note the results.
2. Than wait or do something until your battery is down to 20%, shut the display off for the same time, kill recent apps and start Antutu test run again and compare the results.
I've also tried the same after a reboot, with always the same results.
With 100% I get scores between 60 and 66k and with lower capacity (20%) I get only 48 till 50k!
I am not interested about the benchmark results, but I need to know if this only occurs on my side.
Click to expand...
Click to collapse

So, guys!
I have tested it the last few weeks and it is a fact that the performance in benchmarks is dependent by the battery level.
We have tested it with 3 devices and it is always the same.
But thank God, it seems on the devices perfomance themselves (in apps/ui) this has no effect!
But each one can replicate this behavior very easy!

ollimi1 said:
Hi Jemcik, hi Denhot!
I'm facing the same issues on my new device and it's definately not normal!
With a battery level of 19% I was not able to get the 4 A57 cores online, which results in lower system performance. Have you found a solution?
@Denhot!
Maybe we should rename the thread into: IS OPT PERFORMANCE REALLY DEPENDENT ON BATTERY STATUS AND IS IT A ROM FEATURE OR AN ISSUE!?
I think, one of the kernel devs should be able to answer this question.
Click to expand...
Click to collapse
I have the same issue! When battery level goes lower than 20%, my A57 kernels become offline. I checked this with CPU-Z and PerfMon. And this is the same on stock or custom kernel. Now I am using Boeffla kernel. The most frustrating is that my UI suffer from this. I have lot of lags in simple apps, such as calculator or some messengers.

Same issue here, there are threads in one plus forums.
I think the threashold level is at 40 % ?? They made this to keep the battery up. You can also see faster battery drop till the 40-30% mark then it is harder to kill the battery.
I am also dissapointed in this, maybe we can search the kernel sources ? Or is there a daemon app that triggers this?
I received the phone with 20%-30% battery, started an antutu knowing how powerfull 810 chip is, then boom 45k same as the previos phone i had with 801 chipset...i was like what the fxck....runing antutu again with full battery - 66k.

well i have run benchmark in back ground with few game and apps .. and checked with cpuz max that i have notice was around 50-60% cpu load still 2 off those a57 cores were off using this device for 2-3 days it always turns off 2 cores for me rest 6 is working most of the time :/ Even in battery saver mode .. i am not sure if this is a cpuz issue as i have not rooted my device yet so cant say properly ..
Also i face some freq. benchmark issue like in benchmark it scores around single core - 690 multicore - 2.6K .. and if i restarts device it scores normal - 1.1K and 4.5K .. i have no idea whats wrong with this :/

20% Battery Mark
The drop in performance at 20% Battery is standard behavior of the Rom and Stock Kernel. The Big Cluster (A57) is completly shut down to save Battery. If you dont want this you have to use a custom Kernel which is able to switch this Battery saving strategy off. Boeffla Kernel for example can do that.

Read http://www.anandtech.com/show/9828/the-oneplus-2-review/2.
They "optimized" the soc.....
No they just turned off some cores so there is no heat problem.
So I think this is my first and latest oneplus.

they've hit the mark! What the hell, i think they must be sued for false marketing. Its just like buying a car with 400 hp and those hp are only there when i'm parked or listen to music, if i'm on the highway or on the ridge the car has 100 hp...wtf :|

Killer2k8 said:
they've hit the mark! What the hell, i think they must be sued for false marketing. Its just like buying a car with 400 hp and those hp are only there when i'm parked or listen to music, if i'm on the highway or on the ridge the car has 100 hp...wtf :|
Click to expand...
Click to collapse
Calm down lol it's actually good on their part. Shutting down A57 cores on low battery is a good thing because the A53 cores use much lesser battery. If you're out on a trip and have 10% battery, with the A57 cores this will probably drain off within an hour of intermittent usage. When only the A53 cores are active, the battery life will increase greatly.
Companies design phones for average users, not just gamers. If you don't want this feature, root your phone, flash boeffla's kernel and disable the BCL Battery Driver. It's as simple as that

[OFFICIAL] GlassCannon - Interactive tweak port N5X l G4

Following the advice of @shadowstep and @Davey126 I have created a thread to separate this from the whole Interactive guide thread by @soniCron. This is due to (1) one, the thread is no longer updated for almost a year and (2) two; to explain the tweak, establish baselines/guides for testers and to gather more interested individuals to try it out.
-------------------------------------------
Introducing GlassCannon!​
Description: A sound modification to the famous interactive parameters. Provides the smoothest interface, great performance while bestowing the lowest frequencies available. Ramping up quickly to maximize "inputs" from I/O overheads then immediately ramping down once tasks are done. The perfect balance between lowering down your frequency, and finishing up tasks quickly.
Why Glasscannon? Why not?
Who am I? I came from the hammerhead scene. I have been modding interactive parameters for more than 2 years and owns a community called: Android Battery Community whom has its own fair share of followers but has been quite stagnant for almost a year ever since my hammerhead broke. Though, I have been tweaking things with other devices; LG G4, Samsung Note 6, OPO and other smartphones that I got my hands on. Now I think it's time for me to get into the Nexus 6P scene. And after just literally 2 days after I posted the tweak, there are messages and posts tempting me to port it to N5X and LG G4, and with enough encouragement as well as a promise of testers; I edited the values matching my GlassCannon tweak with the former LG G4 .txt file I have in my desktop and here it is!
The difference? After years of being a paranoid about my battery (literally looking at dashboards, cpu cycles etc. you know, that guy who just tends to not be satisfied about everything) I finally settled down and read a lot of things and made it as my basis. Most tweaks in here uses target load as an optimal way to force cores to stick into lower frequencies but we won't be doing that with GlassCannon. We will be using two underrated tunables: above_hispeed_delay and input_boost. This two underrated tunables are being neglected for years, though some used it quite efficiently; I have yet to see a tweak that maximizes the two tunable's potential. We would be using above_hispeed_delay as a substitute to the unpredictable target_load. Instead of assigning too much within a tunable that we can't even lay our finger on how it works properly, why not let the SoC handle it and assign a delay along with timer_rate so it can run efficiently? And let input_boost jump up here and there to provide quick surge whenever there are tasks running under the hood.
Look under (Version: N5X l G4):
Code:
[COLOR="Gray"]/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 384000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1440000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 93
/sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0 600000:19000 787200:20000 960000:24000 1248000:38000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 50000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 600000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack 380000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 29 384000:88 600000:90 787200:92 960000:93 1248000:98
/sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 60000
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu0/cpufreq/interactive/boostpulse_duration 0
/sys/devices/system/cpu/cpu4/cpufreq/scaling_governor interactive
/sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq 384000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq 1824000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/go_hispeed_load 150
/sys/devices/system/cpu/cpu4/cpufreq/interactive/above_hispeed_delay 20000 960000:60000 1248000:30000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_rate 60000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/hispeed_freq 960000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_slack 380000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/target_loads 98
/sys/devices/system/cpu/cpu4/cpufreq/interactive/min_sample_time 60000
/sys/devices/system/cpu/cpu4/cpufreq/interactive/boost 0
/sys/devices/system/cpu/cpu4/cpufreq/interactive/align_windows 1
/sys/devices/system/cpu/cpu4/cpufreq/interactive/use_migration_notif 1
/sys/devices/system/cpu/cpu4/cpufreq/interactive/use_sched_load 0
/sys/devices/system/cpu/cpu4/cpufreq/interactive/max_freq_hysteresis 0
/sys/devices/system/cpu/cpu4/cpufreq/interactive/boostpulse_duration 0
/sys/module/cpu_boost/parameters/input_boost_freq 0:600000 1:600000 2:600000 3:600000 4:960000 5:960000
/sys/module/cpu_boost/parameters/sync_threshold 1248000
/sys/module/cpu_boost/parameters/boost_ms 40
/sys/module/cpu_boost/parameters/migration_load_threshold 15
/sys/module/cpu_boost/parameters/load_based_syncs Y
/sys/module/cpu_boost/parameters/shed_boost_on_input N
/sys/module/cpu_boost/parameters/input_boost_ms 300
/sys/module/cpu_boost/parameters/input_boost_enabled 1
/sys/module/msm_performance/parameters/touchboost 0
/sys/module/msm_thermal/core_control/enabled 0
/sys/module/msm_thermal/parameters/enabled Y[/COLOR]
Explanation:
go_hispeed_load: Anything between 85-94 is average by my tests, it tends to stick to hispeed_load 40-60 which is what I think would be "optimal" for our cat.
above_hispeed_delay: The most important part of our tweak along with input_boost. This should set up the perfect "delay" so cpu cores could adjust and decide before ramping up to higher frequencies. Our frequency set as hispeed from little cluster is 600000.
target_loads: We won't be dwelling much in this. We put a small amount so that our frequency could ramp up if needed and take a pause on frequencies we deemed to be really significant; 600mhz, 672mhz, 960mhz and 12348mhz. Along with hispeed_delay, it should provide low consumption and tend to stick on 384mhz and 600mhz 89% of the time.
timer_slack: Put it to 380000, just trust me.
max_freq_hysteresis: Asking why theres jitters and a bit of stuttering on your screen? this is the culprit. Turn it to 0 and you will be fine as long as you correct the other tunables. This is because hysteresis actually uses "former" frequencies to calculate which frequency would be best to ramp up to next. If you tend to stick to lower frequencies more, with this on then you will be sticking at low frequencies almost forever, which obviously isn't something good.
input_boost: Now, to explain why this is important; there are two things I would like to emphasize. (1) One, this value was made so that under the hood tasks as well as simple bumps to your frequency if there is a notification, sync etc. would be possible. (2) this value is extremely useful to provide that quick boost to complete tasks with ease. The big clusters would have an input_boost of 633000 which was supposed to be the stock mhz. Why? I deemed that the big cluster isn't that necessary unless you are running an extremely graphic heavy game. So tone it down to 384mhz underclocking it and provide input boost to the mhz that was supposed to be the stock frequency, increasing battery life without sacrificing anything.
Will this be updated? NO, NEVER. I am asking myself why does this other "tweaks" update from time to time if there are no kernel parameters that are changing? Aren't all those tweaks supposed to be tested hundreds of times before releasing? Then why change the parameters again? Am I asking too much? Am I fat? NO. Just NO. EXCEPT if there will be changes within the interactive parameters then sure.
Maximal, Minimal and Nominal Frequencies? Not to hurt anyone's heart but I personally think that this is a retardified(if that is in fact a word) version of "I shall say something smart". I don't see the point of determining what the nominal, maximal and minimal frequencies are as we can't even put a finger what they literally mean. This is actually "subjective" and I really find this so called nominal frequencies irrelevant. Please don't hate.
Do note that most of the explanations above were not edited and is still pretty much the same as N6P description because I'm lazy af.
​Credits: @soniCron, @xSilas43, @shadowstep for pointing out the missing timer_slack and input_boost, google for many things to read, this website for music while typing, that website for providing me more things to read, a bucket of fries and two chickens to make me company.
Go ahead and feel free to download the .txt file below and happy tweaking!
======================​A SINCERE THANKS TO EVERYONE WHO TESTED AND PARTICIPATED
Tips Hat​
After many things happening and after more than a month, I am really glad that we have succesfully ported GlassCannon to N5X and LG G4 (or any other device with same cpu structure). I am proud to present to you the fruits of the small labors of both me and the team as well as others behind the scene testing GlassCannon for your devices.
What has been the verdict? Overall, via landslide; the GlassCannon's Beta2.0 has come out on top. I figured and of course realized after the alphatest that people in N5X community complained (though in small dose) about stutters and a small lag in some apps. Most were debunked especially if you are using an online app but I had to wrap around everything and investigate further. Even though I promised that the Beta would be more battery efficient, I adjusted it so that it should provide a much better performance and smoothness without compromising the battery life of our cats. And thus, the verdict is Beta 2.0 *autistic screeching*
Special thanks to: @Curlyfry2121 @shadowstep @crian @spartan268 @IcyGlacial @Lazerlord
Just a headsup, I will be leaving the Alpha below for other people to download if they still want some!
Grab a copy below! Enjoy!​

Official Testers:
@shadowstep N6P
@Lazerlord
@Curlyfry2121
@mesmurized
@@spartan268
@deani77 N6P
@igoorsoouza
@CazeW
Credits to:
Everyone whom are secretly using the GlassCannon profile. To my Kentucky Fried Chicken for keeping me company. @Davey126 for encouragement and other stuffs, @The Flash because you are the fastest man alive, @shadowstep for being a MTG fan, @flar2 for being an awesome developer and supporting this kind of tweaks, @soniCron for starting this and many more. Huge thanks! and I hope this will go on for the better!

Thanks
Sent from my Pixel using Tapatalk

Firefox, Google plus, and Snapchat, with a little Hangouts during school where the data connection is little to none half the day.

Curlyfry2121 said:
Firefox, Google plus, and Snapchat, with a little Hangouts during school where the data connection is little to none half the day.
Click to expand...
Click to collapse
Thanks for the second full cycle *takes notes*
Well thats a huge steep slope we have. I can see where thise battery drains come from and you really have to do something about those. Have you ever considered airplane mode while you are at an area where there's little to no signals? Those red marks should have drained your battery like crazy! At first I was skeptical when you said you have a bad signal lol.
Now about the cpu times etc.:
(1) One, that is pretty much a great cpu stats for both little and big. I can see that it sticks to 600mhz the way I tuned it too. Those little percentage above 600mhz are pretty nice, that means thst they never got stuck in that number for more than 30-40ms (above_hispeed_delay and timer_rate) doing the trick. (2) Two, I can even see the big cluster's cpu5 off, what more can I ask for? (Purely intentional to set a really high ts
Arget_load and go_hispeed_load at lowest frequency to make this happen) this means everythung works fine as intended (the way I tweaked it to be.)
Anyway this is to be expected for light usage. Btw could you please install accubattery for me and turn on "cpu core" on the overlay settings within the app? There should be 6 overlay batteries at your bottom right continuously changing to see cpu frequencies. Now with thst try a full cycle again and note this:
*At what apps does most of the cores get to red (above 3/4)
*In your observation, how long does it stick to yellow (1/2 above) and red frequencies? (Above 3/4)? Please tell in miliseconds e.g. red at 20ms most of the time etc.
You will see what I'm talking about when you install the app
Anyways continue again with a normal full cycle bro and I'll be waiting for the next update!

phantom146 said:
Thanks for the second full cycle *takes notes*
Well thats a huge steep slope we have. I can see where thise battery drains come from and you really have to do something about those. Have you ever considered airplane mode while you are at an area where there's little to no signals? Those red marks should have drained your battery like crazy! At first I was skeptical when you said you have a bad signal lol.
Now about the cpu times etc.:
(1) One, that is pretty much a great cpu stats for both little and big. I can see that it sticks to 600mhz the way I tuned it too. Those little percentage above 600mhz are pretty nice, that means thst they never got stuck in that number for more than 30-40ms (above_hispeed_delay and timer_rate) doing the trick. (2) Two, I can even see the big cluster's cpu5 off, what more can I ask for? (Purely intentional to set a really high ts
Arget_load and go_hispeed_load at lowest frequency to make this happen) this means everythung works fine as intended (the way I tweaked it to be.)
Anyway this is to be expected for light usage. Btw could you please install accubattery for me and turn on "cpu core" on the overlay settings within the app? There should be 6 overlay batteries at your bottom right continuously changing to see cpu frequencies. Now with thst try a full cycle again and note this:
*At what apps does most of the cores get to red (above 3/4)
*In your observation, how long does it stick to yellow (1/2 above) and red frequencies? (Above 3/4)? Please tell in miliseconds e.g. red at 20ms most of the time etc.
You will see what I'm talking about when you install the app
Anyways continue again with a normal full cycle bro and I'll be waiting for the next update!
Click to expand...
Click to collapse
Gotcha! And yeah I did use airplane mode one time but I forgot to today lol. I will install it and I'll follow your instructions for tomorrow's cycle, and yeah now you get what I meant ?

phantom146 said:
Thanks for the second full cycle *takes notes*
Well thats a huge steep slope we have. I can see where thise battery drains come from and you really have to do something about those. Have you ever considered airplane mode while you are at an area where there's little to no signals? Those red marks should have drained your battery like crazy! At first I was skeptical when you said you have a bad signal lol.
Now about the cpu times etc.:
(1) One, that is pretty much a great cpu stats for both little and big. I can see that it sticks to 600mhz the way I tuned it too. Those little percentage above 600mhz are pretty nice, that means thst they never got stuck in that number for more than 30-40ms (above_hispeed_delay and timer_rate) doing the trick. (2) Two, I can even see the big cluster's cpu5 off, what more can I ask for? (Purely intentional to set a really high ts
Arget_load and go_hispeed_load at lowest frequency to make this happen) this means everythung works fine as intended (the way I tweaked it to be.)
Anyway this is to be expected for light usage. Btw could you please install accubattery for me and turn on "cpu core" on the overlay settings within the app? There should be 6 overlay batteries at your bottom right continuously changing to see cpu frequencies. Now with thst try a full cycle again and note this:
*At what apps does most of the cores get to red (above 3/4)
*In your observation, how long does it stick to yellow (1/2 above) and red frequencies? (Above 3/4)? Please tell in miliseconds e.g. red at 20ms most of the time etc.
You will see what I'm talking about when you install the app
Anyways continue again with a normal full cycle bro and I'll be waiting for the next update!
Click to expand...
Click to collapse
Accubattery requires me to pay to use the overlays, and I have no money what so ever on my play account :crying: is there anything else I could use instead?

Curlyfry2121 said:
Accubattery requires me to pay to use the overlays, and I have no money what so ever on my play account :crying: is there anything else I could use instead?
Click to expand...
Click to collapse
I forgot about all of that ? well I dont really recommend the other alternatives since most are outdated. Though cpu float should do the trick

I'm going to start all over with my testing again in case my previous one was skewered for some strange reason. Downloaded gboard instead of bb keyboard and rebooted my phone. I'll reset the CPU stats as well after my app updates are done since that'll likely tax things a little too much. I'll have proper results probably 24 hours from now.
My main culprit right now is that the g4 skin is more heavyweight than thought to be so a nudge more CPU power is needed for general tasks to account for it if that makes any sense. Otherwise i run my phone fairly lean as it's debloated and i make use of greenify, amplify, and powernap so there's minimal services and apps in the background at most times.

spartan268 said:
I'm going to start all over with my testing again in case my previous one was skewered for some strange reason. Downloaded gboard instead of bb keyboard and rebooted my phone. I'll reset the CPU stats as well after my app updates are done since that'll likely tax things a little too much. I'll have proper results probably 24 hours from now.
My main culprit right now is that the g4 skin is more heavyweight than thought to be so a nudge more CPU power is needed for general tasks to account for it if that makes any sense. Otherwise i run my phone fairly lean as it's debloated and i make use of greenify, amplify, and powernap so there's minimal services and apps in the background at most times.
Click to expand...
Click to collapse
Not to jump on some hate-wagon here but I am really against powernap, thought that's just me.
I have gboard as well and has chosen a substratum dark overlay for it (if you don't have a substratum support just get the material black theme) also, gboard consumes battery a little tinsy bit than your normal keyboard, don't forget to disable the snippets and share to google statistics in the preference tab to avoid continuous syncing. I'll be waiting for the results and if everything still seems to lag, I might cook something different especially for you

Reasons for new thread:
3) This is a different method to the once described before.

Android O, Naptime FORCE DOZE, My previous stats are as follows;
(This was using my custom governor tweaks and the skipped/unknown lost battery in the middle is a bootloop)

Forgot this xD

After 2-3 days on the latest version, I continue to see overnight battery usage (sleep+doze+battery) trending a bit lower then with my prior profile HawkFlyv1.2. This along with a noticeable increase in responsiveness, puts GlassCannon at the top of my current list.
Good work @phantom146. I'll try to work on providing details for this alpha test in the next day or so

LazerL0rd said:
Reasons for new thread:
3) This is a different method to the once described before.
Click to expand...
Click to collapse
LazerL0rd said:
Android O, Naptime FORCE DOZE, My previous stats are as follows;
(This was using my custom governor tweaks and the skipped/unknown lost battery in the middle is a bootloop)
Click to expand...
Click to collapse
That instagram... :laugh:
LazerL0rd said:
Forgot this xD
Click to expand...
Click to collapse
Any stutters or jitters? phone freezes etc.?
About the battery life, any comments on that? and the one we talked about the pm (regarding the ramping down and input_boost) any thoughts after this cycle?
Will wait for your answer
Mesmurized said:
After 2-3 days on the latest version, I continue to see overnight battery usage (sleep+doze+battery) trending a bit lower then with my prior profile HawkFlyv1.2. This along with a noticeable increase in responsiveness, puts GlassCannon at the top of my current list.
Good work @phantom146. I'll try to work on providing details for this alpha test in the next day or so
Click to expand...
Click to collapse
I am glad you are liking this profile and will wait for more results, also; it would help me if you can try GlassCannon with heavy usage using heavy graphical games such as need for speed asphalt, nba etc. I really want to see if we have any kind of lags or stutters using high performance games. Thanks for the continuous support!

phantom146 said:
That instagram... :laugh:
Any stutters or jitters? phone freezes etc.?
About the battery life, any comments on that? and the one we talked about the pm (regarding the ramping down and input_boost) any thoughts after this cycle?
Will wait for your answer
I am glad you are liking this profile and will wait for more results, also; it would help me if you can try GlassCannon with heavy usage using heavy graphical games such as need for speed asphalt, nba etc. I really want to see if we have any kind of lags or stutters using high performance games. Thanks for the continuous support!
Click to expand...
Click to collapse
Was getting stuttering with Geo Dash ?? but I think it's just the settings I've enabled and or it's bad optimisations. Battery is equal to or slightly less than my previous governor. After a while I don't see much stuttering (btw i had stuttering before on Geo Dash too xD). There's one thing I enabled that you didn't though. And it's a value called fast_ramp_down. I'm gonna try without it now and see if there's still stuttering.

Just checked and stuttering is MASSIVELY reduced by disabling that option. Well, I thought it would be good. Anyway here are today's stats;
PS - I've decided to keep it, with a few of my own changes xD and sorry about the recharging, I was watching some TV shows ?

LazerL0rd said:
Was getting stuttering with Geo Dash but I think it's just the settings I've enabled and or it's bad optimisations. Battery is equal to or slightly less than my previous governor. After a while I don't see much stuttering (btw i had stuttering before on Geo Dash too xD). There's one thing I enabled that you didn't though. And it's a value called fast_ramp_down. I'm gonna try without it now and see if there's still stuttering.
Click to expand...
Click to collapse
LazerL0rd said:
Just checked and stuttering is MASSIVELY reduced by disabling that option. Well, I thought it would be good. Anyway here are today's stats;
PS - I've decided to keep it, with a few of my own changes xD and sorry about the recharging, I was watching some TV shows
Click to expand...
Click to collapse
well thats good to hear I was really wondering why you were getting stutters as 4 of my testers never got them. Its cool it is your phone to begin with so just tweak away but thanks for keeping the tweak it means a lot to me that somebody will use them as a daily profile :good:
Btw, those stats are crap hahahaha I can't even see where to begin with those charging cycles haha :silly:

phantom146 said:
well thats good to hear I was really wondering why you were getting stutters as 4 of my testers never got them. Its cool it is your phone to begin with so just tweak away but thanks for keeping the tweak it means a lot to me that somebody will use them as a daily profile :good:
Btw, those stats are crap hahahaha I can't even see where to begin with those charging cycles haha :silly:
Click to expand...
Click to collapse
Tomorrow I'm trying a mix of yours and a few I've created before. I done a little research and it seems my idea should work. But it's more experimental than Android O :laugh:
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
The day after I'll test yours again, and I'll stay with whatever is better ?