I have the SetCpu widget on a screen and every so often I notice that it changes the min/max from what I set it to.
The only thing I have messing with the CPU is Tasker, but they only trigger at night.
Is this just because it's the stock kernel and not a custom?
Thanks
Related
Hey, if I'm using SetCPU on the NS4G with the latest stable Netarchy BFS and a smartass governor and I want to save battery, do I need to have a 'screen off' profile and underclock the CPU a bit? I notice that it slows down waking the phone up, which is a minor nuisance and if I can avoid it because the governor will keep it slow already when not in use, then why not?
Using the "smartass" governor and profiles is not a good idea. The idea of using that governor is that you don't need profiles.
Download Proton Voltage from the market and use the suggested voltages within that app and make it boot everytime on start. It will help you conserve battery.
Without setcpu or pimp installed, if I just set the max of 1000 and min of 216 in the cm7 performance settings menu to restore on boot, will I get the same effect (the only governor setting that will stick is "null")?
Or is it still beneficial to use setcpu to set a screen-off profile?
And the screen-off profile, should the min and max be the same? 216/216? Or is it better to stagger it a little, like 216/312?
I ended up still using setcpu. The built in CPU settings did not work for me.
Sent from my G2x using Tapatalk
mmapcpro said:
Without setcpu or pimp installed, if I just set the max of 1000 and min of 216 in the cm7 performance settings menu to restore on boot, will I get the same effect
Click to expand...
Click to collapse
No, because this allows the governor to change the CPU anywhere between 216 and 1000. This is the default; unrooted stock has it like this.
And the screen-off profile, should the min and max be the same? 216/216? Or is it better to stagger it a little, like 216/312?
Click to expand...
Click to collapse
I keep it 216/216 then allow an in-call profile that goes up to 312 in case when I'm calling someone and the screen is off it needs a bit more juice.
So basically, if I have setcpu installed, but I leave profiles "DISABLED", and leave the sliders alone, then I'm getting no different result from stock? The governor will decide to use the cpu at whatever frequency between 216 and 1000 that it needs at the time?
mmapcpro said:
So basically, if I have setcpu installed, but I leave profiles "DISABLED", and leave the sliders alone, then I'm getting no different result from stock? The governor will decide to use the cpu at whatever frequency between 216 and 1000 that it needs at the time?
Click to expand...
Click to collapse
The Tegra 2 chipset doesn't allow you to change the governor settings. So to answer your question, yes the CPU chooses what frequency it needs depending on load.
I am using the Clemsyn Kernel now, but have never done any overclocking before.
What is the effect on battery life if I went to around 1.4ish?
What is the effect on the lifetime usage of my unit if I overclock?
After I download SetCpu, what settings do I use? Do I have to change anything in voltage?
I read something where people sometimes underclock when the screen is turned off. How can I do this?
Thanks for any help. I am a noob when it comes to overclocking.
deadhead85 said:
I am using the Clemsyn Kernel now, but have never done any overclocking before.
What is the effect on battery life if I went to around 1.4ish?
What is the effect on the lifetime usage of my unit if I overclock?
After I download SetCpu, what settings do I use? Do I have to change anything in voltage?
I read something where people sometimes underclock when the screen is turned off. How can I do this?
Thanks for any help. I am a noob when it comes to overclocking.
Click to expand...
Click to collapse
Start off by setting your main profile to 1.4GHz and tick set on boot. And theres your overclock... I think interactive gov. is the most useful, you can try others if you want.
If you would like to limit the speed when screen off, add a profile under profiles select screen off and set your wanted frequency when screen off.
reidar.ostrem said:
Start off by setting your main profile to 1.4GHz and tick set on boot. And theres your overclock... I think interactive gov. is the most useful, you can try others if you want.
If you would like to limit the speed when screen off, add a profile under profiles select screen off and set your wanted frequency when screen off.
Click to expand...
Click to collapse
+1 This is exactly what I've done
If you set the max speed to 1.4 GHz and set the governor to performance it will drain the battery faster than if you had it set to the others. You'll most likely have already upgraded the TF by the time it dies due to overclocking. It does shorten the life, not dramatically though. You can set up underclocking in profiles.
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Jamin13 said:
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
i guess setcpu makes it easier to change cpu frequencies quickly through the widget, ns tools doeesnt have a widget so its "harder"
qtwrk said:
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Click to expand...
Click to collapse
SetCPU won't control the Backlight Notifications and Dimmer.
Harbb said:
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
Click to expand...
Click to collapse
I'm just a bit OCD about battery life some days. I'd rather use the app than making my own scripts. I kinda derped with the profiles earlier today. All is good now.
I wish the two would play better together too - and I don't see how "just don't use them both" or saying SetCPU is no longer needed is acceptable answers. Especially since many of us actually paid for SetCPU...
Now that it looks like we'll only get two governors in MathKids kernel (what a crock)... saying you are picking the wrong one is a bad answer too. Ondemand certainly isn't the best for battery life, and for those of us who have tested and measured battery life we know just picking one isn't a solution either.
So what is the actual answer? Because setting the governor parameters at boot isn't the problem. It's switching between profiles - and the governors that give you the best battery life and giving acceptable performance need to be tweaked from their defaults.
With OnDemand I'm looking at using over 16% battery per hour under 4.1, even with considerable screen off time. Not being able to set it to Wheatley on screen off is killing the battery.
I will say the problem seems to lay directly with SetCPU and I'm going to contact the dev and see what I can find out. I don't see why it should be changing the parameters back to default on profile change.
But people who use neither or just one probably just not comment. Not to flame, or fight, but it's not helpful to add nothing.
guys...my phone sometimes freezes on the lockscreen....and I have to pull out the battery...the problem is that this happens with all roms, sense or not based....
what's going on?!
You may get more help if you provide a little more info, ie:
-Are you using a specific 3rd party launcher with roms?
-Are you using a custom kernel, and if so what are your settings?
-Have you tried running in safe mode to rule out 3rd party apps?
-Did this problem begin after anything in particular you can think of?
-etc....
Maybe too low CPU values?
Undervolt can cause this as well.
It happened to me while using APEX on ARHD.
But indeed more info is needed.
this started a week ago...with miui official/faux kernel and now with aokp b38/tamcore kernel....I know tamcore kernel is undervolted, and don't know nothing about faux's one...
I use nova launcher, setcpu is set at 384/1188 and I have a profile screen-off at 192/432...
uh, forgot, I use SIO scheduler...I set it with no frills and uninstalled it after, to have just one cpu control app (setcpu)...
this morning my alarm didn't ring! then I had to pull out the battery because it was freezed...luckily I woke up by myself this morning XD
I recommend to use a higher off-screen value (384 MHz) as a first try. See how it reacts and also use an app to check the current voltage (like system tuner / st pro).
If this does not helps then start isolating apps.
I have NOOP sched and 384-432 Off-screen and had no issues far, but I remember that with 192 Mhz a while ago the screen did not wake up a few times (on ARHD 6.3.x).
I updated to b39, nothing now....if it freezes i'll try setting a higher minfreq...
thank you all! thx+1