Database Info

[Q] Is this okay for me to do?

First off:
Rom:
Virus rom RC1B3
Kernel:
1.8ghz bolted BFS uv kernel
if you overclock, your battery life is less. more power = more usage
so, in theory, if you underclock, less power = less usage..
when I'm at work, I barely use my phone. Maybe to text or a call here and there..
So I wanted to improve my battery life as much as I could,,, I have SetCPU and I have the minimum at 350mhz and the maximum at 650 using the smartass governor when not in use.. Since this is underclocking, the battery life has improved drastically,, though is it safe? I don't see any reason why not, just though I'd like some input on it.

Yeah, you're fine. With the Smart-Ass governor you don't really need to underclock. It's called smart-ass for a reason. It will only use as much is needed. So when your phones screen is off not running any tasks, the governor will underclock itself.

Another thing to add is if you are using SetCPU, then you really do not need to set up any profiles that would underclock the phone if you are using smartass.

[Q] SetCPU governors and best frquencies

Hey guys, i just rooted my phone, flashed LBC Mod 0.5.1 and installed SetCPU. I'm completely new to this and i tried googling about the governors, but couldn't understand a word. Now my question is - what do they do? Also, what are the best frequencies?

Basically put, a governor determines how quickly your CPU speed changes between your minimum and maximum frequency settings.
For example, try setting it to conservative. This will make the changes quite slowly, and you'll notice quite a bit of lag between home-screen and when scrolling quickly through lists. It will take a few seconds to realise you are putting more demand on the device and adjust the CPU frequency accordingly.
I think conservative is the slowest, and really only useful for low battery profiles. At the other end of the scale is 'Performance' which simply keeps your CPU maxed out at your top setting all the time. I can't recommend this one. Only really good for intensive games, but I think the Desire S can cope fine with any out there at the minute. This one will drink battery and cause your phone to run hot.
The best balance of reacting quickly and not interfering with performance or draining battery is the 'smartass' one, although some people prefer the 'ondemand' one.
I haven't a Scooby-do what 'userspace' does. I think it is for when you have another program to control CPU speed that reacts to parameters other than demand. Can anyone else confirm?
Try 'smartass' and 'ondemand' and see which you prefer for performance v battery life.
Edit: The best speed is up to you. I would not recommend going over 1.5GHz even if the kernel supports it. Your phone will not live very long. Personally I am waiting until an application comes along that requires I up the speed to run it properly. Everything I have thrown at it so far has been dealt with well leaving the CPU at 1GHz.
If you feel the need, when changing CPU speeds, do so in small steps. Don't just max out the slider. Find what is best for you with small adjustments. Your phone will become unstable if pushed too far.
The light that burns twice as bright, burns half as long.

@wnp_79
I hope that that lot goes into the new edition of your guide!

ben_pyett said:
@wnp_79
I hope that that lot goes into the new edition of your guide!
Click to expand...
Click to collapse
I think it just may do! I am thinking about doing an entire section simply for S-Off & rooted users, but I'm waiting to see what happens with this AlphaRev business first. Then the safe S-Off procedure can be included in the guide which is aimed at newcomers. Then we get them flashing ROMs!
Would do a separate one for more advanced users, problem is I'm still learning this stuff myself too.

Personally I’ve come to realize that 1.2~1.3 is the best top CPU speed for my usage. I do not play games but use internet a lot and generally interact intensively with the phone within the day. Only other profiles I have set is for screen off and <16% battery. Scaling is set on-demand.

245 ... 1200 MHz
smartass govenour
- good performance
- excellent battery life
- snappy from the verry start (lock screen) thanks smartass
profiles for
- bat<30%
- temp>40°C

axelpix said:
245 ... 1200 MHz
smartass govenour
- good performance
- excellent battery life
- snappy from the verry start (lock screen) thanks smartass
profiles for
- bat<30%
- temp>40°C
Click to expand...
Click to collapse
Have you tried the latest version of LBC ROM (v0.5.2) which has the new O/C Daemon? if yes, then what did you think when compared to setCPU.
I previously used settings through setCPU very similar to those you've written above (although I had a slightly lower top end) but, I didn't find it as snappy from the lock screen when compared to the new Daemon that comes within the Unity kernel, which I did have initial reservations about.....but can only see it getting better over time.

SetCPU with smartass feels faster to me. Absolutely no lag on lockscreen. You must not have a screen off profile. Or at least not one with a different governor.
Yes, the new OC daemon is a nice approach, but needs some interface to configure. Currently there's no way to have profiles for battery or temperature.
Sent from my HTC Desire S using XDA App

I use ondemand and have the screen off profile set into the 400Mhz Max, to allow for house keeping and music playback, that's it!

axelpix said:
SetCPU with smartass feels faster to me. Absolutely no lag on lockscreen. You must not have a screen off profile. Or at least not one with a different governor.
Yes, the new OC daemon is a nice approach, but needs some interface to configure. Currently there's no way to have profiles for battery or temperature.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Your right when I used setCPU my screen off profile was conservative, although the author of the daemon has promised a set CPU like gui to come, so lets hope that s soon and comes with some profile options (just charging, battery and temp profiles would do)
Sent from my HTC Desire S using XDA Premium App

I have used SetCpu with only smartass governor for a few days, compared to both smartass governor and screen-off profile(all 245MHz with ondemand).
I found it is more battery saving on both smartass governor and screen-off profile(lowest freq.). The reason is that the lowest freq.(245MHz) have been selected much more times according to the cpu used freq. stastics in SetCpu info menu.
I guess the auto screen-off profile in smartass governor may not work well or stable. so if I explicitly setup a screen-off profile with the lowest freq., the lowest freq. will be selected restrictly when screen-off.
Sorry for my poor english and hope u all know what I said.

ben_pyett said:
Your right when I used setCPU my screen off profile was conservative, although the author of the daemon has promised a set CPU like gui to come, so lets hope that s soon and comes with some profile options (just charging, battery and temp profiles would do)
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Ditto. I too want a GUI for easy use of the daemon. Until that comes, I'm using SetCPU.

allen oddest said:
I have used SetCpu with only smartass governor for a few days, compared to both smartass governor and screen-off profile(all 245MHz with ondemand).
I found it is more battery saving on both smartass governor and screen-off profile(lowest freq.). The reason is that the lowest freq.(245MHz) have been selected much more times according to the cpu used freq. stastics in SetCpu info menu.
I guess the auto screen-off profile in smartass governor may not work well or stable. so if I explicitly setup a screen-off profile with the lowest freq., the lowest freq. will be selected restrictly when screen-off.
Sorry for my poor english and hope u all know what I said.
Click to expand...
Click to collapse
Hm, on my device smartass always puts back to 245MHz in ScreenOff mode.

axelpix said:
Hm, on my device smartass always puts back to 245MHz in ScreenOff mode.
Click to expand...
Click to collapse
Remember that the phone needs to run @ a certain frequency to keep itself running even when the screen is off. Although Set CPU resetting itself is a new one on me. Have you ticked "run at boot"?

[Q] SetCPU vs. Voltage Control, and what are some recommended settings?

My understanding is most people prefer Voltage Control, but SetCPU allows for specific under/overclocking profiles that can increase performance without killing battery life.
If someone could direct me to popular, trusted settings, I'd appreciate it. I'm not a heavy user or power user, so I'm looking for something that just works well. I don't care about benchmarks and things of that nature.
I'm sure this has been discussed, but I was unable to find posts that didn't concern user-specific issues.
Thanks,
Wyatt
EDIT: 53 views and no replies. I guess I'll experiment for myself. Wish me luck!

gnarlynewport said:
EDIT: 53 views and no replies. I guess I'll experiment for myself. Wish me luck!
Click to expand...
Click to collapse
That's really all it comes down too...experimenting and finding out what works best on YOUR phone with YOUR configuration...
GOOD LUCK!
ps... have been very stable with OC'd to 1.4
-25 down too 200
-100 on 100
bfq and conservative

I use VControl myself...i like the UI.
For Performance: 100-1.4GHZ (1.5 works too, but is WAY overvolted, and 1.6 is extremely unstable), -100mV from 100-1000 MHZ, -75 for 1.1-1.4GHZ.
For "Battery Life": (i really don't see a difference...) 100-800 MHZ (anything below 800 is painfully slow), -100mV across the board.
I leave schedulers and governors at their stock settings, the only time I change anything is to set the gov. to Performance on Performance for max Quadrant scores.

kvswim said:
I use VControl myself...i like the UI.
For Performance: 100-1.4GHZ (1.5 works too, but is WAY overvolted, and 1.6 is extremely unstable), -100mV from 100-1000 MHZ, -75 for 1.1-1.4GHZ.
For "Battery Life": (i really don't see a difference...) 100-800 MHZ (anything below 800 is painfully slow), -100mV across the board.
I leave schedulers and governors at their stock settings, the only time I change anything is to set the gov. to Performance on Performance for max Quadrant scores.
Click to expand...
Click to collapse
How many Mhz levels are you selecting? In my experience anything above 5 and it WILL NOT clock up to the higher settings. Maybe thats why you notice no difference in battery life?
For instance if you had say 100, 200, 400, 800, 1000 and 1400 you will reace 1000mhz only
if you had 100, 200, 400, 800, 1400 you would reach the 1400mhz. ive tried many combos and 5 or less was the max it would use (voltage control app, im sure setcpu would most likely be the same)

How many slots does the imnuts kernel support?
Sent from my SCH-I510 using Tapatalk

I started using SetCPU, and I think I prefer it.
Quick question, it seems like rebooting is unnecessary for the changes to take effect, is that true?
Overclocking definitely worked. I got 1853 @ 1200mhz in Quadrant, up from 1600.
Edit: now 2025 @ 1300mhz / 1300mhv
2nd Edit: Late last night, I was using a stability test in one of the apps, but I can't for the life of me remember which app or how I found it. Now I'm using StabilityTest from the market. What's a safe cpu temp for these phones? I'm getting 32 degrees under full load in an air conditioned environment.

gnarlynewport said:
I started using SetCPU, and I think I prefer it.
Quick question, it seems like rebooting is unnecessary for the changes to take effect, is that true?
Overclocking definitely worked. I got 1853 @ 1200mhz in Quadrant, up from 1600.
Edit: now 2025 @ 1300mhz / 1300mhv
2nd Edit: Late last night, I was using a stability test in one of the apps, but I can't for the life of me remember which app or how I found it. Now I'm using StabilityTest from the market. What's a safe cpu temp for these phones? I'm getting 32 degrees under full load in an air conditioned environment.
Click to expand...
Click to collapse
I just switched over to Setcpu as well. It seems to work better for me also. I can now select 6 levels instead of the 5 before in voltage control and I also noticed that the set on boot on voltage control did NOT work but it DOES work in setcpu!! Im happy!

Haven't tried Setcpu yet, but I preferred Pimp my CPU over VC when I was using Miui on the Fascinate.
Sent from my SCH-I510 using XDA App

cpu govener??

question... I see all the govener setting in ns tools, setcpu, ect.... just wondering something.... What setting is.used in factory otu roms? lets say a.unrooted nexus s, what is.it natively set at? 100/1000 ? and ondamand? or is.it 1000/1000?
Sent from my Nexus S 4G using XDA App

100/1000 ondemand is the default.... but I always change it to 200/1000 smartassv2 it works best for my phone
Sent from my Nexus S 4G using xda premium

I usually use "ondemand", it seems to work best. Once I decided to try "powersave" and my phone slowed down to a crawl, pretty much unusable. I don't know what that was about, but I definitely don't recommend it...

Jabaculemos said:
I usually use "ondemand", it seems to work best. Once I decided to try "powersave" and my phone slowed down to a crawl, pretty much unusable. I don't know what that was about, but I definitely don't recommend it...
Click to expand...
Click to collapse
Powersave limits the cpu to the absolute lowest frequency at all times. It is not usable for normal operations, except for Setcpu screen-off profiles.
Performance governor is the opposite ; it keeps the cpu running at max frequency (1ghz with stock kernel) and is useful only for speed benchmarks.
The other linux kernel governors are described in detail in numerous threads... All you have to do is search "kernel governor ".
My personal choice is smartassv2 since it's responsive, efficient with battery consumption, and features a screen-off sleep profile.

Ezekeel recommended me lazy with proof screenshots

Governors control how the CPU frequency adjusts. They work like this:
Ondemand: Starts at a low frequency and when there is any CPU activity it uses max frequency. It goes back to low over time.
Conservative: Like ondemand, but instead of using max frequency on CPU activity it uses the next step. It's less responsive than ondemand since it goes like: "100% CPU > Higher Freq. > 100% CPU > Higher Freq..." instead of "100% CPU > Max Freq."
Lazy: Like ondemand but there is a small delay between frequency changes. I use this one.
Performance: Max frequency all time.
Powersave: Min frequency all time.
Interactive: This is a bit complex, actually it's sampling the CPU usage and trying to predict what will come up (I think).
Smartass: It's like interactive, but rewritten. It should give better results.
Default is ondemand 100/1000 and it works pretty good.
Hope I helped.

[Q] Confused about which governor to use with Speedy-7

I'm a litte confused about which governor to use.
By default this kernel uses conservative and it performs quite well. I would expect it to be less snappy, but the difference is very small. Especially scrolling through the home-screens etc. is fluid.
Now, interactive is supposed to be the new ICS default-governor and normally you would expect it to be sthe snappiest one. Anyway, with interactive scrolling through my home-screens is a little choppy... How can that be?
SmartassV2 seems to be good in an overall-view, but I'm not sure what to think about it, because I generally would prefer using a more classical governor.
What governor would you use on a stock-4.0.3-ROM with Speedy-7-Kernel if you don't use heavy apps or games, but want all those general apps (launcher, browser etc.) to rum really smooth?
Thanks
McDV

Hi,
i use lulzactive on my Nexus S.
If you use it with NS tools, it gives you more option to control screen off freq.
With that it has great battery life.

lulzactiveV2/sio is the smoothest for me. Anyways I don't know yet which is the best governor for the night when I sleep. Can I use powersave? When I don't use my phone it should stay at the lowest clock as possible.
Sent from my Nexus S using XDA App

personal experience: wheatley --> luzlactive --> lazy , best battery-performance balanced

Thanks for all your answers.
I've tried all those governors now and I think smartassV2 seems to be the one I will use for now.
But some other question: The kernel offers Live OC. It seems pretty clear what this is: All the speeds are increased by x%, including the bus-speed of 200Mhz, without increasing the voltages.
Lets say I just overclock about 10%, so the maximum-clock is 1100 Mhz, without increasing the voltage. Will I drain more battery than with 100% speed? And is there any visible advantage in overclocking just about 10% or won't I see or feel any difference at all?