Events refactor in Android session based capturing.

webrtc/api/android/java/src/org/webrtc/CameraVideoCapturer.java

Index: webrtc/api/android/java/src/org/webrtc/CameraVideoCapturer.java
diff --git a/webrtc/api/android/java/src/org/webrtc/CameraVideoCapturer.java b/webrtc/api/android/java/src/org/webrtc/CameraVideoCapturer.java
index 43513055fae7cffee915da11941e0bdf03202e3d..a53935621ffa02129cb46077682a664d5f4b22e9 100644
--- a/webrtc/api/android/java/src/org/webrtc/CameraVideoCapturer.java
+++ b/webrtc/api/android/java/src/org/webrtc/CameraVideoCapturer.java
@@ -121,7 +121,6 @@ public interface CameraVideoCapturer extends VideoCapturer {
     }
 
     public void release() {
-      checkThread();

[magjed_webrtc, 2016/09/15 14:58:06]

Do we call this on another thread now? Is that safe?

[sakal, 2016/09/15 15:08:18]

Yes, we do. It is called from the thread that calls stopCapture. I don't see why
this method wouldn't be thread safe. surfaceTextureHelper is final member.
Handler is final member in surfaceTextureHelper. cameraObserver is final member.
removeCallbacks should be safe to call on multiple threads.

       surfaceTextureHelper.getHandler().removeCallbacks(cameraObserver);
     }
   }