That is working as intended. The process is kept around with nothing running in it if there is enough memory, to reduce the work if it is needed again in the future.
On Fri, Jan 7, 2011 at 11:59 AM, Moto <[email protected]> wrote: > Currently I believe I'm doing a ok job managing my application's remote > service. When I'm done using it I can see the onDestroy() called, perfect... > > Now the issue is I can see the remote process still hanging around, via > DDMS or via phone's running processes. Users see this and think I'm doing > stuff on the background etc... blaming my app and than asking for an exit > button... Truth is they don't need an exit button! > > So my question: > > How to gracefully terminate a remote service process? > > I could get the PID and kill it but something tells me this might not be > the nice way to do this since the service might be restarted again... > > Any help would be greatly apreciated! > > -Moto > > -- > 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
