Hi currently I'm using latest version of coredroid and my
question now is is there a limit on how much I can
overclock my desire hd
Thanks for all answers
It depends, some people's phones can handle a lot of oc and some peoples phone can only handle it up to a certain point...it's all about testing it out. Also, oc isn't always good for your phone....should read about it before doing so if u don't want to 'damage' your phone! However I have been ocing since I got my dhd and haven't had any problems
Sent from my HTC Desire HD using xda premium
Thanks
Sent from my Desire HD using xda premium
I've been overclocking my DHD to 1.15ghz from the default of 1ghz for several months to no ill effects.
I might give 1.3ghz a go in the last year of my contract with my carrier when it doesn't really matter and can trade up.
I've been overclocking at 1.3Ghz for the last 3 months with no ill effects, and pretty zippy!
I've pushed it farther up to 1.8Ghz but didn't really see much performance gains, and ended up with a few freezes at times.
i've ran Quadrant at 2.0ghz...no probs, but that was only once I tried.
My phone been running at 1.2ghz now for months, with zero problem.
Matt
runs steadaly at 1.2ghz, but the Hz might not say everything since many custom roms undervolts and stuff like that,
1.15-1.2 is max for me, the performancegain of going higher was none for me, that i felt, not saw on numbers on quadrant. which of course was better.
1.4 was steady, and 1.6 it started freezing for a couple of seconds, but that might be because i was downloading torrents at the same time, and wanted to see if i could increase the write speed to the sd-card.
Related
I bet everyone has heard of the droid 2 and X being overclocked to crazy speeds right? Well... how come the Incredible hasn't reached those speeds?!?! Im sure some awesome dev could probably achieve this! There are many Inc owners who would like... scratch that... LOVE this speed increase, and im sure they wouldn't mind donating to the truly amazing dev who does this. Now the question is... whose willing to do it?
Sent from my ADR6300 using XDA App
The problem is that our phones can't handle those speeds mine cant handle anything over 1.113
Sent from my Incredible using XDA App
Gahh Its Lee said:
The problem is that our phones can't handle those speeds mine cant handle anything over 1.113
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That doesn't mean we can't try! Lol
Sent from my ADR6300 using XDA App
You could probably achieve this. Except you'd be buying another phone after your incredible spontaneously combusts from this kind of overclocking. Motorola phones use a different line of processors, OMAP from Texas Instruments rather than the Snapdragons.
then why with D2 or X's is that possible?
Because the Droid 2 and X use completely different processors made by completely different companies. We have a Qualcomm Snapdragon they have Texas Instruments OMAP.
No, see. Those speeds are fake. There's no way a mobile processor with today's technology could handle speeds of 2GHz or higher. 1.6Ghz is the highest I've seen on the X/2, and it wasn't very stable. That's why these "overclock apps" for the Droid X/2 only have options for 1.4GHz max.
Fake... plain and simple... you can't even overclock a PC processor 1.5ghz above its stock speed without some serious cooling. You really believe that a phone, with no fan/water/cooling of any kind can do it?
I am not a dev but my first degree was in engineering 20years ago. So when I say that its extremely unlikely that any of the massive OC stories are true I am talking from knowledge of engineering processes. 30-40% OC seems to be in the realm of reality. Beyond that, you enter the land of the bovine excrement.
First of all, as an engineer you simply do not design these chips with that much OC'ing being possible. Up to 40% OC seems possible - I would actually predict that some time in the near future we will be able to run the chips in the inc at 1.3 - stable. Expecting anything more is silly. If it was possible to run them at those speeds, guess what, they would have released them as 1.5 or 2 GHz chips.
Secondly, even if you were to temporarily be able to run them at substantially higher frequencies than what we can see them get to right now, they would be extremely unstable and would run hot very quickly. Thats too big a risk to take. In the best case scenario, you will just have a bricked device - replacing which will cost you $500-600. In the worst case, you will burn your hand and/or your face.
I would recommend that the OP volunteers his money, device(s), body and brains towards finding just how far we can OC an incredible. In the meantime I am happy to sit on the sidelines and implement solutions which are more logical and less quixotic.
wow LOL sounds cool to me just wondering, thank you!
IMO, Over clocking is over rated. You end up with reboots, crashes, and an unreliable phone.
I see a lot of people more concerned with quadrant scores than good battery life. Some of them expect both. I for one think the incredible is fast enough already, especially coming from a storm 1.
Sent from my ADR6300 running Virtuous 3.1.0, v4 kernel, using Tapatalk Pro.
To be honest i do notice a little bit of a speedup when I had mine overclocked to 1.15. But of course less battery life is a trade off with that. I am running the newest HTC stock kernel, no OC, and am very happy with battery life and speed. The phone would absolutely FLY with an OC of 1.5ghz or higher. But as someone said, if it was made to do that, they would have just put a 1.5ghz chip in there to begin with.
Hey all, I want to get some info on the limitations of our processor, mainly is their a ceiling on how high we can overclock our Evo's?
I am sure most of us here are familiar with the insanely fast 1.3ghz-1.8ghz(I think the top I read was 1.8ghz) speeds some newer phones are getting clocked to, the only thing that caught my eye about these speeds is that they are reported stable & usable. Coming from a Hero(a while ago) that I had to overclock to my Evo that is not really necessary to overclock was nice, BUT it would be awesome to have an Evo clocked at 1.5ghz-1.8ghz and stable as well as usable, is this even remotely doable? If not what is causing the limitation? Just curious
Edit: HAPPY THANKSGIVING, I am very thankful for my wife & kids as well as all you great guys and gals here at XDA!
Sent from my White Evo 4G
It all depends on your phone....what may run on yours may send mine into random reboot...I found mine is stable at 1.13
You may want to raise the bar a little at a time to see what you can handle....be sure not to have it set on boot till you are sure your phone can handle it....
Sent from my froyo using the xda app
matthewjulian said:
Hey all, I want to get some info on the limitations of our processor, mainly is their a ceiling on how high we can overclock our Evo's?
I am sure most of us here are familiar with the insanely fast 1.3ghz-1.8ghz(I think the top I read was 1.8ghz) speeds some newer phones are getting clocked to, the only thing that caught my eye about these speeds is that they are reported stable & usable. Coming from a Hero(a while ago) that I had to overclock to my Evo that is not really necessary to overclock was nice, BUT it would be awesome to have an Evo clocked at 1.5ghz-1.8ghz and stable as well as usable, is this even remotely doable? If not what is causing the limitation? Just curious
Edit: HAPPY THANKSGIVING, I am very thankful for my wife & kids as well as all you great guys and gals here at XDA!
Sent from my White Evo 4G
Click to expand...
Click to collapse
not exactly sure how it works on the phones but if its anything like a pc processor then it would take a kernel that can tweek voltages right like to get a 1.8 on our ever i would say it would need about a 3 step down uv but not sure if it would be stable heck at 3 step down uv it shouldn't boot unless its set oc'd on splash boot I'm pretty sure since our proc. are first gen snapdragons and the one's in the G2 and myTouch 4G are second with a smaller die ours won't be able to make it that far up with out major modification
Hmmm......so if I were to get off my ass and learn to compile a kernel I could at least attempt it, good info, thanks! At least now I have a place to start researching, I think I would be happy with a bump to an even 1.5ghz if it were stable, well if anyone else has more info I'm all ears!
Sent from my White Evo 4G
I got mine at 1.15 anything past that seems unstable 1.2/1.25 reboots automatically (cm7 nightly 88)
The FroYo kernels come unlocked to 1190 I believe. When I was running FroYo I ran 1152 all the time. You don't really need to compile your own kernel unless you really want to. All of the kernels available here are unlocked except for the stock kernels. Also 1190 was about the limit for most EVOs.
I don't have an evo, but I do have a snapdragon, use quadrant to check scores after an overclock. 1190 isn't so good. Makes lower scores than the stock 1ghz. Fsb bottlenecks at that speed, but gets a boost at 1530. I've had my snapdragon around 1600 stable all day. Low battery life though.
Sent from my HTC HD2 using XDA Premium App
The hd2 can go up to 1.5ghz I know so why can't the desire, you may ask 'why does it need to get faster its fast anyway ' well that's because I want to see how far it can go. ages ago our kernels were going up to 1.3ghz and surprisingly it was stable for me. Any answers
Sent from my HTC Desire using XDA App
DHD has a different processor
What? He is not even mentioning Desire HD, only HD2, which has an identical chip.
My fault, swear it said DHD!
EddyOS said:
My fault, swear it said DHD!
Click to expand...
Click to collapse
lol shouldve went to specsavers
Lol yeah , but seriously any idea
Sent from my HTC Desire using XDA App
No cpu is the same, even if its the same model, one person may be able to oc theres to 1.5 ghz. where as another may be only able to oc theres to 1.1 ghz. someone on another forum oc'd there droid x to 2.5ghz lol
Sent from my Desire HD using Tapatalk
AndroHero said:
No cpu is the same, even if its the same model, one person may be able to oc theres to 1.5 ghz. where as another may be only able to oc theres to 1.1 ghz. someone on another forum oc'd there droid x to 2.5ghz lol
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
This is very true not only that there is the stresses that your ROM and apps are taking on the CPU some will be OC'd to be extremely fast but never actually use that amount of CPU speed so will always be stable however some users will take theirs to the limit and will only remain stable at much less CPU speed.
It's pretty much the same with all processors but who really wants to fry their processor just checking how fast they can make it run. If 1.3Ghz is stable for you then that's all good bump it up yourself once your cpu burns out you know it can't go that fast
warlordxxx said:
This is very true not only that there is the stresses that your ROM and apps are taking on the CPU some will be OC'd to be extremely fast but never actually use that amount of CPU speed so will always be stable however some users will take theirs to the limit and will only remain stable at much less CPU speed.
It's pretty much the same with all processors but who really wants to fry their processor just checking how fast they can make it run. If 1.3Ghz is stable for you then that's all good bump it up yourself once your cpu burns out you know it can't go that fast
Click to expand...
Click to collapse
+1 and if the op really wants to try it, why not throw a donation at a dev, get him to compile you a kernel that can be oc'd that much
Sent from my Desire HD using Tapatalk
998Mhz does me just fine on my Desire. I used to run 1.51Ghz on my DHD but all I got from it was an awesome Quadrant score and a piss poor battery life. For day to day use I really don't notice the difference from 998Mhz to 1190Mhz with a HAVS/BFS kernel on my Desire.
my amoled went up to 1300 and my wife slcd wont go over 1030(i menan it will but any stronger activity will crash it)
2.5ghz overclocked with a droid x?
how good was the battery life on that?
I think 998 MHZ is enough for my Desire. 1.5 GHZ is nothing to me.
Hi!
First of all, I have been reading around and I did not find exactly what I want to know.
Yesterday I managed to root my desire and flash the CM7 ROM (http://forum.xda-developers.com/showthread.php?t=957344). Today I've added a custom kernel, "vork" 720p (http://forum.xda-developers.com/showthread.php?t=782875&highlight=vork).
My quadrant score is still low (around 1100), even though the phone behaves much better than the stock.
I have 2 questions:
1. What can I do to make it perform even better? (i have a friend with a desire hd who just flashed a sense rom, without any added stuff and scores over 2200).
2. should i install a new "radio"? My gsm signal is much stronger than before as it is.
3. Since this is my first time, what do you think of my choices with the ROM and Kernel? I chose them because they were popular and i assumed they are well tested and function well.
Thank you for your time.
Desire HD has better processor and GPU I believe hence bigger difference. Your score is good for Desire. I got around that overclocked on LeeDroid GB ROM.
Sent from my HTC Desire using XDA App
why do you even care bout the quadrant score ? :X
if you really feel excited bout high numbers having nothing to do with ur phone performance, go with data2ext roms, quadrant gives them 3000+ points, but still they perform worse than, for example, LeeDroid.
then again, new GingerBread Sense 2.1 roms have low quadrant scores, but they are really really fast.
I dont really care about quadrant, but it seems like a valid tool for measuring performance. At least it seems that everyone is judging by that. Quite frankly the phone works very well, i am just out of ideas to make it even better. And if the scores are meaningless why do people use it?
Its probably one of those my d...ck is bigger than yours things. Anyway I used data to SD and I also had high scores but overall experience was very laggy and jerky
Sent from my HTC Desire using XDA App
Quadrant scores are mesaurable only when you launch them on stock, unrooted roms. then it can give you and idea on how this phone with this software will perform.
after rooting, some hacks or scripts make quadrant scores not real
So this means my phone is fine as it is? There is nothing more I can do to enhance it?
you can overclock it, it should all be said in your ROMs topic.
like "OC up to 1200Mhz" means you should be able to set processor speed to 1200mhz with SetCpu. it all depends on kernel i think
Ok, thanks everyone for your input! If there are any more suggestions, I dont mind.
I have a og evo I want to know why when I overclock to 1.2ghz it freezes my phone why does it do that ?
Sent from my Nocturnal 4G using xda premium
Each Evo is different. Some of them can't handle that high overclock, or can't be undervolted very low. Each one is different, each has its limits.
I don't understand the big deal with overclocking. It burns your battery faster. I personally underclock, with little to no lag and is good enough for my casual gaming needs
Mine doesn't like a clock much at all. I can get about 1.1 before it starts locking up but even then it hangs a lot. I honestly don't see a difference from 1.0 to 1.2. Get a decent rom, good kernel and try out the v6 script an I almost guarantee you will like that better.
beaumontcali48 said:
I have a og evo I want to know why when I overclock to 1.2ghz it freezes my phone why does it do that ?
Sent from my Nocturnal 4G using xda premium
Click to expand...
Click to collapse
Well for us to be able to help you, you would need to provide us with more details on how you are trying to accomplish this.
I use no frils cpu but have also tried setcpu and viperMOD I know that's the best way to overclock but is very confusing. Have any step by step instructions to of to 1.2 I know having higher voltages helps as well.
Sent from my Nocturnal 4G using xda premium
Sent from my Nocturnal 4G using xda premium
Overclocking is overrated. If you need to overclock for every day usage, then something is wrong - at least in my opinion. Resource intensive gaming is different, but you shouldn't need to overclock for browsing, texting, casual games, etc.
Try out the V6 Supercharger script. I'm not currently using it, but have in the past and it seemed to make my phone more snappy. A lot of people swear by it and it's a great script, definitely worth a shot. There are other things you can do to speed up your phone without overclocking. I'd try other options first since overclocking will chew through your battery. Increase the dalvik vm heap size, there are plenty of free apps on the market to help with this task. Uninstall apps you don't use, I'll bet that you never use some of the apps on your phone. Back them up with Titanium Backup and you can restore them if you ever need them again.
In case you didn't already know, the Evo can't overclock past 1.2, I'm not 100% sure why - it has something to do with the processor.
Supersonic Evo 4G | MIUI | Tapatalk
I never oc over 1075 and only when plugged in if i play a game I need to oc.for I just activate my charging profile and plug up and play 1.2 ghz is a good chance of doing serious.damage as these older scorpion processors get very very hot at that clock speed so they lock up to try and protect themselves from heat damage or they shut down the phone 1075 is as high as you should need to go for any games the evo can handle on the subpar gpu
Sent from my Classic-EViLizED-ToMAToFiED-EVo4g-
beaumontcali48 said:
...also tried setcpu and viperMOD I know that's the best way to overclock.
..
Click to expand...
Click to collapse
I'm pretty sure viperMOD is more for undervolting than overclocking, which are not suppose to be combined together. I am running vipermod with max voltages - 50. Other nite was playing snes9x and was getting some lag with a game so I bumped max CPU up to 1.2. Phone went into a bootloop and had to superwipe and reflash everything. Don't know if its b/c vipermod + 1.2 CPU or just bumping up CPU. Didn't try it again.
Support TrevE!!
shift
Get a shift. Mine runs fine at 1.9. But usually run it art 254-1200 on demand.
{ParanoiA} said:
I'm pretty sure viperMOD is more for undervolting than overclocking, which are not suppose to be combined together. I am running vipermod with max voltages - 50. Other nite was playing snes9x and was getting some lag with a game so I bumped max CPU up to 1.2. Phone went into a bootloop and had to superwipe and reflash everything. Don't know if its b/c vipermod + 1.2 CPU or just bumping up CPU. Didn't try it again.
Support TrevE!!
Click to expand...
Click to collapse
You can overclock and undervolt together just fine. You just need to ensure that every frequency has a high enough voltage to run the processor at that step. My Evo is overclocked and undervolted just fine, although IIRC I can only push it up to 1.1 GHz . My tablet is 1ghz to 1.6ghz and is undervolted as well, though.
merge rls 2.0, iron monkey, Droid overclock because of the profiles options. I set up four profiles including one for temp. sometimes i'm underclocking and sometimes overclocking but only up to 1.19 to prevent freeze and boot loops. Only downside is right at open Droid overclock needs su permission but that is my choice since profile changes at open.
Very snappy afterwards.
Sent from my PC36100 using XDA Premium App
When I had the 4G, I was never able to go above 1118, or somewhere around that. It would have freezing issues.
On my evo shift, I was able to do 1.7 gHz (compared to stock 800 mhz) ok. 1.6 pretty reliabily, and I could run 1.5 all day long. Some guys could do 1.9. It just depends on the phone.
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
tommy0823 said:
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Shoot the brutha a link
TrevE Supporter!
tommy0823 said:
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
What? Overclocking and undervolting are two completely different things, and they aren't mutually exclusive. Unless you can provide a good reason as to why it's counter productive to do both, I don't buy that at all. Just checked my phone, my overclock requires an extra 25 mV for all three steps I've overclocked. 25mV isnt much, and it certainly isn't going to kill my battery that much faster.
Besides, the only time the CPU is going to be entering these high power modes is when it needs to do work, and it's better to do work as fast as possible to go back to sleep. Would you rather wake up, do a mundane task for 5 minutes, then go back to sleep or wake up, do a task at 2x the speed while only consuming 30-50% more energy, then going back to sleep after only 2.5 minutes?
HUGI is real.
Sent from my Transformer TF101
Yea shot me the link too bro.
Sent from my PC36100 using xda premium
First let me say I don't use viper mod or any voltage controlling mod.
On sense 3.0 roms such as mikg I over clock to 1152 and set the minimum to 384 and its smooth as butter. No problem and battery lasts all day.
On aosp however such as decks (I'm on it now) I underclock to 499 and leave the min at 254. Smooth as always and battery lasts forever.
Anything past 1152 is going to cause problems (at least in my experience) also the rom/kernel can effect how much you can overclock.
Sent from my PC36100 using xda premium
Gary13579 said:
What? Overclocking and undervolting are two completely different things, and they aren't mutually exclusive. Unless you can provide a good reason as to why it's counter productive to do both, I don't buy that at all. Just checked my phone, my overclock requires an extra 25 mV for all three steps I've overclocked. 25mV isnt much, and it certainly isn't going to kill my battery that much faster.
Besides, the only time the CPU is going to be entering these high power modes is when it needs to do work, and it's better to do work as fast as possible to go back to sleep. Would you rather wake up, do a mundane task for 5 minutes, then go back to sleep or wake up, do a task at 2x the speed while only consuming 30-50% more energy, then going back to sleep after only 2.5 minutes?
HUGI is real.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Its counter productive because it is giving less to something that needs more. (Don't take this post as me trying to be a ****. Just voicing how someone explained it to me a while ago)
Think of this as cars.
Lets say you have a nice fancy v8 mustang. Stock, everything is well, balanced.
If you start adding parts and get it pushing out 1000 horsepower (overclock) your most likely gonna need more feul (voltage) or at least stock amount flowing into the engine just to keep it running.
Now lets say you got that same 1000 horsepower gas destroying mustang and you start to lower the amount of gas flowing into the engine (undervolt (done in vipermod)) cylinders (CPU) wont get enough gas, it wont work, and your stuck going no where.
So if that made sense (did to me) then you can see why they are counter productive. Unless your using vipermod to overvolt (which idk if you can since I don't use it) then you can disregard this whole post
Sent from my PC36100 using xda premium
Your car analogy is completely irrelevant. You can look up the exact voltages that the CPU runs on at every frequency, *even when overclocking*. Overclocking an Evo 1ghz to 1.2ghz takes maybe a 5% bump in voltage, and that 5% extra power is only going to be used *when the CPU is running at max speed* (which is only when there is a lot of work to do), and even then, it's *still better to let the CPU run at max speed with a tiny bit more power consumption than to cap the CPU at a slower speed and make it work for even longer*. Intel calls it HUGI, Hurry Up and Get Idle.
I know what I'm talking about, and I wish people would stop trying to argue with me based off of second hand speculation. I do this for a living, after all. There is absolutely nothing wrong with overclocking and undervolting, and it's the best way to get the most battery life *and* performance out of your phone, period.
Sent from my Transformer TF101
Gary13579 said:
Your car analogy is completely irrelevant. You can look up the exact voltages that the CPU runs on at every frequency, *even when overclocking*. Overclocking an Evo 1ghz to 1.2ghz takes maybe a 5% bump in voltage, and that 5% extra power is only going to be used *when the CPU is running at max speed* (which is only when there is a lot of work to do), and even then, it's *still better to let the CPU run at max speed with a tiny bit more power consumption than to cap the CPU at a slower speed and make it work for even longer*. Intel calls it HUGI, Hurry Up and Get Idle.
I know what I'm talking about, and I wish people would stop trying to argue with me based off of second hand speculation. I do this for a living, after all. There is absolutely nothing wrong with overclocking and undervolting, and it's the best way to get the most battery life *and* performance out of your phone, period.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Hmm, *interesting*. I believe the best answer to the OP was covered rather well earlier. It's all about your rom/kernel/hardware combination. With all the variables to consider as relevant, your best bet is to experiment and find what works for your device. Don't check set on boot untill you are confident the set-up is stable. Higher is not always better with overclocking. My device runs blazingly well underclocked @768max. Gets insanely great battery @499max. However my quadrants are better @ 1036 than at 1190.
Great thing about android is you can experiment and learn through trial and error.
Sent from my PC36100 using xda premium