HTC Performance (overclocking) OEM

[PDAPhoneJunkie]

No, this will not work for the Mogul. You must not read, this actually can damage your device.

[Hidavi]

My Mogul is definitely faster after this, man. Is there any way to test the actual running frequency of my CPU?

[PDAPhoneJunkie]

It is all in your head. It will NOT work because of the dual procesor. Open TCPMP and check your "Clock Speed" Under Option>Settings. I can promise you it probably is somewhere around 385. Unless you have a one of a kind procesor in your Mogul that can work with HTC Performance...

[pio_masaki]

Yea they have different CPUs, I mentioned this earlier (page 26 I think). Software written for the 6700 and earlier won't scale or change CPU's in the 68800 and later. Far as I know there is still no software to change the CPU speeds in the 6800+ CPUs. If it makes you feel any better, my qwest apache is plain slow compared to my sprint apache, both run stock carrier roms, it's just slower, it could just be your build is faster and that is what you are seeing.

You can also benchmark with TCPMP, though it would require a before and after benchmark of the different roms, meaning benchmark a file on your upgraded, then flash back to your stock, using the same file in the same manner (phone or sd memory) and you may get a slight difference in speed. There is variation from run to run anyways, keep that in mind. Best way is to run 3 each, and use the averages to determine if any actual increase is there.

[tronnixx]

Ok guys - I have read dozens of posts on this HTC Performance utility whether it works or not so here you go:

HTC Performance .cab:

The PXA270 Proccessor has 4 clock steps 312-416-520-624 , any of the speeds in this range are not considered over or unclocking. These processors are designed to operate at any of these frequencies which is controlled by the device.

Now, on the HTC Performance utility you will notice if you enable dynamic stepping with 520Mhz selected, there should not be a speed increase while operating on the XV6700, you will also notice as pointed out by someone else if you look in the registry that under the keys HTC > HTC_MISC you will see "EnableMonitoring" set to 1, and "EnableOverClocking" set to 0. This is because the HTC performance was designed for a PXA270-based phone that has a standard speed of up to 512, so in essence it does not do anything, especially on the XV6700 with the default clock of 416Mhz. HOWEVER, When the HTC Performance Utility is set to dynamic stepping with the 624 option selected, the reg key "EnableOverClocking" is now set to 1. Therefore, the 624Mhz option does actually overclock the system but it may not ever reach the 624Mhz, but rather the 624Mhz option allows the system to roam over 416Mhz as needed. Whereas with the 520Mhz option, on the XV6700 this option is just for the system to cap at it's already set default of 416Mhz. Or, on other phones it may be 520Mhz. It would of been nice if the HTC Performance utility show the actual max/current values but the utility was designed for another HTC phone model at 520Mhz.

Bottom line: The 520Mhz option does nothing more then the phone already does capping out at 416Mhz on the XV6700 - and The Good News, the utility does actually speed it up, but ONLY WHEN SET TO THE 624Mhz option (It enables the system to go up to 624Mhz as needed)

Even though this utility does step it up (when set at 624Mhz), I am not too impressed by their stepping alghorithm. So, here is what I did to optimize battery life and peak performance:

Using a program such as Power Hack Master:

1) Stick to the PXA27X's core clock speeds: 312-416-520-624
2) Enable Scaling between above speeeds. You can use the default scaling or I use 20%-40%-80% Ratio (Under 20% decrease speed, above 40% increase, above 80% go to fastest (624Mhz).
3) In PHM (I dont know about XCpuScaler) you can force application specific speeds. So for Java, Internet Explorer or any other application where you want full speed you can set it so when you launch the program it automatically overides scaling and forces the speed you choose.

I attached Pocket Hack Master (the latest WM6 version. It will operate in trial mode until you purchase the key to unlock.)

P.S.
I am writing a very tiny and lightweight program that will run as a process that will use a very small memory/cpu footprint. I just need to test the various speeds and optimize it, run the benchmarks, then post the utility. If you have any ideas let me know.

[BigDiesel07]

If you can find one for the Touch Pro, that would be awesome

[tronnixx]

Originally Posted by BigDiesel07

If you can find one for the Touch Pro, that would be awesome

Find what? If you're talking about Pocket Hack Master, the one above will work on your HTC Touch...

Your HTC Touch has a TI OMAP 850 with a 201Mhz clock. This new version of Pocket Hack Master above will safely
bring the TI OMAP from 201Mhz up to 276Mhz. Just don't try to go higher...

The Power Hack Master version above works with the following:
Supports Intel® XScale™ and Bulverde™, Samsung® S3C24xx™ and Texas Instruments® OMAP™ processors

[weedahoe]

Originally Posted by tronnixx

Ok guys - I have read dozens of posts on this HTC Performance utility whether it works or not so here you go:

HTC Performance .cab:

The PXA270 Proccessor has 4 clock steps 312-416-520-624 , any of the speeds in this range are not considered over or unclocking. These processors are designed to operate at any of these frequencies which is controlled by the device.

Now, on the HTC Performance utility you will notice if you enable dynamic stepping with 520Mhz selected, there should not be a speed increase while operating on the XV6700, you will also notice as pointed out by someone else if you look in the registry that under the keys HTC > HTC_MISC you will see "EnableMonitoring" set to 1, and "EnableOverClocking" set to 0. This is because the HTC performance was designed for a PXA270-based phone that has a standard speed of up to 512, so in essence it does not do anything, especially on the XV6700 with the default clock of 416Mhz. HOWEVER, When the HTC Performance Utility is set to dynamic stepping with the 624 option selected, the reg key "EnableOverClocking" is now set to 1. Therefore, the 624Mhz option does actually overclock the system but it may not ever reach the 624Mhz, but rather the 624Mhz option allows the system to roam over 416Mhz as needed. Whereas with the 520Mhz option, on the XV6700 this option is just for the system to cap at it's already set default of 416Mhz. Or, on other phones it may be 520Mhz. It would of been nice if the HTC Performance utility show the actual max/current values but the utility was designed for another HTC phone model at 520Mhz.

Bottom line: The 520Mhz option does nothing more then the phone already does capping out at 416Mhz on the XV6700 - and The Good News, the utility does actually speed it up, but ONLY WHEN SET TO THE 624Mhz option (It enables the system to go up to 624Mhz as needed)

Even though this utility does step it up (when set at 624Mhz), I am not too impressed by their stepping alghorithm. So, here is what I did to optimize battery life and peak performance:

Using a program such as Power Hack Master:

1) Stick to the PXA27X's core clock speeds: 312-416-520-624
2) Enable Scaling between above speeeds. You can use the default scaling or I use 20%-40%-80% Ratio (Under 20% decrease speed, above 40% increase, above 80% go to fastest (624Mhz).
3) In PHM (I dont know about XCpuScaler) you can force application specific speeds. So for Java, Internet Explorer or any other application where you want full speed you can set it so when you launch the program it automatically overides scaling and forces the speed you choose.

I attached Pocket Hack Master (the latest WM6 version)

2 things..........

First and foremost, youre taking the OC thing way to seriously. By OC'ing you have to understand we are not talking about forcing the CPU to go beyond what it is capable of and cryo-cooling it. We are in speaking about running it higher than the default setting provided by the carrier.

Secondly, DONT post a version of Pocket Hack Master AND a serial number for it. You need to read the rules of the forum and community and be aware no pirated software can be provided or hosted.

Now I think its great that youre bright enough to know where and how to get what you want. But it wont be allowed here. Sorry.

My advice is to take it down before you catch too much attention.

[tronnixx]

Originally Posted by weedahoe

2 things..........

First and foremost, youre taking the OC thing way to seriously. By OC'ing you have to understand we are not talking about forcing the CPU to go beyond what it is capable of and cryo-cooling it. We are in speaking about running it higher than the default setting provided by the carrier.

Secondly, DONT post a version of Pocket Hack Master AND a serial number for it. You need to read the rules of the forum and community and be aware no pirated software can be provided or hosted.

Now I think its great that youre bright enough to know where and how to get what you want. But it wont be allowed here. Sorry.

My advice is to take it down before you catch too much attention.

I SAID IT IS NOT CONSIDERED OVERCLOCKING because the PXA27X is designed to operate at 312-416-520-624. None of those frequencies are considered overclocking. If you go over 624, then yes. But this processor is actually designed for 1 of those 4. Believe it or not, in some embedded devices using the same processor the default freq. is 520Mhz.

Next time please read my post more carefully.

It does indeed speed it up over 416Mhz safely without damage as it was designed by Intel this way. Again, it's not considered overclocking. HTC probably wanted it at 416Mhz for battery reasons, or for a new model with the same processor perhaps.

[orionsbuckle]

Originally Posted by schettj

Somehow I missed this in the new ROM/Kitchen... I just manually installed it, and, wow - really pretty slick.

Anyone have any more info on where this app came from?

10 second overview:
It's a control panel. You launch it, enable 'dynamic CPU frequency scaling' checkbox, and pick the 520mhz max.

Then you forget about it, except your apache now runs like it's on steroids.

I've done some light batterymeter tests with it, and it does allow the cpu to drop down to standby/low power just fine - my idle power draw is the same 27ma (screen off but 6700 on) and the full power use is not a lot higher. I will have to see how the battery impact is during the day.

It is noticeably faster... snappier. Stable, so far, as well.

So, anyone else using it? Anyone know where it came from?

this is ok to use on our TP???