HTC Performance (overclocking) OEM

[Maxx134]

Originally Posted by PolloLoco

You're not going to be saving more energy than a stock phone, but you would only be burning more power when actually using the overclock. That's why I love to use my phone at 624 100% of the time, I've been doing it for over the last year. I don't think the power loss is significant at all. With a 2600 lithium polymer battery, I can still go 2 days of heavy use without charging - though my phone will be close to dead by the end.

I mentioned long ago in both Xcpu & PHM my findings on the 6700, to disable autoscaling & also increasing the "Bus" speed as being more effective than just CPU speed. :P

For those of you who want the best performance on a 6700:


Turn on "VJLumosII" (to disable auto-scale)
Open Pocket Hack Master.
Set speed to either:
520Mhz,260B,130m,65lcd
546Mhz,273b,137m,68lcd
572Mhz,286b,143m,72lcd
Goto settings/system/backlight.
Lower brightness.
Goto PHM & exit application.
Open "CPU-ID".
Verify unit still running overclocked without PHM.
Open "acbPowermeter" to verify unit using less Ma draw.
Open TCPMP player & open a video.
In TCPMP select file/benchmark and verify HUGE increase in performance.

There you have it...
Your unit will revert to normal when you turn off.

[CopyCounsler]

max seems to have the right idea. The LumosII is the key to this... Found this on their site:
LumosII allows PHM to work!
« on: August 08, 2006, 06:06:45 PM »

Enabling LumosII on my PPC6700 (and similar units) allows the unit to think its using camera mode, so the autoscaling is disabled, which is how it was designed .
This enables me to run both overclock programs without problems on battery power.
Although this does not make xcpUScalar run better, it makes Pocket Hack Master run when it could not before. PHM makes this unit scream! It runs noticeably better and much more efficient than xcpuScalar.
Now with PHM, my battery drain has returned to normal levels, even with this max brightness from LumosII.

-----------

So I'm going to test some more and post back the results - possibly even putting some asm and reg tweaks together to provide a one click solution to put into the startup folder. This seems to be the best solution.

Copy

[PolloLoco]

Originally Posted by CopyCounsler

max seems to have the right idea. The LumosII is the key to this... Found this on their site:
LumosII allows PHM to work!
« on: August 08, 2006, 06:06:45 PM »

Enabling LumosII on my PPC6700 (and similar units) allows the unit to think its using camera mode, so the autoscaling is disabled, which is how it was designed .
This enables me to run both overclock programs without problems on battery power.
Although this does not make xcpUScalar run better, it makes Pocket Hack Master run when it could not before. PHM makes this unit scream! It runs noticeably better and much more efficient than xcpuScalar.
Now with PHM, my battery drain has returned to normal levels, even with this max brightness from LumosII.

-----------

So I'm going to test some more and post back the results - possibly even putting some asm and reg tweaks together to provide a one click solution to put into the startup folder. This seems to be the best solution.

Copy

Man, that sounds like good news. Coincidentally, I'd just downloaded a trial of PHM to play with. I've been wondering if I can overclock beyond 624 as I'd heard others could.

Good luck with your experiments.

Edit: My experiments with PHM did not go well. I could overclock to 624 just as easily as XCPUScalar. 728 locked up during testing, just as with XCPUScalar. 663 worked, but as with XCPUScalar - I had a lot of screen distortion. I then tried to find a speed between 624 and 663 that worked well - but my 6700 totally locked up. On a soft reset, it stuck on the boot screen. I had to hard reset. That sucks, so I'm going to go back to XCPUScalar indefinitely.

[CopyCounsler]

well running PHM and the VJLUMOSIII, I've noticed a few things.

First, when I slide the keyboard out, it's stuck in portrait mode. Second, I'm running @ 520 and it's fast in every benchmark I run. I even get faster card reads with PHM. Third, my earlier test with iGuidance and 10seconds using xCPU is now an 8 second calculation, almost twice as fast as the "stock" experiment.

The only bad part is this: I can't seem to figure out how to "batch" PHM to load automatically. I just started looking into it but if someone has a cheat sheet list or something, I can provide a one click solution to boot with windows. I've also got the tweaks finished to lower the brightness again and load the camera (by turning off VJLUMOS)

It draws around 165mA average which is much better than 250-300 I was getting with xCPU.

More to come. Still playing around with it.

Copy

[PolloLoco]

Excellent work CopyCounsler. If you can figure out a painless way to enable PHM consistently, I may switch over again.

When you state the battery draw, is that by using the program's scaling function? Or only by having it set at 520?

[CopyCounsler]

at the moment, I do not have ANY scaling enabled.

My favorite speed so far is: 286wTurbo (572), 143bus, 72lcd

Oh.. almost forgot. this favorite speed of mine and the alternates (520 and 546) make the screen "flicker" a bit. much like the xCPU did on 108mhz... Well not MUCH like it but that's the flicker i'm talking about. Like the refresh isn't *quite* right.

More to come.

Copy

[Maxx134]

Originally Posted by Maxx134

I mentioned long ago in both Xcpu & PHM my findings on the 6700, to disable autoscaling & also increasing the "Bus" speed as being more effective than just CPU speed. :P

For those of you who want the best performance on a 6700:


Turn on "VJLumosII" (to disable auto-scale)
Open Pocket Hack Master.
Set speed to either:
520Mhz,260B,130m,65lcd
546Mhz,273b,137m,68lcd
572Mhz,286b,143m,72lcd
Goto settings/system/backlight.
Lower brightness.
Goto PHM & exit application.
Open "CPU-ID".
Verify unit still running overclocked without PHM.
Open "acbPowermeter" to verify unit using less Ma draw.
Open TCPMP player & open a video.
In TCPMP select file/benchmark and verify HUGE increase in performance.

There you have it...
Your unit will revert to normal when you turn off.

I forgot to state in my post that the "LumosII" proggy would benefit either overclockers to draw less MA since they can be disabled & you will still Be overclocked untill shutdown or sleep.
The sole reason for me choosing PHM is that it enables me to choose a specific setting wich on the 6700 works best.
The settings I posted from PHM all work better than stock 624Mhz of Xcpuscalar...

The HTC overclock proggy is not making any verifiable difference that i could prove.. but when left on it actually did affect my speed configuration tests in PHM (no good to have more than one overclock proggy on!)

CopyCounsler it will be a benefit 2 us 2 post whatever you have for automation of the LumosII. The PHM has a setting for itself in edit/settings...

[CopyCounsler]

Ok.. busy over the weekend but did have a chance to prove some things once and for all.

First off, Lumos works. Second, I'll have some future postings with some automation for all to enjoy.

I've noticed when I use my phone intensively, it pays to turn on phm. Otherwise, it's more beneficial to the battery to do NOTHING to the cpu speed at all.

Also, I've been running with all the glyph cache and fat settings to the max (32767 and 8096 respectively) throughout all the testing.

Just for those wondering what I've been up to, take a peek at the screenshot. More to come...!

Copy

[CopyCounsler]

Ok guys and gals here you go. These are extremely beta and comments/suggestions welcome.

PHMLoader.exe
AltCamera.exe

These both assume 2 things: (besides .NET framework)
1)VJLumosII is installed on your main memory. (default dirs)
2)PHM is installed on your main memory. (default dirs)

Now. PHM should be set to minimize automatically on autoload in the settings.

Heres what they do:
PHMLoader - Will take a snapshot of your backlight settings, load VJLumosII and then load PHM. Once finished, your screen will be locked (your slide out will not work anymore cuz of lumos) and your screen backlight will return to its original setting once user input is detected.
VJLumosII is loaded along with PHM automatically.

AltCamera - Will stop VJLumosII from running and then start camera upon successfully doing so. Will also monitor and restore brightness settings as well as fire up VJLumosII back up after CLOSING, i repeat CLOSING camera. If you do not exit camera, this program will continually wait for you to close it before restoring VJLumosII.

I suggest putting PHMLoader in your startup folder and assigning altcamera to your camera button.

VJLumosIII allows me to detect if you have vj even running to see if I need to shut it down before running camera, I may or may not even bother continuing development on using it. It would run a bit fancier though...

Also, when running camera, I do not disable PHM so whatever speeds you have set is what the camera will operate on.

ANYWAY, ENJOY everyone.

Copy

EDIT: disclaimer: not responsible for loss of sleep, battery, data or relationships when using these programs! :P

[PolloLoco]

Excellent work CopyCounsler,

I find it interesting that you've discovered that it's favorable batterywise to use no PHM instead of scaling. It sounds like in this case - XCPUScalar's "hibernate" feature is preferable.

Also - when your automated combination is running, we're unable to slide out the keyboard or rotate the screen? Is that correct?

Finally, Maxx134 asserted that the previously stated lower clockspeeds in PHM are superior to 624 in XCPUscalar. Is that through benchmarking I assume?