Add a way to not ignore performance points for resolution and frame rate (3rd try) #21
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
flambert
approved these changes
May 15, 2024
simonlary
pushed a commit
that referenced
this pull request
Oct 1, 2024
…ate (3rd try) (#21) In androidx@3521ccd, a fallback was added when there is no coverage for 720p 60 FPS. That introduced performance issues on several device models that are now dropping 15-40 frames / sec in Live playback (depending on the model). That's because they used to stay at a lower resolution/framerate, and are now trying to playback 720P 60 FPS, but they struggle to do so. This PR will allow us to disable the fallback on the identified device models. So they will revert to using the lower fps track. Previous attempts #19 and #20 had an issue with lower resolutions. They were handling the formats that we didn't want to be supported correctly, but they were also discarding lower resolutions/frame rates. This one has been tested on a device similar to the ones with the issue, and is confirmed to work properly.
simonlary
pushed a commit
that referenced
this pull request
Oct 1, 2024
…ate (3rd try) (#21) In androidx@3521ccd, a fallback was added when there is no coverage for 720p 60 FPS. That introduced performance issues on several device models that are now dropping 15-40 frames / sec in Live playback (depending on the model). That's because they used to stay at a lower resolution/framerate, and are now trying to playback 720P 60 FPS, but they struggle to do so. This PR will allow us to disable the fallback on the identified device models. So they will revert to using the lower fps track. Previous attempts #19 and #20 had an issue with lower resolutions. They were handling the formats that we didn't want to be supported correctly, but they were also discarding lower resolutions/frame rates. This one has been tested on a device similar to the ones with the issue, and is confirmed to work properly.
simonlary
pushed a commit
that referenced
this pull request
Jan 21, 2025
These were missed when upgrading to both SDK 19 and 21, but they now cause failures like: ``` Caused by: java.lang.RuntimeException: Failed to parse package buildout/intermediates/apk_for_local_test/debugUnitTest/packageDebugUnitTestForUnitTest/apk-for-local-test.ap_: buildout/intermediates/apk_for_local_test/debugUnitTest/packageDebugUnitTestForUnitTest/apk-for-local-test.ap_ (at Binary XML file line #20): Requires newer sdk version #21 (current version is #19) at org.robolectric.shadows.ShadowPackageParser.callParsePackage(ShadowPackageParser.java:61) ... 20 more ``` #cherrypick PiperOrigin-RevId: 670241471
simonlary
pushed a commit
that referenced
this pull request
Jan 24, 2025
…ate (3rd try) (#21) In androidx@3521ccd, a fallback was added when there is no coverage for 720p 60 FPS. That introduced performance issues on several device models that are now dropping 15-40 frames / sec in Live playback (depending on the model). That's because they used to stay at a lower resolution/framerate, and are now trying to playback 720P 60 FPS, but they struggle to do so. This PR will allow us to disable the fallback on the identified device models. So they will revert to using the lower fps track. Previous attempts #19 and #20 had an issue with lower resolutions. They were handling the formats that we didn't want to be supported correctly, but they were also discarding lower resolutions/frame rates. This one has been tested on a device similar to the ones with the issue, and is confirmed to work properly.
jdtremblay
pushed a commit
that referenced
this pull request
May 29, 2025
…ate (3rd try) (#21) In androidx@3521ccd, a fallback was added when there is no coverage for 720p 60 FPS. That introduced performance issues on several device models that are now dropping 15-40 frames / sec in Live playback (depending on the model). That's because they used to stay at a lower resolution/framerate, and are now trying to playback 720P 60 FPS, but they struggle to do so. This PR will allow us to disable the fallback on the identified device models. So they will revert to using the lower fps track. Previous attempts #19 and #20 had an issue with lower resolutions. They were handling the formats that we didn't want to be supported correctly, but they were also discarding lower resolutions/frame rates. This one has been tested on a device similar to the ones with the issue, and is confirmed to work properly.
jdtremblay
pushed a commit
that referenced
this pull request
May 29, 2025
…ate (3rd try) (#21) In androidx@3521ccd, a fallback was added when there is no coverage for 720p 60 FPS. That introduced performance issues on several device models that are now dropping 15-40 frames / sec in Live playback (depending on the model). That's because they used to stay at a lower resolution/framerate, and are now trying to playback 720P 60 FPS, but they struggle to do so. This PR will allow us to disable the fallback on the identified device models. So they will revert to using the lower fps track. Previous attempts #19 and #20 had an issue with lower resolutions. They were handling the formats that we didn't want to be supported correctly, but they were also discarding lower resolutions/frame rates. This one has been tested on a device similar to the ones with the issue, and is confirmed to work properly.
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.
In androidx@3521ccd, a fallback was added when there is no coverage for 720p 60 FPS. That introduced performance issues on several device models that are now dropping 15-40 frames / sec in Live playback (depending on the model). That's because they used to stay at a lower resolution/framerate, and are now trying to playback 720P 60 FPS, but they struggle to do so.
This PR will allow us to disable the fallback on the identified device models. So they will revert to using the lower fps track.
Previous attempts #19 and #20 had an issue with lower resolutions. They were handling the formats that we didn't want to be supported correctly, but they were also discarding lower resolutions/frame rates.
This one has been tested on a device similar to the ones with the issue, and is confirmed to work properly.