In my experience this is normally the result of bad application architecture, which is not as easy to put right as it sounds.
>>if an app has a function that allows users to set an alarm that shall be >>triggered when a condition is met at some unknown time in the future, like >>nearing a particular place, then obviously a Service or other background >>function needs to be kept running that monitors whether the condition is >>met.<< Not true. The app should register a PendingIntent with the AlarmManager and then stop self. Generally you should only need a continual running background service if you are doing a long network poll (instant messaging, VOIP, etc), or monitoring the state of some sensor (shake detection?). Constantly touching the hardware has its own battery implications. My (somewhat dated) rundown on Android Lifecycles: http://www.slideshare.net/zedray2/architecture-your-androidapplication -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
