mirscreencast now attempts to use the buffer stream API to map the buffer (which worksaround some android drivers that return bad pixels if you do glReadPixels on a context that was not rendered in that same process).
If it fails (which produces the error log) then it falls back to the EGL/glReadPixels instead.
Yeah it's "benign".
mirscreencast now attempts to use the buffer stream API to map the buffer (which worksaround some android drivers that return bad pixels if you do glReadPixels on a context that was not rendered in that same process).
If it fails (which produces the error log) then it falls back to the EGL/glReadPixels instead.