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.
Related
anyone got what they think is the best configuration for SetCPU?
stock configuration works great for me
min cpu = 225 (or something like that)
max cpu = 995 (again, or something like that)
????
Stock settings are:
Min: 245
Max: 998
CPU Governer: On demand
Charging 998/998
Sleep/Standby 499/245
Power < 25% 576/245
i concur about the stock clock settings, they work best for me. 998 high/245 low
i am opting for stock... im going to assume that htc/google did their research to give us the best blend of CPU speeds depending on what the phone is doing and what the battery power is...
if stock settings are 998 mhz why overclock it? can you get more from the processor than that?
*black*silva* said:
if stock settings are 998 mhz why overclock it? can you get more from the processor than that?
Click to expand...
Click to collapse
you probably can, but you'd just end up burning it out. what you can do is set the low a bit higher than 245. more battery drain will result.
So what are the out of the box settings on the CPU if you dont use setCPU?
Read this thread you will see them
No one has messed with this app?
I have mine set @ stock, but have also enabled a profile for when the phone is asleep. I set it at 300/245. Not really sure if it makes a difference in battery life.
Mine is set to the A1clock speed which is 768max and 245 min.. no lag when swippin and in act1 video player its still smooth..even a droids 550mhz stock speed. Also got it 245max/min when sleep, remember to exclude setcpu if you u wanna see results..
Goonzy said:
Mine is set to the A1clock speed which is 768max and 245 min.. no lag when swippin and in act1 video player its still smooth..even a droids 550mhz stock speed. Also got it 245max/min when sleep, remember to exclude setcpu if you u wanna see results..
Click to expand...
Click to collapse
What's a1clock?
I noticed that when using SetCPU and setting the minimum CPU speed to 245mhz, it seems like the CPU doesnt clock down to 245, but instead stays at 998. By setting the minimum to 328, it works.
Where can u see that?
Formel-LMS said:
Where can u see that?
Click to expand...
Click to collapse
I agree...where are all you guys/gals seeing/getting information like that off of the phone. What are the apps needed to monitor that information.
Also, exactly what is the stock CPU settings?
gururise said:
I noticed that when using SetCPU and setting the minimum CPU speed to 245mhz, it seems like the CPU doesnt clock down to 245, but instead stays at 998. By setting the minimum to 328, it works.
Click to expand...
Click to collapse
I noticed something similar.
When setting it to 998/245 and hit refresh 5 or 6 times you'll never see something under 998 at the top.
When setting min to something else than 245 but keeping 998 for max and hitting refresh 5 or 6 times you'll see the min value a few times when refreshing.
####################
where is the difference between on demand, user space and performance and what did you take? I took performace for some weeks and just set it to on demand (and 998/245)
so what settings would be proper to set to see a difference?
Hello
Is there a application that allows me to, for example, when motion has been detected to the screen the default speed is set, while if no motion has been detected the CPU is set to 75% and when the screen turns off and the phone is locked, the CPU is set to 30% (all of these are examples)
Something that automatically sets the speed when different conditions happen. I believe SetCPU cant do that.
Thanks
SetCPU. You can set yourself the speed of the core cpu when the screen is off, or when you're charging the phone. Other than that. Your CPU actually knows when to increase the core speed and when to lower it down.
freakfingers12 said:
SetCPU. You can set yourself the speed of the core cpu when the screen is off, or when you're charging the phone. Other than that. Your CPU actually knows when to increase the core speed and when to lower it down.
Click to expand...
Click to collapse
Ah SetCPU supports the things I asked? Did not know.
riahc3 said:
Ah SetCPU supports the things I asked? Did not know.
Click to expand...
Click to collapse
It does exactly what you're asking for. Use the profiles feature for the screen off setting. Otherwise, it automatically scales based on usage.
SetCPU can't set speeds by gestures/motion as far as I know. It can only do charging status, screen status, battery % and temperature...
For maximum flexibility what we need is a Tasker/Locale plugin that can change the CPU speed. Or maybe you could program Tasker with intents?
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.
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.
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