Update tag to r33 + Allow devices to force-add directly-connected routes #1
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
Most sane devices have directly-connected routes properly added by ConnectivityService, but a number of Samsung RIL libraries seem to be doing "special" things, the end result of which is IPv4 mobile data is non-functional due to lack of a default route. Affected devices have a log entry similar to the below: Error adding route 0.0.0.0/0 -> xxx.xxx.xxx.xxx rmnet0 to table 1002: Network is unreachable This reverts, with guards, commit 92e8f96. Change-Id: I6a653d19c1c72c136e78d8d841e87d3c166698ea
…tform/system/netd into HEAD Android 9.0.0 Release 33 (PQ2A.190205.003) # gpg: Signature made Вт 05 фев 2019 02:45:58 MSK # gpg: using DSA key E8AD3F819AB10E78 # gpg: Can't check signature: public key not found
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.
No description provided.