yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
Update: Funny results. But not ha-ha funny.

OK, I was getting freezes, stalls, or SoDs no matter what (Sense on/off, S2U2 on/off, dynamic on/off, 1.41/1.5) but now I'm up for a day-and-a-half with no problems, even doing things that would cause freezes before, like playing Crayon Physics, movies in TCPMP, or intense browsing over WiFi.

I changed two things. I donKt know which is responsible for getting 1.5 to work well (so far) but I'm too happy and lazy to suss it out at the moment. I waited til the phone booted completely before launching OCT instead of running a start-up shortcut, and I also set ALL settings to zero, not just interval. If I'd previously said I'd tried all zeros, I guess I lied a little, as I'd just had interval at zero.

If the settings-to-zero thing is the fix, maybe a 1.5.1 or 1.4.2 could come out that incorporates a simple toggle to disable all dynamic clocking. If the wait-to-run-at-boot is my fix, maybe I could fix up a MortScript thing to put in my startup, to auto-launch after (X) seconds.

Just throwing out info and ideas. Anyone else with 1.5 problems, even after going 1.5 to 1.41, try either running after boot, or ALL settings to zero, and let us know what happens?
[Touch Pro2, Tilt 2 Themes and Apps] Doo Doo:
like i said before i tried the settings you mentioned above i even waited till my phone completely booted before starting OCT & still got BSOD's during phone calls so idk :confused:
[Touch Pro2, Tilt 2 Themes and Apps] nayr1482:
setting the interval to 0 means your are not DYNAMICALLY overclocked anymore...meaning you are just running at your OverClock speed 24/7

as far as battery drain - you will have to see for yourself.
[Touch Pro2, Tilt 2 Themes and Apps] nayr1482:
i have played with all "3" methods (Netripper + Script, SetCpuSpeed, OCT) and I must say the only one I did not have SOD issues with was Netripper + Script.

Now that is a bit of an unfair statement since I have not been testing OCT that long and I have never had it NOT set to Dynamic so...a ways to go.

I have only been testing OCT for 3/4 days now - but I can say I typically get SOD after phone calls, and this morning when my alarm was supposed to go off.

I am trying to figure out if it is because the speed the cpu is set to is too low for the requirements - OR - if it is because there is a demand for more and the cpu tries to jump too high too fast...hard to tell.

I think it would be GREAT if the user could define their "low speed" instead of just dividing the OC speed by the number of steps. Or - at the very least hard-code it into the program that if the screen is off the speed is set to 528mhz. Or better yet - if the user could define a low speed w/ the screen on and a low speed with the screen off :)

I believe most if not all of the SOD trouble is caused by underclocking w/ the screen off and then something demands more speed than you have. But - the only way to fix this with the current setup is to disable dynamic overclocking...because even if you set it to one step you are lower than 528...
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
Same here for not knowing what to say. I've never had any of the phone-call SoD issues with OCT (or MSM7K for that matter.) I've also never had any of the music-player issues. Perhaps it's partly down to the many differences in ROMs and registry setups? I can't really do more than guess though.

I'm going two days stable now though whereas before I'd always locked up with 1.41 or 1.5.
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
I keep my settings all at zero, running at 768mhz, no drain overnight on battery life. 100% at bedtime (around 10pm), 98-100% at 6:30am.

Checks email every 30 minutes.
[Touch Pro2, Tilt 2 Themes and Apps] Alcoholic:
Not that i've seen. Running at 748Mhz (interval = 0) and battery drain is almost identical to stock.
[Touch Pro2, Tilt 2 Themes and Apps] sovereignty:
You read my mind. I was just coming back to this thread to say the exact same thing - minus the stuff about the netripper app.

I used to have SOD on phone calls with OCT set to 1 step in order to step down clock frequency under idle/low load. Right now this is the only way to try to save battery. But, the problem is that there is no way to do this without the CPU underclocking.

@iwfratz - Can you tell us if you will release another version with the feature nayr1482 just proposed?

I think the only thing needed is a checkbox. If checked, your stepping algorithm is used to determine CPU speed. If unchecked, the Max CPU speed will be used if meeting the high load requirements or it will clock down to 528 MHz if meeting the low load requirements.

If you do not intend to release another version, would you maybe post some example source code in your readme file on how to interface with your driver (i.e. - open .dll; get cpu load; set cpu speed; close .dll)?
[Touch Pro2, Tilt 2 Themes and Apps] bsSkunkApe:
Liking this OCT v1.5. Running for a day now with heavy usage including phone calls, wake-up alarms, internet, gps, texting, etc... with no SOD or lock ups with these settings. I even turned the weather animation on in sense just to tax it a little more. It runs everything, cookie animations and all, with no problem! Battery life is same or better too from what I can tell. The only thing I'm keeping an eye on is the temp. Battclock says the phone is running a few degrees warmer than usual.

CPU max - 787.2 MHz

interval - 1000

# steps - 1

load max/min - 0/0

jump max/min - 25/25
[Touch Pro2, Tilt 2 Themes and Apps] stevedebi:
Maximum OC speed varies with the phone

My TP2 recently caught the dreaded "NO USB" illness, and I had to send it in for a warranty replacement. My previous TP2 would O/C to 768 with no problem. But the replacement phone simply froze at that speed. So far it is running OK at 710.

But anyway, the point is that the hardware in the phone apparently varies in its capability to handle O/C.
[Touch Pro2, Tilt 2 Themes and Apps] Rickgig:
I saw this thread about a week ago and it took me a few days to get up the guts to install it. I have used other ROM’s on previous phones but have been reluctant to jack with my Tilt2 since I have only had it for about 2 months. I’m on AT&T and am running WM6.5 stock rom and stock radio.

Over clocking is not new to me but after reading the trouble some of the guys have had with SoD’s I was hesitant to load it (OCT v1.5).

I was drawn to this like a moth to fire! I installed it on my memory card and did not place a shortcut in the Startup folder. I wanted to be in control of when the program was started and to have the ability to reboot the phone without having the software load every time.

Ran the stock settings for 3 days without issue and then kicked it up to 710.4 with all other settings at the stock values.

My experience so far is great. Battery life sucks but that is to be expected. I use Google maps, Bing and have an exercise pgm that utilizes GPS for tracking and haven’t had a problem at all. I thought I had an issue with HTCAddicts cleanRAM but once I reset the scheduler I haven’t experienced any other problem.

The only thing I noticed was on an SMS that I rec’d and replied to. My reply was time stamped 4 minutes earlier than when I rec’d the SMS. The thread looks odd since it sorted my reply ahead of the msg rec’d. Not sure if anything can be done about this and haven’t read all the posts to see if anyone else has run into this.

I placed the GUI executable in my programs folder and launch the program from there, via the toggle “OC on/off”.

In essence, everything loads on my phone completely before I launch the GUI to start the program. So you could consider me one of the fortunate ones that have no issues but loads the program after everything else has been loaded.

I reluctant to play with the other settings since everything works for me plus they are over my pay grade (ie. I have no idea what they do).

If anything else comes up I will post it. This is a awesome program!
[Touch Pro2, Tilt 2 Themes and Apps] smithisize:
I've also experienced this. Idk how to fix it either :/
[Touch Pro2, Tilt 2 Themes and Apps] wmg316:
I don't beleive the time stamp problem is not caused by OCT; try this thread/post here. HD2 thread...but works on Raphael and Rhodium.
[Touch Pro2, Tilt 2 Themes and Apps] Rickgig:
I guess I just assumed it was OCT causing the problem. I have had SMS texts where the time was off a little but nothing like the 4 minutes I experienced while I was runing OCT @ 710.4 Mhz.

I'll look at the fix you posted and research it a it before installing on my Tilt2.

Thanks for the post.
[Touch Pro2, Tilt 2 Themes and Apps] wmg316:
If it is any comfort...I install this on my Tilt 2...and installed on my Fuze prior to that...
[Touch Pro2, Tilt 2 Themes and Apps] NairobiWP:
OCT Icons

I made up some icons for the OCTool. Resolution 256x256. Modify size to your liking.

Enjoy
[Touch Pro2, Tilt 2 Themes and Apps] dayznfuz:
OCT and SOD

So, I've been playing with Netripper+Script and OCT for the last week or so. Did a bunch of testing with OCT in the last couple days.

Netripper's the most stable. Never get the SOD at 710, and almost never at 748. The one downside with Netripper's is you can't turn off the overclocking without reseting the phone. Makes booting up Android a chore. So I really want OCT to work.

But, OCT 1.5 is a mixed bag. I can invariably SOD with OCT in in the car. I'm pretty sure it has to do with cell tower switching or possibly roaming putting a burden on the CPU. I did a lot of driving around the neighborhood, and I've pretty much isolated the problem to the dynamic scaling. If I set step = 0. No SOD with a CPU speed as low as 350-ish. If I set the step to anything else (ie enable dynamic scaling), it SOD's within a minute, even with CPU speeds above 700 and a step=1 (resulting in a minimum CPU speed of 350). Btw, this is all with default interval, load values, and jump values.

So I think there's more to it than just minimum CPU speed. Switching CPU speeds while asleep is a big part of the problem. Last thing I tried was setting Load and Jump pretty high (60 and 80 respectively) to decrease the chance/frequency of CPU changes, and I didn't SOD. There must be a magic number in there somewhere, but I was starting to get some weird looks in the neighborhood on the 10th or so go around, so I called it a night.

Just thought I throw it out there for some smarter people to figure out. Oh, and I hard reset before all the experiments with OCT, so OCT was the only thing installed and running other than sense, WiFi, and BT. No contamination with Netripper.

Edited to add: Tried a Max Load at 50, and I SOD'd. Moved it back to 60, and no SOD in 24 hours.

--------------------

Sprint

TP2

Mr X Rom
[Touch Pro2, Tilt 2 Themes and Apps] dschoms:
I just spent 10 minutes keying in a statement that I'm running @768.0 along with settings and yada, yada, yada, and the stupid-ass website blew me out without the option of re-logging in. So screw the dissertation. I'm been running OCT 1.5 at 768 on Sprint for 2 1/2 weeks and it's been bullet proof.
[Touch Pro2, Tilt 2 Themes and Apps] uncleswoop:
oct at 768 on att tilt 2 for bout 2 weeks straight. only prob is gotta turn it off if i wanna run android. but since thats overclocked as well its really not even a problem.
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
OCT is still under development.

I Know that dynamic clocking is the cause for most / all of the problems reported here, so dont use dynamic clocking so far.

In Version 1.5 I changed the dynamic stepping due to performance issues jumping from very low speeds to high speeds. As a consequence it is not possible to choose a min speed by frequency as requested and possible in 1.4.x. I am sorry, but thats life.
[Touch Pro2, Tilt 2 Themes and Apps] babi3036:
Any help to uninstall?

How to remove? i can't get it removed!
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
Go into the folder for OCT, click on the OCT_stop icon which stops the service,

then try to remove it.
[Touch Pro2, Tilt 2 Themes and Apps] redpoint73:
Good info. I've been running OCT 1.5 for a few days now, and the only time I've gotten the SOD is after ending a call while in the car.
[Touch Pro2, Tilt 2 Themes and Apps] smithisize:
With iwfratz's OCT, I can get a stable overclock at 768MHz, but I can't enable dynamic OC, or else I get SoD after calls.

So, I just set interval to 0, and it's golden.

0 SoD's since I've done that.

Regards

Smith
[Touch Pro2, Tilt 2 Themes and Apps] redpoint73:
I like them! I was looking for some suitable icons, and these are great. I already have your icons installed on my phone.

Thanks so much!
[Touch Pro2, Tilt 2 Themes and Apps] agrickard:
I have been running OCT 1.5 for over 24 hours now and no issues what so ever. Full animation on CHT flies! No real change in battery life, so may try without dynamic clocking.

Settings:

CPU max: gradually increasing - up to 729.6 MHz so far

Interval: 500 (did have it at 1000 for an hour or so then read somewhere here about lowering it)

# steps: 1

load max: 30

load min: 15

jump max: 50

jump min: 3

p.s. Never tried Netripper's app
[Touch Pro2, Tilt 2 Themes and Apps] DutchDanny:
Icons are made now, in the next update they will be there...
[Touch Pro2, Tilt 2 Themes and Apps] twolostminds:
This is awesome!!! Going to give it a shot on my VZW TP2 running MightyROM
[Touch Pro2, Tilt 2 Themes and Apps] cmd512:
Mine SOD'd after ending a call in my study room. So, unless my house turned into a UFO and was flying between towers without me knowing, call SODs are probably not tower related.

Plus, iwfratz already said that OCT's dynamic clock is causing most of the problems and to not use it. That's all I needed to hear.
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
I was one of the ones getting random freezes etc with 1.5 and back to 1.41 as well. Turns out my fix was putting all settings at 0. I got my first-ever phone call SoDs yesterday and today, both while I was running StopWatch and with sleep-on-call enabled, dunno what that's an indication of though. No more freezes like I was getting with just polling at 0 but other settings higher than 0. I put a shortcut to OCT_Toggle on SD and a shortcut to that in Startup, no startup freezes like I'd get sometimes before.

A side note- I used to be able to clock to 768 stable, and still can with MSM7K, but OCT freezes for me now at that speed, and at one speed lower as well. Shrug. Still feels faster at 710 than MSM7K at 768 due to lack of script-related lags. I'd used SKTools to check CPU usage running MSM7K+Script and MortScript was always using 4 to 8 percent of CPU cycles, bummer.

I had a few ideas for features in future versions, implemented as toggles or check boxes maybe:

Disable/enable dynamic clocking (though it's already been suggested)

Disable/enable OCT during sleep (might help people with SoD issues, though I know you say you've a fix for it in future version)

Disable/enable OCT during calls (ditto above)

Disable/enable delay before applying OC settings (for people with Startup shortcuts and occasional boot-up freezes)

Also, just got paid, so I'm sending over some bounty money. Thanks for making my Rhodium 20 to 45 percent faster in one easy step.
[Touch Pro2, Tilt 2 Themes and Apps] BeanAnimal:
How about a little personal responsability?
[Touch Pro2, Tilt 2 Themes and Apps] Maxx134:
I am curious to know, with your experience on "MSM7K+Script " and "OCT app" if you have also tried the other app based solution, "setcpuspeed 1d cab" ? for the MSM7K app..
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
Negatory. At the point SetCPUSpeed was made, I'd had MSM7K and OC_Auto2/3 working fine, so I stuck with that. I switched over when OCT came out, partly to see if it was any good, and partly for its one-stop appeal. It's worked OK for me so I just stuck with it. Probably a lot of people running SetCPUSpeed saying the same thing, lol.

EDIT: Just remembered one thing in particular that helps tip me towards OCT. I use S2U2, and MSM7K always made S2U2 seem stuttery coming out of sleep as it did all its checks and adjustments, while non-dynamic OCT makes on-wake S2U2 run like butter.
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
"New" tilt 2 rom

Weekend, off for three days, installed the release version of the "new" AT&T tilt 2 rom from the HTC site, OCT running, all options zero'd, running 768 no issues yet, but, the phone isn't being used "as hard" LOL.
[Touch Pro2, Tilt 2 Themes and Apps] tedya:
Question: OCT 1.5 on latest Mighty Rom

Hi folks. Is OCT 1.5 safe to use on latest Mighty Rom?

I have Sprint TP2 running latest Mighty Rom.

Thanks.
[Touch Pro2, Tilt 2 Themes and Apps] dayznfuz:
Not saying that changing towers is the problem. I'm saying changing towers puts stress on the CPU. It wants to dynamically change, but can't because it's asleep. Just my theory. Drive around with the OCT GUI running and watch (actually, to be safe, have somebody else drive and you watch) the CPU load/speed. It'll occasionally jump for no reason that I can tell.

It seems that every time I get a SOD is because there was some process that wants to happen when the phone is asleep. The other sure fire way to get a SOD for me is to schedule/run an Autoreset. It'll reset fine if the phone happens to be awake. It always SOD when asleep. There's probably a CPU load as the program wakes up and tries to reboot the phone. Since bumping the Jump Load to 60, I've had no SODs in 48 hours. (Edited to add: Just reinstalled Autoreset and checked. There IS a CPU load. It jumps to 39% on a CPU clockspeed of 375. I tried Autoreset at my current Jump of 60, and it works fine).

Just putting the info out there, because if what I'm thinking is true, fixing the SOD issues could be as simple as having the program automatically disable dynamic scaling or increase the Jump when the device is asleep.
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
1st SOD

Running the new release version of the at&t rom, in Titanium mode, BT, OCT

1.5, 768mhz, all options set to zero. After a phone call, hung up the call via BT,

and every once in a while, I heard a pop/crackle. Tried to wake the phone up, it was doa until a soft reset.
[Touch Pro2, Tilt 2 Themes and Apps] madatoryloginlol:
It says that the installation was unsuccessful and then when I reboot and run the program (all three shortcuts) I get this error.

I have tried to install to both my device (Sprint TP1) and SD. That didn't work, so I manually located all the registry entries, deleted them, rebooted, and reinstalled. Same thing. It doesn't uninstall either.
[Touch Pro2, Tilt 2 Themes and Apps] lovingHDTV:
I don't know if this works for a TP1. I do know it works for a TP2.

dave
[Touch Pro2, Tilt 2 Themes and Apps] agrickard:
729.6 MHz seems to be the sweet spot for me - occasional SODs when increased above that. Have kept all other settings the same, although did try all other settings at 0 for a bit but battery seemed to plummet (well, even more than usual!).
[Touch Pro2, Tilt 2 Themes and Apps] madatoryloginlol:
Others have been successful with the TP1.
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
oct 1.5 w/official release rom

Had 2 more SOD's after calls with the "official" release version of the at&t rom.

Went back to my custom rom, no issues.
[Touch Pro2, Tilt 2 Themes and Apps] crimsoncadillac:
My first SOD

I had been running the OCT tool without any SODs and had been playing around with clock speed increasing a step at a time just for my own sanity testing. At 710.4 was running well with all dynamic settings off, new ATT stock ROM then I got a call. Had been working great with many calls. Then i had the after call SOD. But I found the anomaly to that call. Call waiting apparently caused it. As my desk phone rang with a client saying they just tried my cell.

Just tossing that out there as information for people looking into the SODs. Awesome tool and hopefully with testing like this someone can figure out those little quirks.

Crimsoncadillac
[Touch Pro2, Tilt 2 Themes and Apps] tytnhunter:
Been running these settings for a week with no issues. Thanks for posting!
[Touch Pro2, Tilt 2 Themes and Apps] jh20001:
I have been doing the same. Running on AT&T new official rom (with the updated sense). The OC seems to work just fine but the phone loves to randomly slow down and lock up (seems like it panaics when it has to multi-task like getting a txt msg while you just clicked on the calendar tab). The problem related though I believe are heavily related to AT&T's ROM and not the OC.
[Touch Pro2, Tilt 2 Themes and Apps] smithisize:
We need a new version of OCT or netripper's tool, anything to address, once and for all, the SoD's.

Doesn't matter what settings I try for either tool, I still get SoD about once a day. Annoying as heck, but without the OC, TP2 would almost be unbearably slow running sense vs TF3D so I guess I shouldn't complain.
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
If you look back a few pages, you'll see he's confirmed there's another version on the way. He says it should address some SoD issues.
[Touch Pro2, Tilt 2 Themes and Apps] eried:
Very wonderful app!

I have a few suggestions :D :

-interval_when_cpu_max (for example, interval 1000 always but 10000 when cpu_max because I am using the device)

-jump to cpu_max when resuming / waking the phone

Thanks so much! this app surely deserves the bounty :o

___________________

My settings (3 hours without problems):

TP2 Rhodium Verizon

-CPU max: 710,4

-4 steps

-load min/max: 5/15

-jump min/max: 3/20

-interval: 3000
[Touch Pro2, Tilt 2 Themes and Apps] outchard:
my htc diamond2 topaz with CHT was never so smooth, great job, thanks!

my settings: CPU max 652.8 / CPU min 249.6 and putted OCT_Run.exe in startup folder...
[Touch Pro2, Tilt 2 Themes and Apps] mr.horndoctor:
Agreed! :D
[Touch Pro2, Tilt 2 Themes and Apps] JDog2pt0:
I wouldn't mind some interoperability with nuedyanmicclock. If I OC and use Ndc to underclock (and undervolt to improve battery life) and use the phone which restores the highest clock, instead of jumping to either my OC or at least highest phone default, it only goes to half of what the OC is. Granted, this may have more to do with Ndc than OCT.
[Touch Pro2, Tilt 2 Themes and Apps] derrickadams:
I played with OCT some and it caused my phone to lock up and act strangely. I didnt up the OC any, just used default settings.

Didnt really seem to improve things to much for my current usage amount. Will prolly play with it some more with a new version.

Curious, if OCT did dynamic O/C would that help improve battery life?
[Touch Pro2, Tilt 2 Themes and Apps] Outlaw78a:
Worked perfectly for me from day 1(of the 1.5 of course)

but i sometimes forget to go back to default before booting android...

An icon for the OCT-GUI would be appreciated though,but great none the less.
[Touch Pro2, Tilt 2 Themes and Apps] Echolac:
Guys...how do you change the interval value for OCT v1.5?
[Touch Pro2, Tilt 2 Themes and Apps] levp:
Save settings?

I would like to know this as well, since I'm flashing ROMs at least once a week...
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
Just tap on the box that has "1000" for polling interval, type in new value, click "set" then toggle off/on a couple times. Or set it to "0" for static CPU value, no dynamic clocking.

He has this to say:

Users have made icon sets of their own for all three parts (start, stop, gui) here and here:

http://xdaforums.com/showpost.php?p=7756827&postcount=547

http://xdaforums.com/showpost.php?p=7953291&postcount=651

Easy utilities for changing the icons here:

http://xdaforums.com/showpost.php?p=7806059&postcount=581
[Touch Pro2, Tilt 2 Themes and Apps] tytnhunter:
Uh oh first bsod today. I flashed the new nrg cookie rom and enabled quick menu. I'm getting bsod after every call
[Touch Pro2, Tilt 2 Themes and Apps] notilad:
It freezes the diamond when started. Any solution?
[Touch Pro2, Tilt 2 Themes and Apps] notilad:
Actually, it works on AC (love the speed!), but freezes on Battery.
[Touch Pro2, Tilt 2 Themes and Apps] FL5:
OCT's settings are saved in the registry. Back up the keys at:

HKLM\Drivers\BuiltIn\OCT