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.
Related
What scaling setting do you use, maybe you have custom profile?
I personally use 'ondemand', but I was thinking.... It would be nice to have a smart scaling setting, based on the amount the phone is used, screen brightness and the battery temperature, etc.
Sent from my X10a using XDA App
Hi.
I've set mine at 576 max and left minimum at 245, scaling is on demand, and have set a profile for screen off at 245 for both. I've left the advanced screen as I don't have a clue what any of it means lol.
Non
Used it at first when got rooted. still on root BA23 firmware and im very happy with the current setup. I left the processor to operate the way it want to do.
Dont take me wrong, its a great software, everything is depends on overall apps you are running. and its unique to your phone, check its really necessary.
After-all we are talking about android, not windows.
I want to know the best setting also I had some custome profiles (after reading in a post on XDA) but phone got slow, laggy & sometimes call drop. Then i deleted all custome profiles
Mano1982 said:
I want to know the best setting also I had some custome profiles (after reading in a post on XDA) but phone got slow, laggy & sometimes call drop. Then i deleted all custome profiles
Click to expand...
Click to collapse
I had that problem once. But i think it is a OS bug than the SetCPU bug itself. You should re-root your fone and set profiles one more time. It will help you save a lot of battery
My setting (following someone on the net)
- Fully chage (AC/USB): 998/245
- Screenoff: Max: 348 Min: 245
- Battery <25%: Max: 348 Min: 245
Ok Dundun, I've set profiles again same as yours let's see how it workd
Just came across this thread for decent SetCPU setting: http://forum.xda-developers.com/showthread.php?t=734886
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.
I am new and apologize if this question is answered elsewhere.
I have read that the hotplug governor included in other kernels does not work correctly when paired with a screen off profile set in a cpu control app such as setcpu. I understand that the interactivex governor baked into leankernel 1.10 stable also includes a hot plug when the screen is off. Does anyone know if screen off profiles within setcpu also interfere with this functionality? Or, alternatively, what is the best way to check the status of a cpu hot plug when the screen is off?
lowmanb94 said:
I am new and apologize if this question is answered elsewhere.
I have read that the hotplug governor included in other kernels does not work correctly when paired with a screen off profile set in a cpu control app such as setcpu. I understand that the interactivex governor baked into leankernel 1.10 stable also includes a hot plug when the screen is off. Does anyone know if screen off profiles within setcpu also interfere with this functionality? Or, alternatively, what is the best way to check the status of a cpu hot plug when the screen is off?
Click to expand...
Click to collapse
I dont think interactivex disables a core but just caps the freq to the lowest on screen off. If you want to disable a core on screen off you can run cpu sleeper. If you wanna check if a core goes offline you can dump a logcat and see if a core is being disabled.
lowmanb94 said:
I am new and apologize if this question is answered elsewhere.
I have read that the hotplug governor included in other kernels does not work correctly when paired with a screen off profile set in a cpu control app such as setcpu. I understand that the interactivex governor baked into leankernel 1.10 stable also includes a hot plug when the screen is off. Does anyone know if screen off profiles within setcpu also interfere with this functionality? Or, alternatively, what is the best way to check the status of a cpu hot plug when the screen is off?
Click to expand...
Click to collapse
if you use the shootout and want to see if itz working properly the app cpuspy should tell you