Yes, two suger pills = twice the energy.

Raging Idiot

I think you all had too much fruitcake over the holidays

Using XCPU Scalar I've timed and validated a 22% speed increase from 416-520. Are you saying this is false? Granted anything that I've LOADED into memory takes the same time like loading iGuidance but when I wrote a division loop in vb and let er rip it was 20-24% faster every time. EVERY TIME.

Sugar Pill? Hardly. I'm thinking everyone is loading from their memory card and assuming the processor has a big part in this action and not seeing any faster results.

Load up a math routine. Its faster.

Copy

I ran this yesterday on my mogul and I didn't notice any change. I ran SKTools benchmarking utility and it showed no different results.

how in the do you have a plan so cheap from sprint???

I'm working on a definitive solution to the does it go faster question:

First - there's one thing for sure - the battery drain is linear and parallel to the speed setting.

Second - loading doesn't seem to go faster

Third - math operations DO go faster

Four - it is definately doing SOMETHING...

Copy

stop the insanity...

Test this:
run navigation software, time how long it takes to route two distant points.

turn booster off and repeat.

also try variation of running from storage card vs running from main memory.

I tried from card only and no speed difference with/without booster.

I may have an explanation for all this.
I will need any users to verify, those that have "acbPowerMeter", or "CPU-ID" or "Xcpu" or "PHM" installed (with sticky engine disabled).
OR Any program that shows the current CPU status.

In all overclock programs, they implement a system to disable the processors auto-scaling BEFORE implementing their own overclocking...

If this program is from HTC then it would disable the processor very efficiently before it acted to overclock, (which we do not see it overclocking), so you should at least have a processor running steady at 416mHz with auto-scale disabled....
Disabled it runs at 416mhz, as it does when in camera mode, or using external power...

This is just a theory untill most users here can confirm.

Another theory is that the program itself running in background, "trying" to do anything would trigger our units to stay running at 416mhz and not auto-scale down...

Both senarios would fit the simptoms of feeling faster without actually showing an increase in heavy tasks, since it would be at this speed when doing tasks anyway... :o

EDIT: has anyone checked the Bus and mem speed with this proggy?

The fact that most users here confirm a difference at all states that something must be taking place.. even if it is mass hysteria ! lol kiddin :)

iGuidance 4 & xCPU

All took 10 seconds to load the program.

Calculating the same 700 mile route:

Autoscale - 16 seconds
208 Locked - 17 seconds
312 Locked - 14 seconds
416 Locked - 12 seconds
520 Locked - 10 seconds
624 Locked up

each time I closed out of the program to re-run it. Ran each test backwards (520 first then 416, etc) During EACH menu refresh(draw), 208 was NOTICABLY SLOWER than the 520 screen updates.

I ran 520 and 208 2x at the end and came up with the same times.

I had acbPower running as well and each speed drop resulted in around 20mA drops.

More to come. This is far from over. (once I get time :( )

Copy

ok. I put the HTC per on top of the xCPU heres what I've observed:

The indicator for xCPU current scale speed has locked to 520. The acbPower is at a rate similar to a constant 520 draw (228mA) and each program is set to "autoscale". Re-running the same test with iGuidance @520 proves to be 10 seconds.

taking it off.

nothing changed. even the speed indicator is locked still @ 520. resetting the auto capability in xCPU has resulted in the same 520 readout.

rebooting it. waiting.. (not as long as wm5 wohoo)

Well, it appears that I've broken my autoscale ability with xCPU now. The indicator is not changing and the acbPower reports a constant flow of power @ a higher scale of amperage pull. Reinstalling xCPU and reporting later.

Copy

reinstalling HTC and going to the setting, the X was still checked leading me to believe that all this is IS a bunch of reg tweaks of some sort.

So HTC is now unchecked and my xCPU autoscale is hosed. once I'm home tonight I'm going to rebuild my kitchen with the reg tracker and report back.

Hope my battery makes it out of autoscale mode.. :(

Copy