[EasyUnlock] Update ProximityMonitor to only check for RSSI proximity.

[EasyUnlock] Update ProximityMonitor to only check for RSSI proximity.

This CL also changes UnlockManager to use the new interface for ProximityMonitor.

Review-Url: https://codereview.chromium.org/2845433003
Cr-Commit-Position: refs/heads/master@{#467860}
Committed: https://chromium.googlesource.com/chromium/src/+/bfabbfb6a32d7f654aad1ab45f5d233445db1b21

[Tim Song, 2017-04-26 17:40:26]

Description was changed from

==========
[EasyUnlock] Update ProximityMonitor to only check for RSSI proximity.
==========

to

==========
[EasyUnlock] Update ProximityMonitor to only check for RSSI proximity.

This CL also changes UnlockManager to use the new interface for
ProximityMonitor.
==========

[Tim Song, 2017-04-26 18:13:11]

Patchset #1 (id:1) has been deleted

[Tim Song, 2017-04-26 18:13:18]

Patchset #1 (id:20001) has been deleted

[Tim Song, 2017-04-26 18:13:23]

Patchset #1 (id:40001) has been deleted

[Tim Song, 2017-04-26 18:13:37]

tengs@chromium.org changed reviewers:
+ sacomoto@chromium.org

[sacomoto, 2017-04-27 20:10:03]

LGTM.

https://codereview.chromium.org/2845433003/diff/60001/components/proximity_au...
File components/proximity_auth/proximity_monitor_impl.h (right):

https://codereview.chromium.org/2845433003/diff/60001/components/proximity_au...
components/proximity_auth/proximity_monitor_impl.h:115:
std::unique_ptr<base::TimeTicks> last_zero_rssi_timestamp_;
This is not relevant anymore, right? For BLE we won't see a 0 RSSI, not the
device will try to adjust their transmit power.

Can you remove it?

[Tim Song, 2017-04-28 00:27:26]

https://codereview.chromium.org/2845433003/diff/60001/components/proximity_au...
File components/proximity_auth/proximity_monitor_impl.h (right):

https://codereview.chromium.org/2845433003/diff/60001/components/proximity_au...
components/proximity_auth/proximity_monitor_impl.h:115:
std::unique_ptr<base::TimeTicks> last_zero_rssi_timestamp_;
On 2017/04/27 20:10:03, sacomoto wrote:
> This is not relevant anymore, right? For BLE we won't see a 0 RSSI, not the
> device will try to adjust their transmit power.
> 
> Can you remove it?

Done.

[Tim Song, 2017-04-28 01:38:55]

The CQ bit was checked by tengs@chromium.org

[Tim Song, 2017-04-28 01:38:56]

The patchset sent to the CQ was uploaded after l-g-t-m from
sacomoto@chromium.org
Link to the patchset: https://codereview.chromium.org/2845433003/#ps80001
(title: "fixes")

[commit-bot: I haz the power, 2017-04-28 01:40:31]

CQ is trying da patch.

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

[commit-bot: I haz the power, 2017-04-28 02:58:36]

CQ is committing da patch.

Bot data: {"patchset_id": 80001, "attempt_start_ts": 1493343535884990,
"parent_rev": "97681b526480ec96c009d815b5bd32899587ea60", "commit_rev":
"bfabbfb6a32d7f654aad1ab45f5d233445db1b21"}

[commit-bot: I haz the power, 2017-04-28 02:58:43]

Description was changed from

==========
[EasyUnlock] Update ProximityMonitor to only check for RSSI proximity.

This CL also changes UnlockManager to use the new interface for
ProximityMonitor.
==========

to

==========
[EasyUnlock] Update ProximityMonitor to only check for RSSI proximity.

This CL also changes UnlockManager to use the new interface for
ProximityMonitor.

Review-Url: https://codereview.chromium.org/2845433003
Cr-Commit-Position: refs/heads/master@{#467860}
Committed:
https://chromium.googlesource.com/chromium/src/+/bfabbfb6a32d7f654aad1ab45f5d...
==========

[commit-bot: I haz the power, 2017-04-28 02:58:44]

Committed patchset #2 (id:80001) as
https://chromium.googlesource.com/chromium/src/+/bfabbfb6a32d7f654aad1ab45f5d...