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

Hilarious, true, and very sad, all @ the same time.

Having said that..

Has anyone ran this .cab along with the typical speed hacks (glyph cache, fatfs, etc.)?
If so, what type of results did you see?

Addendum
 

Ran at 520 yesterday all day from full charge. Had to actually USE the phone Google maps and a handful of short phonecalls. Early 4-5 AM 100% Charge,,,

this morning 30%...

I'm guessing that was mostly the Google maps...

Just an update...

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...

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

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

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?

Whenever LumosII or LumosIII is running, it locks the screen display to whatever it is currently on. All keyboard slide events are ignored and do not change the perspective. The button on HTC Home will still do it on a click but the event is in turn broken with the use of lumos. (Which actually I've found to be appealing because when i quick want to text someone, I used to flip the keyboard and give it a breather before I go and type -- but now, I just crank away and no missed letters)

I've got some more scaling tests to do with PHM and will have the results posted soon (I hope) -- then its off to XCPU testing for a final verdict.

Also I'm experimenting with the PHM "autoscale CPU disable" /feature/ to see how it acts on battery/performance consumption.

More to come...

Copy

EDIT: forgot to mention, I'm going to hook my multimeter up tonight and measure "downtime" in realtime to test the ("XCPUScalar's "hibernate" feature is preferable.") is actually preferable or not...

Sweet. I love how thorough you're being, especially with the multimeter. I'd love to see multimeter comparisons between active use as well as dormant.

Right now, I could go either way between PHM and XCPU but I'm leaning towards staying with XCPUScalar longterm because of stability - and perhaps battery life. Battery life will be key, I think.

Yes you can use TCPMP and select file/benchmark to verify.

Both the : (546Mhz,273b,137m,68lcd) AND the (572Mhz,286b,143m,72lcd)
are faster simply because of the higher Bus speed than stock208..

None of my 3 refurbs were ever able to reach 624Mhz though, so for newer refurbs this seems to be the best setting.

If you have Xcpuscalar or PHM and want to experience less process/ram, and Ma overhead while overclocked, you also can try this:

Connect 6700 to USB external power (either to comp or power supply)
Run your favorite overclock program
Set highest stable speed.
Close overclock program
Run "CPU-ID".(to verify still overclocked while plugged in)
I do this whenever synced and also when using "Internet Sharing"
I havent measured sync performance but it is faster :)

Your unit reverts back to normal when you disconnect from external power...

Oh i can totally vouch for this as well, It's been a while since i've came on the forums but several months ago when i found out about PHM and its features i've just been madly overclocking my phone. I concluded the same thing as Maxx134 did:
Raising the ram and bus speeds really do help quicken things up. Cpu did as well of course.
I didn't do any real benchmarks except making a basic timing program in VB and timing the latency between landscape and portrait modes on the home screen. I did get consistent results in that running my phone at
CPU: 598.00MHz, Bus: 299.00MHz, and RAM: 149.50
speed things up immensly. I wish that wm6 was optimized for this phone so that it would be ever so faster. I also tested at super slow speeds(26 mhz anyone?) and conversely things.. err.. happend quite slowly like opening the start menu took like 10 seconds, or to even get a answer the phone dialoag took 3 minutes.. lol

Anywho more specifically my settings were
L: 23
N: 4
A: 1
LCD_26: 0
Turbo: checked
half-turbo: not checked
Fastbus : checked

I could reach 624mhz but it was not stable at all lots of freezes 598mhz works with almost everything except for wifi, probably because of the high increases in bus speed. Videos in tcmp replay back flawlessly

This has been my first PDA phone, and i thought it was going to be quite a bit faster than my dads vx6600, but i was quite wrong. I didn't even realize that my dad's phone was running wm2003 and i was wm5/6 and that the difference was the o/s wasn't in ram anymore. It makes me quite sad that new wm5/6 devices are sooooo slow compared to that of vx6600s D: (at least the ones i've seen are slow) My biggest pet peeve is waiting for the screen to change or to fully refresh or seeing it lag just browsing a folder or something just etc normal tasks. Are there any such phones out there? i'd love to see those 1 ghz phones come out

I multimeter tests are VERY suprising to say the least.

Few things for those that are interested:
I can't disable the option for PHM to disable CPU scaling, it seems to be locked into the checked position for the version I have. (oh well)

XCpu DOES pull the same mA in "sleepytime" as the stock settings do. PHM DOES NOT!@!@! xCPU drains the battery TWICE as fast as stock with or without scaling enabled.

I can get my PPC so hot with PHM my phone turns into a small heater. I notice running PHM with internet sharing IMPROVES the download speeds by around 25%.

PHM benchmarks blow xCPU's marks out of the water.

So in a semi-final conclusion, the only time to use overclocking so far is when you know you are going to be plugged in, otherwise your battery is toast.

I ran one full day with PHM and one full day with xCPU and the drain rate was very similar. now today it is running at stock so once I get the results, I'll post up the data so you can all make your own decisions.

Copy

ALMOST FORGOT!!!!!!!!!!

The multimeter results were within 2-3mA of what acbPowerMeter reported.

I was so interested in knowing if it was accurate - and it is at ANY fluctuation of board/bus/ram speed.

Copy

Excellent comparison. I have the following question though:

"XCpu DOES pull the same mA in "sleepytime" as the stock settings do. PHM DOES NOT!@!@! xCPU drains the battery TWICE as fast as stock with or without scaling enabled."

This statement is confusing. It almost seems like sentence 3 contradicts sentence 1. Do you mean that PHM drains the battery twice as fast? Or are you referring to XCPU in active operation?

I think to be clear you might want to break it down the following way:

Battery loss:
"Sleepytime" - STOCK = XCPU, PHM is much worse.
"Active" - STOCK is best, XCPU = PHM

some beach. That #&%!@ timeout function in this forum made me lose about 10 minutes worth of typing. Regardless, found a workaround for that for future use.



This is a dieing/obsolete phone anyway and all this work will be lost as people upgrade to phones that have dual core processors that can not take advantage of upscaling.

Guess I was right afterall about the sugar pills using twice the energy! lol
Before anyone goes chicken crazy on me, I'm only joking.

Woo hoo I'm glad the onboard gps is now enabled on the Mogul! REVA too!

Now if only you guys would test which standard apps and setups slow up the phone the most (and the apps power consumptions) then we might have a more universal approach to the problems at hand.

Of special interest (as these are in my startup)
btdwake, filedlgchgs, ftouchflo, ilock2, ledoff, notifyme, poutlook, quickmenu, services, sipchange, smartskey, vistahide battery guage, voice command, and wktask.

Most, if not all, of these were included from Colonel's 12-28 ROM and my phone had become slow as crap... I'm now experimenting with new GPS/REVA rom.. :)

/end hijack

I installed the cab. on my mogul but I cant figure out how to set the speed. Can someone help me plz

^ dual core processors that can not take advantage of upscaling ^

So is it safe to say that this application is a sugar pill?

negative. but the only thing relevant is the last 1 or 2 pages.

Still cant find how to select speeds. Can someone help me plz

GOT IT

hi team

grabbed the cab from one of the earlier posts but where exactly do i place it in the phone to run? when i clicked on it to run, it just said installation unsuccessful. so not sure exactly how to run the cab.

any help appreciated

cheers

Copy it to the storage card. Run it from there. It should install just fine.

Skaal!

thanks for the help guitardoc64, but unfortunately that didnt work as well :( :( is there another cab i can try?

okay got i installed and well. it does seem to run faster, programs are opening quicker than before. this is at 524. perhaps myself also is affected by the placebo effect of this program lol all i know is... it runs better than at normal speed.

program works great

broke my phone, I got the "white screen" and i was clocking it at 520..
is there a fix for this?!?
the white screen is translucent but the phone is fully functional, its just like white and fuzzy!

Mogul User WOW
 

I just installed on my Mogul. Seems to be running great. Had to reinstall TCPMP for it to work but otherwise everything else seems fine.

Thanks

blademan :headbang:

OK, so I"m ready to actually BUY a legit copy of some over-clocking app. Which is best? Stick with the free HTC Performance sugar pill? XCPUScaler (sounds like it works?), or... any other options?

A mod or someone needs to step in here and kill this conversation before too many people seriously damage their phones.

YOU CAN NOT OVER-ClOCK DUAL-CORE ARCHITECTURES WITH ANY CURRENTLY AVAILABLE APPLICATIONS.
That means if you put this on your Mogul or Touch then you will have no speed increase, and will likely fry your phone.

If you install on a 6700 then it would serve you well to read the previous two pages in regards to battery consumption, etc.

Will this app work with a MOGUL 6800?
Thanks for the feedback!
-J

As a final note to this discussion and the findings that I've gone through, It is not battery efficient to overclock the 6700. Pocket Hack Master produces the best and fastest results. XCPU is second. HTC did not produce any benchmarks faster than the stock speed.

Battery consumption DOUBLED using any speed adjustment. It is not worth it unless you have a usb cable plugged in 24/7. (and you want a portable egg cooker)

I've uninstalled all hackery on the processor and my battery life has doubled. I am back to two days between "having to charge" on normal use. before using all the applied tricks (and I tried them *ALL*) I would go one day and have to charge each night or face a dead phone.

I haven't had to face a dead phone in a while and I don't miss it -- even though when I opened up the flip to text someone it would never miss a character. I am fine waiting that extra second before I start typing to save my battery life - and overall the life of the phone.

Copy