Root [APP] QuickClock Overclock Assistant

[Airmaxx23]

This was posted in one of the overclock threads recently but I feel that it needs it's own post so it will be seen by more people. All app credit goes to pandapaul.

QuickClock Overclock Assistant - Android app on AppBrain

Edit: There is also an advanced, paid version ($.99) that will automatically figure out your settings for you.

http://www.appbrain.com/app/quickclock-advanced-overclock/com.jpapps.quickclockadvanced


Here is his original post:

Hey Folks,

I wanted to let everyone know that I've posted an app called QuickClock up on the market. It drastically reduces the amount of testing needed in order to find the best voltage settings. It's free for now, so snag it early.

Here's how it works: Find the absolute bare minimum vsel necessary at a given frequency that keeps the phone from crashing or turtling (but isn't necessarily "stable"). Slap that number and the frequency you used into the app, hit calculate, and BAM. You've got your battery-maximizing yet stable vsel recommendations.

Can't use this app to set them directly as I don't like the idea of packaging Tiago's work in my own app (at least not without talking to him first), but all those hours of testing and uncertainty will just fade away.

I'm using it like crazy now that I finally made it, and I hope you enjoy it too.

I wrote up a quick guide on how to use this along with JRummy16's Droid Overclock app.

The first thing you need to do is find the voltage value, at a given clock speed, that cause the phone to immediately crash. To do this just open up the overclock app and go to "CPU frequency scaling" and slide the top slider down to 350. Now go back and go into Advanced/Custom. Using the Slot 1 Voltage / Min field lower the value by 1 and press "apply preset" then preset 1. Continue lowering the voltage by 1 (apply the preset each time) until the phone locks up and reboots, remember the number that caused the phone to lock up. Now open the QuickClock app and enter the 4 frequencies that you will be using in the "Frequency" fields. In the BMP frequency field enter 350 and for the BMP VSEL use the number that locked up your phone but add 1 to it (ex. if 17 caused your phone to reboot use 18). Now press calculate and your scaling values will be displayed below. Enter these values into the overclock app as your new scaling, then save and apply the preset. I tried this out and have been using the resulting speeds and voltages all week without a single reboot.

Here are the stock settings:

350 - 33
500 - 48
800 - 58
1000 - 62

I'm using currently using these settings, kind in mind, each phone is different.

380 - 18
600 - 29
900 - 42
1250 - 62

http://www.appbrain.com/app/quickclock-advanced-overclock/com.jpapps.quickclockadvanced

 

[madAdam]

Thanks. This is very cool. I grabbed the app when I saw your original post in the other thread but didn't have much luck. My problem was using the high freq instead of the low freq to get recommended values. Like most people, I had spent more time experimenting at the top end rather than the bottom.

But I just followed your excellent instructions and am currently trying out the resulting recommendations. I've never set my low freq voltages so low, but the phone seems to like it (and I know the battery will LOVE it!). I'll report back.

Have you had any luck using the profiles in JRummy's app? I've tried screen off, temperature and battery profiles. They kick in OK but don't kick out.

 

[Airmaxx23]

Thanks. This is very cool. I grabbed the app when I saw your original post in the other thread but didn't have much luck. My problem was using the high freq instead of the low freq to get recommended values. Like most people, I had spent more time experimenting at the top end rather than the bottom.

But I just followed your excellent instructions and am currently trying out the resulting recommendations. I've never set my low freq voltages so low, but the phone seems to like it (and I know the battery will LOVE it!). I'll report back.

Have you had any luck using the profiles in JRummy's app? I've tried screen off, temperature and battery profiles. They kick in OK but don't kick out.

I'm glad the instructions helped, it really is a great little app. I can't believe how low I'm able to go with the voltage but it has been solid all week. I use setCPU for battery profiles and have never had a problem.

 

[madAdam]

I use setCPU for battery profiles and have never had a problem.

Do you set your freq scaling and voltages with JRummy's app and your profiles with SetCPU? I've never used SetCPU but perhaps I'll give it a try. Can you recommend some profiles?

 

[Airmaxx23]

Do you set your freq scaling and voltages with JRummy's app and your profiles with SetCPU? I've never used SetCPU but perhaps I'll give it a try. Can you recommend some profiles?

That's exactly what I do. My Profiles are as follows:

Temp > 45.5 C: 900 max / 380 min Priority: 100
Screen Off: 380 max / 380 min, priority: 95
Battery < 30%: 900 max / 380 min, Priority 90

 

[dhoffman1421]

Don't see it in the market, will try to pick it up from your link.

 

[Airmaxx23]

Don't see it in the market, will try to pick it up from your link.

It's there, I just double checked. Just search for "quick clock", it should be the top result.

 

[madAdam]

That's exactly what I do. My Profiles are as follows:

Temp > 45.5 C: 900 max / 380 min Priority: 100
Screen Off: 380 max / 380 min, priority: 95
Battery < 30%: 900 max / 380 min, Priority 90

Thanks again. I'll give these a try as well.

Do you use JRummy's app (as opposed to SetCPU) to apply your scaling freqs at boot?

 

[Airmaxx23]

Thanks again. I'll give these a try as well.

Do you use JRummy's app (as opposed to SetCPU) to apply your scaling freqs at boot?

No, I'd rather take the few extra seconds and apply them each time I reboot just to be safe. I use the profiles in setCPU though.

 

[dwcasey]

Working good for me! Bought the app, then installed and loaded the Milestone overclock module, ran through the auto config. After reboot, I went in and played with the set CPU scaling. I only adjusted the top-end to 1250, then I tried 1300.

Are the CPU/vsel pairs set for me automatically initially?

300 16
600 31
800 40
1300 67

And FWIW, my linpack and quadrant scores are WAY up. I know those are not necessarily good measures of real world performance, but they are still good benchmarks.

 

[dwcasey]

Also wanted to add that with Gscript installed and running the script below, I get a nice report on min/max and how long the CPU has spent at each freq


echo "Current CPU min frequency:"
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo "Current CPU max frequency:"
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo "CPU scaling frequencies and time in each state";
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state;

 

[colchiro]

I've never used SetCPU but perhaps I'll give it a try. Can you recommend some profiles?

Same here.

 

[Outlaw71]

Downloaded this app this morning after seeing it on here. Thanks for the recommendation.

 

[colchiro]

Decided to go with the paid app. It apparently doesn't recognize JRummy's app and suggests I install Milestone to use this.

Seems like a waste to have two apps installed.

Had to reboot for it to recognize JRummy's app.

 

[colchiro]

Not sure this is ready for prime time yet. I DO have root, but still it never reboots while checking parameters. Previously was OC'd to 1250 with ULV.

Get Parameters Automatically comes up with this:

Bare Min Frequency: 300
Bare Min Voltage: 2
Stability Buffer: 13.0

When I calculate only, I get this:

300 3
850 30
1000 37
1250 50

BTW, I'm on Apex 1.3.

Oh, and did I mention it's sooo slooow after running this app?

So decided to try setting this and bumped the minimum to 400 (8 vsel), clicked on "set" and it hung for about 20 seconds, then rebooted.

Guess I need to do the manual method described above instead of the auto method provided by the paid app.

 

[dwcasey]

Odd that it would recommend such low voltage. I wouldn't think that the ROM would affect this, but who knows.

 

[colchiro]

This is what I ended up with:

I had reservations, but used the suggested 1 volt above the crash setting, then booted into recovery and reapplied my Christmas theme (since I had updated Apex), then had a struggle (3 boot attempts + 2 FC's for system + battery pull) to boot back so upped the base voltage by one more volt (for now). Seems ok now, but might bump it one more volt and recalculate.

 

[pandapaul]

Not sure this is ready for prime time yet. I DO have root, but still it never reboots while checking parameters. Previously was OC'd to 1250 with ULV.

Get Parameters Automatically comes up with this:

Bare Min Frequency: 300
Bare Min Voltage: 2
Stability Buffer: 13.0

When I calculate only, I get this:

300 3
850 30
1000 37
1250 50

BTW, I'm on Apex 1.3.

Oh, and did I mention it's sooo slooow after running this app?

So decided to try setting this and bumped the minimum to 400 (8 vsel), clicked on "set" and it hung for about 20 seconds, then rebooted.

Guess I need to do the manual method described above instead of the auto method provided by the paid app.

Hey Colchiro,

First and foremost thanks for using the paid version of my app. Contact me on gChat (thesamuraipanda) when you have a chance and we'll get this figured out. The way the auto finder works is by progressively attempting lower and lower VSEL at MHz. ... Immediately after writing that sentence I realized one thing that could be the problem. If you were using a CPU scaling profile that prevented the CPU from dropping to the lowest scaling point, then it would never actually be stressing the CPU with the low voltage settings. I don't think there's any way that your CPU could operate at all with only 2 VSEL at 300 MHz, so I'm going to modify the way that whole thing works and get this app working perfectly for you ASAP. I just finished up final exams today, so my time should open up a bit more next week... I hope. Lots of things I want to do for the overclocking community.

Get in touch on gChat if you get a chance so we can try some things out.

Peace

EDIT: Actually I'm going to go ahead and modify one thing to slap a bandaid on this until I can have a closer look at things. Look for an update in the market in a few minutes.

 

[pandapaul]

Decided to go with the paid app. It apparently doesn't recognize JRummy's app and suggests I install Milestone to use this.

Seems like a waste to have two apps installed.

Had to reboot for it to recognize JRummy's app.

Wanted to mention also that it can work in conjunction with any functioning overclock module, so you can feel free to use Milestone Overclock, JRummy's app, or no app at all.... so long as you have a functioning OC module loaded up.

One thing I'll be adding in soon is the ability to export profiles to all the other Overclocking apps so that QuickClock will be easily usable in conjunction with the others.

 

[pandapaul]

Also wanted to add that with Gscript installed and running the script below, I get a nice report on min/max and how long the CPU has spent at each freq


echo "Current CPU min frequency:"
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo "Current CPU max frequency:"
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo "CPU scaling frequencies and time in each state";
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state;

I will definitely be adding in CPU monitoring and possibly some battery statistics tracking as well. Knowing you took the time to do that script lights a fire under me to get it done sooner!

 

[colchiro]

Thanks for the quick support and update. Integration with other OC apps would be cool.

Just installed the update (and new Market--eek).

Ran the app, again it didn't detect jRummy so rebooted. (I had the same issue with jRummy, but I think just the first time when I installed it.)

The first time I ran the VSEL Finder, I was getting warnings that it wasn't responding and asking if I wanted to close it. I clicked on "wait". Later I realized that that might be affecting the cpu speed and affecting the outcome so I avoided that behavior in subsequent attempts. I realized it was the lack of a crash that allowed the VSEL to get to a false low level.

Just ran VSEL Finder now and DID get a reboot, but the detected min voltage is below the crash level from my testing (crashed on 12 volts), but it retained my OC max now (1250) instead of defaulting to 1000.

Min Freq: 300
Min Volt: 11
Stab buffer: 13.0

Calculated (w/o editing of speeds):

350 15
600 28
850 40
1250 60

Will see how this goes. Not going to add to profile just yet. Have a busy day, need to drive out of town, come back and go to company Christmas party tonight.

Should have time to think about chatting after that.

UPDATE: Just checked my mail and installed gScript from Market and got a hang followed by a reboot. But we're getting closer. That's what SW development is all about.

 

[colchiro]

Also wanted to add that with Gscript installed and running the script below, I get a nice report on min/max and how long the CPU has spent at each freq


echo "Current CPU min frequency:"
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo "Current CPU max frequency:"
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo "CPU scaling frequencies and time in each state";
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state;

I will definitely be adding in CPU monitoring and possibly some battery statistics tracking as well. Knowing you took the time to do that script lights a fire under me to get it done sooner!

Is there a time since last reboot (or uptime) you can add? I might have crashed/rebooted without knowing it.

 

[nycebo]

Keep us posted. What's curious to me is the huge discrepancy between the ultralow and low voltages of Jrummy's app compared to the 'suggested' values from QuickClock. Hmmm....

 

[pandapaul]

Keep us posted. What's curious to me is the huge discrepancy between the ultralow and low voltages of Jrummy's app compared to the 'suggested' values from QuickClock. Hmmm....

Jared's app errs on the side of stability which is a good idea for preset profiles. QuickClock determines the VSEL for you based on what your phone can handle. Basically I took all the hours of testing I did on my Droid x and derived some formulas that would be useful for everyone. With the updated VSEL finder, I think folks should find the suggested values will save battery life and still maintain stability quite well. If you like Jared's app, keep an eye out for the profile exporting update coming sometime this week.

 

[Airmaxx23]

Keep us posted. What's curious to me is the huge discrepancy between the ultralow and low voltages of Jrummy's app compared to the 'suggested' values from QuickClock. Hmmm....

You need to keep in mind that the ULV and LV settings in his app are not low when compared to stock settings, they are just lower than the other app settings. Everyone's phone is different and his settings will pretty much work with any phone but they are a lot higher than they need to be for some people.