Quote:
|
Originally Posted by saqer
so u're saying running VJay's program simultaneously with either PHM or XCPUscalar will allow you to underscale successfully?
|
Yes
Quote:
|
Originally Posted by saqer
Can't there be bad consequences running Vjays program constantly, though?
|
No Ive done it many a time, it disables on shutoff or when really engaging camera wich sets back to 416Mhz.
Quote:
|
Originally Posted by saqer
You would also not be able to use your camera, correct?
|
You can use it fine anytime it will default speed back to 416Mhz.
Nothing underclocks better than our built-in autoscaling.
By itself lowest Ma for me is 62Ma.
My Lowest Miliamp use with LumosII activated:
XCPUscalar = 131Ma
PHM =121Ma
LumosII with either set to lowest clock, then closed = 102Ma
Problem is our units jump up to 416Mhz right away on a single tap.
What underclocking can do though is set a "cielling" to limit Ma usage and it wont go as high as if it was running at 416 or 512.
But then your Ma gains are lost with constannt higher Ma idle with forced underclocking.
So thats why XCPUscalar did well to disengage and have a "passive mode" to let our own units autoscaling take over.
Edited for clarification, your testing mat differ:
My best savings were from using either overclock with Lumos(activated, then turned down brightness in settings), then closing overclock program and let Lumos hold that setting until I turn it off or it shuts off by itself which automatically shuts Lumos off and unit autoscales itself normally again. the absence of the overclock program gave me more memory and 20-30 better Ma usage.
Oh well thats all I have to say, I gave up on all this a while ago but just needed to spit out my last 2 cents again
