CODEWITHSUNDEEP
android
user902131
user902131

Reputation: 11

Reboot after install

Is it possible to force a reboot of the device after my apk is installed?

I want to force this because I want to ensure that my service is started.

Upvotes: 0

Views: 1605

Answers (2)

Bjarke Freund-Hansen
Bjarke Freund-Hansen

Reputation: 30128

Most probably the answer is no, your are not allowed to do such things from your app. This is the sole privilege of the user holding the phone (and of maybe the core system services).

You can however ensure you service is started when the user starts you main activity, which would be a very normal thing to do right after the user have installed your application.

For additional information see the question How to start android service on installation, which is in fact what you should be trying to do.

Upvotes: 2

Felix
Felix

Reputation: 89576

It's not possible in any way to get your application to do anything as soon as it's installed, before the user first launches it from the home screen. There's no broadcast action you can listen for explicitly. However, you can listen for something generic that gets called a lot, such as:

  • android.intent.action.USER_PRESENT,
  • android.intent.action.SCREEN_OFF, or
  • android.intent.action.SCREEN_ON

In any case you should NOT reboot the device. Your users will hunt you down and kill you with stones. Joke aside, Google might actually pull your app from the Market for this. Just listen for one of the actions mentioned above, check if the app has just been installed (using a one-time boolean preference, for example) and start the service.

Note: if you do end up listening for one of the above actions, please disable your receiver the first time it receives an intent. You can do this like so (in your receiver):

public class FirstTimeReceiver extends BroadcastReceiver {

    public void onReceive (Context context, Intent intent) {
        // start your service (which does stuff asynchronously, of course, and then:
        final ComponentName mySelf = new ComponentName(context, FirstTimeReceiver.class);
        context.getPackageManager().setComponentEnabledSetting(mySelf, PackageManager.COMPONENT_ENABLED_STATE_DISABLED, PackageManager.DONT_KILL_APP);
    }

}

However, you should only do this if somehow this service is absolutely critical for the user (there are few proper scenarios for this), and not for you / your app. As bjarkef mentioned, you should only start it after the user starts your app from the home screen (better yet, ask for permission from the user to run the service).

Upvotes: 0

Related Questions