Please keep in mind, if you don't use startForeground(), your service is not critical, and its process *will* get killed occasionally in the background. Depending on how you have coded the service (what you return from onStartCommand()) it will or will not be restarted after its process is killed. (And you won't see onDestroy() called in this case.)
This is true on every version of the platform. How likely you are to see it has varied between versions of the platform, varies between devices depending on how much memory they have, and varies between users depending on how much they have running. On Fri, Jan 7, 2011 at 4:54 PM, Jake Basile <[email protected]> wrote: > I have considered it, but it's not really what I'm looking for so I didn't > try it. This service shouldn't be in the foreground, and the exact same code > didn't need to be to work in previous versions. I don't think the service is > getting killed because my onDestroy is not called and the service still > shows up in the app manager. > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
