Closed GoogleCodeExporter closed 9 years ago
This is a common mistake of many users with android system... Using a auto-task
killer app or an app that monitor other apps is not always a good idea.
Ok for some apps that's are not well coded, yes it's needed. But if the app
behaves cleanly, it can be still in the task list but consume absolutely
nothing.
Android system automatically handle what apps should be open and closed.
If you configure csipsimple to run only with wifi *for outgoing call* for
example and you quit it with the quit button :
You'll see in your task manager that csipsimple is still running, but in fact
it's just a ghost process that does nothing and that is left running by android
because it doesn't take any resources and it can save time to reload it later.
I advise you to read this article :
http://blog.radioactiveyak.com/2010/05/when-to-include-exit-button-in-android.ht
ml That explain some things.
Auto-task killers apps should be used with a big knowledge of what they do (and
sometimes also with the knowledge of how application you kill works).
I don't know if you already noticed but some android native application such as
voice recognition, keyboard etc etc restarts automatically. Killing them with a
task killer (or auto task killer) has the exact opposite effect that the effect
you want. Loading an app drain the battery. Keeping it freezed in some memory
place if memory is useless for the system save cpu time.
Once this is said, I admit that there is still work to do in csipsimple to
fulfill the requirements for an app with a good behavior regarding resource
management. But... but... the fact it will remains in a task manager is not the
proof that it behaves as it should. Even better, some apps (such as csipsimple
that should be aware of network changes), should appear in the task manager.
By the way you can read my code, you'll see that everything is released if not
needed and that the only thing that remains is a ghost maintained by the
android system.
I spent a lot of time on this issue and previously I though just like you that
it was not normal that the app remains active in the task killer. But after a
lot of research and tests, and android code reading, I know now that this is
normal and you should not be afraid of the fact the process appear in your task
killer.
And last point, this behavior depends on the device : with device with lower
cpu/ram csipsimple is well properly ended by the android system.
Original comment by r3gis...@gmail.com
on 3 Aug 2010 at 12:02
If some task app can convince you, install astro file manager, the embed task
manager application made the distinction between Applications and Services.
You'll see that when not needed (and for now ended with the quit button)
csipsimple will not appear in the Service tab when not needed. Only in the
application tab and besides no cpu is requested, which mean it's just some data
that remains in ram and are not freed by the android system. If you open a lot
of other app so that android will request ram, csipsimple will just disappear
from the list of applications.
Original comment by r3gis...@gmail.com
on 3 Aug 2010 at 12:30
Just a last one... just seen on twitter :
http://www.reddit.com/r/Android/comments/cwhm6/i_stopped_using_a_task_killer_las
t_week_to_see_if/
Even more significant that I though... using a task killer drain the battery by
25% according to this user.
Original comment by r3gis...@gmail.com
on 3 Aug 2010 at 8:08
Original issue reported on code.google.com by
cedricli...@gmail.com
on 3 Aug 2010 at 10:44