Alright, so set cpu has been updated and it says it has a beta setting for the evo. I was reading through the comments and one of them says that setcpu is only for controlling the cpu speed from standard 1ghz and lowering. If i wanted to overclock to 1.2(I think that's the highest i've seen around) I would have to get a custom rom. So.. i have baked snack v7... is that what they are considering a custom rom? or do i have to have a supported overlcock custom rom. then i use set cpu to control the cpu speed.
?
hah thank you.
derik123derik123 said:
Alright, so set cpu has been updated and it says it has a beta setting for the evo. I was reading through the comments and one of them says that setcpu is only for controlling the cpu speed from standard 1ghz and lowering. If i wanted to overclock to 1.2(I think that's the highest i've seen around) I would have to get a custom rom. So.. i have baked snack v7... is that what they are considering a custom rom? or do i have to have a supported overlcock custom rom. then i use set cpu to control the cpu speed.
?
hah thank you.
Click to expand...
Click to collapse
You can only overclock the CPU by using a custom kernel, and at this point in time you lose camera
http://forum.xda-developers.com/showthread.php?t=686240
and everything is good except Set CPU is not having any effect on the cpu. My cpu is not resting...bouncing all over the place. Any suggestions?
PS, I've used OS monitor and SysPanel to try and figure it out. I've killed everything possible but the Set CPU meter if flipping out.
You need a kernel that allows it. And the stock 2.2 does not.
Disabling Perflock
Maybe your answer is at the setCPU documentation site on chapter 10: Disabling Perflock:
“On most stock HTC kernels and some custom kernels, HTC has enabled a driver called "perflock" that constantly resets SetCPU's Max and Min settings”
Sorry I’m new here and still can’t publish URLs, but look for "HTC Dream: G1 > G1 Apps and Games > SetCPU for Root Users [2.0.1] This *actually* changes everything. 07/05/2010"
has anyone tested perflock disabling with the 2.2 rom? i thought about doing it, but dont have the time to test today.
Disabling perflock with setcpu does not work on the stock 2.2 kernel, I read somewhere that the kernel doesnt even use perflock ... don't quote me on that though.
ifly4vamerica said:
Disabling perflock with setcpu does not work on the stock 2.2 kernel, I read somewhere that the kernel doesnt even use perflock ... don't quote me on that though.
Click to expand...
Click to collapse
I've seen others mention that this kernel doesn't have perflock either but until I see some proof I say they don't know what they're talking about. SetCPU is having no effect so good chance perflock is in place and working the same the same as ever.
Furthermore I don't see why HTC would remove it, it prevents non-root users from possibly burning out their CPU from overclocking.
Using Netarchy's latest 2.2 kernel
All is well now!
masbirdies said:
All is well now!
Click to expand...
Click to collapse
Don't you lose camera quality and other things with that kernal?
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?
My SetCPU has only about 3-4 different frequency options between 806Mhz and 245 MHz. Is there any way to increase the number of options between these two frequencies?
andersonjacob54 said:
My SetCPU has only about 3-4 different frequency options between 806Mhz and 245 MHz. Is there any way to increase the number of options between these two frequencies?
Click to expand...
Click to collapse
U have to root your phone and flash some ROMs depending on which type of rom do you like, it comes with kernels for overclocking or you can flash one if you want to. Rooted stock rom doesn't have any compatible kernels it breaks some stuff so you really need to use a different rom..
Fly like a G2
jojo_16 said:
U have to root your phone and flash some ROMs depending on which type of rom do you like, it comes with kernels for overclocking or you can flash one if you want to. Rooted stock rom doesn't have any compatible kernels it breaks some stuff so you really need to use a different rom..
Click to expand...
Click to collapse
Well if he's using SetCPU then he's already rooted, so he's got that covered.
OP as jojo stated, you need a custom kernel to allow overclocking. A lot of people seem to be fond of Pershoot's OC kernels, but I personally just use the one thats included with CM6 and now CM7. It allows an overclock up to 1.5ghz.
martonikaj said:
Well if he's using SetCPU then he's already rooted, so he's got that covered.
OP as jojo stated, you need a custom kernel to allow overclocking. A lot of people seem to be fond of Pershoot's OC kernels, but I personally just use the one thats included with CM6 and now CM7. It allows an overclock up to 1.5ghz.
Click to expand...
Click to collapse
I think he's wanting to know how to add more underclock frequencies. It can be done but you have to decompile the kernel in order to do it and also have decent knowledge of voltage tables (since the purpose of underclocking is to save battery power you have to uv also). Probably well beyond most peoples comfort level however, if the op still wants to attempt it are numerous threads with info - just search for something like 'creating a custom kernel' or 'make a kernal'. One of them is located in the G2 development forum.
Oh ok thanks guys. Yeah, I have Pershoot's kernel so that is not a problem. I was trying to include more underclock frequencies, but if that means editing or creating my own kernel then forget it lol, I'm no expert on that.
andersonjacob54 said:
Oh ok thanks guys. Yeah, I have Pershoot's kernel so that is not a problem. I was trying to include more underclock frequencies, but if that means editing or creating my own kernel then forget it lol, I'm no expert on that.
Click to expand...
Click to collapse
There's a turbo ROM that can deep fry your G2 to 1.8ghz, and it has a lot more frequencies below 806.
Fly like a G2
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.