Related
I hear about people using different taskiller apps and now I have been reading that these apps are the cause of some problems and that the phone "knows" when to close apps if it needs the memory.
So what is the verdict??? Are Taskiller apps evil or necessary or do they have any value at all???
I use Taskiller. It's a great app but I have to admit, I wonder about its effectiveness. I tend to 'close all apps' if there are a lot running but I've found that this often causes more problems than it solves. As an example, I use the footprints widget on one of my screens. If I close the footprint app using Taskiller, sometimes it causes the whole touchflo process to terminate unexpectedly. I've also found problems closing processes with Taskiller which are related to the social networking/mapping features. If you know what processes to put in the 'ignore' list then fine, but closing some processes can hinder the phone's overall function.
Sometimes, however, if you want to close an app, there's no way other than to use a task killer. Take Peep for instance. No way to close it other than killing it. So yeh, task killers; generally unnecessary but sometimes handy.
Most applications do not properly handle shutting themselves down on Android. Android itself does not close many applications automatically, so a task manager is needed. How ever the automatic task managers have a tendency to kill system services as well and can cause a lot of problems on the phone.
s0v3r1gn said:
Android itself does not close many applications automatically, so a task manager is needed.
Click to expand...
Click to collapse
I guess that is ultimately the question....is it really needed???
I used taskiller in the beginning but after I stopped using it I think my phone is generally more responsive and better. Why? Because it doesn't have to start apps everytime I change screen or whatever. However I do have taskiller to kill apps that crashes or similar just in case. I do not use it frequently though. Instead I let the phone handle killing apps and whatnot.
So in my opinion taskiller is not needed because the phone takes care of everything that's needed mostly.
advanced task killer screwed up my text messages so i havent bothered with one since. luckily the device is just as as quick and responsive without it. so my vote is 'a' and 'c'
My favorite has been Advanced Task Killer Free. It doesnt cost anything and doesnt get rid of any vital processes that Android needs, especially if youre using SenseUI. Also, I have seen noticeable performance increases afterwards. So yes, I would say it is needed.
I've been using advanced task killer with problems. It seems to do what it suppose to but it also closes the radio for some reason. The rx signal comes back but the evdo doesn't unless I do a reset... I even payed for the advanced task killer thinking it would have more options but only has a hourly function.
Linux has it's own scheduler which handles tasks very efficiently.
no its not needed. i use to use advance task manager and it totally screwed and lagged my phone. not to mention i wasnt getting my sms because of those apps...i stopped using it and my phone functions great. if i feel that the phone is bunddled up with alot of apps i previously opened, i simply reset it (i hardly do resets because the phone functions excellently).
so no to task killers.
I had Taskiller installed, but after initially using it, I found that I wasn't bothered to use it, but it was still there with the icon at the top of the screen.
I read that they can actually slow your system down, so as I wasn't using it, I uninstalled it and maybe it isn't but the system does seem a little more responsive now
Vince
i used advanced taskiller and it kept my phone awake even when locked/lcd off. that murdered my battery. i uninstalled and use task manager now with no issues. it is not as simple as dragging down the notifications bar but my battery life is fine now.
I've definitely found that there is pretty much zero benefit to regularly using a task killer. Other peoples mileage will vary of course, and I'm sure there will be combinations of applications that don't sit too well together and cause issues, but I'm pretty confident than Android handles resource management well enough for most users.
I do wonder how may of those who swear by task killers are also using swapper, as I can well imagine that swapper will cause problems with Androids own resource management.
Regards,
Dave
HAHAHA guess you're not getting a clear cut verdict on task killers from this thread! seems like everyone has their own opinion....
There was an earlier debate on this topic. The thread is here... http://forum.xda-developers.com/showthread.php?t=569709&highlight=task+killer
and the android info is here (must read for understanding task killing) http://forum.xda-developers.com/showthread.php?t=569709&highlight=task+killer
They work well when set up properly. No reason to be closing widgets and programs on your sense ui that you use on a fairly often basis because it will take some time for them to load when you want to view them.
Leave the stuff you use regularly open and close the junk that takes up resources that you don't regularly use. Most of these programs have exception lists for a reason.
People that automatically end all and close sense, or their system dialer files will obviously run into problems and lag when all that stuff restarts at the same time.
Aridon said:
...Most of these programs have exception lists for a reason.
Click to expand...
Click to collapse
Exactly. They are fine if you exclude ALL the necessary components, then just have a few remaining on the main page that you know can be quit. Advanced Task Killer has been fine for me with their 'ignore list'.
i found that since ive stopped using task killer m battery life has improved quite alot
now i leave all the work to the android system
I have had the hero from day one and have had taskiller installed for about as long. I DID use it but do not now... and have no slow downs...
how?.......
custom rom....?
service which frees memory?
no...
Simply press back to exit a program and not home... if you press home the program most likley will not catch the button press and close. click back to exit and the program closes properly.
Press Back ....... this ISNT an iPhone with only 1 button.
nuff said...
I'm going without on this hard reset. On the last go around, even with disabling native sms app and using a 3rd party I was still getting the 100% awake time issue on the sprint hero.
FWIW, On a sprint hero make sure you ignore htiqagent, iqrd and omadm. Killing these will cause a radio reset, and ignore htcsense if you are using sense, which btw you can disable by removing its default setting in settings-apps-manage apps.
I think it is safe to say that I'm pretty ignorant about Android/Linux/etc. Nevertheless, I have Advanced Task Manager and I like to use it. I do use it judiciously, only ending certain programs/apps yet leaving most of that business to Android. And, of course, I use it to end the program itself.
El Mono
I was messing trying to figure out which is the correct method to close apps, back and home do the same thing, holding HOME (i just found out) brings up a list of recently used apps, but i can't figure a way to properly close them. I have Advanced Task Manager to close them now and again but I don't want to keep it running all the time.
Is there any proper way if the app doesn't provide an exit function?
Because an app is on that list does not mean it is not closed. That list is just the history of the last 6 apps you used.
A lot of people say that you do not need to worry about whether or not an app is fully closed because the software manages that to ensure that it has enough free memory. I don't know enough to know whether that is correct or not.
peterc10 said:
Because an app is on that list does not mean it is not closed. That list is just the history of the last 6 apps you used.
A lot of people say that you do not need to worry about whether or not an app is fully closed because the software manages that to ensure that it has enough free memory. I don't know enough to know whether that is correct or not.
Click to expand...
Click to collapse
Yes, sorry, the apps I'm referring to are shown by the Advanced Task Manager, I merely found the Recent list when trying to find a way to exit apps.
I sometimes have 15-20 apps in there filling up my RAM even on startup things like Shop Savy will be there twice and Photoshop.com.
They, amongst others don't seem to provide options to prevent them starting at boot so I simply uninstalled them, but all the running apps do severely affect the performance when it's filling up.
I have been experiencing the same problem.
Advanced Task Manager lists a whole load of apps that start on bootup and each one of those doesn't have an option to disable this.
After a while (about 3 hrs or so) of using my Hero I am down to about 40mb of RAM which if I don't use Advanced Task Manager to kill unused apps my Hero begins to lag big time.
On the Android it is better to leave them resident in memory than stop them, unless they are 'background' processes and there is something wrong with them (a bug) making them slow down your phone.
Don't judge your Android on amount of free memory left; if anything, the the less memory left over the better as it means the memory is being used effectively to make it nice and speedy.
Processes aren't allowed to consume CPU cycles/consume battery/slow your phone down when they are not focused; the exception is background processes which need to keep going, like the music player etc. What's more, if an app is not focused then its state is preserved allowing your phone to free up its memory when needed; its memory effectively becomes 'cache' allowing it to restart quicker if it happens to have stayed in memory.
So don't worry about wiping an app from memory; for many apps there is simply no distinction between closing it and switching away from it; as soon as you switch away from it it's as good as closed; it's not slowing your phone down or taking up any memory that couldn't be freed instantly if needed, but if it is lucky enough to stay in memory it will re-open quicker.
On my experience, if you press the back button to exit an app, then the app is closed properly, running the code in the app that will release the memory and objects. This is the best way.
The only app it will not work on is the browser as the back button will send you back through the history.
Try it...
MercuryStar said:
On the Android it is better to leave them resident in memory than stop them, unless they are 'background' processes and there is something wrong with them (a bug) making them slow down your phone.
Don't judge your Android on amount of free memory left; if anything, the the less memory left over the better as it means the memory is being used effectively to make it nice and speedy.
Processes aren't allowed to consume CPU cycles/consume battery/slow your phone down when they are not focused; the exception is background processes which need to keep going, like the music player etc. What's more, if an app is not focused then its state is preserved allowing your phone to free up its memory when needed; its memory effectively becomes 'cache' allowing it to restart quicker if it happens to have stayed in memory.
So don't worry about wiping an app from memory; for many apps there is simply no distinction between closing it and switching away from it; as soon as you switch away from it it's as good as closed; it's not slowing your phone down or taking up any memory that couldn't be freed instantly if needed, but if it is lucky enough to stay in memory it will re-open quicker.
Click to expand...
Click to collapse
I understand how and why this should be true, but for me it doesn't seem to be, if my memory falls to less than 40 the phone becomes increadibly unresponsive, I get crashes and have to wait forever for it to do things like open the phone. Immediately after killing all with advanced task manager it goes back to normal.
barryallott said:
On my experience, if you press the back button to exit an app, then the app is closed properly, running the code in the app that will release the memory and objects. This is the best way.
The only app it will not work on is the browser as the back button will send you back through the history.
Try it...
Click to expand...
Click to collapse
I have tried both methods, more often than not though, back doesn't seem to do much either, I have experimented with free RAM and using back or Home, it seems the Home certainly isn't the correct way to do it, but back doesn't work very often either, maybe people aren't coding their apps properly to respond to the back button as an exit method?
this is the never ending discussion whether task manager make sense for android or not.
i'm one of those who say: definetly YES! USE TASKMANGER.
I understand that Android works in a way that taskmanager shouldnt be needed because it handles the tasks on its own, but sadly the concept just doesn't seem to work.
When my ram fills up i can cleary see that the device is getting slower, even just opening apps takes more than 5 seconds. After closing some apps the hero is fast again.
now i don't care whether ANDROID is the reason or some POORLY programmed background apps, because the outcome for me as a user is the same. I#m using advanced task manager and im very happy with it, whenever Android starts to slow down i close the open and unneeded apps, and everything is fast again...don't know how people can claim that Android does handle task management perfectly on its own.
Shahpur.Azizpour said:
this is the never ending discussion whether task manager make sense for android or not.
i'm one of those who say: definetly YES! USE TASKMANGER.
I understand that Android works in a way that taskmanager shouldnt be needed because it handles the tasks on its own, but sadly the concept just doesn't seem to work.
When my ram fills up i can cleary see that the device is getting slower, even just opening apps takes more than 5 seconds. After closing some apps the hero is fast again.
now i don't care whether ANDROID is the reason or some POORLY programmed background apps, because the outcome for me as a user is the same. I#m using advanced task manager and im very happy with it, whenever Android starts to slow down i close the open and unneeded apps, and everything is fast again...don't know how people can claim that Android does handle task management perfectly on its own.
Click to expand...
Click to collapse
The point is, Task manager of any kind is another 3rd party app taking up more memory, and quite frankly on such a high end phone i shouldn't have to worry about this problem. I noticed another thread about changing the values at which the internal task manager kills apps etc, if it becomes more of a problem i'll look into this method of fixing it.
alias_neo said:
The point is, Task manager of any kind is another 3rd party app taking up more memory, and quite frankly on such a high end phone i shouldn't have to worry about this problem. I noticed another thread about changing the values at which the internal task manager kills apps etc, if it becomes more of a problem i'll look into this method of fixing it.
Click to expand...
Click to collapse
yes, in theory we shouldn't worry about tasks in the background, but in reality as you said, the device WILL slow down. so there is no other way around than closing apps manually and defining apps to be kept alive by the 3rd party task manager.
changing values for the internal task manager sounds like something which would only work on a rooted device, but im not sure...
Hello, all. I am currently running the free version of Advanced Task Killer, which seems to work ok, but there has to be something better. What I've noticed is, that after a reboot, the app will tell me that I have about 240 MB of available memory when all apps are closed with the exception of the task killer itself.
However, by the end of the day, after I've opened and closed a few apps, sent some messages and emails, made some calls, etc, the task manager will show significantly less available memory available. It could drop to as low as 135 MB with all apps closed with the exception of the task killer.
This leads to me to believe one of two things:
a) The Task Killer is full of it and it does not have an accurate read of how much memory is actually available.
b) The Task Killer is only able to "kill" certain tasks while others remain running in the background and it does not show that the app(s) are actually running.
Honestly, I think it is option B, because I do notice that when the app tells me that I have less than normal available memory, the phone does tend to function slower and lag a bit. Nothing that cannot be fixed by a powering it off and on, but I am hoping that someone knows of a good app (even if it is a paid app) that will actually bring up ALL tasks running and kill them. I've also noticed that even with this task killer, Google Talk (which I have never used) always remains open in my phone and I have to manually go into into the settings and turn that off.
Any suggestions?
My suggestion is to not use one.
I do use Autokiller though which tweaks the thresholds for Android's internal "task killer".
It's best to let Android do it's thing.
Tikerz said:
My suggestion is to not use one.
I do use Autokiller though which tweaks the thresholds for Android's internal "task killer".
It's best to let Android do it's thing.
Click to expand...
Click to collapse
Really? Do you mind elaborating on why you feel that way a bit so I can understand? Because I do notice that when the I am running a bunch of things at once and I use this app to kill the tasks, it does improve the performance of the phone.
I can understand why some people say you don't need one but I do think it is necessary to have it installed for when you do. I'd rather kill apps than pop the case, battery cover and battery to fix a frozen phone.
I have some GPS apps I run occasionally that after exiting them they don't turn off the GPS or lock the GPS on and drain my battery. So for those apps where the developer didn't put a close buton on the menu it helps shut them down. I don't know why Google Market doesn't require apps to have a close option.
get OS MONITOR from the market
PAPutzback said:
I don't know why Google Market doesn't require apps to have a close option.
Click to expand...
Click to collapse
Because users shouldn't have to manage their own memory. Apple folks already love laughing at us for that very reason, and even though it pains me to say it they're absolutely correct.
I can certainly buy the argument that task killers are nice for those occasions when something does go haywire and it needs to be forcibly killed, and I can understand using one just because you're curious and want to see what's running and how much memory you have, etc, but beyond that I find that they're unnecessary. My EVO runs very smoothly without me manually intervening, even after many days of uptime with many apps running.
GHOST99K said:
get OS MONITOR from the market
Click to expand...
Click to collapse
Wow! That's detailed and a lot more than I bargained for....lol. Thanks! Good thing my phone is rooted and I was able to use it since I never did the recent update to the 1.47.xx OTA update and I'm waiting for a fully functional version to be released, but there is a lot of stuff on this that goes well beyond my basic knowledge. Apparently, my phone has 89 processes running with no apps running (according to Task Killer) and only one widget running and the CPU is fluctuating at 10-40% usage.
Interestingly enough, but apps report the same amount of available memory......EXACTLY the same. So it can be assumed that both apps provide an accurate figure of available memory.
I would advise against using a Task killer. Android has its own memory management, which works extremely well on the EVO, to be honest. The latest update (1.47) feels like its makes the EVO perform much better and allows it to be more efficient.
If anything, I would suggest you read this thread about an app called Autostarts, which isn't a task killer, rather a startup manager that can be tweaked to do many different things. By not allowing certain things to start up when your phone boots, you'll have more memory to begin with and Android will be more efficient in memory management. I would try Autostarts before using a task killer.
Hope that helps.
eagle63 said:
Because users shouldn't have to manage their own memory. Apple folks already love laughing at us for that very reason, and even though it pains me to say it they're absolutely correct.
I can certainly buy the argument that task killers are nice for those occasions when something does go haywire and it needs to be forcibly killed, and I can understand using one just because you're curious and want to see what's running and how much memory you have, etc, but beyond that I find that they're unnecessary. My EVO runs very smoothly without me manually intervening, even after many days of uptime with many apps running.
Click to expand...
Click to collapse
I agree, but having to run a task killer is a small price to pay to not be part of the iPhone bandwagon crew, IMO.
Are you running a custom rom on your phone? I just have a rooted stock rom. Maybe that's why your phone can go days without the performance being affected? I still have all the bloatware on mine, and I've put off removing it because I am still a noob at this and I'm in the learning process. I wonder if the new update that was just released improves this aspect of the phone at all.....?
pseudoremora said:
I would advise against using a Task killer. Android has its own memory management, which works extremely well on the EVO, to be honest. The latest update (1.47) feels like its makes the EVO perform much better and allow it to be more efficient.
If anything, I would suggest you read this thread about an app called Autostarts, which isn't a task killer, rather a startup manager that can be tweaked to do many different things. By not allowing certain things to start up when your phone boots, you'll have more memory to begin with and Android will be more efficient in memory management. I would try Autostarts before using a task killer.
Hope that helps.
Click to expand...
Click to collapse
Thanks, I will definitely look into it. All advise is appreciated as I am very new to all of this. You answered my last question on my previous post with this, too.... I can't wait for a fully functional rooted OEM rom to be released with the goodies from the new update to try it out. I'm hesitant to update my phone now and lose superuser as I use the WiFi tether a lot.
So Samsung for whatever reason, decides it's a good idea to include an easy to access task manager with a giant "kill all tasks" button in TouchWiz. It seems like everyone I know, that has a Galaxy S II, has adopted a certain behavior due this. What they do is, every time they put their phone away, they will automatically go to this task manager and kill all tasks, before locking the phone. When I ask them why the hell they're doing that, the answer is usually something like "wasting battery blah blah blah" or "wasting CPU blah blah blah"... NO!
For starters:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
http://www.infoworld.com/t/smartphones/myth-android-devices-need-task-killers-609
http://androinica.com/2010/05/googl...-imply-task-killermanager-apps-are-pointless/
People that are doing this, educate yourself. And Samsung, well done for encouraging this.
Just because a task is in memory, doesn't mean it's doing anything, and certainly doesn't mean it's using up battery. If it's staying in memory, it's because there's no need to release it just yet. If you start it up again, it will already be there, and load up faster. The alternative is, you keep killing it, and every time you run it again, it will have to reinitialize and reload everything. Which option do you think is actually going to cost more battery?
The whole thing with people saying "oh no it's using CPU, i must kill it"... what?! If it's using CPU, it's probably doing something. Why the hell are you killing a process while it's in the middle of doing something? Do you not care about data integrity at all? It could have been in the middle of syncing, or in the middle of a write operation who knows.
If you run other applications and your memory runs low, then Android will close it. And it will close it properly, as opposed to you force killing it, denying it of any chance to clean up.
Obviously there are rare exceptions with dodgy programs. But most of the time, the tasks being killed are system apps, or trustworthy apps, properly written by Google or Samsung.
If you're not a developer, you probably won't understand the whole Android application lifecycle.
http://developer.android.com/reference/android/app/Activity.html
By force closing an application, you're not allowing it to run its onStop() and onDestroy() functions. This is where apps do all the clean up, releasing resources, unregistering things, closing connections etc.
Do you do this on your PC. Open up Windows task manager, and just kill any task that's using CPU. Or hell, just kill all tasks every 2 minutes! Good luck with that.
This has probably been said hundreds of times, but a lot of people i know are getting GSII's and I see them doing this constantly. It's stupid. Do you really think they designed the operating system so that you have to kill everything each time you touch it?
TLDR: Stop "killing all tasks" (unless theres actually something wrong) and well done Samsung for encouraging this. Just stupid.
Damn your right, I never used a task killer on previous android phones, but for some reason I have got into the habit of doing it now. So I'm going to kill that habit. Well noticed
Well according to the user guide (the full one from Samsung's website)... though personally I don't bother killing anything
Use the task manager › ›
Your device is a multitasking device. It can run more than one application at the same time. However, multitasking may cause hang-ups, freezing, memory problems, or additional power consumption. To avoid these problems, end unnecessary programs using the task manager.
1 In Idle mode, open the application list and select Task manager → Active applications.
The list of all the applications currently running on your device appears.
2 To close an application, select Exit.To close all active applications, select Exit all.
i like the placebo effect and stop telling me what i have to do or not to do!
your writing style is to aggressive, stop being aggressive!
For me, it is worth to have the clear memory option because I already faced the glitch or bugs program which cause my phone to run constantly at 1.2ghz and this will cause my phone become extremely hot. I can't see what application is running but for some reason, the cpu gone crazy. It drain battery in no time. With the simple one click button, I can closed the programs without need to restart the phone. Yes, generally I will let the android system to handle the application by itself but I still think it was a good moved by samsung to have task manager if we use it in proper way...
Sent from my GT-I9100 using XDA Premium App
Well it's not all that bad, with 2 cores one core can easily come into a deadlock and the device will continue to function albeit much slower and consuming a lot of power, when this happens in the taskmanager the processes are listed red
Thanks ever so for much for this post I have just got my first Android phone and thought by doing this it would increase the battery life a tad but did kinda think it was a bit daft having a system that required manually killing tasks. Coming from a Windows 6.1 XDA Zest I am still getting my head round an OS that's doesn't require hours on Internet to work out how to do things.
Sad, but true, I was getting onto Android from Symbian, and first thing after I realised that I do not have option of killing all apps, I have installed the task killer and kept using it for like a week, then I've read one of the articles about it, that its wrong, and that Android is not working as Symbian nor Windows, so I realised that I dont need to do that... unninstalled it and not using it at all since
You don't need Task manager / killer if only all android applications are developed by good programmers that implement Android application lifecycle properly.
The problem is not all applications are developed this way. Some application may buggy / in beta stage that still consuming processing time even they are in background.
Task manager is still useful to close nasty program manually. But I do agree, auto-kill is useless and can cause battery drain and system instability.
Yep .. it's mostly services what eats battery. And there is poor control over that. It would be interesting to see what service was active at what time, or even how much battery did it use. All battery discussions are about guessing what is running in the background and how often and how much. We should not guess such things.
As far as I'm concerned an in built task manager is just as important as an in built modem right now. There are far too many unstable applications out there that hang up and Android can never fully deal with them(despite what research may or may not have been done in the past).
I have a few games installed on my S2(namely Pool Break Pro & TNA iMPACT!) that crash quite often and require the use of the task manager to manually end those programs(they are in the task manager highlighted in red when they have stalled).
However, what I will say is that the button to clear memory in the RAM manager really shouldn't be there at all. The task manager alone is more than enough to manually exit necessary apps that crash and stay open for no reason.
I like to have the ability to close programs easily at hand. It gives me better control over "rogue" apps. I only use it for a few programs though, like the Engadget app. It seems to be poorly coded, often using 40-50% CPU when running in the background.
Sent from my GT-I9100 using XDA Premium App
I like it because it lets me close frozen apps quicker..
the_Calen said:
i like the placebo effect and stop telling me what i have to do or not to do!
your writing style is to aggressive, stop being aggressive!
Click to expand...
Click to collapse
Lol yes. Not to be taken too seriously.
Force closing apps with the task manager when somethings wrong with the phone or closing broken apps makes sense. I'm just talking about people that instinctively press the close all apps button every time they use the phone for a second. It's just silly. Basically doing what those automatic task killing apps do.
I use to kill opera everytime i'm done with browsing because even in idle mode the phone gets very hot when opera runs in the backgtound. But after these explanstions i stop force killing every app
Sent from my GT-I9100 using Tapatalk
If a program is badly written and won't stay idle, then kill it.
I am very selective about what I install, and never kill or need to kill anything.
You have 1 GB of ram on this phone. If you want best battery and speed, don't kill anything. loading a running app from ram uses less power than starting from scratch and booting it from nand, then starting it up.
So if apps are well written, don't kill them. If stuff stays around causing drain, kill it individually but find a better app
This thread is spot on... for the most part. Like Pulser said, there are apps when idling/cached, cause detrimental effects like the one I detailed here causing your phone to stay Awake constantly and draining battery:
http://forum.xda-developers.com/showthread.php?t=1094666
ATK isn't the most elegant method, but it allows you to put everything else on ignore and have it actively kill the apps that love to stay cached and cause issues even after you've exited out of them.
Is there a way to "lock" some apps into a memory so they never quit by the android OS except if I would decide to?
Sent from my GT-I9100 using Tapatalk
You have a valid point, but most of the time those apps don't do anything critical that it would hurt to interrupt. I usually prefer to exit them normally, but sometimes I just kill it, like when I forgot the Messages / Internet open. No need to paranoia though, leaving a few open won't kill your battery.
PINki92 said:
Is there a way to "lock" some apps into a memory so they never quit by the android OS except if I would decide to?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
That's exactly what I needed. There are some apps, like SetCPU, TB, Root Explorer, which can be added to SuperUser authorization and it won't get killed by anything unless someone manually kills it. I'd really really like to know how to add an app under SuperUser or anything which will do the job to add the app in to the OS and which can't be killed by any Task Killer or anything.
Besides I also hate those Task Killer apps, they are meaningless unless an user do nothing regularly with his/her phone.
I've no Task Killer installed but once I used the built in Memory Clear feature and next day my schedule app got closed. From then I never touched it. But one thing if RAM usage goes above 400 MB I think sometime its good to clear the memory as it will help to refresh it. But Samsung should had put the Memory Clear feature more precisely.
Regards.
Sent from GT-I9100
When I updated to Marshmallow I was very disappointed to see their task/memory manager had been dumb down just to take the average memory use of apps. Instead of several versions before showing the running apps in live time.
With that now missing are there any good apps to use with or without root with a good task mananger? Preferably one without a bunch of other junk like clean master and the other apps like that. The one I've found that's the best so far is Task Manager by Hard Infinity.
Thanks in advance!
I should have added a poll from the beginning since I was looking for what most people were using and some possible suggestions. So I have added a poll in hopes to get some responses. Everyone of us has the occasion when an app goes rogue screwing things up, or sucks battery juice to no end, or just freezes up, so it just needs to be shut down. I would love to hear what everyone is using.
NOTICE: I do not condone killing tasks/processes just simply to 'free up' memory. That is the Android System's job, let it do its job.
Check out developer options then Running Services (6th from the top) to see actual live memory usage instead of the averages.
I personally have enjoyed a 'clear all' option in App switching mode from my days of my S4. I use gravity box now and integrated it in my navigation bar to clear and also indicate how much ram is free.
Lastly if you're having issues with any apps stuttering it can help to experiment with background process limit also in developer options, I believe it resets that setting after a restart though.
Hope that helps.
Didn't know about the dev options. The default task manager is really disappointing, couldn't figure out why my RAM was always at 80%. I figure that's no issue, but I like to be aware. Really miss the battery life in my Xperia Z3 and was hoping this would compare with the large battery and doze, but couldn't find the background processes that could be possibly draining my battery.