Develop Bugs

What is the best setting for SetCpu?

Guys! What is the best setting for Set Cpu? I need to conserve battery. My battery lasts about 12 hours. Im using a Reflex S 2.04 rom but i shifted to Leedroid 2.4.1. My settings are 768 On demand and 245 max 245 min on demand for powersave.
What is smart ass? How does it affect the system?

On SetCpu, I run overclocked 1200 till under 80%
Then about 80
700 at 70% battery
600 at 50%
I don't wish to run lower, as the desire gets a little wonky below 500mhz
3 profiles. I can get 3 days battery

I use no frills CPU - oc 1114, ondemand governor 245-1114.
Get about 12 he's heavy use, up to 2 days light. Today I have done 3+ hrs train journey with music, browsing and SMS, checked mail, now hanging about on this forum! 41% left.

All other governors are ****. Just use ondemand.
Im set at 128-1190 ondemand.
Sent from CM7

Meaple said:
All other governors are ****. Just use ondemand.
Click to expand...
Click to collapse
Why?
I use smartass @128-768 Mhz.

remember to use screen off feature (saves a lot of battery)

I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App

MatDrOiD said:
Why?
I use smartass @128-768 Mhz.
Click to expand...
Click to collapse
Because they don't work well. When you need CPU power they tend to lag and it takes that little extra longer which does my head in. Whether it's just me I don't know but it is so annoying. I have noticed it when playing games like RoboDefence. That's why I stick to ondemand because it actually works.

for the sleep off what is the best setting? screen off 245 max 245 min on demand? or 245 max 128min smart ass?

With smartass you do not have to set a profile for screen off. Smartass uses automatically the min cpu-frequency you set. So if you set smartass for screen off, you have two "screen off"-profiles. I think that could cause problems. You should set the screen-off-profile on [email protected] to avoid waking up problems, which can occur with this min 128 and max 245 for screen off-profile.

Meaple said:
Because they don't work well. When you need CPU power they tend to lag and it takes that little extra longer which does my head in. Whether it's just me I don't know but it is so annoying. I have noticed it when playing games like RoboDefence. That's why I stick to ondemand because it actually works.
Click to expand...
Click to collapse
+1 Agree totally
Ondemand is the only governor which doesnt make my phone lag.

westleydan said:
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
You can find this in the wiki...

westleydan said:
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
From SetCPU-Website:
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Click to expand...
Click to collapse
smartass governor – is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Click to expand...
Click to collapse
Source: http://www.ziggy471.com/2010/11/07/smartass-governor-info/

[Q] Setting clock speed to 800 -1200 mhz?

I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?

Deadly Sto(R)m said:
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Click to expand...
Click to collapse
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i read ondemand and conservative governors are od, so using interactive or smartass are better then using others. I will try min 368 mhz but am not sure if it works...

What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.

dhkr234 said:
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
Click to expand...
Click to collapse
First of all, I would like to thank you for your comments.
People don't do anything to access root if they don't want to mess device. I am one of them and want to have a device which both has performance and visuality. You offered me to not to change clock speeds. But we know HTC Desire Z is scheduled to work at 800mhz everytime (default). My opinion is just to set minimum clock speed to 800 mhz or something like this. If my device was burn by this clock speed, it was already dead.
Today i tried this clock speed (min 614, max 1382) and during the day it didn't heat up. Moreover, 8 hours passed, i played NFS for about 1,5 hour, made some call and 30 percent of battery left. It seems this clockspeeds doesn't cause battery drain or i couldn't feel it...
EDIT: 13 hours passes, 16 percent battery left (I made minimum 30 minutes of call)

GPU undervolt

Hello,
Just wondering if anyone has experimented with Tegrak Overclock Ultimate's GPU optimization settings. It allows you to undervolt the GPU. Has anyone tried this and is there any benefit to battery life savings with this? I am playing around with the settings right now, so I'll post my results later. So far been able to undervolt the 267 mhz step by -75mv from 1000mv down to 925mv (900mv is unstable for me). And I undervolted the 160 mhz step by -150mv from 900mv down to 750mv. There is also a 200 mhz step I haven't played with. Perhaps keeping the GPU at 200/160 can yield potential battery savings when playing games because games drain the battery so fast.
Hm. I seem to be able to undervolt the 200 mhz step to 750mv as well. I'm going to run a 200/160 gpu setup at 750mv and see if I can save any battery playing Gun Bros and will let you guys know.

caaznkid said:
There is also a 200 mhz step I haven't played with. \
Click to expand...
Click to collapse
Really? I only have the 267 and 160 MHz clock settings available. Any thoughts anyone?
Oh, I have underclocked my GPU settings but only by a modest 25mV each.

There's only 2 steps, but u can change the clock between 160, 200, and 267

yep ... good results
Yep I've been experimenting with GPU undervolting and had some sucess. So I was methodically working downwards and testing stability... then i saw this thread and thought what the hell, right? I shot for lowest mv of 750 and it's rock solid at 200mhz.
Can confirm 750mv stable at 100, 134, 160 and 200mhz. 267mhz can't be undervolted that much.
I've locked 200mhz 750mz for both speed steps and left it at that. Phone has yet to display any instability in a couple of days of mixed use including gaming. Battery life better? Subjectively yes, mostly I notice phone doesn't get so hot playing Dead Space.
Power consumption scales down almost linearly with clock cycles, and exponentially with voltage (right?). So by my math GPU is using about 40% of the power it does at full 267mhz. I wonder what the TDP of the exynos 4210 is and how much the Mali 400 contributes to that, would give some idea of what battery life to expect. Since GPU sits idle a lot, I doubt it's a magic fix.
Such is the power of our phones I have to underclock the CPU and GPU quite far before any 3D game gets too choppy to play. 160mhz is more than fine for most.
Usually undervolting makes the most sense for power saving because a given computing workload takes a certain number of cpu cycles. But 3D usually tries to render as many frames as it can, with the exception of S2's 60fps frame cap. So slowing down the GPU to no more than you need might improve gaming battery life?
My SGS2 is a bit sensitive to undervolting although underclocking of CPU, so I'm happy be able to so agressively undervolt the GPU.
I'd be interested to know who else can just set 200mhz & 750mv and have it rock solid? If not, 200/800 or 160/750?

I've rarely had problems when I use Tegrak. Then again, I undervolt 100mv on my cpu between 200-1000mhz, and about 50mv on my GPU at 267mhz with the noop scheduler and tweaks enabled. If I can get Tegrak to work with the Gunslinger kernel (currently causes reboot loops when I load the overclock module), I'll report back on battery life with Tegrak and experiment a little more.

jyaworski said:
I've rarely had problems when I use Tegrak. Then again, I undervolt 100mv on my cpu between 200-1000mhz, and about 50mv on my GPU at 267mhz with the noop scheduler and tweaks enabled. If I can get Tegrak to work with the Gunslinger kernel (currently causes reboot loops when I load the overclock module), I'll report back on battery life with Tegrak and experiment a little more.
Click to expand...
Click to collapse
I had the same problem with Gunslinger, I decided to keep my phone on Rogue Stock EL29.
I've been able to drop my GPU Level 0 Clock to 160mhz and voltage to 850mv with out any issues.
I also keep my GPU 1 Clock at 100mhz and my voltage at 750mv without a problem.
Using noop of course.
Changing GPU clocks and volts doesn't help much.
Keeping your CPU Internal Voltage and Core Voltage -50mV and keeping it scaled 200-800 MHz will give you much better battery.

I think the effect would be more significant in ICS since ICS use GPU to render UI

700 MHz vs 350 MHz minimum CPU setting, which one is better for battery life?

According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.

350mhz.
700mhz minimum is not more efficient.

Vangelis13 said:
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
Click to expand...
Click to collapse
for francos kernel it might be the case...not others

I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.

ArmanUV said:
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
Click to expand...
Click to collapse
I've read that ondemand is more power-hungry than interactive...

anton2009 said:
I've read that ondemand is more power-hungry than interactive...
Click to expand...
Click to collapse
Interactive has less in between steps and is quicker to jump to max
Sent from my francoPhone

Franco uses 700 because of the wake lag caused by 350 when using hot plug mod (shutting off cpu1)
Sent from my Galaxy Nexus using xda premium

With 350 or 700 I still get wake lag.

i'm on franco's latest and hotplug is on and my cpu gov is set to conservative and min freq is 350mhz. no lag on waking at all..

180
Vangelis13 said:
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
Click to expand...
Click to collapse
I'm using 180 in imoseyon's Leankernel experimental builds.. works amazing, telephone spends 70% in this state on average, at 180 undervolting at 875mV.

ArmanUV said:
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
Click to expand...
Click to collapse
The cpu may idle in a low power state, but it does not shut down. How can the phone run if the CPU stops running? There is no secondary system that intervenes to start the CPU back up.

adrynalyne said:
The cpu may idle in a low power state, but it does not shut down. How can the phone run if the CPU stops running? There is no secondary system that intervenes to start the CPU back up.
Click to expand...
Click to collapse
that's what I meant. my point is that power consumption in idle state doesn't depend on the min frequency.

But it matters every time your phone wakes up, even if its momentarily.

Only get lag and signal loss when on 350. 700 seems to give me the best sleep and wake time with no lag. I had to learn the hard way. But figured out from reading around that 350 causes some problems on any kernel/governor.
Sent from my Galaxy Nexus using XDA Premium App

The only time 350mhz gives troubles is if you set the min/max to it for sleep.

ChongoDroid said:
Interactive has less in between steps and is quicker to jump to max
Sent from my francoPhone
Click to expand...
Click to collapse
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
ArmanUV said:
that's what I meant. my point is that power consumption in idle state doesn't depend on the min frequency.
Click to expand...
Click to collapse
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.

Actually, stock kernel, onDemand is garbage, and Interactive is best.

EniGmA1987 said:
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Click to expand...
Click to collapse
You're absolutely right, I had em backwards lol
Sent from my Galaxy Nexus using xda premium

Same here.

EniGmA1987 said:
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Click to expand...
Click to collapse
it's not as simple as that. when the screen is off the phone enters deep sleep as much as possible which uses (almost) the same power regardsless of min frequency. The phone obviousely will wake up from deep sleep from time to time and that's when the minimum frequency comes into play. For example, for someone who has a lot of applications syncing every few minutes or someone who listens to music a lot with the screen off (which prevents deep sleep), setting the minimum to 350 will be better. Otherwise, the savings are negligible.
This was put to test by someone here on xda (the gnexus general section) by measuring voltage and current through the battery in different conditions.

Undervolting - good idea or not?

I'm wondering if anyone's undervolted and to what values.
I'm also wondering waht the deafult values are and if they change per kernel.
Is there a way to disable SetCPUs undervolting settings?
Has anyone improved battery life with profiles? On the Eris this was the only way to get usable battery life.

Or not. I gave up undervolting after I actually compared battery life at stock values vs undervolted (on my old phone, sgs4g) and discovered it does nothing for battery life.
Edit: undervolting "might" marginally increase standby battery life, but considering how good this phone already does... it certainly won't increase actual screen on usage.
Sent from my Galaxy Nexus using xda premium

Depends how low you under volt. Got more battery life, maybe about an hour, after finding optimal battery life on my gfs Gnex.
If you don't under volt correctly, of course it won't improve battery life.
From my sexy white, Nocturnaled HTC One X

If you're not overly comfortable with undervolting, then using one of the many kernels with Smart Reflex will do a mild undervolt for you. If you are comfortable, then the only way to find numbers good for your phone is to try and test. I tweaked mine down to the point that I was occasionally getting hot boots when the screen was off and media was playing. Tweaking the numbers back up added the needed stability. Even little things like kernel or ROM revisions can change what voltage is or isn't stable. Another example is that when I updated my Jellybro CM10 version the other night, along with updating leankernel from 4.1.0exp3 to 4.2.0, I had to increase a few of my voltages to avoid hot boots.
Just for example numbers, here are mine:
Code:
1350MHz -- 1200mV
1200MHz -- 1150mV
920MHz -- 1050mV
700MHz -- 950mV
350MHz -- 825mV
These numbers will vary from device to device and even between ROM/kernel combinations, so don't use them as hard fact.

Thanks. On a phone like this it might not make a huge difference but on the Eris (Where stock battery life could sometimes be 6 hours if you actually used your phone) an undervolted kernel with setcpu could turn those 6 ours into 48.
Thanks Cilraaz, I'll try those voltages out and benchmark a bit to see if they're stable for my system.

Two things I can say for sure:
1. you will have very limit battery gain by undervolting with Gnex, no matter how low you try.
2. undervolting will bring some stable issue if you get too low, like lose signal and reboot.

I am using Kernel Franco GPU 384 Stock rom on my 4.1.1 and did undervolting
Current configuration:
384Mhz
950mv
------------
729Mhz
1050mv
-----------
1036mhz
1125mv
----------
1228mhz
1275mv
-------------
I did not change the frequencies of overclocking, because I'm not using them.
I felt an improvement in battery consumption unless the unit is heating up.

Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.

I've read many times undervolting isn't worth it.

Hungry Man said:
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
Click to expand...
Click to collapse
I'm using the following with SetCPU: default (1350MHz-350MHz), charging, CPU temp > 64, and battery < 35%.
If you're using a kernel and governor that support hotplug, then you likely don't want to use a screen off profile. The combination of the two can tend to cause sleep-of-death or hot boots.
I Am Marino said:
I've read many times undervolting isn't worth it.
Click to expand...
Click to collapse
Most people don't want to spend the time to do it right.

I'm actually not used to the new kernels. I haven't messed with my eris in about a year and back them there was "smartass, on demand, performance," and some other one that clocked down instead of up
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.

Hungry Man said:
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Click to expand...
Click to collapse
Hotplug disables one of the CPU cores when the screen is off. Some governors, like hotplugx, will also attempt to disable a CPU core during periods of low CPU usage. For some reason, this combined with a screen off profile can cause some problems. I assume it's because of the "screen-off-max-freq" that Imoseyon mentions in the quote below.
Personally, I prefer the interactivex governor with leankernel by Imoseyon. From his kernel thread:
With interactiveX V2 (for gnexus), things are a bit different, since gnexus has built-in support for screen-off-max-freq for all its governors. I took the new interactive code in gnexus, added early_suspend support (screen off/on trigger), and then added logic to the code so the governor uses the phone's built-in hotplugging capability to turn off cpu1 when screen is off (and then turn it back on when screen comes back on). Cpu1 goes offline entirely - no idle, no sleep.
Click to expand...
Click to collapse

I think undervolting helps - my phone is running 728 - 1228 using the interactive governor, with voltages of 600 mV, 700 mV, and 800 mV (728 MHz, 1036 MHz, 1228 MHz respectively) and I haven't had any issues so far. I know there are some reports that say undervolting doesn't help much, but those are when people undervolt by like 50 mV, whereas here I'm going like 400 mV under lol. (Yes, smart reflex is off).

Thanks Cilraaz. Good to know.
So turning the screen-off profile could improve things? Honestly, my system does fine at 350mhz with screen off. Turning a core entirely off would probably help though.
If I use hotplugx governor that would disable one core when the screens off, right?

Hungry Man said:
If I use hotplugx governor that would disable one core when the screens off, right?
Click to expand...
Click to collapse
Hotplugx will disable a core when the screen is off or when there is low system load. Depending on your kernel/governor choice, other governors may do it also. On leankernel, for instance, interactivex will disable a core when the screen is off, but not on low system load.

Ok, thank you.
I haven't done any comparisons of before/ after since I undervolted/ underclocked first thing. But I was browsing for hours while listening to music while talking to a friend with GTalk. talked for about 1.5 hours with someone, Left it on overnight (10 hours), woke up, used it to talk (voice to text) to someone via GTalk, and it's 3:25PM right now and I still have a fair amount of battery life left.
I'd heard mixed things about the battery on this so I'm happy.
My voltages:
1650: 1300
1520: 1250
1350: 1175:
1200: 1125
920: 1000
700: 925
350: 900
I stress tested each one without a crash.