Honestly this post just shows that you don't know what you are talking about. It isn't using system resources because it isn't taxing any part of the system. RAM takes the same amount of power to store a static bit of data as it does to store "no" data (hint there is no such thing). Free ram is a 100% pointless thing to have. Striving to have more free ram is striving to waste more money.
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.
iOS 7 'Close All' Multitasking!
- Thread starter rsnapeuk
- Start date
- Sort by reaction score
Honestly this post just shows that you don't know what you are talking about. It isn't using system resources because it isn't taxing any part of the system. RAM takes the same amount of power to store a static bit of data as it does to store "no" data (hint there is no such thing). Free ram is a 100% pointless thing to have. Striving to have more free ram is striving to waste more money.
if they really wanted to implement it, I would say the best way is with a swipe down. right now you swipe up on 1,2, or 3 apps to close them, how about if you start swiping down even one of them all of them pull down evenly together and if you follow through with the swipe it closes all "open" apps.
Id love to see this feature. Facebook kills my battery in the background. Im sure other apps are doing the same. A "kill all" feature would be nice. Droid has it, and im sure its for good reason. Apple should add it aswell.
Facebook doesn't use any CPU in the background on iOS, it has no effect on battery life when it's in the background.
Yes, it's because Droid's multitasking is inferior to the iOS way. And yes, I do mean inferior. You can argue all you like and say it's just a different way of doing things, but if there was one aspect of iOS that Apple got bang on, it's how they designed multitasking.
Facebook won't drain any battery when you suspend it.
I used to manually close each app after using it and decided to try doing it the Apple way several months ago. Not only the performance and battery life stayed the same, but now using the phone feels so much easier without having to tap on those little red crosses all the time.
On a side note I tried the same with my Galaxy S3 and I have to say that things are looking worse. After only a day with using the phone and not closing anything it starts to become unresponsive at times, and the battery consumption hits the roof.
So yes you NEED task manager, but only on Android, bexause of the Windows like way of managing resources.
On a side note I tried the same with my Galaxy S3 and I have to say that things are looking worse. After only a day with using the phone and not closing anything it starts to become unresponsive at times, and the battery consumption hits the roof.
So yes you NEED task manager, but only on Android, bexause of the Windows like way of managing resources.
RAM is a system resource and it's consumed by suspended apps. If not, why dump them in a low memory condition (which frees up memory)?
What's your point? Why do you care if RAM is full? Obviously, WordMasterRice was referring to processor and battery resources that actually impact the user.
To assign it to the foreground app if it needs it.
Actually, it does. Its voip needs to "call home" or something and it does so every 10 seconds I believe.
http://www.digitalspy.co.uk/tech/news/a487575/facebook-blamed-for-iphone-battery-drain.html
After i deleted Facebook in favor of the web version, my battery improved a lot.
Last edited:
It was a programming bug specific to that particular app that can only happen for apps that use the voip APIs. If it was not fixed already it should be eventually.
And that's what I was saying, there's no need to quit apps on iOS unless a specific app misbehaves (which seems to be the case with FaceBook).
I didn't/don't experience any battery draining because of FaceBook. But it seems that you did, and the best solution for you was to uninstall the app. A "Close All" button wouldn't have helped you in that case.
i would like it just so im not scrolling 25+ apps....
and yes, after killing apps, i notice my phone getting faster (and slowing down if too many open). im not going to open that big can of worms, but i can notice it so....
and yes, after killing apps, i notice my phone getting faster (and slowing down if too many open). im not going to open that big can of worms, but i can notice it so....
The point is the topic and discussions in this thread. According to Apple, "Making room in memory for a programs code and data requires time and resources and therefore affect the overall performance of the system."
and
here "Because the iOS virtual memory model does not include disk swap space, apps are more limited in the amount of memory they have available for use. Using large amounts of memory can seriously degrade system performance and potentially cause the system to terminate your app."
and
"There is a direct correlation between the amount of free memory available and the relative performance of your app. Less free memory means that the system is more likely to have trouble fulfilling future memory requests."
Yes, he was cherry picking resources to make his point.
I'd rather have iOS open the app then start Low Memory notifications and cleanup.
I'm not trying to convince anyone to change their behavior. I close all my apps at the end of the day instead of letting iOS manage it for me. It's OK if someone else doesn't and has no issues.
Its arrogant to believe that Facebook is the only app with problems among the hundred of thousands apps in the store. And you cant expect users to find out which apps are causing battery drain themselves. So while you take Apples multitasking bragging at face value, Id like a sollution that would be more user friendly than troubleshooting all your apps whenever some developer introduce a new bug. A kill switch could be such a sollution.
Yes it would have. Closing Facebook did the same job as deleting the app, once I realized it was at fault. I just deleted it because i kept forgetting to kill it. For months I lived with a phone that would last no more than 8-9 hrs. without knowing what to blame. At that time, a kill switch would have helped a lot.
Now my phone lasts all day.
Last edited:
Which refers to actually loading a program into memory regardless of the amount of free memory. So, the point here is that you are actually degrading performance by removing an app from memory proactively. Not to mention the time wasted in manually closing the apps.
"If that happens, the system can always remove suspended apps, code pages, or other nonvolatile resources from memory."
This section is about minimizing your apps memory footprint, so that it doesn't conflict with other running apps.
No, he was commenting on the resources that had a significant impact on the user.
At any time, there are usually only 2-4 suspended apps in memory. Closing them once per day has no impact on performance. I'm not trying to convince anyone to change their behavior, I'm just trying to prevent the spread of a myth.
I just used Instruments on my phone and watched memory and processor while FB, Bad Piggies and Tweetbot ran on my iPhone 5 with iOS7.
I was able to have them ALL load and stay in memory. However, when I left FB, it's Processor % went to zero after approx 10 seconds.
I then cleared all apps and ran it again.
So to say that FB has anything to do with battery problems is hard to believe when I have empirical evidence suggesting otherwise.
Here is screenshots of Instruments sorted by CPU activity (which is the one that uses battery)
While it's running and active on my phone and scrolling to make it use more CPU:
When I pressed home and waited 10 seconds:
I was able to have them ALL load and stay in memory. However, when I left FB, it's Processor % went to zero after approx 10 seconds.
I then cleared all apps and ran it again.
So to say that FB has anything to do with battery problems is hard to believe when I have empirical evidence suggesting otherwise.
Here is screenshots of Instruments sorted by CPU activity (which is the one that uses battery)
While it's running and active on my phone and scrolling to make it use more CPU:
When I pressed home and waited 10 seconds:
And that "unless specified otherwise" is exactly the problem. There are a number of circumstances when apps are allowed to run in the background (see "Implementing Long-Running Background Tasks" in this article). If one of the approved apps uses up unnecessary resources, it's probably not good programming, but nonetheless possible and allowed according to Apple's guidelines. One example is the Navigon app, which definitely uses power while in the background even when not navigating a route (I don't know exactly what it does, but the phone sometimes even gets a little warm until I kill the app). As long as there are cases like this, you cannot claim that closing apps manually is completely unnecessary.
No, but it clearly shows a "close all" isn't needed. Navigation, music and VOIP apps are your most likely culprits of staying on but only when they are active. Pandora wont stay running if you arent playing music and it will go inactive.
It would be a lot more convenient than closing 2 dozen apps one by one trying to figure out the culprits.
It's easier than you think. How many apps do you have running that are either GPS, Music or VOIP all running at the same time?!?
There are two problems with your argument: (1) the average user does not know and cannot see which apps are allowed to consume resources while running in the background, and (2) there are more types than the three you mention.It's easier than you think. How many apps do you have running that are either GPS, Music or VOIP all running at the same time?!?
Those are the major ones. I've argued this topic ad naseaum and being a developer, have a pretty firm grasp on how it works, thanks.
I've even listed above my Instruments findings using iOS7 with Facebook (which is theorized has VOIP permissoins) and can do more if you'd like me to.
And it does that instantaneously? I'm aware that it does it automatically, but my phone runs a lot smoother with 300mb of ram free than with 3mb of ram free.