What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

2 Q's regarding Liberty....ok maybe 3

Jdog....does quickclock require you to understand frequencies as well?

Can someone explain this frequency thing to me so I dont fry my phone trying to figure it out.
 
ugh....ok. Well this will make 3 overclock apps on my phone now. Do I disable them or remove them or what? I have SETCPU which makes my phone lag for a few seconds and drives me nuts. Droid 2 Overclock by Jrummy which has done well but I can't figure out how to overclock...and quickclock.

How do I avoid conflicts....and what about the overclock options in Liberty...do I just leave all that alone?
 
i would or if you dont have them set they should be fine if you keep them
if you have titanium back up go freez them
 
Jdog....well I installed Quickclock and calibrated it. It let me overclock to 1305MHz. But I have 2 questions or concerns to share. First off there is no widget.....minor thing but I do like seeing what my CPU is doing. Second....when I reboot my phone Quickclock doesn't start automatically. Is it supposed to?
 
i thought i read that it started on a delay but i am not sure .....how do you know it doesnt start???? did you go to advanced and set it to start on boot?????
 
No....I thought that was risky and could prevent your phone from starting. Is yours set like that? What kind of phone do you have and what is your clock?
 
i have mine set to boot
1200 max has been mu highest over clock


what were the steps you took setting up?
i know it ran vsel test but did you see it run anything after it rebooted ????? i didnt
 
when did it search for highest?????
did you have to do anything to make it search for highest ???? mine has never done that
 
it just did it after rebooting. All I did was unlock pattern and it started right back up. Maybe run calibration again and see if it does it. Or was there an update you might have missed?
 
Back
Top