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 would be available for incoming calls which would make the whole thing a lot easier. (and I wouldn't have to missuse the service in that way)
Regards! On 12 Dez., 00:45, Jean-Baptiste Queru <[email protected]> wrote: > 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 <[email protected]> wrote: > > > 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 > > Notification...though I'm not sure if that will survive the service > > closing down. > > > 2. You can't even be assured onDestroy() is called -- the process might > > just be terminated outright in extreme cases. > > > -- > > Mark Murphy (a Commons Guy) > >http://commonsware.com > > _The Busy Coder's Guide to Android Development_ Version 1.9 Published! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
