Workaround flushing issues on S-3 JB MR2.
Targeting to all API level 19 devices using the OMX.SEC.avc.dec decoder is probably the right thing to do. It shouldn't have negative implications if we apply the workaround on devices that don't really need it, except to slow down seeking slightly due to decoder re-allocation. Given we're talking about JB, I think the priority should be to "make sure it works". Issue: #951 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=111514406
Showing
with
18 additions
and
1 deletions
Please
register
or
sign in
to comment