You can not rely on a service staying alive 100% of the time, because
the system reserves the right to kill the processes that host services
in order to make space for the visible activity.
JBQ
On Thu, Dec 11, 2008 at 3:21 PM, code_android_festival_way
festival.s...@googlemail.com wrote:
At
Ok so all I can do is set some last Toast in the onDestroy message in
order to notify the user of the killed service right?
On 12 Dez., 00:29, Jean-Baptiste Queru j...@google.com wrote:
You can not rely on a service staying alive 100% of the time, because
the system reserves the right to kill
code_android_festival_way wrote:
Ok so all I can do is set some last Toast in the onDestroy message in
order to notify the user of the killed service right?
1. I don't think services can raise Toasts, if they don't happen to be
called on the UI thread. You should be able to post a
In fact when the system (kernel) decides to kill a service to make
space, the service *is* killed outright, no onDestroy().
JBQ
On Thu, Dec 11, 2008 at 3:44 PM, Mark Murphy mmur...@commonsware.com wrote:
code_android_festival_way wrote:
Ok so all I can do is set some last Toast in the
Thank you for your answers. I meant the notification not the Toast
sorry for that. It is not nice to hear all that but ok I have to live
with that. (the users have to live with that because they don't
understand why the service can't be available all the time :) ) It
would be nice if a broadcast
5 matches
Mail list logo
