yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Themes and Apps] lovingHDTV:
V 1.4.1 appears to be working on my Sprint CDMA phone. At least I can see the dynamic clock changing in the GUI. I let the screen turn off, and was able to turn the phone back on.

So far so good.

thanks,

dave
[Touch Pro2, Tilt 2 Themes and Apps] ACoolGuy:
Ok so Sprint TP2 Running NRGrom w/CHT 21911 Aug6 with OCTv1.4.1:

Install went smooth.

Ran GUI and changed only Interval to 100ms. Then Ran OC.

So far smooth as butter. No matter how hard I try to get it to Freeze up on me using various techniques, I am unable to get a SOD. Sense seems a slight bit smoother from the Home Tab. Now just waiting on the speed ceiling removal to see if its stable at around 700 Mhz.

I then put a copy of OCT_Run into the \Windows\Startup folder and it does successfully run at startup with no problems.

Nice Job iwfratz!
[Touch Pro2, Tilt 2 Themes and Apps] dunebuggydude11:
so any estimate of when the app will allow for higher speeds? V1.5 maybe? It's working fine for me on my Sprint TP2 as well, but I'd like to be able to overclock it higher like with MSM7kcpuspeed.
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
+1

Installed v1.41. Everything works fine.

TMoUS Rhodium, HTC WWE 2.07, Sense 2.5. Have max=min=652 and polling=0, mostly because S2U2 needs all the help it can get when I wake up, and I've not noticed much change in battery life running 'hot' all the time.

Nothing else unique to add. +1 from me on can't wait to run the speed higher, and +1 on doing an amazing job. I can't believe how fast you're flying through this thing. Laser high fives all around.

EDIT: I don't know if the uninstall worked or not, as I used SK Tools to remove the old version.
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
I think when he does let it clock higher we are suddenly going to see a bunch of people from the "other" overclock thread show up here...

And remember everyone that virtual slaps on the back and "You da MAN!" are nice, but if your really want to show your appreciation, go click that "donate" button.
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
I read posts from oldest to newest... And was just answering to some old posts without having read the latest about your soft

However I disagree... You mentioned yourself there is a speed ceiling "at the moment there is a hardcoded limit of 650 Mhz"

Anyway great application, thanks a lot for the hardwork
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
Mistyping. SOrry for that
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
And with Netripper's app you have a very nice extra feature. SOD...
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
And I'll be one of the first of them. Can't stand the SOD in phone calls...

But the speed ceiling is holding me off from migrating for the moment
[Touch Pro2, Tilt 2 Themes and Apps] ACoolGuy:
Ok so I may have run into an issue. I let the device stay in standby for about 2 hours and when I woke it up and ran the GUI it showed 528mhz but showed running. I then stopped and started the OC and everytime I started OC it would default to exactly half of the min CPU frequency. I tried changing the min value and every time it defaulted to exactly half and the Load polling was not working at all. I restarted the phone and all is back to normal. I'll let it sit again and see what happens in a bit.
[Touch Pro2, Tilt 2 Themes and Apps] Doo Doo:
sorry to tell you but i been using netripper's app for about a 3 weeks now without any sod's :eek:
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
Lucky you. It's not my case and it's not the case of many users (I agree some do not experience it though). Didn't experience it initially though...

Anyway it just proves the application is not 100% stable and functional
[Touch Pro2, Tilt 2 Themes and Apps] lovingHDTV:
1.4.1 has been working great for me since I installed yesterday. I had it sit overnight just to see if it would wake up OK. Worked great! This is something that I always had problems with using the other program. For some reason after an extended sleep sense would hang and I had to soft reset.

I was playing with it yesterday looking at CPU speed/load when playing music with different music players. When I use windows media player it would underclock down to the lowest 96 Mhz, but using HTC music player it would only go down to about 311 Mhz. Not sure why HTC player requires more CPU than WMP, but that is what I was seeing.

Overall I really like the idea of dynamic clocking, though who knows if it will save any noticable amount battery life.

dave
[Touch Pro2, Tilt 2 Themes and Apps] unxguyjr:
I too had luck with netripper running scripted but found that after a few days memory usage was at 98%...prior to that I statyed around 75 and could run for weeks with out softreset. I have just installed OCT on my Sprint TP2 running Mr. X rom..we will see how things go in a few days.....would also like a little higher clock speed but ok for now...device still very smooth.
[Touch Pro2, Tilt 2 Themes and Apps] iti_uk:
£10 with the proviso that the overclock software automatically scales the amount of over/under-clock depending on processor load.

Chris
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
That is exactly how it works right now...
[Touch Pro2, Tilt 2 Themes and Apps] ACoolGuy:
Let it sit overnight this time and all seems well this morning. I am going to try letting the phone go into standby by itself this morning and check it again in a couple hours to see what happens. This is all with default settings except polling is at 100ms to avoid lag.

Also just a question for iwfratz. Is there any reason that upon opening up the GUI, for a split second before the polling begins showing it appears that 528mhz is shown as the clock frequency. Is it maybe that the program defaults this value until polling updates the value? Just observations.
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
it is the preset value for the text label. I used it to design the GUI aehm put the labels, textfields and buttons together. nothing of any importance, I could change it to #3D=4k-. :)

i hope that someone will design a nice and fingerfriendly GUI based on the descripted interface.
[Touch Pro2, Tilt 2 Themes and Apps] anit77:
I could not uninstall 1.3 using Remove Programs either. Same message as earlier posts. Oct_Stop was run twice & verified via GUI that it wasn't running, then ran Oct_Stop again for good measure. Also checked to be sure there were no running processes related to Oct. Only then did I try to remove.

Used SK Tools to fully remove it.
[Touch Pro2, Tilt 2 Themes and Apps] huggs:
Could you please attach Oct_Stop for me ?
[Touch Pro2, Tilt 2 Themes and Apps] prag16:
Poor benchmark performance with variable clock?

I have the minimum set to 111mhz, and max at 652. I do seem to notice slightly better battery life when i allow the CPU to clock down.

However when running benchmarks, the performance is MUCH WORSE than stock. I have all load/jump settings set as default.

So obviously the CPU is not putting its work in even though it's supposed to stay at 652 when it has full load. This is supported by anecdotal evidence that things aren't really any faster after overclocking. Changing the polling interval to 100 instead of 1000 to eliminate lag didn't seem to help either.

But when I lock the CPU at 652, I DO see the performance gains mentioned by others here. Any idea why this may be happening?
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
run the benchmark multiple time and you get different results each time.

Thats because many programs will run in background and consumes cpu time.

Try this:

- set polling interval above 1000 and something odd (e.g. 1234)

- finish all programs

- disable phone, WLAN, BT

- exit GUI !!!!

- do not move device (gsensor)

- run benchmark several times without pause

With this setup Linpack-WinCE-ARMV4I gives me nearly constant 2.17 MFlops .
[Touch Pro2, Tilt 2 Themes and Apps] ACoolGuy:
Ok so I got this issue again just a while ago. Went to 480 mhz or something and would not come out. Then when turning off oc and back on set to half the min frequency. from this point even if you turn off the oc it continues to run at half the min freq. It does not go back to 528mhz automatically. soft reset fixed it and I now am testing 652mhz as min and max with no polling at all to see if it ever does this again. Follow up tomorrow.
[Touch Pro2, Tilt 2 Themes and Apps] lovingHDTV:
I just checked my phone, been running OC all day, and now the gui shows 528Mhz and 100% CPU load. I check my CPU load in task manager and it is <15%

Not sure if this is a gui issue or a overclocking issue.

dave

Soft Reset fixed it.
[Touch Pro2, Tilt 2 Themes and Apps] prag16:
Unfortunately this is not the case. I tested several times and the result is consistent. At 652 I get good performance, at 652 with the minimum of 112 I get awful performance well below stock. If I set the minimum to 384, it helps, and my performance is better than stock. That's what I've done for now.

But this is RELIABLY reproducible, within a narrow range of performance results. There is definitely an issue (at least on my setup) with having lower minimums; CPU does NOT stay ramped up as it should...
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
I agree, I've notice it is actually slower the lower the minimum is at, and it stutters and lags a lot. I switched back to netripper's just for now since I never get any SoD's anyway and it is smoother.
[Touch Pro2, Tilt 2 Themes and Apps] JVogler:
Leaving the settings alone on default and running the OC tool makes my device lag more and actually slower. While I can get higher benchmarks, just navigating around the device is slower and jumpier than no OC @ 528. Must be all the polling and frequency change lagging me up?

Nothing I've tried has gotten a successful uninstall...I'm seeing people are having success with SK Tools for that though, so I will give it a try.

I can't seem to find any setting combination that actually keeps my device in an OC'd state. While from a technical standpoint, when I have it set to stay OC'd with no polling and min and max at 652...the result of actually using the device tells me it's not staying. When running NetRippers app at equivalent freq. it runs smooth. Anyone else experiencing this? or with solution?
[Touch Pro2, Tilt 2 Themes and Apps] Commdr64:
I've also noticed this with the 1.4 release. Unless I step the minimum up quite a lot, there's a pretty noticable hit in performance.
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
I personally don't care for dynamic clocking. I have both my MHz settings to 652, and *all* other settings at 0. Works perfect for me, stays at 652 all the time and rock solid stable... Those having trouble with dynamic clocking and lag might want to test this way.
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
It is an issue, I can confirm this. It's a rare system constellation I did not handle correct. Will be solved in the next release.
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
I believe there is a solution to that if iwfratz is ok to code implement it (it should not be too difficult). Processors can lose some clock cycle when throttling down or up and if they oscillate too much it may slow the processing. And besides it may oscillate too much (up and down and up and down)

If iwfratz is ok we should implement a minimum time (adjustable please) during whihc we dont clock down. This way when the CPU has clocked up, it doesnt clock down before xxx ms

That will definitely help

However it probably wont be enough. Maybe the main hurtle is the frequency at which your program checks whether the load is at 100%. For instance if you put your minimum speed at 100 Mhz, if you set the check interval at 200ms, then first time you check you clock to 120 Mhz. Then 200ms later you clock it to 140 Mhz, then 200ms later 160 Mhz, etc... In the end it will take you... 1 second to reach 200 Mhz. You can imagine how much this will ruin your benchmarks

One potential solution is to set a multiplier for the frequency increase (So not 20 Mhz by 20 Mhz but 40 by 40 or 100 by 100) or increase very significantly the frequency of load check (But the time at 10ms for instance)

We could also implement a non linear ramp up of the frequency. Something like if I increase the speed a first time after a dicrease I increase or 20 Mhz. if I increase again, I increase of 2x20 Mhz = 40 Mhz (So I am already up 60 Mhz), the third time 3x20 Mhz = 60 Mhz (total already up 120 Mhz). And if ever the load is mall I scale down of 20 Mhz and reset this multiplier (ie next time I re-increase only of 20 Mhz if the load is high). Same on the way down

Or we could go back to No2chem good old solution. A clock frequency for sleep, another one for idle and one for the normal usage... Not the most dynamic, but very efficient

All of his is easy to program. All up to you iwfratz ;)

If I had to choose I'd go for non linear frequency management + the minimum time before downscaling. They are I believe the most elegant solution & probably the most efficient
[Touch Pro2, Tilt 2 Themes and Apps] Commdr64:
I apologize for making my first comment on this thread a criticism. Let me use this post to say "Thank You" for such an amazing tool.
[Touch Pro2, Tilt 2 Themes and Apps] prag16:
I am still plugging along at 384 minimum. It seems that this is my sweet spot; I get the enhanced performance in the benchmarks, everything seems smooth throughout, and there seems to be a slight battery life improvement when running at 384 while idle rather than 528.

Thumbs up; waiting for the upper limit to be removed to see if I can run stable at 768 or so... Any timeframe on when that will be in a build? Any reason why it has not been yet? You can just pop it in there and just emphasize a disclaimer even more strongly that it is to be used at its own risk ;)
[Touch Pro2, Tilt 2 Themes and Apps] airvision:
Some Current Measurements of TP2 and OCT.

At first i want to congratulate member iwfratz for his research and his excellent utility.

Then i want to post some current measurements straight from TP2 battery.

The measurements was done as follows :

- Fully recharged battery.

- Digital multimeter Simpson 467 in series with the positive of the battery.

- OCT will not be loaded at the start up.

Results :

-The phone consumes 126 microAmpers (μA) at off status.

-Start booting from 250 milliAmpers (mA) to 428 milliAmpers (there was a peak at 778 mA)

- Selection of no connection to a mobile provider (no phone - no data - no to everything, just like a flight mode).

-After the full loading of windows about 2-3 minutes the TP2 current stabilized to 250 mA with screen on.

-After 1 minute the screen went to lower position and the current decreased to 150 mA.

Now the good stuff ...

-With nothing running on task manager and pressing the standby button to turn off the screen (and anything else ...) we have something that it is called "saving mode" which is :

for 1 second there is a consumption of 1.5 mA (sleeping)

after that it wakes up for some milliseconds with a current of 135 mA.

and the again & again sleeping & wake.

This duty cycle is continued until the standby button would be pressed again.

So, pressing the button again we consume around 250 ma. (screen on).

The above measurements was done with no OCT as i already said.(pure 528 Mhz).

Running the OCT now.

I lock the CPU to run 115,2 Mhz all the time (min & Max) via the the OCT.

I went to standby mode again and i had the same exactly result as i was running at 528 Mhz. (1.5 ma sleeping & 135 at wake up).

I did the same test for different under-clocking frequencies with the same result.

Then i locked the CPU to run at 652,8 all the time and went to sleep again.

The result was 3 ma on stand by and around 140 ma on wake up.

Pushing the button again & waking up the phone to be ready for normal use the consumption was around 270 ma.

So, what i understood for all this results is :

There is no reason to do under-clocking on TP2.

There is reason to do overclocking (we all know why !!).

If we want more reliable results there must be done with more sophisticated process (I mean jobs that cpu is running or peripherals to handle and all kind of stuffs) and more expensive instruments and more TIME .......

This is my personal opinion.

Thank all of you that you had the patience to read my post.

My personal settings for the OCT 1.4.1 version will be

652,8 max

518,4 min

all the rest as it is ....

looking forward for 750 mhz.

I will congratulate one more time iwfratz for his excellent utility,

and i will leave a question for anybody,

is it possible to change this interval time that HTC uses for stand by and wake up ?

Sincerely to all.

Dinos.
[Touch Pro2, Tilt 2 Themes and Apps] lovingHDTV:
Good stuff,

One question for you. When I underclock I was doing it for the purpose of when the phone was in use, playing music for example, with the screen off or on. I have my phone set to playback with screen off.

I can under clock the CPU to 96Mhz when playing a mp3 file and I can see that it will actually go down to 96 mhz during playback with windows media player. I was hoping that this would reduce the power consumption, but I wonder if that makes any difference, or if the audio amplifier, etc overwhelm the CPU power.

dave
[Touch Pro2, Tilt 2 Themes and Apps] airvision:
Nice test really.

I will make a .mp3 file with a single tone, lets say 1 khz and i will measure it

at low - central - hi CPU speeds.

Give me a day for this.

Thank you.
[Touch Pro2, Tilt 2 Themes and Apps] prag16:
Battery life

This is largely anecdotal to this point, but for the last day or so I definitely seem to be getting slightly better battery life with a 384-652 range than I did at a flat 528... Haven't measured it yet or anything, but I'll have to see how that holds up over more use. Looking forward to higher frequencies :D
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
to prevent stepping all the way from low to high there is jump_max: if the actual load is higher than this it will jump immediately to cpu_max

No, i dont like it.

I am working on the issue, and it will be solved soon.
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
jum_max i symetrical I guess... and the whole interest of what I propose is the asymetry

Why you don;t like the other solution ? It's a again a very classical way to proceed in professional algorithms... What do you think is the downside ?
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
Sorry, i did not get your point. What do you mean with symetrical / asymetrical.

Actual you can define jump_max for jumping up to the max cpu speed and define another trigger value of cpu load to jump to minimum cpu speed. Additional you can define the cpu loads to step up/down.

Choosing the loads for stepping 10% / 40% will be asymmetrical. seeing it from cpu-load, not from the step to make

Or what are we talking about ?? :confused:

It is an approach that define arbitrary power states like On, Backlight Off, Screen-Off, Suspend. But it has nothing to do with cpu usage or cpu load.

In state On (normally maximum CPU-speed) you can read an ebook, need some cpu-time every now and then. Or you can calculate some fractal pictures needing every cpu-tick it can get.

With Screen-Off you can solve some complex equitation in background or just playing music.

cpu speed is not determined by a Power State but by the work to be done. And a specific work will create a specific cpu-load.
[Touch Pro2, Tilt 2 Themes and Apps] Commdr64:
Although it's a bit over mind head, I'm finding this discussion fascinating.
[Touch Pro2, Tilt 2 Themes and Apps] Jackos:
+1 to this, very interesting and fascinating too! :D
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
Thanks for measurements and information. Very interesting !

But I do not understand how this come together:

Why WM power manager underclocks the CPU (not only suspend it), if it does not save power ?

OCT will not induce higher power consumption on underclocking, only on overclocking. Why is it so? The PLL frequency is lowest on OCT@115 Mhz, higher by overclocking @650Mhz, but highest in normal mode on 528Mhz ?

What makes the difference in power consumption ? OCT and PLL frequency wont, as you measurements tells. :confused:
[Touch Pro2, Tilt 2 Themes and Apps] airvision:
As i understand, with OCT you can change the frequency of the Core of the CPU.

The peripherals of the CPU "must" obay at the frequency of 528 and only this one.

I dont know if this is correct....
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
Asymetry: in the first idea I suggested you still step up immediately, but you dont step speed down before xxx ms. The way you scale up or down becomes asymetrical. but forget it, it was not what would help the most (though I think it's worth it

If you read me, that's absolutely not what I suggested as my favorite. I was talking about non linear increment / decrement of the CPU speed (And in my previous posts I already advocated against setting the CPU speed depending on power states). Just said moving the speed up or down depending on the power state was an option. Nevermind...

Coming back to the non linear stuff:

Define a variable that is the increment multiplier IncMult, initial value is 1

If CPU load>MaxLoad

If Last Speed modification was speed up

IncMult++

Else

IncMul=1

Endif

Set the speed at Current speed + IncMult * 20 Mhz (Actualy 19.xxx if I remember well) capped by Maxspeed

And the same on the way down

If CPU load<MinLoad

If Last Speed modification was speed down

IncMult++

Else

IncMul=1

Endif

Set the speed at current speed - IncMult * 20 Mhz floored by Minspeed

I guess you get the idea

First time the increment will be 20 Mhz, second time 40 Mhz, third time 60 Mhz

So for instance if you keep on being overload and you come from a speed of say 200 Mhz, you will have the speed following this path: 200Mhz - 220 Mhz - 260 Mhz - 320 Mhz -- 400 Mhz, etc...

Instead of 200 Mhz - 220 Mhz - 240 Mhz - 260 Mhz etc...

I guess you got the picture
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
Although all this is an interesting intellectual exercise, will it really give a measurable "real world" improvement? As I've said a few times, I just run mine at max CPU all the time and not worry about it. I understand that is not the best approach for everyone, but does it really need to get so complex? How about this nice and simple method: Anytime CPU is < 10% load, jump immediately down to CPU_min. Anytime CPU is > 10% load, jump immediately to CPU_max. Is all this scaling up and down really going to give you much more battery life than what I'm suggesting? Seriously, I would like to know...
[Touch Pro2, Tilt 2 Themes and Apps] JVogler:
I'm WITH YOU on this one! I've been religiously following 'both' threads for the last few months. It seems like a lot of effort is going into underclocking and dynamic clocking and the like. Which seems cool and like a good idea to start messing with after plain old OC is smoothed out.

I'm caught between both worlds right now...waiting for the good parts of each app to come together. NetRipper gets me to the high 700's but will randomly fail so can't be comfortable leaving it OC'd. iwfratz gets me stable speeds i can leave on all day with no worries, but won't allow me to set up to the speed I know my CPU can handle...so whatever comes first...netripper gets stable..or iwfratz makes it so I can clock higher gets my $25 donation...hopefully before i leave for vacation next week!