Artem - WorkSmart Labs wrote: > Everything works well, > except many users have a habit of checking what's running right after > starting the phone, and they complain about our application running in > the background "all the time".
How are they determining this? Android 2.0 has a new Settings page or something to list services, and I haven't tried a BOOT_COMPLETED-and-done service to see how long the service shows up. > I completely understand the Android > policy of not discarding the applications until the memory is needed, > but in a case like this, when no user interaction is involved and > there is no reason to believe that the user will start our app soon, > is there any way to cause our process to exit instantly right after > completing the execution of the receiver? I am looking for something > like Process.destroy(), or some equivalent. You can try System.exit() and see what that does, but there could be side-effects of not letting Android do its normal thing on shutdown. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training -- 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
