Speed and Battery tweaks. - ZTE Axon 7 Questions & Answers

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!

Related

[INFO] Custom Kernels & Overclocking - FuguMod Ultra Pre Release

After reading through the Thread for the Pre Release of FuguMod Ultra in the development section of this forum I thought I would post some info up for people who are wondering why it doesn't work with their phone, and just some general info on overclocking.
- First off, not all phones will be able to run at 1366MHz. Every CPU made has a range of freuqencies it will work at, and it is different for every single one. So some may be able to handle 1366MHz and above, others may max out at 900MHz. If you are getting black screens, freezes, or random behaviour, then your CPU doesn't like the frequency you have it at, try a lower frequency.
- Always keep an eye on the temp of the CPU when testing overclocking, if the CPU gets too hot, and fail safes don't work, there is a chance you could fry your CPU.
- With the FuguMod Ultra kernel, you must also be aware that gpu bus frequencies have been changed, so if your phone is not happy with that it will black screen. (as bus speeds are like cpu speeds, every different device can handle different clock speeds)
- plls values have been changed, and these may cause problems on your phone.
So if you want to have a go at overclocking your phone, back it up, and then give it a go. Select a frequency, and test with something pretty cpu intensive (3d game, multiple quadrant passes) and see if there are any bugs/overheating during a 15min time period. If you notice any problems/too much heat, try a lower frequency, and try again. And if for some reason your phone doesn't like the kernel, you can reflash with your previous kernel or a new ROM as you have already backed up your data.
If you have any other questions about overclocking, feel free to post here and I will try my best to answer them.
--- Samsung G3, InDroid 4.3, FuguMod 2.4 B3 800MHz ---
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
dilzo said:
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
The battery temp is a good representation of how hot the processor is getting as it is right next to the battery (only a thin sheet of metal seperating it) If the battery rises in temperature by a few degrees, then you can summize that the cpu is probably getting a few degrees hotter than that. I really wouldn't recommend letting the battery get above 55degrees (celcius) as this means the CPU may be getting up close to 65degrees (celcius) which is a very bad thing.
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
marcellusbe said:
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
Click to expand...
Click to collapse
Yes, Very true!!
Must also say, Your kernels are pretty legendary! Waiting patiently for the offical release of your FuguMod Ultra
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Piyush Rawal said:
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Click to expand...
Click to collapse
How have you got your phone set up? i.e. what ROM are you using etc.
I am using stock jpq with app2sd, swap, zipalign, ramhack and stuff. Setcpu is installed with default min/max freakquency, No profiles in use and undervolt a bit.
Ok,
This may be an issue caused by XXJPQ, as it is a new release there may be some sort of conflict. Have you tried asking if anyone else has this issue in this thread? http://forum.xda-developers.com/showthread.php?t=1132697
I haven't played around with JPQ yet so don't know what the bugs are yet.
Also, are you running a stock kernel? Have you confirmed that the phone has been rooted properly as well?
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Piyush Rawal said:
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Click to expand...
Click to collapse
Ok cool, I'll report the bug to the developer so that he can have a look into it. Thanks for testing and proving to the kernel.
Little bit of info some might find helpful. After some recent testing, I have found that some people might experience a black screen freeze when phone is in standby for a while with 83MHz min setting and on demand governor. I am not sure of the exact reason for this, whether it is a bug, or that the processor just doesn't like going that low for extended periods of time. If you experience this type of error, just hard reset the phone then open setcpu after phone has loaded and change the "standby" profile minimum to at least the next step up on the slider. Personally I use 223 setting as it provides a smoother lock screen animation, and no significant difference in battery drain.
Sent from my super smooth GT-I5800 using XDA App

hot CPU (75 C)

According to the System Tuner app, my CPU went up to 75 degrees Celsius while I was playing a track on Google Earth. I was running Earth for only a few minutes before it reached 75. I'm not sure if that's the peak yet...maybe it can go even higher.
I've seen several other threads about heat, but most people talk about 50s and 60s. Anyone reach 75C? The front and back of the phone, the top around the camera, were both very hot. It was almost uncomfortable to touch.
Again, I'm talking about 75 Celsius, not Fahrenheit. And I'm referring to CPU temperature according to System Tuner app, not battery temp. Anyone reach this?
picture plz.
the reason is bc someone did a stress test on the N4 and found that the device shuts down at ~57-59C (correct me if im wrong) to prevent damage to the hardware.
Edit: found the link http://www.youtube.com/watch?feature=player_embedded&v=koLJ4BU9tgc
75ºC on a quad core?
I thought it was supposed to be more efficient than a dual core... 167ºF just seems like it's way hotter than any electronic device should ever be.
Sent from my SPH-D710 using xda premium
My first gaming laptop was an ASUS Republic of Game first generation. They did a horrible job cooling the machine. During the 2 months before the machine failed, the GPU would reaches 110 - 140 C if I played games (then, of course, the machine turned the GPU off and still ran as everything else was still about 70-80 C)
When the machine did fail, I opened it up, and found 2 fried thermal unit, a fried GPU and a nearly fried HDD) Amazingly, the machine stills runs, as long as I don't load GPU driver
Well, that's the story. Back to OP, as you see, if the temp is too high, you device can be literally fried. So if you turn off the thermal throttle, please enable it back on and do you best to keep your device cool
I tried to replicate just now and could only go up to 63c. I don't want to keep trying based on the comments here so far. If it happens again I'll be sure to get a screen shot and be aware of what's running.
Where would the thermal throttle toggle exist, if I have the capability at all? I'm running faux123 kernel and use trickster mod and trinity kernel tools for tweaking. I don't see anything about throttle control.
On a similar note, faux123 seems to default to 1ghz minimum cpu frequency. Does that seem right? I've flashed lots of kernels before on previous phones and they always default to the lowest value. When I force the setting down to 384mhz, it automatically changes back to 1024mhz the next time I go in my tool apps. Does this seem normal?
denimjunkie82 said:
Where would the thermal throttle toggle exist, if I have the capability at all? I'm running faux123 kernel and use trickster mod and trinity kernel tools for tweaking. I don't see anything about throttle control.
Click to expand...
Click to collapse
I haven't seen a Nexus 4 kernel that has thermal throttle toggle, or have it disabled yet. I am just checking if you're running one that I am not aware of
denimjunkie82 said:
On a similar note, faux123 seems to default to 1ghz minimum cpu frequency. Does that seem right? I've flashed lots of kernels before on previous phones and they always default to the lowest value. When I force the setting down to 384mhz, it automatically changes back to 1024mhz the next time I go in my tool apps. Does this seem normal?
Click to expand...
Click to collapse
Minimum cpu frequency enforced by kernel is normal. I am not certain if faux123 default to 1 ghz min, but if it's the case, it seems weird for me too. Definitely not good for the battery. If there's no other CPU control apps, I recommend double check the settings, then find an update for faux123, or use trinity kernel
I just flashed a new kernel and my minimum cpu now seems more normal. I hopefully that alleviates the crazy temperatures too.
I'll try to test again tomorrow to see if my temps still go bonkers. It's time to sleep now. Thanks for the help, everyone.

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

Is it safe to change my CPU governor to "performance" to force max clock speed?

Is it safe to change my CPU governor to "performance" to force max clock speed?
I don't want to overclock my Note 4, don't worry, not talking about that. But I am talking about MAX clocking it - forcing it to run at maximum rated speed. I've already tested out SetCPU and used it to change my governor to performance which forces the clock to max, and it nearly doubled my framerate in many games, especially the ones that struggled to play on this device like Xcom:EW.
But I quickly turned it off because I wasn't sure it was safe to do in the new era of smartphones, what with their DVFS and all. I'm worried that I'm going to overheat the CPU, and it's not going to be able to downclock because of temperature anymore. I'm only modifying the governor, but what if I actually used SetCPU to just change the CPU clock to max, without even touching the governor?
Can I hurt my phone by doing this? Can I safely start forcing my CPU to run faster while playing games, knowing that the only thing I risk is my battery draining faster, or am I actually risking damaging components by doing this?
Hello and thank you for using Q/A,
your CPU will not be damaged, but the battery life time will be shorted.
Regards
Trafalgar Square
RC
I personally have used Performance governor on Moto X 2013 for almost the whole 8 months I had it, 24x7 I mean. Never had a problem, yeah maybe battery life was little less than normal but I never did really care about it. Then I ran the same governor for a good period of time on my Note 3 too, same, no problem at all. Like you said, in games the frame rate difference is massive, but I don't play much games, I simply used that governor because it gets rid off all those micro lags and jitters which are Android's trademark, I simply can't them, with default Interactive the micro lags are very apparent.
However with Note 4 I am pretty happy with the BluActive governor, it makes most of the micro lags to go away, so sticking with it.
In any case unless you plan to use a mobile phone for maybe 5 years or so, I don't see any problem at all with it, other than a slightly increased heat, and maybe a little less battery backup, but you will find so many comments which might scare you, that chip burns off if you run it and all that, but those mainly are BS.

Categories

Resources