Re: *OVERCLOCK* Specific OCT V1.5 Settings
 

I have been running 710 successfully on all ROMs except MightyROM, but no big deal since Mighty runs pretty fast to begin with.

I was running

Steps: 1
Load Max: 100
Load Min: 0
Jump Max: 50
Jump Min: 2

for a while, basically setting it up to run at max while the phone is on and then half speed when in standby, but after recently installing on a new flash i noticed that it was running super smooth with the stock settings, so im currently running the stock settins with CPU max speed at 710

Re: *OVERCLOCK* Specific OCT V1.5 Settings
 

Im running the stock sprint rom and right now my current settings are

CPU MAX- 748.8
Steps- 2
Load max- 100
Load min- 0
Jump max 50
Jump min 2

Seems to be running good!! :) id like to see some other stock rom users settings!

Wirelessly posted (htc Pocket PC: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

I'm running the 6.1 shipped rom also. ;)
Go back a few posts for my settings.

Wirelessly posted (htc Pocket PC: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

I thought I would update my settings here since another user was asking in another thread. ;)
I decided to use a variation on mwalt2's setup to see what results I got and I must say I think his way works great!
I'm gonna stick with these settings a while. Thanks mwalt2! :D

My settings are:

CPU max 768
interval 900ms
steps 1
load max 20
load min 19
jump max 50
jump min 2

This way I idle at 384mhz and any cpu activity above 19% it jumps to 768. I don't notice any lag this way from low to high speed and still I can take advantage of the lower clock speed while I'm not doing much. ;)

Re: *OVERCLOCK* Specific OCT V1.5 Settings
 

@horndoctor
I will try out the setings you just posted. I am using Energy OCT14. I have noticed that when I open the OCT_CFG file that my CPU MAX is reset to 658 for some reason. I also cannot get the keyboard to open up so I can change the Interval...not sure why it doesn't open.

Wirelessly posted (htc Pocket PC: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 7.11) Sprint MP6950SP)

For your settings to be saved you have to change them and then click set. Then click OC ON/OFF to run it with OCd speed then wait a couple seconds. Then click OC ON/OFF to stop the OC. Your settings are only saved when you stop or turn off the OC.
As for the interval, use your stylus to click on the numbers and then slide your hardware keyboard out and change the numbers. Then slide the keyboard back in before you finish other changes and then when you are done making changes click set. ;)

Re: *OVERCLOCK* Specific OCT V1.5 Settings
 

I've tried a handfull of different settings and still get SODs when ending a call. Can't live with that for the minimal amount of performance increase. According to the benchmarks in SKTools, not much difference.

Benchmarks |@528 |@710
Integer |327.6040 |379.9755
Floating point |7.578 |10.230
RAM |611 |629
D-bit |841 |1010
Main write |2349.52 |2289.12
Main read |5264.78 |5202.37
SD write |405.17 |530.75
SD read |8347.83 |7375.75
File Access |1949 |1768
File SD |1807 |1838
SK load |3228 |3228

The faster main memory read/write speeds and RAM access speeds are negligible and not worth the headache of having an SOD after a phone call. I did notice that the SODs seem to only happen on incoming calls and not outgoing ones. Something about the way the processor ramps back down may be causing this.

Wirelessly posted (htc Pocket PC: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

I've never had SOD after, before, or during calls. Maybe it's because I'm using 6.1 :dontknow:

Re: *OVERCLOCK* Specific OCT V1.5 Settings
 

That may well be. Never had an SOD on my Incite running 6.1.

Re: *OVERCLOCK* Specific OCT V1.5 Settings
 

Horndoc, I tried those setting you posted a few days ago, (the 768mhz one, stepping at one), and I had first SOD in like a few months. Back to my original, ahem, "so far bullet proof" settings; 749 @ no stepping, 2000ms polling, load max 100, min 0, jump max 80, min 3. :grin:

and I ALWAYS run 6.5.xxx