Develop Bugs

[Q] The perfect SetCpu settings for powersaving

I'm really struggling with battery life at the moment. Has anyone got settings I can use to save on battery life in SetCpu? Profiles etc

+1
I'd like to know too.

I would also like to know =[ my battery dies wayy too fast. I have the darkstone froyo build on my htc hd2 phone energy rom. Any programs or SETcpu settings that will help out?

If your on a rom with preflock disabled then you can underclock.
The only thing you need to change in setcpu really is to make a profile for screen off and set it to 245 (or whatever is the lowest I can't remember) both max and min (leave it on demand, or interactive if your rom has that).
This should give you about 10-15 hours longer battery life

so i wouldnt have to make any other profiles like battery? temperature? stuff like that? should i get rid of my green power and advanced task killer?

No you can keep them (well I don't know what green power is....)
The other profiles are mainly only needed if your OVERCLOCKING, however if your not touching the default max (main profile) then your not overclocking (1ghz).
To save power you UNDERCLOCK which setting a lowered screen off profile would do.
If your slowing the CPU down then the temperature will not rise, so that profile is not needed.
And you don't need to slow the phone down when your using it so none of the others are really needed either.

No you can keep them (well I don't know what green power is....)
The other profiles are mainly only needed if your OVERCLOCKING, however if your not touching the default max (main profile) then your not overclocking (1ghz).
To save power you UNDERCLOCK which setting a lowered screen off profile would do.
If your slowing the CPU down then the temperature will not rise, so that profile is not needed.
And you don't need to slow the phone down when your using it so none of the others are really needed either.
i think im kinda get what you're saying (sorry im kind of slow) so i had just deleted my other profiles and made a screen off one have it set to max all the way right and min all the way left, on demand, priority 100. Now on the main screen i think i touched it cause i read somewhere for max all the way to the right and min all the way to the left. This is confusing lol

The settings I have for my Desire:
Default:
Conservative 245-998
Profiles:
Screen Off - Priority 100 - Powersave
Charging/Full - Priority 50 - OnDemand 245-1305
Battery < 30 - Priority 0 - PowerSave
Running along side JuiceDefender, battery life is acceptable to me

jdeezyboo said:
so i wouldnt have to make any other profiles like battery? temperature? stuff like that? should i get rid of my green power and advanced task killer?
Click to expand...
Click to collapse
Remove everything, setcpu included
Sent from an ipho.../ NETWORK DOWN-PLEASE DON'T TOUCH THE PHONE

Remove everything, setcpu included
Sent from an ipho.../ NETWORK DOWN-PLEASE DON'T TOUCH THE PHONE
__________________
When Chuck Norris holds the Iphone4, the signal increases
That totally defeated the purpose of my question and others before me. Our battery lifes sucked without any programs so now we delete it?

I used darkstones froyo for awhile too. Battery drain killed it for me. I had no luck with anything. Changed to a nand build and its much better. Apparently SD builds just use more battery. With the SD froyo I could never stay below 60ma a few times would drop to less than 10ma but just not consistent. I lost about 8% an hour in sleep mode. Give a well designed nand build a go. In sleep I hover AT 4ma. My battery with Moderate use easily last the day, heavy use (multiple calls, emails, and browsing for an hour or two) still does require a recharge

Im using carbon ara theme with pcb just turn data off wen aint using it via toggle and have a profile for sleep in set cpu for min and max of 245 and from full charfe at 7am by 6 pm im still 65%. Thats using fb checkin email playing angrybirds and checking the forum
Sent from my HTC Desire using XDA App

I also use advanced task killer and kill all tasks wen not in.use
Sent from my HTC Desire using XDA App

bad idea as you are actually making your battery work more by doing that.
Sent from my HTC Desire using XDA App

New to SetCPU!

I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.

You need to update your PRL ...

twigums said:
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
Click to expand...
Click to collapse
I always leave my main profile at 245 mhz min and 998 mhz max (ondemand mode). Then, of course, you'll want a screen off profile, and as far as that goes, I've heard that 128 and 245 draw the same voltage, so I have mine set to 128 min, 245 max (powersave mode). Other than that I just have some low battery profiles and a temp one. I don't really get any lag with this setup, but I've heard some people do. If that's the case, and I'm only talking about lag when first turning on, just up the 245 to 384 or something and I'd make it ondemand.

do i need to check set on boot under the scaling option

twigums said:
do i need to check set on boot under the scaling option
Click to expand...
Click to collapse
No. I would leave it unchecked. This has been known to cause some issues.

grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
what kind of issues are you talking about? i've only heard and practice leaving it off when experimenting with overclocking (since it can put you in a boot loop). once you find a stable overclock speed, you can check it to start on boot so that you don't have to open setcpu every time you reboot if you decide to run it at that speed.
on-demand is a little less laggy (barely noticeable to me) but may consume more juice than conservative.
most kernels will step down to 245 when the screen is off so creating a profile to do that is redundant. you can verify this with the app android system info under the system tab > cpu.
having said that, i don't use setcpu unless i'm benchmarking and want to overclock.
kings #6 bfs kernel is awesome for battery life (default is conservative governor). it's what i use. give it a go when you've gotten a good feel on how kings #10 cfs is working out for you.

Here's what I would hit up..
set it to conservative. Conservative starts your phone at your minimum clock speed and works its way up, as opposed to on demand which starts at the highest and works its way down.
then for advanced i have sampling rate at 50000
Up threshold at 95% <- that's saying that when the workload hits 98%, crank up the processing speed
Down threshold at 70% <- when the load hits 70% turn it down
That stuff right there is agressive as hell, and when I say agressive, i mean...you probably won't ever hit your max frequency unless you are seriously doing some heavy lifting. The settings there are what I use to save up battery, you can get through a day easy with everything on (GPS, Wifi, sync, 3g, the works) and with your current usage, since its similar to mine (except that i also run beejive, skype and twitter at refresh rate of 5min).

grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
Yeah I think you've probably just seen that on some custom kernel pages. They only say not to do that because if you're testing battery life with say...HAVS, it could interfere w/o you realizing it. Set on boot just means you don't have to turn setCPU on everytime you reboot your phone.

just go set a profile on minimal mhz and on powersave mode if kerenal allows if not just use ondemand

My problem with the "Set on Boot" option is if you accidentally fat finger the slider past your stable clock with it checked, you're looking at boot loops and possibly having to restore from a backup to sort it out. SetCPU really needs the "Set on Boot" option grayed out and a "Lock Settings" option that must be checked before "Set on Boot" becomes accessible (unchecking "Lock Settings" would also uncheck "Set on Boot").
Another option would be a user defined field for max stable clock in the advanced settings that would limit the slider on the main tab. Either one should eliminate accidental boot loops.

[Q] SetCPU and battery life - am I doing this right?

I'm looking to optimize my battery life without sacrificing performance when I need it. I know it sounds easier said than done, but I figure that if anyone might know how, they'd be here. My goal here is to have the performance when I need it, and to keep the battery preserved when I don't.
I'm rooted and running ViperROM 4.0.4 Trinity v2.0. I have the "Genocide 1.2GhzOC EB13 Kernel v0.3a" kernel also flashed to my phone. SetCPU is installed and I've set up my profiles, but I think I may be doing something wrong with them.
I am using autodetect settings as is recommended for adjusting clockspeed. Everything is set to on boot. All profiles are set to conservative as I'm not sure which ones actually apply. Below are screens for everything I have currently set up.
|
|
Am I doing anything wrong here? And if not, is there anything I need to do to improve battery life without sacrificing performance?

I would bump your charging max to 1200Mhz and keep the min at 1000Mhz, although I keep max and min while charging through AC power at 1200Mhz.
Your screen off profile is fine. If you get hiccups or missed calls for any reason, bump the max up to 400Mhz.
If you can run it smoothly, set your minimums for your battery profiles to 100Mhz. It what I'm at now and it runs fine. You may want to keep your minimum for your "screen off" profile at 200Mhz if you get hiccups or missed calls like I mentioned before.
As for your battery <50% profile, I'd set the min at 200Mhz if you're wanting to save battery. Don't want the phone running at a higher clock when it doesn't need it. That's the point of running the min lower.
I personally uncheck the "set on boot" to allow SetCPU to always come back to the appropriate profile rather than going back to the default setting.
Also, set a Battery < 101% profile which will be your new default. I have mine at max 1000Mhz and min 100Mhz and it works well.
Also, conservative simply means the battery will remain at the lowest possible clock until it needs more juice. Assuming it starts at 200Mhz, it'll bump up to 400Mhz, 800Mhz, etc. depending on what the demand is. It will jump frequencies from 200Mhz to 1000Mhz if necessary.
On Demand means the CPU will either be at your minimum set clock frequency or your maximum.
On Demand is usually the most compatible/stable, but the conservative setting is best for battery/performance if your kernel allows it.
Hope this helps =). Let us know if you have more questions.
EDIT: The "set on boot" button simply sets the min and max that's shown on the main screen in SetCPU. If this button is unchecked but the "enable" button on the profiles menu is checked, your profiles will still adjust accordingly.

I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!

I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\

I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.

badbeats said:
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
Click to expand...
Click to collapse
This might be a dumb question, but is your phone fully rooted?

I think so I used Clockwork mod 3.0.6 and I am running Bonsai 3, with 2.2.1

ZeppelinJ0 said:
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
Click to expand...
Click to collapse
Yeah I hear you, I get the same crummy battery life with SyndicateROM, I was dying for the 30 hours ! Starting to think it's the battery itself.

musclehead84 said:
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
Click to expand...
Click to collapse
Do you keep your 1200/100 on conservative? And what's the battery life you're getting on average? Dummy question but you know...
I'm going to try out this setting today actually with BakedSnack.

Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.

Blankrubber said:
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Click to expand...
Click to collapse
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\

ZeppelinJ0 said:
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
Click to expand...
Click to collapse
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App

Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1 I think this was a bug with the original release of Twilight Zone that was fixed in 1.0.1.

Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm trying this out right away, thanks!
This whiny message brought to you by the letter E for Epic 4g

Setcpu screen off profile

What's the lowest you've set for Setcpu's 'screen off' profile? I tried 200 min/200 max and it didn't wake my phone when I tried turning it on. I have it set at 200 min/500 max right now. anyway to go lower than that? I'm trying to conserve battery as much as possible.

i got mine set to 200/500 mostly because 200/200 caused glitchy wakeups and occasional glitches when running background tasks with screen-off such as navigation/music/etc.
i also undervolted both 200/500 to 825mv/850mv so either way they both are barely using any of the battery
main reason for locking CPU to 500mhz max with screen off is in case something goes haywire and goes crazy on cpu, at 100% cpu usage @ 500mhz won't heat up the battery at all.

Just 200/500 for me, 200/200 at one point and no more than about 15 minutes later the screen wouldn't wake up.

battery savers - is the grand underclocking itself

2 parts - one question one observation.
Stock everything.
While playing around with battery savers that change cpu frequency when the screen is off, I noticed no thrills cpu stats, that the default GRAND`s behavior is to auto switch to 312MHZ and deep sleep while idle and screen off, is that the case? is there no real need for apps like no thrills cpu/cpuspy to set min-max?
Is there a real need for battery savers?

egor27 said:
2 parts - one question one observation.
Stock everything.
While playing around with battery savers that change cpu frequency when the screen is off, I noticed no thrills cpu stats, that the default GRAND`s behavior is to auto switch to 334HZ and deep sleep while idle and screen off, is that the case? is there no real need for apps like no thrills cpu/cpuspy to set min-max?
Is there a real need for battery savers?
Click to expand...
Click to collapse
Yes, our Galaxy Grand will auto-reduced the frequency to lowest 312MHz on stock kernel when the screen is off, after a few moments later it will enter deep sleep which will conserve battery usage.
Unless you want to Max / Min performance all the time, I would say yes, you don't need those apps to take control over your CPU frequency.

It seems like the min-max is working beyond the screen off situation,
even if the defaults shown by no thrills cpu are 1200MHz .