what on earth is going on with this. 3:19 on 100% with just safari open?
Looks like you actually have much more than just Safari open..
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Battery life for 13" and 15" Macbook Pro
- Thread starter fokmik
- Start date
-
- Tags
- batteries macbook 15"
- Sort by reaction score
Looks like you actually have much more than just Safari open..
Yup, estimates are kinda useless based on posts like that. Also from the looks of it, he probably just unplugged and then use this to make a statement. I am giving battery threads a wide berth from now.
Actually it says 30-day standby.
I Amin the same boat. Sierra reinstall seems to have solved my "active" battery use problem, but it drains like crazy when sleeping, especially overnight.
Admittedly, I'm far less concerned about this because it's extremely rare that I am not able to charge my MBP overnight. I have a hard time imagining many situations where that would be the case.
If I can consistently get 8 hours of battery in continuous use, i.e. on a flight/while traveling, I'd be happy.
Not true. I have had it unplugged for approx 10 minutes before this. The other apps open are CPU/memory/network-light and I wouldn't expect them to cause any issue. I got all-day battery life out of my previous gen MBP with the exact same apps running. The estimate revised to approx 4 hours but its still terrible.
I'm currently reinstalling Sierra on it to rule out a software issue. It is certainly abnormal to have to run through 6 power cycles in 36 hours running very light apps with no significant load to the computer.
I don't own a MBP but had similar problems on my retina MB - I followed the advice on this thread to reduce the standby time and had dramatic results:
https://forums.macrumors.com/threads/standby-lid-shut-battery-drain-fix.1894736/#post-21503383
My battery would usually drain 5-6% overnight but now I lose next to nothing. I actually reduced my standby time to 5 minutes (sudo pmset -b standby delay 300).
Again, I don't own a MBP so my apologies if this has nothing to do with your battery drain in standby mode but I think it is a possibility based on my experiences with my rMB.
I feel like a lot of you are talking about how you discharge with only like 6 Watts doing light internet browsing? Mine is always at 12-20W.
Slightly disappointed with battery performance today. Light usage: PDFs, Word, PowerPoint, a few Safari tabs, iTunes streaming over Bluetooth (local files) and 7 hours used, 14% battery left.
Hopefully it will improve after a few cycles. My style of working - two windows in full screen mode and frequent flicking between applications - might be more graphically intense due to the animations than Apple's wireless web test I suppose. But still, the usage could hardly get lighter.
Hopefully it will improve after a few cycles. My style of working - two windows in full screen mode and frequent flicking between applications - might be more graphically intense due to the animations than Apple's wireless web test I suppose. But still, the usage could hardly get lighter.
Porn is bad for battery. Jk. But really, certain websites draw high power - plugins, ads, etc. You should see what is offending and see if you could live without certain pages. Macrumors draws big power for me sometimes. Appears to be random ads. Safari needs some software fix.
Thanks for the tip. I will probably change my settings for that. But, I don't think Apple intended for us to change the sleep setting to get 30 day standby, did they? Hopefully I Apple will update to fix this. Otherwise the sleep setting will do the same, especially with the super fast SSD.
Battery life also beyond awful here (13 touchbar). I've been tracking usage in a spreadsheet and today managed a whopping 2hr54 of web browsing on battery. There's no indexing or anything going on that I can see, I just opened and started using from scratch with no files being transferred as this is my first MacBook.
Time to send it back?
Time to send it back?
The more people return and state clearly the reason, the clearer it will be to Apple what they have done.
Or you could read this informative thread and follow a couple troubleshooting tips to get 9+ hours. Of course everyone with out-of-the box bad battery life has a legit reason to not be satisfied and return it. Apple really should have fixed a thing or two before having us all beta test. But I recommend the former, since this really is a nice machine.
There is nothing to beta test, the battery is too small. Couldn't be more obvious.
In a nutshell, reinstall Sierra if you data migrated. If not, use Coconut Battery and Activity Monitor to see what apps are killing your battery. Keep an eye on watts. If you need whatever apps are killing battery, then return computer.
[doublepost=1480115192][/doublepost]
"Obviously" you should return your MBP then. End of problem.
No, sorry, but you're not doing the math right. The post you responded to was exactly correct.
Let's look at the units first. A battery is rated for how much energy it stores in Watt-hours or W*hr. A Watt is a Joule (unit of energy) / second. An hour is obviously a unit of time and can be expressed as seconds. So a W*hr is J/s * s = J (energy).
Sometimes a battery's energy is expressed a amp-hours or A*hr, when a particular output voltage is assumed. Also can be expressed as milli-amp-hours, but that's just scaling it by 1000. So your contention that you should use amp-hours to express energy is not correct. In fact, using amp-hours requires you to specify the voltage. Using watt-hours does NOT require specification of the voltage. This is why Apple specifies the battery energy storage capacity in W*hr. In a modern computer different systems (CPU, DRAM, SSD, screen) use many different voltages, so specifying in A*hr would not make sense, since there is not a common voltage used. The battery outputs a certain voltage and the sub-systems need to use voltage regulators to convert the battery output voltage to whatever is needed. The CPU will down-convert. The screen will need to boost.
So the poster you responded to was doing exactly the correct calculation. Measure the overall system power usage in W. Divide the battery energy capacity (in W*hr) by the power consumption (W) to get run time (in hr).
In some previous posts, you've tried to express the power consumption of the machine in A*hr or mA*hr, which is not correct. An amp is a measure of current (coulombs/s). Multiplying amps by time just gets you coulombs (a measure of electric charge, not energy).
This post here shows the correct way to do the calculation. See how when the battery is specified in mAh, the voltage must be specified also. He then converts to an energy unit (W*hr) by assuming a ~12V output voltage.
Last edited:
Per my post a few pages ago, I performed the troubleshooting tips (to include SMC reset and OS reinstall), and still get between 6-7 hours.
This post here shows the correct way to do the calculation. See how when the battery is specified in mAh, the voltage must be specified also. He then converts to an energy unit (W*hr) by assuming a ~12V output voltage.
What is your MBP configuration?
What is your normal use case ?
Thanks for the feedback
Did you do the step of seeing what's draining the battery? If you run the battery monitors, even just the built in Activity Monitor, you can see what the offenders are. It might surprise you that otherwise considered lightweight apps are drawing significant power. You can than make the call if you can live without that app constantly running. Normal draw for me is about 5-6 watts. You must be in the 8-9 range based on your battery life. Something is killing it.
Postman, Robomongo, iTerm, Atom, Chrome (w/ Multiple tabs), Safari (w/ Multiple tabs), Xcode 8, Simulator, Messages