Related
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."
I searched for answers but didn't get satisfactory results, so I wanna ask my G2 peeps.
CM7 has an OC daemon, right?
Since it does, is SetCPU still needed?
How does one configure the OC daemon with profiles for screen off, battery>50% etc etc?
I am running CM7.1
convolution said:
I searched for answers but didn't get satisfactory results, so I wanna ask my G2 peeps.
CM7 has an OC daemon, right?
Since it does, is SetCPU still needed?
How does one configure the OC daemon with profiles for screen off, battery>50% etc etc?
I am running CM7.1
Click to expand...
Click to collapse
CM7 does have an OC daemon but it does not have profile settings like SetCPU. Most feel that using profiles kills the battery faster than not using profiles as the device is having to poll the system so frequently. If you just set the min and max speeds, you'll be fine.
Sent from my HTC Vision using XDA App
Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Because the only reason I have setcpu is to set the profile so it goes to 500/200 mhz screen off...
I think the CM7 included OC/UC manager is pretty darn good. I wouldn't worry about using SetCPU it'll just interfere.
convolution said:
Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Click to expand...
Click to collapse
Yes. You can see the exact way that each governor works, but that's pretty much the case with ONDEMAND.
convolution said:
CM7 has an OC daemon, right?
Click to expand...
Click to collapse
No, there is no background process (daemon) controlling the cpu min/max.
It only applies the settings at boot, aside from that, it does nothing.
on our devices, there are three (main) files that effect the cpu overclocking:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
writing a value to these files will make the cpu do what you want. (which is what the CM7 controls do)
You can still use SetCPU if you want... all it does is write the values to these files & the kernel handles the rest.
For example, it can be a slightly more convenient method of cranking up the max frequency if you are about to play a particularly cpu intensive game.
I also find SetCPU handy to do a quick check on the "time in state" & "memory" stats
If you want to use the SetCPU profiles, then, as OriginalGabriel pointed out, it could lead to slightly increased battery usage as SetCPU has to remain running in the background monitoring the variables.
If you don't use the profiles, then SetCPU won't consume any battery.
virtuous_oc, andrev_oc & ilwt_oc are a background process (daemon) that react to a change in screen state & write their defined settings to the above mentioned files.
The difference:
SetCPU runs in Android userspace & has to wait for the android system to send out a broadcast intent that the screen has been turned on/off before it can react & write the values to the files mentioned above.
The OC daemons do not run in userspace & detect the change in screen state at a kernel level... they will have written the values to the files well before the intent gets broadcast.
convolution said:
Just a question though. What does ONDEMAND govenor do?
Like when the phone is not doing anything, the phone will automatically go to the minimum clockspeed, and if you are playing intense games, the phone will max out?
Does that mean when the phone is screen off, the clockspeed will be minimum?
Because the only reason I have setcpu is to set the profile so it goes to 500/200 mhz screen off...
Click to expand...
Click to collapse
The governor controls how the cpu steps up or down the available frequencies based on the current load.
Each of the governors use a slightly different algorithm in how the cpu steps up or down. (within Max & Min as specified by scaling_max_freq & scaling_min_freq)
The well known governors from the mainline Linux kernel:
Ondemand: at the onset of load, jumps straight to max frequency & then steps down through the frequency table.
Conservative: steps up through the frequencies & back down.
Performance: this governor just keeps the cpu at scaling_max_freq & doesn't scale down
Powersave: this keeps the cpu at scaling_min_freq & doesn't scale up
Also, there are a number of governors that have come about from the Android community, I don't have the time right now to write about all the others that I know of... but can do at a later stage if it helps?
The important thing to note, is that unless you device is staying awake when the screen turns off, the screen off profiles are somewhat pointless, as the cpu effectively gets turned off.
Sorry bout the wall of text... am at work & typed it out in a bit of a hurry... hope it all makes sense
Its not needed but u can use it
Sent from my HTC Vision using xda premium
Notes about Battery Saver script
Can be used with kernels that have init.d support
It completely eliminates the need for an application to set CPU speeds or profiles
Easily customizable if you use a text editor(scripts located in /system/etc/init.d)
It will set Max CPU speed to 500MHz & Min CPU speed to 200MHz when a sleep
If SetCPU, Overclock Widget, Android Overclock or QuickClock Advanced Overclock are detected, the script is ignored, so it will not affect them
Preset profiles are:
1.2GHz - 100-85%
1.0GHz - 84-36%
800MHz - 35-0%
And just an FYI, even at 800MHz, the phone still operates very well & smooth but the battery saving are the real benefit
Click to expand...
Click to collapse
Does this mean that if I don't use Set CPU or any app that undervolt it, the phone will AUTOMATICALLY drop the CPU speed according to my battery level:
1.2GHz - 100-85%
1.0GHz - 84-36%
800MHz - 35-0%
Another word, it will automatically drop CPU speed to 800 MHZ when my battery level is 35-0% in order to save battery?
It won't "Drop" the CPU speed, it will lower the Maximum speed the CPU is allowed to ramp up to.
Drumrocker said:
It won't "Drop" the CPU speed, it will lower the Maximum speed the CPU is allowed to ramp up to.
Click to expand...
Click to collapse
So if I am not doing CPU intensive stuff and just play simple games, email, web surfing phone call, then I am not going to see battery improvement since my CPU probably don't ramp past 800MHZ anyway when I am just doing simple stuff.?
Calk's ROM undervolts the CPU at all speeds so that in itself should help a little with battery life. But you are correct, if you are not doing CPU intensive tasks the CPU probably isn't spending much time at the higher speeds.
There is an app called CPUSpy which shows how much time the CPU has spent in each frequency state.
Your phone will ramp up to 1200 mhz more than you think. When it loads a webpage, it will ramp up to 1200, when it's loading your "simple" game, it will max out for a bit, etc.
It might not stay there for very long, but still. The nice thing about Calkuins rom is that even at 800 mhz, the phone is super smooth and lag free. In fact I just turn setcpu down to 800 all the time.
Let me research setcpu and play around with it. Thanks again for the quick answers.
clamknuckle said:
Your phone will ramp up to 1200 mhz more than you think. When it loads a webpage, it will ramp up to 1200, when it's loading your "simple" game, it will max out for a bit, etc.
It might not stay there for very long, but still. The nice thing about Calkuins rom is that even at 800 mhz, the phone is super smooth and lag free. In fact I just turn setcpu down to 800 all the time.
Click to expand...
Click to collapse
The way Calkulin's rom scripts are setup, setcpu gets reset on every reboot, even if you have it set to boot settings. The scripts installed will still take priority and the old rules apply, just to let you know. So you would have to set setcpu every boot for it to work, that or remove the scripts.
Sent from my SPH-D710 using xda premium
Team era... Does the same idea apply to the blazer 2.0 battery saving script? or does tegrak break it?
Sent from my SPH-D710 using xda premium
I havnt opened that rom, but Im gonna say the same applies, I remove those scripts, 2 will affect the cpu state.
edit, let me clarify, the scripts take prority, even if the app makes a script for init.d, the original script will take over on a reboot. So the script breaks tegrak, setcpu, and voltage control unless you set the app on every reboot.
I am running Calks 2 and desperado kernel. I notice when using setcpu, if you have it set on boot, it will override calks script.
His script does work well on saving battery life though. I ran oc'd while at 20% and still had 1700mhz blazing on performance gov.
I'd still use Calks script over setcpu or tegrak only due to the fact im too sporatic with my phone use to create optimal profiles to fit the way and when i need to use the device.
mindgrind said:
I am running Calks 2 and desperado kernel. I notice when using setcpu, if you have it set on boot, it will override calks script.
His script does work well on saving battery life though. I ran oc'd while at 20% and still had 1700mhz blazing on performance gov.
I'd still use Calks script over setcpu or tegrak only due to the fact im too sporatic with my phone use to create optimal profiles to fit the way and when i need to use the device.
Click to expand...
Click to collapse
Actually in my own testing setcpu will not override the scripts, the slider may stay the same, but trust me, it goes back to 800 (or 1200 over 86%batt), Ive tested it several times. If you want proof Ill tell you how to figure it out. I know Im not respected yet, but I am someone that is known under another name that is highly respected, so, take it as you will.
Sent from my SPH-D710 using xda premium
Era, what's your suggestion for keeping the battery saving scripts running and getting a 1500 ish over clock when needed... something that can do both without having to physically change setcpu everytime. I basically want to permanently over clock to 1.5 and still save as much battery as possible when i have the screen off or it is charging. Idk if setcpu profiles work on this phone because i know they did not work correctly on the galaxy s. And one final question... what voltages do u run at what speeds on the "desperado" kernel to undervolt efficiently?
Sent from my SPH-D710 using xda premium
TeamERA said:
Actually in my own testing setcpu will not override the scripts, the slider may stay the same, but trust me, it goes back to 800 (or 1200 over 86%batt), Ive tested it several times. If you want proof Ill tell you how to figure it out. I know Im not respected yet, but I am someone that is known under another name that is highly respected, so, take it as you will.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
ERA. I wasn't looking to say that you were wrong in any way shape or form. I would be interested to know how you seen this as I am still in the beginning phases of learning the android system. I do plan on writing my own kernal/roms but I was actually sharing what my logical thought process would have been given the apps and system info I had avail.
I have a little ways to go in understanding the structure and FS of droid. Time is everyones enemy. Thanks for the correction again!
I havnt opened that rom, but Im gonna say the same applies, I remove those scripts, 2 will affect the cpu state.
edit, let me clarify, the scripts take prority, even if the app makes a script for init.d, the original script will take over on a reboot. So the script breaks tegrak, setcpu, and voltage control unless you set the app on every reboot.
I'm currently running Calkulin's rom v2.5, and even at 41% battery I notice the cpu still hits 1.2 Ghz. Is his script activated by default or am I overlooking something? I also have nothing like setcpu installed.
This guide on how to use the OC/UV beater app that is used to control my overclock daemon that is included in some roms, and is flashable here for advanced users : http://forum.xda-developers.com/showpost.php?p=21253167&postcount=38 . If you cant find the app, unfortunately its not available in market but installable here: http://forum.xda-developers.com/showthread.php?t=1207546
First of all you need to make sure that any apps like setCpu or other overclocking apps are uninstalled not just disabled. Once this is done you need to reboot for it to take effect.
In the app you will normally have 3 tabs, these can be used to create different profiles. You can set a profile name if you like or just leave them.
You then have 6 dropdown menus for the overclock settings, 3 for each phone state. Your phone has 2 states, awake and asleep, asleep is when the phone is screen off and nothing too cpu consuming is running in the background and awake is for any other time. When you open the app for the first time the will say !set this is normal.
For each state you have a governor, min and max setting. When choosing a governor dont choose smartass as this does not work properly with the daemon (see below for why). Personally i use the normal on demand for awake and conservative for a asleep. Other governors can be used though depending on your preference.
Next you set your frequencies. Normally for minimum its safe to choose the lowest value unless you are having issues. As for the awake maximum choose what ever is the highest your phone runs stable at, or if you dont know, try out the one above your current speed. For asleep maximum either choose the minimum again or the one above (message to all kernel devs- try and enable a speed around 120mhz for maximum battery life).
Now we want to test these speeds out to see if they work, hit save, then temp activate. Now use your phone for a while, preferably trying a few intensive apps. When you are sure its stable use perm activate to set it on boot.
This should be enough for most people, but the app has a couple more features like profile switching based on battery state and ill leave you to work them out if you want as they are fairly self explanatory.
About the smartass governor: this governor was designed to switch maximum speeds based on phone state like screen on and off however the daemon does this for you if you set it correctly and will conflict with each other.
For some reason, I can't set anything except the govs (and they both show the same possibilities - there is no "conservative" for sleep) the rest just says !set and it's the only possibility there is.
Is it the app or is my problem ROM-specific?
Using TurboFire beta 6 ROM
barzhdu said:
For some reason, I can't set anything except the govs (and they both show the same possibilities - there is no "conservative" for sleep) the rest just says !set and it's the only possibility there is.
Is it the app or is my problem ROM-specific?
Using TurboFire beta 6 ROM
Click to expand...
Click to collapse
Looks like its rom specific the app is rock solid normally. I think that the daemon config has gotten messed up in the mix of roms so ill try and see what is breaking it.
I cant seem to get the 460800mhz freq stable no matter what voltage i set. Is there a way to delete that crequency from ever being used, and how?
Works like a charm altho it seems the cm7 kernel does not support UV only OC or might be just me not understanding the UI. Antway i ll play around with it alot cuz so far it seems to ne runing alot better an utilising all freq properly.
Sent from my Wildfire S using xda app-developers app
so the Galaxy Nexus has a dual core 1.2ghz TI Omap right? thats 2 cores running at 1.2ghz each? or are the clockspeeds split between the cores?
using Kernel Tuner to manage my CPU speed i noticed that when i exit the CPU tab CPU1 goes offline until i hit CPU1 on/off. nice feature to be able to turn it on or off on the fly, but why isnt it on by default?
then after a while, even set to Performance mode and no matter what i set, my clockspeeds drop by half and fluctuate as if i have the governor set to Ondemand and again with only CPU0 activated slowing my phone down immensely!
im currently running Axi0m with Fancy Kernel but have noticed this on the included kernel and in EOS and SlimBean too.
its really annoying to watch Need for Speed Most Wanted fps drop gradually while racing, or even Into The Dead
is this my phone acting up or is this actually a Deep Sleep feature?
dragonhart6505 said:
so the Galaxy Nexus has a dual core 1.2ghz TI Omap right? thats 2 cores running at 1.2ghz each? or are the clockspeeds split between the cores?
Click to expand...
Click to collapse
Two 1.2ghz cores.
using Kernel Tuner to manage my CPU speed i noticed that when i exit the CPU tab CPU1 goes offline until i hit CPU1 on/off. nice feature to be able to turn it on or off on the fly, but why isnt it on by default?
Click to expand...
Click to collapse
This may be an app compatibility issue. From the market Application officially supports only HTC EVO 3D GSM/CDMA, however it might also work on other devices. Try a different app, Trickster Mod perhaps.
then after a while, even set to Performance mode and no matter what i set, my clockspeeds drop by half and fluctuate as if i have the governor set to Ondemand and again with only CPU0 activated slowing my phone down immensely!
Click to expand...
Click to collapse
This could be the app too. Performance governor should never fluctuate in speed. It should lock in at the top speed you have set, and never change from there. It could also be that you have something with profiles that changes your speeds/governors when certain requirements are met (under 50% battery underclock and use on demand governor).
is this my phone acting up or is this actually a Deep Sleep feature?
Click to expand...
Click to collapse
There are settings and governors that do disable a core when sleeping, or when not needed in hopes of saving battery. Most don't come with this enabled by default, as there are some folks that run into stability issues with those options.
cupfulloflol said:
Two 1.2ghz cores.
This may be an app compatibility issue. From the market Application officially supports only HTC EVO 3D GSM/CDMA, however it might also work on other devices. Try a different app, Trickster Mod perhaps.
This could be the app too. Performance governor should never fluctuate in speed. It should lock in at the top speed you have set, and never change from there. It could also be that you have something with profiles that changes your speeds/governors when certain requirements are met (under 50% battery underclock and use on demand governor).
There are settings and governors that do disable a core when sleeping, or when not needed in hopes of saving battery. Most don't come with this enabled by default, as there are some folks that run into stability issues with those options.
Click to expand...
Click to collapse
your right, Kernel Turner is "officially" only supported by HTC EVO 3d. ive used it on a bunch of other phones and never ran into any problems, like my Samsung Intercept and Evo Shift even an Exhibit 4g. will give Trickster Mod a go
by chance do you know if Axi0m rom has only 1 core enabled by default? i had noticed these sames fluctuations in it's built in CPU controller BEFORE i installed Kernel Tuner. actually this was the REASON i installed Kernel Tuner
also i dont have any profiles or apps set up to govern my CPU frequencies. literally have have 4 games, TerrariaHB and Kernel Tuner lol.
ok ive played around with it a little bit and still having the frequencies drop to 537 even with Trickster Mod, both cores are saying offline and i set frequency lock.
i had my phone set to 806mhz Performance, played with it for a few, come back and...well?
here it is AGAIN after just sitting there and clicking apply doesnt change it! i have to change the frequency then click apply and it does, but it only seems to for a few minutes
-_- im an idiot...
"Max Screen Off"
You will press v under status bar for apply with setting otherwise you will never stay at the same set than before
For apply at boot use settings > apply at boot
Don't use performance, it's useless and deprecated, use interactive instead
Inviato dal mio Galaxy Nexus con Tapatalk 2