Restrict contentprovider from starting new process #74
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently background service will not started if a new process will start and the app is in background restriction state, but not for content providers. This leave a loophole for bad apps to wake up each other. This patch fix this problem.
|
This is a minor modification from here |
spkal01
force-pushed
the
pyro
branch
3 times, most recently
from
fa6f785 to
d49ac00
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently background service will not get started if there is no existing process for the service, and the app is in background restriction state, but not for content providers. This leave a loophole for bad apps to wake up each other. This patch fix this problem.