For some reason I don't have an option to undervolt anything in SetCPU which I presume is there because it's listed as an app capability and it seems others on this forum have been able to undervolt with this app. I also understand that the ability to undervolt must be first unlocked by a kernel before it can be accessed through SetCPU, and I have this kernel flashed:
http://forum.xda-developers.com/showthread.php?t=1466283
which does list undervolting as a possibility. Am I missing something here? Why can I only schedule profiles around clock speed?
**As a side note, I tried out system tuner and I can reach the undervolting through system tuner but I don't really like the interface for system tuner so I would prefer sticking with SetCPU if possible (especially since I already paid for it)
**My ROM is stock, does that make a difference? Isn't the capability only dependent on the kernel?
DO NOT USE SETCPU! It keeps your second core constantly running which means terrible battery life. I recommend Gideon's script or FauxClock (Which is what I use.) I also recommend undervolting it to -75 mV.
Related
I am new to the setcpu app I am wondering how do I know how much frequency my min and max should be to help my phone out more. Can anyone help me on that plz?
Sent from my PC36100 using XDA App
It will depend on which ROM and kernel you're running, but generally, overclocking doesn't do much good for you. I do however run my Main Max @ 1113 and Min @ 245. I then have a profile set for Screen Off Max @ 245, Min @ 245. This has helped a lot with battery life. This is on CM6.1.1 and the SBC stock kernel.
Also, there are the Scaling options. They will vary based on the kernel you're using. Generally, their names speak for themselves, so pick appropriately. I use Interactive when available, or Ondemand as a second choice. If you choose Performance, you will stay clocked at the highest speed until over ridden by a profile, so don't bother with that one unless it's for testing only.
One thing to think about is that Setcpu doesn't play well with HAVS, so if you're running a kernel with that built in, they will be fighting each other.
Also, if you're running a stock based rom with a stock kernel, you will need to disable Perflock if you want Setcpu to be able to really do it's job. So, while in Setcpu, tap Menu > Perflock Disbaler and attempt to disable perflock. Once it is successful, pick set on boot and close that window. Now Setcpu can work properly and you can start saving battery.
If you're primary goal is to get amazing battery life, I highly reccommend you try some of the new SBC kernels that have trickle charging built in. That's what I've been using since they came out, and it is amazing what a little tweak can do for you. SBC Kernel Thread
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?
I purchased Tegrak Ultimate, and I have SetCPU as well. Right now I am running Calkulin's ROM with Stock EL29 kernel. Trying to figure out Tegrak, but I'm not so savvey with knowing voltages and stuff like that.
I can OC up to 1.47ghz with Tegrak's presets, but I wanted to try and get it up to 1.6ghz OC. I know you have to adjust the voltages, but I can't figure out what I need to do to make it stable, the phone just freezes everytime I try and figure it out. Can anyone give me some knowledge?
It all depends on the kernel you're running. Tegrak is for stock kernels, while SetCPU is for custom kernels. Tegrak allows you to slightly overclock the stock kernel, as well as adjust voltages and change your governor. As you've found, the highest you can go with Tegrak is 1.462 (if I recall correctly). If you want to go higher, you will need to run a custom kernel, such as Steady Hawkin's Team Rogue offerings (like "Gunslinger" or "Hitman"), and use SetCPU. On Calkulin's ROM, having SetCPU installed will disable his battery saving script, which underclocks the CPU at certain battery levels so keep that in mind. I doubt that will matter to you though as you're interested in overclocking not underclocking.
For voltages, I tend to boost the top two CPU steps by 25mv then test for stability. If I have issues then I boost by another 25mv and so on until it's stable (assuming I can get it stable). I'm not big on overclocking this phone though, as I really find no reason to do so. In fact I underclock the top end to 1000mhz and everything I do on the phone still flies.
Honestly though, I don't find Tegrak all that great for overclocking. It's nice for underclocking and changing your governor on a stock GS2 kernel, but not so much for overclocking. That's just me though. Others may find it suits them just fine.
I find that Tegrak is great for undervolting the stock kernel. It allows you to undervolt both internal and core voltages as well as undervolt the GPU and adjust scheduler and governors. If you interested in staying at the stock clock speed and undervolting then Tegrak paired with the stock rogue repack kernel is the way to go.
If you are wanting to overclock and undervolt then programs like setcpu, voltage control, or pimp my CPU paired with the Gunslinger or Whitman kernel are the way to go. As for the programs they all do about the same thing. The only real difference is voltage control uses a script to load you clock/voltage settings and the others have to load at startup and run. So its all preferences. Also both pimp my CPU and setcpu are available for free on xda under the apps section of android development.
I am also running "Gunslinger", I use Tegrak Ultimate to fine tune my o/c after I load the "Overclock Module" and can go about 1.67 at 1.475v before all hell breaks loose if I go higher on o/c or votage. I also use Tegrak to o/c my GPU I have that running at 400mhz at 1100mv. Now I use System Tuner Pro, for freezing apps you can also set votage it also has more tweaks then Tegrak and will show o/c on what ever Tegrak is set at, but System Pro does not have GPU o/c, so I use each other Tegrak/System Pro to really fine tune the GS2 and get the most out of it, if you know what I mean.
http://forum.xda-developers.com/showpost.php?p=14973796&postcount=531
Here is a good ballpark guide when using Tegrak.
Is it OK to run these two together? Will I lose the benefits of this kernel by running SetCPU? Will changing the governor affect anything?
Since the governors on classic are default, it should work the same...
Just remember using profiles has setcpu polling to see the status of your phone...so that does gave a draw on the phone, not much in the overall scheme of things, especially if you already use it, you are used to it.
The concern usually occurs if using custom governors, example Smartassv2 and a screen off profile in setcpu would be constantly fighting each other..negating any benefits of either.
I also do recommend since you're using SetCPU to manage your governors, frequencies, etc to move/delete the init.post_boot.sh file and the reasoning for this is because this file outlines several parameters for controlling your cpu at bootup and some of those settings include, a pre-determined governors polling intervals, up/down thresholds and min/max cpu frequencies so without deleting/moving this file and using SetCpu in conjunction with it, unstability can happen in the background due to your phone constantly going back and forward with itself because of too many apps/scripts telling it to do different things. Now if you're not going to use SetCPU I recommend not to touch this file. You can reference this Post
Good call.. I always forget to mention that file, I dropped using setcpu a long time ago, lol..
I am by no means an expert and always thought SetCPU was useful - I don't use it to overclock - just use it primarily to limit the processor when the screen is off. However, with ICS and Jelly Bean and the improvements related to it, is there still a need for SetCPU? Again, not just to overclock, etc, but to limit the processor when the screen is off to attempt to save battery. Thoughts?
I personally have felt no need for SetCPU once I upgraded from my first Android device - a MyTouch3G.
The schedulers in most custom kernels nowadays already throttle back the CPU speeds when the screen is off. As for overclocking, it IMO doesn't make any noticeable difference anymore so I don't even bother.
athakur999 said:
I personally have felt no need for SetCPU once I upgraded from my first Android device - a MyTouch3G.
The schedulers in most custom kernels nowadays already throttle back the CPU speeds when the screen is off. As for overclocking, it IMO doesn't make any noticeable difference anymore so I don't even bother.
Click to expand...
Click to collapse
But, what if you don't use the scheduler in the custom rom, is SetCPU still redundant?
I use it to set the voltages. If the hotplugx worked well with it I'd use it for profiles but unfortunately it'll crash.