Related
Hey all,
My phone is rooted. I'm wondering how Overclocking might effect battery life. Better? Worse?
Also, what is a solid speed to OC on the Captivate?
It will be worse, but if you do UV it will last a bit longer...
Battery life will go down, but its by such a small amount, you wont even notice it(depending on how much you OC it)
and stable OC values will be different for every phone since all processors are not made equal. For example, my max stable overclock is at 1.2ghz, but my friend was stable at 1.4 with undervolting by 100.
You really just need to play around with it and find what works for you.
If you really want a solid stable number, im pretty sure every captivate I've seen can go up to atleast 1.2 ghz.
Sent from my Captivate using XDA App
Yuna said:
It will be worse, but if you do UV it will last a bit longer...
Click to expand...
Click to collapse
That is very untrue. I read an article (for the life of me can't find it) that overclocking is actually better for battery life. I have in fact had better results on my LG Optimus V with overclocking at 806mHz (highest stable clock setting) than with 600mHz (standard). LeslieAnn (Harmonia dev) linked to the aforementioned article in one of her posts. If I find the link I will post it.
I've only OC a couple of times but 1200Mhz should be stable for the majority of phones out there. The most I've got out of my phone was 1440Mhz on MIUI with Glitch kernel, while my friend was able to hit 1600Mhz with same rom and kernel. It took me quite a bit to figure out what voltages for what steps etc to get it to work well so if you do not feel like tinkering with it for a long while I wouldn't try to push your OC too high.
Battery life doesn't usually decrease unless you over volt. That being said most Galaxy S will get 1.2ghz-1.3ghz on stock voltage. Usually a good idea to undervolt most "steps" except the high clocks (1ghz+) but this varies on phone, rom, kernel, etc.
prbassplayer said:
Battery life doesn't usually decrease unless you over volt. That being said most Galaxy S will get 1.2ghz-1.3ghz on stock voltage. Usually a good idea to undervolt most "steps" except the high clocks (1ghz+) but this varies on phone, rom, kernel, etc.
Click to expand...
Click to collapse
ohh... i thought that said undervolt... but over clocking as well will make it decrease some.
If you ran faster you would burn more energy in the same amount of time. (over clocking)
If you reduced the weight of your legs or gravity you would burn less energy. (under volting).
Most people dont notice battery drain when overclocked because the processor speed doesnt run full speed all the time. it governs to different speeds for what it needs to do.
go stock speed and play a game till it drops to a percentage.
recharge
overclock with NO undervolting and play the game again till the same percentage.
less time. guaranteed.
just sitting at the homescreen and flipping through your app drawer and using face book wont kick your phone into high gear, with stock or overclocking. you will never notice.
TRusselo said:
ohh... i thought that said undervolt... but over clocking as well will make it decrease some.
If you ran faster you would burn more energy in the same amount of time. (over clocking)
If you reduced the weight of your legs or gravity you would burn less energy. (under volting).
Most people dont notice battery drain when overclocked because the processor speed doesnt run full speed all the time. it governs to different speeds for what it needs to do.
go stock speed and play a game till it drops to a percentage.
recharge
overclock with NO undervolting and play the game again till the same percentage.
less time. guaranteed.
just sitting at the homescreen and flipping through your app drawer and using face book wont kick your phone into high gear, with stock or overclocking. you will never notice.
Click to expand...
Click to collapse
I have my phone and nook's clocking speed set at the same for min/max settings. I play a mean game of RUA and AirAttack HD. I've in fact timed my battery life on standard clock settings and my overclocking. While overclocked, my nook lasted 10 minutes longer than at standard speeds (while playing AirAttack HD, which has intense 3D graphics). And you might suggest I undervolted, but I never touch that stuff. My volting stays where it is.
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
ZeppeMan said:
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
Click to expand...
Click to collapse
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
set to 1.13 ghz
then screen off to minimum 245mhz
josemedina1983 said:
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
Click to expand...
Click to collapse
So you underclocked it, what about the speed? It's not to laggy?
Nexus one can run reasonably smooth @ 600mhz and above. It might not open applications as fast as it will be @ 1GHz though.
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
shreyas1122 said:
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I didn't said I want an overclock. It's allready very fast on 1Ghz (compared to my old Hero ), just wanted to know your thoughts about overclocking the N1.
im overclocked at 1152 mhz and profiles set for 245 max with screen off. Overclocking is nice because i like the snappiness but most people cant tell the difference between 998 mhz and 1152. its not needed to overclock but i think profiles help alot. just my two cents
Ok thx, I will try 1150Mhz and see (if it's stable and) what batterylife does. I'm also going to try underclocking.
I have my N1 only for a couple of weeks now and I must say, this phone is awesome. It's VERY fast compared to my old Hero. I remember when I was installing apps on my Hero it became very slow and couldn't do anything untill installing was finished. With the N1 you still can do things while installing apps without lag. The responsiveness and smoothness is also a lot faster. I loved my Hero Because it never let me down, ok it was all a bit slower, but it was getting there. Now with the release of Gingerbread (custom ROM) it became to slow for me and that's why I sold my Hero and bought the N1. It was very difficult to find one, because of the EOL (end of life). But eventually I found one and i'm very happy with it. The N1 is allready more 1 year old, but it still competes with the best phones out there.
I generally run overclocked at 1075MHz, which gives a good balance between battery power usage and processor power. My understanding is that a different voltage scaling method is generally used above 1075MHz, so power consumption will increase above that point.
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
ZeppeMan said:
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
Click to expand...
Click to collapse
This is, of course, dependent upon how the kernel is constructed, but this is what I have generally found to be true.
Give us some feedback
I overclocked it too 1075Mhz when screen is on (screen off 245Mhz). Will give my thoughts in a day or 2.
Just report that my battery drain is almost the same as on stock settings. I think it drains a tiny bit faster on 1075Mhz, but nothing major. On the other hand, I don't feel it's faster on 1075Mhz then on stock speed. Only benchmarks give me performance increase.
I'm now on CM6.1.1 with stock kernel (cyanogen), I tried other kernels like Wilmonks kernel,.. Although it was more responsive, battery was going down even faster. I get best battery results with stock kernel.
Hard to choose
more speed = more battery drain
less speed = longer battery
I think I stay with the last option (less speed = longer battery), because Wildmonks kernel doesn't give me enough performance increase over the stock kernel on stock speed.
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Either way, its so easy to play with the clock settings, i'd just have a play with a bunch of different settings if i were you.
liam.lah said:
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Click to expand...
Click to collapse
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
ZeppeMan said:
wanted to know your thoughts about overclocking the N1.
Click to expand...
Click to collapse
well my thoughts: underclock!
so you can watch movies on it all night!
Sent from my Nexus One
shreyas1122 said:
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
Click to expand...
Click to collapse
You can use SetCPU to create profiles based on different circumstances.
Me, I have mine clocked to a max of 1075 and min of 245 with the screen on, 576 max / 128 min screen off, 998/128 charging (to reduce heat - overclocking while power is applied can make it silly hot), and a failsafe to clock down to 576/128 if the temperature gets over 50*C.
Fabulous app.
Correct me if I am wrong. When you use setcpu to "ondemand", the CPU speed can ramp up to max whenever necessary, otherwise the speed will tune down to min especially in standby mode. In that way, you can enjoy the advantages of overclocking and underclocking the CPU speed i.e. increasing performance when needed and saving power when not in use, right? When I loaded Rod's MIUI and Wildmonk's kernel, I can underclock down to 128Mhz and overclock up to 1.152Ghz. At the end of the day, I still have over 60% of power left after not so heavily use (some web browsing, checking email and listen some music). Overall, setcpu is a great app for me.
A lot of people say that overclocking the Nexus 4 is useless as it's so fast to begin with, but that turns out to be false, yes, it's useless for making e.g. games run smoother, as they all already do, but it's very useful for reducing loading times, and it turns out that the % of time saved is close to the % of increased clock speed.
My setup: Nexus 4, franco.Kernel updater v9.3.3, Franco Kernel #666, Jelly Bean 4.2.2 JDQ39, Governor Interactive. Angry pigs HD 1.1.0 app loading. Fresh reboot for each speed. I did three measurements for each clock speed and left voltages at Franco's defaults. I would suggest looking into the undervolting threads to figure out how low you can go with voltages, undervolting is good underclocking is usually not.
1026 Mhz 1025mV default Franco
15.4s
15.9s
15.7s
1512 MHz 1150 mV default Franco
11.5s
11.3s
11.3s
1620 MHz 1175mV default Franco
11.1s
10.6s
10.6s
1674 MHz 1175mV default Franco
10.3s
10.6s
10.7s
1728 MHz 1200mV default Franco
10.5s
10.3s
10.3s
Conclusion
12.5% faster clock speed = 8.85% faster load time, which means increasing clock speed is 70% effective at reducing load time going from 1512 Mhz and upwards.
40% faster clock speed = 35% faster load time, meaning that people who think running their device at 1026 Mhz is as good as 1512 Mhz are wrong. Nearly doubling clock speed nearly halfens load time.
The reduction in loading time is reduced a bit as you reach higher frequencies, but it's still 70% effective so every extra Mhz helps cut down the wait. Overclocking the Nexus 4 is meaningless in terms of increasing smoothness IN APP, but meaningful in reducing load times significantly and in increasing the responsiveness of your system.
please tell me for saving the battery and still maintaining a little smoothness
the settings to use
i use faux123 kernel.. i just need the voltage,cpu clock n governer settings
so overclocking makes things faster.. really? who would have thunk. and you just found this out?
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
zakoo2 said:
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
Click to expand...
Click to collapse
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
So, a 50% increase in clock cycles pushes the performance by a bit.
Who would've thought...?
well that's normal, overclocking = more power draining, more speed; just like with CPU or ram on pc, no rocket science here.
alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
OC? Don't you mean Downclocking or Undervolting?
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
gohan040 said:
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
Click to expand...
Click to collapse
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
It REALLY depends. I'd say most day-to-day usage, an overclock can actually help save battery by 'racing' to sleep (hurry up, finish, drop to deep sleep on cpu AND radio). I think being on 3g makes it even more pronounced because you're letting the radio drop back down to a lower power state as well as the CPU. So if you need to quickly open an email attachment, and cpu is the limiter, it can help it finish, get off the network, and back to idle state faster and save some battery. Now if you go on running benchmarks instead where you just keep throwing more work at it that's a seriously different story. There is also a point of diminishing returns (usually 1 or 2 steps before the absolute limit, in our case about 1670mhz) but in general, a moderate overclock can help.
sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
I agree with u, but remember its a theory.. U finish faster so the time it uses more power is less....
^^Look at the post above me, he got a good example^^
The best of both worlds (if your phone is capable to do this) is when u UV and OC. U would use less power on a higher frequency. Win-win in theory.
But I know what u mean and its hard to believe, but I think that's what @alan1901 wanted to say.
a pigeon delivered this message.... ** your welcome **
If you are lucky, you can overclock using STOCK voltage for the maximum clock.
IE, i see many undervolting their phones by alot. I would just try 1150mV (default voltage for 1.5ghz) for your highest speed (OC as high as you can with this voltage), which means you are not using more power, but still making your phone faster.
Haven't tried on mine, but say 1.6-1.7ghz should be possible with 1150mV for a few at least.
No, 50% OC is not = 50% reduced load time
Let me summarize:
OVERCLOCKING > UNDERCLOCKING FOR THE AVERAGE (POWER) USER
You load a lot of apps, you don't play games or watch videos for hours, productivity is your focus. Depending on use you could save probably 1 - 6 hours a year (see assumptions below). Battery gains won't be significant, but spending less time with the LCD/Wifi etc on could give you some gains as the CPU is one of the lower power drain components.
UNDERCLOCKING > OVERCLOCKING FOR THE 3D GAMER
You spent a lot of time playing CPU intensive games, keeping the CPU cores at max clock speed for extended periods of time. In that case you could get some battery life gains at the cost of responsiveness and app loading times - your call.
IN MORE DETAIL
-------------------------------------------------------------------------------------
UNDERCLOCKING + UNDERVOLTING PROs/CONs
+ Reduces CPU temperature, if that matters to you.
+ IF keeping the CPU at max clock speed for extended periods of time, a lower max voltage could give you enough extra battery life to negate the time lost waiting for apps to load - your call.
- Increased load times - even on the Nexus 4 a lot of apps take > 10 seconds to launch, and don't forget in-app load times, reboots etc.
- No significant battery saving in most cases, potential for loss (if doing a lot of app loading you could even get worse battery life as the screen, wifi etc has to stay on for longer, and the screen is the main battery drain).
- Time spent finding stable voltages.
OVERCLOCKING PROs and CONs
+ Potential small battery life gain, as your device spends less time with the screen/wifi etc ON.
++ SAVES YOU TIME. I'm estimating 1 - 5 hours a year depending on usage.
- Times spent finding stable voltages and clock speeds.
-/- Apps does not RUN smoother.
Why 50% CPU does not = 50% reduced load time and why you test things
---------------------------------------------------------------------------------------------------------------------
It'd be more like 40-30% depending on relative clock speed. I did a simple test as we did NOT know that app loading was mainly CPU limited, could have been memory. And If load times didn't go down there wouldn't be ANY reason to OC and underclocking would be a good idea.
Assumptions behind an estimated 1 - 6 hours saved a year by overclocking
---------------------------------------------------------------------------------------------------------------------
Say that you're on average waiting 4 minutes a day waiting for apps to load, rebooting your phone, waiting for web pages to load, waiting for in-app content to load etc.
Overclocking can cut down that wait time up to 10%, that's nearly 1/2 a minute saved every day, 3 1/2 minutes a week, 3 hours a year. This means you can get a good return on the time it took you to overclock your device, assuming you'll keep it for a couple of years. So if that's the case, why not do it? You'll save some time and you'll enjoy using your device a bit more.
Currently I'm OCd at max 1674 Mhz @ 1225mV, otherwise using default Franco voltages and interactive governor. Stable and very snappy Might be able to reduce voltage and retain stability but this is fine.
zakoo2 said:
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
Click to expand...
Click to collapse
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
I said little OC. Example. Stock cpu clock is 1000mhz and 1000mv. Now, you OC your phone to 1200,1300mhz without changing voltage, or by increasing it a little bit(+25, +50mv, to make phone stable), it will use higher cpu frequency with the same voltage like on lower frequency or with a little higher voltage. So it would finish tasks faster, going to idle faster without getting any heat and give you more battery. On my nexus s and galaxy s3, galaxy s2, i tested it, and it helped (about 30min more screen on time for me). But if you play games a lot and doing some heavy tasks then underclock and undervolt are best for you. But on that beast of phone, i woldnt underclock it beyond 1.2, 1.3, not sure what frequencies are there. If you UC that phone a lot, you can easyly go with some weaker phone.
Sent from SpeedMachine i9100
is there any kernel that can overclock with 4.3?
Andre_Vitto said:
is there any kernel that can overclock with 4.3?
Click to expand...
Click to collapse
yes, most of them. some even overclock up to 2052mhz :victory:
simms22 said:
yes, most of them. some even overclock up to 2052mhz :victory:
Click to expand...
Click to collapse
like?
Check the Development sections.
This thread makes my head hurt.
I am looking for a CPU governor I can use with just the root that our AT&T Note 3's currently have. What I would like to do is have a governor so when certain games that are really draining my battery are running that it will lower the CPU and give me better battery life. Is this possible with our current root only? I read that SetCPU had this feature with app based profiles but the recent reviews are stating that the app based profiles are not working correctly. Does anyone have any suggestion of what I could use?
Set cpu is working for me, I have the paid version though. I put it on performance governor and it held 1 core wide open at 2265. I then changed it to ondemand and the core dropped to 300. There's also a conservative, interactive, user space and power save governors. Search governors for explanation of each governors settings/purpose.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
kitsinni said:
I am looking for a CPU governor I can use with just the root that our AT&T Note 3's currently have. What I would like to do is have a governor so when certain games that are really draining my battery are running that it will lower the CPU and give me better battery life. Is this possible with our current root only? I read that SetCPU had this feature with app based profiles but the recent reviews are stating that the app based profiles are not working correctly. Does anyone have any suggestion of what I could use?
Click to expand...
Click to collapse
You can set a profile to lower CPU when your battery gets above a certain speed. That would be your best. Another alternative is to set a max speed for x condition or y. Doing all of the above will lower the performance of your game. It would be best to try different max speeds that still allow you to play your game enjoyably and go from there. Games are just a battery hog, even if you lower your speed it will still take milliamps than you'd prefer. I think off hand to just try, is set max speed at the 15xx speed and just use on demand or interactive. Power save will lower performance too dramatically and possibly kill more battery. Performance is really for the most demanding of games or benchmarking.
Sent from my SM900T.
@rbiter said:
You can set a profile to lower CPU when your battery gets above a certain speed. That would be your best. Another alternative is to set a max speed for x condition or y. Doing all of the above will lower the performance of your game. It would be best to try different max speeds that still allow you to play your game enjoyably and go from there. Games are just a battery hog, even if you lower your speed it will still take milliamps than you'd prefer. I think off hand to just try, is set max speed at the 15xx speed and just use on demand or interactive. Power save will lower performance too dramatically and possibly kill more battery. Performance is really for the most demanding of games or benchmarking.
Sent from my SM900T.
Click to expand...
Click to collapse
so this may be a dumb question, but is 300MHz the lowest clock speed it can reach? I just installed Better Battery Stats on my Nexus 7 (2012) and it can get down to 50MHz. Just looking to conserve more battery. Thanks!
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Solarenemy68 said:
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Click to expand...
Click to collapse
That's not really an option for me. I often rock the phone with no case at all and like it in its 168g form. I already have 30-40 hour batterly life with 3-4 hrs of screen time. But I just noticed the lowest clock speed it 300Mhz and I think it can be lower!
Solarenemy68 said:
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Click to expand...
Click to collapse
Yes! This is my solution. No worries when mpdecision gets stuck on 4.4.2 and stops sleeping cores, who cares?! Pry-Fi running continuously in War mode, booyah.
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.