I know there are pros and cons to overclocking but what about underclocking?
Sent from my GT-I8150 using xda premium
iBlueee said:
I know there are pros and cons to overclocking but what about underclocking?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Pro: Lower battery usage, cooler (as in temperature) phone --> longer battery lifetime.
Cons: CPU-intensive apps (e.g., Titanium Backup using bzip) will be slower.
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
I am casually always underclocking my phone for battery life. Yes, its as pepoluan said.
But I think I might be able to share a bit more of my still new knowledge. My phone is mostly set to 1024 or 1209 as max.
(I'm a new member in xda, but stood anonymous modding around since a year ago)
Pros: Significantly better battery life, but it depends on your governor and scheduler used. About temperature its quite arguable but usually it will be lower without high activity in your phone.(will be stated at cons)
Cons: I might say that there are really small affection to your common usage. But when it comes to heavier usage such as gaming or high activity browsing, it might double your battery usage. As the CPU will now use longer max (underclocked)frequency to complete what it could complete when its on its normal frequency. As a result, the phone heats up quickly too.
May I suggest that instead of underclocking maximum frequency, try overclocking your minimum, its my earliest experiment, try on 368. It might or might not boost your battery life slightly too. As less ramping is needed.
Please correct me if I'm wrong. I'm very new here.
Related
Heya,
I've heard of this SetCPU program, and figured it has some solid potential of saving battery power.
My question is - does it work? I've read several post claiming that SetCPU doesn't work on HTC phones.
If it does - will using the "Mix \ Max frequency" mode will save battery during stand by and normal usage, or just slow down the phone?
Using Rooted Desire, LeeDroid 2.2d.
Its primary use is to overclock the CPU, its secondary use is to create profiles and reduce the clock or change the governor. This will improve battery life slightly but also decrease responsiveness, depending on how far you go.
You'll need root if you want to use it.
To really increase battery life you have to use a custom ROM with an undervolted kernel.
So you're saying that the saving in battery life is insignificant considering the slowdown in performance?
yes, you use LeeDroid which is undervolted, thus perfect conditions.
It also uses a custom governor 'Smartass' which gives you best performance while using it and limits the max. clock while sleeping. That's the most common method to increase battery life with SetCPU while maintaining performance. So no, you don't need SetCPU, LeeDroid handles everything perfectly already.
However, the Desire has a very powerful CPU, compared with other Smartphones. So you can use SetCPU to limit the clock to maybe 700MHz or 800MHz. This will increase the battery life but also reduce the processing power. If you don't play games, don't do a lot of simultaneous things or browsing huge websites, don't use heavy loaded homescreens, it's possible that you don't notice the reduced processing power.
Thanks again
I guess there is no damage to the SnapDragon if I lower clock speeds a bit...
But, if I want to do some overclocking - how far is it safe to go?
When I OC'ed my Q6600 CPU I used the TheremalRight Extreme 120 with two Slip Stream fans to cool it off.. So, will heat damage be a constant threat to an overclocked Desire?
I currently live in Israel, and it's hot as hell even on stock speeds
CoreOxide said:
Thanks again
I guess there is no damage to the SnapDragon if I lower clock speeds a bit...
But, if I want to do some overclocking - how far is it safe to go?
When I OC'ed my Q6600 CPU I used the TheremalRight Extreme 120 with two Slip Stream fans to cool it off.. So, will heat damage be a constant threat to an overclocked Desire?
I currently live in Israel, and it's hot as hell even on stock speeds
Click to expand...
Click to collapse
I for one has chosen to disable the default powersave in Auraxt sense, and then using SetCPU to control it, i get a day of power easily, and still goes to bed wit 50% power, that is with stock clocks on normal usage, but with minimum power (245) on screen off
Re overclocking:
To reach high clock speeds you also increase the voltage on your PC, else you can't increase the frequency that drastically.
Because you can't improve the cooling on the desire you have to keep stock voltages but also can't overclock that much.
The overclocking methods on the desire keep the voltage at stock values or even lower (defrost rom).
I don't know the voltage values for LeeDroid.
I it shouldn't get warmer. In the worst case it will crash and reboot until you reduce the clock speed.
Sent from my HTC Desire using XDA App
Does anyone know If underclocking the CPU actually save battery life?
It would technically save an incy teency bit but I doubt you will really notice a difference given the small window of safe underclocking. When I tried it my phone ran like crap but what do I know. The way I figured it was the phone was optimized at 1.2ghz. It's like putting 87 octane gas in a high end sports car. Some people swear by it though. Just try it and see if it works for you.
It can but if it's not by much I would doubt you would notice a difference..
-Sent from my Blu Kuban themed Tapatalk like a Boss
Very true. I would just slightly under volt it then under clock it. Like 25 to 50 mV under. Any less than that and you can run into issues. Tagraz has an OC/UC module within the app.
Sent from my SPH-D710 using xda app-developers app
I like to underclock but noticed that if I underclock + undervolt + use any tweaks my battery drains faster... I've been experimenting with different mods and I know on my phone if I just underclock + under volt I get no issues.. if I run just the tweaks ( kob's or td's ) without underclockin and undervolting everything is OK... so trying to see which one is better on battery + performance...
Sent from my SPH-D710 using XDA Premium App
It's been my experience on gb that under clocking from 1200 to 800 vastly improves battery life. It's possible it's placebo, as I've done no specific testing, but the battery life does appear substantially better. Oh and that is with no undervolting
Any devs think it's possible to lower the min clock speed on our phones? 384MHz seem a bit high compared to all the other devices I have used... (long list)
I noticed the n4 was able to bring it down to 300MHz. Any possibilities for us? Or any custom jb kernels in the works?
Thanks
Sent from my LG-E971 using xda app-developers app
This would need to be coded in kernel. However, lowering the minimum frequence would not mean we would have better battery life. I could go really long explaining this but i'll try to keep it basic. 1st, the energy used vs frequency is not linear. For example, 500Mhz would not use half the energy than 1Ghz. 2nd, This would either cause the kernel to have an higher load than 384Mhz, which would in fact increase the energy consumption or Bump the kernel to an higher frequency, which would make that frequency useless. In both case we are not winning any battery life.
How much can the phone be underclocked while maintaining the stability of the system?
What would happen if i set Max freq to 600 Mhz?
What is the best thing to do to save up the very last bit of juice in the battery for emergency situations where i would only need the phone and message facility? Besides switching off Bt,wifi,sync.
Im asking because i was wondering if underclocking "too much" saves a substantial amount of battery when my battery is quite low and I am "hours away" from a charging port!
And is there a way to change the carrier name on the notification drop down to whatever we want.
Sorry if i sound noobish or if a similar query has been asked before
Thnx.
Underclocking the CPU dramatically isn't going to gain you a great deal in the way of extra battery life because:
1. Unless you are heavily taxing the CPU (complex 3d games etc), the biggest drains on the battery are the screen and the radio.
2. If the screen is off, the phone will drop the CPU frequency right down anyway.
The best way to get extended battery life is simply to carry spare batteries!
Regards,
Dave
Sent from my GT-N7100 using Tapatalk 2
I think 600mhz is way too low and counter productive or for that matter anything less than 1ghz. The phone will lag alot and you'll have freezes. You'll probably end up using up alot of the battery life trying to get tasks completed. You could try leaving the stock clockspeed 1.6ghz, set minimum cores to 2 and slightly undervolt to -25mv, leave the gpu setup to its default 533mhz and also undervolt to -25mv using a kernel that supports stweak app. Then run an app called Stability Test for 10minutes to check for errors.
Also I tried Go Power Master, which can be assigned to disable certain features once your battery hits critical low levels.
Sent from my GT-N7100 using xda premium
bushako said:
I think 600mhz is way too low and counter productive or for that matter anything less than 1ghz. The phone will lag alot and you'll have freezes. You'll probably end up using up alot of the battery life trying to get tasks completed. You could try leaving the stock clockspeed 1.6ghz, set minimum cores to 2 and slightly undervolt to -25mv, leave the gpu setup to its default 533mhz and also undervolt to -25mv using a kernel that supports stweak app. Then run an app called Stability Test for 10minutes to check for errors.
Also I tried Go Power Master, which can be assigned to disable certain features once your battery hits critical low levels.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thats quite informative. Thanx!
For the people that have been overclocking this phone for a while now, what are your opinions on the best max frequency above 1.5GHz to clock to while still keeping decent battery life?
Overclocking isn't exactly a battery friendly thing to do, you will see battery drain if you clock to higher frequencies. My only advice is don't oc too high if you want to keep battery life in mind. Going to 1.67 or 1.72 should give you a decent speedup without murdering the battery.
I run mine at 162 its no diff in voltage from 151 at least on uber kernel it is.. Also try to under clock the the freq until or happy and no random reboots
Sent from my SAMSUNG-SGH-T989 using xda app-developers app