Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Shadow Life said:
Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Click to expand...
Click to collapse
Yes you can, depending on the kernel you use, oc your phone even up to 1.5 ghz.
Flash Glitch, MNICS, Devil or Semaphore Kernel for ICS roms
Do so with care as OCing WILL degrade your processor faster.
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Oc SGS 1.2Ghz
nwsk said:
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Click to expand...
Click to collapse
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Shadow Life said:
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Click to expand...
Click to collapse
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
upichie said:
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
Click to expand...
Click to collapse
+1
Related
I just overclocked my droid using the tazkern 1.1 Besides being miserably slower than before when I boot up, It doesn't even give me the option to go up to 1.1 ghz. Any suggestions?
suggestion:
and don't take this wrongly in any way..
Stop overclocking so much!! It's a damn phone, not a gaming rig. That and also you really risk of damaging of your CPU and other internals...
My Milestone is running stock. It stays cool and is fast enough. This is after i tried some weeks running it on 800 Mhz. It gets too hot and that also during conversations.
I get where you're coming from but still, I was just getting a lil tired of the the thing lagging every time i opened the app drawer or market. I actually fiddled with it a little after I posted that and got it to run perfectly. And I think Im fixing to try out a 1.2ghz kernel just to see what happens. So far there's been no overheating or crashing.
ECC is kicking in and making your phone slower. Use a lower clock, your phone doesn't support it.
Actually its running quite smoothly so far. Ive been running it for around 30 mins now and its super fats, smooth, and appears stable. Ive tested it on youtube tho and its getting pretty warm.
Mines runs all day, every day at 1.2ghz. The quirks are not from the overclock. Thbey were always there.
Thats what Im on now. I think Im using the slayher 1.2ghz kernel.
Droid or Milestone?
If Droid, you're in the wrong forum. This is the Milestone one.
I have mine at 720mhz overclocked and it works fine,i dont have any heat problems,i always check the battery tempeture via SETCPU app,always is at 30C to 32C,not more than 32C!!!
I love it more tha my iphone
I think people need to learn the risks of overclocking.
You may say its stable and running fine and "just a little warm" but you are infact destroying your CPU.
If you touched your computer case and "it was a little warm" you would be worried.
Consistently hot systems aren't expected to last anywhere near as long a cooler systems. Thermal fatigue in silicon results in cracks in transistors, and transistor mounting failures, in particular. Of course, just one transistor failure on a complex system such as a motherboard or graphics card can result in the entire system failing. And a replacement board being an appropriate fix.
Source: http://ezinearticles.com/?The-Effect-of-Heat-on-CPUs-and-Computer-Systems&id=2310508
For computer CPUs, but you get the idea.
Oh dont worry. I turn my phone by the time it burstsinto flames. And btw i apologize but i did post this in the wrong forum. Oops.
droid doesnt equal milestone. development is different due to locked kernel / bootloader..
but saying that. i use 1.2ghz with 70 vsel, or 1ghz with 60 vsel.
its a little lower voltage, but i assume it saves battery.
might not be stable for you, but i've been running it for 8 days straight now..
i dont use a lower voltage cuz i heard it damages the cpu. i stay within safe tested voltages
Link to german oc voltage testing
milestone users have to rely on a kernel module to overclock.
DannyDroid said:
words
Click to expand...
Click to collapse
overclocking damaging the phone? please.. the omap 3430 has the same CPU as the 3630
3630 is upclocked to 1.2ghz and is in the droid 2. i suggest you checking out T.I.'s website. our cpu is clearly capable of reaching these speeds without damage.
Besides. i've had my milestone ever since it came out. I've been overclocking it since it became an option and my phone has never died.
but saying all that. an inexperienced user playing with voltages can seriously damage their phones if they dont know what they're doing. too high or low of voltage or speed can result in a brick.
EDIT: sry for bringing up the droid/milestone thing again, i didnt read the post above me lol
1xinfusion said:
droid doesnt equal milestone. development is different due to locked kernel / bootloader..
but saying that. i use 1.2ghz with 70 vsel, or 1ghz with 60 vsel.
its a little lower voltage, but i assume it saves battery.
might not be stable for you, but i've been running it for 8 days straight now..
i dont use a lower voltage cuz i heard it damages the cpu. i stay within safe tested voltages
Link to german oc voltage testing
milestone users have to rely on a kernel module to overclock.
overclocking damaging the phone? please.. the omap 3430 has the same CPU as the 3630
3630 is upclocked to 1.2ghz and is in the droid 2. i suggest you checking out T.I.'s website. our cpu is clearly capable of reaching these speeds without damage.
Besides. i've had my milestone ever since it came out. I've been overclocking it since it became an option and my phone has never died.
but saying all that. an inexperienced user playing with voltages can seriously damage their phones if they dont know what they're doing. too high or low of voltage or speed can result in a brick.
EDIT: sry for bringing up the droid/milestone thing again, i didnt read the post above me lol
Click to expand...
Click to collapse
The OMAP 3430 is a 65nm chip while the 3630 is a 45nm chip. Newer smaller manufacturing processes = cooler chips. They are NOT the same chips by far.
Furthermore, you realize that many memory chips are made equally. Then the memory manufacturers go and test out different batches. The ones that clock higher can be stamped as higher clocking or faster timing memory. They may be made the same, but usually the better made batches go to the higher end parts. The same goes when Intel makes CPUs. The crappy CPUs with some problems become Celerons. It might've been a Core 2 Duo or i7 or whatever, but Intel goes and disables cores/cuts off memory if it was not a good batch.
You can't look at models and go "well that CPU can do it, why can't mine."
If people have knowledge of CPU overclocking here where you understand that people look for certain serials/batches of Core i7s for best overclockability. Even though to Intel they all meet i7 930 specifications, there's still separation within the i7 930 crowd. Certain batches are better. Maybe not good enough to be an i7 950, but still better than the worst i7 930.
The other question is: What is stability? How do YOU determine what is stable? apps not crashing? In the overclocking world we run Linpack tests for like 24 hours before calling computers stable. Just because you can boot into Windows or Android or play Angry Birds for 3 hours doesn't mean much. It doesn't mean you don't suffer from bugs from overclocking. It's hard to say unless you do a full stress test on your CPU.
The 3600 OMAP is clearly superior to the 3400 series, but I do think that the latter is more overclockable.
I've had no overheating issues at 900MHz, 56 vsel, don't feel the need for higher frequency.
Will, this is all starting to go over my head. I'll just sit in the corner n twiddle my thumbs.
Just think of the 3600 as a 2010 Intel i7 chip and the 3400 as last year's i7 CPU...same platform and architecture but smaller manufacturing process and (probably) a bit faster at the same clock speeds, with the same features.
applebook said:
Just think of the 3600 as a 2010 Intel i7 chip and the 3400 as last year's i7 CPU...same platform and architecture but smaller manufacturing process and (probably) a bit faster at the same clock speeds, with the same features.
Click to expand...
Click to collapse
I was just trying to get at the same idea
I might have been too exact in my words but this is what i meant
and something fyi is that the OC capability of both chips are "capped" at 1.2ghz ... its just dangerous and unstable after that.
heat wise ? I'm inclined to believe that heavy wifi / 3g usage provides a higher source of heat than our petty oc-ing. Our cpus are clearly capable of this. true you make a good point. smaller architecture = cooler and less power. but the heat is probably out of the question. i use setcpu to display my temp. it never goes past the rated temperature. in fact it always stays at around 35c
when using wifi/3g on the other hand.. no need to say. the fact that these chips have no thermal barrier between them and the fact that the heat is able to be felt on the surface on your phone... in such close proximity to the radio chips, the cpu is not going to be heated by oc but by these other factors.
its safe to say you should lower your 3g / wifi usage to reduce thermal stress on your phone
stability wise... I'm not the one to stress test or w.e for long periods of time, but the link i've attached to my previous post shows a lot of people who have.
maybe you should check that out. I'm just here to relay information.
I have mine overclocked to 800 and it stable and quicker than stock its not all cpu its the amount of free memory you have at any given time
here is another very interesting page. this time regarding the droid
http://www.droidforums.net/forum/droid-hacks/20406-max-temp-while-overclocking-12.html
be aware that a lot of the temperatures are in fahrenheit.
highest temps of these guys average around 40-50 Celsius, way below the rated temp
Actually, mine has been running smooth this past week or so with no abnormal heat or crashes.
Sent from my Droid using Tapatalk
I've seen some people that have OC'd their CPU.
I know OC'ing a computer's cpu eventually takes it's toll on the processor, and you get less life out of it. Not to mention the extra heat from oc'in it. Does the same apply to these phones?
Do you get a lot more heat from the cpu?
You can monitor your CPU temperature using free apps and judge for yourself, since every phone may differ in optimal oc/uv settings. However, I personally haven't heard of anyone burning out their phone CPU through an overclocked kernel, since they're generally limited to 'tested' oc ranges.
There is actually a lot of code written into the Galaxy S by Samsung for 1.2 Ghz, but it was taken out due to charging instability. The temp on mine has never gotten too high at 1.2, especially since it doesn't spend a lot of time there unless you are playing 3D intensive games.
What are the benefits of OC/UV (particularly for CM7)?
I know of improved performance due to OC, but what does UV do in regards to performance. Also, how does an OC/UV kernel compare to one without the option?
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
xredjokerx said:
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
Click to expand...
Click to collapse
You can do either or both but don't have to do both. At some point UVing will cause a crash. Right before that point it can cause performance issues. See the link below for instructions on how to find an optimal UV level to maximize battery savings and performance.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
OCing improves speed but can also cause stability issues. For a captivate this usually isn't a problem until you get past 1.2 ghz. After that, it depends on the kernel but I have yet to find a kernel that is completely stable past 1.2 ghz under stressful conditions. Samsung designed the processor to handle 1.2 ghz and in theory it can go up to at least 1.6.
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
venomio said:
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
Click to expand...
Click to collapse
Odd as it sounds, my battery life on CM7 is close to 50% better when it is OC'ed to 1.2 ghz and UV'ed than it was on the froyo ROMs under the same conditions.
That really is odd :S I think I'll try it myself.
so, i am using the Fear Rom and with the OC karnel. i played around the max sittings to 1.4 and tried quadarant. amazing score of 4150. nice... but what will happen if i keep it at 1.4 ?
will it over heat the phone / burn the GPU/CPU when playing games for example ?
i understand the battery life will be shorter. but what other disdvantages ?
ll_l_x_l_ll said:
so, i am using the Fear Rom and with the OC karnel. i played around the max sittings to 1.4 and tried quadarant. amazing score of 4150. nice... but what will happen if i keep it at 1.4 ?
will it over heat the phone / burn the GPU/CPU when playing games for example ?
i understand the battery life will be shorter. but what other disdvantages ?
Click to expand...
Click to collapse
You could dmg ur cpu. But Tegra is known to run 1.8Ghz stable. So with 1.4 you should be good.
Sent from my LG-P990 using XDA App
Oh!! Great 1.8Ghz but only 1.4Ghz is very drain my battery to much.
In the long run, your cpu might get affected but its shouldn't happen so soon.
That said, in my honest opinion, don't need to OC the chip.
The same OCing rules apply from the PC World. The same batch of chips have varying maximum OCing capabilities and thus different stabilities. Although you can stably run a chip at a higher clock, it will definitely shorten its life (Sometimes it could kill it in a year, sometimes beyond what we can measure.). Chip makers purposefully OC chips during tests to simulate the stress effects of using the chip over a long period of time (OCing that makes it seem like the chip is being used for months or years.). Nvidia sticks the Tegra at 1 GHz half because it's cheaper to do so (don't need to ensure higher clock rates which would mean a larger percentage of their chips won't last doing it.) and half because of marketing (At the time, no one has 1.2 GHz like we do now. From what I've seen, Tegra 2 can do 1.2 GHz easy.).
So what it comes down to is how long you plan on keeping the phone and how lucky you are. =)
Imo, in the interest of power savings (P = (V^2)/R), the gains of OCing having an exponentially worse effect on battery life.
imho theres currently no point in oc'ing the Tegra2 in Optimus at all.
Theres no real life benefit, only theoretical benefit when running benchmark apps for show off.
Theres not a single application or game out there today that require more processing power than what the Tegra delivers at 1ghz - and not a single one out there that will run any better or faster by oc'ing because the demand for processing power to run the application or game at its maximum capacity are allready met at 1ghz
Basically there are only negatives in terms of decreased battery and cpu life for nothing but a screenshot of a higher quadrant (or whatever) score
If at some time in the future you should run into a game that would not run smoothly unless the cpu are oc'ed then it would make sence to do so - but for now not.
The games available today either do run perfectly smooth at 1ghz or if they dont, then they dont because of poor programming or other factors and they would still run poorly even if the cpu are oc'ed
Actually there are real life benefits until you find a game which really lags when you run it. Meaning, you should leave it as it is until next year.
It may damage the CPU like what others say but since lower clocks are undervolt it might last as long as a non OC (Stock).
But it will kill the battery faster as you will have to charge more often due to the higher power draws.
hi folks, thinking about leaving oc on permenantly (1200 mhz) I an aware of the dangers, but thought about getting some facts, my question is, how long have people been running art 1200 mhz without any issues, how many weeks or months?
Sent using TCP/IP
1200mhz refers to the highest clock. Your phone doesn't stick to that frequency all the time. It generally scales from 100mhz to 1200mhz. It doesn't really matter if you overclock your device except for effects on battery and I don't think there would be any effect on the Hardware as much as that of an Overclocked computer cpu and considering the average number of months people tend to use their mobile device before getting a new and a better phone.
dhiru1602 said:
1200mhz refers to the highest clock. Your phone doesn't stick to that frequency all the time. It generally scales from 100mhz to 1200mhz. It doesn't really matter if you overclock your device except for effects on battery and I don't think there would be any effect on the Hardware as much as that of an Overclocked computer cpu and considering the average number of months people tend to use their mobile device before getting a new and a better phone.
Click to expand...
Click to collapse
my phone spends approx 20% of its time at Max freq, thats 1/5 th of its time. I think there would be more potential damage than a computer cpu as these have much better cooling (fans), I just want to know how long people have run at say 1200 without any issues.
Sent using TCP/IP
Longest time: two weeks ... whitout problems ...
I'm been overclocking my SGS for over 6 months now, no issues at all.
"Standard" voltage values seems to work fine on my device (1350mV at 1200MHz, 1400mV at 1300MHz) but I've tried to undervolt a bit more than once and had no issues as well.
Bye
There are absolutely no dangers in OC/UV. The worst thing to happen is a freeze or reboot once in a while if u go too high. I've been having 1.5mhz w/ some UV for like 2 months and nothing happened so no worries.
Been doing that for about a month now. No problem.
Knowledge is Power. Guard it well.
there are no risks if you overclock your device,but of course depends on how you do it. first of all i would not go past 1300mV which is the physical limit of our beloved hummingbird..of course you can do that,but past 1300mV you are going to shorten the life of your CPU. if you change phone every year then,there's no problem
then if you want to overclock keeping safe voltage values just get Tegrak Overclock,don't activate the "CPU MAX frequency" option,go in optimization tab instead and push up the max frequency by little steps keeping the voltage at the default value of 1275. test it a bit till you reach the most stable one. for example my CPU it's totally rocksolid 'till 1132MHz at 1275mV,no more. but there are CPUs which can archieve better results. then if you want to optimize and save battery consumption you can play a bit with UV on the other frequencies,cheers