Related
Hello..anyone can teach me how to overclock xperia x10
Bootloader is not unlocked. It's impossible at the moment.
Sent from my X10i using XDA App
satAxOnic said:
Hello..anyone can teach me how to overclock xperia x10
Click to expand...
Click to collapse
First, you crack the bootloader.
When you've done that, I'm guessing you allready figured out how to OC the CPU
Sent from my FreeX10i beta2.
satAxOnic said:
Hello..anyone can teach me how to overclock xperia x10
Click to expand...
Click to collapse
For now just use the overclock widget. set top two settings as high as you want up to 998 click on off screen frequency. set between 246 and next number you choose. set at boot save. define settings at what mhz you like and experiment. do not run on screen and off screen freq at max. i have had my battery sweating and even plugged in all day and not gained a single % of charge. until boot loader is cracked.... this is all you can do.
xperiax10a
2.2b2
Bummmod
gapps1901
quadrant 1800
linpack 40.XX
Although it's impossible today because of bootloader, note it's always dangerous and not great to overclock embedded cpus.
You can't overclock a lot, as you have a battery (X10 works about 5-10 hours with full speed - 998MHz), and the CPU only has passive elements to cool. Overclock can damage your CPU and your motherboard, stress all elements and low your battery life (battery charge and cycle of charge). (Even there's a self shutdown when too hot)
You can get an idea of overclock on Nexus forum, as we have the same CPU (Snapdragon 8250) - I saw overclock up to 1300 MHz, but it's really not looking safe to me
Thanx everyone..
Perceval from Hyrule said:
Although it's impossible today because of bootloader, note it's always dangerous and not great to overclock embedded cpus.
You can't overclock a lot, as you have a battery (X10 works about 5-10 hours with full speed - 998MHz), and the CPU only has passive elements to cool. Overclock can damage your CPU and your motherboard, stress all elements and low your battery life (battery charge and cycle of charge). (Even there's a self shutdown when too hot)
You can get an idea of overclock on Nexus forum, as we have the same CPU (Snapdragon 8250) - I saw overclock up to 1300 MHz, but it's really not looking safe to me
Click to expand...
Click to collapse
Depends also on the voltage (as long as your voltage isn't increasing as you overclock, it isn't really that harmful as long as you watch the heat), and what you have your underclock speed set to with screen off (as this can in some sense reverse some of the possible "damage")...
I had my htc hero overclocked to 710 with the screen on, and underclocked 176 with the screen off and it ran a lot better.
I digress, I see no purpose in doing so when you already have a 1ghz processor that is super fast. I only really see a point in overclocking if the possible benefit is greater than the possible harm, and in this circumstance, I really don't think you would see that much benefit.
fiscidtox said:
Depends also on the voltage (as long as your voltage isn't increasing as you overclock, it isn't really that harmful as long as you watch the heat), and what you have your underclock speed set to with screen off (as this can in some sense reverse some of the possible "damage")...
I had my htc hero overclocked to 710 with the screen on, and underclocked 176 with the screen off and it ran a lot better.
I digress, I see no purpose in doing so when you already have a 1ghz processor that is super fast. I only really see a point in overclocking if the possible benefit is greater than the possible harm, and in this circumstance, I really don't think you would see that much benefit.
Click to expand...
Click to collapse
I have seen considearable difference when maxed out. however the dangers are high of overheat. ive done it once and onetime only. kept on and off screen at 998 and hat it plugged in all day with out a single gain of battery. it was like on life support and was hot enough the phone was sweating even when sitting next to a fan blowing on it constantly.:-( since then i have made adjustments to run between 700 and 998mhz on screen and min 246 and 400mhz when screen off.
if looking for better performance without the overclock and good drain of battery, download and install sysctl from market and follow settings below.
min free kb: 900000
dirty ratio:500000
dirty background:200000
vfs cache pressure:10
Oom allocating: checked
On SetCPU there is Set on boot- to be checked or not?
Sent from my X10i using Tapatalk
it should be checked
OC can damage yo device. Id say its better to hv a lil slower device than a dead device
Sent from my X10x using XDA App
live4speed said:
OC can damage yo device. Id say its better to hv a lil slower device than a dead device
Sent from my X10x using XDA App
Click to expand...
Click to collapse
Not in all instances. Depends on the quality of the chip. Lot of chips are capable of handling higher speeds and temps but are set lower quality assurance.
For instance, I've got a NookColor that has base CPU set at 800MHz and is now overclockable to 1.2GHz
We'll have to do stress tests on some to see what they're capable of.
andrewddickey said:
Not in all instances. Depends on the quality of the chip. Lot of chips are capable of handling higher speeds and temps but are set lower quality assurance.
For instance, I've got a NookColor that has base CPU set at 800MHz and is now overclockable to 1.2GHz
We'll have to do stress tests on some to see what they're capable of.
Click to expand...
Click to collapse
Agreed.
My Motorola Defy has a Omap3630 that comes at 800MHz,stock but can be easily overclocked to 1.3GHz without a sweat.
Just depends on the chip's capacity of "Stress".
Respect
root rookie here.. First device I ever rooted, really I'm new to cell phones in general.
I flashed this rom adryn bamf 4.1 (non remix) and its working good and all
But I noticed on the smartass setting, which underclocks, that after about an hour or so of playing a game/tv whatever my batter will be around 42C, it seems very hot compared to around 32C before I put this rom and kernal on
Two questions
Am I doing something wrong or is this normal
And, How hot can a battery get before it becomes something to worry about?
Thanks =P
Yea in the 40's is way high. Remember, heat is inefficiency (wasted energy). After playing a game for an hour you will probably be in the mid 30's C. I would recommend trying a different kernel and wiping devlik cache. Also, see what apps and services are running in the background and increase the length of time between syncs. Also, smartass scaling did great on my incredible but I have found that it is not perfected yet for the tb. I would suggest ondemand unless the dev or OP specifically says that smartass is the way to go. As far as heat and battery I find that adrenylyn's kernels do the best. As far as performance, drod and ziggy's seem to fly. Isoman or whatever seems to also be a favorite but I personally didn't have great results. It is important to not supremely OC or UC. I would simply stray away from UC in general. For a daily driver, I would stay under 1.5 Ghz, and honestly 1.2 seems to work best for me. Hope this helps.
thanks for taking the time to respond
So why no under clocking? I assumed it would help battery life but not so much?
Just set to 1200 for both min/max? Or on demand scaling up to 1200?
I prob had a bunch of apps running in the backround, i'm new to droid.. came from an old feature phone
42C is definately too hot! As the previous poster suggested, try a different kernel. There also could be a remote chance your battery is defective.
I really feel like it is more likely that something I am doing is impacting it
I had the phone stock for a week and no problems (same usage)
Rooted but stock rom for a week and no problems
Put this kernal on (which everyone says is really good) and this rom and it was getting hot.. So far it is good around 38-39 (still too high?) with 1200mhz on demand min 256mhz
I flashed 2 different kernals and both times after less than 45 mins of browsing forums and playing home run baseball my battery gets to 42C. Could this be caused by the rom? I wonder if I damaged my battery or phone at this point
Mine got up to 113 degrees over the weekend. It felt like I was cooking my phone off and getting ready to throw it like I do in black ops.
I realized my phone was trying to search for a 4g signal when there was none. I entered #*#*#4636#*#*# on my dial pad to turn it off. It reduced my battery heat by 5 degrees. I should point out I was out in the field. Aka in the middle of nowhere where.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
I'm @ 53.4C right now and it doesn't seem to be charging, lol.
raider3bravo said:
Mine got up to 113 degrees over the weekend. It felt like I was cooking my phone off and getting ready to throw it like I do in black ops.
I realized my phone was trying to search for a 4g signal when there was none. I entered #*#*#4636#*#*# on my dial pad to turn it off. It reduced my battery heat by 5 degrees. I should point out I was out in the field. Aka in the middle of nowhere where.
Sent from my rooted Thunderbolt with VirusROM AirborneTB. Xda premium
Click to expand...
Click to collapse
Sorry but to fly off topic what do you do? I'm generally out in the boondocks when I'm on wellsite...
Sent from my Thunderbolt running CM7...
42c isn't anything out of the ordinary, or outside operational parameters for a battery of that type. Not by a long shot, actually. That battery can safely operate at 59c, but the phone won't charge it north of about 47c due to the fact charging will increase the temperature even more.
As for the governors:
The smartass governor operates similarly to the interactive governor, but isn't as aggressive and allows for wake up lag reduction. The governor SHOULD be your main line of controlling clock speed, not your min and max settings. Some might like to argue that point, but that's mainly because they haven't messed around with governor parameters. With and ondemand or interactive governors, and even some smartass governors (Not Ziggy's modified), it's entirely possible to set min as low as 61MHz, and max at 1.65GHz and have the CPU rarely, if ever, reach those speeds. It depends entirely on what you've set the governor parameters to be. I don't know of any app that allows you to modify those because the locations of the parameters aren't always the same name or in the same places so it's best done through a script. The script I uses does routinely reach up to my freq_max, but it does it fairly aggressively, then ramps down just as aggressively. Part of that is the nature of the lagfree governor, part of it is where I've set the thresholds. In any event, governor control via a script is a much better solution than castrating your device.
Well I downloaded cpu master (free) to just mess around with my photon, and come to find out, the governor for the cpu is set to performance, but gave me the option to change it to powersave, so I switch it and I'll report back to you guys and see if I've found the holy Grail to even better battery life
Sent from my MoPho using XDA App
That's awesome
Sent from my MB855 using xda premium
Wait until I or another dev gets onDemand governor enabled...
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
xTMFxOffshore said:
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
Click to expand...
Click to collapse
The general consensus regarding over/underclocking when I had my HTC Hero was that overclocking would save battery because you could get what you wanted done faster. If you scale the CPU back massively while it is set to sleep, however, you will save a lot of battery.
xTMFxOffshore said:
I have SetCPU, and honestly, I haven't noticed a huge difference in battery life with powersave unless I seriously scale the CPU back to like 300 mhz. Then it'll last a while, if I don't do ANYTHING with it. For example, when I'm sleeping, otherwise, it just makes the phone laggy and doesn't seem to help enough to make it worth while. Just my opinion from screwing with it.
Click to expand...
Click to collapse
well, i don't know about your phone or what else you have setup, but my phone didn't lag and it seemed to help, i currently have my evo 3d active so my photon just sits there, so i can give a good feedback of idle time, but i can tell you after switching the governor, it went down 1% in 2 hours, now i say that's an improvement, so when i get back home i'll really give you guys some feedback
P.S. with any phone i had that had a fully custom kernal, i always used conservative governor
Well, perhaps it's just the apps I have running then. As I said, when it's set to sleep, it works pretty well with the powersave mode, otherwise, doesn't seem to make any real difference. Guess it's different for everyone cause of the **** they're running on their phone.
mrinehart93 said:
The general consensus regarding over/underclocking when I had my HTC Hero was that overclocking would save battery because you could get what you wanted done faster.
Click to expand...
Click to collapse
You know, I've never bought into this argument. To me, it is like saying that if I drive 100 mph I will get there faster, so I use less gas....which we all know is not how it works.
Maybe the physics are different for processors then they are for engines, but I think there is probably a happy medium somewhere. And I have a feeling that the manufactures really take this into consideration when they develop the kernels and ROMs. However, I might be wrong.
This is by no means an effort to discourage your awesome work. Everyone gets different results, but stock always seems to have the best battery life for me once all the bloat is gone. However, custom kernels do perform better. That is the trade off, in my opinion.
my2cents said:
You know, I've never bought into this argument. To me, it is like saying that if I drive 100 mph I will get there faster, so I use less gas....which we all know is not how it works.
Maybe the physics are different for processors then they are for engines, but I think there is probably a happy medium somewhere. And I have a feeling that the manufactures really take this into consideration when they develop the kernels and ROMs. However, I might be wrong.
This is by no means an effort to discourage your awesome work. Everyone gets different results, but stock always seems to have the best battery life for me once all the bloat is gone. However, custom kernels do perform better. That is the trade off, in my opinion.
Click to expand...
Click to collapse
Lol honestly I never bought into it either. I was just posting was the other devs at the time said. Even using an OC kernel, I never overclocked my phone.
mrinehart93 said:
Lol honestly I never bought into it either. I was just posting was the other devs at the time said. Even using an OC kernel, I never overclocked my phone.
Click to expand...
Click to collapse
Interesting...I hadn't thought about using an OC kernel and underclocking it back to stock. I wonder what that does, if anything, to performance.
The other concern that I have is that overclocking typically means more heat, which means more battery use... Just figured I would throw that out there too.
well, the results are in, now granted i already had the photon of the charge for more then 24 hours, so at 1d 15hr 57m and 10s i'm at 48%, but from the time i started the cpu test, 1:30pm, it was at 68% so in 8 horus there was only a 20% drop while idle, i say that's a good score , you guys tell me otherwise
A2CKilla said:
well, the results are in, now granted i already had the photon of the charge for more then 24 hours, so at 1d 15hr 57m and 10s i'm at 48%, but from the time i started the cpu test, 1:30pm, it was at 68% so in 8 horus there was only a 20% drop while idle, i say that's a good score , you guys tell me otherwise
Click to expand...
Click to collapse
and just an update, in another 4 hours, it's only gone down 2%!!!!!! come on guys, these numbers can't lie, but remember this is idle feedback, i'll re-activate my photon at the end of the week (missing the beast!) to give more detail feedback on heavy usage and most importantly 4g!!
Development. Development. Development.
Sent from my MB855 using xda premium
Not sure if this will help but let me explain the car analogy. All motors have an effeciency range at x amount of throttle. So same cars will get better gas mileage at a higher speed vs a lower one. Its getting up to that speed where most energy is used.
So let me move this over to electronics. If you run a faster clock speed while on, your apps will open faster so that ia less on time for the screen and other processes that have to run. So using more watts for less time does not always equal more than using less watts for more time. We just need to fill in those blanks and obviously overclocking will not benefit the nook or internet reader as it eould someone who opens a lot of apps for short periods. Same is true for a gamer .
Hope that makes sense and this is all IMHO of course.
Sent from my MB855 using XDA App
scoobdude said:
Not sure if this will help but let me explain the car analogy. All motors have an effeciency range at x amount of throttle. So same cars will get better gas mileage at a higher speed vs a lower one. Its getting up to that speed where most energy is used.
So let me move this over to electronics. If you run a faster clock speed while on, your apps will open faster so that ia less on time for the screen and other processes that have to run. So using more watts for less time does not always equal more than using less watts for more time. We just need to fill in those blanks and obviously overclocking will not benefit the nook or internet reader as it eould someone who opens a lot of apps for short periods. Same is true for a gamer .
Hope that makes sense and this is all IMHO of course.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Let me start this off by saying that I am an agricultural engineer by trade. With that said, I would agree that engines have an efficiency range. However, I would not agree that it is at x throttle. Rather, it is a x load. And most cars are designed to be at optimal load at about 60 mph (wind resist, weight, etc. play a role in this). You're right, it does require more fuel to get to that speed because the load is higher until that speed is reached. Furthermore, higher speeds (greater than 60 mph) do NOT translate into higher fuel mileages because the load increases to maintain the higher speed (because there is more wind resistance, among other things).
I know a bit about electricity too, but I don't fully understand the physics behind circuit boards. However, I think the analogy still holds. I can get to 60 mph as fast as I want, but the faster I do it the more energy is required. Therefore, even though it is done faster it still requires more energy, which also creates more heat, both of which use the battery. So, I continue to contend that there is a happy medium that most be found and I think electronic engineers aren't to far off.
Here is a little more reading about car efficiency, if you are interested: http://www.mpgforspeed.com/
I believe your confusing overclocking and overvolting. We are putting x volts into the processor so the more cycles we can get in x volts the better. If we have to overvolt to overclock then we see big battery hits.
Sent from my MB855 using Tapatalk
2cents, that link is interesting but real world examples have proven otherwise to me. Our saab will do better on mpg at 70 to 75 (30 on cruise control) vs 55 to 65(27 to 28 on cruise). Now the wrx is another story as well. With the old 3.9 final drive i would pull in more air at the airflow meter at 65 than i would at 70 with stoich as the target a/f ratio, and because that motor was doing under 2500 rpms the turbo was out of the equation further taking out efficiency with it. Now with the 4.44 and a better 1-2 gear ratio car gets better at the lower engine speeds and accelerates even better and that was before i retuned it.
Another misconception is bigger motors use more gas, one of the recent corvettes get 30 on the highway proving that there is more to this as well.
I think i have taken this off topic enoigh for now. But in general i think my formula still needs to be applied to see the results as a valid number to compare overclocking and underclocking to running stock.
Sent from my MB855 using XDA App
i'm surprised no one even thought of this topic, regardless if things are getting done "faster" you are overclocking the cpu, making it go faster then what it's suppose to, which makes it use more power i.e. more battery, every phone that i had when i overclocked it, the battery wouldn't last too long, even with my 3500mah OG evo, if i overclocked it, i couldn't get a whole day, so underclocking will have the same effect in a sense since the processor now has to work harder to do what it does at it's stock clocked speed, well, hope anything i said here makes any logical sense, but on another note, the photon has gone almost 3 days unplugged!!!
again it depends on how the overclock is achieved. In most cases overclock is achieved by dumping more electricity into the cpu this will impact battery life, however alot of chips these days can be overclocked at the same volts essentially upping the "MPG" or clocks per volt.
A2CKilla said:
i'm surprised no one even thought of this topic, regardless if things are getting done "faster" you are overclocking the cpu, making it go faster then what it's suppose to, which makes it use more power i.e. more battery, every phone that i had when i overclocked it, the battery wouldn't last too long, even with my 3500mah OG evo, if i overclocked it, i couldn't get a whole day, so underclocking will have the same effect in a sense since the processor now has to work harder to do what it does at it's stock clocked speed, well, hope anything i said here makes any logical sense, but on another note, the photon has gone almost 3 days unplugged!!!
Click to expand...
Click to collapse
I agree with this for the most part. When it comes to power the end result is watts, which is essentially equal to volts x amps. It is not perfect because of a power factor, but it is close. Therefore, if you lower the voltage, the amperage goes up because the same watts are required to run the processor. The inverse is also true. These processors have voltage ranges that they will safely run in, but in the end, they require the same energy (in watts) to function at a given load. Change one a little bit (the voltage for example) and the other (amperage) compensates. Change it a lot and it likely wont work. Again, this is how it works for your typical home appliances. For a circuit board, it might be a slightly different story, but I imagine the science does not change.
---------- Post added at 03:57 PM ---------- Previous post was at 03:47 PM ----------
scoobdude said:
2cents, that link is interesting but real world examples have proven otherwise to me. Our saab will do better on mpg at 70 to 75 (30 on cruise control) vs 55 to 65(27 to 28 on cruise). Now the wrx is another story as well. With the old 3.9 final drive i would pull in more air at the airflow meter at 65 than i would at 70 with stoich as the target a/f ratio, and because that motor was doing under 2500 rpms the turbo was out of the equation further taking out efficiency with it. Now with the 4.44 and a better 1-2 gear ratio car gets better at the lower engine speeds and accelerates even better and that was before i retuned it.
Another misconception is bigger motors use more gas, one of the recent corvettes get 30 on the highway proving that there is more to this as well.
I think i have taken this off topic enoigh for now. But in general i think my formula still needs to be applied to see the results as a valid number to compare overclocking and underclocking to running stock.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
You may be right. Perhaps Saab designed their fuel efficiency at 70 mph. It's possible because many speed limits are now at or near that, but in general, optimal fuel consumption is going to be at or near 60 mph. Obviously gear ratios and such play a huge role in fuel economy. It is like using a custom rom, typically your mods will make it perform better, but the best fuel economy or battery life will come with a stock like setup.
Sure a corvette can have HP and economy. There is a power to weight ratio and lots of aerodynamics involved, which again is designed at a specific speed. But there is no way that a dragster will have a good fuel efficiency. To my point, there is a balance...
I agree, we are off topic a little bit, but the conversation is interesting, nonetheless.
By the way, can a mod move this to general, please?
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.