FORUMS
Remove All Ads from XDA

[APP] QuickClock Advanced - Official Feedback and Help Thread

18 posts
Thanks Meter: 3
 
By pandapaul, Junior Member on 19th January 2011, 07:34 PM
Post Reply Email Thread
Greetings XDA Forum Members,

I've posted this on a couple other forums, but I wanted to make sure it's readily available here at XDA. This is an official thread for feedback and help regarding my app, QuickClock. I greatly appreciate all feedback, and the more detailed it is the more helpful it is likely to be. Below I will include a copy of the full and most recent help file. If ever you have any questions, you may post them here, PM me, or use any of the other contact methods listed on the About screen within the app.

Thanks & take care,
Paul


Getting Started with QuickClock

The Short Version:
1. Calibrate > Automatic > Wait for reboot
2. 'Proceed' > Wait for end of calibration
3. Main menu > Overclock > Touch 'Profile' and make you selection


A wonderful video made by DebianDog: Overclocking Your Phone Using QuickClock, a Beginners Guider

1. Open up the app and hit 'Calibration' then select 'Automatic' and ensure that all three boxes are checked so that the entire calibration process will run. *This is crucial if you want to get the most out of your phone's CPU.*
- It begins at a universally functional setting at 300 MHz then progressively sets the VSEL 1 lower every 10 seconds until the phone crashes. When the device reboots, the calibration will continue with the Max Speed Finder and will determine a reasonable max speed for your device. Once finished, QuickClock will know how low to set your voltages and how high to set your speeds.

2. Once the calibration is complete, head to the Overclock menu by hitting 'Overclock' from the main menu screen. Select a calibrated profile by touching the word 'Profile' or the name of the current profile next to it or by hitting the menu hardbutton and selecting 'Load Profile.' This will load and set to the CPU the calibrated profile of your choice.

3. If you'd like to customize your settings, put in whatever frequencies you would like to use as your four scaling points and hit 'Set CPU.' Make sure that your lowest speeds are at the top and your highest are at the bottom. If your requested speeds do not produce VSESL's exceeding 88 and are within the bounds of your device's minimum and maximum speeds, then the CPU will be reconfigured to the exact specifications you have given. If nothing crazy happens, confirm that you would like to keep the settings in the dialog that pops up. You may also check the box in the popup to save these settings to the currently selected profile.
- If you have put in a speed that is too high for the phone, you may experience what people call 'turtling' where everything slows to a crawl. I've included an Anti-Turtler which requires you to confirm that you'd like to keep the settings. If you choose 'No' or do not say 'Yes' within 10 seconds, the default speeds and Stability Buffer will be loaded and set. It also checks for lag while counting down and will immediately revert to defaults if it is able to detect significant lag time. Once you've set your new speeds, try them out for a while. If you find they aren't actually stable then just increase that stability buffer a little bit, or likewise decrease the buffer if you think you could go lower. When doing this or any other testing use the 'Calculate' button to merely display the calculated VSELs without actually setting them to the CPU. This way you can preview and check things out before they get set.

I've implemented as many safeguards in the app as I could think of, but there's always the possibility of damage to your CPU when adjusting these kinds of parameters. So have fun with it, but be smart and be careful.


Scaling Constraints

Setting Min and Max

On the first screen of QuickClock you will see four numbers aligned left to right below the current frequency and VSEL. These are the currently available scaling frequencies. The '[' and ']' indicate the min and max constraints that you may change by simply touching the current min or max then selecting the new one(s). If you have the scaling constrained to one frequency alone, then touching that number will remove both the '[' and ']' to indicate that you must choose both min and max. First select your desired min and then select the max.


Using Profiles

Loading a Profile

To load a profile, simply touch the word 'Profile' or the name of the current profile on the Overclock menu and then select the profile you would like to use from the list that pops up. If you prefer to use the menu hardbutton, you may click the 'Load Profile' button there to access the same list. When you choose one, the profile will automatically be set to the CPU.

Saving a Profile

When setting the CPU configuration using the 'Set CPU' button, you may opt to update the currently selected profile using the checkbox in the Anti-Turtler dialog. To save the current CPU configuration to a different profile, touch the name of the current profile then select 'Overwrite.' Alternatively you may hit the menu hardbutton while in the Overclock menu and select 'Overwrite.' There are four profile slots available for your use, and by default they contain a variety of useful configurations. The profile slots are color-coded to give further identity to each profile and because colors are fun. If you choose to save a new configuration, the information previously in that slot will be overwritten. You will be prompted for a name, which you may leave the same or alter in as creative a fashion as you desire.

Exporting Profiles

If you would like your profiles to be exported for any reason, you may select 'Export' from the hardbutton menu on the Overclock screen. This will write all four profiles to one Zip archive (named as you choose) on the SDCard. The profiles are exported in the same format used by Droid Overclock and may, therefore, be imported into that app if you like.

Some Definitions

Bare Minimum Voltage/VSEL (BMV)

The lowest possible VSEL setting at a given frequency that will not immediately crash the phone. This is not a stable setting, rather it is a point of information used to calibrate the application in conjunction with the Bare Minimum Frequency and Stability Buffer.

Bare Minimum Frequency (BMF)

The frequency at which the BMV is found. Again, the combination of these two settings does not produce a stable result. That is where the Stability Buffer comes in.

Bare Minimum Pairing (BMP)

Any BMV and BMF pair. e.g. 15 VSEL @ 300 MHz one for me, but so is 66 VSEL @ 1400 MHz. They both are points at which lowering the VSEL by one would result in an immediate crash.

Stability Buffer (SB)

The percentage to increase calculated bare minimum pairings. This defaults to 15% (originally 13%, but that proved less stable on 2.2.1).
The Following User Says Thank You to pandapaul For This Useful Post: [ View ] Gift pandapaul Ad-Free
 
 
25th January 2011, 10:35 PM |#2  
Member
Thanks Meter: 15
 
More
This app doesn't seem to do anything on my Droid X. I hit Calibrate > Automatic and the VSEL gets into the negatives without crashing anything. Other overclock apps work (and crash me) just fine.

I get a popup when I start the app that says my device is not supported, but the app description clearly says it is.
25th January 2011, 10:41 PM |#3  
OP Junior Member
Flag Atlanta
Thanks Meter: 3
 
More
Quote:
Originally Posted by Sunblood

This app doesn't seem to do anything on my Droid X. I hit Calibrate > Automatic and the VSEL gets into the negatives without crashing anything. Other overclock apps work (and crash me) just fine.

I get a popup when I start the app that says my device is not supported, but the app description clearly says it is.


It checks for supported device by checking the string representing "Model number" in the Settings > About phone menu. If yours says "DROIDX" there, it should not be giving you that unsupported message. If that's the case, try an uninstall/reinstall. It wasn't crashing, because it wsasn't setting the VSEL, because it never loaded the module, because it didn't think the device was supported. Make sense? Haha. Anyway, man, let me know what you find out.
25th January 2011, 10:55 PM |#4  
Member
Thanks Meter: 15
 
More
Ah, my model number is "Droid X" which is probably because of the rom I have on it. Let me try and change that to DROIDX and get back to you.

Thanks for the quick response.
25th January 2011, 11:00 PM |#5  
OP Junior Member
Flag Atlanta
Thanks Meter: 3
 
More
Quote:
Originally Posted by Sunblood

Ah, my model number is "Droid X" which is probably because of the rom I have on it. Let me try and change that to DROIDX and get back to you.

Thanks for the quick response.

What rom are you on? Either way, I'll add that in as a possible model number. Easy addition.
25th January 2011, 11:10 PM |#6  
Member
Thanks Meter: 15
 
More
Incredibly Re-Engineered 1.00
25th January 2011, 11:13 PM |#7  
OP Junior Member
Flag Atlanta
Thanks Meter: 3
 
More
Quote:
Originally Posted by Sunblood

Incredibly Re-Engineered 1.00

Oh. Yeup that explains it. That guy... ugh. Well I won't get started on that rom and its dev, but it's wonderful that I now know why people on that ROM were unable to use any of the OC apps. Here's our answer.

I salute you, sir.
25th January 2011, 11:23 PM |#8  
Member
Thanks Meter: 15
 
More
Quote:
Originally Posted by pandapaul

Oh. Yeup that explains it. That guy... ugh. Well I won't get started on that rom and its dev, but it's wonderful that I now know why people on that ROM were unable to use any of the OC apps. Here's our answer.

I salute you, sir.

Hah, no problem. Glad I could help.
In the meantime I'm going back to stock to try the app again.
25th January 2011, 11:30 PM |#9  
OP Junior Member
Flag Atlanta
Thanks Meter: 3
 
More
Quote:
Originally Posted by Sunblood

Hah, no problem. Glad I could help.
In the meantime I'm going back to stock to try the app again.

Sounds good. Keep in mind that if you see negative VSELs in the calibration again, the app may (for who knows what reason) not have gotten SU permissions. I've had people with that issue simply since they didn't hit the right button on the SU request. Then also, if the calibration all goes as it should and you get a random reboot that you think is due to the OC, all you need to do is increase the stability buffer a little bit until you don't get any more random reboots. It defaults to 15, which is usually a nice and stable point that still saves a good bit of battery due to undervolting. Some people are able to drop it to 10, still some have to increase it to 20.
25th January 2011, 11:39 PM |#10  
Member
Thanks Meter: 15
 
More
With stock I got a reboot at 12 so it's working fine. It's testing max clock speed at the moment. Fantastic app.
The Following User Says Thank You to Sunblood For This Useful Post: [ View ] Gift Sunblood Ad-Free
25th January 2011, 11:46 PM |#11  
OP Junior Member
Flag Atlanta
Thanks Meter: 3
 
More
Quote:
Originally Posted by Sunblood

With stock I got a reboot at 12 so it's working fine. It's testing max clock speed at the moment. Fantastic app.

Thanks, man. I'm really glad you're enjoying it. I'm working on some improvement to the max speed finder so that it will resume and build the profiles in case of a crash during that portion of the test. If you happen to be one of the folks that does get a crash during the max speed finder, you're not really even missing out on much. The main thing is getting the right BMV. From there, you could just manually build your profiles, calculate, and set to cpu.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes