Develop Bugs

[INITSCRIPT] screenstate_scaling - switch CPU freq governor on screen state change

Attached init script changes the CPU frequency governor based on the screen state:
Code:
screen on -> interactive governor
screen off -> powersave governor
Don't use this with SetCPU!
Thanks NeoPhyTe.x360 for the idea...
Edit:
This script is released to public domain, so it can be freely used for derivative works without permission!

Good thinking!
Thanks for sharing.

do we flash this in clockwork?

bradputt said:
do we flash this in clockwork?
Click to expand...
Click to collapse
Nope, it's just a init script for the ROM devs...

but is possible to applu in a rooted phone simply copying to /systen/etc or nope? needs setcpu or works without?
thx

Awesome work you do
+10

This is supercool, we wont need to use SETCPU anymore, just flash this and enjoy super battery life, big thanks FloHimself!

bartito said:
but is possible to applu in a rooted phone simply copying to /systen/etc or nope? needs setcpu or works without?
thx
Click to expand...
Click to collapse
You can push this script to /system/etc/init.d but it has some dependencies e.g. the interactive governor, perflock disabler when you want to underclock, ...
NeoPhyTe.x360 said:
Awesome work you do
+10
Click to expand...
Click to collapse
It was your idea, so same goes to you!
ivicask said:
This is supercool, we wont need to use SETCPU anymore, just flash this and enjoy super battery life, big thanks FloHimself!
Click to expand...
Click to collapse
That's the reason we are doing it this way: make the governor switching a bit more low level without SetCPU. But remember, this is not a update.zip and not flashable from recovery...

nice work. i really appreciate this. lets hope all the devs see this

FloHimself said:
Attached init script changes the CPU frequency governor based on the screen state:
Code:
screen on -> interactive governor
screen off -> powersave governor
Don't use this with SetCPU!
Thanks NeoPhyTe.x360 for the idea...
Click to expand...
Click to collapse
Useless... Interactive governor sets low speed when idle.

sbricout said:
Useless... Interactive governor sets low speed when idle.
Click to expand...
Click to collapse
You are right, the interactive governor sets the lowest speed when idle. But idle != screen off.

sbricout said:
Useless... Interactive governor sets low speed when idle.
Click to expand...
Click to collapse
Applications and services can still ramp up the CPU speed during the screen being off, so not useless at all. Switching to the powersave governor for when the screen is off, will stop it ramping up during this time.

I modified the script abit to include frequencies for min and max.
http://linux-box.nl/~sjoer/90screenstate_scaling

sfjuocekr said:
I modified the script abit to include frequencies for min and max.
http://linux-box.nl/~sjoer/90screenstate_scaling
Click to expand...
Click to collapse
Nice, that`s something I`ve done later, too :
http://dl.dropbox.com/u/31174/android/90screenstate_scaling
Thought about extending it some more...

don't punch me, but... how can this be installed?

Kinda complicated, you`ll need a modified init.rc to run the scripts from /system/etc/init.d/ at startup, you have to push the governor modules and perflock_disabler module compiled for your kernel in /system/lib/modules/ the insmod scripts for the governors, perflock_disabler script and the script above to /system/etc/init.d/
FloHimself thank you very much for the scripts and the modules.

Is it me or is this script constantly looping with no breaks/sleeps?

I've installed Neophytes' ArauxtSense 7.1 rom and he already added this on his rom. The question is, do I have to uninstall my SetCPU now? I have my referred settings on it and don't know how to disable it. I have unchecked the "Set on Boot" but everytime I boot my device, I can see that the SetCPU is still running on the background. Any advice? Any risks when having them both?

sub0min0us said:
I've installed Neophytes' ArauxtSense 7.1 rom and he already added this on his rom. The question is, do I have to uninstall my SetCPU now? I have my referred settings on it and don't know how to disable it. I have unchecked the "Set on Boot" but everytime I boot my device, I can see that the SetCPU is still running on the background. Any advice? Any risks when having them both?
Click to expand...
Click to collapse
There shouldn't be any risks, but one of them will force its set freq, and the other one will be constantly changing it
Sent from my HTC Desire using XDA App

Thanks for clearing that out. I guess I'll have to uninstall it then not unless I install another rom. Thank you...

help needed SETCPU problems

Hey guys im having trouble with my phone when setcpu is running. When ever i come out of lock screen it takes a few seconds to be able to do stuff on my phone, like its waking up from sleep. Also some times i get this message and it has to reboot.
"Sorry activity htc sense (in application HTC Sense) is not responding."
Im running the 2.6.32.15 king # 4 kernel.
My set CPU settings are on 1.15 GHz max and 460800 MHz min. Im running conservative at the moment but it does it on other scaling like performance and on demand. my setting for screen off is 460min 614 max.
Is there anything im doing wrong? or should i be using a different kernel? What kernels are the best? Thanks

I would bump up the lower end to about 600. I have have issues lower than that coming out of sleep.

im running virtuous 2.7
power saving kernel
Main Profile is 245-998 ondemand
Screen Off is 245-384 ondemand
I do not have that problem... but it would be a lie if I told you i didn't before!
I was having this problem you are talking about when my main profile was set to conservative.
EDIT: Back up your setcpu + settings in titanium... Uninstall it (or freeze it) and see if the kernel can run it just fine cause it probably will. Most kernels already have the settings for optimum performance and even the devs who make them (like hydra) say that it will work best without setcpu.
Source: http://www.hydrakernel.net/hydra_kernels_information.htm
"I recommend not using the setcpu controls or governor with these kernels. Let the stock governor do the work. If you have setcpu installed I recommend clearing out the settings before flashing the kernels. You can use it to monitor cpu speeds or an app from the market called systempanel if so desired."

[Q] HAVS + CPU Control & [Q] Battery Applications

I have a HAVS kernel (Net's 4.2.2 SBC CFS Aggressive HAVS) and as I understand it any sort of CPU Tweaking application will cause conflict and probably a system crash, correct?
Also, can some recommend me any applications that compliment Juice Defender well. I have Juice Plotter already. I am looking for an aggressive auto task killer that's customizable along with any other suggested applications. Thank you!

A system crash is a possibility but they will basically just counteract each other and either make your battery life worse or give a performance hit.
SetCPU helps dynamically underclock/overclock based on certain scenarios. You can set what scenarios you want. Another option is AutoKiller. It isn't Auto Task Killer. Its a different application. Not quite sure how this works but you can research it. However Froyo does a good job managing most applications.
But if you are looking for customization I would go with SetCPU and AutoKiller

Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks

Vulf said:
Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks
Click to expand...
Click to collapse
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...

I just installed setcpu and ran it. My phone crashed about 10 seconds after I allowed root access. Tried twice more with same results.

aimbdd said:
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...
Click to expand...
Click to collapse
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.

sekigah84 said:
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.
Click to expand...
Click to collapse
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.

lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)

aimbdd said:
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)
Click to expand...
Click to collapse
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?

Vulf said:
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?
Click to expand...
Click to collapse
Again, it is not setcpu it is your settings. You said you moved the slider "one or two notches up" (overclock) from the default 944? The evos default max is 998. Either way, with what you said you are overclocking and your device cannot handle the overclocked speed.
Like I said, you can do the exact same thing that setcpu does through terminal emulator. Instead of blame setcpu you should observe the speed/governor combo you are using.
I can oc my evo to 1.26 on my personal kernel without it rebooting on certain governors but on others it would reboot randomly and I don't set cpu parameters through setcpu, I use te, init scripts, and tasker.

lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Couldn't have said it better. The common misconception around these parts is that SetCPU has some negative effect on kernels with HAVS and this is just untrue.

Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.

sekigah84 said:
Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.
Click to expand...
Click to collapse
The common practice with setcpu is to use it to underclock when sleeping. Depending on the governor you use (besides powersave) you are actually causing the cpu to struggle when completing tasks if you limit the max to 245 for example. During sleep if it needs to perform a task and that task would normally complete in 1 second at 998 mhz imagine how much longer it would take if it was capped at 245.
I have had better results not underclocking while sleeping. I would suggest using setcpu to specify to use the conservative governor when sleeping, ondemand/interactive/smartass when screen on (depending on which one you want), and interactive/ondemand while charging without under/overclocking at all and using the default freqs (245 - 998). I'm certain you would be surprised at how your evo behaves after that.

I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.

aimbdd said:
I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.
Click to expand...
Click to collapse
My last post may have been a bit confusing so I will clarify. When I said underclock I was referring to the practice of capping the max freq to 245 which is what most people do. If you cap the freq at 245 you are essentially underclocked all the time and would cause your cpu to work harder.
The evo underclocks automatically when the cpu load is low enough (idle for example) to save on power, reduce temps, and to basically keep the system running. But I would assume that most of us who have used setcpu have seen how lousy the evo runs when it can't scale up (locked at 245) when using the evo. The governors will underclock the cpu on their own if the device reports it does not need the higher freqs and this occurs during sleep/screen off as well.

Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?

Vulf said:
Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?
Click to expand...
Click to collapse
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.

freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?

freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
This.
Very sound advice and yes some evos can't undervolt as well as others. Always remember too that the stock kernel for the evos use CFS. If you are using a bfs kernel that could also cause issues. Some evos run better with bfs versus cfs but it's really going to come down to the amount of time you want to put into testing and confirming what your evo likes.

Vulf said:
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?
Click to expand...
Click to collapse
Yeah, it does. How far are you trying to overclock before your phone freezes/reboots?

[Q] Set CPU Question

Hi, I am kinda confused by one thing. What is the difference between using SetCPU or similar apps (CPU Master, etc.) vs just setting the Max/Min and governors in Settings -> Advanced Settings -> Performance -> CPU Settings?
If it matters, I am using deck's gingerbread ROM and Tiamat 3.3.7 sbc.

Not much difference really. SetCPU and similar apps are mainly designed to be used on roms that don't have the feature that you're talking about.

peterpunn said:
Hi, I am kinda confused by one thing. What is the difference between using SetCPU or similar apps (CPU Master, etc.) vs just setting the Max/Min and governors in Settings -> Advanced Settings -> Performance -> CPU Settings?
If it matters, I am using deck's gingerbread ROM and Tiamat 3.3.7 sbc.
Click to expand...
Click to collapse
It depends on what type of governor that you want to use. If you plan on using a smartass governor, you should not use SetCPU, but if you are going to use some of the other ones, you may want profiles for screen off, charging, etc. You need Set CPU to do the profiles.

well i dnt think cyanogen has a profile ft like setcpu

djnarcotics said:
well i dnt think cyanogen has a profile ft like setcpu
Click to expand...
Click to collapse
I don't think it does with the default kernel, but if you flash something like SavagedZen kernel with Cyanogen, you will see access to those governors like interactive, ondemand, etc.

I am using the Tiamat 3.3.7-sbc kernel and the available governors are: interactive, conservative, userspace, powersave, performance, smartass.

Any idea on why the settings don't stick? Sometimes I will set the Max CPU at 691MHz, but when I check after a while its back at 998MHz.

[Q] good overclock tool?

can anyone suggest a good overclock tool with voltage parameters? setcpu doesn't seem to have one for the play... and antutu seems bugged when setting voltages... (keeps changing the value for 1300mhz to 1300mv)

seagheart89 said:
can anyone suggest a good overclock tool with voltage parameters? setcpu doesn't seem to have one for the play... and antutu seems bugged when setting voltages... (keeps changing the value for 1300mhz to 1300mv)
Click to expand...
Click to collapse
I'm using Antutu CPU Master Pro and I don't find it buggy. This is better to use imo than setcpu which consumes more battery. Longpress the frequency you are in and using then set to -25mv. Tick on "set on boot" then click "apply". Reboot your phone and check again your settings if it was changed or not. Also, try to reinstall your overclocking app and clear some cache on your phone.

anbu187 said:
I'm using Antutu CPU Master Pro and I don't find it buggy. This is better to use imo than setcpu which consumes more battery. Longpress the frequency you are in and using then set to -25mv. Tick on "set on boot" then click "apply". Reboot your phone and check again your settings if it was changed or not. Also, try to reinstall your overclocking app and clear some cache on your phone.
Click to expand...
Click to collapse
i do agree that antutu is very good... but the problems started when i updated to 2.5... i was using 2.3 before
is -25 the lowest it can go??? isnt -50 safe?
EDIT: also in 2.5 it keeps saying that it has been granted superuser permissions... in 2.3 it only does that whenever i change any setting...

I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)

seagheart89 said:
i do agree that antutu is very good... but the problems started when i updated to 2.5... i was using 2.3 before
is -25 the lowest it can go??? isnt -50 safe?
EDIT: also in 2.5 it keeps saying that it has been granted superuser permissions... in 2.3 it only does that whenever i change any setting...
Click to expand...
Click to collapse
I use 2.3.1 version. I tried -50 on setcpu and it crashed my phone. Haven't tried -50 yet on Antutu. I rolled back my speed from 1.5ghz to around 900+mhz as the speed is still fast (btw im using T.E.A.M. rom).

jacklebott said:
I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)
Click to expand...
Click to collapse
so i only have to run this once? seems good... will try it later...
anbu187 said:
I use 2.3.1 version. I tried -50 on setcpu and it crashed my phone. Haven't tried -50 yet on Antutu. I rolled back my speed from 1.5ghz to around 900+mhz as the speed is still fast (btw im using T.E.A.M. rom).
Click to expand...
Click to collapse
i set my cpu to -50 and it runs fine... did some stress tests and it is stable... running at 1.4ghz (just right for psx games)

jacklebott said:
I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)
Click to expand...
Click to collapse
What are bootloops btw? ty

anbu187 said:
What are bootloops btw? ty
Click to expand...
Click to collapse
Bootloop means your phone endlessly reboots without ever getting past the bootlogo

jacklebott said:
Bootloop means your phone endlessly reboots without ever getting past the bootlogo
Click to expand...
Click to collapse
ah ok thanks, that never happened to me so far. Anyway, any idea why my battery is drained that much even when im not using it. No wifi, no other background apps enabled, or is it with the kernel? ty