Overclocking pros and cons???

[mandeep294]

I want to know wat r d pros and cons of overclocking..
As far as i know pros are better performance..
Con: reduced battery life..
Plzz add ur suggestions in d list..
And does overclocking processor reduce d lifespan of device?

Sent from my HTC Incredible S using XDA App

 

[Splux]

I want to know wat r d pros and cons of overclocking..
As far as i know pros are better performance..
Con: reduced battery life..
Plzz add ur suggestions in d list..
And does overclocking processor reduce d lifespan of device?

Sent from my HTC Incredible S using XDA App

Overclocking will reduce the lifetime of the CPU, but honestly I don't think that you'll really notice it.

If you lower the voltage you'll also get the same or even better battery time even though you overclock it.

If you overclock too much your phone will most likely start to freeze or just shut down.

Can't really think of any major things that might happen.

And pros; games will run more smoothly, you can have more applications running in the background without lag because of the CPU. If you're running out of RAM an overclocked CPU won't help you.

That's all I can think of right now, and hopefully I haven't mixed up anything

*edit*
http://www.tested.com/news/the-risks-and-rewards-of-overclocking-android-phones/444/

Maybe you should read that
*hopes that it doesn't say the exact opposit of what I just wrote here*

 

[scoobysnacks]

If you're undervolting, the processor shouldn't overheat therefore less battery loss and less chance of any damage.

You can overclock our phone processor ~300mhz without seeing any overheating or bad battery drain. I just wouldn't recommend over that for very long periods.

 

[Splux]

If you're undervolting, the processor shouldn't overheat therefore less battery loss and less chance of any damage.

You can overclock our phone processor ~300mhz without seeing any overheating or bad battery drain. I just wouldn't recommend over that for very long periods.

But, there might actually be some phones that will start freezing just by overclocking 300MHz too

Forgot to mention, in my previous post, that how far you can go with overclocking is really device specific, it can differ a lot from two different Incredible S. I remember from the community for my old phone that some people couldn't even overclock 100MHz. CPU's for phones aren't really made to be overclocked, so do it with caution.

And to find out how much you can overclock your CPU, in your phone, just take it easy and go like 50MHz/time and perform some sort of a stresstest of the CPU, when it start to freeze and/or turn off you've gone beyond the limit of what your CPU can take. And don't set the frequency to as close to the limit you can, set it like _MAX_ 50MHz from the limit, I'd go for at least 100MHz below the limit.

Hopefully someone appreciates this post, and if anyone want to point out something I've gotten wrong... please do.

 

[scoobysnacks]

But, there might actually be some phones that will start freezing just by overclocking 300MHz too

Forgot to mention, in my previous post, that how far you can go with overclocking is really device specific, it can differ a lot from two different Incredible S. I remember from the community for my old phone that some people couldn't even overclock 100MHz. CPU's for phones aren't really made to be overclocked, so do it with caution.

And to find out how much you can overclock your CPU, in your phone, just take it easy and go like 50MHz/time and perform some sort of a stresstest of the CPU, when it start to freeze and/or turn off you've gone beyond the limit of what your CPU can take. And don't set the frequency to as close to the limit you can, set it like _MAX_ 50MHz from the limit, I'd go for at least 100MHz below the limit.

Hopefully someone appreciates this post, and if anyone want to point out something I've gotten wrong... please do.

I'm going by this chips specific tolerance, fyi I'm an electronics engineer.

I strongly doubt anyone's phone would not be able to overclock at all.

You just have to watch the heat really. Overall, 200 to 300MHz is very safe.

This generation snapdragon has high tolerances.

I have gotten mine up to 2ghz.

Freezing generally won't occur until after about 1.6ghz, or if the undervolting is too severe.

---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------

Any chip can overclock, it is certain undervolt levels that cause most to freeze.

 

[josephedward]

How about hot countries like Egypt ??? And pocket kept phones.
Would that fry the cpu ??? If overclocked I mean

 

[Nonverbose]

How about hot countries like Egypt ??? And pocket kept phones.
Would that fry the cpu ??? If overclocked I mean

There is thermal overload protection built, the phone resets when the CPU reaches the temperature threshold. So a moderate overclock should create no problems. If the phone is rebooting though you should think about scaling back.

 

[inSaN1Ty_X]

Sorry for bumbing old thread

Biggest issue I've came across with overclocking are the voltages. Took me half a year to adjust CPU voltages even till this point where I can overclock 100mhz. Since not all devs share their acpu table, its impossible to know how severe the undervolting is in particular ROM.
Every CPU is different, and mine needed 100mV(?) higher voltages than the ARHD native voltages to even stay at 1152mhz without insta freeze :/

Sent from my HTC Incredible S using XDA

 

[kaijura]

CPU overclocking does have pros and cons, and I think the cons tends to outweight the pro's but it all depends on the type of user each person is. The only pros means you save a few seconds doing something, or get a better benchmark score - for what reason? I will explain below.

Overclocking can give you that 0-40% more boost. This can show from our stock IncS @ 1.0GHz = 3000 antutu score, overclocked becomes 3600 or 4000. That is a benchmark score, it's just numbers and don't mean real world performance.

How about when you are gaming? This doesn't translate immediately that you will get like 50+% more speed, it's more like in a shooter game your FPS jumps from from 18FPS > ~22 FPS, with a 30% overclock. it's just a measly 3-5 FPS. Often times, this also comes with instability causing freezes, reboots, or a hot phone, and extreme battery drain.

Whether you can tell the difference or need that extra power is up to you and each person, but personally I find that it's a gamble to take that has little gains other than telling others "hey I got this benchmark score"! Good for them.

Now, underclocking is a different story. While in theory it shouldn't cause any problems to the CPU, the purpose is 99% of the time to prolong the battery. This is what voltage controls in kernels are all about.

Sorry for bumbing old thread
Biggest issue I've came across with overclocking are the voltages. Took me half a year to adjust CPU voltages even till this point where I can overclock 100mhz. Since not all devs share their acpu table, its impossible to know how severe the undervolting is in particular ROM.
Every CPU is different, and mine needed 100mV(?) higher voltages than the ARHD native voltages to even stay at 1152mhz without insta freeze :/

The GPL requires whatever kernel that is distributed becomes open source. If you find a developer that doesn't share with you the kernel source they are using, you can complain about it. They are violating the policy that makes android/linux, the OS it is. Most developers tend to take someone else's kernel and bundle it in their rom, but the original creators of the kernel should usually have a source up.

 

[inSaN1Ty_X]

The GPL requires whatever kernel that is distributed becomes open source. If you find a developer that doesn't share with you the kernel source they are using, you can complain about it. They are violating the policy that makes android/linux, the OS it is. Most developers tend to take someone else's kernel and bundle it in their rom, but the original creators of the kernel should usually have a source up.

Meaning: DEVs usually just share a link to github. It's pretty frustrating for "newb" user to even find the kernel source code from there. Seen one ROM where MDJ actually posted the acpu table and it was easy to see the voltages and adjust them to be alike with another ROM/(Kernel) that had trouble with O/C.

As for the Overcloking generally, I only find I usefull if kernel supports governor like smoothass, which really boosts the smoothness and I can truly see the difference.

 

[kaijura]

Meaning: DEVs usually just share a link to github. It's pretty frustrating for "newb" user to even find the kernel source code from there. Seen one ROM where MDJ actually posted the acpu table and it was easy to see the voltages and adjust them to be alike with another ROM/(Kernel) that had trouble with O/C.

well, just ask them where it is then. I'm sure most would tell you to look at that acpuclock source unless they were just not cool with you for some reason.

 

[inSaN1Ty_X]

well, just ask them where it is then. I'm sure most would tell you to look at that acpuclock source unless they were just not cool with you for some reason.

I see. Well for starters, could you provide something like guidence where to find IceColdSandwitch's acpu table? I Would be really really happy.

Sent from my HTC Incredible S using XDA

 

[kaijura]

I see. Well for starters, could you provide something like guidence where to find IceColdSandwitch's acpu table? I Would be really really happy.

You know you can also find a kernels' cpu VDD table using any app that lets you look at SVS values right?? It automatically pulls it for you.

This would probably be better asked in the IceColdSandwich thread as this topic is irrelevant to it since it means to cover all kernels, but here you go anyway:

static struct clkctl_acpu_speed acpu_freq_tbl[] = {
	{ 24576,  SRC_LPXO, 0, 0,  30720,  900, VDD_RAW(900) },
	{ 61440,  PLL_3,    5, 11, 61440,  900, VDD_RAW(900) },
	{ 122880, PLL_3,    5, 5,  61440,  900, VDD_RAW(900) },
	{ 184320, PLL_3,    5, 4,  61440,  900, VDD_RAW(900) },
      { MAX_AXI_KHZ, SRC_AXI, 1, 0, 61440000, 900, VDD_RAW(900) },
	{ 192000, PLL_3,    5, 2,  122500, 900, VDD_RAW(900) },
	{ 268800, PLL_3,    5, 1,  192000, 900, VDD_RAW(900) },
	{ 345600, PLL_3,    5, 1,  192000, 925, VDD_RAW(925) },
	{ 422400, PLL_1,    2, 0,  192000, 950, VDD_RAW(950) },
	{ 499200, PLL_3,    5, 1,  192000, 950, VDD_RAW(950) },
	{ 576000, PLL_3,    5, 1,  192000, 975, VDD_RAW(975) },
	{ 652800, PLL_2,    3, 0,  192000, 1000, VDD_RAW(1000) },
	{ 729600, PLL_2,    3, 0,  192000, 1050, VDD_RAW(1050) },
	{ 806400, PLL_2,    3, 0,  192000, 1050, VDD_RAW(1050) },
	{ 883200, PLL_2,    3, 0,  192000, 1100, VDD_RAW(1100) },
	{ 960000, PLL_2,    3, 0,  192000, 1100, VDD_RAW(1100) },
	{ 1036800, PLL_2,   3, 0,  192000, 1150, VDD_RAW(1150) },
	{ 1113600, PLL_2,   3, 0,  192000, 1200, VDD_RAW(1200) },
	{ 1190400, PLL_2,   3, 0,  192000, 1200, VDD_RAW(1200) },
	{ 1267200, PLL_2,   3, 0,  192000, 1225, VDD_RAW(1225) },
	{ 1344000, PLL_2,   3, 0,  192000, 1225, VDD_RAW(1225) },
	{ 1420800, PLL_2,   3, 0,  192000, 1250, VDD_RAW(1250) },
	{ 1497600, PLL_2,   3, 0,  192000, 1300, VDD_RAW(1300) },
	{ 1574400, PLL_2,   3, 0,  192000, 1350, VDD_RAW(1350) },
	{ 1612800, PLL_2,   3, 0,  192000, 1400, VDD_RAW(1400) },
	{ 1728000, PLL_2,   3, 0,  192000, 1425, VDD_RAW(1425) },
	{ 1804800, PLL_2,   3, 0,  192000, 1450, VDD_RAW(1450) },
	{ 1881600, PLL_2,   3, 0,  192000, 1450, VDD_RAW(1450) },
	{ 1958400, PLL_2,   3, 0,  192000, 1500, VDD_RAW(1500) },
	{ 2035200, PLL_2,   3, 0,  192000, 1500, VDD_RAW(1500) },

If you need the direct source, it is available on my github: here

Edit: OP: this post is not meant to derail your thread, I'll hope you are okay with it.

 

[inSaN1Ty_X]

You know you can also find a kernels' cpu VDD table using any app that lets you look at SVS values right?? It automatically pulls it for you.

This would probably be better asked in the IceColdSandwich thread as this topic is irrelevant to it since it means to cover all kernels, but here you go anyway:


If you need the direct source, it is available on my github: here

[Hopefully it's okey to modify quotes like this on XDA..]

Thank you so so so much ! Yes I know that apps like incredicontrol can show it, but don't want to flash all the possible ROMs and their versions just to find out that when it could be available this easy. Also I can compare values more easily this way, rather than from the screen of my INC S.

But still thanks again! Oh and yea draftted slighlty from OP's question, hope he doesn't mind

 

[nuttaphats]

Very cool i liked omg

 

[TechNoobForSale]

Overclocking a phone's CPU is really an hit or miss. In Benchmarks you'll most likely won't see any improvement. On the other hand, GPU overclock seems to be much MUCH more worth It. It brings real benchmarks and gaming improvements.

 

[lolvatveo]

i'm an experienced overclocker and i'd say that the cpu won't reduce life if the temperature and voltage aren't too high: less than 60°c under 1.6 volts for silicon (combined of both) and CPU is not afraid of continuous work in spite of high frequency (10GHz, 100GHz), as said it only shortens its life when the temperature and voltage are too high. silicon can withstand up to more than 2 volts but 1.6 on average. and unstable cpu overclock the main cause must be the temperature and the components around it like Ram, Motherboard, not the CPU itself. example an intel e6500 cpu has a base clock of 2.93 GHz is overclocked to over 9GHz with excellent temperatures and voltages and fully stable.