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

Root So I'm a little new to overclocking (using quickclock)

S

sonofaresiii

Android Enthusiast
Anyone spare a minute to answer a question?

So I rooted my phone yesterday (awesome) and, after doing some research (rooler's guide and these forums were a help), felt I was ready for overclocking. Decided to start the easy path and get comfortable, so I downloaded quickclock. Calibrated it, set it to highspeed overclocking.

What happened then was, it seemed like my phone would "freeze" for around twenty seconds, then unfreeze for three or four seconds, then freeze again.
Except during those three or four seconds, it would take EVERY input command (tap, swipe, whatever) I had entered when the phone was "frozen" and execute them all at once, in order.

So, okay, the calibration was a little off, I took the highest Mhz reading down a bit.
And that fixed the problem.

Until my phone went idle. When I let it sit for ten minutes and tried to unlock it, it was extremely sluggish, and finally started doing the same freeze-unfreeze-execute-freeze things again. I figured maybe once it ramped back up it'd be fine, but nope.

Instead of changing numbers randomly, I realized I was probably in the realm of "don't mess with anything unless you're sure."

So... any ideas on what's going on/which numbers I need to change to what?

Thanks guys.
 
sonofaresiii said:
Anyone spare a minute to answer a question?

So I rooted my phone yesterday (awesome) and, after doing some research (rooler's guide and these forums were a help), felt I was ready for overclocking. Decided to start the easy path and get comfortable, so I downloaded quickclock. Calibrated it, set it to highspeed overclocking.

What happened then was, it seemed like my phone would "freeze" for around twenty seconds, then unfreeze for three or four seconds, then freeze again.
Except during those three or four seconds, it would take EVERY input command (tap, swipe, whatever) I had entered when the phone was "frozen" and execute them all at once, in order.

So, okay, the calibration was a little off, I took the highest Mhz reading down a bit.
And that fixed the problem.

Until my phone went idle. When I let it sit for ten minutes and tried to unlock it, it was extremely sluggish, and finally started doing the same freeze-unfreeze-execute-freeze things again. I figured maybe once it ramped back up it'd be fine, but nope.

Instead of changing numbers randomly, I realized I was probably in the realm of "don't mess with anything unless you're sure."

So... any ideas on what's going on/which numbers I need to change to what?

Thanks guys.
Click to expand...

Give the Balanced setting a try, your phone might not be able to handle the High Speed overclocking.
 
Personally i don't really mess with the profiles all that much...i let the app calibrate the volatages...and then i set the clock speeds on my own...

to begin with you don't really need to worry about the three lower speeds...but focus on the top clock speed...

you can approach it a couple ways...either starting low and working your way up...or starting high and working your way down...

my phone is simply NOT an overclocker and the highest i can go is about 1.175ghz...

my suggestion would be to set it to 1.2ghz(1200mhz) and see what happens...the app will start a countdown...and if the phone bogs down it will revert you back to stock settings...if 1200mhz doesn't work then try 1175mhz and go again...if it does work, try stepping it up to 1215...and keep fiddling there...

once you have a setting your comfortable with that doesn't lock up the phone right away...you're going to want to test it out over a couple days...for instance...like i said above the max clock speed my phone can take is about 1.175ghz...but at that speed after a few hours of operation the phone becomes unresponsive...so my phone can't run stable at those speeds...so i had to step it back to 1.15ghz...and it runs stable...
 
sonofaresiii said:
Anyone spare a minute to answer a question?

So I rooted my phone yesterday (awesome) and, after doing some research (rooler's guide and these forums were a help), felt I was ready for overclocking. Decided to start the easy path and get comfortable, so I downloaded quickclock. Calibrated it, set it to highspeed overclocking.

What happened then was, it seemed like my phone would "freeze" for around twenty seconds, then unfreeze for three or four seconds, then freeze again.
Except during those three or four seconds, it would take EVERY input command (tap, swipe, whatever) I had entered when the phone was "frozen" and execute them all at once, in order.

So, okay, the calibration was a little off, I took the highest Mhz reading down a bit.
And that fixed the problem.

Until my phone went idle. When I let it sit for ten minutes and tried to unlock it, it was extremely sluggish, and finally started doing the same freeze-unfreeze-execute-freeze things again. I figured maybe once it ramped back up it'd be fine, but nope.

Instead of changing numbers randomly, I realized I was probably in the realm of "don't mess with anything unless you're sure."

So... any ideas on what's going on/which numbers I need to change to what?

Thanks guys.
Click to expand...


Same thing happened 2 me. I spoke with the developer. He told me to change the stability buffer to 20. That calmed it down a lot.

change it to 20, then hit calculate, the hit set cpu, then save.

Hope this helps!
 
honestly? GB is so smooth, I can't tell the differnce between 1 ghz and 1.406! :)
 
Thanks guys, you're the best.

And yeah, I'm going to install GB soon, I want to play around with it now before I move on to the next thing though ;)
 
My settings in Quickclock were as follows,

375mhz@20 vsel
751mhz@38vsel
1001mhz@51vsel
1252mhz@66vsel

I dropped the buffer from 15 to 14 and all was still stable. I'm surprised you had to bring your buffer up to the 20's. You would figure the droid x is a droid x no matter what and system settings would be a-typical but I guess not. Steven you're right about that. GB is so smooth, there isn't much gained from overclocking. The only real gain I get from overclocking is improved browser performance.

undervolting helps save battery life though. Trying to find the "sweet spot" between overclocking and undervolting can be tricky. I just do it the only way you really can, I keep tweaking things. The more I understand my phone and how it works the better I get at it and the easier it gets.

Just play around with it and have fun. You can't REALLY brick your droid. Unless you're one step below a monkey and try opening it up.....lol
 
My current QuickClock setings are:

Stability bufrer: 15

380MHz - 20 VSEL
600MHz - 30 VSEL
950MHz - 48 VSEL
1200MHz - 61 VSEL

I can run stable at 1450MHz but the battery life sucks, I need to keep an eye on the temps and I really don't see much of an difference when compared to 1200ish MHz. I also use SetCPU to set profiles to vary the clock speed at certain times (screen off, temp, low battery). I get 36 hours on the stock battery and 51 hours on a Motorola extended battery with normal use.
 
You must log in or register to reply here.
Back
Top Bottom