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/

Frequency of cpu

A lo of galaxy Nexus users use the freq 729/1*00. Why?
Inviato dal mio Galaxy Nexus con Tapatalk 2

? not sure what you mean
some kernels have the ability to change frequency, but most have a range of 320-1320. using the lower frequency saves battery

StormIceX said:
A lo of galaxy Nexus users use the freq 729/1*00. Why?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
I don't know why they would clock it that high for minimum freq unless they like low battery life or is using a 4000mAh battery.
I use 192/1024 with the 'conservative' governor.

The CPU is one of the most power efficients components on smartphones and most frequency/voltage tweaks don't go beyond the placebo zone. Your priority for a reasonable and enjoyable use should be performance, since undervolting/underclocking doesn't really do much as far as battery goes.
Just take a look at an application like CPUSpy and see how much time your phone spends at the highest frequencies.
For most governors, state time at max frequency is well under <10% of the total time and the difference of voltages is around 300 mv (from ~900 to ~1200 mv at max frequency) so, in my opinion, battery savings obtained by using a lower max frequency are minimal, if existant. On the other hand, it does have a performance hit. Therefore, I use 1350 mhz as max frequency; I would use a higher one but I find it to heat up the phone quite a bit while using it.
Now, there are things that actually influence battery. The screen is by far the biggest battery hog. By using autobrightness (and tweak it to lower levels through CM9) I find that you can get a really good balance between power savings and readability.
Another significant battery hog is a persistent data connection (in my case HSPDA/3G). If you take the time to set the phone to 2G during idle periods you also get a nice battery saving. Wi-Fi isn't really a variable to me because I find it to have a really low idle drain.
You can also try to turn on Airplane Mode when you go to sleep (only if you don't charge it during sleep, that is), because it has a very low idle drain and it's perfect to keep juice for the next day.
Hope some of my tips follow through!

It is known that using a higher min freq saves battery because it takes less time for the cpu to complete the tasks it has been asigned to do.
Others think that they dont get signal drops if they dont use 350 step, when it probably happens because of insuficient voltage.
Sent from my Transformer Prime TF201

bk201doesntexist said:
It is known that using a higher min freq saves battery because it takes less time for the cpu to complete the tasks it has been asigned to do.
Others think that they dont get signal drops if they dont use 350 step, when it probably happens because of insuficient voltage.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
I agree. I get 5-7h screen on time and i have 729mhz min freq. 2000 mah battery.

jnr21 said:
I agree. I get 5-7h screen on time and i have 729mhz min freq. 2000 mah battery.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get 4:30 hours with 350/1200 and wheatley governor platino with fpse, riptide gp and Temple run about 1:30h, 3g on, Facebook and tapatalk. No undervolt. If i set 749/1200 i can have more screen on time?
Inviato dal mio Galaxy Nexus con Tapatalk 2

StormIceX said:
View attachment 1100575
I get 4:30 hours with 350/1200 and wheatley governor platino with fpse, riptide gp and Temple run about 1:30h, 3g on, Facebook and tapatalk. No undervolt. If i set 749/1200 i can have more screen on time?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
Dunno, every phone is different.

If you used a higher minimum frequency you would enhance the race to idle process (deep sleep). Unfortunately I don't think anyone knows where the cutoff is, since it's a balance between frequency, voltage and task load which is hard to objectively measure and therefore calculate the optimal frequency.
In my experience, 700 mhz is just fine for minimum frequency as well, without any noticeable impact in battery (for the better or the worse). It has one downside though, which are low power continuous tasks such as listening to music in which you'll keep your phone awake at 700 mhz when you could do the same task at a lower frequency. On the other hand, a minimum frequency of 700 mhz does make the phone smoother when waking up, etc...
My personal belief is that you should pick the frequencies according to the governor you're using. In conservative, a minimum of 700 mhz is a good idea. In interactive, specially in some custom kernels where it scales more agressively (CMPlus, Leankernel, for instance), you can keep a minimum of 350 mhz without any impact on performance. In wheatley (Ezekeel), I really don't know since it potentiates the use of C4 states which I don't completely understand, but Ezekeel is so smart that you might as well just trust his defaults blindly
About signal drops, as bk201doesntexist mentioned, it's probably fixable by increasing the voltage at the minimum frequency (disabling smart reflex). I used to have that issue with smartreflex on, but it was fixed in the last update. YMMV.

I run my min at 192 and my phone never lags never slow and still deep sleeps within like 10 seconds of screen off. Honestly its whatever you like I believe. I see no difference is smoothness or performance with it at 192 or 700.
Sent from my Galaxy Nexus using Tapatalk 2

Gahh Its Lee said:
I run my min at 192 and my phone never lags never slow and still deep sleeps within like 10 seconds of screen off. Honestly its whatever you like I believe. I see no difference is smoothness or performance with it at 192 or 700.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You don't see it because it's unlikely that when the screen is on your phone ever falls back to 192 mhz, since the minimal task would exceed the load threshold for that step (depends on the governor ofc). Probably the only diference you'd eventually notice would be a slow wake up or some jitterness in the first one or two seconds.
On the other hand, with a 700 min you can notice in an app like CPUSpy that the phone rarely spikes to the maximum frequency because 700 mhz can handle most loads effectively.
I personally don't believe in battery optimizations just by undervolting/underclocking, it's just too minimal of a effect for an already very efficient component...But it's a fun discussion nonetheless
---edit
CMPlus @ Interactive Governor
Use Profile: mostly idle, lots of background music listening, ~2 hours of music in the bg, ~1h of screen on time
You can see that the maximum frequency is hardly a variable here since it only occupies a mere 7 minutes in over 70 hours. The true "muscle" is the 700 mhz slot, that buffers most of the load instead of jumping to the highest frequency (which it still does, but for a very short amount of time)

better performance,better battery life and no data drops
Sent from my Galaxy Nexus using xda premium

dreamhunterr said:
You don't see it because it's unlikely that when the screen is on your phone ever falls back to 192 mhz, since the minimal task would exceed the load threshold for that step (depends on the governor ofc). Probably the only diference you'd eventually notice would be a slow wake up or some jitterness in the first one or two seconds.
On the other hand, with a 700 min you can notice in an app like CPUSpy that the phone rarely spikes to the maximum frequency because 700 mhz can handle most loads effectively.
I personally don't believe in battery optimizations just by undervolting/underclocking, it's just too minimal of a effect for an already very efficient component...But it's a fun discussion nonetheless
---edit
CMPlus @ Interactive Governor
Use Profile: mostly idle, lots of background music listening, ~2 hours of music in the bg, ~1h of screen on time
You can see that the maximum frequency is hardly a variable here since it only occupies a mere 7 minutes in over 70 hours. The true "muscle" is the 700 mhz slot, that buffers most of the load instead of jumping to the highest frequency (which it still does, but for a very short amount of time)
Click to expand...
Click to collapse
Actually my 192 was in use over twice as often as Max or anything else but I'm gonna try 700 since I was at 1350 for 25% of my time awake.
Sent from my Galaxy Nexus using Tapatalk 2

dreamhunterr said:
You don't see it because it's unlikely that when the screen is on your phone ever falls back to 192 mhz, since the minimal task would exceed the load threshold for that step (depends on the governor ofc). Probably the only diference you'd eventually notice would be a slow wake up or some jitterness in the first one or two seconds.
On the other hand, with a 700 min you can notice in an app like CPUSpy that the phone rarely spikes to the maximum frequency because 700 mhz can handle most loads effectively.
I personally don't believe in battery optimizations just by undervolting/underclocking, it's just too minimal of a effect for an already very efficient component...But it's a fun discussion nonetheless
---edit
CMPlus @ Interactive Governor
Use Profile: mostly idle, lots of background music listening, ~2 hours of music in the bg, ~1h of screen on time
You can see that the maximum frequency is hardly a variable here since it only occupies a mere 7 minutes in over 70 hours. The true "muscle" is the 700 mhz slot, that buffers most of the load instead of jumping to the highest frequency (which it still does, but for a very short amount of time)
Click to expand...
Click to collapse
I think the bigger question is.. how did you only touch your phone for an hour out of 70?
Sent from my Galaxy Nexus using xda premium

joshnichols189 said:
I think the bigger question is.. how did you only touch your phone for an hour out of 70?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Well, a total of 1 hour of screen on and 2 hours of music in the background and some phone calls lol.
It's simple, I'm studying at home and I do most of my web stuff on an iPad 3 which I've recently bought. In retrospective, if I had known I was going to buy an iPad 3 I wouldn't have invested this much on a high end Android phone

dreamhunterr said:
Well, a total of 1 hour of screen on and 2 hours of music in the background and some phone calls lol.
It's simple, I'm studying at home and I do most of my web stuff on an iPad 3 which I've recently bought. In retrospective, if I had known I was going to buy an iPad 3 I wouldn't have invested this much on a high end Android phone
Click to expand...
Click to collapse
Your nexus just called me..
she's sad you've replaced her haha

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.

Setcpu Profiles

Hey guys, I'm just wondering what settings do you have on your setcpu for the best performance and battery life? I'm totally new to this lol
Sanks

kazemagic said:
Hey guys, I'm just wondering what settings do you have on your setcpu for the best performance and battery life? I'm totally new to this lol
Sanks
Click to expand...
Click to collapse
i i think that ondemand is the best for daily using... i'm using cm10 rom and i have some music problem so i'm using interactive and it's ok. if you don't use games or heavy apps, you can underclock it to 1ghz or even less and put on powersave.. but you have to try and find the best for you

My setup is a little complicated. I use the ondemand governor, then for the profiles I make it use powersave and under 760mhz between 1am and 8:30am which seems to really help during the night. Also set it to use 760mhz max when the screen is off.
When charging or above 40% battery I allow it to run full speed, but only when the screen is on, therefore helping charge times. On charge or above 80% I set the governor to performance.
In call I set the clock to max 1000mhz and conservative to try and allow calls on low-battery to work properly without lag but also without killing the battery.
I have a couple of other options set for very low battery ( < 12% ) too, but those are only to extend the battery if it's dying.
I wouldn't say all this is necessary... but I need my phone to keep working at all times as I use it for receiving business calls.
It's just a matter of playing around really... depends what you use the phone for. For the most part tell it to use lower clock speeds when you don't need them so much (when phone is off, during the night, during call etc) but you will really notice the speed difference if it's underclocked while you use it, so I tend to allow it to use full whack when screen is on, unless the battery is low.
I also set up profiles to make things like Bloons TD4 run in performance mode and min of 1000mhz, to keep them smooth . Drains the battery though!

lol setcpu does a really good job at battery saving. When using ondemand, my phone can last more than 2 days (if it's on standby)
Have you guys tried under-vaulting? What does it rlly do?

kazemagic said:
lol setcpu does a really good job at battery saving. When using ondemand, my phone can last more than 2 days (if it's on standby)
Have you guys tried under-vaulting? What does it rlly do?
Click to expand...
Click to collapse
If you mean decreasing the voltage on the CPU, no I haven't. From my experience in desktop PCs however, if the CPU voltage is too low it can lead to hardware issues and instability.
If something needs a certain amount of power, and you give it less, it will either try and draw more amps which increases heat and can fry components, or won't work properly. You could probably "under-volt" the CPU at the same time as reducing the clock speed however, but your performance will suffer. When the processor is set to be ondemand it underclocks itself when not in use anyway
The biggest battery drain is screen and radios, concentrate on using them less. Underclocking the CPU will make the phone last longer when in use, but usability will suffer and turn your super fast smart phone into a sluggish one. I only make mine stay underclocked when the screen is off, during a call, or on low battery. During general use I let it do its thing .

UV(Under volt) is actually not to bad. Don't ever set those values at boot, else when they are too low, it will cause BOOTLOOPS. It just reduces the amount of power allowed for the cpu to use, thus it won't use more than required. You can't really ask a person for his/her uv values, as no 2 chips are created equal.
People stating that they UC(underclock) their device is not quite right. We don't have much control over our cpu's to be honest. If you run tegra stats whilst using you're phone, you'll see what I mean. It will sometimes(happens quite often) just bump up to higher frequencies to which you UC them. Also as soon as the screen is locked and unlocked the max cpu frequency set by the governor will just return(for example: say stock is 1500mhz, and you set it to 1400mhz, it will return to 1500mhz after an unlock). Ondemand is very very good for battery and performance. But remember you have to tweak those values individually in order to optain the best possible performace for the given task you want. Whether it is for battery or performance.
It's actually also a lot better to just tweak those values as to TRY and uc. Uv will stick, UC not!
Here is a small example as to battery saving and performance values for ondemand governor:
sampling rate:---------60 000 ----- 30 000
up threshold:--------------95 ----- 60
sampling down factor:-------2 ----- 8
powersave bios: ------------3 ----- 0
ignore nice load:------------0 ----- 0
io is busy:------------------0 ----- 0

Undervolting results

Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?

neustadt said:
Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?
Click to expand...
Click to collapse
Did you set difference voltages for every frequenzy or did you use the two buttons at the top and lower every voltage the same? My device crashes if i go -200. My max freq. is 1566 and my min. freq. is 162. As governor I use smartmax and I/O scheduler is fiops I also underclocked my Gpu to 192 Mhz.

Not yet. I want to find a working global value and then tweak at 162MHz and 700MHz.
Did you limit your max frequency at 1566?

Flatric said:
I also underclocked my Gpu to 192 Mhz.
Click to expand...
Click to collapse
What app did you use for that?

neustadt said:
What app did you use for that?
Click to expand...
Click to collapse
Yes I limtited it at 1566, I used also Kernel tweaker to underclock my Gpu

Flatric said:
Yes I limtited it at 1566, I used also Kernel tweaker to underclock my Gpu
Click to expand...
Click to collapse
Oh, ok. So you limited your max gpu clock. Maybe I will try this out as well. But I would need to find out how far I can go down. Usually I dont play any games so I probably dont need the highest clocks on my gpu. But I do watch the occasional HD video.
In the end it might not help save batterylife, if my GPU doesnt clock that high anyways.
I would rather like to adjust the different speedsteps of the gpu just like on the cpu. ExTweaks looked processing, but doesnt seem to work with f4ktion kernel.

neustadt said:
Oh, ok. So you limited your max gpu clock. Maybe I will try this out as well. But I would need to find out how far I can go down. Usually I dont play any games so I probably dont need the highest clocks on my gpu. But I do watch the occasional HD video.
In the end it might not help save batterylife, if my GPU doesnt clock that high anyways.
I would rather like to adjust the different speedsteps of the gpu just like on the cpu. ExTweaks looked processing, but doesnt seem to work with f4ktion kernel.
Click to expand...
Click to collapse
Please tell me your result if you finished

neustadt said:
Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?
Click to expand...
Click to collapse
I don't understand what you are trying to prove with wrapping your device in a winter pullover while undervolting.
When I have to apply tests at my job for simulating mobile applications, we undervolt (the solenoid of a valve) -30% and do test at very low temperature of -25'C. Then we overvolt with 30% and run '100% duty cycle' test at high temperature of +70'C. At low temperature there is a chance of not reacting anymore, at high temperature it is the latter: the coil could be toast since it can't radiate all the generated heat away.
With the undervolt test, you should put your phone in the fridge or freezer to really seeing it's behaviour at extreme circumstances. In my opinion you are now easing the pain on your phone during undervolting, by heating it from 2 sides, by charging and heat insulating it.

jake3317 said:
I don't understand what you are trying to prove with wrapping your device in a winter pullover while undervolting.
When I have to apply tests at my job for simulating mobile applications, we undervolt (the solenoid of a valve) -30% and do test at very low temperature of -25'C. Then we overvolt with 30% and run '100% duty cycle' test at high temperature of +70'C. At low temperature there is a chance of not reacting anymore, at high temperature it is the latter: the coil could be toast since it can't radiate all the generated heat away.
With the undervolt test, you should put your phone in the fridge or freezer to really seeing it's behaviour at extreme circumstances. In my opinion you are now easing the pain on your phone during undervolting, by heating it from 2 sides, by charging and heat insulating it.
Click to expand...
Click to collapse
Thanks for the info. I tried to apply what I knew about desktop CPUs and overclocking/undervolting to smarphones. Since people cant put their desktop machines into a freezer this was new to me.
I think I found my final settings now and attached them as a screenshots. Its really convinient to apply different voltages to different frequencies. If I look at my last 48 hours of regular usage (it was the weekend and I went biking with gps and stuff) I have still 55% deep sleep state and 30% 162MHz. So this state is clearly the most important for battery saving.
I found that google maps navigation is a good real life test for undervolting. It crashed my device once, where i didnt have any issues going through a scaled stability test. this is a nice feature of the StabilityTest app, where the the test goes periodically through all selected frequencies. Maybe the crash was also related to jake3317 comment, as I was outside at 10° C / 50° F. Anyways I gave the cpu a little more juice on the higher frequencies and I hadn't had a crash since then.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I've been trying to undervolt my phone using SetCpu but nothing seems to work and my phone has recently started to have huge battery drain issues.
May I know the app you guys use to set voltages for your phone? And also to test for the stability of your phone after the voltage changes?

You can use Kernel Tweaker for adjustments and StabilityTest for testing.

Whosat said:
I've been trying to undervolt my phone using SetCpu but nothing seems to work and my phone has recently started to have huge battery drain issues.
May I know the app you guys use to set voltages for your phone? And also to test for the stability of your phone after the voltage changes?
Click to expand...
Click to collapse
I use the App "Kernel Tweaker" https://play.google.com/store/apps/details?id=com.dsht.kerneltweaker

Ah, finally a decent app that doesn't crash out of nowhere. I've spent the last night trying to undervolt using Kernel Tweaker and tested using the stability test.
Unstable at -200mV, rebooting after almost 2 hours. Gonna try -150mV now
Update: -150mV was stable up to 41mins where I had to stop the test as I had to leave for work. Will continue testing tonight
Update 2: -175mV & -150mV unstable, crashing and rebooting randomly. Running -125mV now

Whosat said:
Ah, finally a decent app that doesn't crash out of nowhere. I've spent the last night trying to undervolt using Kernel Tweaker and tested using the stability test.
Unstable at -200mV, rebooting after almost 2 hours. Gonna try -150mV now
Update: -150mV was stable up to 41mins where I had to stop the test as I had to leave for work. Will continue testing tonight
Update 2: -175mV & -150mV unstable, crashing and rebooting randomly. Running -125mV now
Click to expand...
Click to collapse
If you found a stable base voltage you can do two more things: 1st. lower your minimum cpu clock to 162MHz. 2nd lower the voltage of this frequency alone a little more. for me it can take 50mv less then my base voltage. and its my most used clock besides deep sleep.

Will keep that in mind. I'm still randomly rebooting at -125mV.. Bringing it up to -100mV. Hopefully it'll be stable at this voltage!

Whosat said:
Will keep that in mind. I'm still randomly rebooting at -125mV.. Bringing it up to -100mV. Hopefully it'll be stable at this voltage!
Click to expand...
Click to collapse
Thanks please keep us updated on results. Will use it as a base.
Sent from my GT-I8190 using xda app-developers app

It may be worthy to note that every device has different undervolting potentials so you should experiment on your own too!
But I'll keep posted here

Have yet to run a full stability test but I've had a pretty stable day of using the phone at -100mV.
Will probably test while plugged in tonight when I find a reliable power source

So I've got a steady 5 hour stability test going at -100mV, with the exception of 1728 set at -115mV and 162 set at -125mV.
I've now decreased an additional 10mV across the board to see how it goes for the next 5 hours.
I'm also now using the Trickster MOD kernel app instead of the open source kernel tweaker app as I found that the open source version sometimes does not set my settings at boot (Min/Max frequencies to be exact). And the trickster mod app has the bonus of being able to control fauxsound

Whosat said:
So I've got a steady 5 hour stability test going at -100mV, with the exception of 1728 set at -115mV and 162 set at -125mV.
I've now decreased an additional 10mV across the board to see how it goes for the next 5 hours.
I'm also now using the Trickster MOD kernel app instead of the open source kernel tweaker app as I found that the open source version sometimes does not set my settings at boot (Min/Max frequencies to be exact). And the trickster mod app has the bonus of being able to control fauxsound
Click to expand...
Click to collapse
Awesome im interested to see your final results in undervolting im looking to get some more battery power