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
Related
I was wondering what were "optimum" SetCPU settings while running cyanogenmod 7?
Optimum for what? battery life? performance?
Of course, you could just keep it overclocked, as high as 1.8ghz I think depending on your kernel. But your battery life won't be that great.
You can also keep it at the stock 800mhz.
Most people I bet keep it around 1ghz, and have SetCPU profiles set up to lower CPU speed as battery levels get lower and lower.
I personally (not on CM7) set mine up to lower CPU a tad at 40%, even lower at 20%, and drastically lower at 10%.
I guess optimum for performance while saving battery life. I'm new to the whole overclocking and I'm not sure what profiles to set up
Sent from my HTC Vision using XDA App
Well the thing is its really all personal preference when it comes down to it. Just tweak with your settings and check out your results.
I mean optimal performance with maximizing battery life would follow a few basic profiles:
Screen off: 245min/245max
When <10%: 245min/~500max (my personal preference)
And if you're trying to keep your battery pretty decent, I would recommend keeping your clock speed at 1ghz or lower maximum. Anything higher you're gonna start seeing negative battery life.
There are many other things to do to lengthen battery life that aren't SetCPU related, such as managing your radios and networks.
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
smartass v2 and ondemand are very popular on the XDA
Which do you like?
I think smartass is a better governor in my opinion.
Sent from my Inspire 4G
Neither is going to make your battery bigger, lol. But I tend to use smartass. I think the key to saving battery is lowering your sleep CPU to as low as possible.
Sent from my HTC Desire HD using Tapatalk 2
I've been using ondemand and smartassv2 each for a while and I haven't noticed any increases in performance or battery life. Every phone is different, so I guess you should just find what works best for you.
Also, performance wise our phone's processor is more than enough to deal with most things. I have rarely ever felt that I've need to overclock (unless I'm trying to get a quadrant standard PR ), usually it's an issue with RAM (once again, for me at least)
Not so big difference, but I think ondemand is better.
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!