On Wed, Nov 18, 2009 at 8:27 AM, jotobjects jotobje...@gmail.com wrote:
Don't you care just as much about Activities that have threads running
the background?
No, the system can freely kill those processes when it needs memory. Thus
this isn't the cause of the main problem, the overall
On Wed, Nov 18, 2009 at 12:18 PM, jotobjects jotobje...@gmail.com wrote:
If the system is slow due to CPU contention then an Activity running
in the background would also be part of the problem. If the system is
low on memory the System can also kill Services. But I get it that
too many
2009/11/18 Cédric Berger cedric.berge...@gmail.com
So now that (I think) I understand what this force stop is really
about (completely and definitely stopping an app) :
Are there situations where it is done by the system (automatically) ?
(ie. in case it is too low on memory).
Nope,
On Wed, Nov 18, 2009 at 22:45, Dianne Hackborn hack...@android.com wrote:
2009/11/18 Cédric Berger cedric.berge...@gmail.com
Are there situations where it is done by the system (automatically) ?
(ie. in case it is too low on memory).
Nope, definitely never ever. The user must explicitly
That's not the purpose of this API, which is to allow the user to force stop
an application right now, immediately, I don't care what the damn app wants.
:}
There is a UI in 2.0 for the user to explicitly stop any currently running
services.
On Tue, Nov 17, 2009 at 5:15 AM, Bo
On Tue, Nov 17, 2009 at 11:36 AM, jotobjects jotobje...@gmail.com wrote:
On Oct 15, 3:07 pm, Dianne Hackborn hack...@android.com wrote:
What these programs are doing is using the API that is tended to force
stop
-everything- about the application: stop all services, cancel all alarms,
On Tue, Nov 17, 2009 at 11:41 AM, jotobjects jotobje...@gmail.com wrote:
Use Jason's solution. Also if the system kills the Process the
system will later restart the Process if it had a Service running but
it is up to the service to reset its own state.
Not when using this API, which kills
On Fri, Oct 16, 2009 at 00:07, Dianne Hackborn hack...@android.com wrote:
If you kill the process, it will not impact the alarms, the same as it won't
impact notifications etc.
What these programs are doing is using the API that is tended to force stop
-everything- about the application: stop
2.0 includes a UI showing you which -services- are running and the resources
they are using. This is what you really care about, not whatever random
processes are being kept around by the system in case it needs them later.
(Fwiw, the worst that can happen is a bad app sits there spinning the CPU
In fact if you can have more control in 2.0, this will just help to not have
all this task killers used so blindlessly by everyone.
So removing this API will be become less important. And this one still may
be usefull in some cases. Just have to be used more wisely.
thanks dianne for the
2009/11/17 Cédric Berger cedric.berge...@gmail.com
In fact if you can have more control in 2.0, this will just help to not
have all this task killers used so blindlessly by everyone.
Unfortunately I think that is unlikely -- I can't count the number of places
I have seen on the web suggesting
11 matches
Mail list logo
