Related
Hey, back again on a question about overclock an HTC Thunderbolt rooted with CM7 and Tiamat kernel. Anyways, I can overclock it to 1.9ghz pretty stable and suprisingly good battery life ( believe it or not ), get's kind of hot when charging though about 107 farenheit and 99 on daily use w/o it being plugged in. I was trying to get it to reach 2.0ghz, I know some of you will say its not that big of a jump from 1.9 to 2.0 but that's not the point, I am using SetCPU and Incredicontrol, and I just can't seem to keep it stable because I set it 2.0ghz and put the SVS volt in Incredicontrol to the high which is 1550 If I remember correctly, It's pretty stable but as soon as I press the lock button it freezes up and I have to take battery in/out. Any suggestions ? Thanks.
I'm not the most brilliant when it comes to overclocking (Having similar problems), but you have to keep in mind that 2GHz is double your stock clock speed, so yes, that is a big push. My recommendation is to find a low-voltage kernel that has Smartass V2 and try again.
Hmm wel l i do have smartass v2 but using smartass v1 with 1.9ghz overclocked no problems yet maybe il just stay at 1.9 but then again ill keep trying 2ghz until i get bored lol
Watoy said:
Hmm wel l i do have smartass v2 but using smartass v1 with 1.9ghz overclocked no problems yet maybe il just stay at 1.9 but then again ill keep trying 2ghz until i get bored lol
Click to expand...
Click to collapse
...or cook your device. At the voltages you describe, I can all but promise you that you're slowly killing guy your phone. You're talking about a 5% gain in clock for a performance gain of less than 2%. Your phone probably isn't stable at all at 2ghz. Smartass ramps up to policy max at screen on, unless you change it, and it probably locks before the display even comes on. If you like your phone, stop. The return you get probably won't even do 1.9ghz, so count yourself lucky at that. Mine won't run that fast.
loonatik78 said:
...or cook your device. At the voltages you describe, I can all but promise you that you're slowly killing guy your phone. You're talking about a 5% gain in clock for a performance gain of less than 2%. Your phone probably isn't stable at all at 2ghz. Smartass ramps up to policy max at screen on, unless you change it, and it probably locks before the display even comes on. If you like your phone, stop. The return you get probably won't even do 1.9ghz, so count yourself lucky at that. Mine won't run that fast.
Click to expand...
Click to collapse
What is a safe voltage for 1.9ghz? I think right now it's at 1300-1450 I forgot, SVS(I don't know what the SVS is, just says on top of Incredicontrol). It's very stable and the phone doesn't even run hot, no random reboots or anything like that, but since you said the voltage thing I am worry now, can you explain some more? With my overclock right now which is as I said 1.9ghz, Am I still killing my phone? My battery life is pretty good except when watching videos, goes down very fast but other than that it's good. Btw what are good temps for my phone?
Watoy said:
What is a safe voltage for 1.9ghz? I think right now it's at 1300-1450 I forgot, SVS(I don't know what the SVS is, just says on top of Incredicontrol). It's very stable and the phone doesn't even run hot, no random reboots or anything like that, but since you said the voltage thing I am worry now, can you explain some more? With my overclock right now which is as I said 1.9ghz, Am I still killing my phone? My battery life is pretty good except when watching videos, goes down very fast but other than that it's good. Btw what are good temps for my phone?
Click to expand...
Click to collapse
That kind of voltage tends to stress the silicone. If 1450 is your top limit, that's not too bad, but I probably wouldn't venture past that. Your governor is keeping it from running at that speed most of the time. Most of the heat you feel the phone give off is the battery. You really don't feel much of the heat from the CPU. Too much voltage is going to cook your CPU well before it begins to show temperatures on the battery sensor. As far as temps go, pretty much anything under 135F is ok. The battery will be the first thing to fail as temperatures rise. The SoC can tolerate much more. SVS just stands for Static Voltage Scaling, as opposed to HAVS, Hybrid Adaptive Voltage Scaling, which I don't think any Tbolt kernels support.
I don't get the purpose of that level of overclocking. My phone is snappy smooth and basically SAFE at 1.15 or 1.2
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
RevosFTS said:
I don't get the purpose of that level of overclocking. My phone is snappy smooth and basically SAFE at 1.15 or 1.2
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
Click to expand...
Click to collapse
The core is designed to run at 1.5ghz (though the caches and memory arent fabbed to, really) so running at 1.5 or 1.6 isn't a big deal. More than that and you're really challenging it.
Has it ever been heard of that someone killed their gs2 from using 1600mhz in daily use?
My gs2 likes to have 1475 as a minimum voltage for 1600.
sent from I9100 using Omega
Ever rev an engine into the red? Did the engine blow up on the spot? unlikely. However if you constantly KEEP the engine in the red it will eventually break down.
Same thing for OC phones. The processor in the SGS was designed for somewhere around the 1ghz mark. Pushing it 110% likely wont kill it, they build allowances and tolerances into these things to help them last longer. Push that processor to 150% and you are risking serious damage.
Monitor the heat, if you notice its getting HOT then you should really pull the battery and let it sit for a while. Nobody here can say its safe to OC your phone like that, its a calculated risk you obviously didnt spend a lot of thought into.
TLDR: Just because you CAN doesn't mean you SHOULD.
Actually its my thought the reason I haven't been using it on 1.6 yet, and why I'm asking. Iv been ocing my pcs since the late 90s
Now the reason I'm asking here is because the cortex a9 was designed for up to 2gHz operation, but this phones design may or may not provide adequate cooling, that's why I'm asking if other people have any negative experiences with this.
Were not actually over reving the chip its more of a environment issue with cooling/ventilation.
sent from I9100 using Omega
Visentinel said:
Actually its my thought the reason I haven't been using it on 1.6 yet, and why I'm asking. Iv been ocing my pcs since the late 90s
Now the reason I'm asking here is because the cortex a9 was designed for up to 2gHz operation, but this phones design may or may not provide adequate cooling, that's why I'm asking if other people have any negative experiences with this.
Were not actually over reving the chip its more of a environment issue with cooling/ventilation.
sent from I9100 using Omega
Click to expand...
Click to collapse
You do have to have in mind that PCs are much safer to OC, so we shouldn't really compare brtween them.
Regarding the Phone OC, I haven't OC'd mine and probably never will because I have all the horsepower I need, but I think the "safest" OC is between 1.3 and 1.4GHz, since that's a range that all CPUs are designed to overtake (max 200MHz range ).
mine's been oc'ed, uv'ed pretty much within the week I bought the phone in june.
I've got it set to clock between 500-1600Mhz on demand and I've not had a problem yet. Mind you, not many tasks you do on the phone will actually require 1600Mhz and my phone's CPU clocks mostly between 500-800Mhz.
Playing some games or doing quick video conversion will push to 1600Mhz but I rarely play games on my phone and video conversion is short process - burst of 90 seconds to 120 seconds at most. So I think you should be alright so long as you don't leave your phone CPU at 1600Mhz at all times.
Like you said, it is the cooling and ventilation system on the phone, which you can't modify.. Unlike PCs, where you can install bigger fans or water cooling systems. So if the phone isn't constantly cooking itself inside, should be alright.
You should already know that OCing anything is dangerous since you overclock PCs,so I'll skip that part.
Well,if it's dangerous for the phone...It depends.Yes,the processor will die sooner.Yes,you risk frying your device.No,you don't have to push it to the limit(don't push it more that 1450μV,that's the general advice for 45nm chips).However,my thoughts are:
-I won't still have the device when it's time for its CPU to get fried,so I don't actually care.
-Something else,probably the Amoled screen,will make the phone useless by breaking sooner than the CPU will.
-This winter here is really cold(for our standards anyway),so heating has been taken care of.During hotter weather,I kept multiple temperature profiles in SetCPU,so that frequencies get lower as temperatures get higher.
In the end,what matters most to me is to have the experience I want.And with OCing my phone I get it.I'm happy with it,that's all I wanted.So,it's personal preference.Some feel they don't need it,others feel they do.Decide for yourself,that's the best advice.
PS:In case you are using Siyah kernel or CF-Root with Tegrak overclock,try lowering your clock by small steps(8Mhz is the smallest step) for a sane voltage,say 1400μV.Sometimes small increments make big differences.
Thanks for the advice guys. Appreciated.
sent from I9100 using Omega
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Buffalee said:
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Click to expand...
Click to collapse
how can you tell, that its dead because of the use and charging, if you didn't even OC'ed?
Buffalee said:
Don´t oc sgs2.
I got my mobo fried without oc.
Service center replaced everything else but housing and screen.
I used it 2-3 hours in a row, installed programs and put it in charger.
In the morning, it was completely dead.
Overheated because of the use and charging.
So think about twice before using oc 24/7.
Click to expand...
Click to collapse
I bet you didn't know there are faulty products out there that show their faults during intensive usage,eh?Mine's running at 1.6GHz(give or take a few MHz ) for months.I've played games while charging countless times.And my phone is still here,intact,so that I can write this here.
Sent from my GT-I9100 using xda premium
Of course my sgs mobo could have been faulty.
When the mobo fried it was hot, i mean hot.
I didn´t look temperatures.
It didn´t wake up even using jig.
I sended it to service.
If they had succesfully woke it up, they wouldn´t fix it on warranty (rooted).
Normally oc would be fine because it´s using powersave and underclock it.
But if you play like 2 hours on 1,6Ghz it can get too hot (over 60c on cpu).
I can´t recommend that kind of temperature.
And nobody here knows what kind of vrm´s phone has.
Also cooling plates are not designed for massive oc/voltage.
Of course temperature depends on voltage more than the clock speeds.
It´s up to user if he want to use it that kind of voltages/speeds.
I would´t use it 1600Mhz/24/7.
Generally i know what i´m talking about (using water on pc...)
Just look for temperatures and don´t give too much voltage (as low as possible).
Of course you don´t know safe voltage limits, but try and look what other have been using.
Don´t oc much if you don´t know what are you doing.
@tolis626 Hi, I have oc'd to 1.4ghz for the last few weeks, and I have under volted it to 12.75mV, the same as you, have you had any problems at that voltage? Also, is your 1200mhz voltage stable as it seems very low, to say that it was, at stock, 13mV. Furthermore, have you ever tried to under volt 1600mhz please?
Buffalee said:
Of course my sgs mobo could have been faulty.
When the mobo fried it was hot, i mean hot.
I didn´t look temperatures.
It didn´t wake up even using jig.
I sended it to service.
If they had succesfully woke it up, they wouldn´t fix it on warranty (rooted).
Normally oc would be fine because it´s using powersave and underclock it.
But if you play like 2 hours on 1,6Ghz it can get too hot (over 60c on cpu).
I can´t recommend that kind of temperature.
And nobody here knows what kind of vrm´s phone has.
Also cooling plates are not designed for massive oc/voltage.
Of course temperature depends on voltage more than the clock speeds.
It´s up to user if he want to use it that kind of voltages/speeds.
I would´t use it 1600Mhz/24/7.
Generally i know what i´m talking about (using water on pc...)
Just look for temperatures and don´t give too much voltage (as low as possible).
Of course you don´t know safe voltage limits, but try and look what other have been using.
Don´t oc much if you don´t know what are you doing.
Click to expand...
Click to collapse
I know what I'm doing.I know the risks,that's why I don't encourage anyone to overclock as much as I do.I carefully monitor temperatures and voltages over long time periods.Rest assured,I won't come back here crying.
danielsf said:
@tolis626 Hi, I have oc'd to 1.4ghz for the last few weeks, and I have under volted it to 12.75mV, the same as you, have you had any problems at that voltage? Also, is your 1200mhz voltage stable as it seems very low, to say that it was, at stock, 13mV. Furthermore, have you ever tried to under volt 1600mhz please?
Click to expand...
Click to collapse
Well,since 1400MHz and 1600MHz aren't stock clocks,you don't actually undervolt them.You rather choose a voltage for them as there isn't a standard one.
My phone is stable with the voltages in my sig(I've only changed 200Mhz and 500MHz voltages a little but too bored to update my sig ) for months,so yeah,I'd say I don't have any problems.This doesn't mean that no one will.Your phone might need 1325μV or 1225μV for 1400MHz.Every phone's CPU is unique in its own way.
@tolis626 Thanks very much, one more stupid question please, will under volting from stock Samsung voltages, even if it's stable, decrease performance compared to stock voltages on an average exynos processor please, aslo will undervolting from original kernel clock speed increase the processors life span? I have researching this and came up with nothing.
Will it break your phone? Not directly. It will shorten the lifetime.
Besides that the heat can indirectly kill your device.
I'm just curious:
Why overclocking the device? I have mine underclocked to 1 GHz max. It still has enough power to handle everything.
Sent from my GT-I9100 using XDA App
I have just been messing around. I can get 1.6ghz perfectly stable at 1350mv, I tried 1325mv and it hung up after about 2 min of use. I can also get my 1.4ghz down to 1225mv's and 1.2ghz to 1.200 it is rock stable and I haven't tried lower voltages on 1.4 & 1.2.
I am going to keep [email protected] & 1.4 @ 1250mv & [email protected]
danielsf said:
@tolis626 Thanks very much, one more stupid question please, will under volting from stock Samsung voltages, even if it's stable, decrease performance compared to stock voltages on an average exynos processor please, aslo will undervolting from original kernel clock speed increase the processors life span? I have researching this and came up with nothing.
Click to expand...
Click to collapse
No,undervolting will in fact prolong your processor's lifetime,albeit negligibly,because with less voltage less heat is generated.It's plain physics.
Overclocking on the other hand will reduce your CPU's lifetime.The damage(mostly electromigration) is dependent on the CPU and how much you overclock.Quite frankly again,you won't still have the phone when enough damage is done for it to break.If the slightly lower battery life doesn't bother you that much,I say go for it.
danielsf said:
I have just been messing around. I can get 1.6ghz perfectly stable at 1350mv, I tried 1325mv and it hung up after about 2 min of use. I can also get my 1.4ghz down to 1225mv's and 1.2ghz to 1.200 it is rock stable and I haven't tried lower voltages on 1.4 & 1.2.
I am going to keep [email protected] & 1.4 @ 1250mv & [email protected]
Click to expand...
Click to collapse
Dude,that's some nice UV!Mine instantly crashes when I set it to 1375μV at 1600MHz.You're lucky.
Oh and,most probably your phone can handle 1200MHz at 1150μV.
Sent from my GT-I9100 using xda premium
tolis626 said:
No,undervolting will in fact prolong your processor's lifetime,albeit negligibly,because with less voltage less heat is generated.It's plain physics.
Overclocking on the other hand will reduce your CPU's lifetime.The damage(mostly electromigration) is dependent on the CPU and how much you overclock.Quite frankly again,you won't still have the phone when enough damage is done for it to break.If the slightly lower battery life doesn't bother you that much,I say go for it.
Dude,that's some nice UV!Mine instantly crashes when I set it to 1375μV at 1600MHz.You're lucky.
Oh and,most probably your phone can handle 1200MHz at 1150μV.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you very much for all your help I tried undervolting 1200mhz more, I got to 1075mv and it was rock stable, I don't think I am going to try anything lower than that. Just for info, I'm on SiyahKernel v2.6.2 Thanks again
CPUs care a lot about voltage and don't give a rip about MHz except for the minor heat increase. The chip in my phone is a bad clocker though. If I could get 1400mhz to work at close to the stock 1200mhz voltage I would do it in a heartbeat. Sadly mine requires a healthy bump so I abstain. At least until I can afford to replace it
Number one rule of overclocking, don't push the voltage if you can't afford to replace it
I discussed the topic of overclocking processors with a friend of mine who design cellphone CPUs. He told me that over the lifetime of a CPU, the insulating oxide layers break down. This process is considerably faster at 40% extra power and frequency. So don't expect it to last as long as a normally clocked CPU. So the question is how long it would normally last.
Are there any reports from anyone out there that actually killed their phone/fried their cpu from overclocking. I would search...but it's not working
I don't know about the CPUs used in cellphones, but how many burned out CPUs would you like? (I know someone who uses them as parts of his grunge art, and he actually buys them from computer repair shops for about a buck a piece to make sure he has enough.) It's not as common these days, but back when the "art" was in its infancy people burned them out all the time. And when vendors stole the AMD fans and substituted cheaper ones - back in P2 days, IIRC - there were more burned out AMD chips than working ones. (Normal clock on an undercooled chip is the same as overclocking a properly cooled chip.)
So yes, it can probably burn out the CPU unless you keep the overclocking to a minimum, which won't buy you anything noticeable in performance. I laugh when I see people posting that they're overclocking a 3.2GHz CPU to 3.3GHz. If that saves them 2 seconds a year they're lucky.
Well never heard of anybody burning there smartphones CPU, but there are a few app like SetCPU, where u can set profiles for when the temp of ur processor is to high to downclock it.
Also i have heard of people overclocking there phones to twice there normal power and never had any issues.
Theres no need to literally burn the cpu, but you can easily shorten the life of the phone
If you have control of the voltage, and can take it beyond the CPU's limits, it should be quite easy to burn out your CPU.
With that said though, most apps and kernels have safe limits in-place on the voltage and clocks you can set. For example, I can't pass 1.4Ghz with 1500mv (if that's the right term) on my Galaxy Tab. With that voltage anyway, anything above 1.4Ghz is unstable
espionage724 said:
If you have control of the voltage, and can take it beyond the CPU's limits, it should be quite easy to burn out your CPU.
With that said though, most apps and kernels have safe limits in-place on the voltage and clocks you can set. For example, I can't pass 1.4Ghz with 1500mv (if that's the right term) on my Galaxy Tab. With that voltage anyway, anything above 1.4Ghz is unstable
Click to expand...
Click to collapse
Very true. I know we are on the subject of phones, but most of today's computer motherboards have that 'safety' feature where if you overclock or the processor gets too hot, then it will shut down the computer. I am sure phones have the same similar feature.
I have my SGP5 overclocked to 1.5ghz at the moment via Tegrak. Everything is running smoothly but the spot on the back where the CPU is gets warm to the touch. Not hot or anything, but obviously warm.
Before I had it overclocked to 1.45ghz and it stayed a lot cooler, but to get to 1.5 I had to bump the core voltage to 1.35v. I also have the up-threshold set to 35% so it spends a good amount of time at max speed.
Since these things don't have CPU temp monitoring, how do you tell when it's too hot? My battery temp never goes much over 80*F, so that doesn't seem like a good indicator of anything.
Sitting here playing music with Mufin my IR temp gun reads a max of 100*F on the back of the case over the CPU. Battery temp is reading 77*. Is that too warm? How much of a temp differential can there be between the outside of the case and the CPU itself?
I'm no noob to overclocking PCs, but this is my first Android device so I don't really know it's limits as clearly.
Any help would be mucho appreciated!
DISCLAIMER - anything within this thread has the potential to do permanent damage.. I haven't had any issues yet but will not be held responsible for any damage!
So I just pulled the back cover off it. Running the same program for 10-15mins the CPU never exceeded 82.5*F which is well within safe limits imo.
I guess that goes to show how poor the cooling is in one of these things with the back cover on. I'm going to keep running 1.5ghz and report any issues. The difference in smoothness between 1.4 and 1.5ghz is pretty dramatic.. web browsing is very very smooth now. I probably won't be going any higher than 1.5, but for now it seems safe.
Tegrak Ultimate Profile -
Level0
1500mhz
1.350mV core
1.155mV internal
Level 2-4 untouched
Level 5 (undervolted for better battery life)
100mhz
850mV core
900mV internal
Using ondemand governor
35% up-threshold
exodus454 said:
So I just pulled the back cover off it. Running the same program for 10-15mins the CPU never exceeded 82.5*F which is well within safe limits imo.
I guess that goes to show how poor the cooling is in one of these things with the back cover on. I'm going to keep running 1.5ghz and report any issues. The difference in smoothness between 1.4 and 1.5ghz is pretty dramatic.. web browsing is very very smooth now. I probably won't be going any higher than 1.5, but for now it seems safe.
Tegrak Ultimate Profile -
Level0
1500mhz
1.350mV core
1.155mV internal
Level 2-4 untouched
Level 5 (undervolted for better battery life)
100mhz
850mV core
900mV internal
Using ondemand governor
35% up-threshold
Click to expand...
Click to collapse
Just tried your profile, and I have to say it works fantastic! The web browsing really is super fast.
Is there any major danger at this clock speed with On-Demand on? I mean, it'll only use 1.5GHz if it needs it right?
ZaIINN said:
Just tried your profile, and I have to say it works fantastic! The web browsing really is super fast.
Is there any major danger at this clock speed with On-Demand on? I mean, it'll only use 1.5GHz if it needs it right?
Click to expand...
Click to collapse
Ondemand from my understanding, scales processor speed using the values in the up/down (I believe System Tuner refers to down as "powersave bias") threshold. From my experience it's the best governor to use as far as customizing it easily and getting it to respond well.
Whatever you set the up-threshold to, when CPU load exceeds that value it bumps the speed up to the next "level" and ending in full speed. Then when CPU load falls below the down-threshold, it scales it back down to the next lowest level, so on and so-forth. You can also adjust the sampling rate too - lower frequency means it checks the CPU load more frequently and essentially makes the governor more responsive.
When I set mine to 35%, almost any program aside from stuff sitting almost completely idle will trip the CPU to hit 1.5ghz. This makes everything real responsive and may use more battery.. but I prefer having a more responsive device. You can also adjust the up-threshold to a higher number to try to lower temps and extend battery life. You can really play around with it to suit your needs, there's not really anything to screw up there.
There shouldn't be any danger using it with the ondemand.. but since I haven't tested this for more than a few days right now just keep an eye on temps (especially while playing games) and watch out for any "stuttering" out of the blue. Mine gets warm but nothing excessive. You'll be able to feel it on the back between the speakers.
I have to say though, even running such a high clock speed I'm not really seeing any negative effect on battery life so far.
Lemme know how yours goes!
How can it not have any risks? When the heat is too much somethig will explode wouldn't it?
No just kidding, but seriously. There is a risk of overheating a hardware and 'destroying' it, there should be!
Sent from my GT-I9000 using XDA
Well of course there's always some risk in overclocking! Especially when you don't know what you're doing.
As far as using one governor or another though.. when it comes down to it there shouldn't be a huge difference.
Sent from my YP-G70 using Tapatalk
I use SetCPU for root, but i don't see an option for more than 1200 mhz. How can I get it to 1500?
Rapydax said:
I use SetCPU for root, but i don't see an option for more than 1200 mhz. How can I get it to 1500?
Click to expand...
Click to collapse
Tegrak Overclock Ultimate
Sent from my YP-G70 using Tapatalk
exodus454 said:
Tegrak Overclock Ultimate
Sent from my YP-G70 using Tapatalk
Click to expand...
Click to collapse
you bought it?
i really want tegrak OC can you send me it in pm?
kfirbep said:
you bought it?
i really want tegrak OC can you send me it in pm?
Click to expand...
Click to collapse
Dude.
READ THE RULES!
XDA does not allow pirating apps or software to be discussed on the forums.
6. Do not post warez.
If a piece of software requires you to pay to use it, either pay or find your cracks and serials somewhere else. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained.
9. Don't get us in trouble.
Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
If you want an app, why don't you just support the developer and buy it??
First off is this a good idea? can such small devices be over clocked in a safe way without risking damaging the hardware?
if yes which would you say was the best app for doing so?
Hi,
A good idea... maybe, maybe not... it depends on what you want... higher scores in bench?A shorter battery life?A very very hot device while browsing or gaming (if you run at 1.8Ghz for example)?A little extra power for some apps/games?
With overclocking a little (1.5/1.6Ghz) I noticied that some apps open a little faster and the genera UI is a little more responsive...
There is always a (little) risk to overclock our phones, generally due to overheat but also some CPU's can't handle high overclock.
For me I don't remember reading someone burn her CPU with overclocking but...
There are still some software protections before to burn a CPU (thermal throttling, CPU temp limit before shutdown, etc...).
Obiously the duration of life could be reduced mainly if you always run at 1.8Ghz with playing games... So the "safe" way would be no overclock or a little overclock like 1.5Ghz... For you to test and decide...
For the apps: SetCpu, System Tuner... there is a bunch on the Play Store.Just for the CPU settings I would say SetCpu.
For me i will never overclock my cpu. Just install siyah kernel and it's pretty smooth in games. Overclocking will damage your cpu and maybe loose some of the performance.
I can't see the need on this device, I might experiment with uv, maybe even underclocking, but as above, super smooth on siyah, and Slim Rom
Sent from my GT-I9300 using xda premium
Talking about battery life i installed darkys rom 3 onto my i9300 and the battery life is already suffering a loss of maybe around 25%. In saying that over clocking will only cause me to lose even more so ill leave it for now
Sent from my GT-I9300 using xda app-developers app
I'm too running on slim ics and siyah kernel. Best battery life and performance!
GGSunny12 said:
For me i will never overclock my cpu. Just install siyah kernel and it's pretty smooth in games. Overclocking will damage your cpu and maybe loose some of the performance.
Click to expand...
Click to collapse
Overclocking won't damage your CPU unless you set crazy voltages, or let it overheat. Also, it won't lose performance... that's crazy talk. Only if it overheats will it throttle, but that only happens on large clock rates like 1.8GHz or if you're in a hot environment.
I had my old LG GT540 overclocked with no heat problems mind that was only a 600mhz cpu, had it up to 825mhz.
But we already have a powerful cpu in this phone, foe now I don't see the need to overclock.
Sent from my GT-I9300 using xda premium
The best app depends a lot on your kernel and device. For example, for my Galaxy S2 the best OC was with TegraK Overclock.
With my Xoom CPU Tuner is still the best.
With the S3 I suppose CPU tuner would be alright as well, but I haven't had the urge to OC it, because I find SiyahKernel still quite unstable in the S3.
You need an overclockable kernel in order to OC your phone.
As for damages, it is hard to tell if they are permanent, but picture this: your battery will have to be recharged more often, because it will drain faster. Since batteries have a limited lifespan which depends on how many charge cycles they go through, the more often you discharge/charge them, the shorter their lifespan will be.
Also, there is no telling what kind of ill-effects the added heat can do to the phone. It may be totally harmless, but it may also affect the quality of the display, since the added heat will be right underneath the screen.
The lifespan of the CPU will be shortened: instead of being able to work well for 20 years, it will work well for 18, 17, 15, but more than enough time for us to already have replaced our S3 for organic, intradermal smartphones!