In the power options, under processor power management, the maximum processor state on battery seems to always revert back to 100% after a reboot or changing power plans. Any ideas why the setting won't stick?
I noticed this as well
..very annoying
is that the only setting you noticed reverting? or are there more?
I assumed win8 handles processes differently requiring less battery consumption.
Sent from my EVO using xda premium
but that isn't the issue
if u go into settings and change the 100% to anything else
it always reverts back .....very annoying ....marked difference in battery life noticed
If you create a new power plan and use it, the settings will stay after a reboot. This is what I did.
Did anyone try 20% CPU so far ? And if so, how is the battery life?
I won't mind getting Surface Pro if I can throttle down its CPU when on battery to Surface RT's speed for a longer battery.
I currently have a RT version with me
Power consumption curve for CPUs is very non-linear. 90% from 100% will probably save you more power than 20% from 90% will. You'd just be wasting a ton of processing capability.
GoodDayToDie said:
Power consumption curve for CPUs is very non-linear. 90% from 100% will probably save you more power than 20% from 90% will. You'd just be wasting a ton of processing capability.
Click to expand...
Click to collapse
Not only that but the windows throttle percentage is not really as specific as a 0-100 range would suggest, so even if you set 20% it might limit the cpu to its minimum frequency.
If you use a tool such as this you can see what the current frequency is: http://www.cpuid.com/softwares/tmonitor.html
With my laptops (much slower) Core2Duo the minimum frequency was too slow, but about 50% of the max worked well and dramatically reduced the heat under load.
Some people reckon it is better to allow the cpu to use its full frequency so that it finishes the job faster and can move back to the lowest idle state. I am not sure that really applies to i5 (which doesn't support the ARM-style idle states that haswell will) and like you say the power consumption at lower cpu frequencies doesn't vary much. My experience with windows is that sometimes for no apparent reason at all programs such as word or chrome sit using 50+% of the cpu and you have to restart the process. It doesn't happen often at all but you might not realise until your battery is low. With the pro's i5 I expect you could get away with quite a low cpu frequency and would at least know you will always get roughly the same battery life.
This is the same problem that w700 has, an even earlier product. This situation made the biggest thread in the acer community because people are angry, some even took back their products and traded for the surface which made it the same than people realized it was not the w700 itself. Throttle stop didnt work because it seems to be more temp related.
Here are some interesting topics
http://community.acer.com/t5/Acer-T...rottling-Turbo-Boost-issues/td-p/6873/page/28
http://forum.tabletpcreview.com/acer-gateway/54122-w700-throttling.html
Walderstorn said:
This is the same problem that w700 has, an even earlier product. This situation made the biggest thread in the acer community because people are angry, some even took back their products and traded for the surface which made it the same than people realized it was not the w700 itself. Throttle stop didnt work because it seems to be more temp related.
Here are some interesting topics
http://community.acer.com/t5/Acer-T...rottling-Turbo-Boost-issues/td-p/6873/page/28
http://forum.tabletpcreview.com/acer-gateway/54122-w700-throttling.html
Click to expand...
Click to collapse
Actually, it is nothing like that problem. The OP is talking about manually limiting the max clock of the device using the Windows setting that has been there for a while now.
Related
I think I may have a simple yet very inefficient method of ensuring stable overclock at higher frequencies. I have been messing around with many different OC kernels (along with many different roms ), and have noticed the same situation. While charging, all overclock speeds beyond 633 are pretty stable. It may take a few attempts to reach a certain speed (as the phone might reboot), but once successful its all golden!
I'd previously though instabilities were due to the fact that these kernels were undervolted and thus, after a certain frequency, needed more juice to function properly, but when I removed the charger. My god...it still ran! Just as effectively for extended periods of time.
The only problem was the phone would either reboot or hang if the screen was powered-off and idle/sleep for more than 1-3 secs. So I tried using SetCpu's profiles to lower the clock speed to various speeds below 633 during sleep. Yet to no avail. The phone would always freeze/reboot when it attempted to clock back up.
So if someone were to develop an app that would implement a toggle feature, or make modifications to the current kernels to disable sleep for test purposes I believe that might help. I am far too inexperienced a programmer to dev this but know there was a command under reference called "Partial Wake Lock" that can disable cpu sleep.
Also I realize, if implemented as is, this will destroy battery life. But with a good toggle switch it can be treated as an Overdrive mode!!!
Forgot to mention that while charging and clocked beyond 633 it always awoke with no problems.
My phone will clock to 710 before freezing up but it's crazy unstable. It seems to behave well at 652 with a freeze up roughly every 6-7 hours. I've never tried it that high with the charger though. Seems interesting.
extended batteries also reduce overclocking, my 2600mah battery peaks at 595, where as the official battery gets me to 633
-------------------------------------
Sent from my HTC Magic
I have exactly the same issue. My G1 runs stable on 672, while plugged in into
the charger. Even using GPS for navigation, browsing and so on, everything works great. As soon as the charger is plugged out and the phone goes into sleep it reboots.
I end up in changing the frequencies on demand with setCPU. When i need more speed, e.g. browsing the web, i set it manually to 672. And before putting it in my pocket i reduce to 614. Even on battery i can use 672.
Also tried profiles in SetCPU but this did not help.
BTW. Using 5.0.8t4, same was on t3
Damian
Nagoki said:
I think I may have a simple yet very inefficient method of ensuring stable overclock at higher frequencies. I have been messing around with many different OC kernels (along with many different roms ), and have noticed the same situation. While charging, all overclock speeds beyond 633 are pretty stable. It may take a few attempts to reach a certain speed (as the phone might reboot), but once successful its all golden!
I'd previously though instabilities were due to the fact that these kernels were undervolted and thus, after a certain frequency, needed more juice to function properly, but when I removed the charger. My god...it still ran! Just as effectively for extended periods of time.
The only problem was the phone would either reboot or hang if the screen was powered-off and idle/sleep for more than 1-3 secs. So I tried using SetCpu's profiles to lower the clock speed to various speeds below 633 during sleep. Yet to no avail. The phone would always freeze/reboot when it attempted to clock back up.
So if someone were to develop an app that would implement a toggle feature, or make modifications to the current kernels to disable sleep for test purposes I believe that might help. I am far too inexperienced a programmer to dev this but know there was a command under reference called "Partial Wake Lock" that can disable cpu sleep.
Also I realize, if implemented as is, this will destroy battery life. But with a good toggle switch it can be treated as an Overdrive mode!!!
Click to expand...
Click to collapse
The speeds will be different on different phones due to the hardware even slightly different depending on where the phone was made mine can go to 720mhz while others 614mhz which means unless another way of overclocking is found then we won't have a stable overclock for a while :/
mejorguille said:
My phone will clock to 710 before freezing up but it's crazy unstable. It seems to behave well at 652 with a freeze up roughly every 6-7 hours. I've never tried it that high with the charger though. Seems interesting.
Click to expand...
Click to collapse
Lemme know how that goes. I've noticed higher clock frequencies are much more stable while charging.
Jedipottsy said:
extended batteries also reduce overclocking, my 2600mah battery peaks at 595, where as the official battery gets me to 633
-------------------------------------
Sent from my HTC Magic
Click to expand...
Click to collapse
That's strange. Maybe its a voltage difference between batteries that makes its more unstable.
vassloff said:
I have exactly the same issue. My G1 runs stable on 672, while plugged in into
the charger. Even using GPS for navigation, browsing and so on, everything works great. As soon as the charger is plugged out and the phone goes into sleep it reboots.
I end up in changing the frequencies on demand with setCPU. When i need more speed, e.g. browsing the web, i set it manually to 672. And before putting it in my pocket i reduce to 614. Even on battery i can use 672.
Also tried profiles in SetCPU but this did not help.
BTW. Using 5.0.8t4, same was on t3
Damian
Click to expand...
Click to collapse
I believe when the phone is charging the operating system either suspends or extends idle/sleep when the screen backlight is off. This would explain why it reboots on battery and not while plugged in. Also the SetCpu profiles would work if only overclocking wasn't so unstable.
xillius200 said:
The speeds will be different on different phones due to the hardware even slightly different depending on where the phone was made mine can go to 720mhz while others 614mhz which means unless another way of overclocking is found then we won't have a stable overclock for a while :/
Click to expand...
Click to collapse
That is true, but if we can help the relative stability of each clock rate past 528 by using simple methods (i.e. overclocking while charging), we can simply aim to improve its reliability until a better way to overclock is found.
I remember there was an app like this for the HTC Touch, when the phone is idle the app will reduce the cpu speed thus save the battery - I noticed a huge increase in battery life with the touch back then and thought it was an essential app. Is there anything like this for the HD2? I think we all can save some battery life for our HD2's
freakflow said:
I remember there was an app like this for the HTC Touch, when the phone is idle the app will reduce the cpu speed thus save the battery - I noticed a huge increase in battery life with the touch back then and thought it was an essential app. Is there anything like this for the HD2? I think we all can save some battery life for our HD2's
Click to expand...
Click to collapse
Without an app to increase cpu speed and disable dynamic speed it already does this ...
LeoCpuSpeed3 will allow you to change the settings ...
first of all, the hd2 does run at 998Ghz at optimized speeds at heavy load, otherwise at idle its 700Ghz, unused. it already has this feature built in. increasing speeds arent safe especially where theres no coolant system or heatsink on these arm cpu. peeps can do whatever with their $500 dollar investment
aoakes said:
first of all, the hd2 does run at 998Ghz at optimized speeds at heavy load, otherwise at idle its 700Ghz, unused. it already has this feature built in. increasing speeds arent safe especially where theres no coolant system or heatsink on these arm cpu. peeps can do whatever with their $500 dollar investment
Click to expand...
Click to collapse
True I would not recommend overclocking the phone, but many many people, including myself, use it locked at 998 with no problems, it gets warmer using wifi than it does at 998 ...
Also really I do not get much more battery life out of it set to dynamic ...
any app can reduce cpu below 700Mhz?
thanks.
Guys, NetRipper created an app that provides all of this. It covers all your LEO CPU manipulation needs - underclocking/overclocking even static & dynamic speed setting. Conveniently, its called Leo CPU Speed! You really have NO EXCUSE for not finding it - just type the damn words in a search box "leo cpu speed".
Please, don't act like morons!
Devs invest their precious time to create apps for you, give them intuitive names, write up tutorials, answer your questions .... it is not their job to run a search query for you - use the SEARCH box BEFORE you start hogging attention UNNECESSARILY; it'll take you less time finding it than posting up new questions!
It would be good if there was an app that reduces cpu speed to under 700mhz when the phone is locked and as soon as the phone is unlocked it takes it right back up to the full 998mhz.
Would save more battery than using autoscaling cause it would reduce it to less and you'd get full speed when the phone is unlocked since it would be at 998mhz. Something like that would be quite good providing it actually would save any battery
aLlamaWithARifle said:
It would be good if there was an app that reduces cpu speed to under 700mhz when the phone is locked and as soon as the phone is unlocked it takes it right back up to the full 998mhz.
Would save more battery than using autoscaling cause it would reduce it to less and you'd get full speed when the phone is unlocked since it would be at 998mhz. Something like that would be quite good providing it actually would save any battery
Click to expand...
Click to collapse
i totally agree...
aLlamaWithARifle said:
It would be good if there was an app that reduces cpu speed to under 700mhz when the phone is locked and as soon as the phone is unlocked it takes it right back up to the full 998mhz.
Would save more battery than using autoscaling cause it would reduce it to less and you'd get full speed when the phone is unlocked since it would be at 998mhz. Something like that would be quite good providing it actually would save any battery
Click to expand...
Click to collapse
on my Leo - when locked - the battery current is around 4mA,
if its typical, then not much is to be gained by underclocking this particular state
p107r0 said:
on my Leo - when locked - the battery current is around 4mA,
if its typical, then not much is to be gained by underclocking this particular state
Click to expand...
Click to collapse
yeah, mine is at 4mA as well..
isn't it like when in standby/locked the hd2 automatically underclocks to somewhat around 200mhz??
so, no need for an additional app.
hebbe said:
isn't it like when in standby/locked the hd2 automatically underclocks to somewhat around 200mhz??
so, no need for an additional app.
Click to expand...
Click to collapse
You're actually right! Moreover, the instant you interact with the phone again the CPU will popup to 700+, and then if you push it a little, it'll go all the way to 998. All of this is OEM behaviour! So, these guys REALLY need to move on
Doesn't matter which ROM, which kernel (except stick, didn't stay on there long enough to notice), when everything are off or idling, CPU would still constantly kick up to 601mhz (unless i under clock of course), never really sleep/idle at 214 or whatever
Y?
Seems like this CPU can never sleep, or even idle, thus killing the battery
this phone (and alot of newer ones) are using an idea called Race to idle.
this means that the cpu will kick its cpu speed up higher than it needs to get things done faster, so it can get back to a low power idle state faster.
In reality your cpu is really going in and out of sleep states hundreds or thousands of times a second, the frequency is just kicked up so that it can spend less time computing, and more time sleeping.
for the hell of it try downloading an app that shows you cpu usage in %
that number is the amount of time that the cpu is in a fully awake state vs being in its first stage sleep state, LP1.
if nothing happens for a bit longer than it will go into an even lower power state called LP2. frequency can still be set to a higher number (like 600mhz or even 1ghz) but the cpu is actually not doing any calculations. its sleeping till something needs it.
also, changing cpu speed takes a long time (cpu wise), the cpu has to pause, change speed, then wake up. so the less it does this the less lag you have.
^The guy above is right, you can put it to 1.5 gHz and it wouldn't die sooner, what makes the difference is how much you use the phone. If you listen to music and text, you don't need it to go farther than 800 mHz, but the extra boost with make it faster but also use more energy.
What background apps are open?
Klathmon said:
this phone (and alot of newer ones) are using an idea called Race to idle.
this means that the cpu will kick its cpu speed up higher than it needs to get things done faster, so it can get back to a low power idle state faster.
In reality your cpu is really going in and out of sleep states hundreds or thousands of times a second, the frequency is just kicked up so that it can spend less time computing, and more time sleeping.
for the hell of it try downloading an app that shows you cpu usage in %
that number is the amount of time that the cpu is in a fully awake state vs being in its first stage sleep state, LP1.
if nothing happens for a bit longer than it will go into an even lower power state called LP2. frequency can still be set to a higher number (like 600mhz or even 1ghz) but the cpu is actually not doing any calculations. its sleeping till something needs it.
also, changing cpu speed takes a long time (cpu wise), the cpu has to pause, change speed, then wake up. so the less it does this the less lag you have.
Click to expand...
Click to collapse
Thanks, and i know about the race to idle. 1. My previous phone was a galaxy s 4g. when in idle, it stays at 100mhz, lowest speed and stay there til the screen goes out. Great idle battery life. Cpu info and the likes shows large percent of time in sleep state based on reading the time in state file
2. I haven't found a single kernel that support the time in state file (various cm, faux, morfic, harsh, can't remember the rest, sorry devs - gb n ics). Without this file, we cannot determine time in sleep
Bonus, i use to have a viewsonic tab with same harmony tegra 2 board as the g2x and it can't get 3 days of standby compared to other tablets that can do over a week. Also due to sleep issue. And that don't even have cell data. Wifi off too
atb1183 said:
Thanks, and i know about the race to idle. 1. My previous phone was a galaxy s 4g. when in idle, it stays at 100mhz, lowest speed and stay there til the screen goes out. Great idle battery life. Cpu info and the likes shows large percent of time in sleep state based on reading the time in state file
2. I haven't found a single kernel that support the time in state file (various cm, faux, morfic, harsh, can't remember the rest, sorry devs - gb n ics). Without this file, we cannot determine time in sleep
Bonus, i use to have a viewsonic tab with same harmony tegra 2 board as the g2x and it can't get 3 days of standby compared to other tablets that can do over a week. Also due to sleep issue. And that don't even have cell data. Wifi off too
Click to expand...
Click to collapse
that's due to the 'unique' governor built into tegra. it likes to kick the speed up at the slightest need for power, and keep it there just in case you want to do something. its sure as hell an eager little bugger
on the galaxy s 4g you can change the governor to change its behavior, your probably using a fancy Linux governor that is tweaked to be damn near perfect, Nvidia tried to design its governor from scratch... the success they had is debatable, but its different from what your used to.
Nvidia seemed to prefer performance over battery life, and its definitely not the most standby friendly, but the good news is that custom kernels and roms allow you to change that
Thanks. That's a satisfactory and most likely to be true. Used on demand gov on the gs4g w plenty of tweaks. Hopefully we can do similar tweaks in here on the new kernels
Yeah for a light user like myself, I only use the phone for text/fb/twitter/email and music, so I usually keep my clock at 800mhz, and well.....when i need to play games i just clock it to 1.2kmhz, thats usually enough for me, havnt lag in any 3d games i played yet so far.
and sell, if you open the setcpu and watch it for like 20 seconds, you should notice it never going above 601 on idle, mine kinda bounce between 389 and 601 with 389 most of the time. Which kernel/rom you using anyways? Just wondering.
Hi all,
I've had my Surface Pro 2 256/8 since release and all has been fine until (possibly) the firmware update.
Turbo Boost was working fine and the CPU was going up to its maximum of 2.6Ghz but it is now seemingly capped at 2.23Ghz.
I've checked in PC Settings, Task Manager and CPU-Z, the maximum that the CPU ever reaches is 2.23Ghz, as indicated.
Anyone else experienced this? I have tried all power profiles (Performance, balanced, Power Saver and there's no difference).
Thanks!
EDIT: Having used HWiNFO64 on the High Performance profile I can see that the core is limited to x23 which is producing the 2.3Ghz clock speed. It occasionally indicates x26 (2.6Ghz) for a millisecond before ThermMon shows that it is being throttled back to x23. So it appears it's not reaching maximum speed to keep the heat lower, why this has happened is still inconclusive..
Have you tried to change the CPU maximum utilization in power settings?
Sent from CM10.1 U9200
>I've had my Surface Pro 2 256/8 since release and all has been fine until (possibly) the firmware update.
You've answered your own question. One reason to cap speed is for battery life. That's what the latest firmware update provides. You've found the downside.
http://www.theverge.com/2013/11/4/5064026/microsoft-surface-pro-2-battery-life-firmware-update
So they cap turbo mode to increase battery life, given the SP2 is advertised as having an Intel i5 CPU with no mention of speed on the MS site I think they'll get away with it...
e.mote said:
>I've had my Surface Pro 2 256/8 since release and all has been fine until (possibly) the firmware update.
You've answered your own question. One reason to cap speed is for battery life. That's what the latest firmware update provides. You've found the downside.
http://www.theverge.com/2013/11/4/5064026/microsoft-surface-pro-2-battery-life-firmware-update
Click to expand...
Click to collapse
Well, in that case, the CPU shouldn't be capped when NOT running on battery power, should it?
There is also cooling to consider regardless of if it is on battery or mains. Although was heat particularly problematic pre-update?
>Well, in that case, the CPU shouldn't be capped when NOT running on battery power, should it?
As another noted, SP2 slicks never said CPU would be running at max spec.
PCs are normally more configurable. But if you enter SP2's UEFI setup, the only thing you can change is Secure Boot. MS is emulating Apple in more ways than one.
The cynics among us (guilty as charged) would say that MS handled this just right: Release the device with uncapped speed to get the best possible performance for reviews. Then afterward, cap the speed to claim "improved battery life" as well. If MS had capped the speed to start with, SP2 would be no faster than SP, and would get slammed hard. SP2 is already slammed as having minimal improvements over SP.
Reviewers aren't going to take the trouble to revise their reviews, and even if they did, not many people will re-read them. So, with this method, you can indeed have your cake and eat it too. Think of it as a more "legal" form of juicing performance tests without the explicit cheating that Samsung and others resorted to.
e.mote said:
> SP2 is already slammed as having minimal improvements over SP.
Click to expand...
Click to collapse
Anyone thats knows the difference between the CPU's will know that theres not a huge speed increase though, the only thing they should of done was stick a decent SSD in there, I've got an unused PX-256M5M sat on my desk that reads/writes at near on full sized 2.5" SSD speeds where as the mSSD's have always had half decent read and poor write.
Other than that what else is there to improve on, the camera perhaps as per the Surface2, battery life, check, the only other thing the Pro/Pro2 needs imho is more accesories, yes they are coming but should of been ready at launch imho, I'm crying out for a dock...
I know i made some negative posts on the htc u11 but tbh i love this phone and i was just feeling annoyed by some things.. But i wanted to ask, i expected this phone to be lag free and super fast, yes it is super fast abd smooth but the thing is that it does lag with me and it is noticable. Happens a couple of times a day i think, am i the only one having lag problems? I do have the power saving option on and idk if it's what's causing the phone to lag or not but all i know is it does lag with me and it is unexpected since this phone has htc sense and snapdragon 835. Share your thoughts below
Not just lag but freeze
I'll share my thoughts : you should really stop openning these threads because actually no one believes you, we're all aware that you're here to throw up on this phone.
For who ? We don't know.
Maybe a simple Samsung fanboy who's upset because HTC made a better phone than Samsung's flagships two years in a row ?
Now stop please, it's not funny and it will not prevent people to buy the U11 if they want to.
I don't see Samsung logo on front... Soo no lag here.
Dejan Kruljac said:
I don't see Samsung logo on front... Soo no lag here.
Click to expand...
Click to collapse
Turn off the power saver. It's not needed with the Snapdragon 835 and it alters the distribution of the load between the clusters. Things that would complete swiftly and thus conserve power on the big cores gets offloaded to the little cores. The kernel isn't optimized to take advantage of the efficiency of the 835. With it being incredibly easy to get 7 hours of SoT, there is no need for the power saver. Somewhere on XDA there's a very detailed explanation as to what the power saver does and why it shouldn't be used unless your phone is about to die but it curbs both clock speeds and shuffles around the load, preferring to not use the big cores at all. It basically abolishes the efficiency of the big.LITTLE premise and often has opposite the intended effect if you're actively using the phone.
If you need optimization, you can use Boost+ to set individual high drain apps up to be run in 1080p, limit background usage, etc. This is much more effective than essentially killing the performance of the phone and gaining little, if any, additional battery life. It can have the opposite effect and in fact did so on the 10.
Think of it like this - the little cluster may take half the power per cycle than the big cluster (I don't know the exact numbers and highly doubt it's anywhere near half but it works for the example). You open an app that would have completed in a single cycle on the big cluster. That same app can take four to five cycles on the little cluster. You've just thrown efficiency out the window.
If you have a lot of background apps misbehaving and a lot of apps constantly syncing, it can be advantageous but I haven't seen any evidence of that since the Snapdragon 820. The 805 in my Nexus 6 benefited from it but my Note 5 with the Exynos 7420 and my 10 with the Snapdragon 820 suffered.
Lag?? OP must be in the wrong forum. Please go back to your Lagsung S8..
I had freezes on my previous HTC(one m7), and the reason was some crappy game I installed. After removal - no lag at all. Just try and revise your applications and remove ones you have doubts
0 lag. None, Nada, zilch. Either the person who started this post has an app or setting that is causing it or they are intentionally trying to keep people from buying it...Which seems crazy...who would care that much...?