Revert of VideoCapturerAndroid: Use one thread per startCapture()/stopCapture() session

Revert of VideoCapturerAndroid: Use one thread per startCapture()/stopCapture() session (patchset #2 id:60001 of https://codereview.webrtc.org/1763673002/ )

Reason for revert:
Frame rate and freeze detection not working properly after switchCamera(). This is because the previous cameraObserver is not removed before posting a new one.

Original issue's description:
> VideoCapturerAndroid: Use one thread per startCapture()/stopCapture() session
>
> Currently, VideoCapturerAndroid sets the thread and handler in the ctor
> and clears them in dispose(). This CL sets the handler in startCapture()
> instead and clears it in stopCapture(). The purpose is to prepare for
> sending in the SurfaceTextureHelper in startCapture() instead of letting
> VideoCapturerAndroid create it in the ctor.
>
> All access to the handler is now synchronized by a lock, and all
> Runnables are posted with a token so that they can be removed all at
> once in stopCapture() to guarantee that no pending operation will be
> executed after stopCapture().
>
> BUG=webrtc:5519
>
> Committed: https://crrev.com/9cbebee523dbd280a4f67ad414a432ed730f241f
> Cr-Commit-Position: refs/heads/master@{#11939}

TBR=perkj@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=webrtc:5519
Committed: https://crrev.com/430a9c3bfde108063df2756a98e5ab59094234ed
Cr-Commit-Position: refs/heads/master@{#11941}

[magjed_webrtc, 2016-03-10 12:30:15]

Created Revert of VideoCapturerAndroid: Use one thread per
startCapture()/stopCapture() session

[commit-bot: I haz the power, 2016-03-10 12:30:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1777253002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1777253002/1

[commit-bot: I haz the power, 2016-03-10 12:30:33]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-10 12:30:40]

Description was changed from

==========
Revert of VideoCapturerAndroid: Use one thread per startCapture()/stopCapture()
session (patchset #2 id:60001 of https://codereview.webrtc.org/1763673002/ )

Reason for revert:
Frame rate and freeze detection not working properly after switchCamera(). This
is because the previous cameraObserver is not removed before posting a new one.

Original issue's description:
> VideoCapturerAndroid: Use one thread per startCapture()/stopCapture() session
> 
> Currently, VideoCapturerAndroid sets the thread and handler in the ctor
> and clears them in dispose(). This CL sets the handler in startCapture()
> instead and clears it in stopCapture(). The purpose is to prepare for
> sending in the SurfaceTextureHelper in startCapture() instead of letting
> VideoCapturerAndroid create it in the ctor.
> 
> All access to the handler is now synchronized by a lock, and all
> Runnables are posted with a token so that they can be removed all at
> once in stopCapture() to guarantee that no pending operation will be
> executed after stopCapture().
> 
> BUG=webrtc:5519
> 
> Committed: https://crrev.com/9cbebee523dbd280a4f67ad414a432ed730f241f
> Cr-Commit-Position: refs/heads/master@{#11939}

TBR=perkj@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=webrtc:5519
==========

to

==========
Revert of VideoCapturerAndroid: Use one thread per startCapture()/stopCapture()
session (patchset #2 id:60001 of https://codereview.webrtc.org/1763673002/ )

Reason for revert:
Frame rate and freeze detection not working properly after switchCamera(). This
is because the previous cameraObserver is not removed before posting a new one.

Original issue's description:
> VideoCapturerAndroid: Use one thread per startCapture()/stopCapture() session
>
> Currently, VideoCapturerAndroid sets the thread and handler in the ctor
> and clears them in dispose(). This CL sets the handler in startCapture()
> instead and clears it in stopCapture(). The purpose is to prepare for
> sending in the SurfaceTextureHelper in startCapture() instead of letting
> VideoCapturerAndroid create it in the ctor.
>
> All access to the handler is now synchronized by a lock, and all
> Runnables are posted with a token so that they can be removed all at
> once in stopCapture() to guarantee that no pending operation will be
> executed after stopCapture().
>
> BUG=webrtc:5519
>
> Committed: https://crrev.com/9cbebee523dbd280a4f67ad414a432ed730f241f
> Cr-Commit-Position: refs/heads/master@{#11939}

TBR=perkj@webrtc.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=webrtc:5519

Committed: https://crrev.com/430a9c3bfde108063df2756a98e5ab59094234ed
Cr-Commit-Position: refs/heads/master@{#11941}
==========

[commit-bot: I haz the power, 2016-03-10 12:30:41]

Patchset 1 (id:??) landed as
https://crrev.com/430a9c3bfde108063df2756a98e5ab59094234ed
Cr-Commit-Position: refs/heads/master@{#11941}