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