How to use Tasker to auto-kill app when screen is off?

[jakobkraft]

I have full version of Tasker which I use to control brightness on certain apps and which I've read does a million other things. I'm pretty sure that there's also a way to auto-kill an app with Tasker so the app switches off automatically when my screen is turned off but I can't figure out how to do it. My phone is rooted T-Mobile Galaxy S2, btw. I know there are certain Task managers that are supposed to be able to do this but I tried several and none of them worked.
The program I'd like to close when screen is off is LGCamera app -- invaluable since I shoot A LOT of HD video (its fixed-focus mode is awesome), but annoying because very often when I reawaken my phone, the camera display is corrupted. Easily fixed if I close and restart the program but could be avoided if the program would just close on its own when the screen goes off.

Any help would be greatly appreciated -- thanks in advance!!

 

[ardchoille]

Auto-killing apps is bad for android systems, here's why:

Activities
Android apps use activites to preform tasks. For example, if you use a file manager to send a picture via email, the file manager calls the send activity within an email app, passes the file name to it and the email app sends the picture.. not the file manager. This will result in seeing the email app as "running" even though the user didn't actually launch that email app.

Smaller apps
Using activites helps developers design smaller apps. A file manager app that contains every bit of code needed to do everything a file manager does would likely be so large that no one would want to install it. Developers know that an android phone more than likely has an email app so there is no need for the developer to include email code in his/her file manager to send a picture when he/she can call an activity in an existing email app to do the job. This results in a smaller file manager app since there is no need to include email code or any other code for an activity that can be done via an app that is already present on the phone. This also alleviates redundant code. When you install an app outside of the android market, also known as sideloading, the file manager app calls the package installer (already present in Android) to install the requested app.

Running apps vs. cached apps
The "Manage Applications" list included in many android devices lists running apps as well as cached apps. Cached apps don't use any CPU or battery, they're cached so they will load faster the next time you need them. Killing cached apps results in those apps requiring more time to load the next time they are launched.

System management
By default, every android application runs in its own Linux process. Android starts the process when any of the application

 

[jakobkraft]

Auto-killing apps is bad for android systems, here's why:

Activities
Android apps use activites to preform tasks. For example, if you use a file manager to send a picture via email, the file manager calls the send activity within an email app, passes the file name to it and the email app sends the picture.. not the file manager. This will result in seeing the email app as "running" even though the user didn't actually launch that email app.

Smaller apps
Using activites helps developers design smaller apps. A file manager app that contains every bit of code needed to do everything a file manager does would likely be so large that no one would want to install it. Developers know that an android phone more than likely has an email app so there is no need for the developer to include email code in his/her file manager to send a picture when he/she can call an activity in an existing email app to do the job. This results in a smaller file manager app since there is no need to include email code or any other code for an activity that can be done via an app that is already present on the phone. This also alleviates redundant code. When you install an app outside of the android market, also known as sideloading, the file manager app calls the package installer (already present in Android) to install the requested app.

Running apps vs. cached apps
The "Manage Applications" list included in many android devices lists running apps as well as cached apps. Cached apps don't use any CPU or battery, they're cached so they will load faster the next time you need them. Killing cached apps results in those apps requiring more time to load the next time they are launched.

System management
By default, every android application runs in its own Linux process. Android starts the process when any of the application

 

[ardchoille]

Normally I would agree would all this -- but the fact is when I turn on my screen, if my camera app was open when the screen timed out, the display is completely corrupted and unusable. I have to close it and reopen it to continue use. Go here to see video of the issue: http://androidforums.com/android-applications/455693-lgcamera-app-screen-goes-corrupt-if-screensaver-comes.html

In this case, the app does NOT turn off on its own from disuse or is cached, as your info suggests, so ideology aside, an app killer would definitely be a good thing in THIS case.

My info is taken directly from Google, the creators of android. If your camera app is causing problems then I would suspect the creator of the app overlooked a bug.

 

[Kicksilver]

Simple: uninstall the task killer

It'll work wonders.