Changed: Migrating to ChickenHook RestrictionBypass #3744
Closed
Conversation
This file contains hidden or 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
3507c71 to
b164895
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
LSPosed Hiddenapi Bypass uses sun.misc.Unsafe, which is not good, it is literally unsafe, and may be removed in future.
For bypassing hiddenapi, there is a safer way on Chickenhook Restriction Bypass lib.
References:
https://github.com/ChickenHook/RestrictionBypass
https://blogs.oracle.com/javamagazine/post/the-unsafe-class-unsafe-at-any-speed
https://androidreverse.org/blog/2023/02/21/android-api-restriction-bypass-for-all-android-versions/
https://developer.android.com/distribute/best-practices/develop/restrictions-non-sdk-interfaces