Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Still no "close all" function
- Thread starter bluewomble88
- Start date
- Sort by reaction score
Folks you can post all the pseudo-technical marketing links you want, but there are legitimate reasons to close apps that's been covered over and over. There are many threads that already argue this point to death.
Apple should update their knowledge base then.
http://support.apple.com/kb/ht4211
"If you force an app to quit by 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."
No, it doesn't. BAR uses intelligent scheduling or notification triggers to temporarily launch the app or revive it from suspended state into the background. It works the same whether the app is suspended or quit entirely.
https://developer.apple.com/library/ios/releasenotes/General/WhatsNewIniOS/Articles/iOS7.html
"Apps supporting either the fetch or remote-notification background modes may be launched or moved from the suspended to background state at appropriate times."
Emphasis mine.
----------
That statement applies to the background activities introduced in iOS 4. Not background refresh (BAR).
Last edited:
http://stackoverflow.com/questions/...tification-will-ios-launch-my-app-if-it-is-no
Is this accepted answer wrong then?
"Also keep in mind that if you kill your app from the app switcher (i.e. swiping up to kill the app) then the OS will never relaunch the app regardless of push notification or background fetch. In this case the user has to manually relaunch the app once and then from that point forward the background activities will be invoked. -pmarcos [apple employee]"
Last edited:
It helps if you don't oversimplify the argument to make your point. Yes, there are legitimate reasons to close apps if something goes wrong. That's why Apple provides that ability. However, there is no significant reason (other than OCD-like reasons
) to routinely remove all apps from the recently-used app list.
It helps if you don't oversimplify the argument to make your point. Yes, there are legitimate reasons to close apps if something goes wrong. That's why Apple provides that ability. However, there is no significant reason (other than OCD-like reasons
Give me back my thoughts damn you!. Yikes dude, I would have put it exactly in those words.
Try it yourself. I've tried it with both Tweetbot and the GMail app the last time this discussion came up. Swipe the app from the multitasking view. Wait for a BAR to trigger (Tricky for an app like Tweetbot, since intelligent scheduling adapts to how you use it). I use Tweetbot frequently, so I waited about three hours. Then engage airplane mode and open the app. See if the content has been refreshed. It did for me.
I've never seen any documentation for a "has been killed in the app switcher" state for an app.
Here are the states that I'm aware of:https://developer.apple.com/library...w.html#//apple_ref/doc/uid/TP40007072-CH4-SW1
Someone explain to me: if the background app kicked our from RAM, next time you open that app, it still need be reloading to the RAM... What is tie differences between this and closing down app the reloads?
Maybe somebody like me does not like all the app on the multitasking tray and wanting close down everything. What is the harm to provide such close all button? The popularity of such jailbreak app shows some people like it
That's in the list for iOS 9, along with incredibly innovative features like a sort of widget looking stuff that you can have, with strict limitations, on the home screen! Wouldn't that be a-mazing?
Thanks, I will try eventually - set up my iPhone as new with the iOS 8 beta and haven't got it to a state ready to test that
Did you do your testing with 7.0 or 7.1? A user above said he thought quitting stopped BAR in 7.0 but not in 7.1. I am finding multiple references to a consistent policy that quitting apps preventing BAR on the apple dev forums, but they all predate 7.1.
The harm is that it leads the technology ignorant (not an insulting term, it just means they don't know how these things work) to think that it is needed.
I can't tell you how many times I've seen people from best buy explain to customers that they should close programs to save battery and performance, I let the customer leave, then explain to them they they are spreading misinformation (unintentionally).
If you don't like the icons being there in the bar thats fine, but the option very quickly leads to mass misunderstandings, just take a look at how many of the supposed tech sites still further the idea that closing apps effects performance. It doesn't.
The whole point of iOS is that the user should be involved in as little maintenance and operation as the system as possible.
It takes less energy (battery power) to keep an app loaded into RAM than to load an app into RAM for the first time (after it's been closed).
Opening and closing apps all day will consume more battery than just leaving them open and letting the OS close the most idle apps to recover RAM if it needs it.
How much battery is wasted for the app being ideal for 10 min in the background? Like when I first load Facebook it has to load completely. But if I leave it and go back to it within a min it of coarse doesn't have to load like it did BUT if I leave it for 10 min and come back I have to load it up as if I just opened it.
I do hate the 10 min cut off. I always have to go back within 10 min to mc tube to make sure my downloads don't stop
I do hate the 10 min cut off. I always have to go back within 10 min to mc tube to make sure my downloads don't stop
It helps if you don't oversimplify the argument to make your point. Yes, there are legitimate reasons to close apps if something goes wrong. That's why Apple provides that ability. However, there is no significant reason (other than OCD-like reasons
Yeah, I decided to not get sucked back into the same arguments.
The other threads have (public) developer documentation pasted in them that discuss low memory conditions and how the OS and apps are required to react to that. I've simply chosen to try and avoid low memory conditions so the iOS and apps don't have to do that dance. I've had to restart my phone too many times to simply launch X-Plane and other memory intense applications to believe that iOS memory management works as well as it does on paper. A quick Google has smart people on both sides of the argument so I don't stand a chance.I've also previously posted how my kid's iPod with over 50 apps in the recently used apps list can take seconds to simply open settings until I remove them all. Yes, anecdotal evidence.
Never had to close all apps.... Don't even realize they are even back there. It does 0 to performance what do ever.
Most of background app will in freeze state and removed from RAM...since iOS does not have page, if the system decides to kick background out of RAM, then what is point to keep it in the system tray? If I were to resume the app, it need reoload to RAM anyway.. Isn't it same as you reloading the app?
If there is 20+ apps in the background, I highly doubt all these apps will still preserved in the RAM... Probably most of them were cleared from RAM long time ago. So I still do not see the how close these app harm battery life.
The iOS task switcher is a hybrid list of open apps, apps in freeze state (no cpu but reserving RAM) and shortcuts (apps opened recently). If you restart your phone you will only see the recent apps list in task switcher.
This topic has been beat to death. Stop trolling.
Last edited:
As an experiment, after making my posts above I stopped closing all my apps at the end of each day. This morning I experienced the third "lock" of my phone where it was unresponsive and sending calls to voicemail until I reset it. I'm going to start closing all my apps again.
My mom doesn't know how to close apps and her iphone 3GS has been up and running for like 10 months now and she's never once told me it's slow or gets stuck.
Check your diagnostics logs for any kind of errors. An app might be your problem.
Agreed that it's an app and one of the reasons I want a close all feature. Nuking from space is easier than killing them one by one.
Agreed that it's an app and one of the reasons I want a close all feature. Nuking from space is easier than killing them one by one.
Well, now that iOS 8 shows you what app is using your battery the most maybe we'll see more diagnostic tools in the future.
I used to close all my apps but stopped doing it because it's a waste of my time. Doesn't effect me in any way if the apps are open in the backround.
Agreed that it's an app and one of the reasons I want a close all feature. Nuking from space is easier than killing them one by one.
Then just kill the one app that is giving you issues, remove it, contact the developer, etc.