Machine Learning. What do you think Nest does? If Apple can't do such an elementary think as this then they should stick to security bug fixes.
Pretty defeatist. Past experience is always usable as a predictor of future behavior. It's only a problem until somebody else solves it and proves it can be done. Then suddenly the competition figure it out and deliver their own implementation. It just takes thinking out of the box but you're suggesting Apple is not capable of that.A Tesla or Nissan Leaf can't do it accurately, for the same reasons a phone can't. You simply cannot predict what usage is going to take place going forward. This isn't a thermostat which reacts to regular patterns.
Seems like plenty of people are just fine with and even like seeing remaining percentage of battery life and don't have any particular misunderstandings or fears of it. Not sure what "based on people" means as it doesn't seem to say anything in this context.Based on people.
[doublepost=1512393204][/doublepost]
Sure you can. You just write an algorithm to do it. It’s not hard after all as it’s just software.
Based on people.
[doublepost=1512393204][/doublepost]
Sure you can. You just write an algorithm to do it. It’s not hard after all as it’s just software.
So you want the phone to do even more work, constantly, just to show you a time that will always fluctuate based on what you’re doing? And you don’t think that would affect the battery life?Based on people.
[doublepost=1512393204][/doublepost]
Sure you can. You just write an algorithm to do it. It’s not hard after all as it’s just software.
Percentage still makes a difference.That percentage thing is all in your mind. They do the same thing, when the bar gets red, guess what, you need to charge your phone.
Long story short: there should be an option to choose our preference.
Explain.Amazingly ignorant.
This would be insignificant relative to all the other memory sucking things Apple will add to iOS 12.So you want the phone to do even more work, constantly, just to show you a time that will always fluctuate based on what you’re doing? And you don’t think that would affect the battery life?
Nothing really wrong with it. Just an added step that hasn’t ever been necessary in the last decade of iOS use.Whats wrong with using the battery widget?
You can’t go by time because all usage is different. Phone call, local music, streaming music, YouTube, Facebook, games, all different processing power. Heck, even web browsing varies depending on ads and site formats.
It's easy to see that they couldn't fit both the graphic and the percent in there along with the cellular and WiFI connectivity indicators. It's a bit odd that we can't choose whether percent is displayed instead of the graphic, but I bet that will come with a future update.
Better yet: Make all of the data displayed left and right of the notch behave like Apple Watch complications and let us customize each one to display what we want. I don't usually pay attention to the cellular and WiFi indicators unless I'm having connectivity issues, so perhaps I would rather go to the control panel to check those and instead display battery graphic + percentage and today's date?
Originally I was pissed that you just had the icon, but I've come to agree that seeing the percentage made me paranoid. That being said, I do think we should have a choice.Personally, I prefer the battery icon. I rarely need to know exactly how much battery I have and just a general idea is fine. A percentage adds a little amount of clutter that I would rather not see all the time.
GPS has much more going for it as far as known quantities. Speed limits and traffic on routes probably account for 95% of the time estimate. Phone usage is much more random. You can be on standby waiting for a call all day, but at the end of the day you decide to use Waze to drive home. Phones can't predict what you'll do with it, and they have a big disparity in the battery usage of different activities. GPS time estimates is a much simpler formula.Not that I care for time remaining, but they would do it the same way a GPS can predict your arrival time. If your usage goes up (for GPS, if you speed up) the time remaining decreases in real time. As your usage goes down (for GPS, if you slow down or hit traffic) the time remaining increases. It recalculates and adjust on the fly.
I miss the %, because there is no quick way for me to tell if my phone is actually at 100% when I pick it up off the charger. When I put it down on the wireless charger it will say the % below the over-sized green battery symbol.
Others have said you can check the % under the battery widget. This is true, and a workaround that does work, but it is an extra step.
The current battery symbol is so small, it actually hard to tell if you have 90% or if you are at 100%...
It hasn’t been that long. Development pipelines are not as agile or reactive as everyone would like. Ask for something now and if you’re lucky you’ll get it it about 4 months to a year later. That’s because there are many things in the pipeline and they have to be prioritized.Future update now that we discussed it perhaps? We are on iOS 11 and they haven't thought of it yet?
GPS has much more going for it as far as known quantities. Speed limits and traffic on routes probably account for 95% of the time estimate. Phone usage is much more random. You can be on standby waiting for a call all day, but at the end of the day you decide to use Waze to drive home. Phones can't predict what you'll do with it, and they have a big disparity in the battery usage of different activities. GPS time estimates is a much simpler formula.
Would that kind of information be useful though and, more so, perhaps even just be misleading and more of nuisance than anything else?All it has to do is calculate based off of current usage. It really is much more simple then you make it out to be. If you are on the phone and look at it, it will tell you how long you have if you keep talking on the phone until it is dead. As soon as you hang up, that time remaining increases based off of the now current usage (not on the phone, but still in non-standby mode). Once it goes into standby, this can be recalculated based off of low power mode.
I could easily program this in windows, All it has to do is calculate based off of current voltage usage, as it goes up, the time remaining is decreased, as it goes down, time remaining is increased. I would need to know the minimum voltage of the battery when the device shuts off. I am not an iOS programmer, so I would have no idea how to do this in iOS, but it would be easy enough to do in windows.
Now, I see no real need for this, but wouldn't hate it if they implemented it with an on/off switch. Just like numeric % of battery remaining, love it or hate it, there are people who want it back, and if it is implemented like it was in the past (on/off switch), no one is forced either way.