Related
I have read many times that people overclock their device and make it faster, how its been done and what's the pro's and con's?
Thanks
pro:
well doh! speed
con:
short batt life
instablity
it dont make flash and sdcard or screen refresh any faster and in many cases the cpu is not really a bottleneck
Rudegar said:
pro:
well doh! speed
con:
short batt life
instablity
it dont make flash and sdcard or screen refresh any faster and in many cases the cpu is not really a bottleneck
Click to expand...
Click to collapse
Thanks for your post!
But how they do that?
Changing some components? And what's the cost roughly?
Thanks
do what ?
people dont overclock anything but their cpu
my point is that for some tasks it dont help to have a faster cpu
You might want to try Search which will allow you to find all the information you require, including the Omapoverclock app.
Hi guys!
I haven't yet rooted my Desire(I would have but I was fool enough to install the 2.2 OTA).The main reason for me to root would be the ability to overclock my device.All this time that I have been around here on the Desire and Nexus One forums I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.However,to my great surprise,I noticed on OpenDesire ROM's thread that the Desire can be overclocked @1344MHz(which of course made me think a big HELL YEAH!).Is that number ok for all of us or for some select few?I remember from my Hero days that only some few,lucky guys like myself could overclock up to 768MHz,although there were cases of people,rare,yet not unheard of,that could overclock @844MHz.Is this the case here or are things different with the Snapdragon?
Many many thanks guys!
C'mon guys,no one?
tolis626 said:
I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.
Click to expand...
Click to collapse
I don't think overclocking to 1267MHz happens in rare cases. I had no problems oc-ing to 1267 and it seems that a lot of forum member were able to do this too.
Why don't you downgrade your HBoot to 0.80, root your phone and try it out?
Just make sure your phone does not become too hot if you try 1344MHz.
I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave
foxmeister said:
I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave
Click to expand...
Click to collapse
so this, its really not needed at all. a decent fast rom and 1ghz is more than enought for things to be super speedy. any decent kernal will provide more than enough speed.
overclocking(and lots of other things these days!) reminds me of that bit in jurassic park where they are all sat around the table and geoff goldblum says:
"Yeah, but your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should".
herein lies the lesson, just because you can do it doesnt mean you should do it.
Well,I have my reasons wanting to overclock...First off,I will check if I can see any difference in speed or smoothness.If there isn't,I will just revert the clock back to normal after some benchmarks.
I just am the kind of guy that wants to get the most out of his phone!
I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.
sbdags said:
I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.
Click to expand...
Click to collapse
That's what I'm talkin' about man!
And now that I think of it,it's not that much.I mean,the Hero could overclock @768,which is 45% overclocking.The Desire's 1267 is about 27% and 1344 is about 34,5%.Nothing too much!So why not?
Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.
Kinma said:
Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.
Click to expand...
Click to collapse
Well my man,in this case the MSM7200A is no beast but rather a pooch that barks to no avail!Good pet however!
Joking aside,the Snapdragon is a beast for a mobile phone,but even beasts get beaten.Now,if I can somehow reach or even get close to the performance of the Galaxy S or the Droid X I'll be happy.Software wise I believe that HTC is far superior ,but it's hardware is a little out of date.Let's see what their new devices will do for us!
Btw,does anyone know if the so anticipated HTC Ace will be anything better than what we already have or if it will be the Evo for GSM users?
Thanks!
The desire is plenty fast as it is and I don't see the point of overclocking it. I've had it to 1267 in the past and it made no difference at all for usability. I'm also the type that overclocks all his computers...
Sent from my HTC Desire using Tapatalk
Personal preferences dude...What everyone does with their phone is their own business.I wish I could resist overclocking too!
However,I was watching a thread over at the N1 forums in which a dude named Storm9999(genius dude,not just a random one) stated that an overclock @1,3GHz could fry our phones.Is that so?I mean,I know overclocking reduces the CPU's lifetime,but is it THAT MUCH dangerous?
I think overclocking can kill your phone.. I use to overclock my own o2 orbit and it died after a year..
Friend of mine just burned his old HTC by overclocking it and as a consequence is going to buy a desire.
I had my phone overclocked at 1345Mhz for a moment, just to test it, and it made no real difference to when it was overclocked at around 1.2Ghz, which in turn has very very little difference to stock 1Ghz.
I think the only case where you see some small impact is in games.
I've tested HD recording at 1.345 Ghz and stock speed and there was no difference.
If anything, it's going to kill your battery and shorten its life for sure, going so high. If ever I will OC again I won't go over 1.1 and only if I find some tangible improvements.
As said, this phone is always fast, there is no real need to OC, other than for 'fun'.
The fun is what I want...Well,most probably I will have my phone overclocked at the maximum speed it can get for about a week or two and then go back to 1 or 1,1GHz...
Btw,your signature kicks ass andycted!
Hello!
So, I have a DHD with the Revolution HD ROM (2.0.8) and the Buzz Sense kernel. I have locked the CPU to min/max 1516MHz Perf. scaling and, upon running the AnTutu System Review 1.2("System Benchmark" under Market) I get a score of 1879.
Yet in the Rankings I see that the #2 device is a DHD with 2.2 @1516MHz with a whopping score of 2774!!!!!
So, how could I reach those heights? The only thing I can think of is the slow SD card that came with the mobile (read/write scores: 34/117), but other than that what could be holding me back?
Cheers
T
I have reached pretty high scores while testing, but then the overall rom smoothness has pretty much sucked. It is normal that synthetic benchmarks give lower results when you use a custom rom, the optimizations that ensure general smoothness and usability cause it. One big reason is CPU scheduling, in custom rom (custom kernel) cpu time is divided for each task in a different way, thus reducing the overall benchmark score.
jkoljo said:
I have reached pretty high scores while testing, but then the overall rom smoothness has pretty much sucked. It is normal that synthetic benchmarks give lower results when you use a custom rom, the optimizations that ensure general smoothness and usability cause it. One big reason is CPU scheduling, in custom rom (custom kernel) cpu time is divided for each task in a different way, thus reducing the overall benchmark score.
Click to expand...
Click to collapse
Aha... but then this means that this or the other ROM do not let a specific app (say, a heavy 3D game) take the phone to its full potential...
Incorrect, it is just the synthetic benchmark that suffers. Games will run fine, faster than stock.
Jkoljo's right.The overall system speed is much better,performance is better,but it sucks a little in benchmarks.If you are so desperate to see high benchmark scores(I was once too! )try kamma's 1.4 kernel.Quadrant 3200.Need I say more?
tolis626 said:
Jkoljo's right.The overall system speed is much better,performance is better,but it sucks a little in benchmarks.If you are so desperate to see high benchmark scores(I was once too! )try kamma's 1.4 kernel.Quadrant 3200.Need I say more?
Click to expand...
Click to collapse
Really? 3200? Wow. Just out of curiosity, what scores are you getting with other kernels?
Well, at the end of the day, it doesn't matter - I haven't seen an app or game that runs slow or choppy or whatever. It's just for the heck of it
krakout said:
Really? 3200? Wow. Just out of curiosity, what scores are you getting with other kernels?
Well, at the end of the day, it doesn't matter - I haven't seen an app or game that runs slow or choppy or whatever. It's just for the heck of it
Click to expand...
Click to collapse
Oh yeah,I know what tou mean!
Anyway,with Lee's and Apache's kernels I get about 2500-2600 in Quadrant.CPU clocked all the way up to 1.5 GHz of course!
Are there any bad things that can pop out if phone is OCed to 768MHz? Does it last shorter, can it screw battery etc..?
Thanks
It's unlikely you will 'pop out' something at 768 MHz. Some Wildfire's will not be stable at that speed, and, that is about the worst it can get, in which case, your Wildfire will lag a lot,and you will have to tone down the frequency a bit.
Battery life may take a hit, but, it wont be anything drastic again, also, as for component life, again, it may take a hit, but, even at 768, it will last till the time you are ready to retire it.
what is the recommended overclock speed, i can overclock to 729mhz and its stable no reboots etc or should i overclock to 691mhz??
Not really necessary, if your phone is not behaving abnormally at 729.
Is the difference with overclocking really that noticeable compared to stock speeds?
It's marginal. Definitely not as much as the overclock %age suggests. The only big difference will be in benchmarks.
3xeno said:
It's marginal. Definitely not as much as the overclock %age suggests. The only big difference will be in benchmarks.
Click to expand...
Click to collapse
i just overclocked to 729MHZ its awesome, the speed is noticable , and its stable i hope its fine and doesn't take more battery life lol
got mine at 710mhz and its stable no problems at all
keep the max overclock value at 729 MHz and the minimum on at least 264 MHz.
This saves battery when phone isn't in use and the speed increase is noticeable, it's rather nippy! (certainly for texting anyway)
------------------------------------------------------------------
Device: HTC Wildfire, 16GB Kingston micro SD
ROM: CM7
Recovery: CWM
Status: Overclocked @ 726 MHz - stable
Curious if overclocking the CPU and GPU is really worth it looking at performance vs battery life. My device seems zippy already, but I'm just wondering if overclocking would improve anything seeing as some other tablets are moving onto 2.0+GHz.
If so, what kernel would you recommend me to use?
I would not overclock it, if you think it is very fast already. Overclocking from 1.5GHz to 2+GHz is probably mostly used for people trying to get the highest benchmark score.
i used to test roms and over clock the kernels while testing now iam back to basics
as i noticed even with a small overclock the system got hot around camera area on most kernels
that was enough for me to stop oclocking