Update incremental install docs.

docs/android_build_instructions.md

 # Checking out and building Chromium for Android
 
-There are instructions for other platforms linked from the 
+There are instructions for other platforms linked from the
 [get the code](get_the_code.md) page.
 
 ## Instructions for Google Employees
 
 Are you a Google employee? See
 [go/building-chrome](https://goto.google.com/building-chrome) instead.
 Google employee? See [go/building-chrome](https://goto.google.com/building-chrome) instead.
 
 [TOC]
 
@@ skipping 290 matching lines @@
 See [Debugging Chromium on Android](https://www.chromium.org/developers/how-tos/debugging-on-android)
 for more on debugging, including how to debug Java code.
 
 ### Testing
 
 For information on running tests, see [android\_test\_instructions.md](https://chromium.googlesource.com/chromium/src/+/master/docs/android_test_instructions.md).
 
 ### Faster Edit/Deploy (GN only)
 
 GN's "incremental install" uses reflection and side-loading to speed up the edit
-& deploy cycle (normally < 10 seconds).
+& deploy cycle (normally < 10 seconds). The initial launch of the apk will be
+a little slower since updated dex files are installed manually.
 
 *   Make sure to set` is_component_build = true `in your GN args
 *   All apk targets have \*`_incremental` targets defined (e.g.
-    `chrome_public_apk_incremental`)
+    `chrome_public_apk_incremental`) except for Webview and Monochrome
 
 Here's an example:
 
 ```shell
 ninja -C out/Default chrome_public_apk_incremental
 out/Default/bin/install_chrome_public_apk_incremental -v
 ```
 
 For gunit tests (note that run_*_incremental automatically add
 --fast-local-dev when calling test\_runner.py):
 
 ```shell
 ninja -C out/Default base_unittests_incremental
 out/Default/bin/run_base_unittests_incremental
 ```
 
 For instrumentation tests:
 
 ```shell
 ninja -C out/Default chrome_public_test_apk_incremental
 out/Default/bin/run_chrome_public_test_apk_incremental
 ```
 
 To uninstall:
 
 ```shell
 out/Default/bin/install_chrome_public_apk_incremental -v --uninstall
 ```
 
+A subtly erroneous flow arises when you build a regular apk but install an
+incremental apk (e.g.
+```ninja -C out/Default foo_apk out/Default/bin/install_foo_apk_incremental```).

[agrieve, 2017/01/05 16:26:40]

nit: these commands need either a && or a ; to separate the two.

Also - should use a single ` for an inline snippet

[estevenson, 2017/01/05 16:36:48]

Done.

+Setting incremental_apk_by_default = true in your GN args aliases regular

[agrieve, 2017/01/05 16:26:39]

nit: add `` arround incremental_apk_by_default = true

[estevenson, 2017/01/05 16:36:47]

Done.

+targets as their incremental counterparts. With this arg set, the commands
+above become:
+
+```shell
+ninja -C out/Default chrome_public_apk
+out/Default/bin/install_chrome_public_apk
+
+ninja -C out/Default base_unittests
+out/Default/bin/run_base_unittests
+
+ninja -C out/Default chrome_public_test_apk
+out/Default/bin/run_chrome_public_test_apk
+```
+
+If you want to build a non-incremental apk you'll need to remove
+```incremental_apk_by_default``` from your GN args.
+
 ## Tips, tricks, and troubleshooting
 
 ### Rebuilding libchrome.so for a particular release
 
 These instructions are only necessary for Chrome 51 and earlier.
 
 In the case where you want to modify the native code for an existing
 release of Chrome for Android (v25+) you can do the following steps.
 Note that in order to get your changes into the official release, you'll
 need to send your change for a codereview using the regular process for
 committing code to chromium.
 
 1.  Open Chrome on your Android device and visit chrome://version
 2.  Copy down the id listed next to "Build ID:"
 3.  Go to
     [http://storage.googleapis.com/chrome-browser-components/BUILD\_ID\_FROM\_STEP\_2/index.html](http://storage.googleapis.com/chrome-browser-components/BUILD_ID_FROM_STEP_2/index.html)
 4.  Download the listed files and follow the steps in the README.