ansaurus

Question

onBoot Complete as user preference

Answer 1

A:

Check out my answer to this question. And these links.

http://www.androidcompetencycenter.com/2009/06/start-service-at-boot/

http://stackoverflow.com/questions/2784441/trying-to-start-a-service-on-boot-on-android

http://stackoverflow.com/questions/2782448/android-how-to-start-a-service-at-boot-based-on-user-settings

Qberticus 2010-08-12 06:57:23

Answer 2

A:

As a matter of fact, there is:

Your boot receiver:

public class BootstrapReceiver extends BroadcastReceiver {
   @Override
   public void onReceive(Context cntxt, Intent intent) {
      String action = intent.getAction();

      if(Intent.ACTION_BOOT_COMPLETED.equals(action)) {
          // do your thing
      }     
   }
}

Add a receiver and a permission for receiving boot events:

  <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
  ....

  <receiver android:name=".BootstrapReceiver" android:enabled="true">
     <intent-filter>
        <action android:name="android.intent.action.BOOT_COMPLETED" />
     </intent-filter>
  </receiver>

Via the application (Use this if you want to programatically add/remove boot receiver and not via AndroidManifest.xml. But remember, you will still have to declare the boot permission in your AndroidManifest.xml)

  Context ctx = getContext();
  BootstrapReceiver booter = new BootstrapReceiver();
  IntentFilter filter = new IntentFilter(Intent.ACTION_BOOT_COMPLETED);
  ctx.registerReceiver(booter, filter);

Unregister:

  ctx.unregisterReceiver(booter);

naikus 2010-08-12 07:02:30

Your second part doesn't work. By definition BOOT_COMPLETED is only sent when the system first boots... before your app has run... so there is no opportunity to call registerReceiver() to tell it about the receiver before the broadcast is sent.

hackbod 2010-08-12 08:37:55

@hackbod Its quite obvious to mention here, it will work only on next boot

naikus 2010-08-12 08:51:13

No, it won't work. The registerReceiver() only lasts for the lifetime of the process. That is why there is no need to have BootstrapReceiver in your manifest -- this just sets up a direct callback to the Receiver instance you provide. Once the instance goes away (when your process goes away), the registration is gone.

hackbod 2010-08-12 21:20:20

@hackbod, You are right! I checked the documentation and there seems to be no way to do that. My bad :)

naikus 2010-08-13 10:08:27

Yes there is a way to do that: it's called `PackageManager.setComponentEnabledSetting`.

Christopher 2010-08-17 22:42:46

Answer 3

A:

The best way to do this is use PackageManager.setComponentEnabledSetting(): http://developer.android.com/reference/android/content/pm/PackageManager.html#setComponentEnabledSetting(android.content.ComponentName, int, int)

So simply decide whether you want your receiving to be enabled or not by default by setting android:enabled in the manifest. Then use this API to explicitly enable or disable the component at run time as desired. If the component is disabled, at boot it will not be available, and thus not receive the broadcast.

hackbod 2010-08-12 08:41:26

ansaurus

tags:

views:

answers:

onBoot Complete as user preference

related questions