Database Develop

[POLL] Overclocking, How far does you galaxy Go and S stay stable? without rebooting

How far is your Galaxy s stable?
mine just hits the 1.1GHZ, beyond that only crashes no matter which voltage i Use. please Use the poll so we have a good picture of what the average galaxy s is capable of..
also comment which version of SGS you are using and 8gb/ 16 Gb etc..

i9000m
PS this thread should be moved to General

had mine at 1.54ghz running MIUI with tk glitch kernel.
was amazingly fast, but my phone got hot quick, i dont like OC'ing i feel it may do more harm than good in the long run.
others may and will disagree but thats my opinion on it

Mine with 1.3GHz OC and some Undervolt is perfectly stable.....

simone201 said:
Mine with 1.3GHz OC and some Undervolt is perfectly stable.....
Click to expand...
Click to collapse
Agree with the chef ...
Although I can overclock to 1540MHz it does get hot and Im sure it will do damage in time ..
1300MHz is a great overclock ...
It will be interesting to see what my SGS 2 can be safely overclocked to

1.2 GHz seems ok for me - with UV
Doesn't really get hot.

Running mine @ 1440 MHz with MIUI but i think I can go higher if I want . I have the 8 GB version

1.3 and very stable and with great performance both q score caffiene mark and in daily use

Which voltage are you using?
Mine seems to freeze on voltages above the 1.3V,
above the 1.2 GHZ always freezes. I,m using darkeys 9.5 Rom.
someone some advice which rom is the best for OC, (just for benchmarking) for once.
rixsta said:
Agree with the chef ...
Although I can overclock to 1540MHz it does get hot and Im sure it will do damage in time ..
1300MHz is a great overclock ...
It will be interesting to see what my SGS 2 can be safely overclocked to
Click to expand...
Click to collapse

Mine can handle up to 1.3-1.4ghz

Im getting stable speeds of 1.7ghz. Im on watercooling though..
Sent from my GT-I9000 using XDA Premium App

1.4ghz is my max for full stability. 1.5ghz works fine (no reboots), but the CPU occasionally gives an invalid result during calculations, e.g. during benchmarks like linpack, results can sometimes be inaccurate; 1.44ghz also seemed to work, but I picked 1.4ghz max for longevity/reliability.
UV Values are:
100mhz - 200mV UV (750mV)
200mhz - 150mV UV (800mV)
400mhz - 100mV UV (950mV)
800mhz - 75mV UV (1125mV)
1ghz - 50mV UV (1200mV)
1.2ghz - 50mV UV (1300mV)
1.3ghz - 0mv UV (1400mV)
1.4ghz - 50mV UV (1400mV)
Max UV were found by starting from 100mhz Max frequency, decreasing UV until stable for 5 minutes of software decoding of 720p MKV, and then increasing Max frequency one step. Occasionally the previous step UV needed to be decreased by 25mV to obtain a stability at the next frequency step.
i9000M (16GB)

Guys, if you wanna push your phones to their full stability limits- play on Shadow Guardian game...)
Sent from my GT-I9000 using XDA App

I can run my SGS stable at 1540 MHz with glitch kernel in MIUI 1.5.20 ROM.
Total stability in a 48 hours stress test.
Enviado desde mi GT-I9000 usando XDA Premium App

Mine is stable at 1.5 Ghz with a 200mv undervolt, but only if I select it as a single frequency.
For multiple frequencies, I was stable at 1.4Ghz on an earlier kernel, but it's slightly unstable now... I'll probably try tweaking the governor.
I'm on a i9000m using tk-glitch's V9D-VC and CM7 #11 build.
By the way, shouldn't this thread be in general?

I am on MIUI v3 and CM7_SGSMTD_platypus-kernel_20110522_r0_quorra-prer11_test4-r2 kernel.
I don't use undervolt settings and 1.2 Ghz is fine for me; above values generally don't work stable.
By the way, 1.2 ghz is almost enough for all games and operations, I did not run into that pushing apps for high oc's.
Regards.

1.44GHz, extremely smooth and stable!

Never seen an option to go above 1.54, but 1.54 works flawlessly so I've chosen 1.5 in the poll. (16gb i9000)

1.3-1.4 GHz tkglitch kernel Miui v3
Sent from my GT-I9000 using XDA Premium App

It's not the ROm it's the KERNEL who can oc, i adviise using XAN, hardcore kernels in 2.2. or gto's ginger kernel at 2.3 they are stable and 1280 i guess it's the limit not to warm up
But a questin what send me an undervoltage config, to 1300 if the gpu games work for someone at 1300mhz
.
fstluxe said:
Which voltage are you using?
Mine seems to freeze on voltages above the 1.3V,
above the 1.2 GHZ always freezes. I,m using darkeys 9.5 Rom.
someone some advice which rom is the best for OC, (just for benchmarking) for once.
Click to expand...
Click to collapse

[Q] Overcome-Hermes, 1.4GHZ OC stable only when in UV -75mv

I was using stock for my gtab and lately installed Overcome-Hermes.
I noticed that the 1.4ghz oc using setcpu is unstable and often hangs in games especially "Dungeon Defenders" using the default assigned voltage of 1500mv
I played with the voltages for a while and found out that the 1.4ghz OC is stable when i set it at -75mv which is about 1425mv.
Is this normal? Aint the higher clock supposed to require more voltage?
Device does not freeze up, not even once so far, when i undervolt 1.4ghz to 1425mv.

RigelKentL said:
I was using stock for my gtab and lately installed Overcome-Hermes.
I noticed that the 1.4ghz oc using setcpu is unstable and often hangs in games especially "Dungeon Defenders" using the default assigned voltage of 1500mv
I played with the voltages for a while and found out that the 1.4ghz OC is stable when i set it at -75mv which is about 1425mv.
Is this normal? Aint the higher clock supposed to require more voltage?
Device does not freeze up, not even once so far, when i undervolt 1.4ghz to 1425mv.
Click to expand...
Click to collapse
i think its normal since it states here: http://overcome.mimzo.com/?page_id=68
"THOUGH FOR HERMES, BEST STABLE SETTINGS SO FAR: -100mV AND BELOW."

RigelKentL said:
I played with the voltages for a while and found out that the 1.4ghz OC is stable when i set it at -75mv which is about 1425mv.
Is this normal? Aint the higher clock supposed to require more voltage?
Device does not freeze up, not even once so far, when i undervolt 1.4ghz to 1425mv.
Click to expand...
Click to collapse
My experience with gingerbread UV/OC states that the higher the OC the lower the UV. However, seems that some UV is necessary for OC; especially for 1.4Ghz.
My setting for that frequency is the same; -75Mv and seems stable for a couple of days.
And yes and no, although higher frequencies need more power higher voltage is not a must.
Last note and 2 cents; if it is stable do not bother )

Something is not right here, with Froyo I had -200mV at all speeds - stable withouth problems, but with GB and -100mV the tab already unstable at higher speeds...

[Q] Overclocking the Tab

Hey does someone know the overclock configuration that was posted on the Overcome page once? I'm running on Overcome 4.1 with the belonging Kernel which allows me to get to 1.6ghz (theoretically) and I'd like to overclock to 1.2ghz.
I'd be very grateful if you could help me
Edit: I found this http://forum.xda-developers.com/showthread.php?t=1036020 but does this guide also apply to Overcome 4.1?

Just use Voltage Control or SetCPU. It's really not that hard at all. Just be careful with your voltages-overvolting will eat your battery more but may allow you to reach higher frequencies, and undervolting may get you better battery life but may make your tab unstable.
As a reference, I have my Tab running at 100-1.4 with smartassv2 and stock voltages on the Overcome 4.0 kernel.
Sent from my SCH-I510 using xda premium

thanks ;-) but which sheduler do you use?
for those who also have problems with overclocking and for
the newbies (like me =-D) I found this page which describes the usage of shedulers
and governors http://forum.xda-developers.com/showthread.php?p=19846297

IO Scheduler: CFQ
Governor: Smartassv2
At least that's what I use on my phone. I just left everything alone on my tab.
Sent from my SCH-I510 using xda premium

thanks, you helped me a lot ;-)
I'm using Voltage Control on 1.3ghz with stock voltages on smartassv2 and deadline and it runs pretty stable

Thanks, useful tip for me too.

I use SetCPU
OC max 1.3GHz, min 100MHz
-75mV from 100Mhz --> 1.0GHz and then -50 from 1.0GHz to 1.3GHz
PLUS various profiles to set max to 800MHz whilst screen off etc etc

that's exactly the same that I did =-D=-D=-D

That's pretty much what I have. OP, sorry I couldn't answer your PM, my tab is currently bricked and I haven't had the chance to recover it.
Sent from my SCH-I510 using xda premium

yea I have time =-D that's not so important, just make sure your tab runs again ;-)

phlooke said:
I use SetCPU
OC max 1.3GHz, min 100MHz
-75mV from 100Mhz --> 1.0GHz and then -50 from 1.0GHz to 1.3GHz
PLUS various profiles to set max to 800MHz whilst screen off etc etc
Click to expand...
Click to collapse
This is what worked for me as well, just don't check"set at boot" option till you've tried that speed for a few days and you config proves stable.

Joe Blough said:
This is what worked for me as well, just don't check"set at boot" option till you've tried that speed for a few days and you config proves stable.
Click to expand...
Click to collapse
Haha, I did check that option when I foolishly set the OC max to 1.6GHz
...I was just able to uninstall between one of the many lopping reboots
Anyway all, sorted now. In fact I have reverted to stock voltage for 1GHz up to 1.3GHz because playing Trial Xtreme2 would cause a reboot when I'd exited the game - seem's all ok now *touches wood*

Undervolt/Overclock Captivate...

What kind of success/failure are people having with overclocking and undervolting?
I'm doing this through ROM Toolbox Pro. Is there a better way? I'm a n00b with some of this stuff.
I have the phone overclocked to 1200mhz and all cpu levels are undervolted by 100mV.
Im doing so to get more performance, and better battery life. Just wondering what settings everyone else is using.
Also I'm using CM 10.1, with the BlueMint Theme.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.

DR650SE said:
Just wondering what settings everyone else is using.
Click to expand...
Click to collapse
Every phone has different limits. It's just like PC overclocking, no two CPU/MB/RAM combos are exactly the same. In general most of Captivates will handle 1200 step OC with default voltages. Not too many will handle 120% live OC though. It doesn't matter what tool you use to OC. All tools try to play with the same kernel settings. In my experience UV saves very little battery but increases significantly the chances to get stability issues. This is why I never play with UV. My particular phone can do 1400 step OC or 1200 live OC with 1350mV. I run it on 1200 step OC @ default. Also, keep in mind that different ROMs/kernels give different OC results.

RE: undervolt
I agree with Val D that undervolting will not show any significant benefits. Overvolting has helped me with stability while overclocking. I use the free Voltage Control app for voltages, or the free NStools app. Rom Toolbox is a great app too- I use it for many other things- stick with what works for you. Currently I am running at 1200Mhz step, at 120% Live OverClock to get CPU up to 1440Mhz, and ARM voltage of 1350mV at that 1200Mhz step. Rock solid. Battery life suffers a bit, but I run this way for gaming. Day-to-day regular usage I just set to 1400Mhz step and no Live OC, default voltages. I have run fine in the past at 1500Mhz, no Live OC. Overclocking the CPU tends to make my phone a bit snappier and more responsive. A big battery drain that affects my phone is an app such as Gmail running in the background, or leaving wifi enabled when not in use. Setting the phone to Airplane mode has been a big battery helper too (I do not make any voice calls on this phone anymore). Governor and scheduler setting can also have a big effect on battery life. I searched for this post I made a while back that linked to two great articles on studies of battery life and voltages, and ended up reading through them again:
http://forum.xda-developers.com/showpost.php?p=28141250&postcount=1194
Great information. Edit: just figured out how to link articles in my signature.

Thanks guys. I know each one over clocks differently. Just looking for some rough outlines. Thanks for the links. I'll be reading up on those. I have extensive computer over clocking experience, but on e phone its a whole new ball game. Basically trying to make this phone last longer.
I'll have to learn what live OCing is vs step OCing.
Thanks again!
Sent from my GT-P3113 using Tapatalk HD

I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.

PxGold said:
I just do 1200mhz OC using CyanogenMod 10.1 - the option is in the performance menu. So far no problems.
Click to expand...
Click to collapse
Awesome. Didn't even realize that as there. I've been using ROM Toolbox to OC to 1200MHz.
Sent from my Samsung Captivate/JB CM 10.1 via Tapatalk.

overclocking to 1200 mhz will made any difference ?

Klitoni said:
overclocking to 1200 mhz will made any difference ?
Click to expand...
Click to collapse
I really didn't notice much of a difference in speed or responsiveness using CM 10.1.

Good Gaming Kernel for CM 10.1

What is a good gaming kernel for CM 10.1 ?
Sent from my LG-P880 using xda app-developers app

I'm using iodak v7. It gives great performance, smoothness and CPU throttle doesn't kick in until high temps like 80-85 are reached. Most games reached around 80 max in my case and cores were still running at 1.5GHz. I really love this because it doesn't cause lags! Try it. Btw, while gaming, I OC CPU to 1.7GHz and GPU to 600Mhz which gives additional performance.

scarfaceq said:
I'm using iodak v7. It gives great performance, smoothness and CPU throttle doesn't kick in until high temps like 80-85 are reached. Most games reached around 80 max in my case and cores were still running at 1.5GHz. I really love this because it doesn't cause lags! Try it. Btw, while gaming, I OC CPU to 1.7GHz and GPU to 600Mhz which gives additional performance.
Click to expand...
Click to collapse
Are there any bugs and how is battery life ?
Sent from my LG-P880 using xda app-developers app

battery life is what you would expect, around 3-4 hours on screen time