On Wed, Oct 27, 2010 at 5:01 AM, mort <m...@sto-helit.de> wrote: >> There should be no code running at this point; hence, IMHO, this >> status is pointless and confusing. > > I don't think so. From a user's point of view, there's no difference > if there's a started service that's actually doing something by > Handler.postDelayed every 5 minutes and an app that does the same by a > repeating AlarmManager.
Sure there is. It's called a "process" and "a big chunk of RAM". > I'm generally a bit confused about Google making misused services > "pariahs" while I could bomb a device with AlarmManager Intents every > few seconds and nobody would see any difference to a paused Activity, > except maybe in battery consumption. Because it's really easy for developers to accidentally think that everlasting services are a good idea. IMHO, it is less likely that they will accidentally make something run every few seconds via AlarmManager and think that is a good idea. >> This requires no modifications to Android. You are welcome to work out >> a convention and try to get task managers and app developers to adhere >> to it. > > In theory, that's true. But an official way to do that is an entirely > different thing than a private campaign that might even end up with > dozens of concurring intents because every task manager developer > wants his own package name contained. That would not be "a convention". -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 2.2 Programming Books: http://commonsware.com/books -- 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
