Related
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?
ok idk ow to overclock correctly i need a way to make this sense 3.5 rom less laggy an run more smoothly, can anybody help me with this???
Yes just use Daemon Controller (basically functions the same as SetCPU) and set your maximum frequency. For most ROMs I would set it around 1.5Ghz, and set the governor to smartass or smartassv2. The governors will depend on the kernel you're using. For a good sense kernel, I would use this one.
Additionally, you can download Incredicontrol via the market and that will enable you to adjust your voltages, based on the frequency steps. A lot of people prefer to bump the voltage up or down 25% to increase performance or reduce battery drain.
I AM NOT RESPONSIBLE FOR ANY PAIN AND SUFFERING YOUR DEVICE MAY INCUR.
If I helped, slap my Thanks button around a bit.
chattguy said:
Yes just use Daemon Controller (basically functions the same as SetCPU) and set your maximum frequency. For most ROMs I would set it around 1.5Ghz, and set the governor to smartass or smartassv2. The governors will depend on the kernel you're using. For a good sense kernel, I would use this one.
Additionally, you can download Incredicontrol via the market and that will enable you to adjust your voltages, based on the frequency steps. A lot of people prefer to bump the voltage up or down 25% to increase performance or reduce battery drain.
I AM NOT RESPONSIBLE FOR ANY PAIN AND SUFFERING YOUR DEVICE MAY INCUR.
If I helped, slap my Thanks button around a bit.
Click to expand...
Click to collapse
0k the number says 245760 i cant tell which is the 1.5 ghz?
245mhz... That is your lowest frequency. You'll set that as your minimum. Your max should be set at 1497mhz. It'll have some numbers straggling on the end but disregard them. 1497mhz = 1.5Ghz.
Sent from my Incredible 2 using Tapatalk
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
Hi all I'm fairly new to these forums, although I have been watching from afar for quite some while now!
I have been trying out custom roms and various kernels and was wondering how do I go about overclocking my device? Only reason I am asking is because I was checking out benckmark results for other devices and noticed some can be particularly high.
Any insight would be most appreciated!
I wouldnt try any overclocking on the HOX because of the heat issues. A more safe and stable way of doing it is changing the govenor of the kernel or forcing cores online. I think you can use core control (in the apps and themes section) to change core behaviour and system tuner to change govenor.
view heisoom
I have now installed core control. Got to admit it is nice having the option to save a bit more power. How much as an estimate do each of cores use anyway just out of interest?
meleelord said:
I have now installed core control. Got to admit it is nice having the option to save a bit more power. How much as an estimate do each of cores use anyway just out of interest?
Click to expand...
Click to collapse
you can download an app called tegrastats to find out more but all you should know is this. once you activate the corecontrol and depending what app you use you should be fine. if i was you i would also use no-frills cpu app. that way you can underclock and would save you more juice
Goku80 said:
you can download an app called tegrastats to find out more but all you should know is this. once you activate the corecontrol and depending what app you use you should be fine. if i was you i would also use no-frills cpu app. that way you can underclock and would save you more juice
Click to expand...
Click to collapse
Fantastic! Many thanks for the advice. I have now installed no-frills cpu, and started to tinker around with the settings. Could I ask as I am still fairly new to some of this, when I first went on to the settings both maximum and minimum were set to 1.5 GHz (Not sure if it was just saying this on the app or not or if these are the actual settings) but I would guess this would use a lot more power am I right?
meleelord said:
Fantastic! Many thanks for the advice. I have now installed no-frills cpu, and started to tinker around with the settings. Could I ask as I am still fairly new to some of this, when I first went on to the settings both maximum and minimum were set to 1.5 GHz (Not sure if it was just saying this on the app or not or if these are the actual settings) but I would guess this would use a lot more power am I right?
Click to expand...
Click to collapse
yes you are right. put the min frequency to say 200 or 300 mhz and then press apply on boot and then reboot and you should be fine