Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(370)

Unified Diff: components/proximity_auth/screenlock_state.h

Issue 2898513002: [EasyUnlock] Observe proximity changes and clean up TX power strategy. (Closed)
Patch Set: Created 3 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: components/proximity_auth/screenlock_state.h
diff --git a/components/proximity_auth/screenlock_state.h b/components/proximity_auth/screenlock_state.h
index 7ba06593e7bb417e6e994d5f8e6bc03df8a28e13..84667a73681b4633729ec36fcd15111543654be2 100644
--- a/components/proximity_auth/screenlock_state.h
+++ b/components/proximity_auth/screenlock_state.h
@@ -34,16 +34,11 @@ enum class ScreenlockState {
// signal strength is too low, i.e. the phone is roughly more than 30 feet
// away, and therefore is not allowed to unlock the device.
RSSI_TOO_LOW,
- // A phone eligible to unlock the local device is found, but the local
- // device's transmission power is too high, indicating that the phone is
- // (probably) more than 1 foot away, and therefore is not allowed to unlock
- // the device.
- TX_POWER_TOO_HIGH,
// A phone eligible to unlock the local device is found; but (a) the phone is
// locked, and (b) the local device's transmission power is too high,
// indicating that the phone is (probably) more than 1 foot away, and
// therefore is not allowed to unlock the device.
- PHONE_LOCKED_AND_TX_POWER_TOO_HIGH,
+ PHONE_LOCKED_AND_RSSI_TOO_LOW,
// The local device can be unlocked using proximity-based authentication.
AUTHENTICATED,
};

Powered by Google App Engine
This is Rietveld 408576698