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
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.
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.
I have a Galaxy S3 running a custom ROM (WICKED), In the past I have been using the tweaked stock kernel with ondemand the the CPU would sleep at appropriate times. I updated to the newer version of the ROM and for some odd reason setting the governor to ondemand on the tweaked stock kernel would keep the CPU awake at all times. The only change I made was that I added a screen off profile set to ondemand with lower than full max clock speed. Luckily the ROM came with a another kernel option (Deviant kernel, OC'able), however several governors such as ondemand, conservative and intellidemand has the same issue; my CPU was an insomniac. Finally I tried using the interactive governor with the custom kernel and the CPU now sleeps as it should within a few moments after the screen turns off.
tl:dr: this issue seems to be less of one pertinent to my phone and more so a misunderstanding on my part how governors decide when to sleep the CPU. Why wasn't my CPU sleeping? Which governors are appropriate for a screen off profile?
Hello,
I was able to see that a few others have been having this issue (noted in the dev section ) but I wanted to ask if anyone else has noticed that their CPU frequency does not go above 384 mhz after phone comes out of deep sleep?
Using CyanogenMod 11.0 Nightlies with stock kernel. A reboot of the phone makes is speedy again, however if the phone goes to sleep, its super laggy when it it wakes up. ( the only solution I found is to either reboot, or set the minimum frequency and max frequency to be the same 1500 mhz)
Please let me know if I am alone in experiencing this mhz lock to 384 mhz after phone wakes up.
Note: I did a clean flash and I am still having the same issue.
exhalum said:
Hello,
I was able to see that a few others have been having this issue (noted in the dev section ) but I wanted to ask if anyone else has noticed that their CPU frequency does not go above 384 mhz after phone comes out of deep sleep?
Using CyanogenMod 11.0 Nightlies with stock kernel. A reboot of the phone makes is speedy again, however if the phone goes to sleep, its super laggy when it it wakes up. ( the only solution I found is to either reboot, or set the minimum frequency and max frequency to be the same 1500 mhz)
Please let me know if I am alone in experiencing this mhz lock to 384 mhz after phone wakes up.
Note: I did a clean flash and I am still having the same issue.
Click to expand...
Click to collapse
change to ondemand in cpu settings, its not the default as to why idk, issue and fix has been posted many times b4.
if it is set to ondemand then you have some other prob or a setting that needs to be adjusted or app running in the background
vincom said:
change to ondemand in cpu settings, its not the default as to why idk, issue and fix has been posted many times b4.
if it is set to ondemand then you have some other prob or a setting that needs to be adjusted or app running in the background
Click to expand...
Click to collapse
I actually don't have that as an option for the CPU governor.
All I have available is
Interactive
Conservative
userspace
powersave
performance
All of which cause the same lag issue as what I mentioned. Each nightly flash sets it back to "Interactive" as the default, but since you mention ondemand can you confirm if you can actually see ondemand as an available option to select on your phone using Official CyanogenMod 11.0 Nightlies for Skyrocket ([TeamChopsticks)? I don't have ondemand available.
exhalum said:
I actually don't have that as an option for the CPU governor.
All I have available is
Interactive
Conservative
userspace
powersave
performance
All of which cause the same lag issue as what I mentioned. Each nightly flash sets it back to "Interactive" as the default, but since you mention ondemand can you confirm if you can actually see ondemand as an available option to select on your phone using Official CyanogenMod 11.0 Nightlies for Skyrocket ([TeamChopsticks)? I don't have ondemand available.
Click to expand...
Click to collapse
Interactive does usually end up being default, but I believe it was sometime last month where ondemand was removed from that ROM... which was the point where I jumped ship to another ROM.
Cpu Sticks at 384 On Call Or Wake
Hey All Hate to Bump this, but I have been having this same Issue for Months, Has Anyone Come Up With a Solution Other The Changing ROM??
I'm Also Having this "FREEZE" When The Phone screen is off and I get a Call but the Answer screen doesn't come up while the phone rings straight thru to Voice Mail, But if I slide to The right (On The Blank Screen) It answers.... I have messed with the CPU Performance Settings, and No Help....It does it On the Default settings and the Altered Settings??? I Checked the DEV Thread and Really Didn't see much about this....
Any Help Appreciated;
Mike
exhalum said:
I actually don't have that as an option for the CPU governor.
All I have available is
Interactive
Conservative
userspace
powersave
performance
All of which cause the same lag issue as what I mentioned. Each nightly flash sets it back to "Interactive" as the default, but since you mention ondemand can you confirm if you can actually see ondemand as an available option to select on your phone using Official CyanogenMod 11.0 Nightlies for Skyrocket ([TeamChopsticks)? I don't have ondemand available.
Click to expand...
Click to collapse
You can use conservative; remember to tick de option "Apply automatically on boot".
franzpimp87 said:
You can use conservative; remember to tick de option "Apply automatically on boot".
Click to expand...
Click to collapse
Ya I set it after I made that post and was gonna update today These Settings SEEM to be working extremely well... Will update if it changes..
Governor :Conservative
Min :192
Max:1512
I/O: NOOP
And it's Kinda Strange I/O on NOOP Is Actually throttling the CPU pretty well....Gonna run Like this for awhile and a see how Performance/Battery Use Work Out, And Probably Start Playing with the NOOP Setting, But from my tests it actually seems the most fluid, and Actually drops to 192 when no use....
Mike