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
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
Interesting point you raise actually.
I've just installed Setcpu and used the on demand governor. I left the values as default (200mhz for minimum and 1.2 ghz for maximum) - with no overclock.
I've immediately noticed swiping through the screens is a bit smoother and the biggest improvement is the gallery. All my photos appear much smoother. Before the gallery app was a bit lagy.
I haven't set any profiles yet such as screen off.
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
jzuijlek said:
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
Click to expand...
Click to collapse
Have you tried this yet though on the Galaxy S2?
There is definitely less lag than before - as stated, specifically in the gallery app. Just generally swiping feels more responsive as well. Battery is still pretty awesome, especially when using Lightening Rom 1.1 and the Android battery calibration app.
Hmm. I'll try SetCPU on the SGS2 and post back the findings (Performance+Battery).
I don't know how can it get any more smoother, I mean its already SO smooth!
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
alexleon said:
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
Click to expand...
Click to collapse
IT IS TRUE. I agree with every single line you wrote, it is just my expericence.
I have too setcpu conservative and undercloked 800 Mhz.
There no slow down or lag at all... But I am wondering if it gives a real boost to battery life. I am not sure of this.
I'll keep you guys posted... But I think that an undevolted Kernel it is really a need as for the solution of the damn dual core ginger bug that is sucking 20% of my battery every day
Well,from my experience with my Desire and Desire HD(won't even bother with the Hero,I had no real knowledge then),governors can make a huge difference.I for one like smartass or interactive governors(mostly the same).I wouldn't suggest conservative,interactive does the job much better.Tasks get done in less time and the CPU throttles down more quickly.Other than that,you can underclock or overclock all you like,it never made any big difference in battery life for me(Unless Sammy's CPUs are different in that aspect-Snapdragons are really "overclock-friendly").That's personal preference after all!
Anyway,the best solution IMO would be a vdd_levels interface.For those who don't know what it is,it is a mod made by -snq(Meet him at the Desire forums-That guy's a true LEGEND!He can patch/modify anything!),which practically allows you to change the voltage levels of the CPU on the fly rather than having to stick with the values hardcoded into the kernel.Using this and a simple script in GScript to change values that won't survive reboot or in init.d to be applied on boot,you can find the optimal voltages for your CPU(Don't forget,every CPU is unique and different),thus reducing heat and maximizing battery life.
If a dev brings that to the SGS2 it will be a big step in the right direction as far as I'm concerned.
I use SetCPU without issue, but only to run profiles (i limit the device to 500mhz when the screen is off). The rest of the time it scales itself up to 1.4GHz without fuss and using stock voltage. Battery life is fine, best ive had for an android device.
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
I did set ondemand which is a little more reactive and slightly smoother.
Though System Tuner is less cpu-consuming and much more useful on the SGS2. No need for all those complicated settings from setCPU. Only changing governor and changing frequencies on standby are useful.
leedavis said:
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
Click to expand...
Click to collapse
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
I am using Check Rom with set CPU I have it 1.2ghz max and 200. Using conservative governer. I been off charge for 15hrs, however I am using light usage I am on 72% screen on has been 5h 25m at time of writing. Not yet calibrated the battery.
jonny68 said:
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
Click to expand...
Click to collapse
What are the settings are you using for the setcpu program in your S2?? Did you remove the Juice defender application?
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.
I flashed the cm7 1.4 240-325-300 Kernel.
In my settings what should I keep my min and max at for all time usage?
I max them and my quad score is like 5501
don't know if your supposed to keep those certain.
Also does decrease or increase battery life.
I left mine at the default values. Was wondering this myself though. How do you test quad scores?
Download quadrant standard from market
Sent from my MB855 using XDA App
You want the lowest value to be at the lowest(216 i think) because this allows the processor to idle at that low speed, if you keep the minimum speed at 1ghz your processor will ALWAYS be running 1ghz at the lowest, and that will be an obvious way to kill your battery in no time. So set that to the lowest, and for the maximum i personally run mine at 750 for CM9, think i had it at 800 for CM7 but cannot remember for sure. This is limiting how fast the processor can run so the lower the better as far as battery goes. It comes down to you personally, if you game and do processor heavy tasks often then having the processor underclocked like i run mine will affect your gaming/app/overall experience. Its always like 2 clicks away to bump it up to a higher speed and i have a link on my home screen so if i do decide to do anything processor heavy i can bump it up quickly. But in general it takes more power for your processor to run higher so if your really concerned about battery life try bringing it down. I can still score a solid 1,500+(with a bunch of crap installed on my Photon mind you) on CM9 with my max at 750 and min and 216. Benchmarks are honestly just a number, it comes down to how if performs for you and what you are doing with your phone.
Awesome, I'm lowering it now and battery is dropping slow so its good, thanks for the detailed reply.
Sent from my MB855 using XDA App
First off is this a good idea? can such small devices be over clocked in a safe way without risking damaging the hardware?
if yes which would you say was the best app for doing so?
Hi,
A good idea... maybe, maybe not... it depends on what you want... higher scores in bench?A shorter battery life?A very very hot device while browsing or gaming (if you run at 1.8Ghz for example)?A little extra power for some apps/games?
With overclocking a little (1.5/1.6Ghz) I noticied that some apps open a little faster and the genera UI is a little more responsive...
There is always a (little) risk to overclock our phones, generally due to overheat but also some CPU's can't handle high overclock.
For me I don't remember reading someone burn her CPU with overclocking but...
There are still some software protections before to burn a CPU (thermal throttling, CPU temp limit before shutdown, etc...).
Obiously the duration of life could be reduced mainly if you always run at 1.8Ghz with playing games... So the "safe" way would be no overclock or a little overclock like 1.5Ghz... For you to test and decide...
For the apps: SetCpu, System Tuner... there is a bunch on the Play Store.Just for the CPU settings I would say SetCpu.
For me i will never overclock my cpu. Just install siyah kernel and it's pretty smooth in games. Overclocking will damage your cpu and maybe loose some of the performance.
I can't see the need on this device, I might experiment with uv, maybe even underclocking, but as above, super smooth on siyah, and Slim Rom
Sent from my GT-I9300 using xda premium
Talking about battery life i installed darkys rom 3 onto my i9300 and the battery life is already suffering a loss of maybe around 25%. In saying that over clocking will only cause me to lose even more so ill leave it for now
Sent from my GT-I9300 using xda app-developers app
I'm too running on slim ics and siyah kernel. Best battery life and performance!
GGSunny12 said:
For me i will never overclock my cpu. Just install siyah kernel and it's pretty smooth in games. Overclocking will damage your cpu and maybe loose some of the performance.
Click to expand...
Click to collapse
Overclocking won't damage your CPU unless you set crazy voltages, or let it overheat. Also, it won't lose performance... that's crazy talk. Only if it overheats will it throttle, but that only happens on large clock rates like 1.8GHz or if you're in a hot environment.
I had my old LG GT540 overclocked with no heat problems mind that was only a 600mhz cpu, had it up to 825mhz.
But we already have a powerful cpu in this phone, foe now I don't see the need to overclock.
Sent from my GT-I9300 using xda premium
The best app depends a lot on your kernel and device. For example, for my Galaxy S2 the best OC was with TegraK Overclock.
With my Xoom CPU Tuner is still the best.
With the S3 I suppose CPU tuner would be alright as well, but I haven't had the urge to OC it, because I find SiyahKernel still quite unstable in the S3.
You need an overclockable kernel in order to OC your phone.
As for damages, it is hard to tell if they are permanent, but picture this: your battery will have to be recharged more often, because it will drain faster. Since batteries have a limited lifespan which depends on how many charge cycles they go through, the more often you discharge/charge them, the shorter their lifespan will be.
Also, there is no telling what kind of ill-effects the added heat can do to the phone. It may be totally harmless, but it may also affect the quality of the display, since the added heat will be right underneath the screen.
The lifespan of the CPU will be shortened: instead of being able to work well for 20 years, it will work well for 18, 17, 15, but more than enough time for us to already have replaced our S3 for organic, intradermal smartphones!