Database Develop

Any app to auto kill on exit?

Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App

It would be nice to have, say, long press back key to kill the current app.

Big_O said:
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You obviously didn't search for this:
http://forum.xda-developers.com/showthread.php?t=678205
You DON'T need to intervene with N1 memory management, since you don't know how it works. You assume wrong. And most bad gossips are created by people wrongly assuming something, thinking they know something while they actually don't.
My N1 runs equally well with 40MB and 250MB free. The only reason I use a task killer is to kill apps that I want to return to their "initial" state for some reason, or to kill apps that I suspect of wrongdoing.

Exactly, the nexus has no memory management issues. It is just your misunderstanding of how Android works. Leave your tasks alone.

If you have one or two particular apps that are bad citizens and should be shutting down in the background but don't... you can use "1Kill" from the market to create a home screen shortcut that kills that specific app when you press it.
Fring used to be a bad citizen - it would lock my wifi on even when I didn't want to be using it, and had no exit feature. So I'd always have to kill it after finishing up with it. Now it does have a proper exit, thankfully.

Jack_R1 said:
My N1 runs equally well with 40MB and 250MB free. The only reason I use a task killer is to kill apps that I want to return to their "initial" state for some reason, or to kill apps that I suspect of wrongdoing.
Click to expand...
Click to collapse
Ditto!
1 app running or 50 apps running they all still run the same.

I find it even funnier how iOS4 users in Apple-land are suddenly freaking out that so many applications appear to be open "in the background" and complaining that they have to spend so much time "killing" apps.

Big_O said:
Seems the N1 has memory management issues. Instead of constantly closing apps to free up memory or have some app try to manage things, be nice to just kill the thing on exit. Any app that will auto-kill when an app exits?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I think you have the memory management issues.

Before anyone gets tarred and feathered, that explains why many users on unrooted stock roms ha e frequent touchscreen lockups, hesitation and freezes. Guess theres a reason why the market has so many task killers. Maybe the devs should read this thread also lol. Instead of flaming, positive feedback is appreciated. I did search, but its a bit time consuming sifting through 5000 posts. Maybe you guys o rooted phones have no lockups, but google shows an azzload of people with similar issues.
Sent from my Nexus One using XDA App

1) You've been given some answers in the thread, if you cared to look.
2) App that loses focus goes to background. That's the way OS is built. If you want apps to be killed on losing focus, get iOS 3 to run on your device. Seriously, what kind of answer would you expect, if you want to turn multitasking OS into non-multitasking?
3) The market has task killers because they can be written for multitasking OS, and because they help dealing with bad apps. Not for any other reason.
4) The OS loads some of your most used tasks when it runs, even if you don't know about it. Just loads in the memory, and allocates no CPU time. If you leave your phone unattended, your free memory goes down by itself. Why? Because free memory is wasted memory. You can check the "EMPTY" processes in Astro, for example.
5) The best task killer is careful selection of your apps. You see hangups? Find out the app that's doing it and remove it, or kill it specifically after running if it's necessary.
6) Task killers are a good source of lockups and freezes too, did you know? I guess you didn't read that thread...
All this meant to say: instead of looking for a way to cripple your OS, learn to select your apps, and don't solve issues that you don't have.

cmstlist said:
I find it even funnier how iOS4 users in Apple-land are suddenly freaking out that so many applications appear to be open "in the background" and complaining that they have to spend so much time "killing" apps.
Click to expand...
Click to collapse
Yeah, I think Apple needs to tweak their multi-tasking still. I've played with my gf's iPhone a bit this week, and it's a little annoying how now you have to explicitly quit every app. For example, with the Settings app if I go to change a preference quickly then return to home Settings app is still in the running apps list. I think little utilities like that should be able to quit themselves automatically.
I know the app isn't wasting memory or CPU down there, but I just don't see why you would want it cluttering up your app switcher forever.
Oh well, it's progress though. At least now you don't have to quit everything else you're doing to listen to Pandora

well android does the same thing. if you go into the settings menu, then hit home button, the settings is still running in the background. of course andoird will kill it later when it needs to.

Apps automatically starting up, by themselves

Hello all,
I recently bought my N1 about 4 days ago. So far its been great. Easily one of the best phones I've ever owned. However, I am having this problem where apps in android seem to startup by themselves. I'm using Advanced Task killer to kill em but ill kill them and then like a minute later they're back up and running without me starting them. Its quite annoying as my battery is taking a beating from it having to close and open apps and repeat. The biggest offenders of this are the voice apps such as voice search, voice dialer, Google voice (which isn't even setup), and the amazon mp3 store. A few third party apps I downloaded tend to do this as well.
Have any of you guys experienced this? Is there any way to fix it? Thanks in advance! XD
Sent from my Nexus One using XDA App

decoyjoe said:
Hello all,
I recently bought my N1 about 4 days ago. So far its been great. Easily one of the best phones I've ever owned. However, I am having this problem where apps in android seem to startup by themselves. I'm using Advanced Task killer to kill em but ill kill them and then like a minute later they're back up and running without me starting them. Its quite annoying as my battery is taking a beating from it having to close and open apps and repeat. The biggest offenders of this are the voice apps such as voice search, voice dialer, Google voice (which isn't even setup), and the amazon mp3 store. A few third party apps I downloaded tend to do this as well.
Have any of you guys experienced this? Is there any way to fix it? Thanks in advance! XD
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Do not worry about app running in the background, what you are probably seeing is the list of what was run, Android is verry good at managing memory, in fact I do not even use a task manager and I am fine with it.

Well that's the thing. Some of these apps that startup I have never run such as the mp3 store. So I close it and I get an additional 10megs of memory. But then it just starts back up. So I don't know how to stop it all together.
Sent from my Nexus One using XDA App

There are apps that automatically run in the background but don't effect performance like Google voice voice dialer etc..what I did was add them to the ignore list. Trust me those apps are always running no matter how many times you close them
Sent from my Nexus One using XDA App

Like has already been said, stop worrying about it. Those apps are NOT stealing memory, they're NOT using battery.

Free memory does not benefit you. Android will automatically load apps in to memory so that they are available to switch to fast as possible.
You should not kill apps unless they are bisbehaving. Killing off apps forces Android to load them back into memory if its algorithm thinks you are likely to use it. The act of loading data into memory uses power and Android tries hard to avoid it.
I was obsessed with managing my memory and running apps when I bought my nexus one. Everyone at that time suggested task killers so I got one of those. I had crappy performance with random sluggishness. I figured I just needed to kill off more apps. Eventually I read an article from an Android dev explaining this stuff and I backed off and have had a much better experience since.
I wish Google was more vocal on this subject. Everyone thinking auto task killing is a necessity on Android really gives it a black eye.
Sent from my Nexus One using XDA App

http://forum.xda-developers.com/showthread.php?t=712352
Jack_R1 said:
...
2) App that loses focus goes to background. That's the way OS is built. If you want apps to be killed on losing focus, get iOS 3 to run on your device.
3) The market has task killers because they can be written for multitasking OS, and because they help dealing with bad apps. Not for any other reason.
4) The OS loads some of your most used tasks when it runs, even if you don't know about it. Just loads in the memory, and allocates no CPU time. If you leave your phone unattended, your free memory goes down by itself. Why? Because free memory is wasted memory. You can check the "EMPTY" processes in Astro, for example.
5) The best task killer is careful selection of your apps. You see hangups? Find out the app that's doing it and remove it, or kill it specifically after running if it's necessary.
...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=678205
Remove your task killer (or, if you insist, just clear the auto-kill list), erase all you think you know about memory management - because you don't know - and stop worrying.

[Q] ignore Apps in 2.2 Task Manager

how the title says how can someone ignore Apps which are need like (sms time fix) when one clears the memory and not having to restart the app every time after clear memory

Just don't use the level 2 clear and you'll be fine. Only apps you should ever kill are the ones that show up in "Active Applications". Except for your launcher of course. Killing system apps and services is like shooting yourself in the foot.

ryude said:
Just don't use the level 2 clear and you'll be fine. Only apps you should ever kill are the ones that show up in "Active Applications". Except for your launcher of course. Killing system apps and services is like shooting yourself in the foot.
Click to expand...
Click to collapse
How so? Could you elaborate?
I'm sincerely curious as to why the L2 clear is a bad idea.
Thanks, dude!

Senor Forum said:
How so? Could you elaborate?
I'm sincerely curious as to why the L2 clear is a bad idea.
Thanks, dude!
Click to expand...
Click to collapse
Clearing L2 level cache kills essential android processes too, and system would again need to restart all the needed ones again. Read abt 'android memory management' (link in my signature), and see if that helps.

Senor Forum said:
How so? Could you elaborate?
I'm sincerely curious as to why the L2 clear is a bad idea.
Thanks, dude!
Click to expand...
Click to collapse
App data is stored in RAM so that you use less CPU the next time you run that app. RAM uses much much less power than CPU, why would you want to have empty RAM?
If an app in your task manager shows cpu % next to it, then close it because you don't want the CPU to be used at all.

As the previous two said, why would you need to have RAM free?
This is not like BBOS, which needs like 25% memory free in order to start an app.
The whole reason for having high RAM is to use it, if it is always free (unused) what benefit do you get from it?
Using task killers or freeing up memory in order to save battery is only going to drain your battery more.
Android loads programs into memory based on what it deems needs to be available to run quickly... and once you kill it, it will use CPU to load it again shortly thereafter.
CPU is a bigger drain on power than letting programs hang in memory.

[q] best autorun task killer

Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works

no one is using any app. to stop unnecessary start up of tasks

try autostarts its very good
Sent from my GT-I9000 using Tapatalk

Ditto on Autostarts. Also, Autokiller Memory Optimzer works really well, it doesn't kill tasks itself, it tweaks the Android function thar does it to work better.

auto killer mem optimizer workd well for me.but now i simply don use any of those batt saving app,mem apps etc i jus kill apps in inbuilt task killer...iam using my phone to the peek cause at the end ill b getting a 2ghz dual core by selling sgs.......cant stick to old things lol........cheeerz

tarunagg said:
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
Click to expand...
Click to collapse
... what?
Do any of you even understand how Android works?

so mind sharing ur exp wiv us on how it works???

manosv said:
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
+1 Autostarts. It amazes me what runs on the phone after start-up, after you switch states or update apps. The perfect cure for batt draining nonsense

rocky23 said:
so mind sharing ur exp wiv us on how it works???
Click to expand...
Click to collapse
Google it. Android is Linux based. Its memory management is not the same as Windows. I'd explain further, but you're the 4,753,857,195 person to ask.

I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.

Shanakin said:
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Click to expand...
Click to collapse
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww

webwude said:
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
Click to expand...
Click to collapse
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.

upichie said:
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
Click to expand...
Click to collapse
Well actually I don't see the point that an app, that I hardly use once per month should be loaded everytime I start the phone or change my internet connection. Also more apps at startup increase the time when the phone is available...
But on the other hand, you are certainly right, after a while, only the latest apps are still in background / memory. What I have recognized nevertheless: if you use a lot of apps with push functionality and load on startup, the phone runs out of memory...
Kind regards,
ww

[Request] Process manager/Task manager

I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.

There is no more need to use task killer to manage android systems any more. You will be doing more harm than good, in fact there is no good in killing tssks manually.
Sent from my SAMSUNG-SGH-I747 using xda premium

Point noted.
But when I use Airdroid task manager, I see a process when the corresponding app is not running the background.
To mention a few; Cut the rope free, stocks & Hill climb racing.
Few system process like picasa uploader, chrome etc.
As you said andoird may optimize most of them, but I would like some control when running thin on battery.

mohan_168 said:
I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.
Click to expand...
Click to collapse
use greenify https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en to hibernate any persisting apps/processes (except system). apps relaunch when you open them.

Killing apps and then having to reload them actually uses more battery than them being dormant in the background and already loaded when called upon. The problem is when you have misbehaving apps that stay in the foreground eating up cpu, instead of going dormant into the background. And this does happen. I use an app called Watchdog that alerts me when this happens. It allows you to kill the app when this happens. It also allows you to whitelist and blacklist apps and processes.
Sent from my Nexus 4 using Tapatalk 4 Beta

main phone setting, apps, running.. default task/process manager. in the top right will be an option to show cached process as well.

simms22 said:
main phone setting, apps, running.. default task/process manager. in the top right will be an option to show cached process as well.
Click to expand...
Click to collapse
We all know that is there. The op mentioned wanting more options, mainly monitoring and kill options.
Sent from my Nexus 4 using Tapatalk 4 Beta

mohan_168 said:
I am wondering if we have a task manager/process explorer app for Nexus 4? Currently I am using AirDroid v2 that includes a task manager, but I am looking for one with more options.
I travel a lot & would like to kill as much unwanted applications running in the background as possible to conserve battery.
Click to expand...
Click to collapse
fernandezhjr said:
We all know that is there. The op mentioned wanting more options, mainly monitoring and kill options.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fast reboot(free), but the paid version i like better https://play.google.com/store/apps/details?id=com.greatbytes.fastreboot&hl=en

rayiskon, I will try greenify & let you know how that helps.
fernandezhjr, I agree restarting app is not an optimal way, but I require to squeeze battery to atleast make phone calls when I am away from charging options.
simms22, fast reboot looks promising. I'll try the free one for now and take it from there.

It's kind of already been said, but I want to clarify as much as possible.
Apps running dormant in the background (using RAM) use no more power than if it weren't running. This is because all of the memory you have is being refreshed all the time, the controller has no idea whether there is actually data there, it still refreshes the entire space of memory.
Apps running "dormant" but using CPU do use more power than if it weren't running. I assume OP is wanting some sort of monitoring app that shows which apps are using CPU, in which case is fine. If OP is wanting to kill all apps that he isn't using at the time to conserve battery, then he would actually be doing the opposite of what he wants, as it requires to CPU to spin back up to restart it later. Again, the difference here is RAM vs CPU, one doesn't use battery (or rather, uses the same amount of battery, no matter how much of it is being utilized), and one can use more or less battery depending on how much it's used.

Johmama said:
It's kind of already been said, but I want to clarify as much as possible.
Apps running dormant in the background (using RAM) use no more power than if it weren't running. This is because all of the memory you have is being refreshed all the time, the controller has no idea whether there is actually data there, it still refreshes the entire space of memory.
Apps running "dormant" but using CPU do use more power than if it weren't running. I assume OP is wanting some sort of monitoring app that shows which apps are using CPU, in which case is fine. If OP is wanting to kill all apps that he isn't using at the time to conserve battery, then he would actually be doing the opposite of what he wants, as it requires to CPU to spin back up to restart it later. Again, the difference here is RAM vs CPU, one doesn't use battery (or rather, uses the same amount of battery, no matter how much of it is being utilized), and one can use more or less battery depending on how much it's used.
Click to expand...
Click to collapse
Thanks for the detailed explanation. I understand killing process, shutting down cached process or apps & later restarting them is only going to fire up the CPU usage which completely defeats the purpose of conserving battery.
Though not a daily ask, at times I am stuck in situation where a phone call or SMS is all I need to keep me going.