Apps perhaps not REALLY closing when closed.. examples

[Vertigo50]

The OS has changed. It's apples and oranges. Just because the Mail App ran in the background in OS 3.0 doesn't mean it works the same exact way in 4.0 with Multitasking enabled.

Just saying - a does not equal b necessarily.

Okay. Apparently, no matter what anyone says in this thread, your mind is made up and you're not going to be happy until you "prove" the point you started.

So, you're right. None of the apps every close, they continually use up memory and battery power, and you should always be really anal about closing each and every app immediately the moment you are done with them.

Happy?

I'm done.

 

[samcraig]

Okay. Apparently, no matter what anyone says in this thread, your mind is made up and you're not going to be happy until you "prove" the point you started.

So, you're right. None of the apps every close, they continually use up memory and battery power, and you should always be really anal about closing each and every app immediately the moment you are done with them.

Happy?

I'm done.

Wow. Relax. I was responding to your post. Defensive much? I personally don't care either way - again was just relaying my experience. And I don't believe they all run taking up memory and never "leave." Did you even READ the progression of the thread.

Clearly or at least the most logical reason proposed is that some programs are a little wonky in their programming AND that the OS does a save state - so if the program boots wonky - then the only way to get it to actually RERUN - is to a) restart the phone b) remove it from the task bar so it loads fresh vs from saved state.

Go take your smug somewhere else...

 

[dagomike]

I'm sincerely not trying to be rude - did you read my original post? Maybe it wasn't clear.. in either event - when I close the App (hitting the home button) and restart it - it's still hangs.

Only when I either restart my phone and/or clear it from the task bar will it reload / run correctly.

Clearing it from the task bar is quitting it. That's how you quit an app.

Before you just hit the home button, now it sits in the back ground. Before if it misbehaved you quit it by hitting the home button. Now you do it by clearing it from the task bar.

 

[Coukos34]

Wow. Relax. I was responding to your post. Defensive much? I personally don't care either way - again was just relaying my experience. And I don't believe they all run taking up memory and never "leave." Did you even READ the progression of the thread.

Clearly or at least the most logical reason proposed is that some programs are a little wonky in their programming AND that the OS does a save state - so if the program boots wonky - then the only way to get it to actually RERUN - is to a) restart the phone b) remove it from the task bar so it loads fresh vs from saved state.

Go take your smug somewhere else...

I'd agree that the quick switch bar can be used as a task manager. That's how I reset a program like safari, mail, etc that isn't running right. I'm starting to think with all the save state functionality being added in, we may see more apps having issues. Used to be that an app like Facebook would load each time opened, kind of like a computer boots each time. Now the ability save state (or hibernate/sleep) has more probability of having an issue, no?

 

[kas23]

I'd agree that the quick switch bar can be used as a task manager. That's how I reset a program like safari, mail, etc that isn't running right. I'm starting to think with all the save state functionality being added in, we may see more apps having issues. Used to be that an app like Facebook would load each time opened, kind of like a computer boots each time. Now the ability save state (or hibernate/sleep) has more probability of having an issue, no?

I do the same too. There are times when Beejive or Mail are not connecting correctly. It's not as simple as just closing the app now. You have to go into the multitasking bar and force quit them and then restart them.

 

[marksman]

No

 

[admanimal]

There's no "perhaps" about it. Apps that have been recompiled for iOS 4 and haven't specifically excluded themselves from multitasking support will be asleep but in RAM when you switch away from them, until the system needs their memory back in which case they will be terminated.

This can make things more complicated for everyone. App developers have to make sure that their apps don't assume they will be started/terminated every time they are run, and if something should go wrong in an app (that doesn't cause it to crash), users have to make the effort to really terminate it. I would be willing to bet that 99% of app issues related to multitasking are due to bugs in the app rather than the OS.

Apps that have not been recompiled to support iOS 4 will completely close and restart every time you use them, although they will still appear in the task switcher.