Revert of Expose effective connection type to Cronet

Revert of Expose effective connection type to Cronet (patchset #6 id:200001 of https://codereview.chromium.org/2146563002/ )

Reason for revert:
Speculative revert to see if this fixes failing tests on ClangToTWin(dbg) tester:
https://build.chromium.org/p/chromium.fyi/builders/ClangToTWin%28dbg%29%20tester/builds/2913

Original issue's description:
> Expose effective connection type to Cronet
>
> CronetURLContextAdapter registers as an Effective Connection
> Type (ECT) Observer. When it receives notifications on
> network thread about changes in ECT, it passes them to
> Java land where ECT is stored in a guarded variable.
>
> ECT is computed using transport RTT and downlink bandwidth.
> This CL also adds default transport RTT thresholds for
> different effective connection types so that NQE can
> compute ECT when thresholds have not been specified using
> field trial params (as is the case for Cronet).
>
> BUG=625305
>
> Committed: https://crrev.com/16cad789693aa8032dec86a8585e0dcec5f6124e
> Cr-Commit-Position: refs/heads/master@{#409624}

TBR=ryansturm@chromium.org,xunjieli@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=625305
Committed: https://crrev.com/aa64633ecf68180fe381a0b5c31b874d4aab7ee8
Cr-Commit-Position: refs/heads/master@{#409873}

[tbansal1, 2016-08-04 19:45:10]

The CQ bit was checked by tbansal@chromium.org

[tbansal1, 2016-08-04 19:45:11]

Created Revert of Expose effective connection type to Cronet

[commit-bot: I haz the power, 2016-08-04 19:45:42]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[xunjieli, 2016-08-04 19:47:30]

lgtm. Tarun: when relanding your CL, could you rebase it on top of
https://codereview.chromium.org/2210633002/ and get rid of the manually created
EffectiveConnectionType.java and rename ChromiumEffectiveConnectionType.java ->
EffectiveConnectionType.java ? The last step is to add
EffectiveConnectionType.java to Cronet's source and api jars in BUILD.gn.

[commit-bot: I haz the power, 2016-08-04 19:47:51]

Description was changed from

==========
Revert of Expose effective connection type to Cronet (patchset #6 id:200001 of
https://codereview.chromium.org/2146563002/ )

Reason for revert:
Speculative revert to see if this fixes failing tests on ClangToTWin(dbg)
tester:
https://build.chromium.org/p/chromium.fyi/builders/ClangToTWin%28dbg%29%20tes...

Original issue's description:
> Expose effective connection type to Cronet
> 
> CronetURLContextAdapter registers as an Effective Connection
> Type (ECT) Observer. When it receives notifications on
> network thread about changes in ECT, it passes them to
> Java land where ECT is stored in a guarded variable.
> 
> ECT is computed using transport RTT and downlink bandwidth.
> This CL also adds default transport RTT thresholds for
> different effective connection types so that NQE can
> compute ECT when thresholds have not been specified using
> field trial params (as is the case for Cronet).
> 
> BUG=625305
> 
> Committed: https://crrev.com/16cad789693aa8032dec86a8585e0dcec5f6124e
> Cr-Commit-Position: refs/heads/master@{#409624}

TBR=ryansturm@chromium.org,xunjieli@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=625305
==========

to

==========
Revert of Expose effective connection type to Cronet (patchset #6 id:200001 of
https://codereview.chromium.org/2146563002/ )

Reason for revert:
Speculative revert to see if this fixes failing tests on ClangToTWin(dbg)
tester:
https://build.chromium.org/p/chromium.fyi/builders/ClangToTWin%28dbg%29%20tes...

Original issue's description:
> Expose effective connection type to Cronet
> 
> CronetURLContextAdapter registers as an Effective Connection
> Type (ECT) Observer. When it receives notifications on
> network thread about changes in ECT, it passes them to
> Java land where ECT is stored in a guarded variable.
> 
> ECT is computed using transport RTT and downlink bandwidth.
> This CL also adds default transport RTT thresholds for
> different effective connection types so that NQE can
> compute ECT when thresholds have not been specified using
> field trial params (as is the case for Cronet).
> 
> BUG=625305
> 
> Committed: https://crrev.com/16cad789693aa8032dec86a8585e0dcec5f6124e
> Cr-Commit-Position: refs/heads/master@{#409624}

TBR=ryansturm@chromium.org,xunjieli@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=625305
==========

[commit-bot: I haz the power, 2016-08-04 19:47:52]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-04 19:51:27]

Description was changed from

==========
Revert of Expose effective connection type to Cronet (patchset #6 id:200001 of
https://codereview.chromium.org/2146563002/ )

Reason for revert:
Speculative revert to see if this fixes failing tests on ClangToTWin(dbg)
tester:
https://build.chromium.org/p/chromium.fyi/builders/ClangToTWin%28dbg%29%20tes...

Original issue's description:
> Expose effective connection type to Cronet
> 
> CronetURLContextAdapter registers as an Effective Connection
> Type (ECT) Observer. When it receives notifications on
> network thread about changes in ECT, it passes them to
> Java land where ECT is stored in a guarded variable.
> 
> ECT is computed using transport RTT and downlink bandwidth.
> This CL also adds default transport RTT thresholds for
> different effective connection types so that NQE can
> compute ECT when thresholds have not been specified using
> field trial params (as is the case for Cronet).
> 
> BUG=625305
> 
> Committed: https://crrev.com/16cad789693aa8032dec86a8585e0dcec5f6124e
> Cr-Commit-Position: refs/heads/master@{#409624}

TBR=ryansturm@chromium.org,xunjieli@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=625305
==========

to

==========
Revert of Expose effective connection type to Cronet (patchset #6 id:200001 of
https://codereview.chromium.org/2146563002/ )

Reason for revert:
Speculative revert to see if this fixes failing tests on ClangToTWin(dbg)
tester:
https://build.chromium.org/p/chromium.fyi/builders/ClangToTWin%28dbg%29%20tes...

Original issue's description:
> Expose effective connection type to Cronet
>
> CronetURLContextAdapter registers as an Effective Connection
> Type (ECT) Observer. When it receives notifications on
> network thread about changes in ECT, it passes them to
> Java land where ECT is stored in a guarded variable.
>
> ECT is computed using transport RTT and downlink bandwidth.
> This CL also adds default transport RTT thresholds for
> different effective connection types so that NQE can
> compute ECT when thresholds have not been specified using
> field trial params (as is the case for Cronet).
>
> BUG=625305
>
> Committed: https://crrev.com/16cad789693aa8032dec86a8585e0dcec5f6124e
> Cr-Commit-Position: refs/heads/master@{#409624}

TBR=ryansturm@chromium.org,xunjieli@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=625305

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

[commit-bot: I haz the power, 2016-08-04 19:51:28]

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