Great post Maxx134... Wish I would have used that when I had my 6700.... which I just sold on Craigslist for $150....woo hoo :)

Working on the touch
 

ok, this "HTC Sugar Pill" or "Mojo Magic" is doing its magic on my touch. HTC Album Camera and the Camera load up very quickly. 520 has a quick feel to it. I'm just as confused as everyone else why this works. I guess it is what it is.

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.

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

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?

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

Ah, that "flicker" is what I saw at 663. I described it as distortion, and never felt comfortable using it for more than 5 minutes at a time. Good luck.

You know you're a ppc geek when you spend 6700 hours trying to get your 6700 to go .67 of a second faster.

touche'

Copy