A Detailed video breakdown of ios multitasking shows you dont need to kill your Apps.
Posted 08 January 2012 - 02:03 AM
A few days ago, iPad education proponent Frasier Speirs had an interesting post on his blog which corrected several misconceptions about iOS multitasking. The post explained thoroughly why killing all of the applications running in your iOS device’s multitasking tray is a fool’s errand.
Simply put, it is largely unnecessary to manually close all of the running apps in your tray in order to regain ‘lost’ memory, conserve battery live or make other apps run better. There are some basic exceptions, like crashed apps or heavy GPS users, but in general, it’s useless.
Speirs got a lot of responses to the post, many with detailed questions and inquiries about his opinions. Instead of answering them individually, he used the Instruments package provided by Apple to monitor the memory usage on the iPad as he ran and closed apps.
The results show pretty conclusively that closing apps, outside of troubleshooting a problem, is unproductive.
Speirs explains the experiment:
There are five sections to this video demonstrating:
An app going from active to background to suspended
Instacast HD requesting extra background time to finish a podcast download
TomTom running indefinitely in the background
Batman Arkham City Lockdown and Real Racing 2 HD competing for big chunks of device memory
Batman Arkham City Lockdown forcing several smaller apps out of memory
The iPad in this video is an original iPad running iOS 5.0.1. All the apps used are the current versions at the time of posting this video.
We’ve heard a lot of misinformation lately about how multitasking works. A lot of bad advice has been given about killing all of your apps being mandatory for good performance and much of it has come directly from the mouths of Apple Store employees.
This video shows that most of that talk is flat out wrong. If there is a problem with a specific app, it’s frozen or refuses to quit when it should, then killing it by holding down until it ‘wiggles’, then tapping the ‘-’ button can be a good troubleshooting option. But it is definitely not necessary for day-to-day operation of your device.
via The Next Web
You Tried it from xRepo? You Like it? then Buy it!! That's our Purpose as xSeLLiZe.
Leechers are not welcome Here. i Will Put my Foot Down weather you like it or not.
Posted 08 January 2012 - 03:40 AM
Posted 08 January 2012 - 05:44 AM
Very informative article/video, but didn't we already know multitasking worked this way?
Some people who are still reliant on Backgrounder don't necessarily think the same. They think that they need complete control to get proper and/or desired effects. :/
Posted 08 January 2012 - 06:58 AM
Posted 08 January 2012 - 07:04 AM
Posted 08 January 2012 - 07:20 AM
That's the way multitasking should designed, give user freedom whether to minimize or quit.
Posted 08 January 2012 - 10:25 AM
Clear all the apps and it goes up.
Posted 08 January 2012 - 12:13 PM
"When you press the home button, the app moves from Active to Background. Most apps usually then go from Background to Suspended in a matter of seconds" True Story Bro!
Its only me that have more than 200Mb free of Ram without any app open and with many app in backgroud even after wait 10min still have something like 10 or even 20Mb of Ram free?
So SBSetting and all the other JB app that give you the free ram are wrong?
If someone tells you that all the apps in the multitasking bar are running, using up memory or sucking power, they are wrong.
The problem is not the use of CPU or power but the fact that less free ram really make you phone slow and sometimes crach apps!
When you hit the home button, an app moves from Active to Background and quickly to the Suspended state where it no longer uses CPU time or drains power
Like I said, that dont happen in all app, or a video showing it, will be nice, other way is just a person talking...
An app may request an additional 10 minutes of Background running to complete a big task before becoming Suspended.
Edited by ALL, 08 January 2012 - 12:14 PM.
Posted 08 January 2012 - 12:55 PM
Posted 08 January 2012 - 08:45 PM