iPhone Do you kill apps from multi-tasking on iPhone?

[jabingla2810]

No, it doesn't. Nowhere does it say that apps have to be in the recently used list. In fact, there is no "in the recently used list" app state.



That may be how you perceive your experience. Doesn't change the fact that Background Refresh does not require an app to be in the recently used list or even suspended in memory.



Just guessing, but maybe because you don't regularly open it on your iPad. One of the things that intelligent scheduling takes into account is how when and how often you open the app. Or maybe Betaworks implemented it poorly.



Personal anecdote doesn't qualify as facts.



So, developer documentation isn't enough?

This has got to be my last response, because life is too short.

Suspended state: app is frozen in the background, AKA, visible in list of recently used apps.

Background state: app is doing something in the background, maybe finishing a task like uploading some photos.

That statement says, if an app that is in the suspended state, gets a request to update its data, it can become a background app, and perform its update.

Gmail doesn't refresh it's data if it's not in the recently used apps list, regardless of push notifications.

The test I did.

Close gmail, but leave suspended. Send email to myself, wait for push notifications. Turn on airplane mode. Open gmail, and the new message is there waiting for me.

Doing the same test, without Gmail in the recently used apps list, and the message isn't waiting for me when I open the app. I even left it 5 minutes after the notification before turning airplane mode on.

Maybe the documentation is right, but maybe the developers of all the apps I'm using, including Apple, haven't figured it out yet.

 

[cynics]

I've experienced both of the above scenarios apply. Some apps seem to act as if background refresh was OFF if the app is closed out of the recent app/multitasking.

However that's not always the case. FmF for example I could not get to work without background refresh turned ON. And it works fine even if I never open the app now.

This conversation has peaked my interest now. I'll have to play with it when I get home.

If nothing else I feel even Apples explanation of background refresh could be spelled out a little better.

 

[BaldiMac]

Suspended state: app is frozen in the background, AKA, visible in list of recently used apps.

There is your first mistake. An app can be closed and still in list of recently used apps.

Background state: app is doing something in the background, maybe finishing a task like uploading some photos.

Yep.

That statement says, if an app that is in the suspended state, gets a request to update its data, it can become a background app, and perform its update.

It also says that it can launched to the background state. I highlighted it in bold! Did you miss the "or"?

See the additional documentation that I added to my last post.

Gmail doesn't refresh it's data if it's not in the recently used apps list, regardless of push notifications.

The test I did.

It does with the latest update to the Gmail app on iOS 7.

Close gmail, but leave suspended. Send email to myself, wait for push notifications. Turn on airplane mode. Open gmail, and the new message is there waiting for me.

Doing the same test, without Gmail in the recently used apps list, and the message isn't waiting for me when I open the app. I even left it 5 minutes after the notification before turning airplane mode on.

Maybe the documentation is right, but maybe the developers of all the apps I'm using, including Apple, haven't figured it out yet.

Works for me on the Gmail app in both circumstances. Also worked for Max(IT) who shares your overall position.

 

[dejo]

That statement says, if an app that is in the suspended state, gets a request to update its data, it can become a background app, and perform its update.

Which statement says this?

 

[BaldiMac]

I just finished testing with Tweetbot. Removed it from the multitasking view around lunch time (3 hours ago). Just put on airplane mode and then opened the app. New tweets had been downloaded.

I normally check Tweetbot every couple hours. Especially right after I get back from lunch.

 

[jabingla2810]

There is your first mistake. An app can be closed and still in list of recently used apps.

*sigh*

I never said anything that disagrees with this, no idea why you are bringing this up.

I'm out, this is exhausting.

Maybe everyone is having different experiences and non of this means anything.

 

[BaldiMac]

I never said anything that disagrees with this, no idea why you are bringing this up.

Sure you did.

Suspended state: app is frozen in the background, AKA, visible in list of recently used apps.

AKA means "also known as" as far as I know. Which would suggest that you think that both descriptions are of the same thing.

 

[jabingla2810]

Sure you did.



AKA means "also known as" as far as I know. Which would suggest that you think that both descriptions are of the same thing.

No, I meant, for an app to be frozen in the background it must be in your recently used apps list.

You twisted it to, if it's in your recently used apps list, it's frozen in the background.

There is a difference.

Ok, maybe you didn't twist it, and just misread it. But still, I didn't say what you thought I said.

This is silly now, arguing over semantics. All I will say, is non of my apps refresh their content if they aren't in the recently used apps list.

It appears that yours do.

Unless we arrange to meet up and have a look, this isn't going to end, and I don't fancy doing that to be honest. (No offence intended! )

 

[DramaLLama]

I'm confused at the people that say "No, it's pointless to close background apps. I only close them if I'm experiencing a problem".


...so now it's not pointless is it?

Also I'm not really knowledgable about 'freeing up memory' when another app needs it but by some explanations here you guys (some of you) are saying that iOS will take the memory if it needs it for something else.. well if something is using memory in the background waiting to be 'free' when needed, wouldn't that just be using more battery, if even a slight amount?

 

[BaldiMac]

I'm confused at the people that say "No, it's pointless to close background apps. I only close them if I'm experiencing a problem".


...so now it's not pointless is it?

You are oversimplifying. It not pointless to close background apps to resolve specific issues. It's pointless to close background apps as a matter of routine, and even more pointless to regularly empty the multitasking view because most of the apps in the list are not running anyway.

Also I'm not really knowledgable about 'freeing up memory' when another app needs it but by some explanations here you guys (some of you) are saying that iOS will take the memory if it needs it for something else.. well if something is using memory in the background wouldn't that just be using more battery, if even a slight amount?

Nope. RAM doesn't use additional power just because there is an app suspended in memory. On the contrary, regularly closing apps takes additional time and processing power and means that apps will be loaded from the SSD more often. All of which actually does have an impact on battery life.

 

[DramaLLama]

You are oversimplifying. It not pointless to close background apps to resolve specific issues. It's pointless to close background apps as a matter of routine, and even more pointless to regularly empty the multitasking view because most of the apps in the list are not running anyway.

What determines what's running in the background versus what's viewable in the multitasking view? I'm guessing whatever you have 'background app refresh' enabled for? I thought this would still refresh whether in the multitasking view or not.

Nope. RAM doesn't use additional power just because there is an app suspended in memory. On the contrary, regularly closing apps takes additional time and processing power and means that apps will be loaded from the SSD more often. All of which actually does have an impact on battery life.

Hmm makes sense I guess.. my gf closes out her apps almost every single time she puts down her phone for longer than an hour and it's rubbing off on me, although I've never thought about if it was actually useful to do so.

edit: To add, how would you know if a specific app is causing issues (what what kind of issues are we talking about) when you've got all of them open/viewable in the multitasking view? For some reason I feel like games would be a big battery killer 'in the background'... do they work just like everything else?

 

[Shrink]

Just a suggestion...

Close the apps if you want.

Don't close the apps if you don't want.

At this point, the "why" of it doesn't matter.

 

[BaldiMac]

What determines what's running in the background versus what's viewable in the multitasking view? I'm guessing whatever you have 'background app refresh' enabled for? I thought this would still refresh whether in the multitasking view or not.

Short Version.

1) The multitasking view is just a list of all the apps you have used in the order in which you have opened them. Think of it as a recently used app list.
2) Music, VOIP, and Location tracking apps can run in the background if you ask them to. (e.g. Music apps can continue playing in the background as long as you keep the music playing.)
3) Other apps have a limited amount of time (5-10 minutes) to complete a task they are working on when you switch away. (e.g. Finish uploading a batch of photos.)
4) In all other situations, an app is suspended to RAM when you switch away. If another app needs the RAM, suspended apps are closed completely. (Usually only the last 3-5 apps that you used are suspended at any one time.)
5) Background Refresh is simply a way for app developers to launch apps into the background to download small updates (e.g. tweets, emails) on a schedule determined by the OS or in response to notifications or location triggers.

Hope that helps!

 

[Badrottie]

I find killing apps more fun so I did.

 

[Strax]

Just a suggestion...

Close the apps if you want.

Don't close the apps if you don't want.

At this point, the "why" of it doesn't matter.

Come on now, this is the internet. How dare you post such a reasonable stance? I say you should only close apps if you don't want to and only leave them open if you definitely want them closed.

Now argue with me until I'm forced to challenge you to physical combat on a neutrally located playground.

 

[Zxxv]

killing apps unless they are doing something they're not supposed to and freezing up or something seems such a stupid thing to have to do. Why would apple expect users to kill apps all the time? users set them, if they set them to refresh in the backgournd thats what the user should expect to happen ALL THE TIME , no matter what, even after killng an app it should reboot back to running in the back ground as that is what the user has set with background refresh. If a user has set back ground refresh to no then killing the app will kill the app. Opening the app again will run the app. Homebutton back to springboard will mean the app will stop but if it doesn't the os will allow it to run for ten minutes is it, then will kill it.

No backgournd refresh means just that. Stop doing what your doing

Back ground refresh means keep doing what your programmed to do.

seems simple

 

[Shrink]

Come on now, this is the internet. How dare you post such a reasonable stance? I say you should only close apps if you don't want to and only leave them open if you definitely want them closed.

Now argue with me until I'm forced to challenge you to physical combat on a neutrally located playground.

I am embarrassed...

Let's just skip the arguing, cut to the chase, and just head out to the school yard at 3:00 today!

You'll be able to identify me...I'll be the one hiding in a corner, whimpering and begging...

 

[Strax]

Sounds like a plan. I'll be the increasingly middle-aged woman who will be questioning the wisdom of this entire idea and beginning to doubt that we're even in the same time zone much less the same playground.

 

[Max(IT)]

No, I meant, for an app to be frozen in the background it must be in your recently used apps list.

You twisted it to, if it's in your recently used apps list, it's frozen in the background.

There is a difference.

Ok, maybe you didn't twist it, and just misread it. But still, I didn't say what you thought I said.

This is silly now, arguing over semantics. All I will say, is non of my apps refresh their content if they aren't in the recently used apps list.

It appears that yours do.

Unless we arrange to meet up and have a look, this isn't going to end, and I don't fancy doing that to be honest. (No offence intended! )

I'm sharing your experience, so I'm thinking you are right, and Apple "understanding iOS 7 multitasking" is saying that.

----------

Short Version.

1) The multitasking view is just a list of all the apps you have used in the order in which you have opened them. Think of it as a recently used app list.
2) Music, VOIP, and Location tracking apps can run in the background if you ask them to. (e.g. Music apps can continue playing in the background as long as you keep the music playing.)
3) Other apps have a limited amount of time (5-10 minutes) to complete a task they are working on when you switch away. (e.g. Finish uploading a batch of photos.)
4) In all other situations, an app is suspended to RAM when you switch away. If another app needs the RAM, suspended apps are closed completely. (Usually only the last 3-5 apps that you used are suspended at any one time.)
5) Background Refresh is simply a way for app developers to launch apps into the background to download small updates (e.g. tweets, emails) on a schedule determined by the OS or in response to notifications or location triggers.

Hope that helps!

Multitasking view is .... Multitasking view, not just a recently used apps view, otherwise they had called it , well, recently used apps view

 

[dejo]

...otherwise they had called it , well, recently used apps view

But that is what they call it!

http://support.apple.com/kb/ht4211

 

[Septembersrain]

I think 7.1 helped with the whole bad memory management issues. The device I installed it on no longer has weird app crashes anymore.

 

[Max(IT)]

But that is what they call it!

http://support.apple.com/kb/ht4211

In the same page they call it differently:

dragging it up from the multitasking display, it won't be able to do its background activities, such as tracking location or responding to VoIP calls, until you relaunch the app.

 

[RichardC300]

I find killing apps more fun so I did.

Bruh. Me, too. I find killing 3 apps at once really entertaining.

 

[Max(IT)]

Bruh. Me, too. I find killing 3 apps at once really entertaining.

I'd like to kill'em all !

 

[Bear]

Some apps I don't bother killing, but some apps never re-initialize correctly unless you kill them. So I kill the apps with re-initialization issues. I also usually kill apps I use infrequently.