Database Info

Mini Overclocking Guide

Mini Overclocking Guide​
NOTE: The Steps Below were Tested on Froyo Roms. I have found different and perhaps better ways to test stability with CM7 Roms so I added a section for that too.
You can still use Stability Test but I don't use it too often anymore for CM7.
Programs Required for testing:
#1 Stability Test
#2 Neocore (please note that some kernels are not FPS unlocked meaning that the frame rate will not go over 56fps so make sure to compare apples to apples when testing different kernels).
For overclocking/undervolting you can use either Pimp My CPU or Voltage Control
Intro:
I posted this Guide in ROM thread but decided it might help someone trying to get a head start overclocking...just a reference not a bible.
First of all, please realize that no two CPUs are created equal. Just like with PC Overclocking, there is the luck of the draw involved here so just because one person can do 1.4Ghz it does not mean you will be able to do so nor it means that my UV settings will work for you.
Achieving 1.2Ghz should be feasible for almost all users since most of the code for it was already done by Samsung themselves. After that point though, it is a matter of luck. Many users can do 1.3Ghz but getting into 1.4Ghz the chances of stability drop dramatically.
Please note that with CM7 Roms it seems a LOT more people is able to hit 1.4Ghz and even 1.5Ghz fully stable. 1.6Ghz is also working although not as common. It is easier to use it if you select 1.6Ghz as the ONLY frequency but of course battery life will be affected.
So, start at 1.2Ghz and try to achieve stability with the lowest possible UV settings you can get to improve your battery life then when fully stable, go for a bit more speed if you like until you find your limit.
Process:
The following is the process I use to get 100% stability. Of course, you can use your own or tweak as you like as this is hardly the ONLY TRUTH of overclocking…I just hope it gives you a good idea on how to achieve stability.
I normally use these settings for 1200Mhz:
1200Mhz @ -100
1120Mhz @ -100
1000Mhz @ -100
900Mhz @ -100
800Mhz @ -100
400Mhz @ -100
200Mhz @ -100
100Mhz @ -100
After setting those up , click the Apply Now button but do not save to the Boot settings until you are sure they are stable for you.
To check stability I first run the Stability Test program and let it loop about 30 times or at least 20 of the CORE (not the RAM).
If it fails give it another shot if it fails again then it is time to adjust the voltages for 1200Mhz.
My experience has been that Stability Test crashes to the home screen when it needs more voltage so if it crashes for you change the UV to -75 and test again.
When you are able to pass that test , you can go to Neocore and try looping Neocore and let it running for about 5 to 10 minutes.
If Neocore freezes, at least for my phone, it means that voltage is too high so I need to drop the UV.
Right there is where the whole trick is. Trying to find what UV voltage is enough for Stability Test to pass but still low enough so that Neocore does not freeze.
This takes a lot of trial and error specially when going for 1.4Ghz!
Another thing is that the UV setting for the frequency below the one you are going for, like 1120 and 1000 for example, do have an effect on the stability you are trying to achieve on 1200Mhz because the phone does not seem to like big voltage jumps .
Some times changing the voltage for the frequency below the one you are adjusting is a good way of achieving stability.
This becomes more important when for example you find out that changing 1.2Ghz to -50 gives you stability for Stability Test but then you need -75 in order to pass Neocore test. What do you do then? What I have done with relative success is , use -75 but then increase the voltage to the frequencies below 1200.
For example if I had
1200Mhz @ -75
1120Mhz @ -100
1000Mhz @ -100
I would change it to:
1200Mhz @ -75
1120Mhz @ -75
1000Mhz @ -75
then test Stability Test to see if those changes help you pass it without having to increase the voltage for 1.2Ghz directly thus avoiding the Neocore freezing issue.
Another process some users are doing is just run Neocore for about 30 minutes and it seems to be a good alternative for some. Guess it all depends on your particular phone.
So, as you can image, this means a LOT of trial and error and restarts of your phone. For 1.2Ghz it should be painless but if you want to go higher, prepare to do a lot of the steps above.
Another thing to consider is that some phones seem to work better with kernels that only have one top speed after 1Ghz as opposed to kernels that offer multiple speed options so this is yet another variable to work with.
Also, remember that to restart your phone, there is no need to pull out the battery. Just press and hold the Volume Up and Power button and it will restart.
I am sure this guide can be done a lot better and will be glad to add or edit with any recommendations you can offer.
I hope this helps some of you trying to push your phones to the limits and have fun!
UPDATE for CM7 Users
With CM7 what we considered THE holly grail of speeds, 1.4Ghz with Froyo Roms suddenly became a VERY common thing.
I have no explanation as to why but a LOT of users are able to get 1.4Ghz and even 1.5Ghz perfectly stable on CM7 and the phones just fly at those speeds. Some are also able to get 1.6Ghz stable but that is harder.
Setting only one speed like 1.6Ghz dramatically increased the stability as well. Just a hint for you guys wanting to do some benchmarks.
You can use a program like Pimp My CPU or Voltage Control to set the voltages and the Maximum and Minimum speed.
Now while the Steps at the beginning of the guide (for Froyo roms) should be fine for CM7 as well ...I have noticed, at least with my phone , that a video player called Moboplayer is VERY good for stability testing CM7. In fact, I do not even use Stability Test any more since I moved to CM7.
When the voltage is a bit low on my screen it creates some artifacts, usually green spots that come up and go in random areas until it freezes.
My actual favorite player for CM7 is Dice Player because for me it plays 720p files better but I like moboplayer a lot as well specially because of the artifacts it shows when I am not stable so it is a quick way to tell the settings are not going to work.
Another thing I love to use if the Riptide Game (tegra 2 game) with Chainfire 3D plugin to make it work on our phones. That game will just close without warning when my speed is unstable. So I just let it running the demo on its own for about 10 minutes.
So basically, I use Moboplayer and Riptide to test my stability and with those tests my system is ready to go and takes less time than the steps I used to do.
Of course you can come up with your own preferred tools since our phones are quite unique and seem to have their own personalities.
It seems some users are having luck with my settings so here are my settings for 1.6Ghz This is for GLITCH kernel (V10C VC). Remember that each kernel has different voltages so instead of giving you a minus value like -100 I will give you the actual voltage I am using for each speed.
1.6Ghz - 1425mV
1.5Ghz - 1400
1.44 - 1325
1.4Ghz - 1325
1.3Ghz - 1275
1.2Ghz - 1275
1.0Ghz - 1200
800Mhz - 1100
400Mhz - 950
200Mhz - 850
100Mhz - 850
For Governor I normally just have Smartass and the Scheduler is NOOP.
Not that while for 1.6Ghz my current setting is either -50 or -75, if I were to select only 1.6Ghz as my max and minimum speed, I am then able to lower the voltage to -100 perfectly stable. Just an interesting thing for you to play with.
Important Note for CM7 users getting many FCs like google service or android service.
CM7 has a much smaller data space for application installs and every time I get to that limit my phone gets crazy with FCs. You can check that by going to your applications and launching the TERMINAL application then type df (in lower case) and pressing Enter.
Look at the top table listed for /datadata and make sure you have some available space.
As long as I keep that from filling up (in fact I prefer to keep it around 60% max to give me some room) my phone works like a charm.
You can use an app like APP2SD to move application data to the SD card to free up space.
Have fun and enjoy your pumped up phone!
UPDATE 12/30/2011
CyanogenMod 9 (ICS) users with Glitch kernel using LiveOC you can use my settings as a starting point.
This is what I use for 1603Mhz
Voltages:
ARM voltage
from 1500 to 1200 = 1.5V ; 1000 = 1.375V ; 800 = 1.250V ; 400=1.100V ; 200=950mV ; 100=900mV
Int from 1400 to 1200 = 1.2V ; 1000 = 1.15V ; 800 = 1.125V ; 400=1.100V ; 200=1.100V ; 100=1.000V
Then 123% LiveOC using 1300MHz step (giving you 1.6GHz)
Governor I am still testing but usually Smartass V2
You can of course use it as a starting point for lower speeds if you like.

Nice man. Saves alot of frustration with this.

Awesome! Thank you!

You are the OC master, Shaolin.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

I wish I was a master indeed but I just have a lot of patience I guess to test ..and test...and crash..an test some more

I think I saw a post that said that any temperature below 56 degrees Celcius is fine for the captivate. I still start to worry though if it reaches 50 during a stability test, what's your opinion?

I noticed that mine when it its 50C or so for any reason (battery temp IIRC) it stops charging so that is where I normally draw the line. If I cannot keep it under that I dont feel comfortable.

That 50 is pretty high, at least for me. Even with stability test going for an hour or so at 1400, I only hit 46. Haven't seen anything higher
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Depends on ambient temp of course...you cannot compared devices temps without knowing the ambient temp. In any case, I saw that when I was using the first Trident kernel. That one even made my screen feel very hot...kinda scary lol
Right now, the only app I have that makes my phone stop charging, even when temp is low, is the Justin TV viewing app....weird. I even ran the phone at 600Mhz only to make sure.

AReynante said:
That 50 is pretty high, at least for me. Even with stability test going for an hour or so at 1400, I only hit 46. Haven't seen anything higher
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I was testing out 1500 1400 is fine for me with -100 for each value. 1500 is a different story since I haven't managed to find a stable combination yet (that doesn't reach 50 degrees Celcius).

Sweet. Are you getting to 50C with a specific app? I only get there with some streaming apps but I really only use 1.5 for fpse emulator for example.

I don't have an app that tells me the temperature so the only time I know is if I do a stability test. I'm not sure if I really have a need for 1500MHz since I don't use emulators much but it's more of a "yea my phone can do it" kind of accomplishment - unless I'm missing out on some other benefits of 1500Mhz over 1400Mhz besides possibly more smoothness.

zuN! said:
I don't have an app that tells me the temperature so the only time I know is if I do a stability test. I'm not sure if I really have a need for 1500GHz since I don't use emulators much but it's more of a "yea my phone can do it" kind of accomplishment - unless I'm missing out on some other benefits of 1500Ghz over 1400Ghz besides possibly more smoothness.
Click to expand...
Click to collapse
Lol 1.5 terahertz I want that phone!

studacris said:
Lol 1.5 terahertz I want that phone!
Click to expand...
Click to collapse
Wow didnt notice that....thats Fing awesome!

Stability Test question
Hey Shaolin,
Just a quick question here, when you mention running stability test through 30/50 runs, are you referencing the RAM runs or the core runs? Just checking, since the RAM runs complete within a few minutes whereas the core runs take closer to half an hour, etc.
Thanks for posting the guide, much appreciated!!!

Since the new version I am only doing 30 of the core runs since it seems to take longer than before.
You are welcome amigo

shaolin95 said:
Since the new version I am only doing 30 of the core runs since it seems to take longer than before.
You are welcome amigo
Click to expand...
Click to collapse
Hey mate, maybe you can add this to your guide as I thought before that stability test and several runs of new core, nenamark, etc...that after passing those tests you're probably stable but what I found out that I can pass those tests without problems and just recently those test are not enough for you to be sure if you are really stable what I have found is to run or record in your phone video cam in its highest resolution about 720p for 200mb worth of data if your phone won't freeze then it's pretty stable you can delete those files afterwards.

Indeed each phone and user can find specific things that work for them, for example with my phone I can just use mobo player and play some videos and I get artifacts when voltage is low or I had a game that with low voltage will always freeze at the same spot yet some user do not have the same effect.
I guess I can add a small list of other possible quick tests like that video one you mentioned as alternatives

I found out another way to test stability which is to do a batch operation of backing up apps with TiBu. I'm not sure what it implies if it crashes though

Hi shaolin95, can I link this post in my VoltageControl thread? (with credits ofc)

[Q] SetCPU vs. Voltage Control, and what are some recommended settings?

My understanding is most people prefer Voltage Control, but SetCPU allows for specific under/overclocking profiles that can increase performance without killing battery life.
If someone could direct me to popular, trusted settings, I'd appreciate it. I'm not a heavy user or power user, so I'm looking for something that just works well. I don't care about benchmarks and things of that nature.
I'm sure this has been discussed, but I was unable to find posts that didn't concern user-specific issues.
Thanks,
Wyatt
EDIT: 53 views and no replies. I guess I'll experiment for myself. Wish me luck!

gnarlynewport said:
EDIT: 53 views and no replies. I guess I'll experiment for myself. Wish me luck!
Click to expand...
Click to collapse
That's really all it comes down too...experimenting and finding out what works best on YOUR phone with YOUR configuration...
GOOD LUCK!
ps... have been very stable with OC'd to 1.4
-25 down too 200
-100 on 100
bfq and conservative

I use VControl myself...i like the UI.
For Performance: 100-1.4GHZ (1.5 works too, but is WAY overvolted, and 1.6 is extremely unstable), -100mV from 100-1000 MHZ, -75 for 1.1-1.4GHZ.
For "Battery Life": (i really don't see a difference...) 100-800 MHZ (anything below 800 is painfully slow), -100mV across the board.
I leave schedulers and governors at their stock settings, the only time I change anything is to set the gov. to Performance on Performance for max Quadrant scores.

kvswim said:
I use VControl myself...i like the UI.
For Performance: 100-1.4GHZ (1.5 works too, but is WAY overvolted, and 1.6 is extremely unstable), -100mV from 100-1000 MHZ, -75 for 1.1-1.4GHZ.
For "Battery Life": (i really don't see a difference...) 100-800 MHZ (anything below 800 is painfully slow), -100mV across the board.
I leave schedulers and governors at their stock settings, the only time I change anything is to set the gov. to Performance on Performance for max Quadrant scores.
Click to expand...
Click to collapse
How many Mhz levels are you selecting? In my experience anything above 5 and it WILL NOT clock up to the higher settings. Maybe thats why you notice no difference in battery life?
For instance if you had say 100, 200, 400, 800, 1000 and 1400 you will reace 1000mhz only
if you had 100, 200, 400, 800, 1400 you would reach the 1400mhz. ive tried many combos and 5 or less was the max it would use (voltage control app, im sure setcpu would most likely be the same)

How many slots does the imnuts kernel support?
Sent from my SCH-I510 using Tapatalk

I started using SetCPU, and I think I prefer it.
Quick question, it seems like rebooting is unnecessary for the changes to take effect, is that true?
Overclocking definitely worked. I got 1853 @ 1200mhz in Quadrant, up from 1600.
Edit: now 2025 @ 1300mhz / 1300mhv
2nd Edit: Late last night, I was using a stability test in one of the apps, but I can't for the life of me remember which app or how I found it. Now I'm using StabilityTest from the market. What's a safe cpu temp for these phones? I'm getting 32 degrees under full load in an air conditioned environment.

gnarlynewport said:
I started using SetCPU, and I think I prefer it.
Quick question, it seems like rebooting is unnecessary for the changes to take effect, is that true?
Overclocking definitely worked. I got 1853 @ 1200mhz in Quadrant, up from 1600.
Edit: now 2025 @ 1300mhz / 1300mhv
2nd Edit: Late last night, I was using a stability test in one of the apps, but I can't for the life of me remember which app or how I found it. Now I'm using StabilityTest from the market. What's a safe cpu temp for these phones? I'm getting 32 degrees under full load in an air conditioned environment.
Click to expand...
Click to collapse
I just switched over to Setcpu as well. It seems to work better for me also. I can now select 6 levels instead of the 5 before in voltage control and I also noticed that the set on boot on voltage control did NOT work but it DOES work in setcpu!! Im happy!

Haven't tried Setcpu yet, but I preferred Pimp my CPU over VC when I was using Miui on the Fascinate.
Sent from my SCH-I510 using XDA App

Important Information About Overclocking - MUST READ

This is a message from a developer who is in a team who develops a kernel with a very large overclock. Do not take this is an idiot babbling, read this and take it to heart as this is very important.
I want to talk to you about overclocking our phone and how dangerous it can actually be. I love overclocking, and have overclocked my main computer, and I overclock my phone, but my overclock (as you can see from my signature) is very mild. A simple 800MHz overclock.
When we first got overclocking on our phone (thanks to Fugumod), we were around 800MHzish and it gave a nice boost. It got up to 1GHz and it gave another good boost. Over time, we have discovered the phone works at high speeds, now 1366 in Fugumod, and 1400 in G3MOD. Now if you look at these speeds and compare it to the original clock speed on our phone (667MHz, or you can look at the Spica which has the same CPU but with a larger transistor process: 800MHz), this is a 204% overclock on Fugumod and 209% on G3MOD.
Now let's put these percentages into perspective: on your desktop computer, a 200% overclock is normally only possible with serious cooling: water or liquid nitrogen, and we are attempting to do this in a PHONE with NO cooling, and NO ventilation. Furrthermore, it is kept in our pockets beside our thigh muscle: the largest muscle in our body and it emits a large amount of heat. These are not ideal conditions for a CPU to be kept in, especially when it is in a fragile state such as overclocking. We are lucky however because phones have clock governors which clock it back when it is idling to conserve power.
When you overclock the CPU, you must also overvolt it to keep the system stable while overclocked. However the downside is that if you overvolt your CPU, you will use more power, and also reduce the lifespan of our CPU. Let me show you how much more power is required to run the phone at 1.4GHz.
Now, as we don't know the exact power consumption of our CPU, I will assume the power consumption is 100mW. In overclocking a desktop computer, we use this algorithm:
Code:
OC Wattage = TDP * ( OC MHz / Stock MHz) * ( OC Vcore / Stock Vcore )^2
So that means 100 * (1400 / 667) * (1525 / 1200) ^ 2 = 338mW. That is over 3 times the power consumption of the CPU at stock speeds. That also in turn effects the lifespan of the CPU as the transistors are both having to work twice as hard (as the CPU clock is twice as high) and are drawing three times the power consumption, this means the CPU will last 6 times less at 1400MHz.
When we were starting out with overclocking our phones, we didn't have a lot of the nice new features we have discovered that boost performance but now that we do, these huge overclocks just aren't as necessary anymore.
TL;DR
Guys, our phone can go at 1.4GHz or 1.36GHz, yes. But is it a good idea to keep it at those sorts of speeds? No. The reason marcellusbe and the G3MOD team provide such HUGE overclocks are for rare occasions. When the phone is just doing nothing, we expect you to put it back to 667/800MHz, but when you are wanting to play Angry Birds or emulate Castlevania 4 or something, you put it up to 1400MHz, but put it back again once you are done. 24/7 usage at 1400MHz or 1366MHz is DESTROYING your CPU and your battery.
USE OVERCLOCKING WITH EXTREME CAUTION
Extra Information
Here is a graph to show the power consumption increase from running the CPU at higher overclocks and also the reduction from undervolting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Even an i7 is rarely oced to 200% - its too much and can be dangerous

cdesai said:
Even an i7 is rarely oced to 200% - its too much and can be dangerous
Click to expand...
Click to collapse
Precisely my point.

Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...

dharamg3 said:
Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...
Click to expand...
Click to collapse
+1 For that too
Nice information. I always used to keep my phone to 1200 mhz. Damn should reduce it now

Thanks, excellent info.
Sent from my GT-I9000 using Tapatalk

I never try to go beyond 800Mhz
I think it is sufficient for daily use
(More than sufficient)

exactly.... i was going to post somthing like this
when u need that boost (like for ps1 emulator or hd games) us upto 1.3ghz
but otherwise just leave it at 800-900mhz...
u dont need crazy oc all the time!

Doesn't SetCPU (or any other app for that purpouse) do exactly that? If you set scaling and min/max freq. accordingly? What is the difference beetween that and setting in manually?

Gud info mate......
Governer should be Ondemand right ????

Hm, a guy called Kyrillos told me, that normal voltage at 667MHz is 1200mV. So, in newest g3mod, from 500MHz on, its higher, at 800MHz its already 0,1 volt above max in stock.
So how dangerous is it to let it allday at [email protected] ?

DaBigFreak said:
a guy called Kyrillos told me,
Click to expand...
Click to collapse
He s a recognized developer. A very good one infact. He was right by the way. Its only the faulty reading.
---------- Post added at 01:32 PM ---------- Previous post was at 12:54 PM ----------
Hillbeast excellent, excellent info. That s the precise reason I don t use high overclocked kernels. Maximum I goto is 800MHz.

raja4sure said:
Gud info mate......
Governer should be Ondemand right ????
Click to expand...
Click to collapse
Yes. I use it mostly. Other devs and experienced users here as well for what i've noticed. Or conservative which saves battery because it scales freq more gradually. http://www.setcpu.com/ - http://www.setcpu.com/#7
And profiles, especially the Temp and screen off. Prevents from overheating and exscessive battery discharge, respecitvelly.
DaBigFreak said:
So how dangerous is it to let it allday at [email protected] ?
Click to expand...
Click to collapse
Probably very. But overclocking in general shortens life span of electronic components, primarily because of increased heating. If that worries someone that it is probably best not to overclock at all.
I personally see no difference between manipulating cpu freq manually or by using some app to do it when necessary. If I'm wrong then please feel free to elaborate.

dharamg3 said:
Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...
Click to expand...
Click to collapse
I will update this thread and I hope it will actually get stickied as it's quite important information in my opinion and it could save some peoples phones.
mrvek said:
Doesn't SetCPU (or any other app for that purpouse) do exactly that? If you set scaling and min/max freq. accordingly? What is the difference beetween that and setting in manually?
Click to expand...
Click to collapse
SetCPU will obviously set the max and min settings, but in an ideal situation you will want to have a mild overclock (or none at all) if you are just using for phone for normal functions such as TXTing or browsing or something like that, but SetCPU can't detect when you are wanting a more intense operation such as a game, so you're best to adjust it when you are needing it and switch it back.
I keep a SetCPU widget on my home screen to do that.
DaBigFreak said:
Hm, a guy called Kyrillos told me, that normal voltage at 667MHz is 1200mV. So, in newest g3mod, from 500MHz on, its higher, at 800MHz its already 0,1 volt above max in stock.
So how dangerous is it to let it allday at [email protected] ?
Click to expand...
Click to collapse
The stock voltages for our phone at 667 is 1200mV, yes. At 1300mV you will notice a mild increase in consumption.
If we follow the same algorithm in the OP:
Code:
OC Wattage = TDP * ( OC MHz / Stock MHz) * ( OC Vcore / Stock Vcore )^2
We get (again, assuming the standard consumption is 100mA) 100 * (800 / 667) * (1300 / 1200) = 140mA. Yes, it's higher but not too much higher. If you UV it by 50mV @ 800MHz you'll go to 130 and at 1200mV it'll be 118mA.
Overclocks like this are still not 100% safe, but they are nowhere near as dangerous as a 300% power consumption increase.

This is the Information I was looking for past 2-3 weeks. Finally you posted it here.
Thanks hillbeast

Hey man. I really appreciate your effort to inform. I just would like to add something.
Overclock: in modern cpus power consumption increases almost linearly with clock. Let us say linearly to be safe. It means double clock double power (and so heat)
Voltage: when you increase the voltage the power increases approx quadratically (double voltage for times power). But also higher voltage means stronger signals in transistors and so higher stability.
Heating and lifetime: the heat decreases the lifetime of electronic components but not in a linear way. Please also note if a circuit does not die very soon (infantile mortality) it will last very long in normal conditions. So even if it was cut by half starting from the normal 10 years expected lifetime it would be anyway long for a phone.
So it is clear voltage is much more important than clock for power consumption. Decreasing the voltage you could have an overclocked cpu which consumes and hests up less than the stock one. Of course it is less likely to be stable.
Personal computer cpus needs cooling and are difficult to overclock because they become very unstable when overclocked so you have to increase voltage.
Finally to be clear I want to repeat your lesson.
DO NOT OVERCLOCK UNLESS YOU REALLY KNOW WHAT YOU ARE DOING. and don't complain with developers if your phone will break.
Sent from my GT-I5800 using XDA App

After reading this, I will never overclock more than 1GHz. Thanks

I agree extreme 200% overclocking is harmful to cpu and disagree with some of the points.
I don't think wattage and tdp formula are correct. If it is correct in reality battery should drain in 1/3rd of the stock time and should heat up immediately. we are just increasing the power supply in mv which is 1200 to 1500%. That means 25% power increase.
When the phone is in idle (no music, wifi, data ...) mode cpu/armcore is completely turned off. That means no frequency, no power supply and no heat. Other peripherals have separate clocks and they will keep running in idle mode. This is the difference between desktop and phone cpu.
frequency is 'no of times turning on and off transistors in a circuit per second'. In fact cpu's are designed to work at much more frequencies than stock. But stock frequency is decided by considering various operating conditions worldwide and $$. Personally i use 1020Mhz and phone operates like stock frequency.

I don't agree with one of the last statements:
hillbeast said:
So that means 100 * (1400 / 667) * (1525 / 1200) ^ 2 = 338mW. That is over 3 times the power consumption of the CPU at stock speeds. That also in turn effects the lifespan of the CPU as the transistors are both having to work twice as hard (as the CPU clock is twice as high) and are drawing three times the power consumption, this means the CPU will last 6 times less at 1400MHz.
Click to expand...
Click to collapse
Assuming you use setcpu, your phone spend most of the time in standby. if you use your phone a lot, it will be in standby 70% of the time.
Assuming that when your phone is not in standby the clock is automaticly set to 1400 (which is probably not, but we're doing worst case), your phone will be overclocked 30% of the time.
If your statement about battery drain is correct, the processor will use 160% more battery than usual. This, will not result in a huge battery drain, because actually, the processor is draining very little battery compared with things like display, wifi, 3g and so on.
If your statement about lifespan of the cpu is correct, the lifespan of the cpu is reduced to 75%. Considering that a cpu can last years and that you usually throw your phone away way before the cpu stops working, doesn't seem like a big deal to me.

That is true. Unless you run your phone 24/7 at max OC speed and phone heats up excessively there really should not be problems. That's why we have good apps and scaling governors that save the cpu and battery. In my case the phone spends most time at 400Mhz, then on 800, then 1400 then other freqs (based from setcpu report - info → time in state). Main profile beeing 400/1400, ondemand. And temp doesn't go over 31°C on daily use. What increases temp are mostly games but for that i use several setcpu profiles (in this point i disagree with hillbeast and the ability of setcpu to know my specific requirements. I know that it can't know what i need and when but if I set manually the requiered freq (max) to play a game the phone would heat up significatly (angry birds for about 30 mins gets me to 36°C - relatively high). And then i need profiles not to overheat the phone. And now when I already have profiles, why not let everything be automatic?).
Please don't get me wrong, I agree that OC-ing is quite risky and it should (must‼) be done with great caution and that is an implicit requirement.

Overclocking / Underclocking

either with setcpu or voltage control...would someone care to just explain how to use these apps.
I understand the governers, and I understand the min / max.
So If I bump that max up to 1400 or even 1600 and leave the minimum down...what exactly does that do?
If paired with on demand does it mean it will use as much processor as it needs to perform a task all the way up to the max of what I have it set to?
also, the thing that seems to confuse me mostly are the individual sliders you can adjust per frequency.
I know this is broad question, but I was just hoping someone wouldnt mind explaining this to me as best as possible...or at least dumb it down for me.
I have googled and searched, and really havent found clear answers to me personally to understand it.
thanks

I personally use voltage control extreme.
In regards to the individual sliders you speak of, I believe that those control how many volts the phone uses at each particular frequency. You don't want to turn the voltages down too low/high though because you can freeze your phone and have other problems.
I use the "conservative" governor and seem to get the best battery life with it.
By overclocking to 1400 or 1600 it allows for your phone to run applications, videos, etc. smoother, by using the remaining cpu capabilities of the phone's hardware. The drawbacks of overclocking are that it sucks the battery very quickly, it can cause the cpu to overheat, and can also decrease the life of the processor.
Hope that helps some!

So what is a safe top end? To run on a daily basis.
Sent from my SAMSUNG-SGH-I997 using XDA App

Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App

Perpetrator said:
Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App[/QUO
But doesn't overclocking cause the phone to heat up? I suppose it also depends on what temperature the phone is rated to safely run at too though doesn't it? Cause with increased temperatures I am pretty sure the processor's life could be impacted. But that is probably only if you overclock for a extended period of time.
I would suggest staying at 1.2 for daily use, but if you are doing something that requires a little more cpu you can just bump it up until you don't need it anymore.
Just my 2 cents worth.
Click to expand...
Click to collapse

I know that some ppl OC to 1.6 with ondemand gov and use that as a stable setting... others report problems, FCs, ... think it depends on individual phone.
Some stay at 1.4 to be cautious...
The UV section is where I hear a lot of dissenting opinion. Some say -100 across the board gives best battery/stability... others say voltage should be high toward 1600 and UV more as you approach lower frequencies... personally I find that a graduated setup is best but I am not an expert.
Just sayin' what I've read here.

[Q] voltage control tutorial?

Is there a tutorial (written or video) that shows how to use this? I've never overclocked or changed the voltage before and i dont wna just go in there n start messing with stuff when i have no clue what im doing. Ive looked around for maybe a begginers tut or like voltage control for dummies, but havent really found anything. Anyone know of one? Thanks.

It's really not very hard. The regular Voltage Control will not allow you to overvolt, so you will not run the risk of frying your processor. Don't go over 1400 mhz though. Bad magic after that.
Undervolting will not harm your phone, the most it will do is make it lock up. Just experiment with different voltages. Back in the day I used to run -75 mV across the board without many issues, but I don't really have a use for it anymore since I carry a spare battery. Don't be frustrated if your phone doesn't like even -25 mV though, because every processor is slightly different in their abilities to handle voltage and frequency changes out of spec.
Please note that PBJT kernel is already undervolted a good amount.
Sent from my SCH-I510 using xda premium

Here's my setup - no lag, no hiccups or freezing!!
1300mhz (max) -75mV
1200mhz -75mV
1000mhz -75mV
800 down to 100mhz -50mV
Hope this helps!

n1ghtwish said:
Here's my setup - no lag, no hiccups or freezing!!
1300mhz (max) -75mV
1200mhz -75mV
1000mhz -75mV
800 down to 100mhz -50mV
Hope this helps!
Click to expand...
Click to collapse
Can you please tell me what the actual voltage is? I found that with IMO 4.0 kernel, and with Tegrak Overclock Ultimate, I can clock the at 1.252 Ghz @ 1285mV and 1.3 Ghz @ 1330mV stably. However, I don't know what the actual stock voltage is or the PBJT voltage or IMO 4.0 voltage, etc.
I figure you could check the voltage at least with the free version of Tegrak.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stable for days... Vr ..smartassv2.. 1200 max 100 min.. Eclipse with 1/15 pb&j
Sent from my SCH-I510 using XDA App

Phone is laggy
I am also new to the voltage and clock adjustments. I am finding that my phone is SUPER slow now. I used another forum member's numbers that were supposed to offer a good balance of performance and battery life. I know that every phone is a little different, but I don't want to start messing around and screw stuff up
My setup is:
1300-1400 -0
1000-1200 -50
800-900 -75
100-700 -75
I am running PBJ 415 with FP1 on Tweaked 2.0.
Please be gentle, I am a newb

dees_74 said:
I am also new to the voltage and clock adjustments. I am finding that my phone is SUPER slow now. I used another forum member's numbers that were supposed to offer a good balance of performance and battery life. I know that every phone is a little different, but I don't want to start messing around and screw stuff up
My setup is:
1300-1400 -0
1000-1200 -50
800-900 -75
100-700 -75
I am running PBJ 415 with FP1 on Tweaked 2.0.
Please be gentle, I am a newb
Click to expand...
Click to collapse
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.

BleedsOrangeandBlue said:
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.
Click to expand...
Click to collapse
FYI, if you have the governor set to performance, then the minimum doesn't matter. That governor runs the CPU at max constantly. Great for performance, but hideous for battery life. The only time it will ever ramp down is when it goes into deep sleep, otherwise, it's running at 1GHz.

BleedsOrangeandBlue said:
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.
Click to expand...
Click to collapse
My phone was great when I flashed, but within about 12 hours, things were horrible. I have since flashed back to the stock fp1 kernel, and life is good. Unfortunately, I am not a person who 'leave well enough alone'. I'd like to enter the world of over/ under clocking and see if I can gain some additional performance.
Thanks in advance for any additional info/advice you can provide.
Sent from my Xoom using XDA

shrike1978 said:
FYI, if you have the governor set to performance, then the minimum doesn't matter. That governor runs the CPU at max constantly. Great for performance, but hideous for battery life. The only time it will ever ramp down is when it goes into deep sleep, otherwise, it's running at 1GHz.
Click to expand...
Click to collapse
War Eagle!
I thought that was how it worked, but I will open voltage control from time to time and it will read that its currently at 400 or 800 MHz. Does the program not display properly?
edit: Playing around with it some more, if I change it to something else and then switch it to performance it goes right to 1000. Weird that it displays incorrectly when the program is opened.