So i saw many posts on which people have asked as to which task killer should be used !
and then i stumble upon this site which provided me the details,
*I HAVE NOT WRITTEN THIS*
sources-by Chris Hoffman
http://www.howtogeek.com/127388/htg-explains-why-you-shouldnt-use-a-task-killer-on-android/
Android Doesn’t Manage Processes Like Windows
Most Android users are familiar with Windows. On Windows, many programs running at one time – whether they’re windows on your desktop or applications in your system tray – can decrease your computer’s performance. Closing applications when you’re not using them can help speed up your Windows computer.
However, Android isn’t Windows and doesn’t manage processes like Windows does. Unlike on Windows, where there’s an obvious way to close applications, there’s no obvious way to “close” an Android application. This is by design and isn’t a problem. When you leave an Android app, going back to your home screen or switching to another app, the app stays “running” in the background. In most cases, the app will be paused in the background, taking up no CPU or network resources. Some apps will continue using CPU and network resources in the background, of course – for example, music players, file-downloading programs, or apps that sync in the background.
When you go back to an app you were recently using, Android “unpauses” that app and you resume where you left off. This is fast because the app is still stored in your RAM and ready to be used again.
Why Task Killers Are Bad
Proponents of task killers notice that Android is using a lot of RAM – in fact, Android stores a lot of apps in its memory, filling up the RAM! However, that isn’t a bad thing. Apps stored in your RAM can be quickly switched to without Android having to load them from its slower storage.
In summary, you shouldn’t use a task killer – if you have a misbehaving app wasting resources in the background, you should identify it and uninstall it. But don’t just remove apps from your phone or tablet’s RAM – that doesn’t help speed anything up.
Empty RAM is useless. Full RAM is RAM that is being put to good use for caching apps. If Android needs more memory, it will force-quit an app that you haven’t used in a while – this all happens automatically, without installing any task killers.
Task killers think they know better than Android. They run in the background, automatically quitting apps and removing them from Android’s memory. They may also allow you to force-quit apps on your own, but you shouldn’t have to do this.
Task killers aren’t just useless – they can reduce performance. If a task killer removes an app from your RAM and you open that app again, the app will be slower to load as Android is forced to load it from your device’s storage. This will also use more battery power than if you just left the app in your RAM in the first place. Some apps will automatically restart after the task killer quits them, using more CPU and battery resources.
Whether RAM is empty or full, it takes the same amount of battery power – decreasing the amount of apps stored in RAM won’t improve your battery power or offer more CPU cycles.
hope u understood!
words of wisdom by fellow-mates
go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
I understand this response, but I don't believe it. Task killers has always helped me in every matter. Even on a computer it helps greatly.
Conclusion: I noticed the same battery life using a Task Killer, than not using a task killer.
Sent from my HTC One V using Tapatalk 2
Curiousn00b said:
I understand this response, but I don't believe it. Task killers has always helped me in every matter. Even on a computer it helps greatly.
Conclusion: I noticed the same battery life using a Task Killer, than not using a task killer.
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
you don't have to believe it. those are real facts. go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
salve.
1ceb0x said:
you don't have to believe it. those are real facts. go into settings - apps and see how many running apps you have. now go to cached apps and see there, how many apps there are. you see? nearly 50% of those apps discovered by you in the processes are apps that you didn't opened ever but they are still opened and running. why? because that's how linux manages its resources. instead of having free ram for no use (what's the point of having 14gb of ram when you only use 1gb), linux fills all the ram blocks with useful apps or apps that you are running frequently so that when you call that app, it will bring it on the screen almost instantly. this my friend, is called multitasking.
and no, you are wrong. if you use a task killer killing the apps every 10 minutes, the cycles the whole system does - opening again apps and caching them, task killer closing them - results in much more functions done by CPU => more battery spent. even if you say that the battery life its the same, you are wrong. when using a task killer IT MIGHT drain your battery with 0.1% per hour. it's not that much, but IT EXIST.
oh and yeah, one thing: android has its own task killer. that's why you don't need one app to kill your other apps. because android its doing it by itself. if you don't believe me, strip down one kernel, open the init.rc file and find the values for task killer.
salve.
Click to expand...
Click to collapse
I hope u don't mind if I take some of ur message and put it in the op
Sent from my One V using xda app-developers app
That's great.. I liked the article. I qm giving you a thanks for it
Sent from my One V using xda app-developers app
cybervibin said:
I hope u don't mind if I take some of ur message and put it in the op
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
sure. no problem mate
soham_sss said:
That's great.. I liked the article. I qm giving you a thanks for it
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Thank you
1ceb0x said:
sure. no problem mate
Click to expand...
Click to collapse
Sent from my One V using xda app-developers app
task killers were great before 1.6 but useless after that
Lloir said:
task killers were great before 1.6 but useless after that
Click to expand...
Click to collapse
+1 android has devloped a long way since!
cybervibin said:
Thank you
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
you're welcome!
I'm using task menager when is needed, and also I'm using custom system memory tweaks, it makes my phone running faster and smoother some apps knows to stuck and they keep the phone from entering deep sleep, and that drains the battery, so if you know what are you doing use task menager and customize when what apps the system should kill
Sent from my HTC One V
I have a task killer installed, but only use it manually, ie. if there's a stubborn app that's crashed/frozen/etc and just won't close and is eating the battery
donJim said:
I'm using task menager when is needed, and also I'm using custom system memory tweaks, it makes my phone running faster and smoother some apps knows to stuck and they keep the phone from entering deep sleep, and that drains the battery, so if you know what are you doing use task menager and customize when what apps the system should kill
Sent from my HTC One V
Click to expand...
Click to collapse
Use auto run manager the answer to most of ur problems
qzfive said:
I have a task killer installed, but only use it manually, ie. if there's a stubborn app that's crashed/frozen/etc and just won't close and is eating the battery
Click to expand...
Click to collapse
Sent from my One V using xda app-developers app
yayyy so task killer only kills my battery
you got that right!
Good to know. Thanks
Related
I think many of us are using some kind of task killer. BUT, I find task killer sometimes cause more problem than it solves. And sometimes it doesnt really increase free RAM.
What I did was create a simple app to force Android memory manager to free RAM (by unloading tasks based on its own logic). This way you eliminate 3rd party task killer wrongful termination of tasks such as those active ones required by widgets etc.
This app just basically starts and creates a huge heap (forcing Android to free RAM) and then closes.
(You may still see this task linger in memory after you run it, but it will be unloaded the next time you start other app. You will see your free RAM increased a lot)
====Edit
You May not see free RAM increase immediately after running. You will see RAM increase a lot a bit later after you have started other app (which forces BfreeMem to be unloaded from memory)
Tip: Just put a shortcut on desktop. Click it when your RAM is low (<50-60Mb) and it will do its job. Dont run it when your free RAM is above 90Mb.
I'm trying it
Sent from my GT-I9000 using XDA App
This app should be tested by more Samsung Galaxy S owners to see if is working as it should be or not.
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
cosmoboi said:
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
mib1800 already had got ur all private data, no more diffs.
cosmoboi said:
Try already.... No diff.... What's the difference?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You have to wait for BfreeMem to be unloaded. (If you are impatient use a Task killer to unload it and you see it frees up lots of RAM.
Basically BFreeMem is a very bloated. When it starts it force Android memory manager to unload other tasks to cater to its RAM requirement. After that if you start other app, Android mem mgr will unload Bfreemem thus freeing huge chunks.
I tweak it to works best if your free RAM is around 50-60Mb. When I run it and when BfreeMem is unloaded later, free RAM goes up to about 100Mb.
btw: this app requires no permission so your data is safe
AutoKiller is a much better alternative.
The concept sounds correct. Not entire sure if it will work in practice.
psychedelic'd said:
AutoKiller is a much better alternative.
Click to expand...
Click to collapse
My purpose is to have something that does not circumvent Android memory manager which keeps track of tasks and their stats. It knows better what tasks are best to kill based on their usage/last access/active state/priority. Furthermore, if Android memory manager kill a task due to low memory, it will save the state for that task so that the next time that task is used the saved state is restored.
3rd party task killers sometimes mess this up by killing tasks which are actively use (resulting in those tasks being restarted just after being killed leading to wasted power and more lag) or killing dependent tasks such as those used by widgets without saved state causing widgets to malfunction.
snapper.fishes said:
The concept sounds correct. Not entire sure if it will work in practice.
Click to expand...
Click to collapse
I am using it. It does free up RAM. Is it useful? Depends. If you have lots of active apps (widgets/service etc), those freed RAM is filled up soon as Android restore back those "killed" tasks. Not much gain here. On the other hand, if you have lots of zombie apps lingering in memory then yes. The extra RAM does give a boost to the next app you open
AutoKiller is less of a task killer and more of a memory manager. Sort of like what your app is trying to do, but much better. More information: http://andrs.w3pla.net/autokiller/details
Your concept is good, but having an app that continually increases ram usage will waste battery. Then having to kill that app manually in order to free up ram is tedious. Just my 2 cents.
The new task manager in Touchwiz has a function to manually clear ram any way, which works great.
psychedelic'd said:
AutoKiller is less of a task killer and more of a memory manager. Sort of like what your app is trying to do, but much better. More information: http://andrs.w3pla.net/autokiller/details
Your concept is good, but having an app that continually increases ram usage will waste battery. Then having to kill that app manually in order to free up ram is tedious. Just my 2 cents.
The new task manager in Touchwiz has a function to manually clear ram any way, which works great.
Click to expand...
Click to collapse
OK. AutoKiller is changing Linux configuration. Unfortunately, it needs root.
I have used the TouchWiz TaskMgr clean Ram at safe level - it still messed up my widgets (Beautiful widgets, weather & toggle)
Bfreemem app does not continually run or increase RAM usage. You just run it when the free RAM is low (or close to threshold). At this low RAM level it just knocks other tasks out of RAM. btw: You should NOT run it when you have huge amount of free RAM. You should run it when RAM is low like <50Mb.
You dont really have to kill Bfreemem task manually since it will be quickly unloaded by the Android memory manager when RAM is required since its state is finished.
JUst put a shortcut on the desktop and click it when you feel RAM level is low and it will do its job.
Can it be used with autokiller?
It could be also automated to check if memory is low, and automatically kill applications. Battery drain would be present in that case tho..
Never has the default task killer from samsung messed up my widgets including Beautiful weather, I tried using task killer and never saw the benefits of it since andriod automatically keeps 40MB of free ram...
EarlZ said:
Never has the default task killer from samsung messed up my widgets including Beautiful weather, I tried using task killer and never saw the benefits of it since andriod automatically keeps 40MB of free ram...
Click to expand...
Click to collapse
When I try the option Level 1 - Clear Memory (in Samsung task killer), my beautiful widget clock stop working.
Soniboy84 said:
Can it be used with autokiller?
It could be also automated to check if memory is low, and automatically kill applications. Battery drain would be present in that case tho..
Click to expand...
Click to collapse
Personally, I dont use task killer. Not sure whether Autokiller kills tasks physically or just adjust some running config. Just have a feeling task killers (those that kill tasks physically) cause RAM leak. For example when my phone reboot, I can see at least 12 tasks (in Advanced Task Killer) and free RAM is about 95Mb. If I physically kill those tasks, my RAM may temporarily goes up to 130Mb but sometime later free RAM drops to 50-60Mb and there were no more tasks to kill.
When I use Bfreemem, my free RAM fluctuates betw. 60-100 Mb and I can still see all/most of those tasks that were there just after boot-up.
If you have one of those scheduler/timer app, you can just use those to schedule Bfreemem to run regularly. (I can build another timer app to schedule)
Been using Quick System Info PRO for the past few days, and am truly impressed! Multi-functional as a task manager to close / ignore running apps...cache cleaner keeps system from bogging down. Process tracking / cpu usage tracking. Tons of system specs available to view, etc. Uninstall apps directly from this as well. Find out exactly what apps start on boot up, and trim as you see fit.
I know memory is at a premium for us Archos IT users...I encourage you to check this app out. It's a little more complicated than your standard task killer, but truly helps trim things down. Best of all, it's free! Option to donate to disable ads, I donated just cuz the dev blew me away with this app!!
Enjoy, and please offer up your own opinions!
How do u change what programs run on startup? I downloaded it and its good but I don't see that feature.
Task killers (apparently) shouldn't be used on Android (generally... there are always exceptions)
If an Android app is created properly, it shouldn't be eating away at the RAM, and Android will free up what it needs.
If it killed everything, then the multitasking feature will be as useless as Apple's
I won't explain further, I'll just link Lifehacker instead:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Please note: Although I don't use task killers my self, I don't disagree with them. I'm just putting this out there so you can make your own minds up
thefunkaygibbon said:
Task killers (apparently) shouldn't be used on Android (generally... there are always exceptions)
If an Android app is created properly, it shouldn't be eating away at the RAM, and Android will free up what it needs.
If it killed everything, then the multitasking feature will be as useless as Apple's
I won't explain further, I'll just link Lifehacker instead:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Please note: Although I don't use task killers my self, I don't disagree with them. I'm just putting this out there so you can make your own minds up
Click to expand...
Click to collapse
While I certainly agree with this...do you own an Archos? Task Killer is almost necessary for the Archos 70it. Until they increase memory allocations, the need to minimize what's running at startup or any given time is absolutely needed.
Bandage said:
While I certainly agree with this...do you own an Archos? Task Killer is almost necessary for the Archos 70it. Until they increase memory allocations, the need to minimize what's running at startup or any given time is absolutely needed.
Click to expand...
Click to collapse
I agree but I still can't figure out how to configure the startup. Can you let me know how?
Bandage said:
While I certainly agree with this...do you own an Archos? Task Killer is almost necessary for the Archos 70it. Until they increase memory allocations, the need to minimize what's running at startup or any given time is absolutely needed.
Click to expand...
Click to collapse
I disagree. They are not needed. I don't use one on my 101.
blazingwolf said:
I disagree. They are not needed. I don't use one on my 101.
Click to expand...
Click to collapse
So what are you using your tablet for? Reading ebooks? If you have more than 1 user process running at a time, in addition to system processes it gets bogged down. Android is great at multitasking...256k RAM is not. I have my 70 trimmed down to skinny, having removed some bloatware apps. Normal is around 55-60% of RAM usage during standby.
If I decide to break out a game, like Dungeon Hunter or another system hog...I run into occassional FC's if I haven't freed up some RAM. A TASK MANAGER helps me select the things I want to shut down to free that RAM for an app / process that I choose to run. Stop confusing TASK KILLER with TASK MANAGER. (Was a typo in my response earlier) Yes the app allows me to kill tasks, the difference is...I'm killing what I CHOOSE to kill.
PS - I haven't done much to alter start up apps thru this Manager, just have used it to trim fat and gain control of my RAM usage.
Bandage said:
So what are you using your tablet for? Reading ebooks? If you have more than 1 user process running at a time, in addition to system processes it gets bogged down. Android is great at multitasking...256k RAM is not. I have my 70 trimmed down to skinny, having removed some bloatware apps. Normal is around 55-60% of RAM usage during standby.
If I decide to break out a game, like Dungeon Hunter or another system hog...I run into occassional FC's if I haven't freed up some RAM. A TASK MANAGER helps me select the things I want to shut down to free that RAM for an app / process that I choose to run. Stop confusing TASK KILLER with TASK MANAGER. (Was a typo in my response earlier) Yes the app allows me to kill tasks, the difference is...I'm killing what I CHOOSE to kill.
PS - I haven't done much to alter start up apps thru this Manager, just have used it to trim fat and gain control of my RAM usage.
Click to expand...
Click to collapse
Play games, read books, video, music, etc. Just about anything you can do with it.
I also used to have a task killer and decided to install Watchdog which works in a different way. Works a lot better that all the rest of the task killers I have used and did not have any issues. Apps run smooth even if I have more than one running.
thanks
i use this apk
Bandage said:
Been using Quick System Info PRO for the past few days, and am truly impressed! Multi-functional as a task manager to close / ignore running apps...cache cleaner keeps system from bogging down. Process tracking / cpu usage tracking. Tons of system specs available to view, etc. Uninstall apps directly from this as well. Find out exactly what apps start on boot up, and trim as you see fit.
I know memory is at a premium for us Archos IT users...I encourage you to check this app out. It's a little more complicated than your standard task killer, but truly helps trim things down. Best of all, it's free! Option to donate to disable ads, I donated just cuz the dev blew me away with this app!!
Enjoy, and please offer up your own opinions!
Click to expand...
Click to collapse
There is a YouTube video showing why not to use a taskiller, and how much lag there is when you kill all the apps, let them cache in the OS and its faster, don't be afraid of having low memory, this was done on the 70 tab 8 gig, sorry for no link, its one of the top ones.
Sent from my PC36100 using XDA App
I am using advanced task killer to manage process. But some process can not be killed. Are these processes not killed or just respawned quickly. How to really kill them. Thanks.
Sent from my Desire HD using XDA App
yeah i wonder how to remove/uninstall apps such as stocks which i do not even touch at all.
The best method is to uninstall your task killer. They are junk and will only slow your phone down. Every time you kill those process, they have to restart which uses more cpu and battery than just leaving them in memory in the first place.
Please google about android task managers and you will find some good explanations as to why you shouldn't use them.
Sent from my super slick Android device.
iroquois said:
yeah i wonder how to remove/uninstall apps such as stocks which i do not even touch at all.
Click to expand...
Click to collapse
You need root and some form of s-off. Then you can either delete with root explorer, titanium backup, out adb.
Sent from my super slick Android device.
Like dr.m0x said, those task killers and other optimizer are the worst thing out there on the market.
Android handles these things just fine. If your RAM gets low it will kill tasks on its own. And if your RAM isn't low - then why kill tasks? Free RAM doesn't help at all.
Also background apps almost never use battery/CPU power. If you don't believe it check the battery usage history. And most background tasks have a CPU usage of a couple of seconds.
About removing stock apps, a nice and clean way is to use ROM Cleaner (download in the dev section). It removes apps from the ROM before you flash it.
Thanks, I think I got what I want
Sent from my Desire HD using XDA App
Can anyone explain the amount of RAM that this phone is suppose to have?
The specs for the phone lists 768 MB. However, the total memory that comes up is 617940 kB.
Thanks.
Bull Shot said:
Can anyone explain the amount of RAM that this phone is suppose to have?
The specs for the phone lists 768 MB. However, the total memory that comes up is 617940 kB.
Thanks.
Click to expand...
Click to collapse
where are you finding this number? i am at 758 MB. since i have a bunch of apps installed, that would seem about right.
How are you guys getting so much free ram? When I check on Task Killer, whenever I kill all the apps I'm not using it usually shows 358 mb ... and programs I'm not using automatically keep running (i.e Maps).
hmm maybe im not checking the right place? i'm getting my 758 mb number from settings--SD and phone storage. the internal phone storage tells me 758mb.
on an unrelated note though, you shouldn't use task killers. they are considered by most to be more of a drain on your battery life as android is already setup to manage closing unused apps on its own.
Many people use the term "memory" to mean system memory as well as storage. I try to avoid calling system storage as "memory" and tend to use "storage" instead, or refer to the type of storage.
Total ram is around 768mb. Part of it is reserved (not sure why, possibly for filesystem caching) so around 603mb is available. For this platform that is a healthy chunk of RAM to work with. Even with my hefty usage I have ~126mb free.
Internal storage is something like 2gb, with it partially consumed by the Android install as well as NAND configuration adjustments for reliability which cause some of the storage space to be consumed through hardware (there's an excellent explanation of this somewhere, don't have a link handy), resulting in about 1.1gb being available. I have 103 apps installed, 523.5mb of the internal storage used, with 638.8mb available.
There was an excellent tool posted on xda (http://forum.xda-developers.com/showthread.php?t=1066060) called Android Optimizer that gives a lot of good information about memory, storage, cpu usage, etc. I'd recommend checking it out. It's not available on the market and it is a little buggy so use it with a bit of caution if you choose to use any of the optimization functions.
cool. thanks for the explanation nimdae!
There have been so, so, so many posts on this topic that I will not rehash them all here. Instead, I will ask a simple question: For what do you use all that free RAM?
Ask yourself that question, and be serious about it. I think you will find yourself uninstalling your task managers and memory optimizers before long.
Edit: to avoid unnecessary discussion, Watchdog is in fact neither of those, and I would highly recommend it as the only memory app you will ever need.
Edit 2: the total RAM displayed is the RAM that is actually available to be used by anything the user may want to run. As a poster earlier said, the system reserves a certain amount of RAM for its own use to keep important processes moving along. The reserved RAM is not available, and so doesn't appear in total RAM. Unless you want to uninstall the OS. Then you could have access to all 768 MBs.
I would like to reiterate why you should not use automatic task killers.
As of, I believe, Android 2.0, the garbage collection and memory management was significantly improved. However, this was not a new system in Android, it always existed.
How it works:
If you haven't noticed with Android, when you leave an app, it doesn't close it unless the app specifically does something to end the process. This is by design. Android allows the app to remain in memory. Frequently used apps will load faster with this design. A "task" that is not killed and is in the background ONLY consumes memory, it does not "run" (in Linux terms, the process is actually in a "stopped" state so the task can't do anything anyway). Only a "service" can run in the background. Most apps that have long running services have lightweight services.
If an application loads that requires more memory than is available, Android will examine backgrounded tasks for candidates to be killed to free up memory. This makes it so as many tasks as possible can remain in memory for better performance. In understanding this, you should know that if you have a large amount of memory, and memory usage is high, this is a GOOD THING. With the amount of memory in the I2, there is a lot of breathing space for this.
There is one other case where a backgrounded task will be killed: if it has been in the background for a certain period of time without being brought forward. Killing a task to free up memory to load another task can actually be a little cpu expensive (but not THAT much) so this can make it slightly easier.
Please note that backgrounded tasks WILL NOT contribute to battery drain. Only tasks at the front and services will. Killing your backgrounded calculator will do nothing for you other than free that small amount of memory it uses. Used memory does not contribute to extra battery drain as DRAM refreshes happen on ALL cells anyway.
Background services can also be made candidates for being killed. If an app needs more memory than can be made available by killing backgrounded tasks, then services become targets to be killed as well.
Automatic task killers cause a couple of problems. A less major problem is you lose that one benefit you get by keeping tasks in the background: performance. I don't just mean how fast it loads. If it can bring a backgrounded task to the front from memory rather than load from storage, you remove extra processing to load the app, including storage access, that contribute to higher battery drain. The other problem is a poorly configured task killer can break things like notifications.
Managing your services is always a good idea. Having a lot of services running means background processes that are capable of contributing to battery drain. Additionally, there are apps with misbehaving services (services that consume resources or use features they shouldn't). While I'm against automatic task killers, using something to monitor and manage services is a good idea. Just always keep in mind the implications for killing a service: it may affect a feature to an app that you would rather not impact.
Excellent explanation nimdae! Task killers are the devil.
On another note, my posts are getting too long...
nimdae said:
On another note, my posts are getting too long...
Click to expand...
Click to collapse
Everything is longer in Texas.
xgunther said:
Everything is longer in Texas.
Click to expand...
Click to collapse
That's what s...no, that's too easy.
Move along, nothing to see.
Before I read this I was like a task Nazi. I killed my tasks often, but now I think I will just let them be. Nice write up BTW. Very informative.
Sent from my ADR6350 using XDA App
TB13 said:
Before I read this I was like a task Nazi. I killed my tasks often, but now I think I will just let them be. Nice write up BTW. Very informative.
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
Remember: I'm not saying don't manage things. Poorly behaving services are the #1 cause of high battery drain (at least on non-LTE devices), and this will be even more problematic when you overclock.
xgunther said:
Excellent explanation nimdae! Task killers are the devil.
Click to expand...
Click to collapse
I tried not using them and I get better battery life with them...I use it maybe 3 times a day after heavy multi tasking. It's to each their own..but I see results for it..like 5 extra hours.
Sent from my ADR6350 using XDA Premium App
knipp21 said:
I tried not using them and I get better battery life with them...I use it maybe 3 times a day after heavy multi tasking. It's to each their own..but I see results for it..like 5 extra hours.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
If you get that much extra, you have a misbehaving app. Better to get the app developer to fix it or find an alternative.
nimdae said:
If you get that much extra, you have a misbehaving app. Better to get the app developer to fix it or find an alternative.
Click to expand...
Click to collapse
True, I don't need to use it often though lol
Sent from my ADR6350 using XDA Premium App
I'm in Texas as well.
sent from a phone without root.
I use a task killer only to manually kill an app that freezes or something. Its easier than going to manage applications. I have the autokill disabled.
Sent from my ADR6350 using XDA Premium App
AngelsPunishment said:
I use a task killer only to manually kill an app that freezes or something. Its easier than going to manage applications. I have the autokill disabled.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
CyanogenMod (maybe other ROMs) have a feature to kill a frozen app by holding the back button (long press, whatever). However, this can also be an annoyance on systems where for unknown reasons it registers a long press on a tap (my eris did this a lot).
I use system panel lite to the what processes are running and how much memory is being used how can I manage this properly so I can save on resources. my phone seems like it is using a lot of memory and cpu as well
I tried system auditor and I don't think that works well at all
I use OS Monitor to monitor processes and memory usage and I use Autorun Manager to control what apps allowed to run at startup and run by itself (enable/disable recievers).
I don't use any task management app. Android OS automagically do it for you.
For more information about task management on Andoid, I recomend you to read this article:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Hope it helps.
I use Android System Info (prev used it on the N1).
Has tabs for system, tasks and apps as well as 'overall'
and tracks memory and cpu%.
buzzcomp said:
I use OS Monitor to monitor processes and memory usage and I use Autorun Manager to control what apps allowed to run at startup and run by itself (enable/disable recievers).
I don't use any task management app. Android OS automagically do it for you.
Click to expand...
Click to collapse
This. Unless you have a poorly coded app, I wouldn't even worry about it. I haven't used a task manager since my G1 days.
Unused ram is wasted ram. There is absolutely NO NEED to manage memory in android yourself, and you end up wasting battery/time/effort trying to so.
Tl;dr, android caches more recently used apps in memory, and clears memory when needed. Don't manage it yourself.
Sent from my Galaxy Nexus using Tapatalk 2
In addition to what the guys above me said, you should look at what apps are always running in the background and pay attention to the permissions apps ask for before downloading them. Many apps will rerun themselves right after being closed by task managers making it a vicious circle of death for your battery.
I use system panel paid version with monitoring enabled to keep my processes in check. System panel is by far the best method on android. I just check the history over the last 2 hours, or I check it in the morning to see what it tracked all night while idle, and its by far the most accurate and most complete picture you can get to see what an android phone is doing.
dmuhamma said:
In addition to what the guys above me said, you should look at what apps are always running in the background and pay attention to the permissions apps ask for before downloading them. Many apps will rerun themselves right after being closed by task managers making it a vicious circle of death for your battery.
Click to expand...
Click to collapse
Any app that starts with priority 300 is a service and will just start back up when killed. I like to look at processes with memory usage app by twistbyte. With this you can see all apps running and what priority they are running under. Know that any app running in 300 will use battery in background.
Sent from my Galaxy Nexus using Tapatalk 2