Database Users

[Q] How do i stop programms from auto executing?

running UK 2.1 build 6649. I have it rooted...how do i stop certain apps from launching. When i check task manager , all these programs are running when I never launched them. Kind of getting sick of Autotask killer and Cache memory cleaner programms to recovery ram

Ignore them. Most are likely not "running" but are frozen in state in RAM and don't affect you at all. Killing apps the OS has started only means the OS will re-launch them using the same RAM and more battery life.
I only use a task killer if an app is really acting weird.
I've never figured out why Android launches some apps, but I ignore them.
You'll sleep better too!

[Q] What's the easiest way to exit/close a running application in NC?

Hi there. First time android user, do not have much experience just wondering what would be the easiest way to exit/close a running application in NC?
The way I'm doing it right now is through Home Button -> Task Manager and Kill the app.

Some apps have an exit option if you click the menu button, but the majority of them do not. Android will automatically close apps that are not being used if it needs memory for currently running apps, so I wouldn't worry too much about it

Advanced task killer there's just a little Droid Guy in notification click him then full view of running apps, to kill/switch to, as well as showing free ram.
sent from a Nook Color using xda-app
Oops didn't see that's what your doing, some apps have an exit but tbh even hitting that most stay running in task manager, I'm a first time android user as well, but task managers just seem the best.

I find that the NC doesn't close apps... in fact I've had as many as 12-13 apps running in the background. I either kill them all or do a reboot every day or two days.

Easy Way
Just Download " Android Assistant " From Android Market For Free
And It Will Close All Not Used Programs At Once

if you are using cm7, go to Settings>Applications>Development, check Stop app via long-press, then you can kill an app by long-pressing the BACK button.
i think this is the best way to exit and kill an app, hope it help

accept97 said:
Hi there. First time android user, do not have much experience just wondering what would be the easiest way to exit/close a running application in NC?
The way I'm doing it right now is through Home Button -> Task Manager and Kill the app.
Click to expand...
Click to collapse
As of Android 2.2 Froyo, memory management is much improved. Unused apps in the background are automatically killed off, and there's been a lot of discussion that task killers actually degrade performance. The issue is that some of the apps that these kill will automatically reload, actually consuming more battery in the process.
However, there are some apps that stay active in the background that can cause problems. There is a difference between just "flipping away" from an app, and backing out. If you back out of an app (with the back button or right-left swipe on the status bar if using B&N 1.4.1), these will free up properly.
I'd try that first. Then, if the results still aren't satisfactory, you can play with the task killers.

[Q] How to save memory

What is the best way to conserve memory to ensure the nook is running at full potential? Also does supercharger v6 work?
Sent from my Incredible 2 using XDA App

Yes V6 script works amazingly. What ever you do do NOT EVER use a task killer!
---------------------------------
Sent from my LG Optimus V using Tapatalk

Why shouldn't use task killer?

flynlady said:
Why shouldn't use task killer?
Click to expand...
Click to collapse
I develop Android apps so I'll explain why a task killer isn't needed on an Android system.
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’s code (activities) needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.
* Android is hard coded to automatically kill a task when more memory is needed.
* Android is hard coded to automatically kill a task when it’s done doing what it needs to do.
* Android is hard coded to automatically kill a task when you haven’t returned to it in a long time.
* Most services (while possibly running in the background) use very little memory when not actively doing something.
* A content provider is only doing something when there is a notification for it to give. Otherwise it uses very little memory.
* Killing a process when it isn’t ready only causes it to have to reload itself and start from scratch when it’s needed again.
* Because a task is likely running in the background for a reason, killing it will only cause it to re-spawn as soon as the activity that was using it looks for it again. And it will just have to start over again.
* Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few.
* The only true way to prevent something from running at all on your phone would be to uninstall the .apk.
* Most applications will exit themselves if you get out of it by hitting “back” until it closes rather than hitting the “home” button. But even with hitting home, Android will eventually kill it once it’s been in the background for a while.
If you see an app running that you didn't launch, it's most likely because an activity within that app was called by another app to perform a task. If you kill the app you didn't launch, the system has to relaunch that app in order to complete its task. This is why some people kill a task and then see it immediately running again. Constantly killing that app creates a situation where the user is battling the system resulting in wasted system resources.
Android is Linux Android is not a Windows-based OS, it is based on Linux. Many of the apps you think are running aren't actually running, they're cached, this is typical with a Linux operating system and is much more efficient than other systems. Cached apps don't use any CPU or battery, they're cached and will load faster the next time they're needed.
Let the system manage resources.
Sent from my NookColor using Tapatalk

I have had many apps running and my system gets slow, and when I look to the available memory is super low like 25mb. In order to get the system nice and smooth I used Advanced Task Killer to close all those apps that don't automatically close like you say. Maybe its just my NC, or maybe its a problem with the apps I used, but I do find it useful to use a task killer. I can select which apps to close so I normally close games, media, etc. The other system and necessary apps I leave running.
In my experience with the NC having a Task Killer has been better.

jgaf said:
I have had many apps running and my system gets slow, and when I look to the available memory is super low like 25mb. In order to get the system nice and smooth I used Advanced Task Killer to close all those apps that don't automatically close like you say. Maybe its just my NC, or maybe its a problem with the apps I used, but I do find it useful to use a task killer. I can select which apps to close so I normally close games, media, etc. The other system and necessary apps I leave running.
In my experience with the NC having a Task Killer has been better.
Click to expand...
Click to collapse
I am sure that the previous developer, koopakid08, is correct about the way Android handles memory and apps, and I really enjoyed and appreciated his detailed post. I just have to believe what he says is accurate, as others also say the same thing. But I totally agree with you that using a task killer absolutely helps my Nook Color run better whenever the available memory gets below, say, 75mb. Without killing tasks, my Nook Color may not respond for many minutes, or may self-restart on it own. Perhaps there is something about using task killers after all.

koopakid08 said:
I develop Android apps so I'll explain why a task killer isn't needed on an Android system...
Click to expand...
Click to collapse
Please tell me you didn't type all that out on your Nook. Bless your fingers...
Sent from my DROID BIONIC

[Q] annoying apps running

how to stop apps that are always running in the background? i was so annoyed by the facebook app that is always running even though i logged out and stop it in running apps in the settings.

You might see it there but it doesn't necessarily mean it's using considerable amount of CPU. It surely does take some amount of memory but then it will be automatically displaced when a foreground app needed more memory.
Just let the android os handles it's memory. Using a task killer or the likes is not recommended actually.
Tapatalked from my Xperia P

[Q] How can I manage background processes?

Basically, I went into Settings>Apps>Running and realised I don't want Facebook in there ever unless I actually open the app. I opened the Facebook app Settings and disabled Notifications off. Also Messenger Location Services is off too. Each time I try and kill the process or reboot it comes back.
Things that load that I want to permanently disable unless I actually open the specific app:
Facebook
Maps
Google Play Store

I use Titanium to put a widget on my screen where I can freeze and unfreeze that app. I have done it with maps and some other programs that were aggressive in their communications. Unfreeze them, open and use, refreeze when done.

Thanks grubbster.
Any other options available to me?

Other than ignoring it, you can kill the app each time you close it. There's a developmental setting that shuts down the apps (not sure if it's in Cyanogenmod only or just stock) because it doesn't keep anything in the background. This would close ANY app that's not holding forground view however.

I'll just leave it as it is to be honest. Just thought there was a quick way of doing it similar to how the MSCONFIG utility operates in Windows.

MSCONFIG does that for startup, there are apps that block apps from starting up in android too but those apps need to be running as well which defeats the whole purpose of having plenty of RAM in the first place..
The whole point is Android manages the background apps just fine. Having 2GB of RAM but wanting 1.6GB to be free all the time (200MB used by GPU AFAIK so you are left with 1.8GB) is not the smartest way to manage apps. You want them snappy, in and out and done. Apps sitting in memory doesn't use more power because the RAM is active even as long as it's plugged into the the motherboard.