[Captivate General] shaolin95:
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.