Overclocking and undervolting is highly debatable, some say its good and some say its bad... so its upto you to proceed further
First rule of overclocking.. Your Mileage May Vary
Most of the people here in xda do know about overclocking and stuffs but still there are many who are so eager to overclock their beast . Hence this guide.
I have given some good info below about these stuffs as far as i can , you can always use google to get further details.
What is overclocking?
Overclocking is the process of making a computer or component operate faster than the specified clock frequency by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking")
Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable.
You can get more performance from your chipset, though s3 is already fast you can see the visible changes in application execution time and much more like instant response time.
* Overclocking is always risky if something is configured improperly and may also result in permanent damage of your hardware. As long as it is done safely you are good to go.
* You may see some increased power consumption.
* Extreme overclocking might kill your hardware.
The process where you provide less voltage to your cpu rather than the stock voltage.
* Reduced heat from your device.
* Good battery life.
* Extreme undervolting will make your device unstable and some times even end up with a boot loop.
Dividing the guide into 2 parts CPU and GPU
The max clock that can be used on our s3 is 1800mhz and the minimum is 100 mhz. Below given is the stock voltage for all clocks for your reference.
1800mhz : 1450mv
1700mhz : 1400mv
1600mhz : 1350mv
1500mhz : 1325mv
1400mhz : 1275mv
1300mhz : 1238mv
1200mhz : 1175mv
1100mhz : 1125mv
1000mhz : 1088mv
900mhz : 1050mv
800mhz : 1000mv
700mhz : 975mv
600mhz : 963mv
500mhz : 938mv
400mhz : 925mv
300mhz : 900mv
200mhz : 900mv
100mhz : 900mv
1. Kernel with overclocking support.
2. ns tools to change frequency/voltage.(you can use the app of your choice here).
3. set cpu and stability test to test the stability of CPU.
4. Some patience.
Set the current clock you want to test via ns tools. (Select max frequency in cpu tab).
Open set cpu's cpu stress test and run it for atleast 10 minutes. If you didnt get any errors on those 10 minutes and the test completed successfully then the clock is ready for daily use
Now for undervolting use the same ns tools and reduce the voltage by -25mv.
Repeat step 2.
you can reduce the voltage further by -25 mv after the completion of stress test until the app become unstable. (Advanced users can try reducing -50mv )
Repeat step 1,2 and 3 for every possible cpu clock you see in ns tools.
Note the stable cpu voltage for every clock, once you finish testing all your clock values save it as a profile in nstools and set it on boot.
Voila !!! now you have finished overclocking/ under voting your beast The very same guide can be used to underclock you cpu.
1. Not all chips are capable of running at higher speeds like 1800 mhz. Those speeds are highly experimental.
2. Recomended max overclocking is 1600 mhz.
3. If your device gets hotter allow the device to cool for few minutes before starting the test.
4. Combining the overclocking and undervolting will give you the best of both the worlds
In case of emergency:
1. If your device becomes unstable and not responsive either press the power button until your device restarts or pull out your battery.
2. If you end up with the boot loop due to extreme undervoltage below is the cwm flashable to reset your voltage.
Though quadrant is comletely outdated and is not recommended am just adding this screenshot to show the potential of overclocking the below screenshot is tested with 1600mhz(checkrom 3.5 +siyah)
*********************Do note me if any information is incomplete or wrong ill change it.*******************************
* xda and its amazing developers for their work on the kernels.
* ultimate kernel cleaning script (@buster041284 ).... have edited the cwm zip to wipe init.d