aboutsummaryrefslogtreecommitdiff
path: root/en/devices/input/migration-guide.html
diff options
context:
space:
mode:
Diffstat (limited to 'en/devices/input/migration-guide.html')
-rw-r--r--en/devices/input/migration-guide.html5
1 files changed, 3 insertions, 2 deletions
diff --git a/en/devices/input/migration-guide.html b/en/devices/input/migration-guide.html
index 4ddc8274..6f50f004 100644
--- a/en/devices/input/migration-guide.html
+++ b/en/devices/input/migration-guide.html
@@ -44,8 +44,9 @@ USB product id / vendor id or by device name.</p>
function input devices. These files should simple contain a line to set
the keyboard type to <code>SPECIAL_FUNCTION</code>.</p>
<p>A good way to ensure that all built-in input devices are appropriately configured
-is to run <a href="dumpsys.html">Dumpsys</a> and look for devices that
-are inappropriately using <code>Generic.kcm</code>.</p>
+is to run <a
+ href="https://developer.android.com/studio/command-line/dumpsys.html">Dumpsys</a>
+and look for devices that are inappropriately using <code>Generic.kcm</code>.</p>
<h2 id="migrating-to-android-honeycomb-32">Migrating to Android Honeycomb 3.2</h2>
<p>In Honeycomb 3.2, we added support for joysticks and extended the key layout file
format to enable joystick axis mapping.</p>