There are ~ 7 billion people on the planet. Only you know what you mean by "kill."
The symptoms you describe, however, are consistent with a "stopping power." The user usually forcibly stops the application by going to Settings, finding your application in the list of installed applications and clicking the "Force Stop" button for your application. There are some devices and firmware that make Force Stop more accessible than this β such devices and firmware assemblies were written by frightening IMHO idiots.
If your application is disabled, your code will never run again until something uses an explicit Intent to run one of your components. Typically, a user does this by clicking on the icon of their application in the launch pad. Until the user does this, your BroadcastReceiver will not work, and there is nothing you can do about it.
Instead of using some function on the device to βkillβ your application, try terminating its process through DDMS. If your application continues to work in this case, then, however, you decide to βkillβ your application before doing a βforced stopβ. A simple process termination, for example, due to low memory conditions, should not impede future transmissions.
source share