|
|
||||
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 Last edited by CopyCounsler; 01-22-2008 at 07:30 PM. |
|
||||
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... Last edited by CopyCounsler; 01-23-2008 at 02:53 PM. |
|
||||
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. |
|
||||
Quote:
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... Last edited by Maxx134; 01-24-2008 at 09:48 PM. |
![]() |
|
|
|