bApTizE, Thank you for posting your results! It is exactly what I needed.
Your results suggest that a battery charging issue could be the problem and cannot be ruled out; as could it be a problem associated with the accuracy of how the battery readings are reported (but I doubt it is the latter). But here's what I'm finding based on your obserations with ML.
- Your battery life is approx. 60% of what it should be based on the initial capacity of 5516 mAh and an average current draw of 707 mA. I would expect your battery to last almost 8 hours (which is what is reported from the Time Remaining field) since 5516 mAh / 707 mA = 7.8 hours. But, you'll noticed that after 1 hour, your battery has dropped to 75%, meaning you are only getting around 4 hours the way you were using you computer during the test.
- Your current drop is greater than expected (707 mA expected versus 1408 mA observed). After 1 hour, with an average curent of 707 mA, I would exptect your remaining current to be 5516 - 707 = 4809 mAh. But, your results indicate 4113 mAh. This isn't close and would reflects an average current of 5516 - 4113 = 1408 mAh. This is about twice the drain that is reported (707mA) and is greater than your largest current draw (1089 mA)! This means that either 1) the software is reporting an incorrectly low current drain or 2) the battery was not charged to its full capacity due to over/under charging. I suspect the latter.
What this means is that we can't rule out a battery charging issue as the root cause of what's going on. Similarly, we can't completely rule out some other bug that is incorrectly reporting the actual current draws. I'll need to think about how to troubleshoot this more, but it means that the problem IS NOT necessarily the current drain based on what you're dong on the computer since that appears to be 707 mA, which seems reasonable.
These findings also suggest that the problem is software (or possibly, but not as likely - since it works with Lion, firmware) or configuration / cache related, and not battery related. In other words, a battery replacement isn't likely to fix the problem - unless the battery was previously damaged due to under/over charging or heat.
I lean toward configuration, cache, or software rather than firmware because my MBP worked with Lion but misbehaved under ML. It it were solely a firmware issue, I would expect it to continue to misbehave with Lion. For the same reason, I don't think the firmware is reporting incorrect current readings.
Good data and thanks again for testing. Now to give it a bit more thought as to why. But I'll definitely share these findings with Apple via their feedback URL since I think they should really look at their charging algorithm to solve this one.