Fix: Enable high refresh rate support via preferredRefreshRate (#2086)#2098
Open
zaibihsn wants to merge 2 commits into
Open
Fix: Enable high refresh rate support via preferredRefreshRate (#2086)#2098zaibihsn wants to merge 2 commits into
zaibihsn wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #2086
Description:
This PR enables high refresh rate (90Hz/120Hz) support for Android devices, bypassing the aggressive 60Hz lock applied by some OEM skins to Compose apps.
Implementation Details:
Implemented the preferredRefreshRate API for devices on Android R (API 30) and above.
This approach successfully signals the OS to utilize higher refresh rates without explicitly forcing a display mode, preventing unintended physical resolution downgrades on multi-resolution panels (e.g., Galaxy S20).
Preserves Variable Refresh Rate (VRR/LTPO) capabilities, allowing the system to drop frame rates on static screens for battery optimization.
Thanks again for the incredibly detailed review and for providing the minimal implementation! I completely understand the issue with the multi-resolution panels and the battery impact on LTPO displays now—that was a great learning moment.
I've pushed the updated commit using your suggested preferredRefreshRate approach for Android R+. Let me know if this looks good to go!