Android: Fix Random Service starts in the client #3492
Merged
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.
Description
The Default value here is "START_STICKY" - So if the OS stops the service not because of the unbind, Android will re-deliver the intent but without the extra "start-only".
We handle a start without extras as if the os requests-always on, thus enabling the vpn.
Start_NOT_STICKY means here that once the service is stopped by the os, we won't get a new intent to restart.
Reference
closes #3179