Personally I would like to see this API go away. I'm finding we now have to code around task killing applications, which shouldn't be the case. Being a good Android citizen and following the rules, allowing the OS to do the work it was designed to do is the way to go. Users are confused when the app runs in the background claiming it's taking cpu and wasting battery because it shows up in task manager lists. In our case our bg service only watches a particular directory waiting for new files to be added. It's not *running*, it's waiting. Users go off and kill our app then wonder why it doesn't work any more.
My two cents. Todd On Oct 13, 8:58 pm, Dianne Hackborn <[email protected]> wrote: > On Tue, Oct 13, 2009 at 9:09 PM, EboMike <[email protected]> wrote: > > Task killers aside, what about if the OS decides to stop a process > > because memory is low? > > It doesn't do what these apps are doing. As I said, what these apps are > doing (especially the ones that do this stuff behind the user's back) is > abusing an API that is not intended to be used this way. > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- 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
