Related
There's some apps on the market that can makes phone CPU goes faster and push it to its limit, and mine is called overclock widget.
One quick question here, does this app shorten G1 CPUs life? will it harm the CPU in the long run? If so, how much the damage it could cause??
My G1 is a little bit lag, i consider to use this app, but if it shortens the CPU life, than it's not worth it and im okay with the lag.
You can't OVERclock your G1. You can only clock it to its rated frequency. The processor is rated at 528Mhz, but when it's distributed, it's set to run between 245-384. So it's UNDERclocked when you buy it.
The process is made to run at 528Mhz, so you can safely do it. It will decrease your battery life, but won't hard your processor.
tehseano said:
You can't OVERclock your G1. You can only clock it to its rated frequency. The processor is rated at 528Mhz, but when it's distributed, it's set to run between 245-384. So it's UNDERclocked when you buy it.
The process is made to run at 528Mhz, so you can safely do it. It will decrease your battery life, but won't hard your processor.
Click to expand...
Click to collapse
lol then I feel dumb now that I used "overclock" word without knowing what it means. Haha
Thank's for the confirmation.
So even if I clock it to min = 528, max = 528, it will not harm the CPU at all?
Will it makes the CPU Hot for always clocking the rate to the max??
Yes, it will increase in temperature.
Typically, you don't want to run it at its maximum speed continually. Just for short bursts as needed. That's what automatic clock scaling is for.
riki28 said:
lol then I feel dumb now that I used "overclock" word without knowing what it means. Haha
Thank's for the confirmation.
So even if I clock it to min = 528, max = 528, it will not harm the CPU at all?
Will it makes the CPU Hot for always clocking the rate to the max??
Click to expand...
Click to collapse
lbcoder said:
Yes, it will increase in temperature.
Typically, you don't want to run it at its maximum speed continually. Just for short bursts as needed. That's what automatic clock scaling is for.
Click to expand...
Click to collapse
I see, Okaay, I will use it when I need it then, if 128-384 mb is the default rate by HTC, then I think it's the best freq rate for the phone...
Thanks for the info guys =)
For the record, you are "overclocking" it. It's clocked at a specific speed in stock format and you're OC'ing it from that.
TheSamurai said:
For the record, you are "overclocking" it. It's clocked at a specific speed in stock format and you're OC'ing it from that.
Click to expand...
Click to collapse
Wrong...
As quoted from http://en.wikipedia.org/wiki/Overclock - "Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer." Maybe as specified by HTC, but on actual terms, no, it's not overclocked.
r3s-rt said:
Wrong...
As quoted from wiki/Overclock - "Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer." Maybe as specified by HTC, but on actual terms, no, it's not overclocked.
Click to expand...
Click to collapse
lol @ proving yourself wrong.
I preordered my G1 and rooted it as soon as possible, fully charge it atleast once a day and keep my overclock widget set to 528 min - 528 max.. My phone holds good charge and works fine more than a year later
r3s-rt said:
Wrong...
As quoted from http://en.wikipedia.org/wiki/Overclock - "Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer." Maybe as specified by HTC, but on actual terms, no, it's not overclocked.
Click to expand...
Click to collapse
Quite a FAIL
Aznneedlovetoo said:
Quite a FAIL
Click to expand...
Click to collapse
HTC made the phone, but not all of the components. Qualcomm made the MSM7200A processor, and they set the recomended frequency at 528 Mhz. Anything lower then 528 should therefore be considered an underclock, and anyhting over should be considered an overclock.
OT, overclock is completely safe until a point. A company will test its products way harder then what consumer use for it would be. For example, if you were building a house in which the roof weighted a ton, you would use wooden walls that was designed for a ton. But, say that the roof is a little more then a ton, 1.001 tons, would the walls break? No, they would not. Qualcomm probably tested the processor much higher then the recomended values and set the maximum low enough so that they would not have issues about consumers with bricked hardware. My phone runs perfectly stable at 652 Mhz, but I cannot comment on battery life as my phone has always sucked way too much more then normal, even when I was still on stock. Setting it to say 160000 max and 528 min would be perfect for your phone without any risks.
http://pdadb.net/index.php?m=cpu&id=a7200a&c=qualcomm_msm7200a
For the most part, unless you are planning on using your phone for a decade or so, you should not worry too much about the effects of increasing your processor clock speed.
You will notice an increase in temperature, in fact it is actually quite significant and a bit scary. If I recall though, seeing performance charts, increasing the clock speed on the Qualcomm processor does increase performance, but really not by a significant or (correct me if I am wrong) discernible amount.
I know this contradicts a bit with what I said earlier, but its more of just my own theory and that is I believe the heat from the processor probably would be fine for the processor itself, but I don't know about the other components. The temperature actually does get so hot to the point where it would be uncomfortable to have the phone on your lap. I have a hybrid silicone/plastic case on my phone and it expands by ALOT when the processor is clocked to 528Mhz from the heat.
So what's the best solution?
I just bought an HTC Dream on Ebay. As soon as I get it I plan to unlock and flash CM6. Will it come with overclocking software? If so, what's the best way to get the performance when it's needed and otherwise let it underclock?
onecallednick said:
I just bought an HTC Dream on Ebay. As soon as I get it I plan to unlock and flash CM6. Will it come with overclocking software? If so, what's the best way to get the performance when it's needed and otherwise let it underclock?
Click to expand...
Click to collapse
you best bet is to use setcpu 2.0.2 and it wont come with it
I would just like to put a little clarification note in here about the definition of overclocking....
Fact is that the rated maximum clock speed is/may_be based on certain IDEAL conditions and that a particular APPLICATION of that component may have a lower rating as a result of its characteristics. Specifically, knowing that speed makes HEAT, one could rate a CPU at LOWER than its manufacturer's spec in order to keep it within the heat envelope.
I am not saying that that is what is happening in this case, but it could, along with battery life, be part of the equation that led to them setting the clock below the chip's maximum rated speed.
So from this perspective, bringing the clocks up to 528 COULD IN FACT be considered OVERCLOCKING.
Further perspective, the processor if considered as a stand alone device is rated at 528MHz, so those terms the processor is underclocked when running at a lower frequency
However if you look at the processor as a component part of a larger assembly, then the manufacturers defined speed is set by other concerns than merely that of the processor's designed rating, and in this context running it at higher speeds than the device's rated speeds would be considered overclocking.
It all depends on perspective, from Qualcomm's perspective, HTC underclock the processor, from HTC's perspective, we overclock if we raise the clock frequency above that which they rate the assembly at.
And as we are talking of a multilayer PCB with components on both sides, what is the heat rating of the components on the opposite side of the PCB to the processor? I don't know, but I bet HTC does, and that may be a factor to consider, the processor may not fail, but what of the surrounding components?
And for the record, I use setcpu, and have it scaled for 160-528, it does heat up under heavy use, but not so much that I worry unduly, as has been said, HTC probably do take the heat envelope into account, as most manufacturers do, and most take the safe approach, and prefer to stay away from the edges of the envelope.
So unless you plan to peg your cpu clock at 528 or nothing, it should be safe enough, and will not reduce the life of the device significantly.
I am sitting here, testing my battery drain in "nothing going on" mode. Phone is on but asleep, WIFI/GPS/3G all turned off. I'm actually having trouble getting the battery to lose charge - wish we always had THAT problem. Anyway, it's not of much use in this fashion, but I did want to establish a baseline.
My specific question is about processor modes. I have a kernel (I assume, not the ROM) with an associated voltage control app. In that app, I can manage my clock speeds. The question is: would I theoretically get better battery life by limiting my clock to lower speeds? And if no one has done this test, or knows the answer in theory, can we discuss the best way to provide a constant processor drain on the phone (although one that isn't tied to speed like I assume many of the tests would be) so that I can make the observations in a reasonable time span - a sixty minute test that drains 20-30% of the battery would seem to be about what I'm looking for. As I said above, with nothing going on, I haven't drained a single % off the battery in 90 minutes.
I do a lot of backpacking and hiking, and the ability to use the phone and its GPS over a period of 5 days without carrying 5 spare batteries would be a real godsend.
There is a thread on here somewhere that lowering the clock speed actually increases battery consumption under load, as the processor has to work longer to do a task.
nickm50 said:
There is a thread on here somewhere that lowering the clock speed actually increases battery consumption under load, as the processor has to work longer to do a task.
Click to expand...
Click to collapse
+1
Don't lower too much for any reason. For e.g., if u have a overclocked kernel at 1280, u could scale it down to 1000, but don't go beyond that. Values over 800 are used very less unless there is a task demanding that much CPU.
Plus, by math, a task that takes 5 seconds at 1280 speed would take 8-9 seconds at 600-800 levels. So I wouldn't recommend reducing clock speed to such levels, even in standby mode.
I haven't found the thread about underclocking increasing battery drain, but it seems most people believe that canceling overclocking, and also undervolting, will extend battery life. I'll fool around with that for a while.
Soccer_Dad said:
I haven't found the thread about underclocking increasing battery drain, but it seems most people believe that canceling overclocking, and also undervolting, will extend battery life. I'll fool around with that for a while.
Click to expand...
Click to collapse
Yes. Cancelling overclocking means setting at 1000 from 1200 and 1280 or other speeds over 1000.
Under-volt to some extent, but not too much, esp at higher speeds.
diablo009 said:
Under-volt to some extent, but not too much, esp at higher speeds.
Click to expand...
Click to collapse
Yea, in theory, if you under-volt too much, it's going to stress the device to meet the action requirements for the required action. Right now, everything on the phone is calibrated to run on around 3.7v or just a little bit lower, so if a certain process doesn't acquire enough voltage or suck enough amperage from the battery, you'll get one of the common results: 1)Random shutdowns or 2)Battery drain.
vunuts said:
Yea, in theory, if you under-volt too much, it's going to stress the device to meet the action requirements for the required action. Right now, everything on the phone is calibrated to run on around 3.7v or just a little bit lower, so if a certain process doesn't acquire enough voltage or suck enough amperage from the battery, you'll get one of the common results: 1)Random shutdowns or 2)Battery drain.
Click to expand...
Click to collapse
It would lead to stress on CPU too 'cos it would be like putting regular gas and expecting peak hp out of a sports car. I can notice a difference in pickup and power between regular and premium gas in my car when I need quick pickup. For normal use it performs good, but u never know when u need that optimum power. Same with our phone CPU too.
diablo009 said:
Like putting regular gas and expecting peak hp out of a sports car.
Click to expand...
Click to collapse
Great analogy..... But..... You can just disable the knock sensor in the car and bypass the OBDII codes that pop up Yes, I am a gearhead lol. But in a sense, this is exactly what we are doing to our phones, trying to run with the minimum and expect the maximum.
And that brings me to this quick fix: Undervolt as much as possible, install a Nitrous Express kit for those times when you're in need of optimal power
I just don't mess with the OC and UV personally. I'm running everything based off of jk4 with Setiron's kernel with the standard lag-fix that's pre-applied with it, and I got rid of any... hmmm, I don't want to say "useless" apps, but I guess unnecessary or unproductive for me. If I show off my phone, people see how quick it is and like the customization of my launcher and how cool it looks, that's about the flashiest thing on my phone, but once you open the app drawer, it's all business.
I've undervolted my device and right now I have
100mhz - 825 mah
200mhz - 825 mah
500mhz - 800 mah
for some reason the 500mhz setting is stable and if I undervolt 100mhz/200mhz even more, I crash.
If I set my minimum processor power to 500mhz would I consume less batter than if I were to use 100mhz/200mhz?
Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels
Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.
Maskell said:
Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels
Click to expand...
Click to collapse
It's been my minimum even before posting this thread. I just started to wonder.
I've been on it for 10 hours now. I have 45% battery life left. Probably due to my 1700mhz being @ 1350mah right now.
I can assure you, it's VERY stable. It's so SMOOTH. Smoother than just having rocketrom and all that stuff. NO LAGS, NO SHUTDOWNS. ALL STABLE.
I can see better battery life, and CPU Spy says it used up 47% 1700mhz and 40% 500mhz. I think it's giving me better battery life.
It's evenly splitted up probably because I was using lulzactive governor.
but then again I didn't log my previous battery life without undervolting.
Some more insight would be nice.
SweCrow81 said:
Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.
Click to expand...
Click to collapse
There are alot of risks. Minor chance that you will cause hardware damage to your phone but I'm saying VERY minor. Just don't be stupid with voltages, like just suddenly overdropping the voltages. Your processor might die.
It's scary as hell, it crashes alot while testing and all that ****.
Feels good when you get it stable though.
TL;DR
Very slight chance to damage your hardware; only if you're very daring.
It should increase your battery life by atleast 20% if you reach the peak of your processors limit.
Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help
clairenix said:
Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help
Click to expand...
Click to collapse
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest
kaos_king said:
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest
Click to expand...
Click to collapse
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?
clairenix said:
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?
Click to expand...
Click to collapse
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.
I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.
kaos_king said:
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.
Click to expand...
Click to collapse
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
liutszho said:
I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.
Click to expand...
Click to collapse
It's basically the same with SetCPU aside from its voltages.
I do not know if it should be used with SetCPU with the note because from what I've researched. It's only a common practice with SGSII.
Tried setting 100 and 200 mhz to 825. Crashed my phone twice in one day using it, gonna revert back to 875
clairenix said:
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
Click to expand...
Click to collapse
Many thanks!
I will just experiment then, i didnt want to do that and then cause hw damage. I'll let you know how my processor gets on
Hi guys!!!!!!!!
I want to know, if i want to overclock my nexus 7 what is the max safe temp i can go?
If my fuzzy memory serves me right stock thermal throttling starts at 85c and thermal shutdown at 100c..
Thanks
Thanks but is not what i asked for i asked for the max SAFE temp for the nexus 7 because i want to overclock the device!!!!
But thanks anyway
If someone wants to put their opinion go head that will help me ALOT!!!!!!!!!!!!!
GumarGamer said:
Thanks but is not what i asked for i asked for the max SAFE temp for the nexus 7 because i want to overclock the device!!!!
But thanks anyway
If someone wants to put their opinion go head that will help me ALOT!!!!!!!!!!!!!
Click to expand...
Click to collapse
Oh boy.. ..... ... What I gave you is EXACTLY what you asked for. I'm going to suggest you don't overclock because it's apparent you have no idea what you're doing or talking about.
I know what i am doing
I overclocked many devices and computers so i know what i am doing but 85 is not a safe temp so if know the max safe temp tell me if you don't stop insulting me and get a life.
GumarGamer said:
I overclocked many devices and computers so i know what i am doing but 85 is not a safe temp so if know the max safe temp tell me if you don't stop insulting me and get a life.
Click to expand...
Click to collapse
Negative bro. Just because you've overclocked "many devices" doesn't mean you know what your talking about. He answered you and your response is get pissed and tell him he's wrong? If you know he's wrong you must know what's right, so why'd you ask!? If the manufacturer sets the the "safe temp" at 85 then yes 85 is safe enough. If you think that's too warm, fine pick a lower temp and go with it.
Sent from my Nexus 7 using xda premium
Sorry
Sorry I overreacted
The question as posed has no answer.
The stock kernel throttles at 95C and shuts down at 100C
Some dev kernels use lower values than this.
The effect of heat is cumulative, and likewise for the number of temperature cycles.
(The point there is that 5 hrs @ 80C could be worse than 1 hr @ 85C)
In general devices that are heavily used experience reliability failures earlier than lightly used devices, whether they are overclocked or not.
Good luck and enjoy your device - while it lasts.
bftb0 said:
The question as posed has no answer.
The stock kernel throttles at 95C and shuts down at 100C
Some dev kernels use lower values than this.
The effect of heat is cumulative, and likewise for the number of temperature cycles.
(The point there is that 5 hrs @ 80C could be worse than 1 hr @ 85C)
In general devices that are heavily used experience reliability failures earlier than lightly used devices, whether they are overclocked or not.
Good luck and enjoy your device - while it lasts.
Click to expand...
Click to collapse
I actually had a post written out going into this perspective also but decided to not even bother. :laugh: Good on ya though for going through with it. Another spin on it is the affect those high temps have on the hardware and chipsets around, or hovering on top of it. This is why I typically don't overclock my devices for anything other than a run through benchmarks. Also, besides using more battery and generating more heat for a longer duration, typical overclocks rarely produce any significant difference the end user can actually notice on these high end devices anyway. Hell, I don't even notice a difference on my single core Nexus S when OCing from 1ghz to 1.4ghz.
Hi,
I saw BravoMotolora's article about CPU binning, and I thought that it would be great if we compare CPU bin and voltages.
It will be great to know the relationship between voltage and PVS number.
Please follow this procedure
1. Install a custom kernel that lets you do undervolt, e.g. franco.Kernel
2. Do what BravoMotolora said
3. Undervolt your N5 by 25MV
4. Run Antutu
Then, you might see your N5 rebooting or giving you a Antutu score.
If you get the score, go and try the procedure again
I got to -50MV with PVS1 N5.
Please post your results(undervolt that you did and your N5's PVS) here!
Can you not do this?
Do not do what? I mean most of guys here will do undervolt to save battery anyway so won't it be good to share some intel?
Sent from my Nexus 5 using XDA Premium HD app
I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.
you do realize that many custom kernels set their voltages different than default/stock, and differ among themselves? for example, if you go -50mV less on using franco kernel, and go -50mV less using trinity kernel, it means nothing because their voltages differ to begin with. i mean you cant really compare each others voltages that way. you would need to write your voltages in real numbers, and cpu speed steps.
I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
johndrmr said:
I honestly never saw a huge benefit in undervolting. It can also cause errors which lead to worse battery life.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
Click to expand...
Click to collapse
agreed. i personally do better with underclocking, than with undervolting.
simms22 said:
agreed. i personally do better with underclocking, than with undervolting.
Click to expand...
Click to collapse
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though
This phone does pretty well arlt idle I think. Can't imagine you would see much gain from UV.
Sent from my AOSP on HammerHead using XDA Premium 4 mobile app
klin1344 said:
I'm the same as OP... I have PVS 1 and the max I can UV is -50mV.
Click to expand...
Click to collapse
I have a PVS 2 and can undervotl -75mV accross the board and -87.5mV at 300Mhz.
So 2,26Ghz I can run at 0.975 Volt.
CM11 with Bricked Kernel.
Together with Sync off, Google hotword off and optimized automatic brightness I get constantly 5 - 5,5 hours screen on time with websurfing, mail and music stream.
Marcel
menting said:
it's a lot easier to underclock 20% than to undervolt 10%, which approx. gives you the same active power savings. It's a lot safer too, if you don't have a spec sheet for the CPU handy.
underclocking does nothing to idle power (or leakage power) though
Click to expand...
Click to collapse
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.
rajendra82 said:
Underclocking drops the performance of the phone, as the peak performance is not available when needed. Undervolting on the other hand gives you battery savings without affecting peak performance at all. If done too aggressively, it can make the phone unstable, but there is never any danger of hardware damage. The instability will at most cause errors, random reboot, or a freeze up. If this happens, you know you've pushed too far under, and you can bump voltage closer to stock after booting the phone back up. If running stably, undervolting is actually marginally better for your phone hardware than stock voltage because you are wasting less of the energy in heating up the chips and damaging them.
Click to expand...
Click to collapse
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.
simms22 said:
i underclock, sometimes to 1036mhz max, with all 4 cores always on by default(no hotplugging). sure, in a benchmark itll score less, just like i expect to score more when im overclocked. but to the normal user, they would never be able to tell that my phone is only clocked to 1036mhz. meaning the user experience isnt lowered in any way. even intense gpu oriented games dont show that im running underclocked. so when you say it drops the performance, it isnt entirely accurate.
Click to expand...
Click to collapse
I agree with you here. 1036 mhz is a great CPU speed for running the device and most apps. Most games UC the CPU for better battery temp like in PPSSPP. Less temperature throttle and more stable frames per second.
Benchmarks are a difference story though but who cares about those. UC is lag free, and buttery smooth so why not?
Sent from my Nexus 5 using Tapatalk
zz_marcello said:
Sorry, but CPU underclocking means always a drop in CPU performance.
When you compensate this drop in your case by always having all four cores active you produce more heat with the active cores.
(and I estimate it will produce more heat/battery depletion than the original phone settings. (max 2,26Ghz and variable core usage)
When you argue that in general a normal user is not realizing a drop in performance due to underclocking...fine.
But it will always be a drop in performance.
Undervolting in opposite to underclocking produces no drop in performance but actually a rise in efficiency. (and thats what CPU/GPU development is all about).
Less heat, less battery depletion, same performance.
Why not taking advantage of that by undervolting?
Its free lunch.
Click to expand...
Click to collapse
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.
simms22 said:
again, sure, if youre benchmarking the performance will drop, yes. but if its something that the user doesnt see or feel, then its irrelevant.
no extra heat is produced. also, i get 5.5-7h screen on time with very heavy use. granted, i use the browser much more than i game, but thats what i use my device for mostly.
when needing the extra performance, or wanting to, i overclock. everybody uses their device differently, has differing needs. i would never say one way is better or worse than the other way.
Click to expand...
Click to collapse
You can do everything you are already doing, but also undervolt, and your battery life will increase, without affecting your performance. Your performance will be different than my performance (because I don't underclock), however imperceptible as it may be. So undervolting is still better than not undervolting, even for you.
Using EX kernel 3.27, underclocked to 1.5Ghz, undervolted to "700 min" and using "stock" thermal throttling setting. Rock solid and it barely even gets warm now. Responsiveness and performance is only a touch worse than stock; the only places I really notice any performance reduction is in intensive games and app install times. Battery life is massively improved.