Vivo Z1 Pro - Frequent MediaCodec.CodecException.ERROR_RECLAIMED failure
See original GitHub issueSearches:
-
q=MediaCodec.CodecException - No result
Issue #5649 - Not related Issue #3896 - Stale Issue #1036 & Issue #978 - Outdated
[REQUIRED] Issue description
Facing MediaCodec.CodecException.ERROR_RECLAIMED after 2-3 minutes of video playback on DRM protected content
Exception Log:
E ExoPlayerImplInternal: Internal runtime error.
E ExoPlayerImplInternal: android.media.MediaCodec$CodecException: Error 0xffffffe0
E ExoPlayerImplInternal: at android.media.MediaCodec.native_queueSecureInputBuffer(Native Method)
E ExoPlayerImplInternal: at android.media.MediaCodec.queueSecureInputBuffer(MediaCodec.java:2608)
E ExoPlayerImplInternal: at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.feedInputBuffer(MediaCodecRenderer.java:1113)
E ExoPlayerImplInternal: at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:654)
E ExoPlayerImplInternal: at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:575)
E ExoPlayerImplInternal: at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:326)
E ExoPlayerImplInternal: at android.os.Handler.dispatchMessage(Handler.java:102)
E ExoPlayerImplInternal: at android.os.Looper.loop(Looper.java:224)
E ExoPlayerImplInternal: at android.os.HandlerThread.run(HandlerThread.java:65)
I MediaCodec: kWhatStop or kWhatRelease
E EventLogger: playerFailed [209.88, 176.18, window=0, period=0]
E EventLogger: com.google.android.exoplayer2.ExoPlaybackException: android.media.MediaCodec$CodecException: Error 0xffffffe0
E EventLogger: at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:397)
E EventLogger: at android.os.Handler.dispatchMessage(Handler.java:102)
E EventLogger: at android.os.Looper.loop(Looper.java:224)
E EventLogger: at android.os.HandlerThread.run(HandlerThread.java:65)
E EventLogger: Caused by: android.media.MediaCodec$CodecException: Error 0xffffffe0
E EventLogger: at android.media.MediaCodec.native_queueSecureInputBuffer(Native Method)
E EventLogger: at android.media.MediaCodec.queueSecureInputBuffer(MediaCodec.java:2608)
E EventLogger: at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.feedInputBuffer(MediaCodecRenderer.java:1113)
E EventLogger: at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:654)
E EventLogger: at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:575)
E EventLogger: at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:326)
E EventLogger: ... 3 more
[REQUIRED] Reproduction steps
- Build sample demo app from v2.10.4 Exo or download this apk
- Expand
Widevine DASH Policy Test (GTS)
- Open
WV: HDCP not specified
- Play the video for a while approx 3 minutes
[REQUIRED] Link to test content
[
{
"name": "Widevine DASH Policy Tests (GTS)",
"samples": [
{
"name": "WV: HDCP not specified",
"uri": "https://storage.googleapis.com/wvmedia/cenc/h264/tears/tears.mpd",
"drm_scheme": "widevine",
"drm_license_url": "https://proxy.uat.widevine.com/proxy?video_id=d286538032258a1c&provider=widevine_test"
}
]
}
]
[REQUIRED] A full bug report captured from the device
[REQUIRED] Version of ExoPlayer being used
v2.10.4
[REQUIRED] Device(s) and version(s) of Android being used
Personally reproduced: Vivo Z1 Pro - Android 9 - 100% reproducible User reports : Samsung Galaxy Tab A 8.0 - Android 7.1.1 Samsung SM-J415F - Android 8.1.0 Vivo 1806 - Android 9
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We’ve ordered a Vivo Z1 Pro device to try and reproduce this, but it’s going to take a while for it to be delivered. We’ll update this issue once we’ve received it and tried to reproduce.
@ojw28 Thanks for procuring and trying to figure out the issue. Unfortunately, we are also not able to reproduce the issue since the day you commented. I assume some silent patch has been done from Vivo as we have not done any os upgrade.
Also to note that our analytics indicate that the error rate from this device, for this reason, dropped from ~280 per day to ~30 per day gradually. I assume that the issue is solved by the manufacturer.
Thanks for your time debugging the issue. Very much appreciated.