Related
Has anyone seen any benefits in using task killers or managers on the Evo? Has it helped or made battery life worse ? Do we even need them with the Evo ?
in my experience the phone runs smoother if you keep running tasks to a minimum. i have an app called ES Task Manager and it comes with a widget that has one touch kill all. i hit that and turn off the screen when i'm not going to be messing with the phone for awhile.
I used to use Advanced Task Killer (ATK) and loved it until one day my phone would not work whatsoever. It kept force closing HTC Sense and I had to do a hard reset last week. It was very upsetting and the sprint technician said the task killer was to blame.
I agree. I switched from Advanced Task Killer to ES and it's great. Really helps out battery and smoothness. I can get about 12-16 hours per charge when doing that with normal use.
What's ES?
Sent from my PC36100 using XDA App
I use Damage Control 3.2.2.1 with its built in killer set at 150 MB with Advanced Settings Part 2 Laptop_OOM activated and JIT. Banned everything except Facebook.
Then I use autostarts to stop programs from starting up at boot, speeding up boot time and using less power.
Credits go to TheBiles.
I can usually get about a day and a half of regular use before I reach 10%.
Best tip? Don't use any task killers..
At most use autostarts and thats it.
b1indsided said:
What's ES?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have become an believer in task killers - I use ES ( search market for: estrongs )
Increased battery life and smoothness, just make sure to not have it kill the HTC processes and you'll be good
b1indsided said:
What's ES?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Estrongs task manager
Task killers are a bad idea on Android. It's best to just let the OS do its own memory management. The only reason to use a task killer is as a last resort for a rogue app or something like that.
There's a thread about this around here with a detailed explanation as to why this is true and how memory management works in Android. I can't copy and paste because I'm sending this from my phone. And I'm lazy.
Autokiller and autostarts are probably the only two apps that make sense to use and this is to enhance management, not override the built in management like task killers do.
Sent from my HERO200 using XDA App
Ugh this is why I hate the debate.
Some people say use it... some people say Android's memory management is fine.
My ATK usage is simple. I close programs that I do not use and won't start any FC's.
So basically after I'm done playing a game, I use ATK to close out of it.
I leave most things open unless it's like Sprint Zone or something.
I decided to be less lazy for once.
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Sent from my HERO200 using XDA App
simply put, if you have any linux experience you'll realize why task killers aren't neccessary like in a windows mobile platform device.
I use ATK. As far as battery life, I haven't seen an increase or decrease, but the phone runs smoother and sometimes an app gets stuck, so I kill that sob off.
Use Autostarts only. It is a permission manager--not a task-killer.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
mgraham361 said:
I decided to be less lazy for once.
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
That article is bogus. If you analyze the evidence and the conclusion presented there, it's a non sequitur.
Your mom is a non-sequitur.
That article is a total sequitur xD
You need to be more explicit.
Sent from my Evo 4G
I tried ATK since the BB Mobile guys were pushing hard for you to install it before you even left the store with the phone. I gave ATK an honest try, and experimented with most of the settings. At the end of the test, I found that ATK didn't really help me. That being said, my battery life is much better now since I moved for the rooted stock image to Fresh 0.3.
myersn024 said:
I tried ATK since the BB Mobile guys were pushing hard for you to install it before you even left the store with the phone. I gave ATK an honest try, and experimented with most of the settings. At the end of the test, I found that ATK didn't really help me. That being said, my battery life is much better now since I moved for the rooted stock image to Fresh 0.3.
Click to expand...
Click to collapse
Heh, BB Mobile reps always act like they're experts. These guys know less than the average XDA forum reader. They'll have you think otherwise though!
As much as I disliked the idea of not managing my own processes, be it by manually killing them or with some automatic thresholds, after some reading, I decided to let Android handle things as it was designed to do.
To satisfy my itch for being "in control", I downloaded (from the market, for free) an app called MinFreeManager, which allows for you to tweak the parameters for Android's memory management. I also read a suggestion from Flipz to use AutoStarts to better control what apps are starting, and when. AutoStarts basically lists events within Android and allows you to toggle if an app should run or not.
That said, I've noticed my Evo has been very smooth and responsive. I periodically open TaskKiller to see how much available memory there is and to be nosy. The truth is that apps do clean up and are disposed of properly by Android. Give it a shot for a few days. What's the harm?
So ever since i did the OTA 2.2 it keeps running more apps in the background. I have my ATK set up "Crazy" and shut apps down when screen is off. But i cant keep it above 180ish. Is there something im missing??
Yeah, task managers don't work in Froyo! Lol! Little known fact. Basically, the Android team got tired of the abuse of task killers and made them defunct. They'll stop processes, but they just restart. You never needed one, and with Froyo, it has better memory management and other things that completely negate any benefit task killers might have brought. To stop a malfunctioning app, use the built in task manager. Settings>Applications>Manage Applications and go to the running apps tab. Select the app you want to manage and hit Force Stop.
Sent from my PC36100 using XDA App
Wish it would just fully stop. Well Im gonna do it (root) when someine has it available for 2.2
I uses taj killers and noticed some slowing now that I have gotten rid of the task killer I have had better battery life and better speeds. Just let Android manage your apps and quit closing apps that don't need to be closed. Closing an app through a task killer will do some damage just like you should not force close an app on a computer unless it locks up on you.
Sent from my EVO using XDA App
you can run a task preventer (I like "autostarts") to keep those apps from even starting in the first place.
Also if you want to have the system kill tasks more aggressively you can scale up the lowmemkiller. You can do this manually by echoing whatever values you want to the lowmemkiller file (more on that if you want to know) or there are apps that will do it for you. I don't know which on the market will do it, I run damagecontrol and DConfig has a lowmemkiller adjustment
Okay, so I hear in FroYo that you're not suppose to kill and end tasks? Does that means services as well? And if I wasn't suppose to kill them, then wouldn't that make my battery life worse because of all the things running in the background?
TIA
Sent from my Epic 4G
You shouldn't use a task killer in any version of android from Froyo on, froyo handles its memory management extremely well when left alone, using a task killer could result in apps constantly opening and closing in the back ground, which would use a lot of battery .
Texted while driving
Alright. I got rid of my task killers. Is ending services fine though? And what about the task manager that the phone provides? (I'm guessing the second one is a no?)
And what other precautions should I take for battery (other than having low brightness, of course)
Sent from my Epic 4G
Only use the one built into the touchwiz framework if you have an app running out of control hogging resources.
If you're looking to improve battery, I strongly suggest Juicedefender with ultimatejuice, I have almost tripled my battery since I started using them.
Texted while driving
063_XOBX said:
Only use the one built into the touchwiz framework if you have an app running out of control hogging resources.
If you're looking to improve battery, I strongly suggest Juicedefender with ultimatejuice, I have almost tripled my battery since I started using them.
Texted while driving
Click to expand...
Click to collapse
Thanks. Just got both. What do you reccomend I put the aggressiveness on?
Sent from my Epic 4G
I keep it on custom and 15 minutes every 2 hours.
Texted while driving
063_XOBX said:
I keep it on custom and 15 minutes every 2 hours.
Texted while driving
Click to expand...
Click to collapse
Wait, I'm a bit confused. What do you mean 15 min every 2 hours? Like I can only put my frequency to 15 min OR 2 hours? Sorry if I seem stupid lol
Sent from my Epic 4G
Data on for 15 minutes every 2 hours.
Texted while driving
063_XOBX said:
Data on for 15 minutes every 2 hours.
Texted while driving
Click to expand...
Click to collapse
I figured it out
Thanks for everything.
Sent from my Epic 4G
I use the Advanced Task Killer for Froyo. Several apps I have like the Weather Channel and stock browser lower my available memory to a minute amount of what it was at boot up and do not reload if killed.
BONSAI 4 and loving it!
kennyglass123 said:
I use the Advanced Task Killer for Froyo. Several apps I have like the Weather Channel and stock browser lower my available memory to a minute amount of what it was at boot up and do not reload if killed.
BONSAI 4 and loving it!
Click to expand...
Click to collapse
The amount of memory available on your phone is supposed to become low. Apps are stored in memory when not being used. This does not take battery and allows the program to start in a faster fashion then otherwise.
Sent from my Incredible using Tapatalk
I'm sorry guys, but the information given in response here is really dangerous. Yes Froyo, and all versions of Android have built in memory management. HOWEVER, it is the job of the application developer to use the proper calls and closes to make sure the application isn't holding onto resources when in a background state. This is NOT always the case, and is constantly overlooked on all OS platforms, especially with how fast application development is happening on mobile platforms.
YMMV, when and if you should be using task killers.
linuxmotion said:
The amount of memory available on your phone is supposed to become low. Apps are stored in memory when not being used. This does not take battery and allows the program to start in a faster fashion then otherwise.
Sent from my Incredible using Tapatalk
Click to expand...
Click to collapse
No it's not. There is only 337MB of RAM available of which about 150 is used by system. If I keep loading apps that stay in memory when not being used I will have no resources or memory available for additional web pages or other apps. Why should the Weather Channel app load 50 MB of memory and stay there if I use it twice a week? When an app is closed I want it out of RAM. I can wait the 50 milliseconds to reload if I want to use it again.
BONSAI 4 and loving it!
Here we go again another argument of task manager for android
For me i use advanced task manager to kill some apps to speed up my phone a little and also use it to switch between programs that are already open where as if you try reopening some programs the restart,
I also ignore apps that i need to open and stay open like beuatiful widgets, word games to get more reliable notifications and widget locker.
I freeze with titanium some services such as drm and sns...
Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
mattallica76 said:
Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
Click to expand...
Click to collapse
I like to save some for a rainy day
mattallica76 said:
Free RAM is wasted RAM. Unless your trying to track down rogue processes, task killers are totally unnecessary.
http://lifehacker.com/#!5650894/and...ed-what-they-do-and-why-you-shouldnt-use-them
Click to expand...
Click to collapse
What that article hints at but doesn't exactly explain is that due to how the Dalvik JIT works, killing those apps that aren't actively consuming CPU will cause worse performance over the long run. The JIT has to spin up everytime the app is loaded - if it is already in memory then it's already optomized.
At least that's my understanding! I could be totally talking out my arse
EDIT:
Here is its straight from the Dalvik lead dev.
Well don't know about performance but yesterday killing apps with ATK Froyo especially the browser, I came home with 62% battery left. Today had about the same use but disabled ATK and never used it and came home with 31% battery left. ATK is doing something for my battery and will give up apps loading quickly for battery life any day.
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).
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