[APPS] Droid X/2 Overclock App - Easy & Noob friendly ;)

[sensatti]

Any voltage with over 1.1GHz makes my DX like freeze for 5 seconds then resume for 2 second then freeze. And just repeats till I manage to turn it back to 1.1

I would like to get higher than that

Sent from my DROIDX using Tapatalk

The highest I can get without major lag is 1.15. Hard to imagine the cpu's in these devices vary so wildly that some can get a stable 1.45 and others cant get above 1.1.

Sent from my DROIDX using DroidForums App

 

[spider210]

Still doesn't work not sure why... how else can I get this

Sent from my DROIDX using Tapatalk

 

[MrKleen]

Still doesn't work not sure why... how else can I get this

Sent from my DROIDX using Tapatalk

At this point I wouldn't worry about it, It may not even work. At least for now it no longer works with the D2 even after 3 updates. I think it works for most with the X however.

Check out the one click scripts that work very well if you don't mind connecting your phone to your computer. Darkonion has a good one...

 

[spider210]

Id really like to try this app... I got a dx not d2

Sent from my DROIDX using Tapatalk

 

[bowhunter]

View attachment 18389
I have been running at 1.2/low voltage, for over 24 hrs. have had no problems. It is very smooth and fast. Battery drain not that noticable.

 

[Daali]

Does this app check to see if you already have the overclock module? I have been doing this manual for a couple days, but I like to support forum devs, so I bought it.

Force closes on my tranquility 2.3.8a with overclock.ko in place, but not insmod ed

Sent from my DROIDX using Tapatalk

 

[BossBrew]

Sweet app, running low voltage @ 1.2GHz all day without a problem. I had freezing issues at 1.3 GHz and Up.

 

[mjsplicer78]

Excellent work Jrummy. Haven't set anything to boot just yet but have ran servral benchmark tests with quadrant. First is medium voltage set @ 1.1-1.4, the second was low voltage 1.1-1.4, and the last is low voltage 900-1.4dancedroiddancedroid:icon_ banana::icon_ banana:

Nice benchmarks! How did you manage that? I have tried all 3 of your settings on my X running rubix focused+incognito, and I never benchmark over nexus one.

Sent from my DROIDX using DroidForums App

I haven't done anything special to my X. I have been over the N1 consistently since I rooted, and deodexed though. The only thing is that I've been running the OTA and not leaks of 2.2 up until RubiX and APEX hit

 

[RK KINGKONG]

force closes ,trying to reset

Just ran 1.3ghz on low voltage anything higher causes reboot. 1.3 is very stable and quick. Once I get done trying different frequency I will do battery usages. Got a quadrant score of 1792 on 1.3 lv

Sent from my DROIDX using DroidForums App

just becuase I already didnt know what I am doing I tried running mine at your settings , just rooted not running any special roms or themes . I set it then ran a quadrant test n now im running slower than I was originally . Im trying to put it back at stock clock speeds but now it just freezes and force close when I try .
any suggestions , Im just trying to get it back to normal now that i saw that trying to run your settings slowed me down . not saying its your fualt I just tried to follow your sets cause you were successful with it ..

 

[DxBlade]

If you didn't set it to overclock at boot just reboot the phone and you will be back to stock. i have had the best results with this setting but each phone is different if 1.3 is too high for you try a lower one or try the medium or high voltages.

 

[sensatti]

Hmm, I have been running at 1.15 ghz all day but all of a sudden the phone rebooted and now every time I try to OC again to any frequency nothing happens. Setcpu is not detecting any changes and it doesn't seem to actually be changing anything. I get the confirmation that the set scaling was done but again no changes show up in setcpu. Any ideas?

 

[MrKleen]

Hmm, I have been running at 1.15 ghz all day but all of a sudden the phone rebooted and now every time I try to OC again to any frequency nothing happens. Setcpu is not detecting any changes and it doesn't seem to actually be changing anything. I get the confirmation that the set scaling was done but again no changes show up in setcpu. Any ideas?

After setting your speed are you re autodetecting in setcpu?

 

[stealthgriffin]

I've been having the same problem after a restart. I have to go back into the overclock app and re-oc it to get setcpu to recognize the overclock.

Sent from my DROIDX using DroidForums App

 

[Smarcisin]

everytime i run this app it just force closes...running last leaked 2.2 rom with apeX installed over it

 

[DxBlade]

i had that happen a few times set cpu was set to the max frequency and when a restart occured it cpu went to stock and set cpu would still show the oc speed. i did a force stop on setcpu and then it would refresh and work again.

Stealthgriffen if you did not set it to scaling on boot it will revert to stock after a restart. i would suggest keep it in the realtime scaling untill you find the best setting for your phone.