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
mandeep294 said:
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
Click to expand...
Click to collapse
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*
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.
scoobysnacks said:
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.
Click to expand...
Click to collapse
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.
Splux said:
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.
Click to expand...
Click to collapse
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.
How about hot countries like Egypt ??? And pocket kept phones.
Would that fry the cpu ??? If overclocked I mean
josephedward said:
How about hot countries like Egypt ??? And pocket kept phones.
Would that fry the cpu ??? If overclocked I mean
Click to expand...
Click to collapse
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.
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
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.
inSaN1Ty_X said:
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 :/
Click to expand...
Click to collapse
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.
kaijura said:
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.
Click to expand...
Click to collapse
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.
inSaN1Ty_X said:
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.
Click to expand...
Click to collapse
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.
kaijura said:
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.
Click to expand...
Click to collapse
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
inSaN1Ty_X said:
I see. Well for starters, could you provide something like guidence where to find IceColdSandwitch's acpu table? I Would be really really happy.
Click to expand...
Click to collapse
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:
Code:
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.
kaijura said:
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
Click to expand...
Click to collapse
[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
Very cool i liked omg
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.
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.
Finally after someone pm'd me I looked back into GPU Overclocking.
New thread created issues with old thread OP permissions (people seem to be asking the same questions over and over again all information will be kept in OP & DO READ THE THREAD, repetitive questions will now be ignored)
Benefits:
Smoother UI
Handle 2d & 3d core GPU intensive applications & games
Currently only 2D core has been overclocked working on 3D core OC
2D-core original value - 192mhz OC to 245mhz DONE achieved 25% performance boost grp_2d_clk outputs 245760000hz
3D-core original value - 245mhz OC to 300+mhz WIP hoping to achieve 40-50% performance boost
2D-core OC only Download: Coming soon...
Download Links for other devices coming soon...
Works for all HTC Sense/Cm9/Cm10 kernels (Just ask a kernel developer for your device to implement the source code)
Note: Don't have internet on PC so providing 3 main files that need replaced for 2D-core OC to work
Download link to source code: http://d-h.st/wbH
3D-CORE OC TESTS Download: Coming soon...
Do check under sys/kernel/debug/htc_clock/clks/ look for file with all clocks & look for GRP_clks (Graphics clock)
OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.
So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.
(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)
(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)
Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.
Main thread is in Desire HD Android Development section: http://forum.xda-developers.com/show....php?t=2368497
Sound really great, do you have the commits on github? More easy to follow , will test it for Runnymede. Great job
Sent from my Find 5 using XDA Premium HD app
anders3408 said:
Sound really great, do you have the commits on github? More easy to follow , will test it for Runnymede. Great job
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
I have github but dont reqlly use it much, only have net on laptop so cannot push commits
Shaky156 said:
I have github but dont reqlly use it much, only have net on laptop so cannot push commits
Click to expand...
Click to collapse
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app
anders3408 said:
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
Benchmark are not really something that should be taken too seriously but yes antutu reported in 20-25% increase in performance not always accurate but 2d core clk results in 245mhz, user from desire hd reported going from in range of 2x fps to 4x fps and that is without the 3d-core overclock (2d-core is used in 3d graphics afaik)
anders3408 said:
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
diff patch to make life easier
diff --git a/arch/arm/mach-msm/clock-7x30.c b/arch/arm/mach-msm/clock-7x30.c
index 8e97664..5e9bc2e 100644
--- a/arch/arm/mach-msm/clock-7x30.c
+++ b/arch/arm/mach-msm/clock-7x30.c
@@ -2992,8 +2992,8 @@ static void __init msm7x30_clock_init(void)
clk_set_rate(&mdc_clk.c, 1);
/* Sync the LPA_CODEC clock to MI2S_CODEC_RX */
clk_set_rate(&lpa_codec_clk.c, 1);
- /* Sync the GRP2D clock to AXI */
- clk_set_rate(&grp_2d_clk.c, 1);
+ /* Set rate of 2D-core GPU Clock @245Mhz (OC of 53Mhz 25% perf boost by Shaky156) */
+ clk_set_rate(&grp_2d_clk.c, 245760000);
}
struct clock_init_data msm7x30_clock_init_data __initdata = {
diff --git a/arch/arm/mach-msm/devices-msm7x30.c b/arch/arm/mach-msm/devices-msm7x30.c
index d52db55..f428e57 100644
--- a/arch/arm/mach-msm/devices-msm7x30.c
+++ b/arch/arm/mach-msm/devices-msm7x30.c
@@ -1319,11 +1319,7 @@ struct resource kgsl_3d0_resources[] = {
static struct kgsl_device_platform_data kgsl_3d0_pdata = {
.pwrlevel = {
{
- .gpu_freq = 364800000,
- .bus_freq = 249600000,
- },
- {
- .gpu_freq = 245760000,
+ .gpu_freq = 245760000, /*Restore correct GPU frequency and bus frequency (Shaky156)*/
.bus_freq = 192000000,
},
{
@@ -1336,7 +1332,7 @@ static struct kgsl_device_platform_data kgsl_3d0_pdata = {
},
},
.init_level = 0,
- .num_levels = 4,
+ .num_levels = 3,
.set_grp_async = set_grp3d_async,
.idle_timeout = HZ/20,
.nap_allowed = true,
@@ -1372,14 +1368,13 @@ static struct resource kgsl_2d0_resources[] = {
static struct kgsl_device_platform_data kgsl_2d0_pdata = {
.pwrlevel = {
{
- .gpu_freq = 0,
+ .gpu_freq = 245760000, //Set 2D-core GPU Frequency @245mhz (Shaky156)
.bus_freq = 192000000,
},
},
.init_level = 0,
.num_levels = 1,
- /* HW workaround, run Z180 SYNC @ 192 MHZ */
- .set_grp_async = NULL,
+ .set_grp_async = set_grp2d_async, //Set the 2D-core Graphics Clock Asynchronous to the AXI clock (Shaky156)
.idle_timeout = HZ/10,
.nap_allowed = true,
.clk_map = KGSL_CLK_CORE | KGSL_CLK_IFACE,
diff --git a/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c b/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
index e81b025..b8686c0 100644
--- a/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
+++ b/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
@@ -488,10 +488,8 @@ int kgsl_pwrctrl_init(struct kgsl_device *device)
pwr->pwrlevels.io_fraction =
pdata->pwrlevel.io_fraction;
}
- /* Do not set_rate for targets in sync with AXI */
- if (pwr->pwrlevels[0].gpu_freq > 0)
- clk_set_rate(pwr->grp_clks[0], pwr->
- pwrlevels[pwr->num_pwrlevels - 1].gpu_freq);
+
+ /*Removed AXI Sync code (Shaky156)*/
pwr->gpu_reg = regulator_get(NULL, pwr->regulator_name);
if (IS_ERR(pwr->gpu_reg))
For now its an empty oc, meaning it doesn't work
Sent from my Find 5 using XDA Premium HD app
anders3408 said:
For now its an empty oc, meaning it doesn't work
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
I was in IRC before you came on, talked to synergy, I've changed the OC code, removed mistake and set GPU OC a different way, guess what? tested on my sisters phone again and benchmark was improved, not majorly but on 2 of the draw tests, consistant results of improvement by 5-8fps and rest were by 1-2fps, but like I said lets see where 3d-gpu OC takes me, as that will definitely show if OC is working
What you guys got and what I got was different in benchmarks, which is weird, I got imrovements, you got the opposite. So can't call it an empty OC lol
Shaky156 said:
I was in IRC before you came on, talked to synergy, I've changed the OC code, removed mistake and set GPU OC a different way, guess what? tested on my sisters phone again and benchmark was improved, not majorly but on 2 of the draw tests, consistant results of improvement by 5-8fps and rest were by 1-2fps, but like I said lets see where 3d-gpu OC takes me, as that will definitely show if OC is working
What you guys got and what I got was different in benchmarks, which is weird, I got imrovements, you got the opposite. So can't call it an empty OC lol
Click to expand...
Click to collapse
your improvements here : 0xbench is very small, and should be higher if it is oc'ed , but yes its a plausble
Okay after looking @ GPU Overclock for 2 weeks, This is the news on GPU OC for MSM8x55/MSM7x30 socs.
My findings...
2D-core OC from 192mhz to 245mhz successful.
3D-core OC will not happen without me obtaining the datasheet (which is proprietary)
The clocks are protected, via Ownership/Permissions, and maybe an RCU/MPU
No Overclocking the CPU does NOT Overclock the GPU, thats the worst thing I've heard in my life lol.
The lowest the GPU can hit is 192mhz or lpxo freq
Bus is not overclockable, it always is 192mhz
EBI_2D_clk will and has always been 0mhz
Modifying kgsl platform data and/or the graphics table with random values or even calculated values from correct pll freqs will NOT OC the gpu
it's ashame the GPU clocks are protected.
IF anyone is looking to continuing this project and is on the right track you're more than welcome to get in contact with me, especially if you have the msm7x30 datasheet.
The QSD8x50 soc is more open than this soc, so I'm doing a few tests on the HD2
Also it is overclocked, wasted my time testing, measured the gpu frequency and output to dmesg tells me it is correct, if it wasnt setting then the dmesg would ouput it failing to set the gpu frequency. just like it does for 3d-core oc
it was said before and ill say it again, the gpu clock is relative to the cpu clock, you cant overclock the gpu, their all part of the soc "system on chip", you can increase the bus bandwidth etc, which is already present in my kernel, but performance increase? not any atall
onejay09 said:
it was said before and ill say it again, the gpu clock is relative to the cpu clock, you cant overclock the gpu, their all part of the soc "system on chip", you can increase the bus bandwidth etc, which is already present in my kernel, but performance increase? not any atall
Click to expand...
Click to collapse
GPU clocks on msm7x30 devices is hardcoded.
Sent from my Find 5 using XDA Premium HD app
Hi plz anyone help me my battery work just 5 and 7 hour I have cm10 plz help me how can I install this and how can I got more battery plz hellp
Sent from my Sensation XL using xda premium