[krohnjw]

Originally Posted by Asphyx

I'll say it again for those who are so devoted to 6.5 that they will make up all sorts of stories to try to get people to use a buggy OS...

The SOFTWARE does not use a voltage!!!!! the HARDWARE does!!!
It does not take any more power to run program A than it does to run program B.

The difference is in what the two softwares do and that is all about the settings!

TF3D only eats more battery if you have it checking for email every 5 mins and run push internet. Other than that it does not use any extra power or hardware functions. More Ram yes! But thats becuase it displays a hell of a lot more information than Titanium does! As for updating in the background well unless you have push internet and 5 min mail enabled there is nothing for TF3D to update when idle or suspended. No more than titanium does. Weather doesn't update when your not on that tab...SMS updates the same no matter what your running.

I have run probably 20 different flavors of 6.5 and Im never ONCE got more battery life...if anything I got less because I spent so much battery power resetting a crashed beta interface.

Now this is the point where some 6.5 fanboy says but it's the future you need to use it to be current!

to which I say stability is more important than keeping up with MS' release schedule!

You can compare WM 6.1 to 6.5 all you like but that is not the comparison nor the statement made.

The statement

"The SOFTWARE does not use a voltage!!!!! the HARDWARE does!!!
It does not take any more power to run program A than it does to run program B."

is both incorrect and correct! Hardware IS the part that causes battery drain, but 2 programs can VASTLY use the same hardware differently!

If software A does nothing but load a simple interface and sit and software B loads the same simple interface but performs many other CPU operations (perhaps gathering data or simple doing math to do math!) then software B will indeed drain the battery faster.

Performing CPU operations, retrieving and storing data from memory (RAM, NVRAM or any sort of solid state or hard disk) and drawing/redrawing the UI *USES THE HARDWARE*. The hardware here is the CPU, the BUS, RAM, Disk (Solid state in the case of the TP) or any other peripheral queried.

These operations range from the simple of reading files (registry/hive entries or config files if not cached in memory) to the more abstract of the memory manager swapping out dirty pages to retrieve data requested by a program (now you're using both disk and RAM) as well as the arithmetic operations that have to happen to make everything work. These are things you don't even see. Throw in graphical operations rendered on the CPU (or the GPU if supported) and you are using more hardware! All of this costs power - and the amount of which varies by the number of operations done by a program the number of which generally increases with their complexity - 1 command != 1 CPU operation, as well as the number of other pieces of hardware touched to get the job done (Does the program need to hit disk or query a device for status). Rendering a complex interface generally requires more operations than a simple interface and hence will use more power.

Now, the merit of how *much* more power can be debated between any 2 programs but to simply state that any 2 programs not using the Radio/GPS/Gyro use the same amount of power is either dishonest or uninformed.

The difference is in what the two softwares do and that is all about the settings

This is not entirely true - 2 pieces of software can accomplish the exact same task with varying levels of inefficiency. Efficient code will require far fewer operations than VERY inefficient code which will lead to increased CPU time (due to requiring more operations) and as a result more power will need to be consumed to do the same task. As they say you can paint a turd gold but it's still a turd. You could tweak the settings to your heart's content for our 2 fictional applications above and you'd always end up with the inefficient code requiring more power (assuming the same configs) as you can't change the op code of the compiled binary.

Apply that to TF3D and Titanium and there could be a large difference in the number of operations required to perform a task (such as a screen redraw) or there could be a negligible difference (without some sort of utility to measure it's all speculation). But it is wholly possible for one to "use" more power to accomplish the same task as the other.

I'll say it again for those who are so devoted to 6.5 that they will make up all sorts of stories to try to get people to use a buggy OS...

None of this is a story of any sort - feel free to debunk any of the above if you would like.