Slightly more gracefully handle ADB failures with locked devices

It still fails, but the screen now turns on and shows as locked,
which makes that a little clearer, and avoids a complete no-op.

Author: pimterry

src/interceptors/android/adb-commands.ts

@@ -243,12 +243,22 @@ export async function injectSystemCertificate(
     await run(adbClient, deviceId, rootCmd.concat('sh', injectionScriptPath));
 }
 
-export function bringToFront(
+export async function bringToFront(
     adbClient: adb.AdbClient,
     deviceId: string,
     activityName: string // Of the form: com.package/com.package.YourActivity
 ) {
-    return adbClient.shell(deviceId, [
+    // Wake the device up, so it's at least obviously locked if locked.
+    // It's not possible to unlock the device over ADB. Does nothing if already awake.
+    await adbClient.shell(deviceId, [
+        "input", "keyevent", "KEYCODE_WAKEUP"
+    ]);
+
+    await delay(10);
+
+    // Bring the activity to the front, so we can interact with it (this will
+    // silently fail if the device is locked, but we're ok with that).
+    await adbClient.shell(deviceId, [
         "am", "start", "--activity-single-top", activityName
     ]);
 }