Broadcast receiver not working in android oreo

前端 未结 6 1062
迷失自我
迷失自我 2020-12-03 05:28

My Broadcast receiver is not working on oreo but its working below oreo it\'s working fine, I searched a lot regarding this but could not find the suitable solution. Does an

相关标签:
6条回答
  • 2020-12-03 05:58

    Broadcast Limitations

    If an app registers to receive broadcasts, the app's receiver consumes resources every time the broadcast is sent. This can cause problems if too many apps register to receive broadcasts based on system events; a system event that triggers a broadcast can cause all of those apps to consume resources in rapid succession, impairing the user experience. To mitigate this problem, Android 7.0 (API level 25) placed limitations on broadcasts, as described in Background Optimization. Android 8.0 (API level 26) makes these limitations more stringent.

    1. Apps that target Android 8.0 or higher can no longer register broadcast receivers for implicit broadcasts in their manifest. An implicit broadcast is a broadcast that does not target that app specifically. For example, ACTION_PACKAGE_REPLACED is an implicit broadcast, since it is sent to all registered listeners, letting them know that some package on the device was replaced. However, ACTION_MY_PACKAGE_REPLACED is not an implicit broadcast, since it is sent only to the app whose package was replaced, no matter how many other apps have registered listeners for that broadcast.

    2. Apps can continue to register for explicit broadcasts in their manifests.

    3. Apps can use Context.registerReceiver() at runtime to register a receiver for any broadcast, whether implicit or explicit.

    4. Broadcasts that require a signature permission are exempted from this restriction, since these broadcasts are only sent to apps that are signed with the same certificate, not to all the apps on the device.

    Check Official Documentation here

    Hope this helps.

    0 讨论(0)
  • 2020-12-03 05:58

    Register your broadcast receiver in activity on create method rather than in manifest and unregister it on destroy method. Hope this will work on android 9.

    0 讨论(0)
  • 2020-12-03 05:59

    I also had this kind of issue, but I found a better solution:

    Class MyReceiver

    @BroadcastReceiverActions({
            "android.intent.action.SCREEN_ON",
            "android.intent.action.SCREEN_OFF",
            "android.intent.action.DREAMING_STARTED",
            "android.intent.action.DREAMING_STOPPED",
            "android.intent.action.ACTION_POWER_DISCONNECTED",
            "android.intent.action.ACTION_POWER_CONNECTED",
            "android.net.conn.CONNECTIVITY_CHANGE"
    })
    public class MyReceiver extends BroadcastReceiver {
    
        public MyReceiver() {
            super();
        }
    
        @Override
        public void onReceive(Context context, Intent intent) {
            Session.getGlobalReceiverCallBack(context, intent);
    
            //Log.e("dfd", "" + intent.getAction());
        }
    }
    

    Class AppController

    public class AppController extends Application {
    
        private BroadcastReceiver receiver;
        MyReceiver mR;
    
        @Override
        public void onCreate() {
            super.onCreate();
            mR = new MyReceiver();
            receiver = DynamicReceiver.with(mR)
                    .register(this);
    
        }
    }
    

    Class MainActivity

    public class MainActivity extends AppCompatActivity implements GlobalReceiverCallBack {
    
        @Override
        protected void onCreate(Bundle savedInstanceState) {
            super.onCreate(savedInstanceState);
            setContentView(R.layout.activity_main);
            Session.setmGlobalReceiverCallback(this);
    
        }
    
        @Override
        public void onCallBackReceived(Context context, Intent intent) {
    
            Toast.makeText(context, "" + intent.getAction(), Toast.LENGTH_LONG).show();
        }
    }
    

    For complete reference you can see also https://github.com/devggaurav/BroadcastReceiver-For-Naught-and-Oreo-devices

    0 讨论(0)
  • 2020-12-03 06:00

    I have faced the similar issue when implementing call recording app,

    I have added the following code in the AndroidManifest.xml file, then the register is working normally

             <receiver android:name=".Services.Receiver"
                 android:permission="android.permission.RECEIVE_BOOT_COMPLETED"
                 android:enabled="true"
                 android:exported="true">
                <intent-filter>
    
                    <action android:name="android.intent.action.PHONE_STATE"/>
                    <action android:name="android.intent.action.ANSWER"/>
                    <action android:name="android.intent.action.CALL_BUTTON"/>
                    <action android:name= "android.intent.action.NEW_OUTGOING_CALL"/>
                    <action android:name="android.intent.action.BOOT_COMPLETED" />
    
                </intent-filter>
             </receiver>
    
    
    0 讨论(0)
  • 2020-12-03 06:11

    Android 8.0 offers several improvements to JobScheduler that make it easier to replace services and broadcast receivers with scheduled jobs:

    https://developer.android.com/about/versions/oreo/background

    0 讨论(0)
  • 2020-12-03 06:13

    The problem comes with the service you're trying to run, services or persistent background services are not permitted to run for long for apps targeting Oreo and above.

    Check this guide and this as well for migrating your app to support Oreo.

    0 讨论(0)
提交回复
热议问题