I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
Interesting point you raise actually.
I've just installed Setcpu and used the on demand governor. I left the values as default (200mhz for minimum and 1.2 ghz for maximum) - with no overclock.
I've immediately noticed swiping through the screens is a bit smoother and the biggest improvement is the gallery. All my photos appear much smoother. Before the gallery app was a bit lagy.
I haven't set any profiles yet such as screen off.
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
jzuijlek said:
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
Click to expand...
Click to collapse
Have you tried this yet though on the Galaxy S2?
There is definitely less lag than before - as stated, specifically in the gallery app. Just generally swiping feels more responsive as well. Battery is still pretty awesome, especially when using Lightening Rom 1.1 and the Android battery calibration app.
Hmm. I'll try SetCPU on the SGS2 and post back the findings (Performance+Battery).
I don't know how can it get any more smoother, I mean its already SO smooth!
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
alexleon said:
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
Click to expand...
Click to collapse
IT IS TRUE. I agree with every single line you wrote, it is just my expericence.
I have too setcpu conservative and undercloked 800 Mhz.
There no slow down or lag at all... But I am wondering if it gives a real boost to battery life. I am not sure of this.
I'll keep you guys posted... But I think that an undevolted Kernel it is really a need as for the solution of the damn dual core ginger bug that is sucking 20% of my battery every day
Well,from my experience with my Desire and Desire HD(won't even bother with the Hero,I had no real knowledge then),governors can make a huge difference.I for one like smartass or interactive governors(mostly the same).I wouldn't suggest conservative,interactive does the job much better.Tasks get done in less time and the CPU throttles down more quickly.Other than that,you can underclock or overclock all you like,it never made any big difference in battery life for me(Unless Sammy's CPUs are different in that aspect-Snapdragons are really "overclock-friendly").That's personal preference after all!
Anyway,the best solution IMO would be a vdd_levels interface.For those who don't know what it is,it is a mod made by -snq(Meet him at the Desire forums-That guy's a true LEGEND!He can patch/modify anything!),which practically allows you to change the voltage levels of the CPU on the fly rather than having to stick with the values hardcoded into the kernel.Using this and a simple script in GScript to change values that won't survive reboot or in init.d to be applied on boot,you can find the optimal voltages for your CPU(Don't forget,every CPU is unique and different),thus reducing heat and maximizing battery life.
If a dev brings that to the SGS2 it will be a big step in the right direction as far as I'm concerned.
I use SetCPU without issue, but only to run profiles (i limit the device to 500mhz when the screen is off). The rest of the time it scales itself up to 1.4GHz without fuss and using stock voltage. Battery life is fine, best ive had for an android device.
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
I did set ondemand which is a little more reactive and slightly smoother.
Though System Tuner is less cpu-consuming and much more useful on the SGS2. No need for all those complicated settings from setCPU. Only changing governor and changing frequencies on standby are useful.
leedavis said:
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
Click to expand...
Click to collapse
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
I am using Check Rom with set CPU I have it 1.2ghz max and 200. Using conservative governer. I been off charge for 15hrs, however I am using light usage I am on 72% screen on has been 5h 25m at time of writing. Not yet calibrated the battery.
jonny68 said:
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
Click to expand...
Click to collapse
What are the settings are you using for the setcpu program in your S2?? Did you remove the Juice defender application?
What exactly does overclocking a phone do? And how is it better? And how is it worse?
I just installed Kamma's GSM kernel and im overclocked at 1.8 ghz. My phone seems a bit smoother but I don't notice any battery life loss. So my question is, what are the downsides and upsides of overclocking?
Also, if anyone uses CPUMaster, what are their settings?
If you don't notice a hit on battery life, then there is no harm done at keeping it @ 1.8Ghz, in reality and in regular computers, overclocking TECHNICALLY reduces the life of the CPU, but not by a lot, and chances are that if it does die out because of it, you would have a new computer/phone by that time.
It's not too serious, plus the actual native speed of our processor is 1.5Ghz, not 1.2 which is what it comes underclocked at. Don't worry about it, you're fine.
I know everyone is excited about overclocking their primes, but has anyone thought about underclocking it? I would love to hear the capabilities of that on battery life. Also, will we be able to use setCPU to control our speeds on the prime?
Already can be done, in a sense on stock prime. JUST KEEP it in powersavings mode. You will get the most/longest battery life out of it. Plus you can still play movies or games in that mode just fine.
NOW IF YOURE rooted, I'd say get System Tuner Pro app. IMO its alot better than set CPU. It does all the same things and alot more. From there you can manually lower the maximum frequency range and there goes underclocking Or you could try out one of system Turner's preset modes. I believe they have a power saving one also.
Really though stock powersavings mode is good enough for long battery life. ITS optimized for everything to still work pretty well or fast. Manually lowering the Max speed too low might cause it too lag really bad or maybe even instability. It would be about finding that sweet spot to where everything still runs good.
ONE THING TO think about though is no matter how much you underclock, the display brightness will be the biggest battery drainer. SO underclocking with Max brightness or something won't make sense.Plus be on the lookout for undervolting once bootloader is unlocked.
Came here to say exactly this ^^^
I think demandarin's comment pretty much sums up the best/latest approaches to underclocking available for the Prime. As noted, it makes the *most* sense with the LCD brightness completely down.
However, the only *real* way to qualitatively discover how much savings a strong underclocking scheme would have is to test it. When the time allows (testing battery life on these things takes a LONG time!! ) I'll end up doing this...
I see alot of folks asking about over clocked kernels best combo and what not. Also they are asking if a over clocked kernel is out and has good battery life.
No over clocked kernel will ever bring excellent battery life lol. Truth is the more you up the cpu the more juice it will need. The stock kernel was set within standard speeds due to keeping things smooth and keep the battery life decent also keeping the heat down on the cpu... If you mess with things you will get faster speeds at the cost of you battery life and heat.
I am not saying not to use them you just can't expect a over clocked kernel to give you better battery life.. Also turning your brightness down will help save battery... Using WiFI will also help if your wireless signal isn't strong enough in your area. Don't run a antivirus program on your phone either lol this will also suck your battery down.. These are linux based phones.
Thought I would help out some of the folks that are asking about things like this..
Just so everyone knows, the power consumption of your phone uses a standard formula:
power = voltage^² * frequency
So for every bit of voltage you go up, power consumption drastically rises. As you raise the frequency then power consumption rises, but you have to double your frequency to double your power drain.
EniGmA1987 said:
Just so everyone knows, the power consumption of your phone uses a standard formula:
power = voltage^² * frequency
So for every bit of voltage you go up, power consumption drastically rises. As you raise the frequency then power consumption rises, but you have to double your frequency to double your power drain.
Click to expand...
Click to collapse
Nice Most kernels do get things thumped up with that route on it. More push means more juice.
Sent from my reaping 3D
I have the same problem!
Just want to know everyones opinion on if it can really save life for the S4. Cause the way I see it is if the cpu is constantly being clocked down/up for instance, when my screen is off I have it so that cpu is at about 400mhz and when the screen comes on it boosts back up to anywhere between 1200 and max
If you're driving, and you slow when down to say 30mph and slam on the gas to get up to 100mph instead of steadily getting there, you're going to use a lot more gas. So if it is the same with the phone, aren't I using more battery life than saving?
Markymarc206 said:
Just want to know everyones opinion on if it can really save life for the S4. Cause the way I see it is if the cpu is constantly being clocked down/up for instance, when my screen is off I have it so that cpu is at about 400mhz and when the screen comes on it boosts back up to anywhere between 1200 and max
If you're driving, and you slow when down to say 30mph and slam on the gas to get up to 100mph instead of steadily getting there, you're going to use a lot more gas. So if it is the same with the phone, aren't I using more battery life than saving?
Click to expand...
Click to collapse
I'm not entirely sure, but with your example, doesn't that depend how long you're going 30 or how long your screen is off at a crack? If you turn on your screen for 10 minutes for every 20 it's off, I think it would save your battery more in the long run.
You use more gas in the car analogy as you have to overcome a ton or so of mass driving at 30 mph. Changing clock speeds faces no such resistance, so it won't be the same with the phone.
yes, the acceleration doesn't really affect the drain. the fact you're running at a higher clock speed is the drain. you can adjust your steps and max speed, thus saving a little bit of battery. undervolting can help to, but the cpu usually draws so little power that the savings may go unnoticed.