Root [Boost Mobile] The Advantages Of Advanced Task Killer

[dollardagreat]

ATK is a very important app for all android devices from the Nexus to the Replenish. Android cuts on apps whenever it wants to. When too many apps is running at the same time, the phone freezes and reboots itself, many people have this issue with many android devices. Not just the warp. What drains ur battery is wifi, interactive widgets, apps that sync like facebook, twitter, etc.... what drains ur phone the most is app being on and never getting shut off....

ATK shut off programs soon as u done with it so the next app could feel flawless. So ur video to play and not buffer on occasions. So Angry Birds could feel like Angry Birds on the Iphone. So ur Facebook app could show up quicker. So ur battery wont drain. I use the widget daily and its on my rom Essentials.Sensation for a reason. The phone comes with a task killer for a reason.

Cut off auto start and show notification and just use the widget. The phone will be flawless.

https://play.google.com/store/apps/details?id=com.rechild.advancedtaskkiller&hl=en

U could complain and blame the phone company or people roms, or think u have a mess up battery, or phone, or u could maintain a phone to make it flawless with ATK.

What this ( Android Task Killers Explained: What They Do and Why You Shouldn't Use Them )article tells u is to drain ur phone ram and burn up ur battery but it dont explain how to keep ur phone in gud health. Which ATK will do.....

Hope this help Warpers And All Android Users.....

Sometimes people say when they downloaded it they started to notice more fc's and this because u have too many programs running at the same time on the phone then it can handle and while ATK is trying to kill them, the phone get confuse and fc. Maintaining the right apps is a must for ur phone. Many apps hang in the back and stay on like facebook even tho u turn sync off, even maps does it, ATK helps big.....

 

[xBabyfaceKingx]

Actually having a task killer is what drains your battery even more because the app is constantly killing apps which puts more work on the CPU. Other apps that are running in the background are doing just that, running in the background. They're not really doing anything but sitting there giving you quicker access to it when you want to use it later which takes a little less stress off the CPU thus increasing battery life. In my experience, task killers drain the battery the most. I could only get about 7 hours of battery life with moderate usage with a task killer. Best battery saver for me was uninstalling the task killer and now I can go a full day and a half without having to recharge.

 

[mercury0x000d]

In my experience, it depends on what task killer you're using. Personally, ATK was the only one that seemed to do its job well. Some others I tried did in fact drain more battery than they saved. On my phone, I set ATK to kill almost everything when the screen powers down, so that going into standby there's not a lot of extra fluff running. And you do have to be careful what you have it kill; killing important tasks could be the reason for the extra force closes that some people experience, although Android usually just re-launches that task if it's something it needs.

 

[StarScream2109]

Yes but as soon as it closes those apps they just reopen the system does it itself instead of spending more juice on doing it over and over

 

[dollardagreat]

ATK cut off programs that is running and I manually does it, not ATK. Some programs built into the rom have to keep running, that why android cut them back on. Also some apps use maps or if u have gps or locations on then maps will never turn off and burn a lot of battery.

ATK cant drain energy because its only a few kb's, that as simple as i could put it, but to put it into details, if u running the facebook app which takes 7 to 9 mb's of ram, or phandroid which takes 11 mb's of ram, or a clock/weather widget that takes 7 mb's of ram AT THE SAME TIME, YOU YOURSELF IS HARMING THE PHONE. Interactive widgets harm ur phone and takes ur ram, I use only stable widgets like power control, music and calendar pad. Ram is what makes ur phone function well, without free ram, ur phone is nothing just like a computer. It sound cool to go right back to ur app where u left off but u hurting ur phone, that all u doing. It takes less energy to restart the app then to keep on the app just to come back where u left off and now u mad ur battery dead or ur phone freezing up and rebooting, don't make no since but this what people choose.

Yes but as soon as it closes those apps they just reopen the system does it itself instead of spending more juice on doing it over and over

 

[xBabyfaceKingx]

ATK cut off programs that is running and I manually does it, not ATK. Some programs built into the rom have to keep running, that why android cut them back on. Also some apps use maps or if u have gps or locations on then maps will never turn off and burn a lot of battery.

ATK cant drain energy because its only a few kb's, that as simple as i could put it, but to put it into details, if u running the facebook app which takes 7 to 9 mb's of ram, or phandroid which takes 11 mb's of ram, or a clock/weather widget that takes 7 mb's of ram AT THE SAME TIME, YOU YOURSELF IS HARMING THE PHONE. Interactive widgets harm ur phone and takes ur ram, I use only stable widgets like power control, music and calendar pad. Ram is what makes ur phone function well, without free ram, ur phone is nothing just like a computer. It sound cool to go right back to ur app where u left off but u hurting ur phone, that all u doing.It takes less energy to restart the app then to keep on the app just to come back where u left off and now u mad ur battery dead or ur phone freezing up and rebooting, don't make no since but this what people choose.

I have to disagree with this. RAM (Random Access Memory) is a piece of hardware that gives the CPU quick and easy access to an application when needed. If you close an app completely, then you are taking that app off of the RAM which is making the CPU do more work once you want to reopen it. Android utilizes RAM differently than a computer so having your RAM mostly used up is not a bad thing (this is not harming the phone), it's actually a good thing. When your RAM is running really low then the Android OS automatically knocks low priority apps off of the RAM so really there is no need for a task killer app imo.

 

[dollardagreat]

No offense, but that sound dum, ram is ram and use the same way, android dont use it no differently, u pay for more ram for a faster phone. All androids have ram spec and that will tell u how fast it will process, if u manage ur ram u maintain ur phone but u smarter then the android developers that place task killer as a stock on most there phones and tablets...

I have to disagree with this. RAM (Random Access Memory) is a piece of hardware that gives the CPU quick and easy access to an application when needed. If you close an app completely, then you are taking that app off of the RAM which is making the CPU do more work once you want to reopen it. Android utilizes RAM differently than a computer so having your RAM mostly used up is not a bad thing (this is not harming the phone), it's actually a good thing. When your RAM is running really low then the Android OS automatically knocks low priority apps off of the RAM so really there is no need for a task killer app imo.

 

[xBabyfaceKingx]

No offense, but that sound dum, ram is ram and use the same way, android dont use it no differently, u pay for more ram for a faster phone. All androids have ram spec and that will tell u how fast it will process, if u manage ur ram u maintain ur phone but u smarter then the android developers that place task killer as a stock on most there phones and tablets...

It may sound dumb to you but it makes sense to me and I'm sure many others will agree as well. Just do a little googling. Android is made for multi-tasking and if your constantly killing off apps then your not really multi-tasking. Maybe in the older days of Android a task killer was almost certainly needed, but that was back when phones were not equipped with a lot of RAM. Newer phones that are coming out have more than enough RAM and CPU power to achieve most multi-tasking processes for example, our wonderful ZTE Warp. There may be ways that a task killer may be useful for certain situations, but it is certainly not needed to maintain a healthy phone.

On a side note, I have never seen a new phone out of the box have a task killer installed.

 

[Deleted User]

The warp did

 

[Rachel A]

My understanding (rudimentary granted) was that KillBackgroundProcesses forces apps to close and pretty shortly afterwards restart.

I'm confused by this though because there was a Restart call in Eclair that was deprecated in FroYo and replaced with the above call. Not really sure of the difference though. Perhaps we can get a knowledgeable dev in here to chime in...

 

[xBabyfaceKingx]

The warp did

Did?
What happened to it?

 

[StarScream2109]

Theres a task manager not a task killer like atk

 

[Deleted User]

It was called task manager. Maybe I'm wrong, but I swear I remember it lol, might have been cm7 lol

 

[dollardagreat]

Its call task manager and it kills app like ATK but to each is own.....

 

[StarScream2109]

Task manager allows you to kill one as you need game freeze wont respond well close it do it again atk just kills everything

 

[jetx2x]

It may sound dumb to you but it makes sense to me and I'm sure many others will agree as well. Just do a little googling. Android is made for multi-tasking and if your constantly killing off apps then your not really multi-tasking. Maybe in the older days of Android a task killer was almost certainly needed, but that was back when phones were not equipped with a lot of RAM. Newer phones that are coming out have more than enough RAM and CPU power to achieve most multi-tasking processes for example, our wonderful ZTE Warp. There may be ways that a task killer may be useful for certain situations, but it is certainly not needed to maintain a healthy phone.

On a side note, I have never seen a new phone out of the box have a task killer installed.

Totally agree... back in the day running the android system was a strain for the phones... but now we have QUADcore phones with up to 2gbs of ram... (a Japanese variant of the GSIII) that's more ram and CPU power than on some computers and definately more than mine... and even though our warps are about 2 generations behind now... it still is capable of running smoothly at all times of the day... or at least mine is... when I first got this phone and didn't know any better I used every app killer and battery saver available and was plagued with problems... but now that I've gotten in the habit of manually closing apps that I know hog memory or cause lag while in the background... my phone is smooth as butter.. with much better battery life

Sent from my N860 using Tapatalk 2 Beta-5

 

[Deleted User]

Same here, except I use a swap partition. I used to have freezing and reboot when the memory got to low. And I would reboot it once or twice a day just to clear the crap out. Now I can go days, then I ending up testing something.

 

[EarlyMon]

Using a task killer is simply the wrong thing to do.

I develop Android apps so I though I'd explain why a task killer isn't needed on an Android system.

Activities
Android apps use activites to preform tasks. For example, if you use a file manager to send a picture via email, the file manager calls the send activity within an email app, passes the file name to it and the email app sends the picture.. not the file manager. This will result in seeing the email app as "running" even though the user didn't actually launch that email app.

Smaller apps
Using activites helps developers design smaller apps. A file manager app that contains every bit of code needed to do everything a file manager does would likely be so large that no one would want to install it. Developers know that an android phone more than likely has an email app so there is no need for the developer to include email code in his/her file manager to send a picture when he/she can call an activity in an existing email app to do the job. This results in a smaller file manager app since there is no need to include email code or any other code for an activity that can be done via an app that is already present on the phone. This also alleviates redundant code. When you install an app outside of the android market, also known as sideloading, the file manager app calls the package installer (already present in Android) to install the requested app.

Running apps vs. cached apps
The "Manage Applications" list included in many android devices lists running apps as well as cached apps. Cached apps don't use any CPU or battery, they're cached so they will load faster the next time you need them. Killing cached apps results in those apps requiring more time to load the next time they are launched.

System management
By default, every android application runs in its own Linux process. Android starts the process when any of the application

 

[KOLIO]

Using a task killer is simply the wrong thing to do.




See also -

http://android-developers.blogspot.com/2010/04/multitasking-android-way.html

If there is any confusion on this, I'll be happy to answer questions.

Meanwhile, remember - task killing is like a drug - the more you do it, the more you need to it, and you may feel good at first, but it's quite harmful.

Friends don't let friends use task killers.

Well said! This explanation should be stickied in every forum.

 

[UnknownUser1]

Using a task killer is simply the wrong thing to do.




See also -

http://android-developers.blogspot.com/2010/04/multitasking-android-way.html

If there is any confusion on this, I'll be happy to answer questions.

Meanwhile, remember - task killing is like a drug - the more you do it, the more you need to it, and you may feel good at first, but it's quite harmful.

Friends don't let friends use task killers.

I only semi agree i use bomb that task set to kill on screen lock and its only helped my bat but it has a safe mode and some apps do reopen themselves but take minimal ram but i would definatly say it has actualy caused more good than harm as long as you dont take ot overboard like takin it outa safe mode. I find it helps cuz it closes a task when im done with it and all i have to do is hit the lock button. Amd its a small dl (less than 1 mb) which is a good thing when it comes to a task killer cuz why use a task killer to free up a few mb if it takes up the space it frees

 

[mercury0x000d]

Task manager allows you to kill one as you need game freeze wont respond well close it do it again atk just kills everything

ATK actually only kills what you tell it to. And in recent versions, what you tell it to can't include system apps, which are listed in green in ATK's list. These you must kill manually if you want them dead.

I see the point of those claiming that killing tasks is bad, and Android does in fact kill what is necessary when more ram is needed, however going as far as saying it will actually hurt your hardware is a little overboard.

As far as ATK killing battery life, yes this is correct... if you have it set to kill things constantly, or like every 5 minutes or whatever. I leave mine set to only kill on screen timeout, thereby eliminating the vicious cycle of ATK kill/Android relaunch/ATK kill, etc., etc., etc.

 

[EarlyMon]

Android = Linux OS + Dalvik Virtual Machine + apps that run in the Dalvik and use Linux services

The idea that Android uses ram differently than a computer isn't so. Your phone is a computer. It's not Windows, it's unix running a stack engine.


Task killers have a nasty habit of killing the apk, and turning the attached threads in the Linux services into zombies. (an actual, not made-up term)

If you believe that a task killer is good for you, great, but please don't spread the myth that they are a good thing, and don't use one without first checking all of your options and understanding what you are signing up for.

The last thing 99.99% of Android users need is a task killer.

 

[StarScream2109]

Agreed Earlymon

 

[Prinny]

Zombies, huh? I had no idea that the extend of a task killer went that far to turn my phone into something that will eat my brain...

Oh, wrong zombies?


Right. My bad. So THESE zombies are the type that cannot be killed, and if I'm not mistaken, needs to recieve a wait () command to show that the system no longer needs it. Correct? If I'm wrong about that, could you further elaborate for me, EarlyMon? I'm just a little curious about that.

 

[EarlyMon]

In unix, the ultimate low-level kill command is "kill -9 [process_id]" - it will unconditionally obliterate anything.

Zombies won't even respond to that - being threads that are no longer alive but can't be killed, they acquired that name _years_ ago.

If you do it right, you can place a "kill -9" (like how that's close to Plan 9 From Outer Space? unix is humorous) and kill off an entire process and all of its parts.

But - you can't kill apks quite so easily that way because they're running in a virtual environment and that environment controls the connection.

The app kill found under settings, Apps does it the right way.

I've seen ads for killers that claim to do it the right way - I have not personally checked them all - but the few that I did check were not truthful.

In some communities, devs have found valid ways to have idle processes closed down whenever the screen goes off by initiating a low-level task for that part of system management at boot-up.

So - it can be done and maybe the previous poster who's killing on screen off and reporting good results has found the magic app that finally gets that right.

What I tend to recommend is a thorough look at all of your apps with *wakelock* permission given - that's what will kill your battery and performance when the screen is off, but your phone isn't sleeping properly.

Here's my phone - it sleeps correctly when the screen is off -



Note that it wakes up long enough to satisfy syncing things that I'm ok with - such as email - and then goes back to sleep.

(2000 mAh battery, 10 hours on battery, lost 40% of battery with 4 hours of screen on time - not too shabby, and no task killer)

So - how do you find out what's keeping things awake and what the real battery hogs are? I use the GSam battery monitor, it's free and does the job - hopefully, it's Warp-compatible. It's just a monitor, so it can't hurt to try it and see.

Another alternative to task killers are apps like Juice Defender - use it to set schedules and events so that you can automagically control turning your data feeds on/off by changing radios on/off and sync on/off.

Ok, that's enough for now - hope this helps.