After switching from Magic to Hero (which is a great improvement!) I've noticed that there are a couple of new recurring processes on the Taskiller list, which I have never seen before on the Magic; eg: com.htc.provider.weather, HTC locatiediens (=localisation service, in Dutch), com.htc.socialnetwork.provider, HTC media uploader; beside TouchInput and Touchflow, which I've already put on my ignore list.
I assume these are specific Sense processes, partly vital for the UI; is there anybody who could give a list of the vital processes, we should put on the ignore list and/ or a list of processes which are safe to kill if system slows down?
I've already contacted the dev of Taskiller; but he says he has no Hero experience, so cannot advice on this issue..
Any advice is welcome, thanks in advance!
Balazs
I have the same question...
It would be great if we know whixh process correspond to what
I fiddled around with this and it's safe to kill everything. The vital processes will just start right up again. socialnetwork.provider and provider.weather are, I'm assuming, to do with Facebook/Google integration and weather widget/applications respectively. If you're going to be killing processes regularly, I'd suggest you put touchflo and touch input in the ignore list, as they need to be running constantly for the UI to work. You can kill them, but the phone will hang for a few seconds while they restart.
Related
Hello Chefs (and all you microwave re-heaters..you know who you are..)
I have a request for a feature either as a standalone app, or implemented into a rom. Maybe, it's not possible. I don't know.
What I would love to see is a simple task killer (no gui) mapped to the 'hangup' button on android phones. When I'm running an app and I want to close it, I hit the hang up button, and it kills the currently running app. This seems to me to be intuitive, would streamline task management/eliminate unneeded apps running in the bg, and make Android much more user friendly.
Order of Operations would work something like this.
User starts an App (Browser)
If the user hits the hangup button, Browser would be killed and the screen would return to the home page. A second click on the hangup button would turn off the screen and lock the phone.
If the user hits the home button, the app stays running in the background, and when the user clicks Browser again, the app returns in it's current state with the last loaded page available.
Like I said, it seems pretty simple and straightforward. I know it would require a rooted phone, but it seems like it would give maximum flexibility to the user and allow them to kill the apps that they want when they want to. But maybe it's not possible. So please, let me know. Thanks for the great work guys.
And what would you do if you had a call running in the background?
WHY do you want to kill the running application? It won't do anything once you switch off of it except consume memory, and if more memory is needed, the task killer will take care of that for you.
If you need this you either:
* fail to understand how the user interface works in android (including reclaiming of processes)
Or
* are running applications by developers who didn't design the application to work correctly on android.
The button you are looking for is the back button. It will background the app immediately and allow it to be overwritten as soon as anything needs memory.
Why do several apps randomly start up?
It feels like I constantly have to open task killer and kill over a dozen apps even when my phone hasn't been touched since the last time I killed almost the exact same list of apps.
Att Navigator, stocks, countdown, etc. seem to be the regular culprits. Any help with this situation would be awesome.
I've noticed the same thing on my Aria. AT&T Navigator always restarts by itself and I've never even used it. So I just set ATK to auto kill.
Look at the sync settings and you can disable things you dont need (News, stocks etc)
A "Running" app behaves differently on android. The app may be "Running" but it is also "Sleeping" which means that it may not be using any resources (battery, cpu, etc).
Using a task killer may actually be hurting your performance and battery life.
http://androidspin.com/2010/05/25/why-you-dont-need-a-task-killer-app-with-android/
I just check the running apps on my Aria and I understand why every single one is running. AT&T Nav is NOT running. You should check all the widgets you are using, having the widget on the home screen start app automatically.
If you're rooted....
I can't tell you why it does it, but I can tell you how to stop it. If you're rooted, spend the $.89 (approx.) for Autostarts. One of the best programs I've installed.
I was having the same issue, I use AT&T Nav, but it always seemed to show up on the task list even when I hadn't started it. For whatever reason, it's set to start whenever you get a text message! With Autostarts I was able to stop it (along with many other things).
Best of luck to you!
armyengineer51 said:
I can't tell you why it does it, but I can tell you how to stop it. If you're rooted, spend the $.89 (approx.) for Autostarts. One of the best programs I've installed.
I was having the same issue, I use AT&T Nav, but it always seemed to show up on the task list even when I hadn't started it. For whatever reason, it's set to start whenever you get a text message! With Autostarts I was able to stop it (along with many other things).
Best of luck to you!
Click to expand...
Click to collapse
One caveat to this, BE CAREFUL. This is a powerful program and it will let you stop just about any service/program on your phone. You could really do some damage if you don't watch it.
I'm using Cyanogenmod 6 (stable) on my HTC Dream.
Now, I know that there's been a change in Froyo (Android 2.2) whereby task manager apps can no longer kill running apps. That's fine. I can kill tasks in Running Services if I want. (Although I wish I had a faster way of accessing the Running Services...)
Anyways, I'm noticing that I'm having a problem with apps being closed by the system when I definitely never want them closing unless I close them myself. I was able to do this just fine in pre-Froyo ... but there are really some apps, like AndChat, that I don't want closing at any odd random time (I'm guessing this happens when the system decides it needs to free up some RAM or something). Is there a way to keep certain apps ALWAYS running unless I close them?
Please tell me there's a way to do this. I'm loving Froyo otherwise, but there are some apps that I don't want the system closing on its own.
Please tell me there's a way around this. I never had this problem pre-Froyo.
Can I maybe prioritize non-essential processes or something (So that maybe it'd close some other app instead of the one or two I want to keep running)?
Please help
If you do, then whatever you are trying to do that causes those processes to be killed will NOT WORK. You will get the magical disappearing application problem where a newly launched program will randomly die. It could get really messy if there isn't enough free memory to load the launcher -- you'll end up in battery munching loops at seemingly random times.
*sighs*
That's just ... sad. I understand what you're saying. I do hope there's still another way though. I really try not to have much running. But sometimes even if all I have running is AndChat and a browser, AndChat would close. It's really annoying.
Thanks for your reply.
The most annoying thing to me about the way FroYo manages apps is that my browser will often close when not being used, and upon returning to it only the last page displayed will reload but any other windows that were open do not.
This never happened in 2.1
Sent from my PC36100 using XDA App
Hi, people...
I am running a rooted stock GB ROM with abyss kernel and would like to know how to prevent certain apps suddenly starting to run in the background. I have Android assistant installed and it is great for killing multiple apps and other stuff. But some apps like Latitude, Gmail, Samsung account, Yahoo finance seem to sneak from behind and when I check AA I see them running so I have to mark them and kill them. How can I completely keep them, or any other non-system app out of operation, unless I start them?
Many thanks....
Killing apps is NOT preventing apps from autorunning.
Task killers are bad because some apps will just rerun itself, wasting battery life.
I personally use Autostarts, it can prevent apps from running when starting up, or when triggered by an event like for example: Wifi connected, data connected, etc...
Be careful with it if you are trying to disable system apps as some things can break your phone.
Markuzy, thanks for the reply...
I know that killing apps isn't doing the job, but at the moment that is what I do when I check my phone and see the pest running around. I have Android assistant there I have been offered to stop stuff like Accuweather, Skype, Youtube and similar stuff from running at startup, but I will try Autostarts to see if that does better job and offer better and more comprehensive list of what can be NOT ALLOWED TO LIVE, as opposed to killing..
Don't worry, I'm not touching any of the system bits, just regular apps...
Use Titanium Backup(Donate version) and then freeze the offending apps.
You can always defrost them later
I know that android is very good at handling background processes and ram but I have so many apps that I don't use at all. They consume big amount of ram and for instance, sometimes browser loads pages again when I get back to it from another app. I assume this is because of ram. So I guess, if I can shut down some running apps in the background, available ram would be more.
I can see them at settings-apps-running(or cached processes).
For example, right now in "running" section I have 9 processes and 3 of them are poweramp, awesome beats, accuweather.com and in "cached processes" I have 10 processes and 6 of them are beautiful widgets,calendar storage,google account manager, google search, calendar, google play store. Other processes are system services that I have no problem with. When I go to developer settings-background process limit and block them, there are no cached processes anymore but that probably has a side effect. I wish I could choose which apps I want in the background.
I can shut down these apps manually but every time I restart the phone, they are there again. How can I stop them?
if you rooted, you can use Autostarts or ROM toolbox from the playstore. it can change the receivers of the apps not to start at boot
CooLasFcuK said:
I know that android is very good at handling background processes and ram but I have so many apps that I don't use at all. They consume big amount of ram and for instance, sometimes browser loads pages again when I get back to it from another app. I assume this is because of ram. So I guess, if I can shut down some running apps in the background, available ram would be more.
I can see them at settings-apps-running(or cached processes).
For example, right now in "running" section I have 9 processes and 3 of them are poweramp, awesome beats, accuweather.com and in "cached processes" I have 10 processes and 6 of them are beautiful widgets,calendar storage,google account manager, google search, calendar, google play store. Other processes are system services that I have no problem with. When I go to developer settings-background process limit and block them, there are no cached processes anymore but that probably has a side effect. I wish I could choose which apps I want in the background.
I can shut down these apps manually but every time I restart the phone, they are there again. How can I stop them?
Click to expand...
Click to collapse
The simple answer is that you don't need to stop them!
As you say, Android is already very good at keeping track of background processes, to the extent that if a new program needs more RAM, Android itself will kill a background process that hasn't been used for a while to free up RAM for the new program.
The Cached processes screen SHOULD be full of recently used programs; it shows that Android is doing what it is supposed to do and is shifting inactive processes out of active RAM in case you want to load it again, without completely dumping the process memory.
Now, as for the side effect you mentioned, that would be a significant hit on battery life. By holding programs in RAM as it is supposed to do, the OS can load the program quickly and cleanly and more efficiently by simply reading the RAM rather than reading flash, writing to RAM, then reading from RAM. The general mantra for UNIX based systems is that unused RAM is wasted RAM.
Another thing to note is that if you do not close tabs when switching active programs (including going to homescreen) then the Browser is designed to hold that tab in memory. Even if you close the Browser (excluding closing the tab specifically with the "little x"). Even if you reboot the damn phone, it will still load the tabs/pages you had open last. The pages are not held in memory as such, just what was open and what tab order, so if you do open the browser after a while, it will load the last page from scratch.
TL;DR version: The running and the cached processes will remain exactly where they are until a new program needs more RAM than is available, at which point Android will kill something to make room. You do not need to do this manually. It will cause more power drain by making very inefficient use of RAM/Flash memory. Empty RAM is wasted RAM.
whilst Chaos is right, I notice severe performance drops when ram is filled, despite Androids theoretical advantage. It doesnt work...
Best to prevent from loading altogheter.
Root, lose warranty, backup apps, uninstall or freeze apps so the bloatware is removed.
For others, change autostart settings in Romtoolbox. So they wont start on boot.
Search for safe stuff to delete. There are lists for that
Sent from my GT-N7000 using Tapatalk 2
Or just dont install the apps that you dont really need.
Via GtN7000
LoVeRice said:
Or just dont install the apps that you dont really need.
Via GtN7000
Click to expand...
Click to collapse
Lol, even then you might still need to remove bloatware lol
Sent from my GT-N7000 using Tapatalk 2
Thanks so much for detailed answers.