If this update reduced power consumption and improved battery life in some way it would have been stated, if only to offset the bad PR relating to the removal of the time estimate.Not really. I seen Apple add and remove stuff in updates without telling us couple times before.
So what was the need in removing the "Time Remaining" in the first place? Hopefully they bring it back.
How 'bout that graphics issue???
I wish their was a "down vote" choice for all the negative responses from the anti-Apple trolls on this forum. So it's anecdotal, placebo effect when something is improved but it's fact if it's negative?
I have ben plenty critical of Apple at times but some of you are ridiculous. You should go play in traffic with Google maps clutching Surface 4's.
you'll be amazed at how removing the time estimate creates a placebo for improved battery life
Definitely will do that. If we are allowed to have intensive and opinionated discussions, then we should have a down vote option. This isn't Facebook. Moderators can still moderate.We used to have it a loooong time ago. Can't remember why Arn took it away. It was quite a storm for a bit. Email Arn. Tell him you want it back. Just don't let it be anonymous.![]()
Pure PLACEBO! You remove the way to measure something and then people overestimate it. Devious psychological tricks 101. Well done Timmy!
I guess removing "time remaining" did the trick. And I bet Tim and Phil are laughing their a$$e$ off right about now.
Never mind, right about now, Tim is sitting next to Peter Thiel at Trump Tower with a sad Pepe the Frog face on.
It's just not an accurate estimate. You used to be able to set it to show that number all the time in the top bar, but Apple got rid of that a while ago.
Back before app nap and timer coalescing, the time remaining estimate was somewhat accurate because the usage was consistent. Now with those features, the CPU can go from using almost no power to used a lot of power and back again. It does this wildly depending on what the user is doing.
The time remaining estimate looks at current power usage to make the estimate. So if you are opening an app, the CPU is running at max power for a second, the time remaining estimate gets really low. Then the app finishes loading, the CPU goes back to using almost no power, the time remaining estimate gets really high.
Since the OS can't know what you will be using the computer for the future, it can't really give you an accurate estimate. Even if it just goes off of average usage over the past hour or so, the future estimate will be very inaccurate.
This kind of sounds like an Apple PR media release were it not for the factual inaccuracies. How much of this do you actually know verses guess or presume?
What you claim doesn't make a whole lot of sense. The estimate didn't update continuously and was clearly based on some sort of average. So I doubt it's based on a simple instantaneous power draw updated every so often as you suggest. If it did that it would lead to massive swings in the estimate that are just not observed in reality.
Many people are claiming they found the estimate reasonable and accurate enough to be useful, which wouldn't be the case if its method of calculation was as useless as suggested in your post.
Fortunately Apple were decent enough to keep the estimate in Activity Monitor.
So you're saying a company with the size and resources of Apple couldn't update a battery indicator alongside introducing those new features, and even so, after years of real usage feedback anonymously sent by its users?It's just not an accurate estimate. You used to be able to set it to show that number all the time in the top bar, but Apple got rid of that a while ago.
Back before app nap and timer coalescing, the time remaining estimate was somewhat accurate because the usage was consistent. Now with those features, the CPU can go from using almost no power to used a lot of power and back again. It does this wildly depending on what the user is doing.
The time remaining estimate looks at current power usage to make the estimate. So if you are opening an app, the CPU is running at max power for a second, the time remaining estimate gets really low. Then the app finishes loading, the CPU goes back to using almost no power, the time remaining estimate gets really high.
Since the OS can't know what you will be using the computer for the future, it can't really give you an accurate estimate. Even if it just goes off of average usage over the past hour or so, the future estimate will be very inaccurate.
How 'bout that graphics issue???
So you're saying a company with the size and resources of Apple couldn't update a battery indicator alongside introducing those new features, and even so, after years of real usage feedback anonymously sent by its users?
So you're saying a company with the size and resources of Apple couldn't update a battery indicator alongside introducing those new features, and even so, after years of real usage feedback anonymously sent by its users?
They only changed it because the numbers on the new (2016) MBP look like ****.Apparently you struggle with reading comprehension. What he said was that the battery estimate was never accurate to begin with. It may as well display any random number because the estimates are always based on what's happening at the time of the update. This leads to wildly changing remaining times and a really useless indication of time remaining.
Your iPhone doesn't tell you time remaining for this very reason and yet no one has been complaining about the lack of such indicators on the iPhone.
Indeed. On first use on battery mine was estimating 3-4 hours, indexing still running, along with initial Crashplan backup. After indexing and backup finished, next outing running on battery, estimate jumped to over 9 hours.I often wonder how many of these "poor battery life" complaints are due to Spotlight indexing all the new stuff that just got dumped onto the machine when people upgrade to a new laptop, and then when spotlight is done doing its thing, battery life goes back to normal.. which may coincidentally coincide with a minor OS update.![]()