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 <[email protected]> wrote: > 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 > > <[email protected]> wrote: > > > At the moment I'm facing kind of a big problem. I am using a service > > to listen with the TelephonyManager for incoming calls in order to do > > something according to the incoming call. To be able to do this I have > > to rely on my running service. It is just sitting in the background > > doing nothing. I know that the right behaviour for this situation > > would be a BroadcastReceiver registered in the Manifest. But there is > > no brodcast sent for incoming calls. So I can't walk this way. > > > Is there a possibility to keep my service reliable alive? At the > > moment I'm just starting the service from my UI with "startService > > (..)". Later on I'm binding to my service. Most of the time the > > service is running fine in the background but in some rare situations > > the service gets killed by the system and is kept killed untill I > > restart it from my UI. > > > Could someone tell me what to do in this case? > > > I'm looking forward reading your answers. > > > Regards! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
