I understand you can overclock your device, I have personally done it upto 597MHZ, but you know how on a regular PC it shortens the life of a CPU Processor like, 10% or something, will it do the same to your phone? Because if my phone dies in a year I'm going to be very angry!
Hi
Rarely...
When you ask about it, you'll receive several diffrent blah-blahs.
The truth is that overcloking causes the processor to run hotter.
You "can" damage CPU by overcloking it drastically, but rarely.
The first syndrome of too high overclock, is that CPU start to do errors (hangups, etc). If the overclockes CPU is working fine, that you shouldn't worry about anything.
As for lifespan... who can measure this 10% of reduced life, when such processor can last for ages. Well, maybe not ages, but long enough to bring your device to a technology museum's exhibition.
Ow.. overclocking causes more battery drain... well... such is life
imablackhat said:
I understand you can overclock your device, I have personally done it upto 597MHZ, but you know how on a regular PC it shortens the life of a CPU Processor like, 10% or something, will it do the same to your phone? Because if my phone dies in a year I'm going to be very angry!
Click to expand...
Click to collapse
the only thing that will happen if you overclock your device, is battery drainage, and sometimes your device will crash.
imablackhat said:
on a regular PC it shortens the life of a CPU Processor like,
Click to expand...
Click to collapse
i just did that on mine, it made my pc loads faster, i wasnt greedy tho, i just notched it up a little. :wink:
Related
[Q] Paradox with underclock & battery savings, does it actually hurt? SetCPU, etc.
In theory, using SetCPU or other underclocking app to reduce CPU clock should reduce the power draw from the CPU, therefore reducing battery consumption.
However, underclocking does not reduce the amount of work that needs to be done. That is to say, whatever app or kernel processing that needs to be done will still be done. When UC'ed, they will be done at a slower pace, therefore taking longer time. In some cases, the UI becomes sluggish, requiring more user interaction time as well.
If, at 1Ghz, a process takes 10 seconds to complete and requires 10mA per second. This task should consume 100mA. By underclocking to 500mHz, perhaps the CPU takes only 6mA, but the task will require 20 seconds to complete. Now the task actually takes 120mA (plus the longer screen on time).
Is my theory sound?
Also, does the constant scaling itself consume power?
As far as I know, Froyo is supposed to scale the CPU anyway. So why underclock? Does it actually work or does it hurt the battery life?
Input please!
Thanks.
Edit: I know the function of CPU speed vs. efficiency vs. battery drain is never linear, and each situation has a different break-even point, but I'm curious the general application of underclocking within the Android environement and its effect on battery life, and more specifically, the Evo.
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNFlNlZCm-gnvD1PzEsDezCIPeA8jQ
Sent from my PC36100 using Tapatalk
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
snovvman said:
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
Click to expand...
Click to collapse
both pics depicts very different device usages. not a fair comparison imo.
quocamole said:
both pics depicts very different device usages. not a fair comparison imo.
Click to expand...
Click to collapse
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
snovvman said:
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
Click to expand...
Click to collapse
Do you think i am right on any part of which i said or am i talking out of my arse lol
A microprocessor does not live by its clock alone. lol
It can cycle through a huge math operation, which is loaded into its registers lickity split with a fast clock. It will have to wait while the memory/code of the programs it runs are loaded either into its cache memory or into execution space. So in calculating theoretical energy use, you got to figure the bus speed, as well as the type of operations the processor is doing.
Golly, ( pronounced like a resident of Mayberry) the bus is key on loading programs to be run. What's the bus clock triggered off? That's the key. You don't want the bus to slow while slowing the cpu. If you can cycle the processor while it prefetches then you've got optimal use, providing it isn't thrashing.
Google cpu wait states for bus synchronization
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
In practice, I haven't seen all that much of a difference.
iitreatedii said:
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
Click to expand...
Click to collapse
iitreatedii said:
Do you think i am right on any part of which i said or am i talking out of my arse lol
Click to expand...
Click to collapse
What you wrote makes sense and the concept is sound. I just wish we knew what that sweet spot is, although I think it changes constantly based on load, code, and operational requirements.
With the two posts above, it would seem like phone manufactures would do everything they can to optimize efficiency. Having SetCPU loaded for 24 hours, I too, can say that I have not seen a huge difference...
Noxious Ninja said:
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
Click to expand...
Click to collapse
Does the stock HTC kernel, 2.6.32 "#11" have/use HAVS?
Greetings gents,hows it going?
I got a question,i managed to overclock my phone to stable [email protected]
But now im trying to push it to [email protected],and its working properly atm,30mins of Stability test and running good.
My only concern is...im watching the temperature and its at 43ºC atm..which isnt exactly "cold" .
My question is,which are the max secure temperatures this beast can go before getting in the risk of frying the CPU?
Thanks in advance ^
PS : I tried searching around but all i found is VSel's...im interested in temps rather than VSel's.
Respect
Is that your battery temp or the CPU temp?
If it's battery temp, I'd be starting to be concerned there. CPU's can handle way higher temps though, 80+C before I'd get worried at all.
But try it out in the sun, too.
dasbin said:
Is that your battery temp or the CPU temp?
If it's battery temp, I'd be starting to be concerned there. CPU's can handle way higher temps though, 80+C before I'd get worried at all.
But try it out in the sun, too.
Click to expand...
Click to collapse
Hmm tbh im not sure which temp it is,StabilityTest says "Temperature"p,now i got no idea tbh which of them it is XD
Time to try again
EDIT : Yep,those 43 - 44ºC are Battery Temps,so should i worry?o.o
80ºC, that's for laptops and desktops, even i start getting warnings in syslog at 85ºC in my core i5 laptop with fan running max speed, and we are talking about a phone processor encased with other chips in a very little space and with no heat dissipation at all... you could not hold it up at 80º though burning and melting on your hands.
There's a lot of info about batteries here http://en.wikipedia.org/wiki/Lithium_ion_battery
I dont think defy is able to drain enough energy to increase battery temperature to dangerous levels, but with temperatures above 40º chemistry inside battery is going to suffer,the higher the temps the less cycles of charge you are gonna get and you are risking a permanent loss of capacity.
The best way for a long life battery is small charges from 25% to 80%
Multiple charges between 80%-100% is the worst thing one can do.
anyway reaching 43º for battery during stress test is not for concern
Battery Monitor Widget is a very good program to keep an eye, and see graphs and stats of battery temps consumption projections and estimations of of juice left.. its simply amazing runs 24/7 and if you dont open it to play with it, it only takes about 10 seconds of total cpu power per day. i would recommend it. So it wont eat your battery when monitoring it, and the same goes for "process monitor" which is perfect to know total cpu power eaten by all apps trhough the day.
unrafa said:
80ºC, that's for laptops and desktops, even i start getting warnings in syslog at 85ºC in my core i5 laptop with fan running max speed, and we are talking about a phone processor encased with other chips in a very little space and with no heat dissipation at all... you could not hold it up at 80º though burning and melting on your hands.
There's a lot of info about batteries here http://en.wikipedia.org/wiki/Lithium_ion_battery
I dont think defy is able to drain enough energy to increase battery temperature to dangerous levels, but with temperatures above 40º chemistry inside battery is going to suffer,the higher the temps the less cycles of charge you are gonna get and you are risking a permanent loss of capacity.
The best way for a long life battery is small charges from 25% to 80%
Multiple charges between 80%-100% is the worst thing one can do.
anyway reaching 43º for battery during stress test is not for concern
Battery Monitor Widget is a very good program to keep an eye, and see graphs and stats of battery temps consumption projections and estimations of of juice left.. its simply amazing runs 24/7 and if you dont open it to play with it, it only takes about 10 seconds of total cpu power per day. i would recommend it. So it wont eat your battery when monitoring it, and the same goes for "process monitor" which is perfect to know total cpu power eaten by all apps trhough the day.
Click to expand...
Click to collapse
Oh Right,
Yeh its true that the best would be from totally discharged to totally charged for its life.
And good to know 43ºC isnt panic-able yet cause the phone runs very well on 1.3GHz/65 and a score of 2700 of Quadrant (Impressive aint it).
Anyways,thanks for all the info =)
Respect
Running 1400MHz/87vsel i have reached 48C in a few minutes. Oc over 1200MHz is not good for battery.
i have setcpu and the lost rogue v1.3 and i what to put it at 1704 MHz but it freezes or reboots, so what could i do? what voltage?
You can try upping the voltage, not every phone will run at the highest speeds. Overclocking is luck of the draw, not every processor will react the same. My phone requires 1550mv @1.6 to be stable and 1.7 is not stable. There is no real advantage to running the processor this high anyways. 1.2-1.4 is the sweetspot, 1.2 does everything the phone needs to and you usually have room to underclock, to increase battery life and usability of the phone. Benchmarks can be fun but imo, stable phone @ lower voltage > semi-stable benchmark monster @ high voltage.
Econ212 said:
You can try upping the voltage, not every phone will run at the highest speeds. Overclocking is luck of the draw, not every processor will react the same. My phone requires 1550mv @1.6 to be stable and 1.7 is not stable. There is no real advantage to running the processor this high anyways. 1.2-1.4 is the sweetspot, 1.2 does everything the phone needs to and you usually have room to underclock, to increase battery life and usability of the phone. Benchmarks can be fun but imo, stable phone @ lower voltage > semi-stable benchmark monster @ high voltage.
Click to expand...
Click to collapse
Agreed, I have tried all sorts of overclocking and always go back to 1.352 or 1.2 because of stability. Sure you can bump it up and get high benchmarks, but who cares it is just a number. I would much rather have lower numbers and a stable phone.
I am running New Senzation ROM with the Desparado Kernel and I am running smooth and blazing fast at 1600. I actually can run at 1704 but dont like to overclock to that speed for very long but havent had any crashes.
bbb1977 said:
I am running New Senzation ROM with the Desparado Kernel and I am running smooth and blazing fast at 1600. I actually can run at 1704 but dont like to overclock to that speed for very long but havent had any crashes.
Click to expand...
Click to collapse
Wanna trade phones? I wonder if you could push it higher? I can get mine to run at 1.7, but it will eventually crash within a few minutes. 1.4 seemed to be the most stable (and got the best quadrants) , but I don't bother OC'ing anymore. The phone runs fine without it. I don't really ee the point. I do notice some lag hear and there at 1.6.
I almost always am in the 800mhz range and rarely does my phone jump to 1ghz and definately almost never hits 1.2ghz. Besides trying to get your phone to give you some meaningless number as far as the real world is concerned ( quads) there is zero reason to ever overclock THIS phone. This phone has better battery life than iPhone with a slightly higher clock which is awesome. It actually performs the best of any phone to date. People conatantly hate on apple so hard to the point that when apple actually does something thats honestly great people still see the cup half empty with them. Apple has some of the best battery life of any smart phone to date. It also is one of the smoothest UI's out. They are a smart company and have great hardware. The example i like and cheer them on for is there way of using there cpu in a certain way. They have a really beefy cpu and then they underclock it quite a bit so it just sips battery power. Yes apple doesnt actually multi task so its easier for them to achieve battery life this way easier and it requires more cpu to run our phones as they have REAL multi tasking but i use the same idea. I underclock my phone to run at 800mhz till i reach 80% cpu load then bump to 1ghz. I never have my phone shutter or lag. The GPU is a monster. I get sooo much more battery life out of it. Overclocking is nearly pointless as a daily driver on this phone. In the past with my HTC Eris and HTC Evo 4g i had to overclock as muCh as possibly due to lack of a powerfull CPU and GPU but this phone (just like iPhone) has more than enough muscle and should be under clock 200mhz with no ill effect at all. Thia phone truely is the first legit android device in my eyes because it has more than enough under the hood. Underclock 200mhz and undervolt -75 and this phone truely shines and comes out #1 phone today in ALL areas. Smoothest scroling, lagless and best battery life to date. I love this phone and my set up
bluefire808 said:
I almost always am in the 800mhz range and rarely does my phone jump to 1ghz and definately almost never hits 1.2ghz. Besides trying to get your phone to give you some meaningless number as far as the real world is concerned ( quads) there is zero reason to ever overclock THIS phone. This phone has better battery life than iPhone with a slightly higher clock which is awesome. It actually performs the best of any phone to date. People conatantly hate on apple so hard to the point that when apple actually does something thats honestly great people still see the cup half empty with them. Apple has some of the best battery life of any smart phone to date. It also is one of the smoothest UI's out. They are a smart company and have great hardware. The example i like and cheer them on for is there way of using there cpu in a certain way. They have a really beefy cpu and then they underclock it quite a bit so it just sips battery power. Yes apple doesnt actually multi task so its easier for them to achieve battery life this way easier and it requires more cpu to run our phones as they have REAL multi tasking but i use the same idea. I underclock my phone to run at 800mhz till i reach 80% cpu load then bump to 1ghz. I never have my phone shutter or lag. The GPU is a monster. I get sooo much more battery life out of it. Overclocking is nearly pointless as a daily driver on this phone. In the past with my HTC Eris and HTC Evo 4g i had to overclock as muCh as possibly due to lack of a powerfull CPU and GPU but this phone (just like iPhone) has more than enough muscle and should be under clock 200mhz with no ill effect at all. Thia phone truely is the first legit android device in my eyes because it has more than enough under the hood. Underclock 200mhz and undervolt -75 and this phone truely shines and comes out #1 phone today in ALL areas. Smoothest scroling, lagless and best battery life to date. I love this phone and my set up
Click to expand...
Click to collapse
Ahhh big wall of text hates!
im now using a custom rom with the overclock kernel... i set my phone to "1.4ghz" with AnTuTu... its working great now... no more fps lags on the games i play... and no crashes... im just curious about one thing? will it break the phone in any way? its not heating up or anything atm... i mean i have experienced phone heat on my sensation xe... that phone gets really hot STOCK....
i dont want to break my play... i really like it compared to other phones in the market right now(the only one with gamepads)... its my first time ocing a phone btw...
If its not noticably hot (the battery too) constantly then your fine, just bare in mind try not to push it past 1.6ghz i found my phone didnt last very long at that speed.
The only thing with oc its that it shortens the life of your cpu obviously depending on how much you oc it....and it drains more battery but its not that big of a deal
Defy39 said:
If its not noticably hot (the battery too) constantly then your fine, just bare in mind try not to push it past 1.6ghz i found my phone didnt last very long at that speed.
Click to expand...
Click to collapse
what do you mean by it didnt last very long? did it break the phone?
Basically, my phone is overclocked to 2.0 GHz with smartass scaling with max 800MHz interactive scaling when screen turned off. It works great! Lasts 2~3 days without gaming (5 to 7 days with airplane mode on) and 4~8 hours of hardcore gaming with full charge (6~12 with airplane mode on). I recommend using an extended battery (I haven't, yet) if you are doing so. And it also involves luck. Even if it is the same model, color, etc. some CPUs are more capable than others.
still testing my phone under 1.4ghz seems stable...
DanielEGVi said:
Basically, my phone is overclocked to 2.0 GHz with smartass scaling with max 800MHz interactive scaling when screen turned off. It works great! Lasts 2~3 days without gaming (5 to 7 days with airplane mode on) and 4~8 hours of hardcore gaming with full charge (6~12 with airplane mode on). I recommend using an extended battery (I haven't, yet) if you are doing so. And it also involves luck. Even if it is the same model, color, etc. some CPUs are more capable than others.
Click to expand...
Click to collapse
is it normal for the phone to be abit hotter than when it was running stock???
btw how does smartass compare to ondemand?? smartass tends to get lower benchmark scores than on demand
seagheart89 said:
is it normal for the phone to be abit hotter than when it was running stock???
btw how does smartass compare to ondemand?? smartass tends to get lower benchmark scores than on demand
Click to expand...
Click to collapse
Yes ofc its normal - as each CPU/GPU creates heat based on the load it takes....
So the higher u OC the hotter it gets - thats why in former days OC was quite dangerous
In todays times cpu normaly 1st get unstable, and then has a safety function to shutdown if it gets too hot. (no warrenty that its the same for all chips)
smartass doesnt switch frequencies at once like on demand (e.g. instant from 200mhz to 1000mhz) but it tries to predict the needed power somehow so the whole switching is done in more steps... (as far as I remember)
So yes its performace is a bit below the on demand - but should not be that noticable - but it will also save your battery.
(This is an old question from 2014). That time the phone was fast enough to cope with anything but 4 years and it is slow now. I want to know if I should OC it, risk and rewards. And if I do, then to what extent. Thanks in advance.
Overclocking is not too risky, if you do it right. Be smart and overclock as you would any computer: increase the clock speed in increments, and test it. If you experience any glitches, crashing, or shutdowns, then back off.
Damage to the cpu from overclocking is mostly about the heat. Smartphones have safeguards in place to prevent overheating. The phone will shutdown once it starts getting hot, well before it reaches temperatures that will damage the CPU.
In theory, more heat is more stress on the CPU, and will result in a shorter life. But in real practice, you should be more worried about the battery. The life of the battery will be affected long before the CPU.
End of the day, you can get some incremental improvement from overclocking. But don't expect a huge difference. The times I've tried to overclock an old Android device to get a little more life out of it, I've mostly been disappointed. Not a significant performance increase, especially considering the loss of stability (lots of crashes, reboots, etc).