H.265 (HEVC) + widewine some devices cannot play
Version
Media3 1.1.1 / ExoPlayer 2.19.1
More version details
Hi, I got problem with some of h.265 streams with widevine. One of tested device is returning decoding error. At the moment I cannot share the stream, however I'm working on it. We also had tested on newest media3 1.4.1 but results were the same. I attach logs, maybe there is something you will see.
log_galaxy_a14.log My apologies for no stream or reproduction steps. I'm working on it.
Devices that reproduce the issue
Samsung Galaxy A14 on Android 14
Devices that do not reproduce the issue
Samsung Galaxy S20 FE on android 13
Reproducible in the demo app?
Not tested
Reproduction steps
Currently only logs available. Working on repro app
Expected result
Stream is played
Actual result
Stream is not played
Media
H.265 stream with widevine L1
Bug Report
- [ ] You will email the zip file produced by
adb bugreportto [email protected] after filing this issue.
@rrfrias: Do the Widevine logs in the attached output look expected? There are a few warnings and errors (e.g. Cdm Identifier not found or Failed to close cdm), but not sure if that can cause the secure codec to fail.
I found that this issue happen all device with mediatek chipset
Following up with Mediatek (Internal ref: 371091096)
Mediatek investigated, found the root cause and has a fix. Following up with Samsung (Internal ref: 400783399) to pick up the fix.
@TeaFather Can you retest? Samsung thinks they have a issued a patch that addresses this issue last November.
@rrfrias can you share version so we can check in OS settings that its already updated?
Samsung did not give me a precise version but mentioned that it should be included when the device updates to android 15. Can you let us know if you are still seeing the problem after the upgrade?
Hey @TeaFather. 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!
Since there haven't been any recent updates here, I am going to close this issue.
@CrashBashMD 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.