yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Themes and Apps] oruam57:
I had a pair of "freezes" (that is the phone blocked completely during some operation, not SOD) with 1.5 so two day ago I reverted to 1.4.1 From then on I had no problem (as my phone only tolerated 633 MHz the 1.4.1 upper frequency limit did not bothered me and I did not use dynamic clock nor for 1.5 neither for 1.4.1)

Now, maybe I am wrong but considering also the recent reports of SODs with 1.5 I have the definite impression that 1.4.1 is more stable than 1.5

For 1.5 iwfratz did "internal optimizations for speed and stability". Maybe he optimized a little too much :rolleyes:
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
1.5 stable

Running 1.5 on SD card, not automatic, 691mhz, zeros in all other columns, Titanium interface,

Custom rom, stable so far, no issues.'

****

Let me clear that up about the automatic part. I don't have it set to run on bootup,

After the phone starts, I start it up manually, if that makes a difference.

I thought about setting a startup file, since it is on the SD card, it would be just a matter

of popping the rear cover, pop the SD card and reboot, but

A. I'm lazy

B. You know it would lock up somewhere inconvenient, you'd pop the SD card out and lose

the card.
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
I didn't have a chance to get 1.40 before it was replaced, but here's all other released versions:
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
...just for completeness
[Touch Pro2, Tilt 2 Themes and Apps] monomer888:
I would also like to report my experience with OCT 1.5.

I've been trying a similar setup.

1) I've installed after a fresh ROM flash and have never ever used Netripper's app.

2) Settings were set as follows:

# of steps: 1 (Speeds 691 & 691/2)

Interval: Set to 1000ms

Jump/Stepping low & high: all 15/30

The device ran fine for about three hours, I had a 'freeze' when waking the device up to use Opera. I then set the interval rate a little higher, choosing 1111ms (because it was easy to type in :p ) to see if that helped. I had no problems for about sixteen hours, and then again the device 'froze' when I woke it up to check email.

I'm not sure what defines a SOD, but my phone definitely was able to wake up and switch the screen on. It just then refused to do anything else.

Anyway I may try running the device at stock speeds for a while just to make sure the freezing isn't down to something else.
[Touch Pro2, Tilt 2 Themes and Apps] Kenno78:
Have you taken a phone call without it freezing afterwards?
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
3-4 with no lockups. Placed calls, received a couple.

My phone isn't getting the voice call load this week as I'm teaching a machine

class, but the emails, text messages have been coming in, no lockups.

I'm using pocketshield as the screen locker, if that helps.

Also, if it helps, I'm using this rom.

[06/1/2010] RRE™ T²-Series 2.5 build 23569 v6.7 - No Manila-TEST BUILD
[Touch Pro2, Tilt 2 Themes and Apps] cmd512:
Interesting, you got the same "frozen screen" as I did when the device actually already came out of sleep (screen was on after a call, screen froze and all 4 buttons below on my unbranded TP2 stayed lit). This is unlike the other OC tool where it would go to sleep/"screen off" and never come back on (before using the proper scripts).

Maybe this is just a glitch iwfratz can fix in the next release!
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
Some information:

1) There was the desire for a single file to toggle OC. The attached OCT_Toggle.exe will do it but will not unload the device driver. Therefore you must use OCT_Stop.exe.

2) For the first time I suffered the reported uninstall problem. Actual I analyse what's the problem and have the chance to solve it.

3) Even if I do not have SODs I am still working avoiding this. It is very hard to solve a problem without the possibility of reproducing it. Please keep reporting issues and specify details (cpu, cdma or gsm, rom) so that there is the chance to recognize some pattern. Thank you.
[Touch Pro2, Tilt 2 Themes and Apps] cmd512:
Thank you for your continued efforts, I look forward to continue testing out your app.

Here are my details:

1) H/W: Unbranded Rhodium Touch Pro 2 (GSM)

2) S/W: Latest EnergyROM w/ WM 6.5.3 (details in signature)

3) Failure mode: Immediately after call ended, phone went back to home screen and froze w/ screen on. All 4 H/W buttons below (Send, Home, Back, End) were lit and stayed lit. Had to remove battery to reboot.

4) Uptime: Failed ~7 hours after install

5) Previous OC tool installed?: No.

6) OCT Settings: 1 stepping, speeds = 729 & 729/2, up/down = 10/10 for both stepping & immediate max/min, polling interval = 1000 ms.

Hope this helps!
[Touch Pro2, Tilt 2 Themes and Apps] lovingHDTV:
I've been doing some testing of my own.

ROM: Energy 23129 Aug13

Phone: Sprint TP2

My testing was to just play mp3 files located on my SD card with the screen off using window media player.

Test #

1. Started OCT upped CPU to 710, kept everything else default - hung within 2 minutes, had to soft reset

2. Started OCT upped CPU to 710, changed steps to 1 - hung withing 10 minutes, had to soft reset

3. Did not start OCT, played for > 30 minutes never hung.

4. Started OCT upped CPU to 710, changed steps to 0, - placed for > 30 minutes no hang.

So I do get hangs, but only if I use the dynamic settings.

dave
[Touch Pro2, Tilt 2 Themes and Apps] wmg316:
On day 3:

At first I used the default settings...and with the "dynamic" clocking, I experienced the freezes. From reading other posts, I decided to disable the "dynamic" clocking and tried these settings:

Day 1

CPU MAX: 710.4 Mhz

# Steps: 0

load max: 0

load min: 0

jump max: 0

jump min: 0

I ran this for a day with no freezes/SODs

Day 2....and still running today:

CPU MAX: 672.0 Mhz

# Steps: 0

load max: 0

load min: 0

jump max: 0

jump min: 0

No freezes/SODs
[Touch Pro2, Tilt 2 Themes and Apps] ///M Class:
I look forward to testing iwfratz's app, however, my current setup is running extremely stable. I had issues with SOD's while running the "Core Cell Evo" ROM. After switching to the latest "Energy Dinik Glass" ROM, while utilizing SetCPU 1.0d (787Mhz/528Mhz-throttled, 175ms, phone sleep=0) I have not had any issues. To those who have used the new app, would you recommend task29/ROM reinstall before testing, or simply uninstall the SetCPU script?
[Touch Pro2, Tilt 2 Themes and Apps] Doo Doo:
i'm running the core cell evo rom & i have no issues of sod's or anything else running netripper's app + script method

with netripper's app + script i run 729mhz all day long & it throttles down to 604mhz during calls & when phone is put to sleep to prevent sod's

i tried iwfratz app but got sod's during phone calls so i reverted back to netripper's app
[Touch Pro2, Tilt 2 Themes and Apps] JVogler:
Toggle.exe works great. Now you only need to dedicate one mapped to key to control your cpu speed from any program!
[Touch Pro2, Tilt 2 Themes and Apps] ///M Class:
A bit off topic... Not sure if it makes a difference, mine was the full version of 3.0, not chef's. I tried task29, install, core restore, then overclock with no luck. I attempted another task29, install, no core restore or PIM restore and still had the SOD issue with anything over 528Mhz. Since installing Energy everything works great. I did notice, however, the Core cell ROM was much snappier and ran with 35+ MB's more free RAM than Energy. Both look great from an aesthetics standpoint.

Also note, I would like to add $10 toward the bounty.
[Touch Pro2, Tilt 2 Themes and Apps] skooter2:
To set the record straight................

1 I did a B/U with sprite BEFORE installing Netrippers app and Oraums script

2 5 Days at 729 no problem

3 HARD RESET / restore from backup/ installed Ifwratz 1.5 SOD

4 Hard Reset/ restore from backup / re install Netripper /Oraum script

5 2 days now with no problem.

THIS IS NOT 100% by ANY stretch of the imagination!!!
[Touch Pro2, Tilt 2 Themes and Apps] deeznuts:
I agree, maybe this dynamic feature is whats messing things up? I also run the same exact settings with max set to 672mhz so it runs it at this speed 24/7. 3 days now and still not one freeze or sod! Use for multiple calls with ease, missed calls, receive/make calls, zero problems! Im using ATT branded Tilt 2 device (htc touch pro 2) which is GSM network with NRG's latest Max Sense rom on 21911 build with pagepool set to 16mb so i get some more free ram. Loving this app, had no reason to ever go past the current speed of 672mhz i have it set at! Thank you!

Since many complain about problems with calls, maybe iwfratz can add a toggle to set a desired speed while during/receiving/making a call? Just using cprog.exe in general which is the dialer. For me though i have zero problems in this department. Ive never tried nettripper's OC app, had no reeason and dont like apps that require mortscript. This is the only OC app ive tried and loving it, no reason to try any others!
[Touch Pro2, Tilt 2 Themes and Apps] atticus182:
I am using the DeepShining's ROM on a HTC Touch Pro 2 (EU, unbranded)

When I am using the dynamic stepping with steps >1 or speed >710.4 the phone has SOD's regularly, but when I use the following settings it's working fine :)

CPU MAX: 710.4 Mhz

# Steps: 1

load max: 25

load min: 3

jump max: 25

jump min: 3

Interval: 200

And uhm when using the following settings it works fine too, but that's without the dynamic stepping :)

CPU MAX: 710.4 Mhz

# Steps: 0

load max: 0

load min: 0

jump max: 0

jump min: 0

Interval: 1000
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
1. Who told you I didn't use Sprite ? I currently do not use it (I use PIM backup) but I was using it before... So i do know it takes on CPU power

2. OK got your point. That's pretty weird. Don't count on me to reinstall Sprite I don't want issues with my phone :)
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
Ouch that's bad... So far I was lucky enough to have no SOD during calls

I have 200 ms interval and 5 steps, maybe it does make a difference

have you also tried stressing your CPU @ 729 Mhz ? I don't believe you clock it too high if you never experienced any crash at that speed but who knows...
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
That's gonne be very difficult to fix given the fat that some users do not experiment it and the ones who do don't have issues systematically

That said it's very possible it comes only with certain sets of parameters. The best would probably be that people experimenting SODs take out the dynamic feature to see if they still do have issues (It seems some people do better without).
[Touch Pro2, Tilt 2 Themes and Apps] lovingHDTV:
I was able to get a freeze last night with my max cpu set to 710 stepping 0. I was playing mp3s off my sd card and that played for about 3 hours straight, no problems. This I started playing around with the library, browsing through stuff and it froze.

Maybe I'll copy some mp3 files over to the device and see if it is an issue while accessing the mp3 files on the sd card.

dave
[Touch Pro2, Tilt 2 Themes and Apps] yan2x1987:
will this work on blackstone????
[Touch Pro2, Tilt 2 Themes and Apps] garyf:
My sprint touch pro 2 running energy rom 6.5 aug. 10 gets consistent SODs when playing mp3s on nitrogen while going into suspend. Not every time, but on every setting I've used within an hour or so.

I've hard reset and I'm about to try 672 with no stepping.
[Touch Pro2, Tilt 2 Themes and Apps] cmd512:
Yeah, I'm almost certain it's from the dynamic settings after a call completes, but then again, dynamic settings are what make iwfratz's tool so great. I do hope he figures it out.
[Touch Pro2, Tilt 2 Themes and Apps] robseargeant:
Still running the 1.4.1 with NP.
[Touch Pro2, Tilt 2 Themes and Apps] prag16:
With variable speeds enabled, I was getting SODs playing music with 1.5 on any clock rates higher than stock.

With 1.4.1 I have not had this problem a single time when using variable speeds.

So this seems to have something to do with the way 1.5 handles the dynamic frequency changes...

1.4.1 is fine but I would like to be able to step up the frequency a bit; perhaps iwfratz could release a 1.4.2 version: Identical to 1.4.1, only removing the frequency cap and NO other changes??
[Touch Pro2, Tilt 2 Themes and Apps] cmd512:
Very interesting find, thanks! So, it looks like the freezes are only with v1.5.

Yeah, like the other person mentioned, iwfratz did some tweaking to the code for 1.5 in addition to removing the cap, so maybe something got tweaked a bit too much. :)
[Touch Pro2, Tilt 2 Themes and Apps] DiAbLoxx83:
OCT 1.5 unistall don't work
[Touch Pro2, Tilt 2 Themes and Apps] prag16:
Side note, I'm not sure what the plans are for the netripper app, but the fact that it cannot stand alone 100% disqualifies it (IMHO) for any bounty consideration as of right now...

And yes, it sure does appear that 1.5 broke something. what I did NOT try was 1.5 WITHOUT variable speeds...
[Touch Pro2, Tilt 2 Themes and Apps] anit77:
I am using aruppenthal's ROM RRE™ T² V6.8 and have been overclocking for a little over a week now. Also I have not re-flashed or hard reset since the end of June. So to say I've had very few issues is an understatement.

With V1.4.1 I set the min clock at 384Mhz no lock ups & no freezes.

With V1.5 I am using:

Interval = 1000

CPU max = 729.6

# steps = 1

Load max = 50

Load min = 15

Jump max = 50

Jump min = 3

No Issues!

The only freezes I've had have been the result of raising the clock to high. At 768 I had a freeze while using Bing, the same freeze at 748.8. I routinely use CorePlayer & Windows Media while texting both sms & mms. At my current settings I've made & received dozens of phone calls with out 1 lock up releated to overclocking. There been known issues with mms and I think I've had fewer problems since overclocing.

I only problems that I've had have been uninstalling previous versions. I used the demo release of SKtools to clean up those removals. V1.4.1 uninstalled without a hitch, no need to use SK.

Lastly I wanted to share something else I've tried. The latest version is the only one I installed on the SD card. After finding everything stable with my current settings I added a short cut to Startup. Then I got to thinking about the boot order and after a little searching I found I could use SKtools to rearrange the it. I set OCT_Run to #2 and it really shortened the boot time for me. I didn't time it but I'd say it shaved a good minute or 2.

I'd like to see if anyone else tries this and sees an improvement with their boot times.
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
V1.5 working for me since the hour it came out, did various benchmarking to find my ideal speeds/settings and not even one SoD or freezing since then no matter if I play a game or listen to music or nothing.

Wonder if the people who it freezes on are running Window Mobile 6.5.x or whatever?

Anyway if I had money I would donate because, for me, V1.5 is a finished product :).
[Touch Pro2, Tilt 2 Themes and Apps] cmd512:
I'm glad it's working out for you.

And of course, the stability any of these dynamic clocking tools are seemingly software dependent at this point. That's why some people won't see SODs if they have certain apps running in the background but their sys will freeze when the app is not.

Ultimately, some of us chiming in they never get SODs vs some folks that can consistently show they have SODs = there are still bug fixes needed. In the end, that's all I really care about.
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
I've been busy w/work the past couple days, but just wanted to chime back in...

I have 3 phones here, all T-Mobile hardware running on AT&T. All running v1.5, running at their safe speed (see note), no dynamic clocking (all zeros), all are running rock solid stable. Sorry to hear that others are still having trouble.

* I still believe that some of the people who are having trouble may just be clocking their CPU far too aggressively. If your CPU crashes immediately at 806 MHz, but you think it "works fine" at 787 MHz because you were able to play solitaire for 5 minutes, then your problem is NOT OCT...
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
1.5 no issues

Ran 1.5 all day at 691.2 with all the options at zero, no issues. Wil

try 729.6 tomorrow.

GSM, at&t, tilt 2, custom rom, installed on SD card, not set to run on reboot.

Battery set to dim display @ 3 min, turn off @ 5 min

When connected, dim display @ 5, screen off @ 10

NOT using the sense UI, titanium on this phone.

OS version reported: 5.2.23568 (23568.5.5.0)

Rom: RRE 23554 WWE

Rom Date: 02/04/10

Radio: 4.49.25.94

Protocol version 61.44ftc.25.38.u

Screen lock, latest version of pocket shield (paid), locking on stylus out/in.

Locking & blank screen on call/end call.

I use a BT headset 100% of the time also, MS voice command enabled.

Hope this helps, so far, stable, will boost the speed for tomorrow.
[Touch Pro2, Tilt 2 Themes and Apps] cmd512:
Maybe, but I do not think this is the majority. I can run day and night at 729 with the other app plus scripts. OCT also ran fine at that speed too, but crashed the phone when it tried to dynamic switch after a call.

So the 1.5 issue surrounds the dynamic speed change, those running at 0 stepping probably will probably not see the issue.
[Touch Pro2, Tilt 2 Themes and Apps] Doo Doo:
i run 729 day & night with the other app + script aswell

but when i used OCT i was running it at 729 with 0 stepping & got sod's during calls so idk :confused:
[Touch Pro2, Tilt 2 Themes and Apps] wmg316:
I have run OCT 1.5 since Friday. I cannot get it to Freeze/SOD at 672, 691, or 710 ... RUNNING all zeros (i.e., no dynamic clocking).

I can however always get it to freeze and/or SOD with the dynamic clocking set....using phone...using playing mp3's.

I am thoroughly convinced there is nothing wrong with 1.5 WITHOUT the dynamic clocking...and that the bug is in the dynamic clocking!
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
I do not think that dynamic clocking is a BUG. maybe a problem ;)

In 1.5 the dynamic clocking changed due to the latency jumping from low to high speeds. There are some things I could/have changed, so please wait for the next version.

If this wont help, we have to abstain from dynamic clocking.
[Touch Pro2, Tilt 2 Themes and Apps] ioandancus:
Hi. I am running OCT1.5 from a couple of hours and everything is working fine.

My settings:

CPUmax = 768 :D

#steps = 1

Load max = 30

Load min = 15

Jump max = 50

Jump min = 3

Interval = 2000

Unstable if using CPUmax = 787.2 or 806.4

In the last hour I am running it with #steps=15 and Interval = 1000 and everything is stable.

I am using Energy.RHODIUM.23129.Sense2.5.Cookie.GTX.Aug.7 ROM with 4.49.25.88 Radio.

Edit: SOD during a phone call. Maybe #steps=15 is to much. Now I am trying 2.

Thank you iwfratz :cool:
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
The thing is the dynamic clocking is not "that" necessary: it wont change much in the battery life (Someone published interesting drain test in this thread) but it's fun and probably worth it to limit the heat generation of the phone
[Touch Pro2, Tilt 2 Themes and Apps] anit77:
I hear you guys but I really think there is more to it than just dynamic OC. I have not had a freeze playing mp3's or sending/receiving phone calls.

I believe you must look at this just like rom development to sort out the bug in that you have to look deeper than the OCT driver. If your having an issue with SOD's and lock up's then you should list everything you have installed on your phone. ROM, Radio, Programs & all tweaks. Try using OCT on a fresh flash and see if you experience problems, then install your programs one at a time to see what is causing the issue.

It may not be necessary but just like overclocking a cpu in a computer it will shorten the life of it. OC'ing hand held processors is relatively new and we don't know what the effects are over time.
[Touch Pro2, Tilt 2 Themes and Apps] mmalka:
I am using Sprite Backup 6.5.5 Build 6 and OCT 1.5 without making those changes and everything is working fine. It could be due to the difference in build or because we have different devices.
[Touch Pro2, Tilt 2 Themes and Apps] wmg316:
Nor do I!!! :eek:

I would love to have dynamic clocking work. But for now, there is a "bug" in the process that causes dynamic clocking not to work for many people...which will hopefully be straightened out. :D
[Touch Pro2, Tilt 2 Themes and Apps] mmalka:
Same issue here. Details:

- Phone: AT&T Tilt 2 (Rhodium) - GSM

- ROM: EnergyROM CHT 23129 of Aug 13

- OCT v 1.5, with CPU Max at 748.8 MHz, interval 100, and rest unchanged

Started Nitrogen and played a mp3. Played ok with screen on. Nitrogen has the option to turn the screen off while playing. As soon as turned the screen off the phone froze and I had to perform a soft reset.

Repeated it after the soft reset, with the same results.
[Touch Pro2, Tilt 2 Themes and Apps] cmd512:
I'm not interested in dynamic clock because it's necessary or I feel excessive heat on the back of my phone. In this day and age of processors, almost all of them support dynamic clock for a reason, to which I feel is a combination of several factors you mentioned. This is why this function is so appealing in iwfratz's tool, and I'll keep testing it out until the issues are ironed out.

My OCT v1.5 was installed on a brand new freshly flashed ROM. Other than Lotus Traveler and Microsoft Voice Command, I have nothing else running in the background other than critical system services. And frankly, I'm not willing to not run these apps for this tool to "work."

On that same note, I can run the other tool + scripts 24/7 at 729/604 throttle with 0 issues. So, in that sense, I would prefer to concentrate on the tool rather than turn this into an "app-hunt."

You should try the other app + scripts... works perfectly and throttles between 729/604.

PM me if you want details how to set it up, it's pretty easy to do.

I will keep playing with both tools until one is solid enough as a standalone. :)
[Touch Pro2, Tilt 2 Themes and Apps] mmalka:
Tried that and did not see any significant difference. It seems to me that Sense loads first and Sense is the one that takes longer to load.
[Touch Pro2, Tilt 2 Themes and Apps] DJGonzo:
I think this is very true. People need to start playing with settings. Like fastsleep when going into a call and whatnot.

Sorry, but overclocking PDAs and Phones is not a new concept. Its a very old one and I don't remember one instance where it broke a device.
[Touch Pro2, Tilt 2 Themes and Apps] JRocca:
Hey,

Not sure if it was stated or not, but when i run this, currently 1.5, and reset all the changes i made go back to a default. Is there a way to keep the setting
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
Just want to say iwfratz that I can't get SoD or freeze no matter what I'm doing lol. Everything is working for me, maybe we got the exact same phones or something?

I'm trying to see what might be causing other people to get these errors and such? Only thing I can come up with are either that:

It's the radio, their SPL version, or something from WM6.1/6.5?

But here are my settings if anyone wants to try it out? I CAN run it at 787 but it does freeze after a while when I'm heavily using my phone but just one speed below that and it's perfect :D!

CPU Max: 768

Steps: 1, was 2

Load Max: 40

Load Min: 16

Jump Max: 70

Jump Min: 60

Thanks a million iwfratz and please don't discontinue your support/work just because some idiots are posting "FIRST OVERCLOCKED ROM" in the ROM section :(.
[Touch Pro2, Tilt 2 Themes and Apps] mmalka:
On the GUI: Make the changes, click on set, click on OC on/off to start, click on it again to stop, and once more to start it. It should then be ok.
[Touch Pro2, Tilt 2 Themes and Apps] JRocca:
Yep that did the trick thanks
[Touch Pro2, Tilt 2 Themes and Apps] p51d007:
Even without dynamic clocking, at 100% battery at 10pm, I only lose 2-3% max

by 7am. With email checking every 30 minutes, and BT enabled (non visible) and no headset connected. Yeah, the dynamic underclock is nice, but at least for me, I'm not seeing any serious battery problems at the 690-720 range.