• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root My droid hates me, will not go over 1000mhz.

ZXMustang

Android Enthusiast
Apr 15, 2010
330
10
Earth
I dont know what it is, but my droid will NOT run at all on anything over 1000mhz. It just locks up almost instantly. Im lucky I didnt check set on boot. Otherwise I would have to reload my last backup. Its super stable at 1ghz, but anything over that its turns into a brick. It also ONLY works at all overclocked with the P3 kernels. I have tried the low voltage and the standard voltage. All the same results. Anyone else have this happening?
 
Im actually on the P3 standard 1250 kernel right now, and it literally locks up solid 5 seconds after I exit setcpu. I tried 1100mhz and it seems to be running ok, but getting really hot right now. I have a droid incredible coming from verizon next week, and I cant wait to see what the snap dragon can do when overclocked. I'll bet it will make it to 1600mhz.
 
Upvote 0
Same here...1GHz has been my max on any kernel I've tried. But it's not like that's slow or anything. :)
Oh and for shits, I went to a local verizon store and got to play with an incredible. I downloaded the CPU benchmark program free version from the market, and it said the incredible was 998mhz and it benchmarked 1145ms, compared to my droid at 1000mhz which ran the test at 850ms. Nice huh? This was not quadrant btw.
 
Upvote 0
I cant wait to see what the snap dragon can do when overclocked. I'll bet it will make it to 1600mhz.

I can tell you exactly. Not many people have been able to get it past 1.26 GHz. No 65nm processor (be it snapdragon or omap3) will reach 1.6GHz.

The fact of the matter is, Snapdragon is already pushing the limits of 65nm tech. That's why the N1 that first reached 1.26GHz is dubbed the JP1 "Jesus Phone 1". LOL.

Oh and for shits, I went to a local verizon store and got to play with an incredible. I downloaded the CPU benchmark program free version from the market, and it said the incredible was 998mhz and it benchmarked 1145ms, compared to my droid at 1000mhz which ran the test at 850ms. Nice huh? This was not quadrant btw.

And a little more Snapdragon bashing (sorry, but it must be done. Snapdragon is the worst hype word introduced in recent memory)...that's because clock for clock, the Snapdragon does not perform as well as the OMAP3 -- So a ~800MHz OMAP3 will match the performance of the 1GHz Snapdragon.



...And for your original concerns, not all Droids were created equal. Some people can clock to 1.3GHz+, and others can barely do 1GHz.
 
Upvote 0
I dont know what it is, but my droid will NOT run at all on anything over 1000mhz. It just locks up almost instantly. Im lucky I didnt check set on boot. Otherwise I would have to reload my last backup. Its super stable at 1ghz, but anything over that its turns into a brick. It also ONLY works at all overclocked with the P3 kernels. I have tried the low voltage and the standard voltage. All the same results. Anyone else have this happening?

In the interest of keeping this on topic, I'll stick to CPU analogies.

I have an Intel Core2Quad Q6600 - one of the better OCing CPUs out three in terms of what it can achieve versus what it started with. It's little brother is the gamer's Paradise CPU since it only has 2 cores and OCs even better (4 GHz is not unheard of in the little bro E8600 series), but this quad can easily OC to ~3.6 GHz or better.

I say can, b/c the one I have at home will never get stable beyond 3.375, and even then is quirky - but runs 3.215 solid. It's not heat, even when I can get temp readings on 3.375 they are well below 62 deg C under load, so I have plenty of room to spare, it's not voltage (750 W PSU, more than ample for my system, all rails checked accordingly for actual power output) and it's not the RAM (RAM easily does 1200 plus, though being sold as 1000 MHz RAM).

It is simply the processor - it has a wall - if I were to go out and buy another Q6600 I may have better luck and get one that I can hit 3.8 on without over stressing the environment too much (especially if I H2O cooled)>

My point is that these things are mass produced - and there is no way to guarantee that just because DROID A can do 1.3 GHz that all DROIDs can do the same.

Some will do no more than 1000, some no more than 1100, some no more than 1200, and some may even break 1300.

2 major things to take away from this lesson:

1) Electronics are never 100% equal. Even if built by hand, and especially not if mass produced.

2) The Quad Core I referenced above in my example comes stock at 2.4 - 3.6 is pretty damned good, and it only represents a 50% OC. Our OMAPs, OTOH, are default 600 MHz processors (that are underclocked by Motorola to stock at 550). I am currently running at 1.2 GHz stable - that is a 118% OC (from stock, 100% OC for the actual clock of the processor itself). You can't shake a stick at that. Show my a computer CPU that you can achieve 100% OC - haven't seen one (if at all) in a very very long time.

Even at 1000 MHz, you're achieving and 81% OC. So feel good about the fact that your processor can OC that easily - the SnapDragon ain't gonna ever be able to OC that easily, and *plus* the OMAP has a better onboard GPU to boot.
 
Upvote 0
You know, the reason for variations between CPUs is because different models within a series are all produced in one shot.

Example: I have a Core 2 Duo E6300. This came from a batch of Intel Core 2 Duos, but Intel didn't know that the processor was going to become an E6300. They simply produce the processor and then keep clocking it higher and higher and see when it stops being stable.

Now, the only difference between an E6300 and an E6400 are that the E6300 is shipped at 1.86GHz and the E6400 is shipped at 2.13GHz. So my processor could have been an E6400 instead if Intel felt it could stay stable at 2.13GHz (the fact that I have it overclocked at 3GHz right now is irrelevant; they allow for a LOT of wiggle room at the factory because most people let their CPUs get all dusty and don't give it proper ventilation).

tl;dr version: Droids that can overclock higher just have CPUs that barely managed to squeeze into the series of CPUs that are used in the Droid, as opposed to being marketed as one from the next higher model of CPUs.
 
Upvote 0
Well, binning, as they call it, also plays a role, sort of what you described, but more so...but yeah, what you are writing is essentially true.

Initially, CPUs are made with set specs, then there is binning - if they make a whole slew of 6000 series CPUs, they'll make them all able to be capable to run at ht highest the 6000 series can - and then under-clock them as needed for shipping out to the really realy real world.
 
Upvote 0
...And for your original concerns, not all Droids were created equal. Some people can clock to 1.3GHz+, and others can barely do 1GHz.

The P3 kernels work well on my Droid. However, in the recent past, I've tried 1.3Ghz and found that my Droid won't even boot up overclocked that high... we're talking boot loop city at 1.3.

When I tried P3, I installed the 1.25Ghz and did not expect it to function, but to my surprise it was very stable. Amazing that such a small difference in clock speed can make a Droid unusable.

By the way Fab, I'm using the 1.25Ghz P3 with yours and Pete's NexBeast, and I can't imagine how even the DroidX (much less the Incredible) could beat it. My Droid is as snappy as can be.
 
Upvote 0
Just to add, though mine seems to handle 1.2GHz, I can't really say I've noticed much of a difference when clocked that high. So far as feel goes, anything above 800MHz seems fine enough, so I've come to settle at 1GHz, running the P3 kernel. Its plenty snappy and stable, while getting appropriate battery life for my uses...can't argue with that.
 
Upvote 0
Mine won't go over 1100 stable. Never has, no matter which kernel I use, and I've tried a LOT of them with a lot of different ROMs and OS versions. If I'm using a LV kernel (which I can't stand - because my phone hates them), then I'm lucky to get to 900 without freezing or rebooting issues.

OP - if your phone is anything like mine, which it sounds like it may be, try out Chevy's MV kernel. I have it running perfectly and the phone runs a hell of a lot smoother and faster than with the P3 kernel I was using before. Personally I don't like the P3 kernels. They do not cooperate with my phone. Lots of bugs, glitches and speed problems.
 
Upvote 0
The P3 kernels work well on my Droid. However, in the recent past, I've tried 1.3Ghz and found that my Droid won't even boot up overclocked that high... we're talking boot loop city at 1.3.

When I tried P3, I installed the 1.25Ghz and did not expect it to function, but to my surprise it was very stable. Amazing that such a small difference in clock speed can make a Droid unusable.

By the way Fab, I'm using the 1.25Ghz P3 with yours and Pete's NexBeast, and I can't imagine how even the DroidX (much less the Incredible) could beat it. My Droid is as snappy as can be.

I was in the same boat; back when we were making the transition from 2.0.1 to 2.1 (instead of from 2.1 to 2.2), Chevy's 1.3GHz kernel was disgustingly unstable for me if I tried to use the 1.3GHz setting but 1.25GHz ran like a charm.

P3's kernels tend to only work up to 1.2GHz for me. Bekit's kernels never work for me. It's just amazing how differently different phones react to the same kernels. I have no idea why, it just happens. :thinking:
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones