CDD: Require writing LMK_KILL_OCCURRED_FIELD_NUMBER to the statsd log
when an app is terminated by the Low Memory Killer.
- This will enable reporting to developers if their apps are frequently
killed by the Low Memory Killer.
Bug: 148611927
Change-Id: I8499925c9af9772c7bfc5478a4fed347274531a1
Test: Manual
diff --git a/6_dev-tools-and-options/6_1_developer_tools.md b/6_dev-tools-and-options/6_1_developer_tools.md
index 8045e8e..33e6df1 100644
--- a/6_dev-tools-and-options/6_1_developer_tools.md
+++ b/6_dev-tools-and-options/6_1_developer_tools.md
@@ -98,7 +98,10 @@
* [C-SR] Are STRONGLY RECOMMENDED to provide, through the perfetto binary,
at least the data sources described in [the perfetto documentation](
https://developer.android.com/studio/command-line/perfetto).
-
+* [**Low Memory Killer**](https://source.android.com/devices/tech/perf/lmkd)
+ * [C-0-10] MUST write a `LMK_KILL_OCCURRED_FIELD_NUMBER` Atom to the
+ statsd log when an app is terminated by the [Low Memory Killer](
+ https://source.android.com/devices/tech/perf/lmkd).
* [**Test Harness Mode**](https://source.android.com/compatibility/cts/harness)
If device implementations support the shell command `cmd testharness` and
run `cmd testharness enable`, they:
