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] My device keeps powering off when the I put the screen to sleep.

For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?

supadupadoug said:
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
Click to expand...
Click to collapse
Flash community kernel your getting sod or try removing your Oc UV settings
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Ok thanks. What is sod by the way???

supadupadoug said:
Ok thanks. What is sod by the way???
Click to expand...
Click to collapse
Sleep of death
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

oh lol im learning slowly but fa showly.

supadupadoug said:
oh lol im learning slowly but fa showly.
Click to expand...
Click to collapse
All good
Infusion kernel is great kernel but your settings are going to be trial an error play around with.UV that's usually the probably with sod
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Question about uv. is less best ie -25? and what does disabling the various clock speeds do?

Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.

Thanks I will give that a try. to oc really isn't my goal just to improve battery life. Right now seems to be working ok @12k with frequency uv @75-50

jdbeitz said:
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Click to expand...
Click to collapse
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)

You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation

supadupadoug said:
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
Click to expand...
Click to collapse
No prob. Buddy glad to have ya
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Entropy512 said:
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
Click to expand...
Click to collapse
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.

Dani897 said:
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Click to expand...
Click to collapse
Not a clue - I only know what netarchy has done, not what he plans on doing.
The architecture of voltage/CPU frequency control is significantly different in GB kernels than Froyo. In general it's cleaner, so a lot of the issues with rapid frequency changes might go away in GB. For example, there's some code in the base kernel that's supposed to facilitate rapid voltage changes (not exactly sure how... the only documentation people outside of Samsung have for the MAX8998 is kernel source code.)

Well guys I have some news. I continued use with set cpu no oc just uv on freq above 624 @ -75 and I kept my screen off profile set to 644 max powersave scaling, and my battery life has been outstanding i check emails frequently been texting all morning and playing wwf and im @ 70% after 4 hrs of use. I know I read % doesn't mean much compared to some volts ratio but I think this is worth mentioning. And for my purposes the goal has been achieved in extending battery life and still having exceptional performance.

Oh and I wanted to add that my phone recharges much faster especially with the screen off with these setting. Maybe nothing new to you but def a plus for a(us) neewb's reading.

[Q] How do I use no frill CPU?

I want to overclock my phone. I have doom kernel v14 installed. I installed no frill CPU on my phone. The min frequency I seleted was at 300 MHz (approx) and the max was 1.4 GHz (approx). Does this mean that the phone will automatically go between these values if I run a heavy app (eg GTA 3)? And what does the 'governor' and 'i/o schedular' mean and what does it do? My current settings are :
sio - I/o schedular
Performance - govenor

Min - 245
Max - 1.2 Ghz
Governor : Smartass v2
Mine is like this.

and what about the i/o scheduler? And what does govenor and i/o scheduler mean?

I'm also on Doomkernel v14 and my battery is draining so quicky. Its dropping 5% every 10minutes even when I'm using any light application. I have SetCPU and my sttings are Max 1401MHz and Min 134MHz with smartassV2 and deadline. Although speed is amazing but battery performance is terrible.

TwilightLoz said:
I want to overclock my phone. I have doom kernel v14 installed. I installed no frill CPU on my phone. The min frequency I seleted was at 300 MHz (approx) and the max was 1.4 GHz (approx). Does this mean that the phone will automatically go between these values if I run a heavy app (eg GTA 3)? And what does the 'governor' and 'i/o schedular' mean and what does it do? My current settings are :
sio - I/o schedular
Performance - govenor
Click to expand...
Click to collapse
Performance governor is a "special" one in that it goes to the max. clock speed, and never uses the min., or any frequency in between. You can do that if you want to do benchmarking reliably, but I'm not sure it's good for battery life.
http://forum.xda-developers.com/showthread.php?t=1663809
^ That page explains all the governors, but from what I can tell from using Cool Tool onscreen system info app, "lagfree" on Doomkernel seems to be a higher performance governor like you'd expect from the name and not how he or she describes: it seems to scale down only quite slowly from a high clock, I'm guessing to eliminate any possible lag while scrolling the interface that might result if it scaled down quicker. And we don't have anything relating to multiple cores
Anyway, I think I saw you say you were on JokaWild as well. Looking at the Joka init.d scripts the SmartAssV2 parameters are tweaked towards performance and it comes as the default for the rom, so maybe try that as a more balanced option than Performance governor.
Another CPU governor and I/O scheduler mega-thread
Play!Ya said:
I'm also on Doomkernel v14 and my battery is draining so quicky. Its dropping 5% every 10minutes even when I'm using any light application. I have SetCPU and my sttings are Max 1401MHz and Min 134MHz with smartassV2 and deadline. Although speed is amazing but battery performance is terrible.
Click to expand...
Click to collapse
I wondered as well if v14 was not as good as v13 3013 for battery life, but better for performance, but 5% in 10 minutes is a lot. Have you tried using the BetterBatteryStats app to find an explanation? Has it got better just through subsequent use / recharging?

Battery life really sucks on jokawild (actually in all CustomRoms).
I have mine like this (r800a):
-smartassv2/sio or bfq
-.62 stock rom with a couple of build.prop mods
-64 baseband
-juice defender
-brightness around 25%
-supercharger v6
My phone has been for like 4hr and still with 100%

mikexd1 said:
Battery life really sucks on jokawild (actually in all CustomRoms).
I have mine like this (r800a):
-smartassv2/sio or bfq
-.62 stock rom with a couple of build.prop mods
-64 baseband
-juice defender
-brightness around 25%
-supercharger v6
My phone has been for like 4hr and still with 100%
Click to expand...
Click to collapse
Was it charging? That's impossible. I left my phone idle,lowest brightness and wifi off for about 30 minutes and it dropped to 96%.
I have deep sleep enabled,juice defender,

Minimum CPU Not Sticking on SetCPU with ElementalX Kernel

Wasn't sure if I should comment this on the ElementalX kernel thread or not, so I made a topic...
I bought SetCPU, and its working great. Other than the fact that changing minimum CPU isn't sticking at all. When I set the max (I undervolted it to 1.5 ghz for regular use) it sticks fine, but the minimum just seems to be locked to 300 mhz. Even if I change it, it goes back to 300 mhz.
Anyone know what's up with this?

bump. Need a solution bros.

That is mpdecision at work. Google it, you will find everything you need to know. Once you disable mpdecision (some custom kernels come with it disabled or give you the option to disable it) you min/max cpu freqs should stick

derukun said:
bump. Need a solution bros.
Click to expand...
Click to collapse
Man, this is OLD news. It is working. You ae only seeing the MPD values, that keep your device from having wake or sleep of death issues. Personally I (even Flar, ElementalX's creator) prefer mdp. It is pretty reliable & since implementing it on the N7 & N5, I certainly haven't had any SOD issues.
At any rate, what those apps report as the voltage is a snapshot based on proc data. It is only as accurate as what the exact voltage is at the instant of that report & hasno effect on what actual device screen on/off minimum voltage really is.