Optionally use hardware rendering on Android 10 and later #2663
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
simonpoole
force-pushed
the
hardware_rendering_yet_another_time
branch
2 times, most recently
from
11742da
to
c73866e
Compare
Starting with Android 10 it seems as if at least most of the issues with hardware rendering in Android have been resolved. This commits re-enables the experimental option to turn it on. Resolves #308
simonpoole
force-pushed
the
hardware_rendering_yet_another_time
branch
from
c73866e
to
169cc79
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.
Starting with Android 10 it seems as if at least most of the issues with hardware rendering in Android have been resolved. This commits re-enables the experimental option to turn it on.
Resolves #308