Hello everyone,
I just rooted my MT3GS last weekend its been running very smoothly with TeamFenix 1.7. However I have a quick question when it comes to setCPU.
Now I am not running the OC kernal right now I'm still taking advantage of the stock clock of 600MHz.
I remember that it was asking for a .txt file for configuration but does anyone have this file can point me exactly what to do. Right now I have it set onto "on demand" and enabling profiles.
EX
100-50% battery 600MHz MAX 600MHz MIN.
49-40% battery 480MHz MAX 245MHz MIN.
39-0% battery 480MHz MAX 122MHz MIN.
I want this thing to be fast as can be for a majority of the time. Any help would be nice.
its best to set it to auto detect and put it on max and just setup a profile for "screen off" and have it set to lowest without crashing
Set screen off to 245/245 this will help with battery life. I'm using the 768 oc kernal and the only profile I use is screen off.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Related
Is anyone using SetCPU with the new Froyo? I just downloaded it from Marketplace and have a question. It disabled the perflock and I lowered the mhz to 806. If my intent is to get a longer battery life did I do the right thing? It was running at 998 so I'm thinking that my lowering it I'll slow down the processor and in turn give myself a bit more life in the battery. Is that right? Thanks in advance.
Sent from my incredible Droid Incredible using the XDA app
Disabling perflock shouldn't scale it down. Did you set it to automatically detect setting when you first started the app? If not, you should. (Might have to re-install)
Yeah it auto detected a min of 245 and max of 998. I couldn't change the max whether setting to user, ondemand or performance without disabling the perflock. Once I disabled that I was able to scale the max level down.
Sent from my incredible Droid Incredible using the XDA app
setcpu was causing too many crashes for me on Froyo leaked 8-01-10.
I uninstalled it for a refund.. even when it did work for me.. I didn't notice any major battery savings.
ive noticed slight battery savings with setcpu. biggest thing ive noticed is the charge time. with a set profile to run the cpu @ 245 when screen is off the phone will charge the battery to 100% from dead in just about an hour and half. and the standby time increases running that profile as well.
I have setcpu running on desire with neophyte v1.2 ROM. It was running perfectly until I put it to charge overnight while sleeping.. when I woke up, the display shows that the phone is running at max speed constantly when it was set to "ondemand". I also have a profile with 245 min/max when screen off but when I wake up after 8hrs, I go to the info tab, I see that my phone is spending more time on max speed than 245 which doesn't make sense because the phone has majority of time with screen off..
What am doing wrongly here?
Sent from my HTC Desire using XDA App
webber2109 said:
I have setcpu running on desire with neophyte v1.2 ROM. It was running perfectly until I put it to charge overnight while sleeping.. when I woke up, the display shows that the phone is running at max speed constantly when it was set to "ondemand". I also have a profile with 245 min/max when screen off but when I wake up after 8hrs, I go to the info tab, I see that my phone is spending more time on max speed than 245 which doesn't make sense because the phone has majority of time with screen off..
What am doing wrongly here?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
need help....
what other profiles do you have?
i have 2 profiles.
one is 245 min 245 max when screen off (priority 100)
the other is 245 min 998 max when charging or full when charging (priority 50)
did i do anything wrong?
Has ur SetCPU got granted by SuperUser?
lpachuong said:
Has ur SetCPU got granted by SuperUser?
Click to expand...
Click to collapse
yup it is. in fact it was working properly until i leave it to charge. i tried uninstalling and re-installed but still it clocks at 998. the sleep profile doesnt seem to work well too
Try using a different ROM.
I experienced the same with the other ROMs when using the ondemand governor. I'm now using Nextsense 5.3 and the kernel allows "interactive" governor in SetCPU and my CPU speed stays at the lowest limits when idle.
amf said:
Try using a different ROM.
I experienced the same with the other ROMs when using the ondemand governor. I'm now using Nextsense 5.3 and the kernel allows "interactive" governor in SetCPU and my CPU speed stays at the lowest limits when idle.
Click to expand...
Click to collapse
do u have any profile for screen off? does it work?
from the info tab, i see my phone spent more time on max speed than min even though most of the time the screen is off
webber2109 said:
do u have any profile for screen off? does it work?
from the info tab, i see my phone spent more time on max speed than min even though most of the time the screen is off
Click to expand...
Click to collapse
Yup it works. Screen off profile--> Max=384 // Min=245
Try a ROM that supports interactive governor.
EDIT:
My "Time in State"
245 = 1352167
998400 = 18389
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
Does anybody know what the ondemand governor uses as it's default screen off settings. By that I mean if I have profiles disabled in setcpu and just allow the ondemand governor to determine frequencies and I leave the max min freq's at default values, then what happens when the screen is turned off?
I know the cpu will eventually go into deepsleep but there are inconsistencies.
If I dont use setcpu and just allow the default kernel settings (im on doomlords btw) to determine the frequencies, then when I turn the screen on after leaving the phone for a while, the cpu speeds up very quickly and the system becomes responsive before I can ever notice.
If I use setcpu however, with a screen off profile set to ondemand, max 245, min 120, then it still takes achieves deepsleep as often as not using setcpu but there is a noticeable lag and stutter for about 5-10 seconds as I turn the screen on to use it again.
Does anyone have any idea;
A) Why this happens?
B) What is the default screen off behaviour for the ondemand governor on doomlords kernel.
you may need a program like system monitor to record your % of cpu activity, im on stock rom and i have it at 100 - 300 mhz max when screen off, i used the program while im asleep to see if there was issues but there was none or lag when the screen turned on
there isnt any inconsistency with mine,but then again i removed alot of the programs i dont use to have very few programs running in the background,playing music with this setting doesn't cause issues
i havent read alot into his kernal yet,guess you wait till someone that has more knowlege in his rom.
[v03 onwards] added new CPU governors:
InteractiveX
Savaged-Zen
SmartAssV2
Hi all, first post here at xda, am fairly new to android devices and am wondering if someone could share some knowledge please? After installing my first Rom (m1ndh4x3r 2.3.5) I haven't been receiving any calls... A friend today said I may be underclocking the phone too much for it to wake on time to ring? Had it set at 200mhz with screen off. After setting it to 480mhz I received a call straight away, question is, have you had this problem too and what's the lowest setting advised that I can have it on please?
Thanks in advance for any help/advice
Your phone is built to run at 600 MHz. Not at 200. You can use apps like setcpu and no frills cpu control to control your phone. These apps let you set the minimum and maximum value of the cpu frequency. You should let it run at its full capability. Optimal settings would be something like
Min: 320
Max: 600
Governor: smartass2
You can underclock more when you are not using it or not expecting calls ( in the night).
You can also set your minimum to 120 MHz, but usually, it'll go into deep sleep mode, rather than stay on 120 MHz. Also, when listening to music, I've noticed, it stays on 320 MHz.
My minimum setting is 120 independently from which ROM (i tried 5 ROMs) I use (3month use = 0 problems).