Home » Android » performance – Android O : PHONE_STATE broadcast limitation

performance – Android O : PHONE_STATE broadcast limitation

Posted by: admin April 23, 2020 Leave a comment


I have been trying to do something similar to truecaller app, where my app is supposed to show a screen after a call gets hung up. Was achieving this by registering android.intent.action.PHONE_STATE implicit broadcast in the manifest file.

But it is not working if I change the app to target Android O, because of the Android O broadcast limitation, and I’m trying to figure out an alternative solution to this use case.

Alternative solutions suggested in android docs: Job scheduler or register a service with context.

Job scheduler: Because of the Job scheduler optimizations there will be some delay to receive the callback. So it will affect the user experience if our app screen is shown a few min after the phone call and polling to check for new call logs every few seconds causes battery drain issue.

Register service with context in Java: I want the behavior to work even if the app is not active or alive. This will not work if the system kills the Service.

Register a Foreground Service: This requires a notification to be shown to the user all the time, which would be spam the user, and running a service 24/7 consumes lots of resources which defeats the whole purpose of broadcast limitation.

Please suggest an alternate solution so that the user experience remains the same.

Thanks in advance

How to&Answers:

Eventually, the action was added to the “Implicit Broadcast Exceptions” list so you can add ACTION_PHONE_STATE_CHANGED to your manifest and it will work:



telephony apps may need to receive these broadcasts.


You have only one solution, use a foreground service and register the broadcast receiver in the service.


As there is NO proper solution to read the PHONE_STATE from Android O. The best alternative we can go for is to trigger a job on new call log entry from the content provider. By this, the behaviour is maintained of showing a screen(with a few sec of delay) after the call ends.

NOTE : The disadvantage is we cannot get the state of the phone call(Ringing or off_the_hook etc.,). The call back will only be received after the new call log has been added to the System DB.


For me, and my production app, the solution would be to avoid targeting api 25 and above, until a better workaround/api comes up.

If your app targets level 24 or below, you’re not affected by the new Implicit Broadcast Limitations and your app can still listen to PHONE_STATE broadcasts even when your app is not running.

An app targeting lower APIs can still be downloaded and installed normally on new Android versions, the only reason to update your sdkTarget value is if your app requires usage of new APIs.


There seems to be an broadcast exception for ACTION_NEW_OUTGOING_CALL but not one for incoming call (or when call ends). It seems like a bug to have one for outgoing but not one for incoming. There’s been a bug report filed in google issue tracker. Hopefully their answer will clarify what we should be doing.

I’ll update this answer if/when the bug tracker gets updated.


As mentioned here: https://issuetracker.google.com/37273064#comment4, ACTION_PHONE_STATE_CHANGED (android.intent.action.PHONE_STATE) will be whitelisted for the Android O release. Though they may be replaced with a different mechanism in a future release.