I suppose you could try having a parent service that only has the job of keeping your other service alive. Essentially it could be crash proof if you made it simple enough. I'm not sure but I think services and activities can execute code when they're paused or closed. Hopefully when something crashes onDestroy() still gets called. You could write your main service to send an intent to the parent service to get restarted.
Take all this with a grain of salt. My advice is just a shot in the dark. On Oct 31, 11:07 pm, Anders Feder <anders.feder...@gmail.com> wrote: > Hello, > > I am developing a slightly "mission critical" Android application, and want > a Service component of it to be essentially "immortal" or at least > "self-restarting" in the event of a crash (of the service). What would be > the best way to accomplish this? I use API level 3 (Android 1.5). > > Thanks in advance, > Anders Feder -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
