android_dynamic_feature_modules.md: onDemand="false" splits are always installed
Bug: 1241142
Change-Id: Ifdc10fc26e05659012c5e292c4babf1589a5cb26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3104366
Auto-Submit: Andrew Grieve <[email protected]>
Reviewed-by: Xing Liu <[email protected]>
Commit-Queue: Xing Liu <[email protected]>
Cr-Commit-Position: refs/heads/master@{#913133}
diff --git a/docs/android_dynamic_feature_modules.md b/docs/android_dynamic_feature_modules.md
index ff2c2281d..1d4440a 100644
--- a/docs/android_dynamic_feature_modules.md
+++ b/docs/android_dynamic_feature_modules.md
@@ -213,12 +213,14 @@
```shell
$ autoninja -C $OUTDIR monochrome_public_bundle
-$ $OUTDIR/bin/monochrome_public_bundle install -m base -m foo
+$ $OUTDIR/bin/monochrome_public_bundle install -m foo
```
-This will install Foo alongside the rest of Chrome. The rest of Chrome is called
-_base_ module in the bundle world. The base module will always be put on the
-device when initially installing Chrome.
+This will install the `Foo` module, the `base` module, and all modules with an
+`AndroidManifest.xml` that:
+ * Sets `<module dist:onDemand="false">`, or
+ * Has `<dist:delivery>` conditions that are satisfied by the device being
+ installed to.
*** note
**Note:** The install script may install more modules than you specify, e.g.
@@ -237,7 +239,7 @@
installed modules:
```shell
-$ $OUTDIR/bin/monochrome_public_bundle install -m base
+$ $OUTDIR/bin/monochrome_public_bundle install
$ adb shell dumpsys package org.chromium.chrome | grep splits
> splits=[base, config.en]
```
@@ -871,7 +873,7 @@
Fake-install and launch Chrome with the following command:
```shell
-$ $OUTDIR/bin/monochrome_public_bundle install -m base -f foo
+$ $OUTDIR/bin/monochrome_public_bundle install -f foo
$ $OUTDIR/bin/monochrome_public_bundle launch
```
