Remove latency-based frame dropping on Android.

Remove latency-based frame dropping on Android.

This logic currently prevents loopback calls on Nexus 5X when it's
slightly overloaded to maintain input framerate since encoding at ~25fps
with one framedrop results in >70ms between frames naturally.

With this change applied Nexus 5X can maintain ~25fps both in and out
without building excessive latency (>2 frames) (this is now covered by
CPU adaptation outside the codec wrapper).

BUG=
R=glaznev@webrtc.org

Committed: https://chromium.googlesource.com/external/webrtc/+/f7704d197b16ec4df06b6353daeea3da0f3c090b

[pbos-webrtc, 2016-04-06 14:51:31]

PTAL, this fixes Nexus 5X loopback performance (though it's still CPU loaded,
and has trouble maintaining 30fps in).

[AlexG, 2016-04-06 19:30:41]

lgtm

Please also consider an option to boost latency threshold to 150 ms - it may bee
too risky to remove latency check at all

[pbos-webrtc, 2016-04-11 14:41:32]

Description was changed from

==========
Remove latency-based frame dropping on Android.

This logic currently prevents loopback calls on Nexus 5X when it's
slightly overloaded to maintain input framerate since encoding at ~25fps
with one framedrop results in >70ms between frames naturally.

With this change applied Nexus 5X can maintain ~25fps both in and out
without building excessive latency (>2 frames) (this is now covered by
CPU adaptation outside the codec wrapper).

BUG=
R=glaznev@webrtc.org, stefan@webrtc.org
==========

to

==========
Remove latency-based frame dropping on Android.

This logic currently prevents loopback calls on Nexus 5X when it's
slightly overloaded to maintain input framerate since encoding at ~25fps
with one framedrop results in >70ms between frames naturally.

With this change applied Nexus 5X can maintain ~25fps both in and out
without building excessive latency (>2 frames) (this is now covered by
CPU adaptation outside the codec wrapper).

BUG=
R=glaznev@webrtc.org
==========

[pbos-webrtc, 2016-04-11 14:42:34]

On 2016/04/06 19:30:41, AlexG wrote:
> lgtm
> 
> Please also consider an option to boost latency threshold to 150 ms - it may
bee
> too risky to remove latency check at all

Latency check is covered by CPU adaptation (and capped to 90ms if I read it
correctly).

[commit-bot: I haz the power, 2016-04-11 14:42:51]

Description was changed from

==========
Remove latency-based frame dropping on Android.

This logic currently prevents loopback calls on Nexus 5X when it's
slightly overloaded to maintain input framerate since encoding at ~25fps
with one framedrop results in >70ms between frames naturally.

With this change applied Nexus 5X can maintain ~25fps both in and out
without building excessive latency (>2 frames) (this is now covered by
CPU adaptation outside the codec wrapper).

BUG=
R=glaznev@webrtc.org
==========

to

==========
Remove latency-based frame dropping on Android.

This logic currently prevents loopback calls on Nexus 5X when it's
slightly overloaded to maintain input framerate since encoding at ~25fps
with one framedrop results in >70ms between frames naturally.

With this change applied Nexus 5X can maintain ~25fps both in and out
without building excessive latency (>2 frames) (this is now covered by
CPU adaptation outside the codec wrapper).

BUG=
R=glaznev@webrtc.org

Committed: https://crrev.com/f7704d197b16ec4df06b6353daeea3da0f3c090b
Cr-Commit-Position: refs/heads/master@{#12317}
==========

[commit-bot: I haz the power, 2016-04-11 14:42:52]

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

[pbos-webrtc, 2016-04-11 14:42:54]

Description was changed from

==========
Remove latency-based frame dropping on Android.

This logic currently prevents loopback calls on Nexus 5X when it's
slightly overloaded to maintain input framerate since encoding at ~25fps
with one framedrop results in >70ms between frames naturally.

With this change applied Nexus 5X can maintain ~25fps both in and out
without building excessive latency (>2 frames) (this is now covered by
CPU adaptation outside the codec wrapper).

BUG=
R=glaznev@webrtc.org

Committed: https://crrev.com/f7704d197b16ec4df06b6353daeea3da0f3c090b
Cr-Commit-Position: refs/heads/master@{#12317}
==========

to

==========
Remove latency-based frame dropping on Android.

This logic currently prevents loopback calls on Nexus 5X when it's
slightly overloaded to maintain input framerate since encoding at ~25fps
with one framedrop results in >70ms between frames naturally.

With this change applied Nexus 5X can maintain ~25fps both in and out
without building excessive latency (>2 frames) (this is now covered by
CPU adaptation outside the codec wrapper).

BUG=
R=glaznev@webrtc.org

Committed:
https://chromium.googlesource.com/external/webrtc/+/f7704d197b16ec4df06b6353d...
==========

[pbos-webrtc, 2016-04-11 14:42:55]

Committed patchset #1 (id:1) manually as
f7704d197b16ec4df06b6353daeea3da0f3c090b (presubmit successful).