Related
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
Is anyone using SetCPU with gingerbread?
I'm using GingerVillain 1.5 but I can't seem to find the right profiles with SetCPU.
Oc'd @ 1,2 Ghz without profiles.
Because when I use the screen off profile, my screen sometimes won't turn on.
Screen off - min 245 max 1200
Can someone help me finding the right profiles?
Share your user experience.
In my experience and many others too, the profiles are not needed. The only profile you should ever need is a temperature profile and that's only if you really have it cranked up.
Having a screen off profile is always bad since switching to another profile doesn't happen instantly - there are polling intervals involved and until the next cycle runs your phone will still be using the screen off profile. That makes the phone slow which causes SetCPU to take longer in switching profiles, bogs down the cpu and it becomes a vicious cycle for a few seconds (sometimes a couple minutes). All the while it's draing your battery because the cpu has to work harder. Even regular profiles eat the battery due to the constant querying of the systems status and processing power used for that - which is the main reason you'll hear people whining about their battery life (some aren't effected as much).
Profiles are just not a good idea except for a temp profile for those that oc to the higher GHz (probably 1.4+).
You could try using cpu tuner instead. Gives you way more options.
CM 7
You have a lot of options with cpu tuner.
What triggers and/or profiles do you use?
My screen on/off has been working fine with CM7 nightlies before and after the RC1. I've been using SetCPU with a normal profile of 1017max/245min and a screen off profile of 365max/245min.
I think your issue is with overclocking. Idk about Gingervillain but as far as CM7 goes lots of people are having issues with the on/off animations and wakelock issues when overclocked over 1ghz. Try using your profiles and clocking at or under 1ghz and see how things change.
Not sure why anyone would really need a higher clock than 1ghz but what do I know. I dont see any slowdowns at 1017mhz and I feel that anything faster than that would lead to heat or battery issues?
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
thanks bro, i OC'd to 1017 and there are no issues
ibemad1 said:
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
martonikaj said:
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
Click to expand...
Click to collapse
Every kernel that I know of out there drops down the clock cycle when the screen times out. The reason not having the screen off profile saves the battery is because SetCPU isn't constantly sending requests about the phones state and then checking that against your profiles to see if it meets the parameters set in them.
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
KCRic said:
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
Click to expand...
Click to collapse
This is very true. It is definitely hard to make a blanket statement because no two people have the exact same setup. All I was saying is what I've been doin with the screen off animation and I've been having pretty solid battery numbers.
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
Ok. My screen has been on for only 40min compared to the 3 hour stand-by and I've already lost 50%. I wasn't even doing anything. Probably 10 min of internet and video. And this is all on WiFi.
Took like 10 pictures and looked at them, messed around with the editors, but didn't use them, just was looking at the settings and stuff. Remember, this was all within 40 minutes.
Anybody else getting horrible battery like this?
FIXED: Ok, I'm a huge idiot. I have SetCPU with an overclocked profile, but I forgot to set a profile for when my screen is off, so it's just overclocking like mad crazy. Sorry.
Still shouldnt drain that much at all ..id consider bad battery maybe...
I use internet txt all day heavile from 7 am to 2pm im on half battery thats with zedomaxepic v3 1.6 oc kernel... Not version 6
Lost kernel is nice too ..just try the usually setting adjustments with sync off bluetooth wifi off
Good luck
Set cpu to 200/1200
Sent from my SPH-D710 using XDA Premium App
lojak29 said:
Still shouldnt drain that much at all ..id consider bad battery maybe...
I use internet txt all day heavile from 7 am to 2pm im on half battery thats with zedomaxepic v3 1.6 oc kernel... Not version 6
Lost kernel is nice too ..just try the usually setting adjustments with sync off bluetooth wifi off
Good luck
Set cpu to 200/1200
Sent from my SPH-D710 using XDA Premium App
Click to expand...
Click to collapse
Well yea, but I guess I should have been more specific. I was over-clocked to the max. I had a profile for the highest frequency, set at performance. So yea... I think it would have drained pretty fast. I forgot to "Enable Profiles" and have it change frequencies, depending. I wasn't like over-clocked like 1.2. eL oh eL!!
Been noticing this since last week. Every time I use my phone for like 1 or 2 minutes, the phone starts getting hot. Usually, it gets hot after an hour of use (Facebook, Messaging, Browser, Twitter, Play Store). Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
This hasn't happened to me before. Not sure if this is normal, but I just want to make sure.
My recent heat and battery drain was coming from an app. I didn't check the CPU.
I checked the battery area of the settings and found a locale add-on that was draining more juice than my screen.
sent from a secret underground bunker
It will happen if your signal is real bad or 3G is down in your area.
I don't think it's my signal. I get 2 or 3 bars almost all of the time at home with the FC09 modem.
Besides opening and/or using an app, it seems that the CPU clock will go max speed if I do something, such as scrolling. Battery is also draining quickly before this was happening to me.
Sent from my SPH-D700 using Tapatalk 2
InsaneHien said:
Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
Click to expand...
Click to collapse
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
AndyYan said:
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
Click to expand...
Click to collapse
Yeah, you're right. I even looked it up. It's part of Jelly Bean.
I'm going back to CM9 or The People's ROM.
You could try a different kernel, or lower voltage. Sorry not sure what phone this topic is for lol but that's some options. It takes a lot to get my phone hot, and I'm on jelly bean
Sent from my Galaxy Nexus using Tapatalk 2
I don't have this problem on nitest kernel with the ns4g modem
Sent from my SPH-D700 using Tapatalk 2
You likely have an issue with your settings.
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Ruedii said:
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Click to expand...
Click to collapse
It didn't help unfortunately.
I flashed CM9 earlier and the issue still exists. I'm now back on CM10 (11/22 nightly).
It's okay if this can't be resolved. I am probably gonna go back to a GB ROM.
EDIT: Issue still persists in GB. I'm guessing it could be a hardware issue? I have no idea. Back to JB. I'm still willing to try anything to resolve this. Thanks to those who posted some solutions.
Sent from my SPH-D700 using Tapatalk 2