Related
Does anyone know how to over clock you're DI to say 1.2? Thanks for any help.
You first need to root your phone, then install a kernel that is compatible with whatever rom you are using, then you need to install an OCing app like SetCPU and adjust accordingly.
I'm rooted running the 2.2 RUU and I have set cpu. So do I just need a kernal? Which one?
i reccomend King Kernel bfs #4, best freaken kernel ever... its located... here
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
makos101 said:
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
Click to expand...
Click to collapse
A lot of factors come into play when you start overclocking, every rom will respond differently.
The first thing to do before anything is to do a complete nandroid back up.
When overclocking keep in mind that the more you overclock the more chances you have of making your system unstable.
I have experimented a quite a bit and I have found that the King Kernal #4 seems to work well for me and at 1.2 it seems to be pretty stable. Any higher than that and my phone will sometimes re-boot itself for no apparent reason.
Again, your rom may handle things different so experiment and see what works best for you.
And remember - Do a complete backup first!
I'm using the number 4 kernal and it only goes to 1.19 is this what you mean by 1.2? I have to keep mine at 1.1 ghz at 1.19 my di gets unstable
Ya that's as high as they can oc these chips. I can only get to 115 safely 119 just crashes. But the charging experience will be better than stock with the BFS #4.
Sent from my ADR6300 using XDA App
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
makos101 said:
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
Click to expand...
Click to collapse
If you are experiencing slow wake up, try increasing the min cpu speed to something around 460. Better batt life and increased speed takes a lot of experimenting. Your OC speed might differ from others due to differences in the phones cpu. For example, I have never been able to oc to 1.19 without the phone freezing or rebooting. My phone can handle 1152 but 1113 is perfect. In my opinion, ROMs have something to due with best batt-speed combo. I am running Ruby 1.1.1 with a setcpu profile of Screen off=245 without any wake lag. Other ROMs I have tried had wake up lag at that speed profile.
My set up:
(ROM-ASOP) Ruby 1.1.1
King's #1 ASOP "I told you so"- only works with ASOP
With the ROM's "Gem" performance scaling setting off, I use setcpu to OC to 1113, min is 245. I have a profile set to SCREEN OFF = 384 max/245 min.
I haven't worried about battery life since I started using King's kernals (I've tried them all with every compatible ROM on xda). I have several posts elsewhere on XDA showing 12 plus hours on a single bump charge and heavy phone use. Good enough for me. Stock cpu speed plus Sense ROM seems slow to me now.....to each his own though.
I hope to get some help because i value the opinions of those on this forum. Currently i am running virtuous 2.7 with virt. kernal v2. I am rooted, s-off, 2.15.xx radio. I want performance without draining my battery. What are the best settings to use in setcpu?
I did try king's kernal #4, but it was rebooting. switched kernals this morning.
One other app I use in conjunction with SetCPU is MinFreeManager. This will readjust your free ram to a higher standard. But with SetCPU I have it at 1113/Ondemand with no custom profiles. One other thing I really don't set is the Set on Boot option. I don't know why but I do. So with SkyRaider Vanilla 3.0 RC3/ KingX Kernel #4/ and MinFreeManager my phone fly's. I can't say for certain what settings you need for your phone but 1113-1115 is preferred by "most" phones and keep the set on boot option off. I keep a Galaxy S live wallpaper running and pandora while browsing the web and no lag what-so-ever.
CyanogenMod 6.0.2 and KingX kernel #1 with the same setup runs almost as smooth.
Hope this helps you out.
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?
Hi,
I have installed and added setcpu profiles but i am not sure they are correct choices for me. I have virtuous unity rom with v4 kernel.
ac charging 1.7 ghz max
Battery under 70 1.5 ghz max
Battery under 50 1.2 ghz max
Battery under 30 1.0 ghz max
Temperature over 50 800 mhz max
(All of profiles have minimum 368mhz of speed)
All of them are ondemand but i dont know when to use conservative. And are these clock speeds good for us?
Can you help me about this?
Sent from my HTC Vision using XDA App
If youre using virtuous unity, you shouldnt use setcpu and use the virtuous overclock app. Its essentially the same but virtuous oc is much faster in changing your speeds.
My speeds for virtuous oc are:
Max wake: 1.5ghz
Min wake: 245mhz
Governer: ondemand
Max sleep: 368mhz
Min sleep: 245mhz
Governer: conservative
Sent from my HTC Vision using XDA App
I'm using CM7 Nightly
Latest Umaro kernel
Screen off = 280/380 powersave
<101% = 280/1.7 ondemand
<40% = 280/800 conservative
charging = 1.0/1.7 performance
temp >50c - 280/380 powersave
I don't.
As stated in the Unity notes (on their website), and as evilcuber mentions:
Virtuous overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
http://www.virtuousrom.com/p/unity_23.html
redpoint73 said:
I don't.
As stated in the Unity notes (on their website), and as evilcuber mentions:
Virtuous overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
http://www.virtuousrom.com/p/unity_23.html
Click to expand...
Click to collapse
I was using setcpu to see momentary clock speeds then decided to create profiles. So it is better to stay with virtuous OC application. I want to ask another question; does sleep clock speeds of cpu effect waking up time?
redpoint73 said:
I don't.
As stated in the Unity notes (on their website), and as evilcuber mentions:
Virtuous overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
http://www.virtuousrom.com/p/unity_23.html
Click to expand...
Click to collapse
Same here, on CM7 though (which has a built in CPU setup). I haven't used SetCPU in months. 806mhz max / 245mhz min, OnDemand governor. One less app running, the same or better battery life, and no sluggishness with profiles.
Deadly Sto(R)m said:
I want to ask another question; does sleep clock speeds of cpu effect waking up time?
Click to expand...
Click to collapse
It can. If you set a low screen off profile like 245/245 or 245/368, your phone may lock down and not wake up properly, or take time to "speed up" when you unlock the phone, which can sometimes be noticeable depending on your phone setup.
martonikaj said:
Same here, on CM7 though (which has a built in CPU setup). I haven't used SetCPU in months. 806mhz max / 245mhz min, OnDemand governor. One less app running, the same or better battery life, and no sluggishness with profiles.
It can. If you set a low screen off profile like 245/245 or 245/368, your phone may lock down and not wake up properly, or take time to "speed up" when you unlock the phone, which can sometimes be noticeable depending on your phone setup.
Click to expand...
Click to collapse
the best way is "try and see what happens" I ill try low screen off speeds and try if the hone wake up late. if so, i am going to get clock speeds higher then it was.
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