Well, you don't really need step one there, you can access the multitask tray anywhere with double tap.
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.
Closing Apps in iOS4
- Thread starter gazzrenn
- Start date
- Sort by reaction score
Well, you don't really need step one there, you can access the multitask tray anywhere with double tap.
You do, because double tap to get the tray will *not* show the current app.
Also, I do close some. Maybe it's because some apps aren't updated, but you can watch memory being released the more apps you close. Additionally, after awhile the little tray gets way too full
You do, because double tap to get the tray will *not* show the current app.
Also, I do close some. Maybe it's because some apps aren't updated, but you can watch memory being released the more apps you close. Additionally, after awhile the little tray gets way too full
As noted earlier, suspended Apps are borrowing free memory. The idea here is that "free memory is wasted memory" and so it is good to use it for something until it is needed. Closing manually works (as you have seen) but the OS will do that automatically when needed...
I do agree that the tray gets quite full, and future software updates could remove icons from the tray if they have not been used in some period of time (a number of days most likely)
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_0 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Mobile/8A293)
The only case that really bothers me is my nav app, TomTom. In order to stop voice directions is to double tap, hold the icon then kill it. Or am I missing something?
The only case that really bothers me is my nav app, TomTom. In order to stop voice directions is to double tap, hold the icon then kill it. Or am I missing something?
A few posters have commented that TomTom stays in 'navigation mode' even after you reach your destination, that is, it continues to try to direct you there. This is arguably a flaw in the App
I find this whole "leave it alone, don't worry about background apps" thing, fairly insulting to users intelligence
However, it would also seem that VoIP apps should have a kill button, so as not to have to go through the 3 step process to kill. And, it seems to me, as VoIP apps are really secondary forms of communication on the phone, and not necessary all the time, a good percentage of people would want the option to close them after using.
Im not sure if Apple offers developers an API call to give ability to build an "X" out button, but, it would be nice.
However, it would also seem that VoIP apps should have a kill button, so as not to have to go through the 3 step process to kill. And, it seems to me, as VoIP apps are really secondary forms of communication on the phone, and not necessary all the time, a good percentage of people would want the option to close them after using.
Im not sure if Apple offers developers an API call to give ability to build an "X" out button, but, it would be nice.
I agree. This whole free memory is wasted memory is BS. Yes, I wanted backgrounding apps, but that doesn't mean I want everything running in background. I'm jailbroken, and with SBsettings my free memory is displayed in the status bar at all times. I use my iphone 4 all day, not closing out any apps and several times during the day it will hover below 50mb free and the phone runs slow. If it dips below 30mb the phone runs like my old 3G did--terrible. Thankfully i have "Remove BG" installed and with one touch it clears all of them out but really i would just rather have menu that lets me choose which apps to background.
I wouldn't say that the phone runs slow (continuously), but it will stutter when memory is low. That happens because an operation will require additional memory and will have to pause momentarily while the OS dumps another app from memory. This is what makes folder open in such a jerky fashion. It doesn't make the phone constantly run slow, however.
I thought so too, but why do you need a multitasking toolbar at all ? It fills up after a few days with all apps you just ran once with their saved state.
In that case why going to the taskbar when I can just run the app from the springboard, instead of scrolling thru ?
I can see my taskbar having 100 apps after 1 or 2 weeks
I use the fast app launcher constantly. I am switching between a handful of apps, and it is easy to toggle through them with the fast app switcher. Much quicker than bringing them up from the springboard, especially if they are in a folder.
Plus it gives me flexibility... all the apps I use are not always the same. This means no matter what combination of apps I might be using at one time, I will always be able to quickly toggle between them. With the springboard, I would have to re-arrange my apps every time I had a different set of app needs to achieve the same effectiveness.
I would think this has more to do with something you are doing with your jailbroken apps than with the actual phone performance itself. The way the fast task switcher works on the iPhone does not do what you claim.. And you can claim it all day long, but as long as you are jailbroken and running jailbroken apps you will never be able to prove it or make a convincing argument that there is something wrong with the implementation.
I use it on my phone all day long, not jailbroken, and the phone does not slow down or bog down.
You keep referring to them as being backgrounded, but that is not what it is. Others have explained how it works, but it seems like you don't really understand what it is doing.
This is one of my problems with people who jailbreak. If you are not knowledgeable enough about what is going on, you are potentially going to have problems that you blame on people who do not deserve it. You don't seem to have the knowledge required to understand what is going on, so you are making some pretty faulty assumptions.
Based on my use patterns, if I have alot of apps in "saved state" Safari pages will constantly refresh when switching between them. Therfore "saved state" does have a negative impact on RAM and performance.