Repository navigation
HDR10+ metadata ignored on some hybrid DV/HDR10+ files when display does not support Dolby Vision #3119
Description
Version
Media3 1.9.2
More version details
No response
Devices that reproduce the issue
Android TV boxes connected to Samsung TVs (which support HDR10+ but do not support Dolby Vision).
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
Play a hybrid Dolby Vision / HDR10+ video file.
Expected result
HDR10+ should be triggered on the display.
Actual result
Playback falls back to HDR10 instead of HDR10+.
Media
Android box detects Dolby Vision capability
TV does not support Dolby Vision
file contains DV + HDR10+
player should fall back to HDR10+
Bug Report
- You will email the zip file produced by
adb bugreportto android-media-github@google.com after filing this issue.
Activity
tianyif commentedon Mar 12, 2026
Hi @guyyagil,
It looks like we haven't received your bug reports or test content, please make sure that you send them to android-media-github@google.com with the subject
Issue #3119. Please also update this issue to indicate you've done this.guyyagil commentedon Mar 16, 2026
Thank you for the response.
I reproduced the issue on my device and generated a bugreport.
I have sent the bugreport to the email address you provided.
Please let me know if any additional information or logs are needed.
amitsamal commentedon Mar 30, 2026
On a similar note but not on TV we found that certain models like google pixel 9a (G3 Tensor chipset) we found dolby vision 8.1 behave differently. It fails sometimes saying invalid hdr10 static metadata.
google-oss-bot commentedon Apr 16, 2026
Hey @guyyagil. We need more information to resolve this issue but there hasn't been an update in 14 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
guyyagil commentedon Apr 17, 2026
I’ve opened a PR that should address this issue:
#3160
It adds proper fallback from Dolby Vision to HEVC, allowing HDR10+ metadata in the base layer to be used when DV isn’t supported.
Would appreciate any feedback.
google-oss-bot commentedon Apr 28, 2026
Since there haven't been any recent updates here, I am going to close this issue.
@guyyagil if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.