Introduce a much faster Presentation renderer #13
+71
−126
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
Instead of using the texture view based map and taking images of the map every frame, this patch directly renders using Android's Presentation class that is mentioned in the documentation. It sets up an Android VirtualDisplay and wires the surface to it, and then directly presents MapView on it. This ends up being a lot more performant than the existing approach.
Author
|
Details of this implementation in my blog post here. From within our apps, the texture implementation gives ~8.26fps, whereas this one does ~34.66fps. |
Member
This was referenced Dec 4, 2025
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.
Instead of using the texture view based map and taking images of the map every frame, this patch directly renders using Android's Presentation class that is mentioned in the documentation. It sets up an Android VirtualDisplay and wires the surface to it, and then directly presents MapView on it. This ends up being a lot more performant than the existing approach.