Android VideoCapturer: Send ByteBuffer instead of byte[]

talk/app/webrtc/androidtests/src/org/webrtc/VideoCapturerAndroidTest.java

Index: talk/app/webrtc/androidtests/src/org/webrtc/VideoCapturerAndroidTest.java
diff --git a/talk/app/webrtc/androidtests/src/org/webrtc/VideoCapturerAndroidTest.java b/talk/app/webrtc/androidtests/src/org/webrtc/VideoCapturerAndroidTest.java
index 0fe827d1f9c658151dd05cb10edf0106e218700d..73ed381ad9ce65a2060eb5f3be8dea6ba88be098 100644
--- a/talk/app/webrtc/androidtests/src/org/webrtc/VideoCapturerAndroidTest.java
+++ b/talk/app/webrtc/androidtests/src/org/webrtc/VideoCapturerAndroidTest.java
@@ -35,6 +35,7 @@ import android.util.Size;
 import org.webrtc.CameraEnumerationAndroid.CaptureFormat;
 import org.webrtc.VideoRenderer.I420Frame;
 
+import java.nio.ByteBuffer;
 import java.util.ArrayList;
 import java.util.HashSet;
 import java.util.List;
@@ -104,11 +105,11 @@ public class VideoCapturerAndroidTest extends ActivityTestCase {
     }
 
     @Override
-    public void OnFrameCaptured(byte[] frame, int length, int width, int height,
+    public void OnFrameCaptured(ByteBuffer frame, int width, int height,
         int rotation, long timeStamp) {
       synchronized (frameLock) {
         ++framesCaptured;
-        frameSize = length;
+        frameSize = frame.capacity();

[hbos, 2015/09/28 12:35:51]

Should limit() be used instead of capacity()?
Or maybe not if we are doing JNI magic with GetDirectBufferCapacity...?

[magjed_webrtc, 2015/09/28 14:42:42]

I know for sure that capacity() is exactly like previous |length|. I'm not sure
if limit() is set at all. We just send a byte[] to the camera, so I don't think
the marker in the ByteBuffer is touched at all.

         timestamps.add(timeStamp);
         frameLock.notify();
       }