Fix android_action_runner.InputSwipe and InputText

telemetry/telemetry/core/android_action_runner.py

Index: telemetry/telemetry/core/android_action_runner.py
diff --git a/telemetry/telemetry/core/android_action_runner.py b/telemetry/telemetry/core/android_action_runner.py
index 07fdccb71d5f7fbd24fe7cd08058013f44569ac5..905e957988447ac1452a502456d0277b8f5b1343 100644
--- a/telemetry/telemetry/core/android_action_runner.py
+++ b/telemetry/telemetry/core/android_action_runner.py
@@ -70,8 +70,14 @@ class AndroidActionRunner(object):
     Args:
       string: The string to send to the device.
     """
-    self._platform_backend.device.RunShellCommand(
-        ['input', 'text', string], check_return=True)
+    # Spaces should be input as keyevents. Pass space character to account for

[rnephew (Reviews Here), 2017/04/26 00:28:25]

Can this we slightly reworded? I dont think its currently clear that we have to
do this because input text 'words_here' does not accept spaces as an input. 

Also, is it that it can't accept spaces as input or are we improperly formatting
the string/list_of_strings being sent to RunShellCommand? This causes multiple
back and forth messages with the devices via adb. We try to minimize these as
much as possible because each time we do it it makes it less realistic and also
increases friction points during runs.

Just trying to get up to speed on the problem. 

[ssid, 2017/04/26 00:36:46]

Sorry for not being clear. The input text command does not accept spaces as
input. On adding spaces to the input the command fails. This is irrespective of
the formatting.

But, this used to work on Android O and some builds of N with spaces. That is
why the benchmark was passing on the cq. But, we still have bots on the older
version which are failing. Maybe a better solution would be to check for version
here? I did not make a version check here because I can't tell which version the
space input was fixed.

[rnephew (Reviews Here), 2017/04/26 01:01:26]

I dont think the added code complexity for gating on version will be necessary.
Unless you foresee us sending a lot of long sentences with many spaces in it via
this command. We should just keep an eye out and if it causes regressions (seems
highly highly unlikely) investigate further. I mostly just wanted to make we are
fully thinking out the implications of changing InputText to work like this.

Maybe just making the comment a little more concrete like:
# Space must be input as key events since 'input text <text>' does not work with
space. Pass space....

[ssid, 2017/04/26 01:12:45]

Done.

+    # strings with multiple spaces.
+    words = string.split(' ')
+    for i in range(0, len(words)):
+      if i is not 0:
+        self.InputKeyEvent(keyevent.KEYCODE_SPACE)
+      self._platform_backend.device.RunShellCommand(
+          ['input', 'text', words[i]], check_return=True)
 
   def InputKeyEvent(self, keycode):
     """Send a single key input to the device.
@@ -105,7 +111,7 @@ class AndroidActionRunner(object):
       duration: The length of time of the swipe in milliseconds
     """
     cmd = ['input', 'swipe']
-    cmd.expand(str(x) for x in (left_start_coord, top_start_coord,
+    cmd.extend(str(x) for x in (left_start_coord, top_start_coord,
                                 left_end_coord, top_end_coord, duration))
     self._platform_backend.device.RunShellCommand(cmd, check_return=True)