Related
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.
To the extent that flickering and low charging is related to Sony thermanager, here is the permanent fix for AOSP/CM based roms. While the idea of thermal manager is good and we should credit Sony for doing it, the implementation kind of s*cks. For example, the manager kicks in when CPU/GPU temperature rises to 44 degrees. Also, several triggers are set between 54-56 degrees. This is plain wrong, because 44, 50 and 55-56 are all perfect numbers for an active device and at these temperatures, thermal manager should not be active. I have adjusted trigger numbers so that there will be no mitigation until at least 60 and surprise surprise, all screen flickering is gone away....
Attached is thermanager.xml which should be put in /system/etc/ with 644 permissions. Reboot is required. UNZIP FIRST. Also, backup your current file just in case.
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
sgspluss said:
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
Click to expand...
Click to collapse
Any touch issues related to thermanager kicking in early could be resolved. But lollipop has overheating issues related to art, which can't be solved by thermal management. That's why strictly speaking, lollipop has to be recalled. In my view it can't be fixed.
A little question
Hello optimumpro
I only need put the thermanager in the path system/etc to make it work? or need something else?. Sorry by the queastion I noob an recently I repair de display and touchscreen for my xperia z1 C6902 and a have the flickering problem.
Thanks for your help.
optimumpro said:
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Click to expand...
Click to collapse
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
This works for me!
before flash this file, my Phone only receives 90ma from any changer, and now reciving 1080ma. Thanks a lot!
Room: Ressurection Remix
Android version: 5.1.1, Xperia Z1 C6943
Sent from my Xperia Z1 using XDA Free mobile app
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
Sent from my C6903 using Tapatalk
agha_jo0n said:
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
View attachment 3434889
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I don't think that app is accurate tbh with the fix it says no higher than 300ma for me and my phone is charging pretty well I'm using 2100ma charger as well
Sent from my Xperia Z1 using Tapatalk
Sorry bro but i don't have this file in system /etc??? Wtf???
ninjasoft said:
Sorry bro but i don't have this file in system /etc??? Wtf???
Click to expand...
Click to collapse
You are probably on kitkat. If that's the case, you don't need thermanager. If you are on lollipop, look again, the files are not necessarily in alphabetical order...
And remember, this one is for custom roms: CM and/or AOSP based. I just looked at your signature, you have stock...
zhuoyang said:
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
Click to expand...
Click to collapse
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
optimumpro said:
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
Click to expand...
Click to collapse
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
zhuoyang said:
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
Click to expand...
Click to collapse
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
optimumpro said:
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
Advantages of undervolting Android
Thank God for Android where we can easily modify and customize our lovely Android devices to the way we want. Being said this, undervolting is one of the biggest attraction for Android! Simply by undervolting an Android you will or might experience:
A longer battery life
More responsive smartphone
Less heat produced by the phone
Super-charge your Android to go further than what it can do (overclocking Android)
Click to expand...
Click to collapse
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
Note: UnderVolting is widely used as a cooling solution and in my opinion more effective than any other cooling solution available for free. Results can will show decrease in the temperature of smartphone. I recommend undervolting to anyone with enough confidence and knowledge to do so. The benefits easily outweigh the risks. I dont see why one shouldn’t do this for a cool and better smartphone experience.Undervolting will NOT compromise performance at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1956346
Undervolting is actually a very good thing for your smart phone when you do it correctly. Undervolting has one major positive effect on your CPU: it will extend the life of your processor by allowing it to do demanding things with lower heat generation
Click to expand...
Click to collapse
zhuoyang said:
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
http://forum.xda-developers.com/showthread.php?t=1956346
Click to expand...
Click to collapse
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
optimumpro said:
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
Click to expand...
Click to collapse
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
zhuoyang said:
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
Click to expand...
Click to collapse
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
optimumpro said:
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
Click to expand...
Click to collapse
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
zhuoyang said:
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
Click to expand...
Click to collapse
"I am not attacking you" Yes you were, I said that some bloggers don't know what they are talking about and you replied that I didn't know what I was talking about. Anyway, I accept your veiled apology.
Neither overvoltage nor undervoltage makes the phone cooler. There is an optimal regime for each cpu and if you go outside of it (in either direction), you are inviting trouble. You are not going to destroy your cpu by either under or over voltage, as there is protection in kernel. The phone runs cooler when cpu works less and the optimal regime causes the cpu work less. If you are reducing juice (voltage), you make cpu work longer, which results in overheating.
I gave you an example of performance governor to make a point that this is counterintuitive: while cpu is set at the higher frequencies, it actually performs the tasks and rushes to idle faster, which results in cooler condition. When the same cpu is set lower (and especially if it is under volted), it works longer, jumps to different frequencies, plugs/unplugs cores, which all contributes to overheating....
What is normal values for this phone ? I have diferent chargers, Samnsung - around 600mA, one HTC - around 400mA and another one with 200mA according to that app. Wich one should i use ? So far i used samsung one because it charges fast...2 hours or less, but the battery dies also fast ....so it may be because of the charger ?
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?
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.
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 ?