Revert of Enable dark_resume_always workaround if the wake-on-packets flag is set

chrome/browser/chromeos/power/light_bar.cc

Index: chrome/browser/chromeos/power/light_bar.cc
diff --git a/chrome/browser/chromeos/power/light_bar.cc b/chrome/browser/chromeos/power/light_bar.cc
index b6b9bcb0b8345ba490dbac8e7b7e76793d384da4..92c2033994547c714642c362bbe41c8980ff0ef9 100644
--- a/chrome/browser/chromeos/power/light_bar.cc
+++ b/chrome/browser/chromeos/power/light_bar.cc
@@ -22,29 +22,12 @@
     "lightbar/sequence";
 const char kKonamiCommand[] = "KONAMI";
 
-// TODO(chirantan): These are used by a temporary workaround for lucid sleep and
-// should be removed once the proper implementation is ready (crbug.com/414949).
-const char kDarkResumeAlwaysFile[] = "/sys/power/dark_resume_always";
-const char kEnableDarkResumeAlways[] = "1";
-
 }  // namespace
 
 LightBar::LightBar()
     : control_path_(base::FilePath(kLightBarControlPath)),
       has_light_bar_(base::PathIsWritable(control_path_)) {
   DBusThreadManager::Get()->GetPowerManagerClient()->AddObserver(this);
-
-  // Until the kernel can properly detect the wakeup source, we need to use a
-  // hack to tell the kernel to always enter dark resume.  Chrome can then
-  // detect any user activity and have the power manager transition out of dark
-  // resume into regular resume.  We don't care if the write succeeds or not
-  // because most devices will not have this file.
-  //
-  // TODO(chirantan): Remove this once we can properly detect the wakeup
-  // source (crbug.com/414949).
-  base::WriteFile(base::FilePath(kDarkResumeAlwaysFile),
-                  kEnableDarkResumeAlways,
-                  strlen(kEnableDarkResumeAlways));
 }
 
 LightBar::~LightBar() {