media: Increase in `ERROR_CODE_FAILED_RUNTIME_CHECK=1004` errors after seek on Android 14 since 1.3.0
Version
Media3 1.3.0
- The number of errors has grown ~3-4 times after the update from 1.2.0 to 1.3.0
- We will update to 1.4.0 in the near future to see if that helps
More version details
No response
Devices that reproduce the issue
We were not able to reproduce the issue locally yet, but here are some stats from production.
The issue is most prominent on Android 14:
Devices:
| Device | Occurrences over last 30 days (unique) |
|---|---|
| SM-X200 | 14,885 |
| SM-P613 | 9,367 |
| SM-A525M | 7,118 |
| CPH2363 | 6,109 |
| SM-A135M | 6,082 |
| moto g84 5G | 5,732 |
| SM-A235M | 5,542 |
| moto g53 5G | 5,249 |
| 23043RP34G | 5,211 |
| motorola edge 30 neo | 3,859 |
| A063 | 3,275 |
| SM-X205 | 2,615 |
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Not tested
Reproduction steps
Based on the user behavior, most users face this issue after seeking the video. Examples:
Expected result
The media plays successfully.
Actual result
Playback crashes with the ERROR_CODE_FAILED_RUNTIME_CHECK=1004 error.
Unexpected runtime error at q2.J.handleMessage(ExoPlayerImplInternal.java:293)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:257)
at android.os.Looper.loop(Looper.java:368)
at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: android.media.MediaCodec$CodecException:
at android.media.MediaCodec.native_flush(Native Method)
at android.media.MediaCodec.flush(MediaCodec.java:2504)
// ... the rest of the stacktrace is obfuscated
The diagnostic info is: android.media.MediaCodec.error_neg_110
https://developer.android.com/reference/android/media/MediaPlayer#MEDIA_ERROR_TIMED_OUT
Media
DASH H.264, Widevine
Bug Report
- You will email the zip file produced by
adb bugreportto android-media-github@google.com after filing this issue.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 1
- Comments: 22 (2 by maintainers)
Commits related to this issue
- Switch default of async crypto mode to disabled There are reproducible issues with codec timeouts when using this API, so we disable it entirely until we know more about potential fixes and where the... — committed to androidx/media by tonihei 2 years ago
- Switch default of async crypto mode to disabled There are reproducible issues with codec timeouts when using this API, so we disable it entirely until we know more about potential fixes and where the... — committed to androidx/media by tonihei 2 years ago
@maartenvgpersgroep API 36+ should be BAKLAVA if you want to use a named constant, not
VANILLA_ICE_CREAM(that was API 35)There is no update from the relevant platform team yet I’m afraid. Since the feature doesn’t seem to be reliable, I’m going to flip the default back to “don’t use it” until we get more information when a fix will be available.