Develop Bugs

SetCPU screen off profile, I don't believe is working

I have SetCPU to underclock all the way it can when the screen is off and that is the only profile I have, profiles enabled, no overclock, kingklick CFS Kernel #11, stock rom
my battery life if anything seems worse
any suggestions?
thanks

ryanleafasaurus said:
I have SetCPU to underclock all the way it can when the screen is off and that is the only profile I have, profiles enabled, no overclock, kingklick CFS Kernel #11, stock rom
my battery life if anything seems worse
any suggestions?
thanks
Click to expand...
Click to collapse
What sort of apps do you have running? I have SetCPU set at 245max and 245min at 100% when screen is off and it has helped my Evo battery last longer. And I have GPS and any IM clients closed when not in use. Using kingsclick #10

selders59 said:
What sort of apps do you have running? I have SetCPU set at 245max and 245min at 100% when screen is off and it has helped my Evo battery last longer. And I have GPS and any IM clients closed when not in use. Using kingsclick #10
Click to expand...
Click to collapse
same as you except I have GPS on, no navigation app running but GPS is on, weather updates every 3 hours from current location.
not much else

Did you disable perflock?

sitlet said:
Did you disable perflock?
Click to expand...
Click to collapse
No need to disable perflock with a custom kernel.

try not setting it so low. some phones respond poorly to this, and the battery drops like a stone.

[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

[Q] CM7 LauncherPro hang on boot

Just wondering if anyone else is having the same problem with CM7 and LauncherPro.
After rebooting, LauncherPro will hang for about 5-10 minutes before Android will force close it, or if I long-press the back key to manually force close it. It's only slightly annoying, since it functions properly afterwards, it would just be nice if there is a workaround or fix available so that I wouldn't have to do that after my daily reboot.

Sometimes it just happens, you may want to check you minimum frequency of your governor.

Min: 245
Max: 998
Governor: Conservative

You can try smartass...and what kernel are you using?

Yeah I am having the same problem. LP always forcecloses when I restart on RC4. Its not to annoying though.
Sent from my PC36100 using XDA App

Been happening to me since at least RC2, using stock kernel, minimum frequency of 384.
I'm pinging the devs to see if they know anything about it...

teh roxxorz said:
You can try smartass...and what kernel are you using?
Click to expand...
Click to collapse
Latest SavagedZen.
Conservative gives me the best battery life without sacrificing performance. From what I've read about smartass, I wouldn't like it.

Try setting memory usage to "high" in LP settings.
Menu>Preferences>Advanced Settings>Memory Usage Settings>Memory Usage preset>Select High.

Word from on high: We need some logcats. When I get home from work, I'm going to be flashing N35, no GApps, install LP, reboot, and then grab the log.
Hopefully that'll light some fires under people's arses. ;D

I have this issue as well.

Just chiming in that I too have this issue, also from about RC2.
Have used stock and Tiamat kernels, both exhibit the same behavior descibed in the OP.

I flashed Tiamat but the problem still exists, so I'm going to say it's either LP or CM7. Testing out the memory boost for LP now.

I have had this same problem with both my old Hero and now the Evo. LP Pro always hangs 1-2 min at bootup. Alternating between conservative, ondemand, smartass does nothing. I used CM6 on Hero, CM7 & Destroyer on the Evo.
Does not hang when I use SprintLovers.

jedijackie said:
I have had this same problem with both my old Hero and now the Evo. LP Pro always hangs 1-2 min at bootup. Alternating between conservative, ondemand, smartass does nothing. I used CM6 on Hero, CM7 & Destroyer on the Evo.
Does not hang when I use SprintLovers.
Click to expand...
Click to collapse
Yeah didn't hang when I had Sprint Lovers or Myn's Warm. Def points toward CM7 for me.

Sunsparc said:
Yeah didn't hang when I had Sprint Lovers or Myn's Warm. Def points toward CM7 for me.
Click to expand...
Click to collapse
Done think its cm7 either. I've had the issue on a few nightlies but set min CPU to 384 and fix permissions in rom manager and its gone away. Wifeys never complained about it on hers and she complains about everything

nate.spangler said:
Done think its cm7 either. I've had the issue on a few nightlies but set min CPU to 384 and fix permissions in rom manager and its gone away. Wifeys never complained about it on hers and she complains about everything
Click to expand...
Click to collapse
I'll try that out. The thing is, shouldn't the phone be running at full blast on boot? What would the min freq have to do with that?

Sunsparc said:
I'll try that out. The thing is, shouldn't the phone be running at full blast on boot? What would the min freq have to do with that?
Click to expand...
Click to collapse
If you have the "set on boot" option checked, then its running at whatever is set.

I unchecked "set on boot" and moved the min freq up to 384, no dice still hangs.

Well you'd have to re-check it after its reset. Are you using a custom kernel?

teh roxxorz said:
Well you'd have to re-check it after its reset. Are you using a custom kernel?
Click to expand...
Click to collapse
Ive used both SavagedZen and Tiamat. Using Tiamat at the moment.

proper way to use smartass?

i just flashed invisibleks .37 kernal with OMFGB (ran into some problems with CM7) and i was wondering the proper way to set up setcpu profiles with smartass (if needed at all)

Sorry. This should be in Q&A.....
Sent from my OMFGB powered hTc Incredible.

watt9493 said:
i just flashed invisibleks .37 kernal with OMFGB (ran into some problems with CM7) and i was wondering the proper way to set up setcpu profiles with smartass (if needed at all)
Click to expand...
Click to collapse
I ran OMFGB 1.1.1 for a long time before they screwed up 1.2(soooooo many errors), and really felt the need to have a lockscreen music controler(1.1.1 doesn't). I always ran 128/768, on 1.1.1 it should run perfect(I run chad's kernel though), just unlock slowly. If you want a faster unlock set it 245/768. Either one of those will get you really good battery life(128 being better obviously). If you are running 1.2, I highly recommend you set it atleast at 921(i think) or above as that just doesn't run as smooth. Also note the way smartass works, unless you want to kill battery life everytime you turn the screen on, try to set the max the lowest possible as it will sit as a frequency the phone feels it should run at without losing any speed(most of the time it's 1036 if you've overclocked). So unless you are just texting or calling, it's not bad, but any multitasking or big app using when the screen on, it'll jump way up.
I believe Chad is working on an ingenious kernel that tries to scale intelligently to what it is doing at all times so it'll save battery life not only when the screen is off, but also while the screen is on.

Can i set profiles or no? Like screen off, battery ones, and one temp one?
Sent from my OMFGB powered hTc Incredible.

watt9493 said:
Can i set profiles or no? Like screen off, battery ones, and one temp one?
Sent from my OMFGB powered hTc Incredible.
Click to expand...
Click to collapse
Oh, well, there is no point for a screen off one if you are using smartass on all your profiles. When it's not doing anything, it automatically scales down to the lowest setting possible(128 for best battery but slow unlock speeds or double clicks sometimes, 245 fixes those problems but using a fraction more battery).
I have a Normal profile(128/768), a Temp profile(245/614), just make sure if you are using GPS you manually scale it up some, my phone always ran like crap when Navigating anything less then 883, but everything, and I mean everything usually was fine at 768 on 1.1.1. If you are running 1.2 probably want to do 883 then 998 for GPS.

Been absent from the G2 scene, need suggestions.

Ive been using CyanogenMod for a while now and for the most part satisfied. Im running 7.0.3 and occasionally experience a few hiccups or oddities. For example, at work I will enable wifi. If I am out of range of the wifi for a while with it still enabled my phone will overheat and shut off. Sometimes wifi calling won't work. I had to restart my phone a few days ago because data wasn't working, but the icon appeared on the notification bar. I'd like to know what other ROMs I should try that may fix these annoyances. Also would it be worth checking out radios? Battery life is decent, but if theres a ROM i should try to get more battery life please recommend it. I can get 8-10 hours, about 1 hour total of tethering and wifi enabled for 5. I'm only overclocked to 1.2Ghz.

The 7.0.3 official is over a month old. Since then many improvements were made and bugs fixed, so I recommend the latest nightlies.
Regarding battery life, your max is 1.2 GHz but what is your min speed? Also, are you using an app like SetCPU or CM's built-in setting? What governor are you using?
Also, it probably makes more sense to post your questions in the official thread.

c00ller said:
The 7.0.3 official is over a month old. Since then many improvements were made and bugs fixed, so I recommend the latest nightlies.
Regarding battery life, your max is 1.2 GHz but what is your min speed? Also, are you using an app like SetCPU or CM's built-in setting? What governor are you using?
Also, it probably makes more sense to post your questions in the official thread.
Click to expand...
Click to collapse
min is 800mhz, governor is on demand. I wasn't aware they were still doing nightlies.

Ive been getting decent battery on Super CM7... just dont use setcpu

master.peterm said:
Ive been getting decent battery on Super CM7... just dont use setcpu
Click to expand...
Click to collapse
Is it SetCPU thats draining my battery? I'll try going tomorrow with it uninstalled. Any suggestions about my data? Sometimes I'll have to restart my phone after having wifi on for 5 hours to get my data to work. Sometimes my wifi calling doesn't work until I restart. Would flashing a radio mod work?

legato89 said:
min is 800mhz, governor is on demand. I wasn't aware they were still doing nightlies.
Click to expand...
Click to collapse
That's an unnecessarily high min, for sure that's one factor for why your battery life isn't so good. Current draw scales roughly linear with CPU speed, as seen in this study. I get by just fine having a 245 MHz min.
Also, SetCPU conflicts with CM's built-in settings if you have both "set on boot". Like master.peterm, I also prefer CM's built-in CPU controls over SetCPU.

legato89 said:
min is 800mhz
Click to expand...
Click to collapse
Why would you want 800MHz min? AFAIK that's the non-OCd max on the G2.
Unless you keep CPU hungry applications running all the time this is going to eat your battery away.