Enable RSSI proximity check by default.

chrome/browser/extensions/api/easy_unlock_private/easy_unlock_private_api.cc

Index: chrome/browser/extensions/api/easy_unlock_private/easy_unlock_private_api.cc
diff --git a/chrome/browser/extensions/api/easy_unlock_private/easy_unlock_private_api.cc b/chrome/browser/extensions/api/easy_unlock_private/easy_unlock_private_api.cc
index d2aa388f9a21a4b5650fe73e2f3bc25d777811fd..fd4e97d7f46115a5023083182ebf8a4c139f3859 100644
--- a/chrome/browser/extensions/api/easy_unlock_private/easy_unlock_private_api.cc
+++ b/chrome/browser/extensions/api/easy_unlock_private/easy_unlock_private_api.cc
@@ -700,13 +700,6 @@ EasyUnlockPrivateGetConnectionInfoFunction::
 
 bool EasyUnlockPrivateGetConnectionInfoFunction::DoWork(
     scoped_refptr<device::BluetoothAdapter> adapter) {
-  if (!base::CommandLine::ForCurrentProcess()->HasSwitch(
-        proximity_auth::switches::kEnableProximityDetection)) {
-    SetError("Turn on 'enable-easy-unlock-proximity-detection' flag.");
-    SendResponse(false);
-    return true;
-  }

[Ilya Sherman, 2015/02/05 23:59:41]

Please remove the flag as well.  Or, if we're not 100% sure yet about whether we
want the flag or not, let's just flip the default value from disabled to enabled
(i.e. keep a disable flag).

[Tim Song, 2015/02/06 00:43:01]

I'll do that in another CL. Basically, I want to decouple the RSSI and TX power
checks from being under the same flag.

-
   scoped_ptr<easy_unlock_private::GetConnectionInfo::Params> params =
       easy_unlock_private::GetConnectionInfo::Params::Create(*args_);
   EXTENSION_FUNCTION_VALIDATE(params);