From db1b888188952547d6ce678a5aea2ea39fabe404 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Vladim=C3=ADr=20Vondru=C5=A1?= <mosra@centrum.cz>
Date: Sun, 24 Mar 2019 17:28:14 +0100
Subject: [PATCH] doc: mention ADB and multiple connected Android devices.

---
 doc/platforms-android.dox | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/platforms-android.dox b/doc/platforms-android.dox
index 4d5ee2f1b..fffdde5bf 100644
--- a/doc/platforms-android.dox
+++ b/doc/platforms-android.dox
@@ -742,6 +742,25 @@ gradle build
 
 @section platforms-android-troubleshooting Troubleshooting
 
+@subsection platforms-android-troubleshooting-multiple-devices ADB fails when more devices are connected
+
+If any `adb` command fails with
+
+@code{.shell-session}
+error: more than one device/emulator
+@endcode
+
+@m_class{m-noindent}
+
+you can pass the device ID via the `-s` parameter to each command. That is,
+however, verbose and doesn't work for example in case of running
+@ref Corrade::TestSuite tests via `ctest`. Instead, it's possible to supply
+the device ID via an environment variable, for example:
+
+@code{.sh}
+export ANDROID_SERIAL="bla"
+@endcode
+
 @subsection platforms-android-troubleshooting-signing-failed Signing the APK using CMake fails
 
 At the moment the location and passphrase for the Android signing keystore is