Apple Executive Confirms: Manually Quitting Apps Doesn't Improve Battery Life (bgr.com)

An anonymous reader writes: Apple software engineering VP Craig Federighi recently dispelled one of the more long-standing myths about iPhone battery life. In short, if you spend a few minutes every day double clicking the iPhone home button and manually closing up applications in an effort to maintain battery life, you're wasting your time. The reality is that the applications you see upon opening up the multitasking pane are actually nothing more than static images intended to represent a list of your most recently used applications. Apple support documents have indicated, "generally, there's no need to force an app to close unless it's unresponsive." Apple support docs further explain: "After you switch to a different app, some apps run for a short period of time before they're set to a suspended state. Apps that are in a suspended state aren't actively in use, open, or taking up system resources."

Comments

Waze

[Chmarr]

Except Waze... Waze is a battery hog. I always quit that as soon as I'm done with its navigation features.

Re:Waze

[MightyMartian]

And Facebook, an app that just eats cycles and battery life on both iOS and Android. That such a major player as Facebook writes such a shitty awful resource hogging app frankly shocks me... until I remember iTunes on Windows.

Re:Waze

[EvilSS]

And Facebook, an app that just eats cycles and battery life on both iOS and Android. That such a major player as Facebook writes such a shitty awful resource hogging app frankly shocks me... until I remember iTunes on Windows.

Facebook was actually caught cheating once by playing inaudible audio to prevent iOS from putting it into sleep.

Re:Waze

[tlhIngan]

Exactly, and there's other apps too. I don't recall if it was in another slashdot discussion or somewhere else, but this topic came up recently and someone pointed to some sort of documentation or other official info on the matter. The gist of it was that apps only have a limited (short) amount of time to run in the background, and then they are forced to shut down. It then went on to say that certain apps that have permissions for certain things can continue to run.

So in summary, apps are not allowed to continue running in the background....unless they are allowed to do so. Which makes the entire argument of "you don't have to manually close them" complete bullshit. Maybe you don't need to for MOST apps, but there are still plenty that do have the permission to continue running.

Apps get around 5 minutes to finish off what they're doing. That's it.

The exceptions would be apps that need to be running in the background - e.g., audio players, navigation apps and VoIP apps.

Audio players are obvious - it would be quite annoying if you put your Spotify or Pandora or the music player or other thing in the background only to have the music stop. Navigation apps are similar - you need to be alerted when you get close. (Waze and other apps also have to keep the GPS active, so it's a double hit on the battery). And VoIP/IM apps need to be active to keep you signed in.

Those are the general classes of apps that can keep background processing. Some apps, like Facebook cheat - they open an audio stream and then play silence, keeping them alive because iOS thinks its a media player app.

Navigation apps can't cheat as they reveal GPS usage.

Re:Waze

[Anonymous Coward]

This article is not talking about iOS. Oddly enough, iOS and Android are different OSes, and work in different ways.

Re:Waze

[93 Escort Wagon]

Facebook was actually caught cheating once by playing inaudible audio to prevent iOS from putting it into sleep.

"Once" was just a few months ago. Their patch to fix this issue went out on October 22, 2015.

Re:Waze

[BarbaraHudson]

On Androd:

• System
• Data usage
• Turn off cellular data
• Scroll down to the evil app (facebook)
• Touch the app's icon
• Turn off background data

Now the app won't be running except when it's in the foreground. You won't chew through your cellular data plan, and you won't get an alert when somebody in Oz posts while you're asleep.

Cell data will still work for the app when it's in the foreground, so problem solved.

Re:FALSE

[Dunbal]

The days of shortages of RAM are long gone. Unfortunately because it makes modern coders sloppy. But RAM is the least of your worries unless you're doing something crazy or have a huge memory leak problem.

Re:I don't think this is 100% true

[radish]

Apps which are put to the background are allowed to run for a little while to let them finish up what they were doing (e.g. saving something). Then they're suspended - their state is written to disk and they're flushed from memory. The screenshot is saved so you can see it in the list, and if you reopen it the app will be restarted from the saved state.

Apps can register themselves as requiring to run full time in the background, examples are navigators, messaging apps, etc. These will not be suspended, and can eat the battery. If you add one of those flags to your app without actually having justification to do so, you'll be rejected from the app store.

Re:GPS is next

[dbIII]

Wifi on the other hand. I get more than three days run time on my slightly aged phone with wifi off and less than a day with it on.

Re:Heh.

[AmiMoJo]

Actually the reason the original iPhone didn't multitask was that it was so underpowered. 400MHz single core CPU and just 128MB of RAM. Remember that at first it didn't even have third party apps, and when they did come along they were very limited in what they were allowed to do in order to preserve the user experience in such a low power, low memory environment.

At the time Android allowed multitasking but needed more powerful hardware and even then performance was quite poor. It certainly wasn't as slick as the iPhone, because it couldn't rely on being able to concentrate on just one task at a time.