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.onUpdate(), can I start a local service and leave it > hanging there until my widgets are disabled? If I didn't explicitly > stop that service will it be loaded again and resumed when the device > wakes up.
Oh, please don't. There should be no need to keep a service in memory just to maintain some state. Since the app widget itself does not reside in your process, the widget framework allows you to keep your widget up to date without consuming much memory. Just persist whatever state you want to a file, SharedPreferences, database, etc. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Need help for your Android OSS project? http://wiki.andmob.org/hado --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
