Database Users

Overclocking with Jrummys?

I just downloaded Jrummy's Overclocker and i was wondering what are some settings for a safe overclock. im shooting for 1.2

gkallivrousis said:
I just downloaded Jrummy's Overclocker and i was wondering what are some settings for a safe overclock. im shooting for 1.2
Click to expand...
Click to collapse
1.2 should be no problem although all phones are different. start with the low voltage at 1.1 make sure the phone is stable. a quick test is to open the browser and load a few pages. a GOOD test is to run quadrant. then just increase the speed until it locks up. pull the battery and set it down 1 or 2 speeds and thats your max stable overclock at that voltage. most people are able to run 1.2 or 1.3 with no issues. i can run at 1.3 with no issues. any higher and after a few days (or less respectively) my phone hangs. Also increasing voltage will yield higher clocks but will drain the battery faster. just play around if the phone locks up just pull the battery. also i would not play with the manual settings until you are familiar with the basic ones first.

I am most stable at 1.25ghz LV. Currently running GummyJAR2.5 with Blueberry Theme.
No issues. I would recomend installing AutoKiller. This is not same as Task Killer. It frees up memory. Same function as the one that comes with Jrummy Overclock but you can customize it more.

auto killer waste battery we have plenty of memory on our phones

so what do you recommend for a jrummy oc? i was thinkin 1.2 on lv

I can only get up to Low volt 1.15 otherwise. Once I click on anything higher i get a MAJOR hanging as soon as its done overclocking. pissed but guess thats just the point that all phones are different.

friguy3 said:
I can only get up to Low volt 1.15 otherwise. Once I click on anything higher i get a MAJOR hanging as soon as its done overclocking. pissed but guess thats just the point that all phones are different.
Click to expand...
Click to collapse
yup...some people can run 1.4 with no problems...try upping the voltage a little

1loudsvt said:
auto killer waste battery we have plenty of memory on our phones
Click to expand...
Click to collapse
I wasn't a believer until I installed it. My ram use to run low and some times made my DX run slow. Since installing the autokiller, my DX runs smoother, zippier and consistant. I have mine pre-set at extream. As for the battery, I don't notice any difference and I am semi heavy user. I been running Autokiller for a while.

Hey guys, I recommend using QuickClock Advanced for some real battery savings. It calculates the lowest stable vsel your cpu can handle and then you can overclock from there.
my settings
300mhz 15vsel
600mhz 30vsel
900mhz 45vsel
1200mhz 61vsel

I could never get over 1.1 using jrummy untill I changed the gov, use anything but "on demand" and I can get 1.4 all day. The stock settings work well using the "performance" gov but battery life can suffer if you get crazy. Performance keeps it running at top speed all the time. Hope this helps.
Sent from my DROIDX using XDA App

Droid-Xer said:
Hey guys, I recommend using QuickClock Advanced for some real battery savings. It calculates the lowest stable vsel your cpu can handle and then you can overclock from there.
my settings
300mhz 15vsel
600mhz 30vsel
900mhz 45vsel
1200mhz 61vsel
Click to expand...
Click to collapse
Ive used similar settings and worked fine on my phone running Rubix.

Set cpu help/question

Ok so I have searched all over the forums and through google to find an answer to this and I can't any where so here goes. I am currently running the syndicate rom with the extreme kernal installed and when I go to use set cpu I have it set to conservative but any time I try to limit the cpu speed with the sliders it doesn't tae effect. The green numbers above the sliders will change stating my preferences but the white numbers that show the actual speed of the processor will continue to climb past my desired bottleneck. It looks like thecpu always stays between a range of 200 mhz and 1.2 ghz no matter what I set it at. If I change the style to something other than conservative it will change the behavior like performance will keep it at 1.2 or what I select and battery saver will keep it at the minimum. On demand and interactive seem to respond as well but are a little buggy and any little touch on the screen will make the processor jump straight to the maximum and stay there fr a bit which I would assume would kill my battery quite a bit faster. Does any one know if this is an issue with the phone, rom, kernal and if there is maybe a better settng than conservative or a different kernal I could use I was looking into the phoenix or fluff kernal. Any help or recomendations would begreatly appreciated. Thanks
Sent from my SPH-D700 using XDA App

Its been a long time since Ive used it (2.2.1 scales pretty good) if I remeber right,interactive is what you want to select,but on some kernels conservtive is what you want to select.I never used the profiles,I think they dont work all the time.

That's odd I never had that problem with syndicate. And I know for sure that almost every overclocking kernel recommends conservative, for some reason the other profiles can cause problems. There's a couple things that I've learned.
Conservative, for one thing, is never going to be an on demand setting. Typically it will just up the cpu to the max you set it at whenever there is some sort of activity on the phone. Which begs the question, what do you have the max set at? if its 1ghz, remember that the kernel is overclocked, so a setting of 1ghz will allow you to go to 1.2ghz. (I'm almost positive you don't want to set it at 1.2, because then it will peak higher than that) I think the max you set it to should be the listed physical limit of the processor (ours is 1ghz obviously), and the overclocking handles it from there (at least that's been my experience).
Also, remember that when there is no activity (your phones in your pocket), the cpu will be at your minimum. So you save battery in that regard, because with out setting cpu limits, like if you're running stock, I think it might run at the max all the time. (I don't that for a fact tho) again, we pretty much have to run conservative, (I've read its something to do with these hummingbirds and setcpu and overclock widget aren't built fot them) so its an all or nothing deal, you can't get "just enough" processor setting.
Try creating different conditions to help yourself out. When I had syndiccate I had a different setting for the screen being off, for being plugged in to a wall, for being plugged in to a computer, and for being below a certain battery %. Those are really cool features and help out a lot.
And as far as other roms...I use baked snack right now with his ultimate kernel. Its only sllliggghttly less stable than syndicate (but most most most defintly stable enough for a daily driver), and I get much better battery life and performance. He recommends using overclock widget, which isn't as flexible as setcpu, but defintly gets the job done. You'll have to google baked snack and find his website since they kicked him off of here.
Hope that helps, let me know if I didn't quite answer your question correctly.
Sent from my baked and emotionless SPH-D700

From my experience,you need to set it to 1.2 to activate OC...That being said,there are some kernels that need the interactive setting to work right...and 2.2.1 scales to the lowest setting when screen off even without setcpu,thats why I dont use it anymore.I will again once we have an official OC kernel for 2.2.1.
Sent from my SPH-D700 using XDA App

I actually used to have bakedsnacks rom and I liked it but it became a bit glitchy on me but I did think the battery life was a bit better. I only am using eclair as I want to wait for a final build of froyo to come out from sprint so the developers can utilize it better. I tried some of the leaked ones but I prefered the 2.1 better, all of the 2.2 ones were missing minor things that I used so I switched back. Also interactive setting just keeps the processor at max clock for a really long time before it scales back down and I didn't like that. Has anyone used the fluff ondemand kernal that is supposed to be for bettery battery life with syndicated 2.1? So I have deleted setcpu but it seemed to eat my battery faster so I put it back on. Maybe I will try some other kernal configurations since I was told that I can swap kernals without looseing data.
Sent from my SPH-D700 using XDA App

Fluff was glitchy for me,I liked Xtreme kernel the best.

SetCPU vs. CMSettings Built-in CPU manager

For those of you on CM7 (preferably RC2 or later nightlies), are you using SetCPU or the built in CMSettings CPU manager? Which is giving you better performance/battery life?
I can't help but think that the built in CM Settings CPU tuner is going to be conflicting with my SetCPU profiles.
Been using nightlies since #30 or so, and I currently run SetCPU with a normal profile, a screen off profile, and a profile for <10% battery and haven't touched CMSettings' CPU manager.
I'm contemplating just uninstalling SetCPU for a day or two and seeing what a 1017max / 245min Ondemand or Powersave governor via CMSettings ends up doing to my battery life considering there will be no screen off profile.
Any thoughts?

I dumped setCPU after a lot of testing (and even bought it on market)
I'm finding I'm much happier using inbuilt CPU settings. I think battery life is the same but performance is better due to the fact that SetCPU would sometimes get stuck in my screen-off profile when turned on causing the phone to be really slow.
I recomend uninstalling setCPU, set your ONDEMAND governor with ~1Ghz and run it... You'll find your battery about the same but much less hassle.

I have yet to try that, I somewhat feel obligated to use SetCPU since I purchased it lol. But it probably won't be the last time I waste money at the market.

Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App

Utorrent76 said:
Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
its the same thing :facepalm:
Try the inbuilt one... I think its way easier

I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?

Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.

I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2

DJAeroX26 said:
I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Definitely. This is the one thing I like about SetCPU is having the 10% and 5% profiles so that I can get the last few % to last forever if I need it. Although in normal day-to-day use I'm never pushing it below 20%.

ScooterG said:
Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.
Click to expand...
Click to collapse
Yea I see this, as far as the governor changing etc.. This is why I'm wondering if it would be easier on my phone to just run only the CM Settings one.
I notice that every 5th or so time I unlock the phone, there is an obvious lag switching from the screen off profile, and my unlock sliders jitter around and it takes 4-5 tries to unlock the phone. I think this is probably partially due to both settings switching over trying to change.
I think I might try backing up and uninstalling SetCPU for tomorrow to see how it goes.

colonelcack said:
I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?
Click to expand...
Click to collapse
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.

redpoint73 said:
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.
Click to expand...
Click to collapse
I'm not sure about CM's kernel with the over-volting but I do know that Pershoots kernel can be overclocked to 979mhz without over-volting (Pershoot told me himself).

At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted

Daughain said:
At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted
Click to expand...
Click to collapse
Well obviously.... But why the hell would you ever need to be running at 1.8ghz? The fact that you are always using a temp-specific profile method should show you that consistent 1.8ghz isn't good for the phone...

Okay so I uninstalled SetCPU last night and I'm going to run just the CM Settings CPU manager all day to see how it goes. Running like this:
ONDEMAND governor
Min CPU: 245 mhz
Max CPU: 1017 mhz
On nightly #19 also.
Okay so its midnight almost, and I'm at 13hrs unplugged and 52% battery still. Pretty general/light use, phone is just as snappy and the lack of a screen off profile doesn't seem to effect battery at all. Liking it so far! very interesting to see the screen off profile not mattering much.

SetCPU for me. I like to have a temperature and charging profile, to prevent the phone from overheating. Even at 1ghz the possibility exists, nice to have a backup incase.

I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison

tackleberry said:
I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison
Click to expand...
Click to collapse
With multiple tries... If you change the settings on one, it cancels the settings on the other... Maybe it's because you had set on boot enabled on both?

im going to run the CM tuner and uninstall Setcpu and see how it runs. i never thought about this but i do get that lag when i turn my screen on sometimes. im gonna miss having the profiles but ill see how it runs over the coarse of a couple days.

SetCPU best speed

Hey everyone, just wanted to post this to see what cpu speed works best for you guys.. Im using these preset things with the program like performance or power saver etc but i dont seem to notice a difference all of them seem to be the exact same.. Wondering how to make it good for like 50% power and 50% performance, basicly balancing the 2 out as long as its better than stalk and not burning out my cpu.. so thanks, let me know what works for you guys as ive heard its slightly different for everyone else
(HTC EVO 4G)

I use the standard "ondemand" governor with a 998max-245min, but the thing I found makes the most difference are the settings under "Advanced".
I use the below "Advanced" settings along with a 245-245 screen off profile.
Seems to get me the best battery and cpu scaling.
It also helps to use an undervolting kernel like Freedom-More.
Try that for a couple days.
NOTE: click the apply button a couple of times (might be bug but they sometimes don't take on 1 button click). Try them as is without "Set on Boot", until you are sure that your phone likes them. Plus, check after a reboot that you verify/reapply them.
Sampling rate: 20000
Up Threshold: 85
Ignore nice load: 0
Powersave Bias: 14

I'm at 691200 on smartass governor with 245000 as min on Rcmix rom
Sent from my PC36100 using XDA App

ReapersDeath said:
Hey everyone, just wanted to post this to see what cpu speed works best for you guys.. Im using these preset things with the program like performance or power saver etc but i dont seem to notice a difference all of them seem to be the exact same.. Wondering how to make it good for like 50% power and 50% performance, basicly balancing the 2 out as long as its better than stalk and not burning out my cpu.. so thanks, let me know what works for you guys as ive heard its slightly different for everyone else
(HTC EVO 4G)
Click to expand...
Click to collapse
The "presets" are how the cpu scales i'd use "interactive" or "smartassv2" 245 min and max at 998+ then search around for here for various profile set-ups

I'm running the Gingerbread-Evo-Deck 1.3 with a Savaged Zen 2.2.1 CFS HAVS Kernel. I'm also undervolted 50mV, and using the interactive x governor set at 128MHz-768mhz. Running a few other simple tweaks learned from Carhauler, and I've got excellent battery life and great performance.

I currently run mine on an ICS rom & it comes standard with a tiatmat 4.1.0+ kernel & the cpu is running at about 245mhz-1036mhz with smartass governor(I usually set it to smartass v2 but it switches back to smartass haha). My battery life for me is enough to get me thru the day.

vulcan001 said:
I currently run mine on an ICS rom & it comes standard with a tiatmat 4.1.0+ kernel & the cpu is running at about 245mhz-1036mhz with smartass governor(I usually set it to smartass v2 but it switches back to smartass haha). My battery life for me is enough to get me thru the day.
Click to expand...
Click to collapse
Which ICS rom are you running?

I currently running RCMix3d Runny® Sense 3.5. Should I just got with ICS to overclock or just find a kernel that allows it?

oidrtybtrd said:
I currently running RCMix3d Runny® Sense 3.5. Should I just got with ICS to overclock or just find a kernel that allows it?
Click to expand...
Click to collapse
Get a new kernal. Try Tiamat 4.1
I have my SetCPU at 128min 1152max smartassV2(i CAN overclock up to 1267) with 1 profile:
Screen Off 128min 245max
My battery life is extremely good.

Samurai 3.0.4 wont allow 1000mhz

I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.

GSF1200S said:
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
Click to expand...
Click to collapse
Did you try reflashing fresh? I'm currently runnin CK23's Urban Precision 1.1 with Samurai 3.0.4 and I'm OC'd to 1400/200. I honestly don't kno why its not working for you, I'll be sure ta mention it in the thread tho.
Sent from a Epic like no other usin XDA Premium....

Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?

kennyglass123 said:
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
Click to expand...
Click to collapse
Yes, Ive done it a third time just to make sure; 100% reproducible with 3.0.4. The first 2 times I booted ACS ICS 5.5 FIRST, then booted back into CWM to flash the kernel. This last time, I flashed the ROM, then flashed the kernel immediately after. Same result. I guess its just my device? Ive never had issues with this before, so..

Did you clear data in Voltage Control? Perhaps it's your governor.