yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Themes and Apps] airvision:
a second consumption test

I am sorry for my delay to give you this consumption test.

(two kids & one wife ....:eek:)

Well, with an .mp3 file of a single tone of 800hz sinusoidal

I complete the following table.

As the previous test, the TP2 was at flight mode with full battery.

The windows mobile player was playing the 800hz file.

I did the test 5 times.

So, for someone who want to listen a play list of mp3's with screen off it is better to use the nominal frequency of 528 Mhz.

I really have to say that i am not an expert on digital electronics.

So i cannot answer why and how.

I just did some current measurements.

I like the overclocking utility of iwfratz and i just want to know about consumptions issues.

Thank you.
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
Good data ! Definitely what's taking the most juice is our screen... That said it's always worth tightening some bolts here and there, especially fi not for the sake of power consumption, just to limit the heat generated

I guess that your results show why Microsoft (and probably other phone OS makers) has never tried to implement variable speed. The gain is too small to be worth the pain
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
Your phone is the product of an intellectual exercise................

That said given the figures produced by airvision you are probably right. And it's super simple to implement (though less fun ehehe)

iwfratz: when do you remove the cap on the max speed we can set ? It's the only thing that holds me from switching from Netrippers application to yours

Honestly it's the biggest improvement that you can easily do in the snap of a finger. Please...
[Touch Pro2, Tilt 2 Themes and Apps] oruam57:
OCT_BKL V1.2

OCT_BKL is a small command line utility to control the OCT device driver developed by iwfratz (http://xdaforums.com/showpost.php?p=7463284&postcount=162).

OCT_BKL action depends on 3 numerical command line parameters (separated by a single blank character). The 1st one selects the action do be done:

1 - Set OCT off and terminate (e.g. OCT_BKL.exe 1)

2 - Set OCT off, set screen off, wait for screen on, set OCT on and terminate (e.g. OCT_BKL.exe 2)

3 - Set OCT on and terminate (e.g. OCT_BKL.exe 3)

4 - Set clock level at P2 and terminate (e.g. OCT_BKL.exe 4 33)

5 - Set clock level at P2, set screen off, wait for screen on, restore clock level and terminate (e.g. OCT_BKL.exe 5 10)

6 - Set clock level at P2, set screen off, wait for screen on, set clock level at P3 and terminate (e.g. OCT_BKL.exe 6 10 33)

P2 is the 2nd parameter value, the clock frequency is P2 * 19.2 MHz.

P3 is the 3rd parameter value, the clock frequency is P3 * 19.2 MHz.

For actions 4, 5 and 6 OCT_BKL sets both minimum and maximum clock levels to the same value, that is

no dynamic clock

.

For actions 2, 5 and 6 OCT_BKL tries to set screen off using TouchLockPro (http://xdaforums.com/showthread.php?t=444215). If you do not use TouchLockPro on your phone you should set the screen off yourself. In that case OCT_BKL waits for 2 seconds for the screen to go off. If nothing happens OCT_BKL completes the requested action and terminates.

For action 5 OCT_BKL gets the restore level from the registry where it was saved by the OCT_GUI utility.

For some more details read the ReadMe.txt inside the zip file.

As usual use OCT_BKL at your own risk, NO WARRANTY, blah, blah, blah... ;)

Edit: V1.3 in post # 382
[Touch Pro2, Tilt 2 Themes and Apps] gjcamp:
Thank you both IWFRATZ and Net Ripper for your hard work and excellent applications. You both have succeeded where others have failed and we now have a couple of viable OC applications for a device that sorely needed it in order to stay up to date with the latest incarnations of windows mobile 6.5.

At this point the only requirement on post #1 was to be stable at least 20%.

Both utilities are stable at the expected OC level of 20%.

Netripper’s implementation states it was not able to perform on battery power. This was confirmed by NetRipper himself and is not a very practical implementation as we are Mobile users.

IWFRATZ’s implementation was first to work on batter power.

Although NetRipper's utility was first, was it really fulfilling the bounty requirement as it only worked while plugged in?

Any other improvements are feature requests above 20% OC and stability. I do not want to stifle any future development on either of these applications but have we not achieved our goal.

It seems to me that IWFRATZ is the first with a stable mobile Rhodium OC app of >= 20% OC.

I hope to see continued development.

Cheers and Thank you.

Donation will be coming.
[Touch Pro2, Tilt 2 Themes and Apps] Filippios:
I'll donate 15$ if this really will works good for our devices :) Thx for idea and motivation!
[Touch Pro2, Tilt 2 Themes and Apps] Balajee:
No one is ready to try overclock working? All I see are bounty posts and no one coming forward to try getting TP2 to overclock
[Touch Pro2, Tilt 2 Themes and Apps] ron_samuels:
Put me in for 15 smakaroos also!:p
[Touch Pro2, Tilt 2 Themes and Apps] stevedebi:
I did some research on the net. Qualcomm will not release the detailed information about the CPU needed to unlock higher speeds. Without the correct detailed specs it will be difficult to change the required settings.
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
I don't know anything about anything, but XDAndroid seems able to overclock the Rhodium easily. Fundamental OS differences I guess?
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
Someone stated before that it's way easy to overclock on Android by simply "inputting a text line" or something because it's linux-based but Windows Mobile is all driver-based (I believe?) so it's a lot harder and the only guy I know of who was close and knows about the crappy processors we have was no2chem :(.
[Touch Pro2, Tilt 2 Themes and Apps] mech_supernova:
I wonder why notochem's Overclocker program for the Touch Pro dosent work on out Touch Pro 2, dont they both have the same prosessor? the 7201A?
[Touch Pro2, Tilt 2 Themes and Apps] stevedebi:
Yes, I think they are the same processor. The last post on his website (September 2009) was that he was having difficulty getting the specs for the processor. Evidently overclocking has to be done by manually setting the processor registers for WM devices. Evidently Android is different.
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
I believe ours is slightly newer or just different than the Touch Pro's :(.
[Touch Pro2, Tilt 2 Themes and Apps] mech_supernova:
found this http://www.nuerom.com/BlogEngine/post/2009/09/07/nueOverClockTest.aspx might work with the CDMA version only, tried it on my GSM tilt2 and it freezes but according to his post that was to be expected dose someone have a CDMA and be willing to try it?
[Touch Pro2, Tilt 2 Themes and Apps] BASSMANBOB:
Im pretty sure its the exact same...its just the hardware is mapped differently
[Touch Pro2, Tilt 2 Themes and Apps] stevedebi:
It is the control software that is different. Windows Mobile was not built to do that sort of thing and it has to be manually programmed.
[Touch Pro2, Tilt 2 Themes and Apps] Shammyh:
I'll throw down $10 on that.
[Touch Pro2, Tilt 2 Themes and Apps] Diamond_dawg:
this may help someone
[Touch Pro2, Tilt 2 Themes and Apps] mech_supernova:
tried it dosent overclock the TP2, only underclocks it according to the profiles :-(
[Touch Pro2, Tilt 2 Themes and Apps] johng75:
as well as an OCing, is there any one looking into memory hacks for the rhodium? taking away some of the ROM space and adding it to RAM space? i personally install very little to the actual phone, and 99% to the memory card which leaves a bunch of un tapped space that i think would be better used as RAM, especially with the issues with the memory hog we all call 2.5 sense?

if i remember correctly the Kaiser had such a hack, taking avail RAM from 85 to 101mb....
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
Well you can change the priority threads for programs and services to sort of make it seem like you're overclocking your device (speed booster which costs money and even that task manager that I forgot the name lol) but I just suggest not installing sense 2.5 because it wasn't meant for our phones and I notice that, just by having 2.5 on my phone that the ENTIRE phone goes slow (see the difference by simply disabling it from the today screen.

Ah but eh not sure about that. I never run out of RAM and tend to allocate a hell of a lot to it to cache using Advance Config.
[Touch Pro2, Tilt 2 Themes and Apps] DaveTheTytnIIGuy:
That hack simply changed the endram memory address in the WM kernel (nk.exe) to utilize the volatile memory normally allocated to the GPU, which wasn't otherwise being used any, due to the lack of proper GPU drivers for the Kaiser. That's why, for example, all the experimental HW3D drivers were broken when using ROMs featuring the 101MB RAM hack.

I believe it's impossible to simply hack NAND memory (device memory, microSD card, etc.) to act as volatile memory, and thus expand the RAM, since there are hardware differences between the types of memory. This hack could possibly be enabled on the Rhodium, but with such a speed hit from the loss of GPU functions that performance would be even worse than before. Even Ervius couldn't get that hack working on the original diamond, so I doubt it's really worth it.
[Touch Pro2, Tilt 2 Themes and Apps] stevedebi:
ROM is not equal to RAM. Can't be done, at least since WM 5.
[Touch Pro2, Tilt 2 Themes and Apps] aestivalisakito:
$25 serious pledge.

Inresponse to al th etalk about rom/ram stuff:

This trick no longer applies, For several reasons but the main one (and please this is to the best of my knowledge, if I am incorrect than please correct me because I really would like to know if I am) is the fact that the Kaiser for example used the same memory modules for RAM is it did for the ROM (hardware wise), therefore could use such a hack as the 101MB. Now that being said, the Touch Pro2 has two seperate memory modules (there are more but for the sake of discussion I am going to keep this fairly simple) for RAM and for ROM. That is why you can make all the room in the world by minimizimg ROM size, compressing with LZX, CFC compression, etc, and all youll get it more storage space.

The kaiser and devices of old (sortospeak)where quite primative in hardware design but quite effective (the GPU was capable of so much more but sh**y drivers cut it off, similiar to the tp2). Now adays they are building these things more similiar to laptops, now if only they would allow use to put bigger ram sticks in.....
[Touch Pro2, Tilt 2 Themes and Apps] iwfratz:
OCT_V-1.5 released

There is a new version of OCT in #162.
[Touch Pro2, Tilt 2 Themes and Apps] oruam57:
OCT_BKL V1.3

OCT_BKL is a small command line utility to control the OCT device driver developed by iwfratz (http://xdaforums.com/show...&postcount=162).

OCT_BKL V1.3 requires OCT V1.5 or above

.

OCT_BKL action depends on 3 numerical command line parameters (separated by a single blank character). The 1st one selects the action do be done:

1 - Set OCT off and terminate (e.g. OCT_BKL.exe 1)

2 - Set OCT off, set screen off, wait for screen on, set OCT on and terminate (e.g. OCT_BKL.exe 2)

3 - Set OCT on and terminate (e.g. OCT_BKL.exe 3)

4 - Set clock level at P2 and terminate (e.g. OCT_BKL.exe 4 33)

5 - Set clock level at P2, set screen off, wait for screen on, restore clock level and terminate (e.g. OCT_BKL.exe 5 10)

6 - Set clock level at P2, set screen off, wait for screen on, set clock level at P3 and terminate (e.g. OCT_BKL.exe 6 10 33)

P2 is the 2nd parameter value, the clock frequency is P2 * 19.2 MHz.

P3 is the 3rd parameter value, the clock frequency is P3 * 19.2 MHz.

For actions 4, 5 and 6 OCT_BKL sets # steps to 0, that is

no dynamic clock

.

For actions 2, 5 and 6 OCT_BKL tries to set screen off using TouchLockPro (http://xdaforums.com/showthread.php?t=444215). If you do not use TouchLockPro on your phone you should set the screen off yourself. In that case OCT_BKL waits for 2 seconds for the screen to go off. If nothing happens OCT_BKL completes the requested action and terminates.

For action 5 OCT_BKL gets the restore level from the registry where it was saved by the OCT_GUI utility.

For some more details read the ReadMe.txt inside the zip file.

As usual use OCT_BKL at your own risk, NO WARRANTY, blah, blah, blah... ;)
[Touch Pro2, Tilt 2 Themes and Apps] Assassin5150:
works great!! my phone maxes out at 748 :( are you gonna be working on an icon for the gui tab?
[Touch Pro2, Tilt 2 Themes and Apps] prag16:
Looks great! I am running at 768 with no issues thus far.

Also, the performance loss when using lower range variable frequency seems to be gone, as long as I set the polling interval to something fairly low such as 200 (1000 causes a noticeable performance hit both anecdotally and in benchmarks).

I will need to test it out for a few days at least to verify, but I think this is definitely sufficient to crown iwfratz the winner of this bounty. At that point donation will be forthcoming.
[Touch Pro2, Tilt 2 Themes and Apps] atticus182:
Interesting! I will try iwfratz's app tomorrow when I'm back home and let you know if it works fine! Thx!
[Touch Pro2, Tilt 2 Themes and Apps] stevedebi:
768 here

Just ran SK Tools Benchmark:

Int = 471 (325 Stock)

Floating Point = 11.171 (7.64 stock)

RAM access = 643 (489 stock)

GDI 1025 (819 stock)

Definitely a winner!
[Touch Pro2, Tilt 2 Themes and Apps] ACoolGuy:
Lovin my phone and iwfratz. 804Mhz with jump up at 25% and down at 3% and 100ms interval. Sense is completely nice now and the landscape photo tab is closer to how fast it should be.
[Touch Pro2, Tilt 2 Themes and Apps] mech_supernova:
I am offically ready to pay my $20 bounty money to iwfratz
[Touch Pro2, Tilt 2 Themes and Apps] chihliouma:
Hi there, thnaks for the update. I've tried to set the CPU speed to 710Mhz and make a shortcut of OCT_run to startup. But after reboot, the speed returns back 652. Is that normal ? Thanks
[Touch Pro2, Tilt 2 Themes and Apps] ACoolGuy:
You need to Hit "SET" then hit "OC on/off" twice to toggle the OC which "SETS" the settings. Then go ahead and reboot the phone.
[Touch Pro2, Tilt 2 Themes and Apps] chihliouma:
I do SET twice to make sure that the speed is set to 710, but after reboot, it still go back to 652. Any idea ?

EDIT : sorry, it's my bad that I didn't follow what you said exactly. But after I try again. It works now. Thanks
[Touch Pro2, Tilt 2 Themes and Apps] JVogler:
So what are the steps exactly to simply overclock...and just stay there since there is no CPU min. in this GUI...
[Touch Pro2, Tilt 2 Themes and Apps] Alcibiade:
Waoh great ! Looks like your app is finished now !

I love it :)
[Touch Pro2, Tilt 2 Themes and Apps] mech_supernova:
the way I did it I set the # steps to 0
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
Read the readme that was included.
[Touch Pro2, Tilt 2 Themes and Apps] BASSMANBOB:
Where is the read me?
[Touch Pro2, Tilt 2 Themes and Apps] buru898:
In Program File\OverClockTool.
[Touch Pro2, Tilt 2 Themes and Apps] Doo Doo:
i got a ? if the # of steps is set to 0 when the phone gets put to sleep is it still being overclocked?
[Touch Pro2, Tilt 2 Themes and Apps] prboy1969:
OK so I've been uing NetRippers app fo r a while now with no SOD . Clocked to 729Mhz . Couple of questions . First , I know a few of you have used both . Are you able to clock higher on one or the other ? Or is it about the same ? Second , do I just install the cab and go ? What are the steps ? Want to know before I try . Is it completely uninstalable ? Thanks in advance for the help .
[Touch Pro2, Tilt 2 Themes and Apps] mech_supernova:
I tried netrippers I kept getting the SOD and eventually had to do a hard reset I got mine set to 768mhz right now and its been at that and running since 6:00 EST its 12:46 now. all you do is install the cab go to overclock tools then OCT_GUI and set the settings how you want and click set then OC on
[Touch Pro2, Tilt 2 Themes and Apps] JVogler:
mech_supernova: worked - setting the # steps to 0 makes OC stick. Thanks

After changing those settings I leave my gui closed and just mapped double click power button to run OC and triple click to stop OC so I can quickly OC whenever I need to extra speed from any program.

I'm not familiar with scripting or programming, but is there a way to have a toggle file, instead of separate start and stop. That way I could just map the file once and use the same key press to start and stop OC?

So, I'm now happy with this program and ready to donate? What post # is the donation info on?

Thanks for the quick effort in getting this program to a useful state!
[Touch Pro2, Tilt 2 Themes and Apps] JVogler:
Is there anyway to disable to pop-up "Exiting OCT device driver" I start and stop OC quite often with a mapped button, and as it is working now I have pull out my stylus and close that box every time.
[Touch Pro2, Tilt 2 Themes and Apps] Doo Doo:
when trying to uninstall, it doesn't uninstall all the way why?

it still shows the app in the remove programs list?
[Touch Pro2, Tilt 2 Themes and Apps] prboy1969:
Was thinking of maybe trying it .
[Touch Pro2, Tilt 2 Themes and Apps] Doo Doo:
i'm trying it out right now so far so good :D good job iwfratz

just need a couple ?'s answered that i posted which can be found

here - http://xdaforums.com/showpost.php?p=7661870&postcount=398

&

here - http://xdaforums.com/showpost.php?p=7663306&postcount=403
[Touch Pro2, Tilt 2 Themes and Apps] 5318008:
Some other people have had the same issue, but uninstalling with SK Tools (if you have it) works OK.

v1.5 (final?) working perfectly here, so, bounty: I just went on vacation, and don't have computer access while away, but when I get back home I intend to PayPal over my share of the bounty pledge.

To be fair, if NetRipper releases a final version of his app, I'll probably send him my bounty pledge too, in recognition of all the good-faith work he's done on his program. It's worth double bounty to me anyways as I have two Rhodiums in my household.
[Touch Pro2, Tilt 2 Themes and Apps] Doo Doo:
but you shouldn't have to use another app to uninstall it
[Touch Pro2, Tilt 2 Themes and Apps] TeDeV:
hey guys, can u plz tell me how to configure oct 1.5?

cpu max = 710

# steps = ?

load max = ?

load min = ?

jump max = ?

jump min = ?
[Touch Pro2, Tilt 2 Themes and Apps] 4bettilt2:
a little explanation of above plus polling interval would educate us challanged users
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
It's all in the readme file (which is a bit hard to find). I'll post it here:

OverClockTool (OCT) V-1.5

=========================

OCT is a tool to manipulate the CPU speed. It is developed on a TP2 with

MSM7200, but should also works on other MSM7200 and MSM7600 devices.

You can over- and underclock your device, even use a dynamic clocking.

settings:

---------

settings will be saved on deactivating OC only after they successfully

assigned and activated for OC.

cpu_max states the maximum speed the cpu will be set to

# steps number of frequency steps

0 : always cpu_max

1 : cpu_max, cpu_max/2

2 : cpu_max, cpu_max/2, cpu_max/3

3 : cpu_max/n with n=1..(steps+1)

load_max if your actual cpu load is higher than load_max, OCT will step up

your cpu one step.

load_min if your actual cpu load is lower than load_min, OCT will step down

you cpu one step.

jump_max if your actual cpu load is higher than jump_max, OCT will jump

immediatley to cpu_max.

jump_min if your actual cpu load is lower than jump_min, OCT will jump

immediatley to cpu_max/(steps+1).

interval: time span in ms for calculating cpu load and stepping.

0 means no load calculation and no dynamic stepping.

program files:

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

OCT_Run: loads driver and starts OC with actual settings

OCT_Stop: stops OC and unload driver

OCT_GUI: loads driver, controls all settings, did not unload driver.

Programming-Interface:

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

To control OC there is a programming interface. OCT is designed as a Device Driver

and features following interface:

- CreateFile opens connection to OCT

- WriteFile send data to OCT. you have to write 2 DWORDs (command, operand)

- ReadFile read data from OCT. you have to read 1 DWORD. (answer)

- CloseHandle close connection to OCT

actually following commands are defined

0x001: start OCT

operand: 0

0x002: stop OCT

operand: 0

0x003: stop OCT and unload driver

operand: 0

0x011: set cpu speeds

operand: #steps, cpu_max. each as one byte from least significant byte to most one.

0x012: set cpu loads

operand: load_min, load_max, jump_min, jump_max. each as one byte from least

significant byte to most one.

0x013: set interval

operand: interval value, 0 means no calculation of cpu load and no stepping

0x021: get cpu speeds

operand: 0

answer : #steps, cpu_max. each as one byte from least to most significant byte.

0x022: get cpu loads

operand: 0

answer : load_min, load_max, jump_min, jump_max, each as one byte from least

to most significant byte.

0x023: get interval

operand: 0

answer : interval

0x031: get actual cpu speed

operand: 0

answer : actual cpu speed in MHz

0x032: get OCT status (on/off)

operand: 0

answer : 0 for OC is off, 1 for OCT is running

0x033: get actual cpu load

operand: 0

answer : actual cpu load. if interval is set to 0 you get last calculated value.
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
I'm sorry but I don't know the answer to that. I'm sure Iwfratz will answer.
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
Post 162, this thread.
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
Happens to me (and others) as well. Make sure to run OCT_Stop *twice* before you try to uninstall, but many times it still won't completely remove itself. However, new versions always seem to install just fine over the old versions anyway, so don't let this minor issue dissuade you from using the program.
[Touch Pro2, Tilt 2 Themes and Apps] TeDeV:
the readme still doesn't help. show me some real examples plz
[Touch Pro2, Tilt 2 Themes and Apps] IMissPalmOS:
The best "example" settings are the defaults. I can't suggest any better than them because I don't use dynamic clocking. I suppose I should explain that, so I will try...

"Dynamic" clocking adjusts the speed of your CPU based on the "load", or the amount of work it has to do at that moment. All the settings mentioned above adjust exactly how this process takes place. You could think of it like an automatic transmission in a car. It automatically decides which gear to shift into based on the revolutions of the engine and the current "load". Such transmissions can be adjusted to give the most power, the most speed, or the best gas mileage. Dynamic clocking is the same concept, and iwfratzs program lets you "tune-up" the settings to your liking.

Now, I personally like my phone "tuned" the same way I like my car; that is to say that I don't care about gas mileage and I don't want my car shifting around looking for the "best" gear when I floor it. When I step on it, I want it to go, NOW, and not shift again until it hits the beefiest part of the RPM range. I apply the same logic to my phone. When I press buttons, I want it to be running full speed, instantly. I don't care about battery life (gas mileage) and I don't want any lag while the CPU scales up (shifts gears). Thus, I have my CPU set at 748 MHz, and *all* other setting at "0". My phone springs into action instantly, and runs smooth as glass...

Hope my car analogy doesn't bore you, and helps you to understand...