Yea, Android wants to be the killer of processes. I believe the thinking is that it is better to leave one running incase the user wants to come back. So when user presses home key the app is just suspended but not killed, unless OS needs its resorces. That's why they relaunch so quickly.
On Sep 18, 8:36 pm, Mark Murphy <[email protected]> wrote: > sdphil wrote: > > i have an app with multiple activities and a local service. > > > if I finish() all the activites and stop the service, the process > > still exists (if I go into adb shell and type ps, I still see it). > > Correct. > > > is there a way to make sure the process is killed when I "quit"? > > Your job is not to kill the process. Android will terminate the process > when it wishes. It may elect to keep a process around for recycling > purposes. > > You *do* need to make sure *you* are not causing the process to stick > around, such as leaving a thread running, or having registered a > listener with Android that you didn't release (e.g., a PhoneStateListener). > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 1.0 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
