[android-developers] Re: Can I keep a broadcast receiver process alive by creating a service that stays around?

Satya Komatineni wrote: > However if you want the widget to be a window to what a service does, > can one of the buttons on a widget start the service, stop the > service, and also collect some stats from the servcie. > > In such a case can the widget provider and the service stay in the apk > fi

[android-developers] Re: Can I keep a broadcast receiver process alive by creating a service that stays around?

Mark, thanks for the response. You are right if the state can be kept in a persistent store, it is the way to go. However if you want the widget to be a window to what a service does, can one of the buttons on a widget start the service, stop the service, and also collect some stats from the s

[android-developers] Re: Can I keep a broadcast receiver process alive by creating a service that stays around?

Satya Komatineni wrote: > The app widget documentation indicates that the "widget provider" > being a receiver of a broadcast service may not exist (the process) > beyond the completion of the call. > > If I want to maintain state between two broadcast events, such as say > widgetProvider.onUpdat