Overclocking's effect on phone's lifespan - AT&T, Rogers HTC One X, Telstra One XL

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

Related

[Q] Overclocking and battery life

This is a question for those who have overclocked their Xoom. How much is overclocking to 1.5Ghz affecting battery life?
Overclocking would be the only reason I would root right now, and I am trying to make up my mind on whether to do it.
My battery life is better after using setcpu to overclock. The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom) with setCPU you are extending the top end of how fast the CPU can go. The clever bit is you can also tell your xoom to slow itself down and go very efficient when the screen is off or if the chipset gets too hot (which it never has). If you do go for it I recommend using setcpu using interactive scaling (prioritising the user interface) and whack the max speed up to 1500 and the min speed down to 217 mhz
I wouldn't recommend setting screen-off profiles at the moment. It seems to lead to some strange issues once in a while.
That said, because you're only going to 1.5 GHz when needed, battery life doesn't really suffer. Additionally, at least in my usage, my screen uses ~70-85% of my battery. This is even during heaving gaming, where the Tegra 2 really has to work hard.
I wouldn't worry about its effects, personally.
MrGinger said:
The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom)
Click to expand...
Click to collapse
All CPUs do this, not just Tegras.
Re scaling, never said otherwise I've never had a problem with screen off profile. Maybe just lucky

[Q] Dangers of overclocking the Sensation's GPU (Adreno 220)

Hey there,
I've read some threads about the dangers of overclocking an Android-device in general. I'm aware of these dangers.
But in my feeling overclocking the sensation is a little different.
Most custom roms set CPU-speed to 1500MHz each core, which is the native clock of the chipset (or am I'm wrong?). No problem so far.
But with tweaking the CPU often the GPU is overclocked, too.
Now the point: What are the dangers of overclocking the GPU?
Does it make sense to overclock just the CPU without the GPU? Is it possible?
What are your experiences with overclocking (e.g. with IsertCoin or RevolutionHD) the GPU?
What you have to remeber with regard to overclocking is that your not alone in doing it when you use one of the custom roms.
Many thousands of ppl are running overclocked handsets and the first things you see happening from overclocking to far is your handset not booting up or locking up well before you would do any physical damage to the handset i would say.
I have run my sensation at 1800 cpu speed and it started ok but locked up when doing one of the benchmark tools , i rebooted and reduced the speed a little but all running fine with no concerns with regard to overheating
So there is a hardware protection to prevent serious damage?
I dont know enough about the handset to say if there is or not i suspect there will be something , but have you ever tried to overclock a graphics card on a pc you get so far and it wont display or something like that so you reduce it.
Heat with any electronic component is i problem and overclocking something increases that heat, but when you get to a certain point your phone will lock freeze reboot etc usually before any damage is done.
If you have any concern about destroying your phone by overclocking the simple answere is that you dont overclock it .
Diydude said:
[...]
If you have any concern about destroying your phone by overclocking the simple answere is that you dont overclock it .
Click to expand...
Click to collapse
Yes you're right of course, but i just want to get a feeling for this topic... i just try to decide if it's a good idea to use RevolutionHD, which is overclocked from the beginning.
And to get a feeling, I just asked about the risks, because the benefits are clear for me
To answer your question, yes, the sensation comes with thermal protection that helps against overheating. If the device becomes to hot, it(in most cases) shuts itself down until it cools. The CPU in the sensation is underclocked when it's shipped at 1.2Ghz(1188), but the true spec of the CPU is actually 1.5Ghz(1536). HTC underclocks the CPU to 1.2 to save on battery consumption. I personally have ran my phone just fine at the 1.5Ghz setting, I've even pushed it up to 1.6Ghz(1620) and it ran fine with the exception it did get just a little hot, but nothing to worry me. That being said I've since underclocked my CPU to 1296 and all is well. And afterall, how fast do you really need your phone to be before you take it too far and fry the cpu?? The sensation is fast right out of the box and even faster when using a NO sense rom, such as cm7(my personal fav)
Side Note : The new sensation XE ships with the cpu at it's original clock speed of 1.5Ghz.. both sensations have the 'exact' same cpu.
In regards to your GPU question, I have mine set @ 300mhz and not 320. The sensations GPU comes clocked at 266.I've ran it @ 320 and it ran just fine.. for me it's more of a personal preference. My graphics look just fine clocked @ 300mhz.. Below is a quote about the chipset and the new one coming out.
"With Adreno 225 Qualcomm improves performance along two vectors, the first being clock speed. While Adreno 220 (used in the MSM8660) ran at 266MHz, Adreno 225 runs at 400MHz thanks to 28nm. Secondly, Qualcomm tells us Adreno 225 is accompanied by "significant driver improvements". Keeping in mind the sheer amount of compute potential of the Adreno 22x family, it only makes sense that driver improvements could unlock a lot of performance. Qualcomm expects the 225 to be 50% faster than the outgoing 220."
if this helped, give the thank you button a punch
p.s. I've ran both insertcoin & revolution HD and both ran fine.. I just really prefer no sense roms
Quakeworld said:
To answer your question, yes, the sensation comes with thermal protection that helps against overheating. If the device becomes to hot, it(in most cases) shuts itself down until it cools. The CPU in the sensation is underclocked when it's shipped at 1.2Ghz(1188), but the true spec of the CPU is actually 1.5Ghz(1536). HTC underclocks the CPU to 1.2 to save on battery consumption. I personally have ran my phone just fine at the 1.5Ghz setting, I've even pushed it up to 1.6Ghz(1620) and it ran fine with the exception it did get just a little hot, but nothing to worry me. That being said I've since underclocked my CPU to 1296 and all is well. And afterall, how fast do you really need your phone to be before you take it too far and fry the cpu?? The sensation is fast right out of the box and even faster when using a NO sense rom, such as cm7(my personal fav)
Side Note : The new sensation XE ships with the cpu at it's original clock speed of 1.5Ghz.. both sensations have the 'exact' same cpu.
In regards to your GPU question, I have mine set @ 300mhz and not 320. The sensations GPU comes clocked at 266.I've ran it @ 320 and it ran just fine.. for me it's more of a personal preference. My graphics look just fine clocked @ 300mhz.. Below is a quote about the chipset and the new one coming out.
"With Adreno 225 Qualcomm improves performance along two vectors, the first being clock speed. While Adreno 220 (used in the MSM8660) ran at 266MHz, Adreno 225 runs at 400MHz thanks to 28nm. Secondly, Qualcomm tells us Adreno 225 is accompanied by "significant driver improvements". Keeping in mind the sheer amount of compute potential of the Adreno 22x family, it only makes sense that driver improvements could unlock a lot of performance. Qualcomm expects the 225 to be 50% faster than the outgoing 220."
if this helped, give the thank you button a punch
p.s. I've ran both insertcoin & revolution HD and both ran fine.. I just really prefer no sense roms
Click to expand...
Click to collapse
some sources say adreno 220 can be overclocked to 400mhz .... bdw how can i overclock ...is der a app like setcpu for it ?????
rohit choudhary said:
some sources say adreno 220 can be overclocked to 400mhz .... bdw how can i overclock ...is der a app like setcpu for it ?????
Click to expand...
Click to collapse
a few time ago some other user reported the same thing about adreno 220
but i think it is too high that value and it is impossible for gpu to handle such a value
in order to overclock the gpu you have to flash another kernel

[Q] overclocking droid charge

How can I go about overclocking my droid charge? I am running TWEAKSTOCK 1.0 rom and was wondering how to overclock my charge?
I haven't seen any over clockable kernels so until then I don't think you can.
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Chitala383 said:
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
With the same kernel?
Well, if you actually searched, this would be clearly stated in many threads.
For GB overclocking, use Tegrak for now, until we can get an actual OC kernel up and running. I think Tegrak will work on the stock kernel as long as you're rooted, as it uses a module to modify the CPU frequency.
Sent from my SCH-I510 using xda premium
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
xdadevnube said:
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
BattsNotIncld said:
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
Click to expand...
Click to collapse
Take what I say with a grain of sand, I'm expressing my views without much scientific validation.
Keep in mind that overclocking is like icing on the cake. There are far more beneficial things like changing the scheduler to noop or deadline. Fugu tweaks and V-6 are highly recommended to improve responsiveness and improve your launcher resiliency. That said, I feel overclocking has its place and helps in many cases. I've noticed, in general, various tasks and some web-browsing will benefit from the increased clock speed. Some things don't ramp up the CPU very much and you won't notice much difference in that case.
I monitor my CPU usage with CPUNotify as well as OS Monitor.
I monitor the CPU temps with TempMonitor (it allows for a notifcation icon that shows the CPU temp.)
I use StabilityTest to check for overclock settings stability. The cool thing about Tegrak is that when you apply overclock settings on boot (paid version only) and you choose settings that crash the phone, the settings don't apply until most of the phone is already booted up, so you aren't stuck in an infinite boot loop of crashing fun. You should be able to simply change up the settings after they apply since the phone will be mostly idle by the time Tegrak settings are applied.
As for settings...
I use the Interactive X governor. I prefer this governor for its simplicity and ability to ramp up to high CPU clock speeds quickly. I enable the governor by typeing "su" and "ix enable" in Terminal Emulator when on Imoseyon's 4.0 kernel.
I change the "scaling min" to 200Mhz to avoid instability when CPU usage ramps down quickly.
Currently at CPU Level 0 I am at 1265mv Core Voltage, 1100mV (unchanged) Internal Voltage, and 1200 Mhz Frequency.
I don't actually change other CPU Levels.
Lately I've been just keeping at eye on temps so I haven't achieved my desired clock speed of a relatively low-voltage 1.4Ghz to 1.5Ghz.
Overclocking is very dependent on the particular sample you get. Some of us have "Golden Chips" and some of us have duds.
Your CPU should be totally safe at temps around 130 degrees F, although I suspect that it could even take higher sustained temps well above that if it needed. I don't actually know, this is speculation.
I like to keep my temps low in general, I rarely crack 100F with my current settings (weather is cool here.)
Overclocking computers is one of my hobbies, and its fun to dive into the phone side of things. I haven't been able to find a whole lot of information regarding overclocking the Hummingbird processor. People have overclocked to 1.6Ghz. Stability tests are essential to improve the reliability of your overclock. Die hards will run the tests for 24 hours to weeks in the computer realm. At least with computers its better understood how the stability test actually works. I run 24 hours of Orthos blend mode (Prime95) on each core.
With phones, its hard to say if it will truly be stable.
I test for an hour on the phone with StabilityTest and call it good. Hopefully in the future more information will come to light regarding how to properly overclock.
Remember, the other side of the coin is underclocking and undervolting. If you drop your voltage, you should see a nice increaes in battery life. If you drop your clocks, then you can drop your voltage even more. If you get your phone dialed in to where there isn't much background apps sucking juice- a phone that is UV/UC'ed should have excellent battery life.
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
kvswim said:
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
xdadevnube said:
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
Click to expand...
Click to collapse
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
kvswim said:
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
xdadevnube said:
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
Click to expand...
Click to collapse
Probably because no one has taken the time to write one. Not exactly in high demand. I knew of one "guide" but the site has been down for quite some time.
Of course there are noobs guides but nothing quite in depth. I suppose people don't write them because there are obvious limits set by the kernel dev, and anything beyond that requires someone who obviously knows what they're doing, which defeats they purpose of a guide.
Sent from my GT-P1000 using xda premium

[Q] - Overclocked kernels - What's the point ?

I see a lot of overclocked kernel editions, and I am wonder could someone explane me, except extensive battery draining, instabillity and overheating of device, what is and is there any crucial positive point of overclocked kernels ?
Overclocked kernels are simply kernels whose speed limit had been raised above the stock speed.
That increases perrormans dramatically as is visible by different benchmarks utilities.
You are correct to assume that higher clock would require some extra voltage and that the phone will get hotter. But it is not always noticeable and is mostly depentant on the configuration.
The cpu clock is not always at the highest possible. Different governors define what speed should the cpu be at any time. If there's a lot of work the cpuspeed would increase and if it idles a lot it would decrease.
I love 3 oc kernels, Sebastian's, bricked and faux. They all have different philosophies but all are excelent, do not overheat and save gather.compared to stock though they allow higher cpu freqs.
I suggest you create a nandroid backup and try some of.there kernels. Give it atleast two days.before you make up your mind about it, and try another if you wish, till you find the one that is right for you.
Sent from my HTC Sensation using xda premium
I agree. I never see the point of over clocking. I always limit my processor to 1.18 or even 1.13 and never have any problems with overheating or poor battery life!
I used overclock kernels for a long time on my gs2. Its nearly the same like with a desktop CPU. Every CPU had it's own work range, many CPUs a
are even able to work with higher frequency but lower voltage than standard. This causes in higher speed with lower power consumption!
all you need is a kernel which allows individual voltage settings for each speed which you can set with setcpu.
BUT my opinion is that even the gs2 with 1,2 GHz dual core was faster than any Android app had needed, so the gs3 at all!
ATM I've setted the max frequency in setcpu to 600 mhz and I can't see any lags or missing speed...
So I guess many people are more looking for benchmarking than real practical advantage..
but undervolting is a real great thing for power hungry smartphones!
Gesendet von meinem GT-I9300 mit Tapatalk 2
You all right guys. That is why I asked myself that question because there is hard to find modded kernels with default speeds and all new goodies, because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value, even in settings they were limited, and that impact widespread device causes instabillity ( and corrensponding unpleasent situations of forced battery pulling).
Last good kernel what I find for my CM7 ( I don't like ICS) is Bricked_XE-1.6.beta7 and with this release of CM7 it seems that kernel edition further development stops.It runs on 1526 Mhz and I allways wonder why shouldn't it run "out of the box" on default speed...
Does anyone have suggestion link, (because I couldn't find it )for any CM7 modded kernel with all new goodies, but running on default Sensation XE Mhz speed ?
i have been using overclocked Kernels for a while now and rarely have any problems, the phone is quick, very quick and the battery drain is really not that different and that is running it at 1.72 with both cores permanently on
tin2404 said:
[...] because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value
Click to expand...
Click to collapse
This really should not happen. The maximum frequency for a governor is set through /sys pseudo-fs and (assuming the governor is not buggy) strictly followed. Maybe you have some leftover scripts somewhere messing with /sys?
tin2404 said:
( and corrensponding unpleasent situations of forced battery pulling).
Click to expand...
Click to collapse
And this should -- like already pointed out -- only be the case under heavy load. Normally, a sensible governor will only set frequencies necessary to satisfy the current load.

[Q] Is the Infuse underclocked from the factory?

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

Categories

Resources