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)

[POLL] Tested Dual-core ( 972 mhz) vs Single-core ( 1.836 Ghz)

Hello guys,
Since i`ve seen so many debates about single vs dual-core, today i was bored and i tested with antutu and quadrant this thing.( I know that benchmarks isn`t a real proof in day-to-day performance )
WANT THE SCRIPTS FOR UNDERVOLTING AND FORCING CPU1 ONLINE OR OFFLINE ? See 2nd post
SO , what I actually did:
-flashed a freshly new rom ( using elegancia 3.1.0 for about 2 weeks and i found to be very stable and smooth with better battery life than any other rom i`ve tested)
-flashed latest bricked kernel min 192 mhz max 972 mhz with gpu oc @300mhz, lagfree governor, I/O deadline, both cores online via init.d script, booted and tested with antutu and quadrant and then i let the phone settle for a while to see what is the power consumption in stand-by with battery monitor widget.
-after that, i flashed bricked kernel with only max speed change to 1836 mhz, cpu1 offline via inid.d script and made those tests again
Here`s what I got:
Antutu: 4827 (both cores online, clocked @ 972 Mhz)
Quadrant: 2592
BMW: -19mA
Antutu: 4593 ( cpu1 offline, clocked @ 1.836 Ghz )
Quadrant: 3393 ( cpu1 offline, clocked @ 1.836 Ghz )
BMW: -28mA
Those numbers doesn`t reflect exactly the user experience. Some apps opened faster with 2 cores, some faster with only 1 core clecked at higher speed. The only major difference i noticed was in the browser( stock ICS browser) where the more fluid experience was with both cores on.
I`m gonna test those 2 configuration further to see which one has better battery and post some screenshots.
I will add a poll to see which configuration you think is the best.

Be aware that SoC are not created equaly, so the UV script or OC will NOT work with all devices.
Unrar the archive and choose what you want
This files needs to be copied in /system/etc/inid.d and then set the right permissions ( read: all 3 needs to be checked; write: owner checked; execute: same as read) . You need a file explorer that has access up to root ( i recommand Root exploer)

Benchmarks should always be done using Performance governor for consistency

Michealtbh said:
Benchmarks should always be done using Performance governor for consistency
Click to expand...
Click to collapse
I knew that, but i wanted a more real-life experience, and in my opinion there isn`t that much difference in lagfree vs performance. I ran benchmarks 2 times and the scores where almost identical

Please be aware that because of the instruction sets hard coded at low level into the cpu it doesn not mean that 2x 900mhz cpu cores is equal to 1x 1800mhz cpu core because of the way in which the second core is utilised. Its exactly the same with pc's hence why sometimes an AMD cpu with 2 cores can give a better real world performance benchmark than an intel cpu with 4 cores. the same applies vice versa, it just depends on what instruction sets were used and how the cpu is used. Benchmarking stuff like this is not a reliable way to test

Jonny said:
Please be aware that because of the instruction sets hard coded at low level into the cpu it doesn not mean that 2x 900mhz cpu cores is equal to 1x 1800mhz cpu core because of the way in which the second core is utilised. Its exactly the same with pc's hence why sometimes an AMD cpu with 2 cores can give a better real world performance benchmark than an intel cpu with 4 cores. the same applies vice versa, it just depends on what instruction sets were used and how the cpu is used. Benchmarking stuff like this is not a reliable way to test
Click to expand...
Click to collapse
Thanks (I'd use thanks button,but i'm limited to 8 oer day) for clarifying this for me and any other users, this post should be sticky because many members on xda think that way. I am aware that 2x900 doesn't equal 1x1800, but I didn't knew the exact explanation. The only reason that I did these tests was to see which configuration gives the best battery life. Their not equal, but acording to antutu, quadrant and end user experience they are comparable

Thanks for your time in doing these tests... It might not be reliable but it was interesting to know bout it... Im curious between the two tests though, which test puts the cpu under more stress? the first test shows awesome result on the battery so being single core might stress the cpu more, im guessing
Sent from my HTC Sensation using Tapatalk

AndroidNeophyte said:
Thanks for your time in doing these tests... It might not be reliable but it was interesting to know bout it... Im curious between the two tests though, which test puts the cpu under more stress? the first test shows awesome result on the battery so being single core might stress the cpu more, im guessing
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
33% left and it's running for15 hours with 2 cores

ICS Overclocking Resources/Guides - Heat issues Kernel tests Post your experiences -

Here's a response from a PM i recieved about my Antutu benchmark scores. This is meant to be a reference to others who are working to squeeze optimal performance out of their captivates.
Hi, want to know what setting you do to reach more than 4000 points on antutu bench xD i just cant go more than 3800
Regards
Click to expand...
Click to collapse
Overclock at your own risk!
I am not responsible to any damage to your phone
I've had lots of experience over clocking desktops computers, I started when I was 14 years old or something. I am very happy to share my experiences here with my captivate.
Here's what I've been using to test the stability and speed of each incremental change: https://play.google.com/store/apps/...chMark&feature=nav_result#?t=W251bGwsMSwyLDNd
It's Antutu Benchmark.
Some may not like Antutu, and that's understandable, it's just the standard i have used to compile my testing results. if you have a better app to use suggest it!
The highest Antutu score i was able to achieve was 4044 when i was on 1.508 ghz. running Devil .86
Recomendations/Results:
I've been testing mostly stock settings between devil .86 and semaphore 1.2.5sc and devil keeps coming out on top with it's scores. not trying to start a war, but devil is just faster. don't get me wrong i love semaphore.
I am using Slim ICS 4.1, it's been the most stable ROM for me so far, if somebody can post their results with a different ROM and kernels then i gladly support it!
Slim: http://forum.xda-developers.com/showthread.php?t=1517486
Tests between Semaphore 1.2.5.sc and Devil .86
I had both semaphore and Devil running live OC of 116% and after each test devil kept winning by about 50-80 points.
I recommend the Devil Kernel by DerTeufel1980, DerTeufel1980 is very helpful and supportive, he also turns out updates like a machine!
The devil kernel supports increasing frequency as well as live OC. It also has so many other cool features that make it fast(like GPU overclocking). This is why I recommend this kernel for Overclocking speed and stability.
His kernel is here: http://forum.xda-developers.com/showthread.php?t=1642460 Sometimes he posts a downloadable release in the middle of a page so you usually have to search for it.
Advice/Settings
Overclocking to high stable frequencies, and having the least apps active is the key to getting the highest overclocking scores with Antutu.
To get scores over 4000 I use this set up:
My settings, SIO, Conservative governor, Frequency at the 1300mhz step, live OC at 116%(this yielded 1.508ghz). I had UKSM on(whether on or off didn't seem to make a difference during my tests), i had the GPU overclocked to 250mhz. I was using the XL mem version (391mb ram).
I had intended on running more tests on the big mem version but the constant reboots got tiresome, if anybody wants to take this up I'll gladly support it.
Crashes: Crashes are inevitable when testing. sometimes you get lucky and only the app crashes, most of the time though you will get a frozen screen or a few seconds followed by a reboot. depending on your kernel some may reset your settings. Use NS tools and save a setting that you know is stable and save your test settings so you can start from where you left off.
Voltages: the key to stability!
BE VERY CAREFUL WHEN YOU ADJUST YOUR VOLTAGES! too much is harmful to your chip!! Heat and overvolting is harmful!
these are my voltages:
Arm voltages
1400mhz it's 1.475
1300mhz its 1.450
Int Voltages
1400mhz it's 1.25
1300 it's 1.225.
The rest is stock. If anybody has found stable underclocking for the lower frequencies please post them here.
Live OC:
Something strange i noticed was that whenever i would do a odd numbered live OC i would get major instability... 116% was much more stable than 115%. weird huh? also i am pretty much unable to get a stable live OC of more than 116 regardless of the frequency step. Each phone will have it's own stability limit for Live OC. Some phones can go all the way up to 130%, but that's rare.
the key is to keep finessing it and carefully and incrementally change things till you find a nice sweet stable spot, other phones can achieve more live OC.
My favorite Fast Stable Safe setting:
My phone is almost always on this setting for everyday use: SIO, Conservative, Freq OC at 1200 and Live OC at 116% yielding 1.392ghz. with a bit of voltage increase this has become my favorite setting, i always use this setup.
Some may balk at my use of the conservative governor, I Love it actually, CPU spy reports that the conservative governor barely ever uses the highest step for regular usage. Which is great because you don't need the highes step to be running all the time as most actions don't require it, the less high voltage you send to the chip the better. It also helps with battery life.
HEAT!!!!
Warnings about heat. voltage increases mean more latent heat. your phone is a closed system so the heat gets locked in easily... Warm is allright(not wonderful) any hotter than warm and you need to take steps to manage the heat. I've found two easy ways to deal with it, aside from putting it in my refrigerator lol
For stress testing I ussually have the battery cover off, one less thing to get hot.
One simple way to manage it when you feel the sd card slot warm is to press the SIM/Sd slot to your lips and blow air through the phone, this will help cool it down. another way to manage the heat is to do this
{
"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"
}
I borrowed a cooling fan from my gaming computer and set the phone up on it with the battery cover off. this really helped keep it cool.
Also, never leave your phone sitting in the sun on a hot day, I don't know why you would in the first place. But just don't.
Higher scores are achievable... just keep tweaking things.. I deleted all my user apps so nothing would run in the background and that did helps my scores a bit.
Also airplane mode prevents unwanted texts form interrupting testing. that way the phone can focus only on the task at hand
I bet wiping the SD card would improve read/write speeds incrementally...
If somebody wants to research this please post it here
Please read this before you post "results"
Please run at least 2 or 3 tests to sort of average the scores before you post about a result. This will help keep information clean of errors that can affect test results.
for example when i was doing a 1.392ghz test on Antutu, during the knights hacking thier swords scene a glitch happened and my frames per second shot up to 102 fps. It occurred for a few seconds but it was enough to offset the scores A LOT. I got a 4185 on 1.392ghz which doesn't seem possible. consequently I hold the #6 score listed for the captivate :laugh:
This is why I say get an average for the scores. with my 1.392ghz set up i tend to get scores ranging from low 3800's to high 3900's
Remember each phone is different!
Have fun tweaking!
Hope this helps!

Hi.
Thanks for sharing.
My undervolting values are:
100 Mhz = 800
200 Mhz = 850
400 Mhz = 950
800 Mhz = 1125
1000 Mhz = 1225
1200 Mhz = 1300
The attachment is a graph with my experiments to find a fast and stable configuration. The red line is my best so far.

BitteredBro said:
Hi.
Thanks for sharing.
My undervolting values are:
100 Mhz = 800
200 Mhz = 850
400 Mhz = 950
800 Mhz = 1125
1000 Mhz = 1225
1200 Mhz = 1300
The attachment is a graph with my experiments to find a fast and stable configuration. The red line is my best so far.
Click to expand...
Click to collapse
Excellent! i might have to try some of your undervolting! Did you do tests with a max voltage set to determine stability?
also what do you test it with?

What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app

melvinaury said:
What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
My guess is that it's the ARM voltages, idk though.

My phone doesn't like speeds over 1.4 nor live OC over 20%. Those are my max settings without freezes or reboots.
For stability testing I use nbajam and blood and glory. Those games are very sensitive to changes in voltage and overclocking.
Sent from my SGH-I897 using xda premium

melvinaury said:
What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Those are arm voltages.
I don't feel comfortable messing with Int voltages.

Anybody able to get a stable 1.6? I can't seem to get it stable...
Sent from my SGH-I897 using xda app-developers app

I think Icepack might work better!

bravomail said:
I think Icepack might work better!
Click to expand...
Click to collapse
Hahaha! Good idea!
Sent from my SGH-I897 using xda app-developers app

baconatorXVI said:
My favorite Fast Stable Safe setting:
My phone is almost always on this setting for everyday use: SIO, Conservative, Freq OC at 1200 and Live OC at 116% yielding 1.392ghz. with a bit of voltage increase this has become my favorite setting, i always use this setup.
Some may balk at my use of the conservative governor, I Love it actually, CPU spy reports that the conservative governor barely ever uses the highest step for regular usage. Which is great because you don't need the highes step to be running all the time as most actions don't require it, the less high voltage you send to the chip the better. It also helps with battery life.
Click to expand...
Click to collapse
Great info, thanks. I had my phone running 1.5ghz (directly, no Live OC) all day long on Glitch kernel a while back... before I started flashing Devil. Right now on Devil I am trying out underclocking while using live OC, so I have the frequency set to 800 with a 110% Live OC so the CPU is at 880mhz. SmartassV2 and SIO. It is very responsive and I should try a higher Live OC I think.
I had trouble using the GPU OC feature... have you been using that at all? I think I remember someone mentioning they had GPU OC plus a Live OC on top of that... I would think that would be harmful to the GPU, right? I set the GPU back to 200mhz since I was getting more and more frequent FCs, freezes and reboots. Thanks for your posts and sharing your results.

They Drew First Blood said:
Great info, thanks. I had my phone running 1.5ghz (directly, no Live OC) all day long on Glitch kernel a while back... before I started flashing Devil. Right now on Devil I am trying out underclocking while using live OC, so I have the frequency set to 800 with a 110% Live OC so the CPU is at 880mhz. SmartassV2 and SIO. It is very responsive and I should try a higher Live OC I think.
I had trouble using the GPU OC feature... have you been using that at all? I think I remember someone mentioning they had GPU OC plus a Live OC on top of that... I would think that would be harmful to the GPU, right? I set the GPU back to 200mhz since I was getting more and more frequent FCs, freezes and reboots. Thanks for your posts and sharing your results.
Click to expand...
Click to collapse
No problem, your post on the devil kernel thread helped convince me to switch to SmartassV2. I'll probably bring a condensed version here for whoever else stumbles here.
I've only had one troubling experience with gpu overclock on. I was going for a high antutu score running something like 1.5ghz. Anyways, for whatever reason during one stage of the test, can't remember which, i got a strange green flashy line across the screen. it was very unsettling cause i thought it was a hardware issue that i would have to live with. it stayed there even though i stopped the test. turning the screen on and off didn't fix it either. thankfully rebooting fixed the issue.
The only other time i've seen visual artifacts like that is when I would overclock my graphics card on my desktop. so i assume it was a graphical processing error.
I can't say for sure if gpu overclocking AND live OC together cause problems. although I wouldn't be too disappointed if my cappy died, then i'd unfortunately have to upgrade to the Galaxy SIII

Dumb question, but how have you two over clocked the gpu? Is it possible to underclock while having the CPU overclocked? For my phone, the gpu always locks before the ram/proc. I can tell because the screen gets all fuzzy with lines which makes me reboot.
Sent from my SGH-I897 using Tapatalk 2

goob1284 said:
Dumb question, but how have you two over clocked the gpu? Is it possible to underclock while having the CPU overclocked? For my phone, the gpu always locks before the ram/proc. I can tell because the screen gets all fuzzy with lines which makes me reboot.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Well we are able to overclock our GPU's because the devil .79 and on kernel allows the choice between either 200mhz(stock) or 250mhz.
to underclock the gpu you would need to talk to a kernel maker.
Maybe you need to increase your voltages... don't increase them too much though. I'm not totally familiar with the architecture and design of each processing bit inside the captivate but from my knowledge of computers, more voltage makes it more stable.
this question should be asked to a kernel maker! i hope you find your solution.
are you past warranty? you're positive it's not a rom issue? did this happen while it was stock?

baconatorXVI said:
Well we are able to overclock our GPU's because the devil .79 and on kernel allows the choice between either 200mhz(stock) or 250mhz.
to underclock the gpu you would need to talk to a kernel maker.
Maybe you need to increase your voltages... don't increase them too much though. I'm not totally familiar with the architecture and design of each processing bit inside the captivate but from my knowledge of computers, more voltage makes it more stable.
this question should be asked to a kernel maker! i hope you find your solution.
are you past warranty? you're positive it's not a rom issue? did this happen while it was stock?
Click to expand...
Click to collapse
Overclocking GPU is an option, but it is disable as well as the 56/60 Hz switch.

[Q] Is the Infuse underclocked from the factory?

I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?

k-semler said:
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
Click to expand...
Click to collapse
uhh well.... yea and no. there are a few things you need to understand about microprocessors. no two are alike. they are built on a scale of a few nanometers and any difference causes a significant difference. to keep production numbers up there is a line they have to draw between performance potential and stability. more chips will be stable at lower clocks so they pick an speed they can get a high production number out of. sometimes a whole line of chips is produced with exactly the same core. chips that pass the highest get boxed as the highest performing and priced. chips that dont pass will either have specific features turned off, cores turned off or be underclocked and sold as lower models. in addition to that the top performing models are actually over priced, and often many more pass the tests than they need so perfectly good processors are intentionally disabled to fill the market for lower speed processors, so yes the cpu may be "underclocked" in a sense. but i don't know if that really applies to the infuse because i don't know if there are any chips in the same family that have a higher rated clock speed, if there are they aren't used in phones.
in example, on my pc i have a 3 core processor, it's actually a 4 core and i can even turn the 4th core on in bios, but a certain percentage of that particular model of chip will be unstable with the 4th core active.
another thing to understand is how the clock speed is set. there is a buss and a table of multipliers and dividers. so as one part of the chip oscillates at one frequency the multipliers and dividers say how may times per oscillation the other components go. the cpu speed changes by changing these multiplier values. the problem is that there are only so many multipliers the cpu is designed to use. this is a hardware limitation and can't be overcome so at some point the only way to get more clock speed is to change the buss speed which affects the entire system and will cause instability in most cases. occasionally you can get around this if you change the multiplier values for other componants as well but it's probably not a good idea to mess with it. the hummingbird chip only has multipliers to go to 1600mhz regardless of stability unless you mess with the buss, one developer got the galaxy s to 1700 with buss overclocking but some things didn't really work at that speed and it took a lot of changes to other system clocks. snapdragon chips can go to higher clocks and process numbers better but the hummingbird is better for graphics and multimedia which is more important on a modern phone imho.
so yeah 1600 is it, as far as practicality goes anyway. there are a few infuses that can only go to 1400-1500 as well and galaxy s phones which have the same clock limitations but are only rates for 1000mhz rarely go to 1600, but a few do, my captivate was absolutely peaked out at 1300, believe me i tried to get it higher, i tried a lot of things with voltages to try to get it stable, but even 1300 took some doing. it took a long time before developers even produced a kernel for the sgs that used clocks over 1200 because many of the early builds of the sgs series were much like mine and were not stable at high speeds.

Beautiful. :thumbup:
Sent from my SGH-I997 using xda app-developers app

[Q] A question about overclocking

How much do you overclock and how stable is your tablet? I have mine clocked at 1400 constantly and so far only had a couple of hang-ups. I know from my experience that it's pretty unstable at 1700, but what about 1500-1600?

Beyond 1200 doesn't really gain you much and may even degrade performance, along with instability. Might give you better benchmarks, but real world, 1200 is probably the sweet spot for stability with modest performance increase.

1400MHz for years, tried 1500MHz but crashed fairly regularly

I've been sitting at 1400mhz for years as well. Noticable improvement in even the smoothness of the GUI.
Sent from my C6606 on 4.4.2 KitKat

Been using it at 1200 MHz -- while 1400 was ok, was using too much juice. Also, I don't see that much difference betwen both clocks, although I'm not a heavy gamer anyway.