Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
What exactly are you referring to here? 3D Touch on Apps? :S
Try this: slowly apply pressure to any app on the home screen that supports 3D Touch shortcuts. The bubble for the shortcuts slowly expands out of the app icons based on the pressure you're using.

I'd never noticed it before Beta 5, but maybe it's been there this whole time.
 
Low Power Mode affects things that would have a meaningful effect on battery power. If Night Shift uses up enough battery to make Low Power Mode savings ineffective enough that they aren't saving as much as they should be, then it would make sense to disable those to save the power (given that that's the whole point behind it). Various options have been grayed out in relation to using Low Power Mode from the beginning of its introduction, so there isn't much new there in relation to that either.
My point is that the user should never have to worry about what options consume power. If they want to use Night Shift and Low Power Mode at the same time, they should be able to. Users shouldn't be forced to choose between features and battery life.
 
Happy to see the security feature on notes .. What I would really like to see for IOS10 would be the first time apple just announces that they are finally ready to combine both OS .. They can do it .. If they dumb down el capitian for Mac book they can make one OS
 
My point is that the user should never have to worry about what options consume power. If they want to use Night Shift and Low Power Mode at the same time, they should be able to. Users shouldn't have the ability to choose between features and battery life.
So if using Night Shift makes Low Power Mode fairly ineffective and basically people don't see the battery savings from it that they would expect or need, that would be OK to mislead them that both Night Shift and Low Power Mode are on but they are just not getting much from Low Power Mode?
 
  • Like
Reactions: warden
It put my 6s+ into restore mode when I attempted to update it. Not sure why just mine.

Nope did it to me too. I was Having a nice cold beer and did the update and then I had no phone! I wonder why, this is the only one I had issues with. I am currently installing the ipsw file.
 
So if using Night Shift makes Low Power Mode fairly ineffective and basically people don't see the battery savings from it that they would expect or need, that would be OK to mislead them that both Night Shift and Low Power Mode are on but they are just not getting much from Low Power Mode?
I see your point. Here's how I think it should work. When low power mode is enabled, Night Shift will not automatically begin. If the user chooses to enable it, however, it should be allowed to happen in low power mode (User consciously chooses to enable power hungry features without disabling other power conserving adjustments).
 
It put my 6s+ into restore mode when I attempted to update it. Not sure why just mine.

I you haven't restored yet, I found an easier way to get your phone back. I plugged it in to iTunes and it actually asked me if I wanted to update or restore so I hit the option key and clicked on update looked for the ipsw file and my phone is back! Now I am downloading the Beta 6 OTA again.
 
I see your point. Here's how I think it should work. When low power mode is enabled, Night Shift will not automatically begin. If the user chooses to enable it, however, it should be allowed to happen in low power mode (User consciously chooses to enable power hungry features without disabling other power conserving adjustments).
And I understand what you are trying to get at, but with that in play it seems that users would be misleadingly believing they are getting meaningful benefits of Low Power Mode when they very well might not be under those circumstances, and that doesn't seem like a good thing either.
[doublepost=1457388452][/doublepost]
Thanks I didn't know it was a Siri feature at 20%
Likely not a feature as much as a glitch/oversight somewhere.
 
And I understand what you are trying to get at, but with that in play it seems that users would be misleadingly believing they are getting meaningful benefits of Low Power Mode when they very well might not be under those circumstances, and that doesn't seem like a good thing either.
[doublepost=1457388452][/doublepost]
Likely not a feature as much as a glitch/oversight somewhere.
I think there will always be some benefit.
Regular Usage + Normal Mode + Night Shift = Poor Battery Life
Regular Usage + Normal Mode = Average Battery Life
Regular Usage + Low Power Mode + Night Shift = Good Battery Life
Regular Usage + Low Power Mode = Great Battery Life
 
I think there will always be some benefit.
Regular Usage + Normal Mode + Night Shift = Poor Battery Life
Regular Usage + Normal Mode = Average Battery Life
Regular Usage + Low Power Mode + Night Shift = Good Battery Life
Regular Usage + Low Power Mode = Great Battery Life
Well, I guess there's likely a range as to what's defined as effective battery savings for Low Power Mode to be called that based on Apple's design of it. With something enabled or set to certain settings that effectiveness might be below that standard and thus Low Power Mode doesn't apply. So perhaps regular usage and Low Power Mode and Night Shift is just slightly above average battery life, but not quite up there even at good battery life, and thus doesn't quite cut it.
 
Well, I guess there's likely a range as to what's defined as effective battery savings for Low Power Mode to be called that based on Apple's design of it. With something enabled or set to certain settings that effectiveness might be below that standard and thus Low Power Mode doesn't apply. So perhaps regular usage and Low Power Mode and Night Shift is just slightly above average battery life, but not quite up there even at good battery life, and thus doesn't quite cut it.
Its still saving some battery. And again: Low Power Mode shouldn't interfere with user facing features.
 
Its still saving some battery. And again: Low Power Mode shouldn't interfere with user facing features.
It already does change user facing issues from the beginning, so that's not exactly new or something that hasn't been part of it before somehow. And I understand it's saving some battery, but it seems like likely not enough for that to qualify as Low Power Mode. It sounds like what you'd like is basically some sort of Variable Power Mode that you can configure how much it saves based on different pieces--nothing really wrong with that idea, it's just that it's not what Low Power Mode is, and that kind of level of customizability is historically not really something that Apple offers (that's not to say that's good, but just that's more or less how it's often been and is with iOS).
 
It already does change user facing issues from the beginning, so that's not exactly new or something that hasn't been part of it before somehow. And I understand it's saving some battery, but it seems like likely not enough for that to qualify as Low Power Mode. It sounds like what you'd like is basically some sort of Variable Power Mode that you can configure how much it saves based on different pieces--nothing really wrong with that idea, it's just that it's not what Low Power Mode is, and that kind of level of customizability is historically not really something that Apple offers (that's not to say that's good, but just that's more or less how it's often been and is with iOS).
Low Power Mode is something that belongs on Android phones: it shouldn’t even be a part of iOS. Ideally, the end user should never have to worry about power management, should never have to choose between features, and should never get a subpar experience for the sake of longer battery life. If there are behind-the-scenes adjustments that can be made to improve battery, they should be baked into the OS. Otherwise, poor battery life is the fault of poor design choices.
 
Low Power Mode is something that belongs on Android phones: it shouldn’t even be a part of iOS. Ideally, the end user should never have to worry about power management, should never have to choose between features, and should never get a subpar experience for the sake of longer battery life. If there are behind-the-scenes adjustments that can be made to improve battery, they should be baked into the OS. Otherwise, poor battery life is the fault of poor design choices.
And that is why it's made simpler where it's on or off, and not something where different aspects of it can/should be chosen to different degrees. As for battery life, it's not about making poor battery life better, it's about getting more out of battery life when it might be needed/desired at the cost of some more power hungry and at the same time generally less critical/important features (and for those that find those features more critical/important then the trade-off is that Low Power Mode isn't something they would use, just like they didn't have the option to do so for years and years until just recently in iOS 9).
 
It should. Are you also using OS X 10.11.4 on your Mac? (if you have a Mac computer)
no I'm not running the beta on the Mac, I did once an is not an experience to repeat. Yes I think is due to the fact that the iOS devices are sync with itunes but not with iBooks for mac or something like that. I have tried to open a epub file from the storage on the cloud and it sync with ibooks in icloud so let's see on the final release.
 
Low Power Mode is something that belongs on Android phones: it shouldn’t even be a part of iOS. Ideally, the end user should never have to worry about power management, should never have to choose between features, and should never get a subpar experience for the sake of longer battery life. If there are behind-the-scenes adjustments that can be made to improve battery, they should be baked into the OS. Otherwise, poor battery life is the fault of poor design choices.

What? Poor battery = poor design choices? The idea of low-power mode is to increase the battery life of just basic tasks. All it is doing is underclocking the CPU and GPU and quickly turning off notifications, all in one step.
 
My point is that the user should never have to worry about what options consume power. If they want to use Night Shift and Low Power Mode at the same time, they should be able to. Users shouldn't be forced to choose between features and battery life.
Ehm plece explain that, if nightshift uses significant amount if power, and your battery is roning low, youhave to choices iirc
1: live with lusing som features (that consume signifficant amounts of power) and get x minutes of extra usage
2: continue to use powehungry features and sacrifice battery life
But apple should be able to ad a swith thar says "ignore battery save and continue nightshift" that pops op a warning saying spmrhing like "this will reduse the efectiveness of low power mode, do you realy want to activate it?"
This way we have a choice and apple gards ther suport from complaints about low power mode not working. If that is not a win win what is?
 
Ehm plece explain that, if nightshift uses significant amount if power, and your battery is roning low, youhave to choices iirc
1: live with lusing som features (that consume signifficant amounts of power) and get x minutes of extra usage
2: continue to use powehungry features and sacrifice battery life
But apple should be able to ad a swith thar says "ignore battery save and continue nightshift" that pops op a warning saying spmrhing like "this will reduse the efectiveness of low power mode, do you realy want to activate it?"
This way we have a choice and apple gards ther suport from complaints about low power mode not working. If that is not a win win what is?
Unfortunately it won't guard them from complaints as people will ignore the warning or not care about it and then complain that Low Power Mode really didn't do anything for them and that it's basically a useless feature.
 
  • Like
Reactions: QuarterSwede
And that is why it's made simpler where it's on or off, and not something where different aspects of it can/should be chosen to different degrees. As for battery life, it's not about making poor battery life better, it's about getting more out of battery life when it might be needed/desired at the cost of some more power hungry and at the same time generally less critical/important features (and for those that find those features more critical/important then the trade-off is that Low Power Mode isn't something they would use, just like they didn't have the option to do so for years and years until just recently in iOS 9).
Then Low Power Mode might as well lock the brightness to it lowest setting and keep the phone in Airplane Mode. The current implantation creates needless complexity:
  1. User is in Low Power Mode and wants to enable Night Shift.
  2. User goes to Control Center and sees greyed-out option.
  3. User exits Control Center and current app to open Settings.
  4. User finds Night Shift and sees it cannot be turned on in Low Power Mode.
  5. User finds the setting for and turns off Low Power Mode.
  6. User can finally enable Night Shift.
  7. User returns to app.
 
Then Low Power Mode might as well lock the brightness to it lowest setting and keep the phone in Airplane Mode. The current implantation creates needless complexity:
  1. User is in Low Power Mode and wants to enable Night Shift.
  2. User goes to Control Center and sees greyed-out option.
  3. User exits Control Center and current app to open Settings.
  4. User finds Night Shift and sees it cannot be turned on in Low Power Mode.
  5. User finds the setting for and turns off Low Power Mode.
  6. User can finally enable Night Shift.
  7. User returns to app.
Pretty much the same thing has existed from the beginning of Night Shift when it comes to using Push for email or having the screen lock in more than 30 seconds. Again, nothing really new or inconsistent with Low Power Mode.

Seems like we've moved on from talking about being able to use one thing along with another to nitpicking some other aspects of it to just not even caring for Low Power Mode at all. Kind of neither here nor there really.
 
Ehm plece explain that, if nightshift uses significant amount if power, and your battery is roning low, youhave to choices iirc
1: live with lusing som features (that consume signifficant amounts of power) and get x minutes of extra usage
2: continue to use powehungry features and sacrifice battery life
But apple should be able to ad a swith thar says "ignore battery save and continue nightshift" that pops op a warning saying spmrhing like "this will reduse the efectiveness of low power mode, do you realy want to activate it?"
This way we have a choice and apple gards ther suport from complaints about low power mode not working. If that is not a win win what is?
That would be a better solution, yes.
[doublepost=1457390891][/doublepost]
What? Poor battery = poor design choices? The idea of low-power mode is to increase the battery life of just basic tasks. All it is doing is underclocking the CPU and GPU and quickly turning off notifications, all in one step.
If the phone had a larger battery, Low Power Mode would be used less frequently or might not have even been implemented.
 
That would be a better solution, yes.
[doublepost=1457390891][/doublepost]
If the phone had a larger battery, Low Power Mode would be used less frequently or might not have even been implemented.
It's not that much about battery size, since even with a large battery someone could still be in a situation where they are low on battery and would like to get more out of it for more important functions (or even when they aren't low and would like to get even more out of it than they normally would, even if normally they would still get a lot).
 
  • Like
Reactions: Mlrollin91
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.