Programmatically enable/disable Broadcastreceiver

Question

We have an app that scans for Bluetooth devices. The code responsible for scanning should only run when bluetooth is enabled. Also we want to disable/enable this feature at any point in time.

We choose to implement a BroadcastReceiver that registers for the BluetoothAdapter.ACTION_STATE_CHANGED broadcast.

Here some of the problems we encountered:

Programmatically enable the BroadcastReceiver:

public void registerForBroadcasts(Context context) {
    IntentFilter bluetooth = new IntentFilter(BluetoothAdapter.ACTION_STATE_CHANGED);
    context.registerReceiver(this, bluetooth);
}

When the app is killed, the BroadcastReceiver is also not active anymore. So if the user multi-tasks-swipes the app to death, it is not being woken up again.
We have full control, when to start the BroadcastReceiver.

Declare the BroadcastReceiver in the Manifest

<receiver android:name="com.mypackage.BroadcastReceiver">
    <intent-filter>
        <action android:name="android.bluetooth.adapter.action.STATE_CHANGED"/>
    </intent-filter>
</receiver>

The BroadcastReceiver is active right after the app start.
The BroadcastReceiver cannot be disabled.

Declare the BroadcastReceiver in the Manifest as disabled + enable it programmatically

<receiver android:name="com.mypackage.BroadcastReceiver"
          android:enabled="false" >
    <intent-filter>
        <action android:name="android.bluetooth.adapter.action.STATE_CHANGED"/>
    </intent-filter>
</receiver>

Then enable the component if you need it.

public void registerForBroadcasts(Context context) {
    ComponentName component = new ComponentName(context, BroadcastReceiver.class);
    PackageManager pm = context.getPackageManager();
    pm.setComponentEnabledSetting(
                component,
                PackageManager.COMPONENT_ENABLED_STATE_ENABLED,
                PackageManager.DONT_KILL_APP);
}

My tests have shown, the state is persisted with the system, so the BroadcastReceiver will stay enabled. It combines the advantages of both methods.

BroadcastReceiver can be disabled
BroadcastReceiver can be on or off by default
BroadcastReceiver keeps activation even if app is disabled and phone rebooted.

Am I missing something, does this method seem legit?

just notice that you have used BroadcastReceiver.class in getting the component, you should use your MyBroadcastReceiver.class instead to get the right broadcast component — ndori, Sep 05 '17 at 07:42

score 13 · Answer 1 · answered Jun 28 '16 at 12:51

It is possible to enable/disable the receiver programatically.

To Enable programatically

PackageManager pm  = Re_editActivity.this.getPackageManager();
ComponentName componentName = new ComponentName(currentActivity.this, name_of_your_receiver.class);        
pm.setComponentEnabledSetting(componentName,PackageManager.COMPONENT_ENABLED_STATE_ENABLED,
                                PackageManager.DONT_KILL_APP);

To Disable programatically

PackageManager pm  = Re_editActivity.this.getPackageManager();
ComponentName componentName = new ComponentName(currentActivity.this, name_of_your_receiver.class);
pm.setComponentEnabledSetting(componentName,PackageManager.COMPONENT_ENABLED_STATE_DISABLED,
                            PackageManager.DONT_KILL_APP);

Manifest receiver

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

Does the receiver need to be disabled (enabled set to false) in the manifest? — georgiaboy82, Jun 16 '18 at 03:27
If you don't want your receiver need to be enabled by default(before setting programatically) then you can disable in the manifest. — Kumar M, Jun 18 '18 at 05:56

score 7 · Answer 2 · answered Jun 17 '14 at 14:15

The BroadcastReceiver cannot be disabled.

Sure it can. Use PackageManager and setComponentEnabledSetting(), as you did in your third scenario.

Am I missing something, does this method seem legit?

It is very legit, at least in terms of managing the BroadcastReceiver. I don't know if there are any Bluetooth-specific hiccups, though I would doubt it. This technique is used for various broadcasts, such as only listening to ACTION_BOOT_COMPLETED when you really do have something that needs to be done at boot time.

Programmatically enable/disable Broadcastreceiver

2 Answers2

Linked