-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
H.265 (HEVC) + widewine some devices reboots #1751
Comments
Please email us the result of |
Bugreport has been sent |
The logcat unfortunately did not capture the reboot cause and he bugreport did not capture the logs of playback or tombstones for the reboot cause. Can you share another bugreport, please? |
another bugreport sent |
Is it possible to send me a true bugreport. 401886_bugreportsTablet.txt.zip contains a logcat 401886_bugreportsTablet.txt but none of the other files usually collected in a bugreport including tombstones. Either run Was phonelogcat.txt the logcat before the crash occurred? Also, can you grant permission to share these logs with Samsung? |
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 reboots (another is returning decoding error - separate issue). 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.
restart_galaxy_tab.log
My apologies for no stream or reproduction steps. I'm working on it.
Devices that reproduce the issue
Samsung Galaxy Tab A8 running on android 11
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
No device reboot
Actual result
Device reboots after initializing the stream. Looks like DRM related issue
Media
H.265 stream with widevine L1
Bug Report
adb bugreport
to android-media-github@google.com after filing this issue.The text was updated successfully, but these errors were encountered: