Unfortunately, poor application implementation by some developers has
made Task Killers a necessity.
I would hazard that between 10-20% of the apps that I have downloaded
contiue to consume CPU cycles in the background for hours after I have
stopped using the app.
There are a bunch of apps on my phone (some of them embedded in the
system by a carrier) that needs to be smacked on a regular basis.
Ones installed by my don't stay resident for very long - uninstalled.
BUt I hate getting my battery drained by an app that I though I had
stopped hours before.
On Oct 8, 7:10 am, "{ Devdroid }" <webnet.andr...@gmail.com> wrote:
> On 7 October 2010 20:15, Nathan <critter...@crittermap.com> wrote:
>
> > I'm straying a bit, but what problems do you generally get from task
> > killers?
>
> The major proble is most people does not need any as they got no bloody
> idea about android application lifecycle. They believe all tasks they
> got listed are running tasks. Majority of users do not know what they do
> by installing task killer and what are the options they configure if they
> do. They blindly follow silly belief task killes (pardon, The Task Killers)
> are remedy to any problems apps or OS or whatever may have. They
> auto-kill services and can probably do other problematic things.
>
> > What's been the usual signs?
>
> If your user reports something odd, you may try the blind shot:
> "tried disabling your task killer yet?"
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
