I am the taskiller developper.
If an user choose to kill your app. Your app may not be restarted.
Users are using taskiller because too more apps have bad implemention
Too many apps are launching without user action, like uninstalled
widgets, because they receive
Broadcast and dont verify the effective use of the app.
Too many apps are implementing Start on boot when not needed.
With taskiller, users are checking that too many apps are loaded on
startup and 50% of these apps are not useful at startup....(like
Too many apps are not explaining what they do. If your apps are using
background service, inform the user that the app will stay
in background, and maybe the users will not kill "stupidly" your app.
And the bad news is that others task managers are implementing
autokill.... or Boot kill....which can made many apps crashing (if
your app use an intents to another app...if this app is autokilled
your app will never worl :( ...
On Oct 13, 1:09 am, Lazarus 101 <lazarus...@gmail.com
> Thanks Dianne for the quick answer.
> ActuallyTasKilleris 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 toTasKillerso 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 <hack...@android.com
> > 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 likeTasKilleris 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 <lazarus...@gmail.com
> > > I have an app that does some polling every 2 hours. I set a repeating
> > >alarmthat 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