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.

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.

Interesting: has anyone noticed min CPU freq has been lowered in 3.0.1.A.0.145

i just flashed 3.0.1.A.0.145 and the rooted system.img... something interesting... has anyone noticed min CPU freq has been lowered to 122Mhz (can be checked by SetCPU)... though 245Mhz is set as default using setcpu the user can select 122Mhz... i guess this means when there is low user activity the battery life should be more!

Such a simple concept. Great idea.
-Sent from my awesome Arc (LT15a)

That seems to be the trick behind "Better Battery performence" from their changelog.

haha, but this don't solve teh problem... battery should live longer when you exactly use the phone a lot

czerwus said:
haha, but this don't solve teh problem... battery should live longer when you exactly use the phone a lot
Click to expand...
Click to collapse
actually if u go to see almost 60-80% of the time ur device will be in low battery state (screen off)... so i am sure this will make some difference...

DooMLoRD said:
i just flashed 3.0.1.A.0.145 and the rooted system.img... something interesting... has anyone noticed min CPU freq has been lowered to 122Mhz (can be checked by SetCPU)... though 245Mhz is set as default using setcpu the user can select 122Mhz... i guess this means when there is low user activity the battery life should be more!
Click to expand...
Click to collapse
ive just updated mine, but on 2.3.2 with setcpu i was running mine when the screen was turned off @ 122mhz!
but yes, the battery does last alot longer especially when you set the profiles up with priorities! i use mine alot in the morning and afternoon on the way home from work for music so during certain times ill setthe profile for the full 1ghz, then charging set a 1ghz but screen off it runs at 122mhz. ive noticed around 4 hours of increased battery life for my arc

av4tar said:
ive just updated mine, but on 2.3.2 with setcpu i was running mine when the screen was turned off @ 122mhz!
but yes, the battery does last alot longer especially when you set the profiles up with priorities! i use mine alot in the morning and afternoon on the way home from work for music so during certain times ill setthe profile for the full 1ghz, then charging set a 1ghz but screen off it runs at 122mhz. ive noticed around 4 hours of increased battery life for my arc
Click to expand...
Click to collapse
oh even 2.3.2 had 122Mhz freq unlocked?
ah then i might have missed it... been testing a LOT of stuff related to X10 / Arc / Optimus One so might have got confused...
sorry!

yeah, least you know though
how reliable have you found setcpu? ive disabled the option "set at boot" and enabled all profiles but i find it not always kicking in when the profiles triggers are met and superuser access has been granted :s

av4tar said:
yeah, least you know though
how reliable have you found setcpu? ive disabled the option "set at boot" and enabled all profiles but i find it not always kicking in when the profiles triggers are met and superuser access has been granted :s
Click to expand...
Click to collapse
havent really had any problems with setcpu before... which version are u using?

2.1.3 ..
THINK its sorted, rebooted and now its charging the profile of 1ghz/performance has kicked in!

[INFO] Custom Kernels & Overclocking - FuguMod Ultra Pre Release

After reading through the Thread for the Pre Release of FuguMod Ultra in the development section of this forum I thought I would post some info up for people who are wondering why it doesn't work with their phone, and just some general info on overclocking.
- First off, not all phones will be able to run at 1366MHz. Every CPU made has a range of freuqencies it will work at, and it is different for every single one. So some may be able to handle 1366MHz and above, others may max out at 900MHz. If you are getting black screens, freezes, or random behaviour, then your CPU doesn't like the frequency you have it at, try a lower frequency.
- Always keep an eye on the temp of the CPU when testing overclocking, if the CPU gets too hot, and fail safes don't work, there is a chance you could fry your CPU.
- With the FuguMod Ultra kernel, you must also be aware that gpu bus frequencies have been changed, so if your phone is not happy with that it will black screen. (as bus speeds are like cpu speeds, every different device can handle different clock speeds)
- plls values have been changed, and these may cause problems on your phone.
So if you want to have a go at overclocking your phone, back it up, and then give it a go. Select a frequency, and test with something pretty cpu intensive (3d game, multiple quadrant passes) and see if there are any bugs/overheating during a 15min time period. If you notice any problems/too much heat, try a lower frequency, and try again. And if for some reason your phone doesn't like the kernel, you can reflash with your previous kernel or a new ROM as you have already backed up your data.
If you have any other questions about overclocking, feel free to post here and I will try my best to answer them.
--- Samsung G3, InDroid 4.3, FuguMod 2.4 B3 800MHz ---

How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App

dilzo said:
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
The battery temp is a good representation of how hot the processor is getting as it is right next to the battery (only a thin sheet of metal seperating it) If the battery rises in temperature by a few degrees, then you can summize that the cpu is probably getting a few degrees hotter than that. I really wouldn't recommend letting the battery get above 55degrees (celcius) as this means the CPU may be getting up close to 65degrees (celcius) which is a very bad thing.

Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.

marcellusbe said:
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
Click to expand...
Click to collapse
Yes, Very true!!
Must also say, Your kernels are pretty legendary! Waiting patiently for the offical release of your FuguMod Ultra

m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.

Piyush Rawal said:
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Click to expand...
Click to collapse
How have you got your phone set up? i.e. what ROM are you using etc.

I am using stock jpq with app2sd, swap, zipalign, ramhack and stuff. Setcpu is installed with default min/max freakquency, No profiles in use and undervolt a bit.

Ok,
This may be an issue caused by XXJPQ, as it is a new release there may be some sort of conflict. Have you tried asking if anyone else has this issue in this thread? http://forum.xda-developers.com/showthread.php?t=1132697
I haven't played around with JPQ yet so don't know what the bugs are yet.
Also, are you running a stock kernel? Have you confirmed that the phone has been rooted properly as well?

It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.

Piyush Rawal said:
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Click to expand...
Click to collapse
Ok cool, I'll report the bug to the developer so that he can have a look into it. Thanks for testing and proving to the kernel.

Little bit of info some might find helpful. After some recent testing, I have found that some people might experience a black screen freeze when phone is in standby for a while with 83MHz min setting and on demand governor. I am not sure of the exact reason for this, whether it is a bug, or that the processor just doesn't like going that low for extended periods of time. If you experience this type of error, just hard reset the phone then open setcpu after phone has loaded and change the "standby" profile minimum to at least the next step up on the slider. Personally I use 223 setting as it provides a smoother lock screen animation, and no significant difference in battery drain.
Sent from my super smooth GT-I5800 using XDA App

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.