Database Users

Quick question on using Advanced Task Manager

Im using advanced task manager to kill tasks so too many are not running. I used it all the time with the mytouch. Now using it with new Vibrant
Question,
I have excluded TwLauncher from being killed when I press end all, or press the widget. but when i kill all tasks (except for the excluded ones) I has to reload my home screen. What other process should I be exclude from being killed so that it does not reload my home screen?
Thanks

the better question is what else did you kill? Keep killing apps often so the list is small and see what app it is. Even better would be to close the one at a time and go back to the home screen each time.
In all reality, with the amount of ram and how good android is at killing apps itself, taskkillers are not needed. Infact google does not recommend them.

Like previously stated, do not use a task killer. Uninstall, reboot and you will have no issues.

s15274n said:
Like previously stated, do not use a task killer. Uninstall, reboot and you will have no issues.
Click to expand...
Click to collapse
precisely.
forcing your phone to constantly kill apps only causes your phone to restart the services which were running in the background. While your phone is now being forced to RE-start those services it uses more clock cycles than simply leaving the services running would have done.
There's more than enough literature and evidence that task-killing in Android is at best useless, and at worst counter-productive.

Common problem or just me???

Hey guys,
Just wondered if any of you have severe lagging problems at times, where i press to call someone but it takes up to 4 - 5 minutes to actually respond, or perhaps never responds untill i apply a soft reset.
I also seem to have noticed these occurrences happen when the battery symbol goes down a bar. I think that as soon my 4 bars becomes 3 i encounter some lag and general sluggishness on the device...
Sorry if this has already been covered in the forums, any help will be appreciated!
Dave

hey dude.
there are lots of lagging issues with windows mobile devices.... thats one of them main factors that keep windows mobile so unpopular.
im not sure how familiar you are with windows mobile OS... but if youre only learning, i can tell you that hitting the 'x', 'back' and 'home' buttons will not exit a program... it will just minimise it.... leaving the program running in the background, consuming all your resources (RAM).
the way to close all the apps that are running in the background is to go to:
start > settings > system > task manager
close all running tasks (similar to PC).
Im not sure if this is the cause of you device being slow, but it might be.
let me know how you go.
cheers.

[email protected] said:
im not sure how familiar you are with windows mobile OS... but if youre only learning, i can tell you that hitting the 'x', 'back' and 'home' buttons will not exit a program... it will just minimise it.... leaving the program running in the background, consuming all your resources (RAM).
the way to close all the apps that are running in the background is to go to:
start > settings > system > task manager
close all running tasks (similar to PC).
cheers.
Click to expand...
Click to collapse
Dutty's task manager ?

not too sure what duttys task manager is all about... im afraid i have never used it. the task manager i was referring too is the standard windows mobile one.
there are task managers and then there are task managers.
some task managers manage your tasks (pick up some milk on way home, take out garbage sunday night... those kinds of tasks - Outlook tasks).
other task managers (the one that will save your RAM), operate similiar to the task manager on your PC.

Cheers for the replies!
I think have installed that task manager (the one in the top right corner with a drop down application list) and that works a treat.
It's not a HUGE problem as I'd say it's fine 90% of the time. I've just been caught off guard a couple of times where i need to use my phone urgently and it just doesn't respond!
Would clearing up some space on the device smoothen it out? i have about 50MB left free
Cheers
Dave

Ive encounted this problem before. Ive flashed new roms + radios etc nothing seams to work it just sorted itself out over time.
try a new radio though think that helped out alot

High number of unrelated apps running on boot.

Just noticed on the last couple of Roms that there are a number of unused applications running in the background. No particular builds are better or worse.
Why is this the case?
Eg stock MDJFroyo Streak Lite and with all the widjets deleted and a fresh restart I have
Facebook
Gallery
Google Search
Maps
Music
Search
Twitter
Youtube.
Now I don't normally use any of these and have static wallpaper with wifi and bluetooth disabled. No widgets showing.
Is this normal?
Was going to use a tool to prevent these from auto loading.

i use autorun killer to see what runs on boot up
give it a try and disable those you dont need

Ran autotask killer however none of the apps showed up.

This is perfectly normal...using a Task Killer won't work as the app will just start up again soon after you kill it. task Killers are not recommended.
It just means the apps start faster when you launch them...they don't do any harm sitting idle in the background.

search for "AUTORUN killer"
not auto-TASK

[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