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
Related
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
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
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.
Hi,
I was wondering if there was any effort to port the following governors to the Defy for CM7?
SmoothAss,
LagFree,
SmartassV2
I ask because I am using Smartass now and while it is great for the battery life(especially when you undervolt), it isn't as responsive when it needs to wake up on a call (screen stays black for 2-3 rings), and phone call processing can be kind of choppy when using HSPA (3G connection). Also sometimes the Mp3 playback skips when background data process goes off, or tower coverage changes.
---
I have seen SmartassV2 on Motorola DEXT and it rocks. 2 Days use worth of average phone use without charging.
Thanks in advance all.
tsurerb now
Any word on feasibility? Is this the wrong place to post this? I seem to have solved some of the problem by putting the first cpu setting at 400mhz. But it is apparent that the cpu never ramps to the second setting of 600mhz. I hear the newer governors solve these issues.
hi, dunno about supporting smartassv2, but you can set smt_sleep_max_freq to your clk2 speed, so in sleep smartass dont limit your defy to 300mhz. You dont be "saving" the batery charge like the smt_sleep_max_freq = clk1 but i think it will be better than having 400mhz in clk1
Using trinity kernel, using set CPU to make a profile for when I use navigation to limit CPU to 1026 MHz, but after coming out of navigation, the second CPU won't go to sleep until I reboot the phone. Anyway to fix this? I'm using ondemand/deadline.
So I guess I've discovered that if you change the frequency at all in setcpu, this causes CPU 1 to not go to sleep until you reboot.
stevessvt said:
So I guess I've discovered that if you change the frequency at all in setcpu, this causes CPU 1 to not go to sleep until you reboot.
Click to expand...
Click to collapse
This depends on the governor you have set, the kernel you have installed determines which governors you have access to. SetCPU homepage help: "hotplug: Available with some multi–core systems. Similar to ondemand, but turns additional cores off when they're not being used."