Currently Being ModeratedDec 2, 2012 1:06 AM (in response to faizalbahadon)
Showing a time remaining screen shot without what's actually running and how much load is on the machine or the strength of the backlight is half of the picture. At 91% with decent load on the CPU or significant SSD access, 2 hours is not an unrealistic number.
I've noticed no decrease in system performance or cooling since upgrading multiple machines to 10.8.2 (two of which are 2012 MacBook Airs). One way to quickly determine if the issue is with 10.8.2 would be to roll back to a Time Machine backup that's on 10.8.1 if you have one available.
Currently Being ModeratedDec 2, 2012 11:38 AM (in response to JasonFear)
While faizalbahadon might have used wrong display/visual examples of the issue he's having, the thing is, these internet forums are obliterated with posts of battery issues and overheating, which both relate directly to the latest upgrade to 10.8.2. I too was a happy user of my 13" MBP since 2009; didn't even run into issues with the Snow Leopard upgrade, but with Mountain Lion, my laptop fan is always working, and the battery never seems to fully charge to 100%. No one seems to have any answers.
Currently Being ModeratedDec 2, 2012 12:05 PM (in response to 545323)
The problem is, we're on an Internet forum and most of the examples provided are anecdotal. Even a thread with hundreds or thousands of posts related to common theme does not automatically assume that upon upgrading a machine to 10.8.2 means shortened battery life and overheating. Heck, just about every time a new dot rev comes out there's threads galore with the usual:
- My wireless doesn't work
- My battery life has been reduced
- My machine now overheats
- My machine is now sluggish
I can easily dig out these threads for 10.8.1, 10.8.0 and each version of Lion and probably Snow Leopard. Plus my recommendation of rolling back to 10.8.1 to "verify" the issue with 10.8.2 is a smart strategy, it's basic common technical troubleshooting sense. If adding/changing something causes a degradation in performance then it's logical to remove it or roll it back. If the roll back fixes the issue then the next logical step is a backup, a clean install and update to the offending version to see if the issue continues to replicate.
Lastly, the user made a specific thread with specific exams but gave half the story. If he/she wishes to lump his issue(s) in with the collective whole then he/she should have posted in those threads. Otherwise rather than trying to address another thread in this thread, you focus on the issue at hand. If every response was: "There's another thread on this, so there must be a problem," then we could also spam that with 98% of the topics created.
Here's some more anecdotal evidence, seeing we're doing that.
Currently Being ModeratedDec 2, 2012 2:27 PM (in response to JasonFear)
Yes yes, sure I understand your desire to stay objective and not jump into conclusions. Admittedly, people will always blame some unrelated events for some issue they don't understand. But if my computer battery works like a gem for 3 years and suddenly, after an upgrade, it goes out of whack, what am I supposed to think? Yes, you are right, others also reported issues with Snow Leopard updates, but that didn't affect me, so it almost seems like such issues affect people randomly, depending on various factors. FYI, a few hours ago I did an SMC reset on my Mac, which completely fixed the issue. The fan rpms dropped and when I unplugged the power adaptor, the "Calculated Time Remaining" indicator almost doubled in time. Who knows, there are probably countless reasons that caused this issue, couldn't an OS update be one of them?
Currently Being ModeratedDec 2, 2012 9:54 PM (in response to 545323)
It's very possible that an OS update could cause some change in system performance that was previously seen as routine. That happens all the time and just about every update usually comes with some degree of quirkiness/randomness. I'm in no way trying to discredit or dismiss the OP's request for assistance, but if one is going to troubleshoot a problem then one needs to have the all facts and understand the variables. If you know 50% of the parameters you're working in how can you realistically troubleshoot a problem effectively.
What if the OP had a run away process caused by a 3rd party application that's set to run on startup which does not behave properly with 10.8.2? It's screaming away with a memory leak and using 30% of the CPU constantly. If that's happening then that battery life is perfectly normal. Because we don't know whether or not that's the case we have to assume the worst case scenario, as frequently that's the problem.
I'm glad the SMC reset fixed your issue, resetting the SMC is a great way to address the exact problem you were experiencing. The good news, a software update (such as updating to 10.8.2) is completely seperate from the SMC, so the software level shouldn't break the firmware level.
Currently Being ModeratedDec 3, 2012 7:03 PM (in response to faizalbahadon)