Develop Bugs

Sticky UI w/ SetCPU & Kernels

Does anyone notice that SetCPU with kernels such as Hydra (1.15 uvoc) and King’s (#2 1.19) causes home screens and apps in drawer to scroll stickily?
I've ran both at max oc and it occurs. I know Hydra does not recommend setcpu. When I force stop setcpu with both kernels the problem goes away and the UI moves fast and slick.
Is there a way to have the benifits of SetCPU's Profiles while making the phone run fast and smoothly as when I force stop SetCPU???
Also are the battery drain problems that are plaguing people due to us using non-stock kernels... or us using oc kernels without SetCPU???

Personally, I've had nothing but disappointments with setcpu. Currently running kingklicks kernel #3 without setcpu. Plenty fast enough for me and better battery life than stock. I think the stock governor does a better job than setcpu.

D3vr04 said:
Does anyone notice that SetCPU with kernels such as Hydra (1.15 uvoc) and King’s (#2 1.19) causes home screens and apps in drawer to scroll stickily?
I've ran both at max oc and it occurs. I know Hydra does not recommend setcpu. When I force stop setcpu with both kernels the problem goes away and the UI moves fast and slick.
Is there a way to have the benifits of SetCPU's Profiles while making the phone run fast and smoothly as when I force stop SetCPU???
Also are the battery drain problems that are plaguing people due to us using non-stock kernels... or us using oc kernels without SetCPU???
Click to expand...
Click to collapse
Kingklick scaling is as good or better than creating profiles in setcpu. Using kingklick# 2 and# 3 as is has improved battery life greatly for me. I posted some" light use" battery life results in the kingklick thread and during the test period I was using setcpu to test the scaling abilities of kings kernal. Overclocking is overrated and setcpu doesn't play nice most of the time anyway. Use kingklick# 3 or# 2 as is and you should get good results. If not, im not much help. If you can't get kings kernal to be stable at least use an undervolted kernal.
Sent from my ADR6300 using XDA App

Thatnks Sam. I agree. But I'm using #2 without setcpu. Its fast and smooth. Better Quad and Lin scores for me than #3 (currently trying) though but not significant. I'll see how it handles battle before I revert to #2
@Inc
I've been using king's #2 its performance is great. smooth without setcpu. What is the default speed of his kernels 2&3(oc1.19G) without setcpu?
Btw I'm running same phone configuration as your signature.

How do you over clock?

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.

[Q] cm7 and setcpu update

[Q] cm7 cpu setting or setcpu?
well atm i am running an evo 4g with cm7 and i just switched my kernel to savaged zen and it's running great. my phone was rebooting on its own w/ the regular cm7 kernel i think its b/c i was using setcpu and people are saying it messes up cm7.
so i was wondering if anyone knew if i can use setcpu with cm7 and savaged as the kernel or if it's possible to make profiles on the cpu settings on cm7 i saw some1 post somewhere that you can but they never explained how.
p.s. please also visit this thread on battery life

AFirst of all, all SavagedZen kernels are Havs kernels (as far as I remember, I'll double check in a few). Anyway, if you are using a Havs kernel, changing cpu settings is pointless/counteractive. I would either leave the settings alone or switch to a no-havs kernel. You can check in settings>about phone.
EDIT: However, if you must mess with the settings, you can find them in Cyanogenmod Settings under Performance Settings. I don't know of a way to set profiles from that screen, though - only max/min & governor.

hi i have an evo running cm7 and i had setcpu and my phone kept restarting however i looked up setcpu again in the market and it said that they just ran an update to stop the problem with cm7, does this mean that setcpu is better to use than the cpu setting in cm7?

Green_Arrow said:
hi i have an evo running cm7 and i had setcpu and my phone kept restarting however i looked up setcpu again in the market and it said that they just ran an update to stop the problem with cm7, does this mean that setcpu is better to use than the cpu setting in cm7?
Click to expand...
Click to collapse
You shouldn't need setcpu use the cpu setting in cm7. They put it there for a reason, those guys are sharp!

I still use setcpu because I like my screen off profiles etc. You should update your setcpu if it prompted you to. I think the latest changes were for cm7/GB.
Sent from my PC36100 using XDA Premium App

Yes but it doesn't let u make profiles unlike setcpu, or does it?
I believe the profiles is definately the most useful
Sent from my PC36100 using XDA Premium App

It says it was for cm7
Sent from my PC36100 using XDA Premium App

I believe the SavageZen governor is a specially tweaked/optimized version of the SmartAss governor.
And if you use Smartass/SavageZen governor, I think it also automatically undervolts when sleeping, and essentially mimics what a screen-off profile in SetCPU would do.

plainjane said:
AFirst of all, all SavagedZen kernels are Havs kernels (as far as I remember, I'll double check in a few). Anyway, if you are using a Havs kernel, changing cpu settings is pointless/counteractive. I would either leave the settings alone or switch to a no-havs kernel. You can check in settings>about phone.
EDIT: However, if you must mess with the settings, you can find them in Cyanogenmod Settings under Performance Settings. I don't know of a way to set profiles from that screen, though - only max/min & governor.
Click to expand...
Click to collapse
but how exactly does havs control battery usage? and if i use setcpu wouldn't the havs not function only setcpu will function b/c of priority?

serdna75 said:
I believe the SavageZen governor is a specially tweaked/optimized version of the SmartAss governor.
And if you use Smartass/SavageZen governor, I think it also automatically undervolts when sleeping, and essentially mimics what a screen-off profile in SetCPU would do.
Click to expand...
Click to collapse
how do u use Smartass/SavageZen governor?

Threads Merged... please post your question once.

Green_Arrow said:
how do u use Smartass/SavageZen governor?
Click to expand...
Click to collapse
In CM Settings, go to Performance Settings & then CPU settings. Under available governors choose SavagedZen or Smartass. I'd try them out & see which you like the most. I prefer SavagedZen, I seem to get better battery life & performance.

egzthunder1 said:
Threads Merged... please post your question once.
Click to expand...
Click to collapse
Thanks, sorry its my 2nd day on this forum

plainjane said:
In CM Settings, go to Performance Settings & then CPU settings. Under available governors choose SavagedZen or Smartass. I'd try them out & see which you like the most. I prefer SavagedZen, I seem to get better battery life & performance.
Click to expand...
Click to collapse
thanks atm im using the savagedzen, and jw is autokiller memor optimizer useful now or not?

Green_Arrow said:
thanks atm im using the savagedzen, and jw is autokiller memor optimizer useful now or not?
Click to expand...
Click to collapse
Personally I have never needed a task killer while on CM7, so I am going to recommend against it.

Well I had talked to someone else that is using it like that and they said they get amazing battery life
Sent from my PC36100 using XDA Premium App

I say no toward any kind of task killer. First of all, they're pointless. You're killing stuff that isn't using any power to begin with, which then restarts anyway. The task killer itself is actually doing something, running on a set schedule, where as the tasks you're killing are just sitting in memory for faster opening.
It bugs me that even the techs at Sprint recommend it, so every person that doesn't know anything about how their phone works thinks it's necessary. Then in the market for every clock widget you see everyone going "like zomg the clock doesn't keep time your app sucks 1*" because the damn task killer is killing it. That's if they can even figure out how to use it & not complain that it "won't open", despite clear instructions on how to put a widget on your screen.
Sorry, totally went off on a rant there.
But yeah, stay away from task killers & let Android do its job. You don't have to have a ton of memory free for your phone to run perfectly fine under normal usage. I don't notice a difference between 300mb & 50mb free. If you don't worry about it, you won't either.
Free memory does not equal more battery.

plainjane said:
I say no toward any kind of task killer. First of all, they're pointless. You're killing stuff that isn't using any power to begin with, which then restarts anyway. The task killer itself is actually doing something, running on a set schedule, where as the tasks you're killing are just sitting in memory for faster opening.
It bugs me that even the techs at Sprint recommend it, so every person that doesn't know anything about how their phone works thinks it's necessary. Then in the market for every clock widget you see everyone going "like zomg the clock doesn't keep time your app sucks 1*" because the damn task killer is killing it. That's if they can even figure out how to use it & not complain that it "won't open", despite clear instructions on how to put a widget on your screen.
Sorry, totally went off on a rant there.
But yeah, stay away from task killers & let Android do its job. You don't have to have a ton of memory free for your phone to run perfectly fine under normal usage. I don't notice a difference between 300mb & 50mb free. If you don't worry about it, you won't either.
Free memory does not equal more battery.
Click to expand...
Click to collapse
but doesn't free memory mean less things are running or even being used just a tad bit which does mean a better battery life?

Green_Arrow said:
but doesn't free memory mean less things are running or even being used just a tad bit which does mean a better battery life?
Click to expand...
Click to collapse
No. Memory has nothing to do with battery.
Screen, radios, and CPU use battery and that's about it.
Sent from my PC36100 using XDA App

matt2053 said:
No. Memory has nothing to do with battery.
Screen, radios, and CPU use battery and that's about it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So do u agree w/ system panel/juice defender?
Sent from my PC36100 using XDA Premium App

Safe under and overclock for Desire Z?

What are the safe/stable clockspeeds for underclocking and overclocking my Desire Z? Also, what app do I use? Like, I don't mind paying for the app (as long as it's not too expensive)
Sent from my HTC Vision using XDA App

SetCPU can be used to overclock if you're rooted. Depending on the ROM and Kernel combination, overclocking to about 1.3ghz is usually safe. Some go up to 1.5ghz or even 1.8ghz, but are often quite unstable depending on other configurations you have in your ROM.
As far as underclocking goes, some custom kernels clock all the way down to 122mhz, I've been using a streamline5 kernel on CM7 (which offers 122mhz min) and haven't had any ill effects with this.

I have the Virtuous Sense ROM (with it's default kernel, although it does have other kernels which can give other cpu speeds), right now but might try out another ROM soon (maybe) do you know what's the min and safe max for this ROM?
Also, can I just set a particular clock speed (e.g. 500MHz) and it should be ok or is there any stability difference between say 500MHz and 505MHz? Just curious. I looked at SetCPU and it looks like a good one. Also, if the clock speed I set makes things go wrong, can I revert it or can I get stuck with it and need to do a wipe?
Sent from my HTC Vision using XDA App

zaghy2zy said:
I have the Virtuous Sense ROM (with it's default kernel, although it does have other kernels which can give other cpu speeds), right now but might try out another ROM soon (maybe) do you know what's the min and safe max for this ROM?
Also, can I just set a particular clock speed (e.g. 500MHz) and it should be ok or is there any stability difference between say 500MHz and 505MHz? Just curious. I looked at SetCPU and it looks like a good one. Also, if the clock speed I set makes things go wrong, can I revert it or can I get stuck with it and need to do a wipe?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
No, there's no need to set a particular clock speed. Just whatever works for you. I wouldn't recommend going under 800mhz, as the phone will really really bog down even with normal use.
I haven't used that particular ROM, but I'm assuming anywhere around 1.3ghz should be safe on the upper limit. Like I said before, anything above that might start to cause issues. You might also want to consider the battery life implications of severe overclocking.
You can change the clock speed any time you want. If you're having wakeup or heat or any other issues just go back to SetCPU and change the max clock speed again. You can also use profiles in SetCPU to change the clock speed when the phone is overheating, or when the screen is off, or when the battery gets to a certain %. There are tons of posts detailing how others have setup their SetCPU profiles.
One last note, don't forget to check the box for "Set on Boot" in SetCPU, this way your changes aren't undone on reboot.

Thank, I think I got everything I need to know in your last reply

I'm on CM7, with the CM7 kernel, and clocked in at 1.5GHz, and have no problems, and the rom is super fast. And I use SetCPU.

[Q] MIUI Set CPU settings

Whats up guys? I have a question about using the Set CPU app.
Is it really worth it to use this app? Will it actually make an improvement in my battery life?
I don't want to use this app to speed up my phone, but to make it better on battery life.
I know you can set up profiles, but I'm not sure on what good setting would be to use. Can anyone give me some insight on this?
Also I'm running the latest version on MIUI and the Tiamat kernel.
P.S. Is there better kernels to be used then Tiamat?
Thanks in advance.

also I'm running the latest version on MIUI and the Tiamat kernel.
Click to expand...
Click to collapse
maybe it's just me, but am getting better bat life with the stock kernal. I ran the tiamat for a few days, switched back and it was obvious to me.

With Tiamat the default governor is smartass, which has a built in setting for when the screen is off, that only lets the phone see a max of 368640, which will save on battery life and does.
Now if you want to get into using your own profiles then an app such as Setcpu can be helpful.
I have been using this and this in place of Setcpu. It's a little faster reacting to the changes form screen off to on. Just another option.
I like the Tiamat Kernels as well as JD's Kernels. They both work well with Miui, at least on my phone anyway.

I've used Set CPU for awhile, but then got away from it. I'm back on it now since MIUI doesn't have a built in OC. I would try the two PacerguyDon suggested. I have used the andrev_oc it is fine. The second one appears to have more functions than Set CPU. Set CPU doesn't allow you to under volt if that is what you are looking for.
I saw that Set CPU is $0.99 on Amazon, if you want it. However, I would try the other two for free and donate to the one you like best.
I have been using JD's Kernel the last few days and it seems to provide better battery life than stock. I originally tried using the Smartass govenor, but had to go back to On Demand. The Smartass was causing screen wake delay when receiving a call.
I stole this from another PacerguyDon's post and it breaks down the different govenors found in most OC apps.
Govenors

Set CPU is free for XDA members. It also does allow undervolting according to their post.
http://forum.xda-developers.com/showthread.php?t=505419