I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
k-semler said:
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
Click to expand...
Click to collapse
uhh well.... yea and no. there are a few things you need to understand about microprocessors. no two are alike. they are built on a scale of a few nanometers and any difference causes a significant difference. to keep production numbers up there is a line they have to draw between performance potential and stability. more chips will be stable at lower clocks so they pick an speed they can get a high production number out of. sometimes a whole line of chips is produced with exactly the same core. chips that pass the highest get boxed as the highest performing and priced. chips that dont pass will either have specific features turned off, cores turned off or be underclocked and sold as lower models. in addition to that the top performing models are actually over priced, and often many more pass the tests than they need so perfectly good processors are intentionally disabled to fill the market for lower speed processors, so yes the cpu may be "underclocked" in a sense. but i don't know if that really applies to the infuse because i don't know if there are any chips in the same family that have a higher rated clock speed, if there are they aren't used in phones.
in example, on my pc i have a 3 core processor, it's actually a 4 core and i can even turn the 4th core on in bios, but a certain percentage of that particular model of chip will be unstable with the 4th core active.
another thing to understand is how the clock speed is set. there is a buss and a table of multipliers and dividers. so as one part of the chip oscillates at one frequency the multipliers and dividers say how may times per oscillation the other components go. the cpu speed changes by changing these multiplier values. the problem is that there are only so many multipliers the cpu is designed to use. this is a hardware limitation and can't be overcome so at some point the only way to get more clock speed is to change the buss speed which affects the entire system and will cause instability in most cases. occasionally you can get around this if you change the multiplier values for other componants as well but it's probably not a good idea to mess with it. the hummingbird chip only has multipliers to go to 1600mhz regardless of stability unless you mess with the buss, one developer got the galaxy s to 1700 with buss overclocking but some things didn't really work at that speed and it took a lot of changes to other system clocks. snapdragon chips can go to higher clocks and process numbers better but the hummingbird is better for graphics and multimedia which is more important on a modern phone imho.
so yeah 1600 is it, as far as practicality goes anyway. there are a few infuses that can only go to 1400-1500 as well and galaxy s phones which have the same clock limitations but are only rates for 1000mhz rarely go to 1600, but a few do, my captivate was absolutely peaked out at 1300, believe me i tried to get it higher, i tried a lot of things with voltages to try to get it stable, but even 1300 took some doing. it took a long time before developers even produced a kernel for the sgs that used clocks over 1200 because many of the early builds of the sgs series were much like mine and were not stable at high speeds.
Beautiful. :thumbup:
Sent from my SGH-I997 using xda app-developers app
Related
I read a lot about undervolting on here and i think i have an idea about what it does but i may be way off, and im sure each device is different. in pimp my cpu there are multiple options, and while this sounds newbish i think this should be explained to folks in some more detail.
this is what im assuming.
undervolting allows for less power consumption.
UV on higher OC levels controls power spikes to the CPU?
what is a safe level to UV and at what frequencies specific to the G2x
i am reading up on this, to get a better idea. http://www.android.net/forum/android-rooting/58117-droid-x-guide-undervolting-guide.html
Here's my understanding of the whole undervolting thing..
In order to maintain stable operation across devices with varying production quality (not all chips are created equal), manufactures use voltage levels higher than necessary for most devices. They cater to the least common denominator. But most phones will still operate reliably at a lower voltage. By undervolting you can extend your battery life and ward off chip killing heat. This all becomes even more important when overclocking. When you overclock your device you increase the power usages (those extra megahertz aren't without cost). This increases both the drain on your battery and the heat produced by your CPU. Undervolting helps to offset both issues.
As for the proper undervolting levels...that will vary with the tolerance of each individual device. But I'm sure someone can provide some general guidelines...sorry I haven't undervolted the g2x yet and don't want to steer you wrong.
Hope this helped...
Good info. I dropped mine .25 on each higher level. So ill see how it goes
G2x with CM7 and faux kernel
what confuses me on this topic is the "it's different for each device" phrase that I keep reading. Is this in reference to the rom/kernel that is being used or is it specific to apps installed/how the phone is used.. or is it a combo of both?
It's confusing me because its seems that OC/UV is hardware specific and each phone has the same hardware. So I don't quite get this "it's different for each device" thing..
schmit said:
It's confusing me because its seems that OC/UV is hardware specific and each phone has the same hardware.
Click to expand...
Click to collapse
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
i think you mean this.
cybereclipse said:
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
Click to expand...
Click to collapse
yes all g2x's have a tegra 2 chip.
But production does not always produce the same tolerances for all the chips.
ussually(with the quality control apparently given to the g2x who knows) but ussually all chips are tested and every chip that is in a g2x will perform reliably at 1ghz as it is specified and sold at.
some of these will run reliably at 1500 or better while some will not go over 1100 without starting to get unreliable.
example is the droid 1 was sold at 550 mhz. they did an update that upped it to 600mhz so they knew all chips were tested to be ok at that threshold. Mine would run at 1200 reliably no overheating(except running flash) no reboots.
with 2 different kernels. there was another kernel that they messed with the voltages so that i would get constant reboots even at 700mhz.
some droids would not run over 700 without experiencing problems.
So yes the tegra 2 chips is the same but the abilities of it can be different. they are guarenteed to run at the speed they are sold at but most will function at a much higher speed without problems while some will not.
oh just thought of a great example. the AMD tri-core processors.
those are quadcores where 1 of the cores did not pass the tests but the other 3 did so instead of scrapping the entire chip they turned off the bad processor and sold it as a tricore. there are motherboards out there that allow this core to be turned back on and many have done this and it works just fine. its just that core didnt pass whatever minimum they set on it even though it was perfectally functional they determined that if it got to this temp or didnt run at this speed(over what it was sold at) it didnt pass.
So while this kernel at this voltage may run fine on your phone it may caused reboots or lock ups on others.
hope this makes some sense.
eagle1967 said:
yes all g2x's have a tegra 2 chip.
But production does not always produce the same tolerances for all the chips.
ussually(with the quality control apparently given to the g2x who knows) but ussually all chips are tested and every chip that is in a g2x will perform reliably at 1ghz as it is specified and sold at.
some of these will run reliably at 1500 or better while some will not go over 1100 without starting to get unreliable.
example is the droid 1 was sold at 550 mhz. they did an update that upped it to 600mhz so they knew all chips were tested to be ok at that threshold. Mine would run at 1200 reliably no overheating(except running flash) no reboots.
with 2 different kernels. there was another kernel that they messed with the voltages so that i would get constant reboots even at 700mhz.
some droids would not run over 700 without experiencing problems.
So yes the tegra 2 chips is the same but the abilities of it can be different. they are guarenteed to run at the speed they are sold at but most will function at a much higher speed without problems while some will not.
oh just thought of a great example. the AMD tri-core processors.
those are quadcores where 1 of the cores did not pass the tests but the other 3 did so instead of scrapping the entire chip they turned off the bad processor and sold it as a tricore. there are motherboards out there that allow this core to be turned back on and many have done this and it works just fine. its just that core didnt pass whatever minimum they set on it even though it was perfectally functional they determined that if it got to this temp or didnt run at this speed(over what it was sold at) it didnt pass.
So while this kernel at this voltage may run fine on your phone it may caused reboots or lock ups on others.
hope this makes some sense.
Click to expand...
Click to collapse
Nice...that was much better than my explanation.
cybereclipse said:
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
Click to expand...
Click to collapse
lol. dude, I'm in the g2x forum.. not the "whatever phone ya wanna talk about" forum. I was referring to the g2x's having the same hardware, lol.
Thanks to the other guy for the awesome explanation
I have downloaded SetCPU in my SGS2 and capped my processor to max-1200mhz and min-600mhz. Will it harm my phone if I switch to performance mode which is max & min at 1200mhz (full capacity).
Well I think it depends on the hardware. But I would never recommend to push it at the max frequency, first of all you will decrease your battery life as well as your CPU lifetime since it will produce more heat.
Obviously it can depends of how many times a day you are using your phone to that max clock. If you are experiencing spontanous reboots that means the clock is too high, if not, well.. up to you to keep it like that.
I overcloked my Hero at 710 Mhz for about 2 years (the max capacity it's 748Mhz) and my CPU suppose to run on stock at 525mhz. I can feel my phone been a little hotter compare to the original clock but it has survived until now. (finger crossed)
But seriously.... ask yourself do you REALLY need all that power from your phone?
It seems like every phone can handle a different clock speed, is there is a tried and true way to find the optimal clock speed for your phone?
No as u say every phone acts on hes own so i dont think there is any software for this ( optimal overclock) but there is software for ocing it easy like setcpu or nstools... you can oc your cpu by raising it, and using it with multitasking and if it doesnt reboot in hour or two of heavy usage then go step higher. When it reboots try with step or two higher voltages and so on until you get highest cpu with moded voltages (not more than 2 steps) stable with no reboots. Ofc i wouldnt recommend this as you are not getting anything special from it and you risk your phone... btw optimal cpu speed is its own stock speed that is just pure logic xd
Though there is no agreed upon definition, to me the optimal cpu speed is not the stock speed, the stock speed is the standard safe speed. When a CPU is manufactured it invariably has defects, the number of defects dictates the speed at which it can run. For example, when they manufacture the i5 and the i7 they probably just take defective i7 chips and turn off two cores and call it an i5. (I don't know if they actually do this with the i5 and i7 but it's been common practice with just about every processor in the past.)
I guess I should use a different term like, maximum safe speed.
Trial and error is the best way to my knowledge, haven't heard of any phone apps adjusting clocks on the fly based on temp, inaccuracies, etc, like on a computer. You can feel the temp of the phone and it'll reboot at the smallest sign of instability, just don't set test profiles to set on boot.
And what you say is correct. Processes with similar imperfections are grouped, tested and sold under a given name with the benchmark being stock frequency and voltages. Common practice and very often you get some chips you can over clock til it expands out of its bracket and others which fail at everything but stock.
It seems to me many people overclock their HOX up to around 2ghz through various kernels/ROMs. I'm relatively new to Android phones but I do have a fair amount of OC experience on PC. The thing is, on PC the OC is generally well studied/tested by many people with well established thresholds, and people often upgrade their cooling system to accommodate OC. If stock cooler is used, there are usually established conservative limits. Furthermore, there are programs that stress test the setup to detect any instability. It's known that OC decreases hardware's lifespan, but if you do it right, that decrease can be negligible because of the realistic lifespan of PC.
Our phone is tiny and its cooling is not upgradable. If we overclock it by 30%, what effect will it have on its lifespan? Is there something about these S4 CPU's that I don't know about? Were they made to be able to easily handle the OC without any significant heat increase?
Please share your thoughts.
I'm not sure the true clock speed of the krait but I've read that most CPUs are under clocked by default
So I would think the impact would depend on its true clock speed
It also depends on how long you intend on keeping the phone. I change phones quite often.
If you intend on keeping it two years then I'd suggest just be safe and not sorry. This phone is fairly new and not much is know of long term issues quite yet
Sent from my One X using Tapatalk 2
i know the S4 can be clocked at different speeds by default (1.5-1.7 GHz Dual-core Krait). there is also superpi for android to test stability. it seems 1.5 - 2.0 GHz doesn't give much of a performance boost as far as benchmarks go imo. If we could somehow manage to tweak memory timings like on a pc that would be awesome.
OC = shorter life........to what extent I cannot say. But it's a fact
Sent from my HTC One X+ p_type 0.91.0
My P3 that was a stock speed of 733 an runs at 1.8ghz for last 6 years with factory cooling says don't worry about it.
Also, i couldn't hit 229ms in pi until 2ghz.
If your worried about shortening the life span, by over clocking, its not for you honestly.
WR
Sent from my One X
you overclocked a Pentium 3 733 to 1.8 ghz? i don't believe that at all..
DvineLord said:
you overclocked a Pentium 3 733 to 1.8 ghz? i don't believe that at all..
Click to expand...
Click to collapse
You are correct, its a typo, it should read 1.4 and not 1.8.
WR
Sent from my One X
First I'd like to say excuse my ignorance. So my note 3 was lagging bad after the update to the newest software so I decided to root my device. Not running a custom rom or anything but the main reason I did so was to be able to set my cpu to certain frequencies. So I have done the root. And have tried multiple app from no frills to trickster mod. But each one I have. It will not let me change the frequency above 1497600 mhz. Each time I click on save no matter what frequency above that one it always reverts to 1497600. I use xposed installer and thought I found a module to fix it (dvsf disabler) but if that is what fixes it ive still had no luck. The phone doesnt run horrible but there is a little bit of lag. Does anyone know why this is happening, and how I coukd fix this?
Anyone have any idea? If this is posted in the wrong forum please let me know, I'm just looking for a way around this.
If your CPU frequency is anywhere close to 1,497,600 MHz, I would like to have a word with the laws of physics, and inform it that it is broken. Simply put, there is a limit on how high your CPU can be clocked before it becomes hot as hell and unstable. The highest clock speed I have even heard of a CPU reaching is around 7,000 MHz, which was a very highly overclocked Pentium 4. Newer high end x86_64 CPUs generally don't tend to get overclocked to much higher than 4,000-5,000 MHz, although they are much more efficient with those cycles than a P4, and have the advantage of hyperthreading. Your phone's CPU honestly shouldn't be clocked higher than 3,000 MHz, and if it's a rather weak CPU, it might not even be able to be overclocked to higher than 2,000 MHz.
Or is it perhaps the case that you meant to say your CPU is clocked at 1,497.6 MHz (decimals are important!), and it won't go higher, because as I have just mentioned, there is a limit to how high you can go?
Basically 1.4 ghz. There have been people overclocking at way above that as the cpu is supposed to be around 2.3ghz.