[Bootstrapping] Introduce an accelerator to put a ChromeOS device into Slave OOBE process.

chrome/browser/chromeos/login/wizard_controller.cc

Index: chrome/browser/chromeos/login/wizard_controller.cc
diff --git a/chrome/browser/chromeos/login/wizard_controller.cc b/chrome/browser/chromeos/login/wizard_controller.cc
index 33b223df551dc0ca3b2d0d1827153987c2deba47..336c2fe3a32ad47ae6b67dfadee44d9bafc773c1 100644
--- a/chrome/browser/chromeos/login/wizard_controller.cc
+++ b/chrome/browser/chromeos/login/wizard_controller.cc
@@ -166,6 +166,12 @@ void SetControllerDetectedPref(bool value) {
   prefs->CommitPendingWrite();
 }
 
+// Checks if the device is a "slave" device in the bootstrapping process.
+bool IsBootstrappingSlave() {
+  return g_browser_process->local_state()->GetBoolean(
+      prefs::kOobeBootstrappingRole);
+}
+
 // Checks if the device is a "Master" device in the bootstrapping process.
 bool IsBootstrappingMaster() {
   return base::CommandLine::ForCurrentProcess()->HasSwitch(
@@ -430,7 +436,8 @@ void WizardController::ShowNetworkScreen() {
   SetStatusAreaVisible(HasScreen(kNetworkScreenName));
   SetCurrentScreen(GetScreen(kNetworkScreenName));
 
-  MaybeStartListeningForSharkConnection();
+  if (IsBootstrappingSlave())

[xdai1, 2016/10/03 21:08:00]

There are two possible screens where we listen to the incoming Bluetooth
connection request: the first one is the HID detection screen, which will show
up when there is no sufficient input devices. In this case, we just keep the
logic as it is today: always put the Bluetooth is discoverable mode. The other
place is the Network screen, which will show up when there are input devices
detected. In this case, we disable the Bluetooth by default until the user
explicitly enable it by pressing a key combo. 

[achuithb, 2016/10/05 22:24:10]

Could you please add a comment here stating this?

[xdai1, 2016/10/05 23:57:29]

Done.

+    MaybeStartListeningForSharkConnection();
 }
 
 void WizardController::ShowLoginScreen(const LoginScreenContext& context) {