[GUIDE] Galaxy S3 CPU/GPU overclocking/undervolting (Updated 12/08/2012)
- Thread starter bala_gamer
- Start date
do we really need to do the steps of the first post for each cpu/gpu frequency step (from 200mhz to 16000mhz for cpu for example) ?? cause that would take ages.. (lots of 10 mins of stress tests)
or we do it only for the max values (i.e. 1600 for cpu) we want?
also whats the recommended minimum values for cpu/gpu? thx
or we do it only for the max values (i.e. 1600 for cpu) we want?
also whats the recommended minimum values for cpu/gpu? thx
Last edited:
As the oc/uv mileage varies its safe to check every stepping if you need much better control over uv.
《Samsung rom》
ufff...i know its not a good idea but i copied your settings and run a 10mins stress test and all seems ok
(jelly bam rom), will test on omega rom as well
hey guys i have a quick question, what do you use for stress testing exactly?
so far i use numerous benchmarks and games but they are not so great for actual monitoring and continuous maximum stress... i tried stress test in setcpu but it just fails on any possible clock (default or even less) and it might be due to ELK4 leak or what not since the system doesnt show any instability whatsoever...
i have also seen people post something like "cpu passes: xxx gpu passes: xxx" in this thread when testing...
what app do you use for this?
so far i use numerous benchmarks and games but they are not so great for actual monitoring and continuous maximum stress... i tried stress test in setcpu but it just fails on any possible clock (default or even less) and it might be due to ELK4 leak or what not since the system doesnt show any instability whatsoever...
i have also seen people post something like "cpu passes: xxx gpu passes: xxx" in this thread when testing...
what app do you use for this?
Last edited:
Mine is 1800MHz, but I didn't do it, I just installed PIMP MY ROM one month ago, I guess!
http://imageshack.us/photo/my-images/832/screenshot2012112622451.png/
EDIT: Is it bad? I mean for the hardware, because when I play NFS Most Wanted it gets really hot, but my battery life is pretty good, it's like 14.. 15h on WIFI and 3G using whatsapp and playing games!
I really want to know if it's really bad for my GS3, I'm telling it now because I was curious to know about my hardware test on the newest siyah kernel!
http://imageshack.us/photo/my-images/832/screenshot2012112622451.png/
EDIT: Is it bad? I mean for the hardware, because when I play NFS Most Wanted it gets really hot, but my battery life is pretty good, it's like 14.. 15h on WIFI and 3G using whatsapp and playing games!
I really want to know if it's really bad for my GS3, I'm telling it now because I was curious to know about my hardware test on the newest siyah kernel!
Last edited:
1.8 ghz on the long run is always bad for hardware, you can use it for some benchmarks(and some showoff
) .. .1.8 is not for daily use!
It's better 1.6, use 2.8 only for benchmarks
Inviato dal mio GT-P7500 con Tapatalk 2
Latest version of antutu my benchmark is 5963, this is bull****,i had before 13786 and now my score is pathetic i'm on SiyahKernel 1.7 with Omega V27.1 JB.CAN ANYONE TELL ME WHY????
1.8 ghz on the long run is always bad for hardware, you can use it for some benchmarks(and some showoff
But I don't know how I did this!
Is it okay to overclock and underclock cpu with nstools when stweaks is also installed? I have siyah 1.8.
Better to use any one for setting it. Nstools will override stweaks afaik
《posted from samsung rom》
Im sorry.... I dont understand what u mean by use any one for it? Im confused...
Bala , for my S3 with siyah kernel , im using; MAX FREQ FOR CPU ; 1.5 with -100mV UV , and as for gpu (i do not play games , only browse,multi-task and watch movies) : GPU FREQS , 266MHZ:850mV , 300MHZ:875mV , 350MHZ:925mV , 440MHZ , 1000mV , 533MHZ , 1025mV.
Also for the cpu im using lulzactive governor because it seems smoother and everything is stable. Any thing that i should change in ur opinion?
Thanks!
Also for the cpu im using lulzactive governor because it seems smoother and everything is stable. Any thing that i should change in ur opinion?
Thanks!
Clear DALVIK/system cache when change gov/scheduler
Been using siyah since 1.7rc1 now 1.8. Tried a lot.... My learning curve took a turn when i got into what dalvik cache does (approximately hehe) and the system cache is also important.
The DALVIK is a kind of "port" of all your apps (remember android is modular and built of just that; apps. both system apps and your downloaded apps) that tells the jre how to optimize/interpret the java code.
It (dalvik) creates data on how to run your apps most efficiently, based on your hardware! I have a general idea of how it works but let's leave it at this. Optimizations based on your hardware!
I was thinking what if you change your clocks/voltages/scheduler/governor etc in STweaks? Will that count as "new hw"
Since I started clearing system cache (not data), which i'm not so sure of what does/is other than it "does not hurt to wipe it" ... it just recreates itself, if that cache is static or change according to hw/dalvik i have no clue!!... ok clearing the system cache, dalvik cache and battery stats (in CWM, vol up+home+power when powering on) my battery has improved, my unit is faster in benchmarks (difficult to say under normal use...) but most important no more touchwiz crashes and bugs. It works flawless (almost.
Also I just came over THIS thread today and tried @bala_gamer's GPU freq's/voltages and, though I have not tested it much yet just run through ANTUTU benchmark a couple of times, at least my unit is stable, a little faster than before but most important it does not get so XXXX hot as it used to!! I simply had never tried to up the mhz without giving (quite a lot) more mV!! ... which has resulted in a VERY hot unit, battery drain and no performance improvement (of course the volt does not give more mhz by itself)..
Now running 600mhz on stage 5 on 1025mV (-50mV/+66MHz) im stoked! Thank you mr @bala_gamer I have also undervolted my unit -100mV (try in smallest steps and test your unit before going lower. If set too low you CAN risk not being able to boot, and i don't know how to fix that without wiping the unit and flashing a ROM... probably easier ways!) and set the CPU to max 1.5GHz (all this done in STweaks) and for the first time in since pre-root, the unit feels COLD when not pushedhard! :good::fingers-crossed: I hope this lasts. Felt like around 40 degrees (the unit not the CPU...) ( a little hotter than my palm .. wow I'm accurate! :silly: ) when running through antutu twice in a row. Before, with higher GPU voltages and before the cache wipes the unit became VERY HOT in myy hands .. so hot that i start to worry about other components.... i know the CPU has protection in itself but i do not think there is a "general temp powerdown feature".
Well... Anyway after tweaking I did the wipes (dalvik/sys cache/battery stats) and that is imo very important to get a stable device. Also if you still get bugs try correcting permissions also under advanced in CWM. I've done this once (correcting permissions... after rooting you tend to install different tools which does a lot your system was not ment to be doing. It is worth it to give it a try if you have a unstable device.
The "touch boost" function probably give you less UI lag, but at the cost of more battery every time you touch the screen. I feel the phone "i9300/stock JB XXDLJ2/div bloatware removed" (just thought i'd mention that part) uses a lot of battery already so I can live without the touch boost. I dont experience any UI lag as it is now, but I've also disabled a lot of stupid animations etc... Like I do on my computer! ... It's not for watching the UI "look cool" I want the s3's performance... It's for those amazing console quality OpenGLES 2.1 Games that keeps coming GO UNITY! ... :highfive:
About governors/schedulers (my experience):
Siyah 1.8 defaults to cfq which at least give ME more UI lag and worse test results.. Probably good at multitasking though (completely fair as it is called) but I want max "power" on the task I am performing (usually games) which deadline seems to provide. Deadline IS the default scheduler for the device anyway. I see it already at boot; every widget is almost done loading after login when with cfq I have to wait SEVERAL seconds Will not try to explain what i believe is the schedulers function. Someone else have done it, I am sure because I have read it!
Governor... The CPU's "mother in law" ... It tells (i believe the java engine) what data/when and in what order to send it from memory to the CPU.. i think...
Every other new siyah build has, as stated in the changelogs, f.x. "improved pegasusq", which is the governor I (and others) highly recommend you use with your i9300 btw. It is also the default governor. The fact that the governor is not static (it relies on some scripts (tweaking the governor...) made me think about wiping the dalvik in the first place (after reading up on what the dalvik is.. difficult to find a ANSWER it is mostly discussions where they seem to agree on the main function but "always" end up in a VERY dev/technical discussion that's when I stopped understanding.
Anyway... not found any improvements using anything other than the pegasusq governor on my i9300.
This is MY OWN trials and errors, and I am positive about the results. Any comments? Is this logical? I am fairly new to this.... My first rooted android phone!... so i appreciate corrections! (and respect people who have been doing this for decades (linux stuff...) i'm a MSOFT guy! .. so Android is my first linux..:victory:
@Guttsy911
Been using siyah since 1.7rc1 now 1.8. Tried a lot....
My learning curve took a turn when i got into what dalvik cache does (approximately hehe) and the system cache is also important.The DALVIK is a kind of "port" of all your apps (remember android is modular and built of just that; apps. both system apps and your downloaded apps) that tells the jre how to optimize/interpret the java code.
It (dalvik) creates data on how to run your apps most efficiently, based on your hardware! I have a general idea of how it works but let's leave it at this. Optimizations based on your hardware!
I was thinking what if you change your clocks/voltages/scheduler/governor etc in STweaks? Will that count as "new hw"
Since I started clearing system cache (not data), which i'm not so sure of what does/is other than it "does not hurt to wipe it" ... it just recreates itself, if that cache is static or change according to hw/dalvik i have no clue!!... ok clearing the system cache, dalvik cache and battery stats (in CWM, vol up+home+power when powering on) my battery has improved, my unit is faster in benchmarks (difficult to say under normal use...) but most important no more touchwiz crashes and bugs. It works flawless (almost
.Also I just came over THIS thread today and tried @bala_gamer's GPU freq's/voltages and, though I have not tested it much yet just run through ANTUTU benchmark a couple of times, at least my unit is stable, a little faster than before but most important it does not get so XXXX hot as it used to!! I simply had never tried to up the mhz without giving (quite a lot) more mV!! ... which has resulted in a VERY hot unit, battery drain and no performance improvement (of course the volt does not give more mhz by itself)..
Now running 600mhz on stage 5 on 1025mV (-50mV/+66MHz) im stoked! Thank you mr @bala_gamer
I have also undervolted my unit -100mV (try in smallest steps and test your unit before going lower. If set too low you CAN risk not being able to boot, and i don't know how to fix that without wiping the unit and flashing a ROM... probably easier ways!) and set the CPU to max 1.5GHz (all this done in STweaks) and for the first time in since pre-root, the unit feels COLD when not pushedhard! :good::fingers-crossed: I hope this lasts. Felt like around 40 degrees (the unit not the CPU...) ( a little hotter than my palm .. wow I'm accurate! :silly: ) when running through antutu twice in a row. Before, with higher GPU voltages and before the cache wipes the unit became VERY HOT in myy hands .. so hot that i start to worry about other components.... i know the CPU has protection in itself but i do not think there is a "general temp powerdown feature".Well... Anyway after tweaking I did the wipes (dalvik/sys cache/battery stats) and that is imo very important to get a stable device. Also if you still get bugs try correcting permissions also under advanced in CWM. I've done this once (correcting permissions... after rooting you tend to install different tools which does a lot your system was not ment to be doing. It is worth it to give it a try if you have a unstable device.
The "touch boost" function probably give you less UI lag, but at the cost of more battery every time you touch the screen. I feel the phone "i9300/stock JB XXDLJ2/div bloatware removed" (just thought i'd mention that part) uses a lot of battery already so I can live without the touch boost. I dont experience any UI lag as it is now, but I've also disabled a lot of stupid animations etc... Like I do on my computer! ... It's not for watching the UI "look cool" I want the s3's performance... It's for those amazing console quality OpenGLES 2.1 Games that keeps coming GO UNITY! ... :highfive:
About governors/schedulers (my experience):
Siyah 1.8 defaults to cfq which at least give ME more UI lag and worse test results.. Probably good at multitasking though (completely fair as it is called) but I want max "power" on the task I am performing (usually games) which deadline seems to provide. Deadline IS the default scheduler for the device anyway. I see it already at boot; every widget is almost done loading after login when with cfq I have to wait SEVERAL seconds
Will not try to explain what i believe is the schedulers function. Someone else have done it, I am sure because I have read it!Governor... The CPU's "mother in law" ... It tells (i believe the java engine) what data/when and in what order to send it from memory to the CPU.. i think...
Every other new siyah build has, as stated in the changelogs, f.x. "improved pegasusq", which is the governor I (and others) highly recommend you use with your i9300 btw. It is also the default governor. The fact that the governor is not static (it relies on some scripts (tweaking the governor...) made me think about wiping the dalvik in the first place (after reading up on what the dalvik is.. difficult to find a ANSWER it is mostly discussions where they seem to agree on the main function but "always" end up in a VERY dev/technical discussion that's when I stopped understanding.
Anyway... not found any improvements using anything other than the pegasusq governor on my i9300.
This is MY OWN trials and errors, and I am positive about the results. Any comments? Is this logical? I am fairly new to this.... My first rooted android phone!... so i appreciate corrections! (and respect people who have been doing this for decades (linux stuff...) i'm a MSOFT guy!
.. so Android is my first linux..:victory:@Guttsy911
Last edited:
Similar threads
- Locked
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
76Only for international s3 variant Disclaimer: Im not responsible if something funny happens to your device Read the guide as much as you want before proceeding with overclocking
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.
Advantage:
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.
Disadvantage:
* 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.
Undervolting :
The process where you provide less voltage to your cpu rather than the stock voltage.
Advantage:
* Reduced heat from your device.
* Good battery life.
Disadvantage:
* 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
CPU
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
Requirements:
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.
Step 1:
Set the current clock you want to test via ns tools. (Select max frequency in cpu tab).
Step 2:
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
Step 3:
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 )
Step 4:
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.
Notes:
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.
http://www.mediafire.com/?e7rk8cu3gw8usqj
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.*******************************
Credits :
* wikipedia
* 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
64GPU OVERCLOCKING
DIsclaimer :
*** I dunno if any other kernels support the very same overclocking , if it is possible kindly inform me ill update it in the post.
*** Using custom kernel or siyah kernel is purely of your choice, im not held responsible if something goes wrong
I would say GPU is by far the weakest hardware in s3, its weak in the sense that its using the very same architecture used for galaxy s2 with some additional improvements to clock it higher. Thanks to the head room given, though the maximum clock for our GPU is 440 Mhz we can over clock it to around 700 Mhz which is roughly 70% more than the stock. Yes it is possible. Thanks to our developer "gokhanmoral" who made it possible.
Advantage:
* Games can be made to run more smoother.
* Much smoother UI.
By default stock mali 400 GPU has 4 steppings , its clock frequencies are as follows
160 Mhz - 875 mv
266 Mhz - 900 mv
350 Mhz - 950 mv
440 Mhz - 1025 mv
Once you install siyah you will be having an additional GPU stepping(totally 5) along with the following available frequencies to choose from.
54 Mhz
108 Mhz
160 Mhz
266 Mhz
275 Mhz
300 Mhz
333 Mhz
350 Mhz
440 Mhz
533 Mhz - 1025 mv
600 Mhz - 1050 mv
640 Mhz - 1050 mv
666 Mhz - 1075 mv
700 Mhz - 1100 mv
800 Mhz - xxxx mv
The voltages for the above additional clocks are purely approximated values. So you can either undervolt or overvolt it as per your need.
Sample screenshot of stweaks gpu interface
REQUIREMENTS:
1. Siyah Kernel 1.5 beta 6 or higher
2. Stweaks
3. GLbenchmark 2.5(Egypt Classic and Egypt HD)
4. Basemark ES 2.0 Taiji
5. Nenamark
Testing methods and procedure:
Step 1:
Install siyah kernel and other mentioned apps and get used to stweaks.
Step 2:
Select the gpu frequency in stweaks along with the recommended voltage and apply the settings.
Step 3:
Open the above mentioned benchmark suits and run it.. if you feel any stuttering or artifacts when running the benchmark then you need some more voltage. Exit the suite and increase the voltage in stweaks by + 25 and restart the benchmark.
(** Egypt HD benchmark does stutters with currently all the mobile available in this world as the test is designed to stress the GPU to its maximum.)
Step 4:
Repeat step 2 and 3 if you need underclock/undervolt your GPU.
Notes :
* Though there are many available frequencies to choose from i would recommend not to use 54 and 800 mhz.
* Make your GPU steppings gradual (Eg : 1xx-2xx-3xx-4xx-5xx)
* If you feel your device warm let the device cool before testing.
* You can monitor your gpu frequencies in real time by using a tool called mali gpu status(caution: do not use these apps when benchmarking as it will degrade your result)
* Dont use any onscreen overlay apps like cool tool as it will degrade your benchmark scores.
Some benchmark results :
Below is the result comparison of basemark 2.0 (mobile with hd screens). Stock s3 gpu scores around 38 fps.
Here is the result achieved with max gpu clock of 700 mhz. It simply smashes all the records.
5Just my 2 cents
- Device: GT-I9300 (Galaxy S3 International)
- ROM: CyanogenMod 10.1 Nightlies
- Kernel: Siyah Kernel (1.9.1 at the time of this post).
- ASV4 CPU
Governor: lulzactiveq
I/O Scheduler: row
min. freq.: 200
max. freq.: 1600
Voltages for each CPU Step
1600 MHz --- 1275 mV
1500 MHz --- 1225 mV
1400 MHz --- 1187,5 mV
1300 MHz --- 1137,5 mV
1200 MHz --- 1087,5 mV
1100 MHz --- 1037,5 mV
1000 MHz --- 987,5 mV
900 MHz --- 937,5 mV
800 MHz --- 887,5 mV
700 MHz --- 862,5 mV
600 MHz --- 850 mV
500 MHz --- 837,5 mV
400 MHz --- 837,5 mV
300 MHz --- 812,5 mV
200 MHz --- 787,5 mV
Now the GPU:
Step 1 ---> 266 MHz @ 875 mV
Step 2 ---> 350 MHz @ 925 mV
Step 3 ---> 440 MHz @ 975 mV
Step 4 ---> 533 MHz @ 1025 mV
Step 5 ---> 640 MHz @ 1050 mV
Thresholds unmodified.5Thanks, Bala - though I have tried doing this for my S before, I havent seen the need yet to do this for S3.
Having said that, if you have the right OC, UV combinatons that worked for you - do you mind sharing them. That will be the best use of this thread.
My settings is always there in my sig mate
《tapatalked from galaxy s3》4misleading OP
no, you misunderstand. the ASV level is like a measurement of your chip quality. In the first post of this thread where you have given a listing of "the stock voltage for all clocks for your reference", all you've actually done is list the stock voltage for an ASV6 level chip. This is only useful to other people with ASV6 chips. For example my chip is an ASV3 chip, and these values would not be stock for me, they'd be undervolted from stock. If someone with an ASV7 chip used your values, they'd be over volting their chip.
Please either:
- get rid of this "reference" set of voltages,
- make it clear that these voltages are for an ASV6 level chip, or
- put down all the ASV level chip voltages and show people how to find out their level (note: to find out your chip level you will usually look at the stock voltages of your chip, making your reference redundant).
ASV chip level reference (thanks to AndreiLux): https://github.com/AndreiLux/Perseus-S3/blob/master/arch/arm/mach-exynos/cpufreq-4x12.c#L377
