mjc147 wrote: > This is probably relevant for nearly all type of music player-like > apps because they need some kind of UI to get started but still need > to continue playing once that UI has been exited.
And that's a fine reason for having a service. However, it's a rare music player that is designed for multiple front-ends, so a local service would be much simpler. > Is there a way around this? When you say "implicitly" are you > implying that the opposite is true when "explicitly" starting a > service? If your service is started via bindService(), it will be stopped sometime after the last client unbinds. If your service is started via startService(), it will run into somebody tells it to stop (stopService(), stopSelf(), Android terminating the process, gravity and a concrete floor negatively impacting the device). If you wish to use AIDL, but still want the service to run even after unbinding, use both startService() and bindService(). -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 0.9 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
