Root KaosFroyo + SetCPU

[crandroid]

I know that kaos is OC'd to 710 by default, but has anyone tried setting their main SetCPU profile to a lower frequency? Tonight I lowered mine to 245/528 to see what it'd be like, and I honestly haven't noticed much of a difference. Maybe some of my LauncherPro animations aren't as smooth, but that might just be in my head.

Haven't tested this beyond a few hours or with heavy multitasking, but I think I might run with it for a while and see what happens.

UPDATE: Getting Linpack scores around 3.5, which isn't as high as the 4.5+ I was getting before, but is just as high as or higher than the scores I've gotten on most other ROMs (including xtr).

 

[Podivin]

I did the same thing on mine, the exact same settings in fact, and ran it that way for 24 hours. I could see some slow down in the way programs loaded (I'm talking about 1/2 second delays here, nothing huge), but that's about it. I did see a fairly dramatic improvement in battery life. Where I would have been at about 50% battery previously I was at 63% with these settings - ymmv of course.

 

[erisuser1]

Go into the "Info" tab in setCPU and scroll down about one page.

There is a section there which reports "Time in State".

I'm not sure what the units are (my phone has been booted about 23:20, and I have a total of about 565,000 counts in there - so they are not microseconds or miliseconds - it works out to about 150 milliseconds/count - perhaps "jiffies"? )

In any event, if your phone was "stuck" at 245 Mhz, you would see no counts in the frequency slots below that. I'm not sure you can stare at the phone when the screen is on to see if any counts accumulate in the lower frequencies - you need to sleep the phone long enough that the sleep profile takes effect.

eu1

 

[ExcessiveIdling]

I've lowered my clock speeds back down to default aka 528/245 and have not noticed any slow downs. Kaos is doing this as well and he as well has not noticed any slow downs but a slight increase in battery life. Goes to show better programming>overclocking. REALLY you don't need to OC!

 

[Frisco]

Goes to show better programming>overclocking. REALLY you don't need to OC!

+1

Overclocking was one of the Huge Hopes of Eris users in the months and weeks prior to root being discovered, I dare say it along with getting rid of unwanted stock apps were the Two Biggies.

Zach's xtrROMs cured me of overclocking, but it's turning out to be over rated for other ROMs as well.

Having said that, I'm not so sure about the earlier 2.2 ROMs and perhaps even v30 of Kaos and the latest Nonsensikal, as there was quite a difference in perceived menu and app loading times between the fast xtrROM 3.0.3 and those Froyos on my device.

But that may speak more about the speed of xtrROMs than those others.

What is interesting is that we've seen reports of the 2.2 ROMs seeming faster than most 2.1s on some Erises. What the developers do with the kernel, setting things to default to 710 or so, might be showing itself there.

 

[LED]

I'm now running KaosFroyo v30 at 528/245 (was running 787/480). I also don't see much, if any, degradation in performance. I think AutoKiller has helped keep things running smooth. I was adamant that OC was needed when I was running v28 (pre autokill).

 

[crandroid]

I'm also running v30 still, so I'm looking forward to seeing if the framework updates in v31 make this even smoother. I may just be done with overclocking for good!

 

[Frisco]

I may just be done with overclocking for good!

I swore it off.

My battery is grateful.

 

[LED]

I wonder if ditching SetCPU all together would be beneficial in regards to battery life. Underclocking may not be overcoming the battery drain that is needed for running SetCPU as a service (i could be wrong).

 

[Frisco]

I wonder if ditching SetCPU all together would be beneficial in regards to battery life. Underclocking may not be overcoming the battery drain that is needed for running SetCPU as a service (i could be wrong).

It's not installed in my default ROM.

I have it in both Froyo ROMs, though. I'm still wavering on that.

 

[LED]

It's not installed in my default ROM.

I have it in both Froyo ROMs, though. I'm still wavering on that.

I think I'm going to uninstall it and see how it goes. I'll have a good idea next week what kind of impact it has, because I'm very consistent with my phone's usage while at work.

 

[Frisco]

Yeah, nothing like running it for a long time both ways.

I only briefly had it in xtrROM 2.1.1 and 3.0.3.. it was funny; I could have swore that overclocking slowed both versions of that ROM down.

 

[Praetorian]

I decided to try out KaosFroyo again with all the tweaks that Frisco and others have suggested plus setting setcpu to 245/528 with launcherpro and I have to say I'm loving it. The rom has been running great all day (once it stopped syncing). I tried running Kaos a few versions ago with ADW and I couldn't take the lag. I'm curios to see how the battery life will be over the next few days.

 

[LED]

I know this is premature to draw any conclusions from, but after un-installing setcpu yesterday, I've been off the charger for 18h2m and battery went from 100 to 98 in that time. I haven't really used the phone (read a few emails and listened to a couple vm). Normally I would lose 3-4% overnight (~8 hours).

I'll have a good idea tomorrow when I'm back at work if there's truly a difference.

 

[Praetorian]

So far I am freaking loving Kaos with 245/528. Its running as fast as xtr so far and my battery life is great. I thought I would miss the sense widgets but who neads a giant clock with the weather anyways? This may seam weird but the best thing I love about this is the pin number for the unlock password. On 2.1 I always have to click the password field and type in a word or switch to numbers but with this I just enter my pin and I'm off.

 

[rick311]

ive gotten 1 day 19 hours without a charge with moderately heavy use. i think i'll keep setcpu with my kaosfroyo.

 

[jxw384]

hi, im sorry if this has been asked already. i have a droid eris with kaosfroyo 32 ... i just downloaded setcpu and was wondering what the ideal settings are for speed and good battery life. thanks so much!

 

[doogald]

hi, im sorry if this has been asked already. i have a droid eris with kaosfroyo 32 ... i just downloaded setcpu and was wondering what the ideal settings are for speed and good battery life. thanks so much!

"Ideal" would be very subjective, but I have very good performance a great battery life with these settings:

default: 245/604 (I have also run 245/528 and may be ok - try it)

profiles:

temp>40c: priority 100, 160/480

screen off: priority 80, 19/480

charging ac/full: priority 75, 245/528 (note: I only charge when I am not using the phone. If you use it while charging, you can bump up that max as well)

battery <33%: priority 70, 160/528


Advanced:

sampling rate: 40,000
up threshold: 50 (adjust this up for better battery, down for better performance)
ignore nice load: 0
powersave bias: 0 (you can adjust this up if you want better battery life)

 

[Frisco]

hi, im sorry if this has been asked already. i have a droid eris with kaosfroyo 32 ... i just downloaded setcpu and was wondering what the ideal settings are for speed and good battery life. thanks so much!

You'll find something akin to your own ideal by experimenting, testing settings left intact, over time.. say three to five days as long as you're not seeing force closes, heat, rapid battery depletion or other anomalies.

Those who post what settings they have success at are telling you about their device, their usage and their personal tolerance and perception for things like app and menu opening speeds, etc; yours will vary, and likely quite significantly.

 

[jxw384]

ok then i guess a better question is, where should i stay between? is there a min and max i should not go above or below?

 

[Frisco]

ok then i guess a better question is, where should i stay between? is there a min and max i should not go above or below?

Max: 729

Min: 245

Sleep: 528 Max - 245 Min

You'll see reports saying higher on the max and lower on the min; I am giving you my tested and personally experienced ideals from the days when I went for days on one setting before changing one way or the other (with the exception of the time I went too high and froze my device up).

I should add this, jxw: I no longer overclock any ROM, as I see only one noticeable difference, degraded battery life (please see post #5).

Most modern 2.2 (Froyo) ROMs have the kernel overclocked at 710, by the way.

 

[rick311]

a lot of people have noticed no change in performance with going BELOW 710. im testing mine and have my max at 604 and have noticed no lag and better battery life.

 

[jxw384]

my main reason for setcpu is for the battery. i find the battery life on the eris to be awful. what are good settings for best battery? also is autokiller or anything like that necessary?

thanks

 

[Podivin]

I agree with SetCPU for battery life purposes.
Personally I don't over clock, I've found the ROMS that I like have decent speed without OCing. I'll not have any setting over 528. And I'll have a sleep setting that is way low - as low as the phone will stand without lagging upon wake - I've used as low and 128/245 - try different settings to see which ones suit you best. If your phone lags when you wake it up increase the sleep speed a little.
For the default speed I use 245/528.

As always, YMMV.

 

[doogald]

Max: 729

Min: 245

Sleep: 528 Max - 245 Min

You'll see reports saying higher on the max and lower on the min; I am giving you my tested and personally experienced ideals from the days when I went for days on one setting before changing one way or the other (with the exception of the time I went too high and froze my device up).

I think that these are very reasonable, though I'm tempted to tell people not to go above 710. 710 seems to be dead-safe; you do read about problems that people have if they go higher, and there seems to be very little added real-world speed from higher clock speeds than 710.

Also, as I said in an earlier post, on Kaos Froyo I get absolutely no lag on waking the phone from sleep if the minimum on a sleep profile is set to 19.2. The same is not true for 2.1 ROMs - with those, I need to have 128 minimum as the slowest speed.

The best thing to do, though, is to try on your own phone and see how it responds. If, for example, you play music in the background with the screen off, you will probably not want a minimum of 19.2. I never play music on my phone, so that is not an issue for me, but others report skipping if they are set that low.