QuickClock Advanced Official Feedback and Help Thread

[RootzMan32]

Hey! can someone explain how I can undervolt my phone with this app? And will the undervolt be in effect when the screen is turned off?
Thanks!

[Droid-X-Forums]

[pandapaul]

Hey! can someone explain how I can undervolt my phone with this app? And will the undervolt be in effect when the screen is turned off?
Thanks!

Certainly. Undervolting is part of the process automatically, so you actually don't have to worry about it (assuming your phone is on the supported list). Run the calibration, pick a profile, and you should be pretty well set. The algorithm that calculates voltage per frequency is written to pick the lowest stable voltage possible.


Also, hello everybody

To anyone who has missed out on help or information due to my absence in the Android community over the past months, I am truly sorry. I miss working on software like QuickClock and talking with you guys about it so much. It was really one of the most interesting things I've ever been involved in. For better or worse, I got a full time job as a microbiologist. I'm happy with the work I'm doing particularly since I'm actually utilizing my college degree, but I very much miss the excitement and fun of Android work. Oddly enough, though, I think I might have managed to combine the two. I'm working on putting together a funding proposal to start a project based around digital image analysis of immunoblots. Half of the software would be intended for use on smartphones (please God let it be solely Android and not iOS).

I bought a Galaxy Nexus a couple days ago and am absolutely loving it, but I strongly doubt there's any chance I'll ever have time to get QuickClock working on it. I'm curious, though, what's going on these days with Android overclocking? I've been so out of touch that I honestly have no idea. Did any apps pick up where I left off or has interest in automated overclocking optimization faded?

Happy to be posting and hoping you all are doing well,
Paul

[silver04v]

Certainly. Undervolting is part of the process automatically, so you actually don't have to worry about it (assuming your phone is on the supported list). Run the calibration, pick a profile, and you should be pretty well set. The algorithm that calculates voltage per frequency is written to pick the lowest stable voltage possible.


Also, hello everybody

To anyone who has missed out on help or information due to my absence in the Android community over the past months, I am truly sorry. I miss working on software like QuickClock and talking with you guys about it so much. It was really one of the most interesting things I've ever been involved in. For better or worse, I got a full time job as a microbiologist. I'm happy with the work I'm doing particularly since I'm actually utilizing my college degree, but I very much miss the excitement and fun of Android work. Oddly enough, though, I think I might have managed to combine the two. I'm working on putting together a funding proposal to start a project based around digital image analysis of immunoblots. Half of the software would be intended for use on smartphones (please God let it be solely Android and not iOS).

I bought a Galaxy Nexus a couple days ago and am absolutely loving it, but I strongly doubt there's any chance I'll ever have time to get QuickClock working on it. I'm curious, though, what's going on these days with Android overclocking? I've been so out of touch that I honestly have no idea. Did any apps pick up where I left off or has interest in automated overclocking optimization faded?

Happy to be posting and hoping you all are doing well,
Paul

Yours is basically it. I still use it to this day.

Running with MIUI

[dtroup64]

Paul,
Loving your app! Thanks for all the work you put into it. I use it on Vortex as well as MIUI and I love it.

[popcenator]

Good to see you're doing well Paul, still a great app and I have yet to see an automated overclocking app like it.

on the move..

[Talon66721]

Glad to hear you're still alive, Paul! Have to admit I was starting to wonder. Congratulations on the job, too!

Sent from my DROIDX using Droid X Forums

[dracon6ai]

First off awesome app, it was my GOTO app on my DX for anything CPU wise. I just recently moved to the GNexus and tried quickclock the instant I got rooted (should of read your supported device). Any chance you can get this working on the GNexus?

[jasondhsd]

Hi hope this thread is still being looked at. Just bought quickclock for my droidx which as been flashed with Milestone .604 so I could get off of .621 (warranty replacement came with it pre-installed ) Anyway Quickclock says device unsupported and when I try to calibrate it starts going into negative vsel. I cleared the data on superuser and quickclock but it does the same thing again. What is going on?!


EDIT: Ok I got it to work I used build.prop editor to change the model from Milestone X to DROIDX and it worked so far I'm OC to 1251mhz with a quadrant score of around 2000.

[Azzuron]

any chance to get this running on the hp touchpad using cm9? awesome tablet. would be great to have your app running on it!

[dbong123]

OK I am having an issue with the calibration. The VSEL keeps going lower and lower and testing all the way past -100 VSEL @300MHz.

Here's the details:
I had a DX .621 in which I used the ZergRush Milestone X Root method. I changed the model number in buid.prop back to DROIDX so the model would be recognized by the overclock apps. I downloaed quickclock advanced and started calibration. After I noticed this problem, I cleared data from superuser and uninstalled/reinstalled quickclock advanced, and still am having the same issue.

If anyone has an answer for me I would be much appreciative.

Thanks

EDIT: the program is recognizing the device because I can get a max clock speed of 1350 if I deselect voltage. Just the Voltage calibration doesn't seem to be working

EDIT: It works now. I think it was a permission issue. I installed titanium backup and it asked if I wanted to fix some permissions and also through Rom manager I fixed permissions and it worked after this