Yah exactly...I was monitoring the service for overnight but unfortunately when the service was killed and subject for restart only the onCreate was called...onStart wasn't called. I'm using IntentService by the way. I was expecting the onHandleIntent() to be called right after onStart() but as I have said onStart() wasn't called after onCreate().
Anyone having the same issue? Thanks, Brian --- On Mon, 3/8/10, kostmo <kos...@gmail.com> wrote: From: kostmo <kos...@gmail.com> Subject: [android-developers] "Scheduling restart of crashed service", but no call to onStart() follows To: "Android Developers" <android-developers@googlegroups.com> Date: Monday, March 8, 2010, 7:30 AM In the 1.6 API, is there a way to ensure that the onStart() method of a Service is called after the service is killed due to memory pressure? -- 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 -- 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
