Develop Bugs

[Q] What's your Underclock frequency?

I've been testing the speed of my evo.
right now i've been underclocking for better battery.
i'm curious as to what you guys are setting yours to
and how it's affected the phone and how you use it
as well as the impact on battery life.

I OC to 1190 and get about 16-18 hours of juice.

bender1077 said:
I OC to 1190 and get about 16-18 hours of juice.
Click to expand...
Click to collapse
setcpu settings? kernel?
i'm using CM6 with kings kernel #2.

SETCPU attached thumbs.
Running BurntDroid 1.1 with Netarchy 4.1.9.1 CFS beta

nice! thanks. i'll give it a shot and see how my evo likes it.
thanks again

conservative
I really hate how sluggish and slow the Evo gets with scaling set to conservative.

dudewithnofood said:
I really hate how sluggish and slow the Evo gets with scaling set to conservative.
Click to expand...
Click to collapse
It's only noticable when you first wake the phone. After that it's smooth. I've had no other issue.

CM nightly, Snap 7.6 Turbo at 806 mhz ondemand yields decent performance.
I'm brand new to underclocking so I don't for sure of its effect on battery life yet.

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/

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

[Q] Any way to UV on Andromadus Beta 5?

Hi guys, I'd like to ask you a question about undervolting. I'm using Andromadus Beta 5 at the moment and it's working well enough for me, but under my rather heavy usage, my battery seems not to last that long. I'm already on the latest .19 radio and my CPU is clocked at 1GHz max with smartass v2 governor and 768 max conservative screen-off (with SetCPU).
I remember that when I was on GB (CM7.1) I used a slightly lower cpu voltage and everything was fine, so does anybody know if it's actually possible to edit the voltage table or whatever in order to UV my CPU on Andromadus?
Thanks in advance!

Don't bother, the Andromadus kernel already has somewhat low voltages. That said: https://twitter.com/rmk40/statuses/170239362020282369

Thanks for the answer. Actually the fact that undervolting the CPU doesn't bring any improvement in battery life seems a bit strange... I was hoping at least in a 5% increase. I also have to say that I have 3G and data always active, so probably that's the main reason of my short battery life.

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.