Develop Bugs

[Q] SetCPU scaling governor?? Which is bes?

I'm running calks rom, and i have setcpu with his profile settings, i just flashed the the newer kernel in the development section for superior battery charging and it has the "smartass" scaling as an option?
Which scaling governor works best? with battery and performance both in mind
"smartass" or "on-demand"

A lot of people say that interactive is really good. my phone doesn't like to play nice with it. I use performance with screen on, battery life isn't a huge factor for me. I set mine to the lowest possible with screen off. I have also heard a lot of good things about smartass, but I have never used it. I would play around with smartass and interactive and see which one works best for you
Swyped from my dark and cyanogenized EVO

I have mine all set to Smartass.
If you select a governer leave setcpu turned on and let your phone idle with the screen on and watch it.
You don't want you CPU maxing out when it's not in use.
I find smartass to keep it at the lowest clock (245 for me) better than any other governers.
Probably should add, i'm getting 20+ hours off a charge with pretty heavy use. but that's with profiles scaling my cpu down as my battery dies, all set to smartass.

With an evo and fresh 3.5.1, n4.3.1 kernal havs, bfs, sbc, the phone has been running very stable @ 1190 but the smartass setting doesnt seem to be playing too well w my phone after many benches w basic setcpu program "long bench" I have determined my phone runs optimal at conservative and performance. Battery isnt terrible on performance as if I stayed by a router for 60% of a full seidio 3500 would be 48-55 hours. This has been best combo for me for speed and life that I have found. no reboots or basic lockups occasionally for an extended time. Maybe its the way smartass looks for what to do by scaling when performance is all way looking for next task that would help it work. But thats my phone, my old droid reponded very dif to kernal swaps as I flashed many too. Battery life off the wifi more has netted me in the 40ish hour charge point. Regardlesd has held 2 days morning to evening routine.

T989 turns off at random times..

hey all, couldnt search forums since its disabled. so like my title says, my phone turns off whenever. the samsung logo comes up and turns off. it happens every so often but nothing annoying. to get it back on is either take battery out or plug to charger and turn it on. when i did this, it gave me the searching for battery thing. this leads me to believe it could be battery? it happens whether the battery is 90% or 20%. anybody have this problem? my phone is rooted using juggs 5.0. phone is just over a month old so wonder if i can get a replacement battery to ruled that one? thanks for the help..

Mines does the same thing except it only reboot when its on charge, and all my contacts dissapear

@OP: Try flashing a different ROM.
Juggernaut has pretty aggressive UVing that not all phones might like.

It happened to me just today. I tried opening Facebook and for whatever reason it FCed. So I reopened it and my phone just turned off. I had to hold the power button for 15 seconds before I felt a vibration and it was alive again. Not sure what the issue is but it's safe to say you're not the only one experiencing this

NJ_RAMS_FAN said:
hey all, couldnt search forums since its disabled. so like my title says, my phone turns off whenever. the samsung logo comes up and turns off. it happens every so often but nothing annoying. to get it back on is either take battery out or plug to charger and turn it on. when i did this, it gave me the searching for battery thing. this leads me to believe it could be battery? it happens whether the battery is 90% or 20%. anybody have this problem? my phone is rooted using juggs 5.0. phone is just over a month old so wonder if i can get a replacement battery to ruled that one? thanks for the help..
Click to expand...
Click to collapse
Random reboots are usually a sign of too aggressive of undervolting. If it's not happening under heavy CPU load and is just happening during standby/sleep phases, then you're just barely on the edge of too much undervolting. Download system tuner from the market and go to voltages in the main menu then knock up the voltage one step (+12.5mV). You should be fine then.
For reference, you can compare your voltages to this list of stock voltages to see what Jugs' global undervolt is. I'm not too familiar with Jugs v5.0:
http://forum.xda-developers.com/showthread.php?t=1523064

yoft1 said:
Random reboots are usually a sign of too aggressive of undervolting. If it's not happening under heavy CPU load and is just happening during standby/sleep phases, then you're just barely on the edge of too much undervolting. Download system tuner from the market and go to voltages in the main menu then knock up the voltage one step (+12.5mV). You should be fine then.
For reference, you can compare your voltages to this list of stock voltages to see what Jugs' global undervolt is. I'm not too familiar with Jugs v5.0:
http://forum.xda-developers.com/showthread.php?t=1523064
Click to expand...
Click to collapse
cool. I give this a try. The last time it turned off was right after I used gps. yesterday I was just browsing. thanks again.

Are you overclocking? If so what freqs/governor? Mine would do this when I would clock it too high for too long. May be an undervolting problem as well.

AaronPauley said:
Are you overclocking? If so what freqs/governor? Mine would do this when I would clock it too high for too long. May be an undervolting problem as well.
Click to expand...
Click to collapse
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.

yoft1 said:
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
Click to expand...
Click to collapse
Thanks for the clarification. I've not really dabbled in undervolting much, and haven't been too concerned with overclocking since the ol' mt3g days. I'm definitely going to read more about it. I've found that for my s2, stock kernel w/ stock frequency set and governor have worked best. Every device is different they say. Thanks your way for the knowledge. Always appreciated.

yoft1 said:
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
Click to expand...
Click to collapse
Thanks for the clarification. I've not really dabbled in undervolting much, and haven't been too concerned with overclocking since the ol' mt3g days. I'm definitely going to read more about it. I've found that for my s2, stock kernel w/ stock frequency set and governor have worked best. Every device is different they say. Thanks your way for the knowledge. Always appreciated.

xperia play overclock

im now using a custom rom with the overclock kernel... i set my phone to "1.4ghz" with AnTuTu... its working great now... no more fps lags on the games i play... and no crashes... im just curious about one thing? will it break the phone in any way? its not heating up or anything atm... i mean i have experienced phone heat on my sensation xe... that phone gets really hot STOCK....
i dont want to break my play... i really like it compared to other phones in the market right now(the only one with gamepads)... its my first time ocing a phone btw...

If its not noticably hot (the battery too) constantly then your fine, just bare in mind try not to push it past 1.6ghz i found my phone didnt last very long at that speed.

The only thing with oc its that it shortens the life of your cpu obviously depending on how much you oc it....and it drains more battery but its not that big of a deal

Defy39 said:
If its not noticably hot (the battery too) constantly then your fine, just bare in mind try not to push it past 1.6ghz i found my phone didnt last very long at that speed.
Click to expand...
Click to collapse
what do you mean by it didnt last very long? did it break the phone?

Basically, my phone is overclocked to 2.0 GHz with smartass scaling with max 800MHz interactive scaling when screen turned off. It works great! Lasts 2~3 days without gaming (5 to 7 days with airplane mode on) and 4~8 hours of hardcore gaming with full charge (6~12 with airplane mode on). I recommend using an extended battery (I haven't, yet) if you are doing so. And it also involves luck. Even if it is the same model, color, etc. some CPUs are more capable than others.

still testing my phone under 1.4ghz seems stable...

DanielEGVi said:
Basically, my phone is overclocked to 2.0 GHz with smartass scaling with max 800MHz interactive scaling when screen turned off. It works great! Lasts 2~3 days without gaming (5 to 7 days with airplane mode on) and 4~8 hours of hardcore gaming with full charge (6~12 with airplane mode on). I recommend using an extended battery (I haven't, yet) if you are doing so. And it also involves luck. Even if it is the same model, color, etc. some CPUs are more capable than others.
Click to expand...
Click to collapse
is it normal for the phone to be abit hotter than when it was running stock???
btw how does smartass compare to ondemand?? smartass tends to get lower benchmark scores than on demand

seagheart89 said:
is it normal for the phone to be abit hotter than when it was running stock???
btw how does smartass compare to ondemand?? smartass tends to get lower benchmark scores than on demand
Click to expand...
Click to collapse
Yes ofc its normal - as each CPU/GPU creates heat based on the load it takes....
So the higher u OC the hotter it gets - thats why in former days OC was quite dangerous
In todays times cpu normaly 1st get unstable, and then has a safety function to shutdown if it gets too hot. (no warrenty that its the same for all chips)
smartass doesnt switch frequencies at once like on demand (e.g. instant from 200mhz to 1000mhz) but it tries to predict the needed power somehow so the whole switching is done in more steps... (as far as I remember)
So yes its performace is a bit below the on demand - but should not be that noticable - but it will also save your battery.

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