docs/defines.md: admit to `ANDROID` too.
Writing this, I think I deliberately left it off because it's rarely useful. But it does exist, and should be documented somewhere --- if only because it's very different from the similarly-spelled `__ANDROID__`.
Change-Id: I37cf36b319ed1198b5944593101c747f430182eb
diff --git a/docs/defines.md b/docs/defines.md
index 65cc873..be48ad8 100644
--- a/docs/defines.md
+++ b/docs/defines.md
@@ -21,6 +21,15 @@
Genuine cases are quite rare, and `__BIONIC__` is often more specific (but
remember that it is possible -- if unusual -- to use bionic on the host).
+## `ANDROID` (rarely useful)
+
+Not to be confused with `__ANDROID__`, the similar-looking but very different
+`ANDROID` is _not_ set by the toolchain or NDK build system. This is set by
+the AOSP build system for both device and host code. For that reason, it's
+not typically very useful except as a signal when patching third-party code ---
+but even then, you'd typically _not_ want this because it's true for both
+device and host.
+
## `__ANDROID_API__`
If your code can be built targeting a variety of different OS versions, use