Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Wait, doesn't that last bit make the opposite of sense? Isn't the best way to troubleshoot which app is problematic to kill them one by one and wait between each one to see when the issue is eventually cleared? How does killing them all at once isolate the problematic one?
Im responding to someone else who goes by that old misconception that a simple phone must be devoid of ANY complicated apps. But I do get your point so I'll elaborate.

If talking about troubleshooting then an activity monitor would be the best tool for the job. But since some people here pretend the iPhone is ONLY for low end consumers that would have no need for an activity monitor then we have to assume that these end users also would be so inept or lazy to do ANY form app-by-app troubleshooting. And IF thats the case then a Kill-All button in the slide down menu would be easier than manually closing each app.

But IMO then iPhone users are a mix of low end AND high end usrs. So IF someone were to truly troubleshoot then a 1st party app killer/activity monitor would be extremely beneficial. Killing all apps and reopening apps one at a time to diagnose a problem makes just as much sense as opening 10 apps and closing one at a time.
 
There is a good reason.

It doesn't need one.

If an app is causing a problem for you, you can manually kill it. However 99% of the time you don't need to worry about it.

My mum has an iPhone and she has no idea how to kill apps, she must have hundreds of apps in her recently used list, and her battery lasts for days.

Yeah, I've been reading that attitude regularly. I don't believe it. As a new user, my IT people (who are all Mac and iPhone people) ALWAYS kill all apps when there is any problem on an iPhone being used on our system. They have all seen problems with some apps continuing to run and problems solved when they are killed. In my own experience, I've seen this at least three times in the last month. I would say 99% is a dramatic overreach, which of course depends on what kind of apps you are using. In one case, a "closed" app was continuing to use location services when it was supposed to be inactive. "It doesn't fit into their philosophy" is BS. Certainly the fact that the phone will not multitask should remove the issue of problems....but it doesn't. And that alone is a deficiency.
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

there is an app called system status that will clear up memory they kinda try to hide it tho


Is there a good reason



edit: inb4 a bunch people say the OS 'doesn't need it'

real smart os doesn't need an app for that, for other things there is an app for that!
 
And not an app? Software is more often a problem than OS or Hardware.

I suppose it depends on how you look at it. The OS shouldn't be letting an app do something it's not supposed to do. And then there is the idea that if an app is causing problems that cause a daily restart, you would think that the developer would fix it or the end user would replace it.
 
If you need to restart daily with iOS than something is wrong with your OS installation or your hardware.
i never said i needed to, i was suggested that for a way to close all apps. since one by one takes a bit long
 
I'm still confused as to why people have this wild and crazy thought that iOS runs like Windows.
Do they not realize that iOS is a completely different type of operating system and using the same thought process is, in itself, illogical?

Maybe these are the type of persons that believe Unix is the same as DOS.
 
And manually shutting down dozens of apps through a time consuming single file closing ritual is easier?

A task killer makes sense because with so many 3rd party apps then the best way to troubleshoot which app is problematic is to kill them all.

Easy solution if you want to kill hundreds of apps. Turn off your iPhone. And then turn it back on. It's not exactly rapid, but it's quicker than closing all the apps if you've got loads and loads open. It is also less taxing on your fingertips. ;)

----------

I'm still confused as to why people have this wild and crazy thought that iOS runs like Windows.
Do they not realize that iOS is a completely different type of operating system and using the same thought process is, in itself, illogical?

Maybe these are the type of persons that believe Unix is the same as DOS.

^^ xD
 
I'm still confused as to why people have this wild and crazy thought that iOS runs like Windows.
Do they not realize that iOS is a completely different type of operating system and using the same thought process is, in itself, illogical?

Maybe these are the type of persons that believe Unix is the same as DOS.

Because if Apple is going to approve apps that screw with your battery life and don't "shut down" when they're supposed to, then why should it be our responsibility to shut them down one by one if a simple app would allow that function? In my experience, most IT people who supervise the use of large numbers of iPhone users in an enterprise situation feel exactly the same way. Not having the ability to do that is illogical, but then again so is the lack of multitasking and the iOS notification "non-system".
 
Wait, what do you need a task killer for?
Last time I remember, they don't really do anything regarding improving performance.

If you need to close an app because it's acting up, double press your home button and kill it.
 
Wait, what do you need a task killer for?
Last time I remember, they don't really do anything regarding improving performance.


If you need to close an app because it's acting up, double press your home button and kill it.

They don't. Even most Android phones run better without task killers.
 
With the way iOS works, it really doesn't need it. When there isn't enough RAM to go around, older processes will save state and die off automatically. If you want to prevent even that from happening, open the multitasking bar and close things out yourself. I usually do this at least once a day, but then again I just don't like stuff in that bar that I'm not going to be using again soon.

If you really MUST have at task manager and an ability to "free up RAM", jailbreak. There's a task manager built into SBSettings, and I'm sure that if you look hard enough someone else has something similar in Cydia that might be slightly more full featured. I don't understand why people complain when there are perfectly good solutions out there. Either it's not a big enough deal to jailbreak and do something about it, or it is.
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 Safari/7534.48.3)

That edit in the OP is very appropriate.

To be fair, the 512mb devices require task killing/memory management much less than older devices. On my 3GS, iOS would slow down and lag considerably if I wasn't constantly closing out apps. I even went so far as to use the jailbroken tweak Backgrounder as my executioner by disabling app suspension for everything. The OS ran much smoother because of it.

Flash forward, and it turns out 512mb of RAM fits almost perfectly with what iOS needs to run flawlessly. Sometimes though this is not the case. On the 4 for example, I notice slight system lag when the user does not close out applications. On my 4S, the effect (if it occurs at all) is laughably negligible.

However, I am convinced that there are two definite perks to being on top of memory management in iOS. One is battery life, which seems to be a heated debate so I'll just chalk that up to an IMO. The other is consistent performance. I've noticed the 4S can launch an app generally about as quickly as it can fetch it from memory. I've had many scenarios where I've had to close out an app and vanilla launch it to fix a problem.

While app suspension arguably improves the experience, and its negative side-effects are also arguably small, there are reasons for the complaints.

Like someone else said, there are low and high end users in iOS. Some people want the option. The constant argument that "Apple knows best" is tiring in this thread.
 
Not everything you see in the multitasking bar is a running app. They are "running" as in using CPU time if they are currently using one of the 7 background APIs like audio.

They are in memory, ie, using some of that 512mb ram if they have been closed recently. Meaning that the last number of apps that could fit into the 300mb of free ram you had are there still in ram, they have no running processes but their resources are in ram so if you launch them again and "resume" them then they don't have to reload everything into memory. As new apps are launched that need memory, old ones are kicked out to give the new ones the memory they need.

The rest of the list, the other 20-100 or so apps you see there are essentially just that, a list. Its like the history in a web browser, these apps aren't open, running, or sitting in ram its simply a list in the order you've used them from most recent to least recent.

If you want to kill apps, you can either restart the phone which dumps all the apps from ram and starts fresh with 300mb free (a couple hundred is used by the OS by default) or you can just force close the last 2-10 on that list and then everything will be fully removed from memory.

The issue is that the multitasking bar shows apps in 3 different states but doesn't distinguish between which state they are in. Either Running (MT API using CPU), in Memory (taking up space in RAM), or just recently launched (think history.)

This is the best explanation I've found online, check it out. http://whenwillapple.com/blog/2010/04/19/iphone-os-4-multitasking-explained-again/

As far as performance issues I have noticed that starting a very memory intensive game such as Infinity Blade will lag as the OS starts clearing memory for it. I have noticed that some apps will lag while others are doing things like when mail starts checking mail while you're launching a game etc. I have noticed that some poorly coded 3rd party apps either have memory leaks or issues with how they use those 7 APIs or just all around get stuck requiring a force close.

As far as a task killer, one does exist, the whole hold down click the (-) to close apps thing in the MT bar but there is not task manager that is user accessible so to speak. The idea I think is that you can still use the phone as if it were iOS 1.0 if you wanted and ignore any new features or use all the new features. Basically, it's kept simple so someone who learned the very basic start app, home button, start other app function doesn't need to worry about what double clicking the home button does. They may notice some of their apps start faster after the first time they use them (resume) but other than that they don't have to learn anything new. I think that is the goal, that anyone can pick up any iphone running any os version and essentially use it the same basic way it used to work without the confusion of "why did pandora stop when i closed it" going on.
 
Why should you even care about how much RAM is being used?

It's like when I see people fret over how a program is using 500mb to run, so bloated... when they still have 90% free.

I really don't get why people are OCD over RAM usage, be it on an iPhone or a desktop PC... unused RAM is worthless, you get no speed boosts if you have 99% RAM free, than if you have 20% ram free
 
OP you should get an android phone LOL then you will be happy with the task manager that drains the battery life even more. :roll eyes:

*inserts sarcasm*
 
i think maybe some apps you think aren't running are taking up more battery/power than you think
 
Last edited:
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

jman240 said:
Not everything you see in the multitasking bar is a running app. They are "running" as in using CPU time if they are currently using one of the 7 background APIs like audio.

They are in memory, ie, using some of that 512mb ram if they have been closed recently. Meaning that the last number of apps that could fit into the 300mb of free ram you had are there still in ram, they have no running processes but their resources are in ram so if you launch them again and "resume" them then they don't have to reload everything into memory. As new apps are launched that need memory, old ones are kicked out to give the new ones the memory they need.

The rest of the list, the other 20-100 or so apps you see there are essentially just that, a list. Its like the history in a web browser, these apps aren't open, running, or sitting in ram its simply a list in the order you've used them from most recent to least recent.

If you want to kill apps, you can either restart the phone which dumps all the apps from ram and starts fresh with 300mb free (a couple hundred is used by the OS by default) or you can just force close the last 2-10 on that list and then everything will be fully removed from memory.

The issue is that the multitasking bar shows apps in 3 different states but doesn't distinguish between which state they are in. Either Running (MT API using CPU), in Memory (taking up space in RAM), or just recently launched (think history.)

This is the best explanation I've found online, check it out. http://whenwillapple.com/blog/2010/04/19/iphone-os-4-multitasking-explained-again/

As far as performance issues I have noticed that starting a very memory intensive game such as Infinity Blade will lag as the OS starts clearing memory for it. I have noticed that some apps will lag while others are doing things like when mail starts checking mail while you're launching a game etc. I have noticed that some poorly coded 3rd party apps either have memory leaks or issues with how they use those 7 APIs or just all around get stuck requiring a force close.

As far as a task killer, one does exist, the whole hold down click the (-) to close apps thing in the MT bar but there is not task manager that is user accessible so to speak. The idea I think is that you can still use the phone as if it were iOS 1.0 if you wanted and ignore any new features or use all the new features. Basically, it's kept simple so someone who learned the very basic start app, home button, start other app function doesn't need to worry about what double clicking the home button does. They may notice some of their apps start faster after the first time they use them (resume) but other than that they don't have to learn anything new. I think that is the goal, that anyone can pick up any iphone running any os version and essentially use it the same basic way it used to work without the confusion of "why did pandora stop when i closed it" going on.

Every app I reopen takes off where it left off. Doesn't that take some memory. Just because apple says something doesn't mean it's true. And it might not even be apples memory management....it could be something wron with a certain app.

Bunch of fan boys here. I'm not sure what is true and what isn't. Way too many fanboys and people who think that having less apps open makes no difference when there's no way to know for sure without doing some research and tests. You don't know every detail of every app. And you dont know just because apple says something that it's fully true, or how a feature works compared to how it is supposed to work
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.