The biggest problem I've run into is that task killers wipe any future alarms you may have set. So a well-behaved app which is not actually running now, but is set to do something in the future (often at the user's behest), will no longer function thanks to the frackin' task killer. But do you think it's the task killer's dev who gets support emails and 1* Market comments?
String On Oct 7, 7:15 pm, Nathan <[email protected]> wrote: > I'm straying a bit, but what problems do you generally get from task > killers? > > I only know of one confirmed problem with a taskkiller, but based on > their destructive nature, I suspect there are a lot more. > > Will they close a program when not visible? This is the one I've seen. > The home screen button behaving. > Will they kill a service before it's done, leaving an orphaned > progress notification, saying 0% forever? > Will they corrupt SQLiteDatabase files in the process of killing > things? > Will they kill a BroadcastReceiver before it is done? > > What's been the usual signs? > > Thanks, > > Nathan -- 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
