Flesh out GN/Android run docs.

site/user/quick/gn.md

Index: site/user/quick/gn.md
diff --git a/site/user/quick/gn.md b/site/user/quick/gn.md
index 22756a6f96c355c7c59866b2474e343a9b288022..6c63482be9b72bb71261c5b77c7515c52ae15761 100644
--- a/site/user/quick/gn.md
+++ b/site/user/quick/gn.md
@@ -81,9 +81,12 @@ desired `target_cpu`:
 Other arguments like `is_debug` and `is_component_build` continue to work.
 Tweaking `ndk_api` gives you access to newer Android features like Vulkan.
 
-To test on a locally connected Android device, you can use our `droid` convenience script:
+To test on an Android device, push the binary and `resources` over,
+and run it as normal.  You may find `bin/droid` convenient.
 
 <!--?prettify lang=sh?-->
 
     ninja -C out/arm64
-    bin/droid out/arm64/dm --src gm --config gpu
+    adb push out/arm64/dm /data/local/tmp
+    adb push resources /data/local/tmp

[csmartdalton, 2016/09/16 19:25:09]

Resources are specific to the dm binary itself as opposed to gn. Can we leave it
out?

 adb push out/arm64/dm /data/local/tmp
 adb shell "cd /data/local/tmp; ./dm --src gm --config gpu"

Seeing those two steps laid out I think it should be obvious that you are
responsible to put files where the program can find them. And if anybody does
forget to push the resources because they are following those steps, dm will
complain and remind them to do so.

[mtklein_C, 2016/09/16 19:30:56]

I see your point but every app we have to use as an example (dm, nanobench)
needs resources.  I'd rather not write instructions that fail.

+    adb shell "cd /data/local/tmp; ./dm --src gm --config gpu"