No. You are right that bindService() will keep the target service running (ONLY if you pass in the appropriate flag), but if you use startService() then the service will remain running even if nothing is bound to it.
On Mon, Apr 13, 2009 at 2:35 AM, jj <[email protected]> wrote: > > If service is running in background in another process, > independent of foreground activity process. As per my study I got the > two ways to know with background process update, > 1. using IPC(AIDL) bindService() > 2.broadcasting intent from service whenever we want update for > particular function. > > But as far as first option is concerned the foreground activity > should be there running. > My background process should run even though the fore ground activity > is no more on screen. User ca launch other application also while > running my background process. > > So only second option is remains the choice. Or there is any other > way. > Am I right about bindService() concept[that it remains only the > fore activity is there], is there any other way to keep binding with > backservice, to know update of it even though fore ground is no more > on screen. > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
