So, Luv's "sugar pill " designation is pretty well accurate ;)

If I remember right, the OEM in BuildOS had helmi's name on it, so I tend to believe it's more than a sugar pill. Maybe it should be renamed "Helmi's Magical Mojo." My device does seem "snappier", so I just assume it's the result of some other process optimizations. Whatever, I'm keeping it unless helmi and luv confess that it's a practical joke.

same here, no point in removing it until its a confirmd dud. sure feels like it does 'something' to the performance... "Helmi's Lil Helper" is what i'll call it from now on...

It installed, but didn't run for me under WM5 AKU 3.5.

WE have to remember that each processor in our phones was only benchtested at the factory up to a certain point past 420(at least this is my understanding). After that it will be processor dependent as to whether it can handle speeds faster than 520 (assuming it is really overclocking it, which we cant seem to see prove). so it is not surprising to me that some are seeing it lock up at 624. some of the kitchen builders told me they saw a battery decrease from using it at 624 and think 520 is the best setting. Just Sayin'

Actually the credit in Build OS goes to Luv2chill. That said, it could still have errors (like the power save registry thing) that either get overwritten or otherwise garbled. I couldn't pretend to know half of what Helmi and Luv2chill have forgotten about WinCE OS, and was only reporting my personal findings about the OEM's performance.

Real world test results.
Application used: TOMTOM5. (maps and exe located on storage card)
Platform: Apache Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) (11-17-07)
Variance: +-2 seconds
Conclusion: No distinguishable difference.


@620
Launch: 1 min 37 seconds
Atlanta to Miami: 24 sec

@520
Launch: 1 min 37 seconds
Atlanta to Miami: 21 seconds

@ normal
Launch: 1 min and 35 secs
Atlanta to Miami: 23 sec

Yeah, no measurable difference... but it FEELs faster, doesn't it ;)

Funny enough, it does.