Show off your OverClocking Numbers Here!

Honestly, I only put it on for Quadrant to see what it could do. I turn it off once I'm done.
 
snap20110115_212609.png

Overclocked to 1.3 ghz.
 
Ok I'm a chump, I was wrong and I'm sorry for being a ****. I can't believe the numbers I'm getting with liberty.

Once again I'm sorry and wow
 
Last edited:
Woot! You belieeeevvvee! Now go hug a sailor :)

I'm getting lower scores with Liberty. The toolbox Is the only thing I can think of that's making it slower. May wipe and reflash because Darkslide was wicked fast.
 
Woot! You belieeeevvvee! Now go hug a sailor :)

I'm getting lower scores with Liberty. The toolbox Is the only thing I can think of that's making it slower. May wipe and reflash because Darkslide was wicked fast.
Who cares about Quadrant scores? The real measure is practical speed during normal use.
 
Who cares about Quadrant scores? The real measure is practical speed during normal use.

Its a benchmark used to get an idea of speed and performance in a quick easy tool. Testing practical speed during normal use generally takes longer testing doing various tasks that mimic many features of a benchmark test anyways. And what ever tasks used varies between users and apps installed/used.

Its also nice to use after changing frequencies, voltages, a new ROM or other performance changes as a type of stress test and to make sure that any changes not only take effect but are effective (at least in a quick benchmark test).

Its also hard to show a screen shot of measurements of performance taken during normal use. This thread is to show off your OC numbers. As the various OC apps make getting to 1.45ghz easy and most everyone can do it whats the point of showing your OC numbers when a quadrant or linpack is a quick easy graph or numerical value that better represents a machines speed?
 
I must insert my foot in my mouth

So I tried it with stagefright once after I installed Liberty and achieved the insane numbers others have posted, after that I wanted to see what Liberty could do on its own so I tried to turn stagefright off, I think I did and I did more than once, and I am still getting crazy numbers.

FYI it goes from left to right starting with 1 GHZ undervolt all the way to 1.45 GHZ, I was using DX/D2 Overlclock
 
Its a benchmark used to get an idea of speed and performance in a quick easy tool. Testing practical speed during normal use generally takes longer testing doing various tasks that mimic many features of a benchmark test anyways. And what ever tasks used varies between users and apps installed/used.

Its also nice to use after changing frequencies, voltages, a new ROM or other performance changes as a type of stress test and to make sure that any changes not only take effect but are effective (at least in a quick benchmark test).

Its also hard to show a screen shot of measurements of performance taken during normal use. This thread is to show off your OC numbers. As the various OC apps make getting to 1.45ghz easy and most everyone can do it whats the point of showing your OC numbers when a quadrant or linpack is a quick easy graph or numerical value that better represents a machines speed?
Do a quick Google search to see how unreliable Quadrant really is. It's marginally helpful at best. Checking your OC numbers is about as useful as comparing horsepower between cars; sure, one may have more, but that doesn't determine how fast it is.
 
Do a quick Google search to see how unreliable Quadrant really is. It's marginally helpful at best. Checking your OC numbers is about as useful as comparing horsepower between cars; sure, one may have more, but that doesn't determine how fast it is.

If it were so bad then why is it that sites like androidcentral use it to test new phones all the time? It may not be perfect but it gives a good base understanding of the power and speed of the device.
 
If it were so bad then why is it that sites like androidcentral use it to test new phones all the time? It may not be perfect but it gives a good base understanding of the power and speed of the device.
Because there's no other method of direct comparison between devices. And (if you haven't noticed) techies have a hard on for numbers. I'm not saying it's completely useless, but it's not the end-all-be-all standard of performance. I can honestly tell you that I've noticed absolutely zero practical speed difference between when my phones scores 2500 or 1900 in Quadrant.

The only time Quadrant has ever shown me anything is when I've clocked at either extreme, but then I already knew how fast/slow the phone was because I was using it as well.

And Quadrant scores can be manipulated (like enabling Stagefright, which essentially offers no practical benefit for everyday use).

Anyway, look at it how you want.
 
snap20100608_042254.png

Droid 1 a year ago...really? YES! I can't believe how little has changed...
 
I'm interested in overclocking my X but have a few questions. First, I'm running stock 2.2.1 rooted with z4. I am currently not interested in doing any custom ROMs. I've seen a few different apps mentioned for doing this including jrummy16's Droid Overclock, Unstable Apps' DX/D2 Overclocker and SetCPU.

I have previously seen more good feedback for jrummy16's app than the rest, at least specifically for use with the Droid X, but on the market there are recent comments from people saying they are getting stuck in boot loops etc. when using stock 2.2.1.

I'm basically looking for the safest way to do a slight overclock (maybe 1.1 to 1.2ghz?) and possibly set up some low voltage settings for extended battery life.

Where do I start?
 
I'm interested in overclocking my X but have a few questions. First, I'm running stock 2.2.1 rooted with z4. I am currently not interested in doing any custom ROMs. I've seen a few different apps mentioned for doing this including jrummy16's Droid Overclock, Unstable Apps' DX/D2 Overclocker and SetCPU.

I have previously seen more good feedback for jrummy16's app than the rest, at least specifically for use with the Droid X, but on the market there are recent comments from people saying they are getting stuck in boot loops etc. when using stock 2.2.1.

I'm basically looking for the safest way to do a slight overclock (maybe 1.1 to 1.2ghz?) and possibly set up some low voltage settings for extended battery life.

Where do I start?

Jrummys app should be all you need. Quickclock has become another preffered OC app that can quickly determine lowest VSEL and max ghz. These values can be exported to jrummys app now too.

For battery life the undervolting will probably be your best bet. Use the profiles to lower frequency when screen is off to save battery, and check out juice defender or use the battery saving option in the battery manager. Essentially find a way to turn off your radios when not in use. Unless you are a CFO and need constant updates.

Using quickclocks automatic settings, it determined my safest max frequency is 1236@63 vsel. Using the "balanced" profile give me a minimum of 300mhz@14 vsel. Previously I was at 1200mhz@60vsel which I may go back to for the drop in voltage.
 
Last edited:
My best of 3 = 1758

DX Stock, 2.2.1 froyo, rooted
OC: UnstableApps DX/D2 @ 1.3 gHz
vsel: 68
 
And my OC number today -- after removing some more bloatware = 1818!

Anyone know if removing bloatware actually affects this? Or was this just a coincidence??

DX Stock, 2.2.1 froyo, rooted
OC: UnstableApps DX/D2 @ 1.3 gHz
vsel: 68
 
You should have run it ten times before you removed bloatware and taken the average. Then run it ten times after you removed bloatware and taken that average. You would have had a better comparison.

I'm going to guess that the bloatware did little to affect your score (an improvement in score of 80 is immaterial). But this all comes back to what I was saying before: I'm sure you'll find more practical speed in your phone as you use it throughout the day regardless of what Quadrant says.
 

Forum statistics

Threads
955,541
Messages
6,965,144
Members
3,163,307
Latest member
Retinaclearreviews