4 ms·

iOS will actually disable these features if the battery is getting low. It will also group them together so that the wireless chips are on as briefly as possibl

• danieldk 13y ago
  iOS will actually disable these features if the battery is getting low. Like Battery Saver? http://www.windowsphone.com/en-us/how-to/wp8/basics/battery-making-it-last http://www.windowsphone.com/en-us/how-to/wp8/basics/battery-...
  • r00fus 13y ago
    Great - another option. I prefer my phone deciding when to do this automatically (and maybe an option to disable it so I can run it into the ground if absolutely necessary).
    • Someone 13y ago
      I prefer magic, too, if it works. I doubt it does in this case, though, and I get the impression Apple knows it hasn't nailed it yet, either. At least, elsewhere in this thread people note Apple's stuff can be overridden on a per-app basis. I also get the impression that Apple's idea about the perfect balance between flexibility and "it just works" neighs more towards the latter than Google's ideas about it, as witnessed by some remarks that Google's Sync adapters that app developers _can_ use are exactly the same as Apple's solution that app developers _must_ use.
      • jakebellacera 13y ago
        While I do agree that iOS isn't nearly as flexible as Android, let's just say that 90% of the time you might want to go with a Sync adapter versus rolling your own solution. Also, I believe that Apple has the best intentions at heart when it comes to implementing Background Fetching in it's current spec. I mean, lets face it, it's way better to have a mobile-optimized OS manage resources than for you to do so, don't you agree?
        • Someone 13y ago
          As I said, I prefer magic, too. More precise: The user in me agrees; the hacker disagrees. The hacker would like to see a 'make world' in each phone.