We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The exact same thing as here #2120 happens on another device.
Video should start playing automatically from the beginning. Instead the output is stuck on last frame.
The device is this one https://www.framexx.com/framexx-sign/
2.9.2
"MBX Quad-Core Enjoy TV Box" running Android 4.4.2
stvm8-bugreport.txt
Update MediaCodecRenderer.codecNeedsEosFlushWorkaround as so:
MediaCodecRenderer.codecNeedsEosFlushWorkaround
private static boolean codecNeedsEosFlushWorkaround(String name) { return (Util.SDK_INT <= 23 && "OMX.google.vorbis.decoder".equals(name)) || (Util.SDK_INT <= 19 && ("hb2000".equals(Util.DEVICE) || "stvm8".equals(Util.DEVICE)) && ("OMX.amlogic.avc.decoder.awesome".equals(name) || "OMX.amlogic.avc.decoder.awesome.secure".equals(name))); }
where "stvm8" is the device in question.
"stvm8"
This has been tested (with the non-secure variant) and it solved the described issue.
The text was updated successfully, but these errors were encountered:
Apply EOS flush workaround to stvm8 devices
b23b86d
Issue:#5203 PiperOrigin-RevId: 224726041
be2942c
erdemguven
No branches or pull requests
Issue description
The exact same thing as here #2120 happens on another device.
Reproduction steps
Video should start playing automatically from the beginning. Instead the output is stuck on last frame.
Link to test content
The device is this one https://www.framexx.com/framexx-sign/
Version of ExoPlayer being used
2.9.2
Device(s) and version(s) of Android being used
"MBX Quad-Core Enjoy TV Box" running Android 4.4.2
A full bug report captured from the device
stvm8-bugreport.txt
The solution
Update
MediaCodecRenderer.codecNeedsEosFlushWorkaround
as so:where
"stvm8"
is the device in question.This has been tested (with the non-secure variant) and it solved the described issue.
The text was updated successfully, but these errors were encountered: