Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iPhone 4 app killer programs???

Well, my iPod touch 4 lasted for 3 days on one charge since I've been killing the apps every time I use it. Amazing. I thought I had a defective iPod, and now I think I can use some of the location services and other things I stopped using because of the drain. Excellent tip.
 
gks said:
I'm a developer. I know how this stuff works. So until you provide me any actual proof then you're talking out your ass compared to apple documentation.

Here's what's happening. Games or ANY app will be frozen into a state that can be reloaded. This state is what is commonly referred to as "Fast App Switching." This means that any app designed to take advantage of this will appear as though it was never actually quit. That's why a game will have itself "paused" and when you come back to it even days later it will appear as though you never left it. This is by design.

An app will NOT LEAVE MEMORY until the operating system declares it needs that memory. Free memory is wasted memory. There are several states memory can be allocated for. To make things simple let's talk about 3 of those states. Free meaning nothing is in there. Which is what you're probably seeing in SBSettings. If you leave an app, it will not "free" that memory. Why should it? If you go back to that app it may as well just load the app from RAM since it is significantly faster than loading it from flash memory. Just because the app is in memory doesn't mean it is actually running.

So, let's summarize. An app can be in memory and not be running. Memory is simply that. Memory. It can be flagged for clearing if another app decides it needs more memory than what is free. So when an app is quit, that memory is flagged for removal. If another app needs it, it can have it. In fact, this is true of ANY app not currently in the foreground. That's why if you fire up other apps like Pandora or Instacast, start playing audio, then run several other apps in an attempt to use up memory. Eventually Pandora/Instacast will stop playing audio because some other app needed memory and was foreground.

It's the same deal as what happens with Safari. If you load a webpage, go into another app, come back to safari and the page neds to reload. The memory was effectively marked as flagged for destruction and some other app needed it so it was reallocated to another app.

Since you seem to be a cocky ass... let's back it up with some actual proof from the Apple Developer documentation.

iOS Application Programming Guide



This means that you can have Audio, GPS, or VOIP apps running in the background. The other option is Task Completion (Under the heading "Completing a Finite-Length Task in the Background") which as I stated has a maximum of 10 minutes to complete.

No app can exist in the background and run code. You do not need a task killer app, nor do you need to kill tasks using the minus sign. The operating system will handle it all for you.

Don't be a dick, dick.
Click to expand...
I'm new to the iPhone and I know this is an old thread,but the first item I was shown by a veteran smart phone user was an APP that monitored device usage.battery drain,memory usage,etc.
And yes, the apps in the background do use all that and drain batt life like crazy.I don't have to be a developer to do simple math.
That being said, is there an app killer/manager that handles this function yet?
 
Last edited:
You know what I think is interesting...even when u do kill an app like safari it'll still open up next time with the same pages u killed it with. Try doing that w Mac os. What's that all about?? Impossible to really stop safari?
 
Pjk2012 said:
You know what I think is interesting...even when u do kill an app like safari it'll still open up next time with the same pages u killed it with. Try doing that w Mac os. What's that all about?? Impossible to really stop safari?
Click to expand...

Um... you can do that with Mac OS.

Anyway, all Safari would have to do is save a list of open pages when it gets a quit message, and then reopen them when it gets an open message. This is a pretty feeble attempt to prove that it is "impossible to really stop Safari."
 
You are dumber than you sound.

gks said:
I'm a developer. I know how this stuff works. So until you provide me any actual proof then you're talking out your ass compared to apple documentation.

Here's what's happening. Games or ANY app will be frozen into a state that can be reloaded. This state is what is commonly referred to as "Fast App Switching." This means that any app designed to take advantage of this will appear as though it was never actually quit. That's why a game will have itself "paused" and when you come back to it even days later it will appear as though you never left it. This is by design.

An app will NOT LEAVE MEMORY until the operating system declares it needs that memory. Free memory is wasted memory. There are several states memory can be allocated for. To make things simple let's talk about 3 of those states. Free meaning nothing is in there. Which is what you're probably seeing in SBSettings. If you leave an app, it will not "free" that memory. Why should it? If you go back to that app it may as well just load the app from RAM since it is significantly faster than loading it from flash memory. Just because the app is in memory doesn't mean it is actually running.

So, let's summarize. An app can be in memory and not be running. Memory is simply that. Memory. It can be flagged for clearing if another app decides it needs more memory than what is free. So when an app is quit, that memory is flagged for removal. If another app needs it, it can have it. In fact, this is true of ANY app not currently in the foreground. That's why if you fire up other apps like Pandora or Instacast, start playing audio, then run several other apps in an attempt to use up memory. Eventually Pandora/Instacast will stop playing audio because some other app needed memory and was foreground.

It's the same deal as what happens with Safari. If you load a webpage, go into another app, come back to safari and the page needs to reload. The memory was effectively marked as flagged for destruction and some other app needed it so it was reallocated to another app.

Since you seem to be a cocky ass... let's back it up with some actual proof from the Apple Developer documentation.

iOS Application Programming Guide



This means that you can have Audio, GPS, or VOIP apps running in the background. The other option is Task Completion (Under the heading "Completing a Finite-Length Task in the Background") which as I stated has a maximum of 10 minutes to complete.

No app can exist in the background and run code. You do not need a task killer app, nor do you need to kill tasks using the minus sign. The operating system will handle it all for you.

Don't be a dick, dick.
Click to expand...

You are incredibly dinner than you sound. Just because you are a "developer" doesn't mean that you know what you are talking about. In your post you referenced an apple source. Can you really rely on them for a topic such as this? When has apple ever admitted to screwing up? Remember the whole antenna issue? And how can you account for theendless number of iUsers that notice a jump in responsiveness of their devices after the kill the apps? Its simply black and white. Even if the apps are in a "frozen" state, they still occupy precious memory resources. Thy have to in order to jump back to the same place without reloading. Even if other apps force them to vacate memory, that's only of you are maxed out. Even if the app itself isn't running processes, the iOS is in order to keep the apps going. You can preach your free memory speech all you want but as long as the devices keep bogging down, learn how to bite your tongue. It'll save us all some headache.
 
Hi everyone :) I have read many of your posts about apps running in the background and how it may affect the functions and battery life of your iPhone...I understand that there is an ongoing argument about what causes these problems and I had a talk with an Apple Tech about this.

They said sometimes battery life is reduced dramatically due to Push Notifications cycling to frequently, downloading many programs at a time without re-springing your device and updating iOS without re-springing your device.

(Re-springing is widly used on jailbroken iPhone hack programs that need to reset (everytime you change the settings in that program) in order for changes to take affect) Re-spring is a built in feature on the iPhone and does not need a jailbreak to use it. Simply powering off your iphone will not re-spring/reset your phone; it will just shut it down; not re-spring it.

Simply:

Press and hold the POWER and HOME button simultaneously until the screen goes black...then wait 3 seconds, then let go. You can also re-spring using Siri by saying 'RESPRING'. (But I haven't had much luck with it).

You should notice on some occasions your battery life jump significantly; and you will notice that iOS update clutches disappear.

Only use when:

-You just unplugged your fully charged iPhone and the battery life drops in minutes.

-You notice programs crashing a lot (due to many program, song and video downloads)

-You did an iOS update. YOU MUST RE-SPRING AFTER AN iOS UPDATE. If you don't and you take your iPhone to the store for help 99% of the Techs there will say "there is a problem with your software and we need to do a factory reset..." They will ask if you are backed up on iCloud or a computer. And then they will set up an appointment for you to come in to do this factory reset :eek:

PLEASE RE-SPRING TO AVOID THESE PROBLEMS :eek:

I hope this is helpful :)
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back