Thanks Dianne for the quick answer. Actually TasKiller is not automatically killing apps, but it has a widget that allows users to kill (almost) all apps with one click. Most of the Android users that I know are using something similar to TasKiller so this is a tricky problem, users will blame my app for not doing what it says it does. I saw there is a PACKAGE_RESTARTED broadcast but obviously the restarted package does not receive the notification so there's not much I can do to "fix" this problem...
Having applications that can affect the functionality of every other apps installed on the system is not such a good idea IMHO. A Task Manager is needed but the user should be clearly informed that the apps he choses to kill are not working anymore because that's exactly what he wanted. Also the permission is called "restart other application" it should be "kill other applications", that's why I thought alarms are not affected by this and that services are getting restarted (I saw services being restarted after crashes or after being killed due to lack of memory so I though it's the same behaviour when calling ActivityManager.restartPackage). On Oct 12, 11:22 pm, Dianne Hackborn <[email protected]> wrote: > That is intentional. Stopping an application is there for the user to stop > everything associated with it -- processes, alarms, services, notifications, > etc. They will not be restarted until someone explicitly does so (typically > this would be the user re-launching the app and having it do the appropriate > thing). > > It sounds like TasKiller is abusing this API. The API is there for the user > to explicitly stop an app from running without going to the most extreme > measure of uninstalling the app. Trying to use it to automatically stop > things behind the user's back seems... questionable, and probably not what > the user actually wants. > > > > On Mon, Oct 12, 2009 at 1:00 PM, Lazarus 101 <[email protected]> wrote: > > > I have an app that does some polling every 2 hours. I set a repeating > > alarm that starts a service but I have noticed that if I use some task > > manager (e.g. TasKiller) to kill my app then the polling will not be > > performed from that moment on. I know this because I store the time of > > the last poll, I have also checked the server logs and there are no > > requests received from the client after I force close my app. > > Is this the way alarms work or should I look somewhere else for a > > crash or smth? because if alarms really get canceled then how should > > we implement the polling? > > > I'm also interested in what happens with a running service if it gets > > killed from another app (I assume all task managers are using > > ActivityManager.restartPackage() to kill other apps), does it get > > restarted? > > -- > 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 -~----------~----~----~----~------~----~------~--~---
