Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I'm currently trying to put animations on VideoView.</p> <p>If you look at Android source Code, <a href="http://codesearch.google.com/codesearch#uX1GffpyOZk/core/java/android/widget/VideoView.java&amp;q=package:android.git.kernel.org%20file:android/widget/VideoView.java&amp;l=1" rel="noreferrer">VideoView</a> is basically <a href="http://codesearch.google.com/codesearch#uX1GffpyOZk/core/java/android/view/SurfaceView.java" rel="noreferrer">a SurfaceView</a>, coupled with a <a href="http://codesearch.google.com/codesearch#uX1GffpyOZk/media/java/android/media/MediaPlayer.java&amp;q=package:android.git.kernel.org%20file:android/media/MediaPlayer.java&amp;l=1" rel="noreferrer">MediaPlayer</a>, with a basic management of player's state machine.</p> <p>Actually, the real 'draw' work seems to be handled by native methods in mediaPlayer (a.k.a. the real player engine implementation on your android device)</p> <p>We've tested animations on different devices, and found that VideoView's underlying video player behavior/implementation isn't the same among different Android Devices :</p> <ul> <li>some devices handle player's view animations correctly</li> <li>others DON'T, and just display blur, black screen, or buggy display...</li> </ul> <p>On top of that, VideoView seems to be written directly on memory, so any 'workaround' (like putting an opaque view in front, and setting an animation on that view) doesn't seem to work.</p> <p>I'd be glad to have others feedback on this :)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload