diff options
author | Clay Murphy <claym@google.com> | 2013-06-18 16:44:01 -0700 |
---|---|---|
committer | Clay Murphy <claym@google.com> | 2013-06-18 23:49:41 +0000 |
commit | 72bdea022dd76f7378ee311cdf3ac72c1c09909b (patch) | |
tree | f841cce295050fd5777d674a4baf71d4fb5a3332 | |
parent | d8fbf20170094f7e914296371a87cfdb57dc6999 (diff) | |
download | source.android.com-72bdea022dd76f7378ee311cdf3ac72c1c09909b.tar.gz |
docs: Repairing broken links from staging.
Bug: 9192223
Change-Id: I4579b4cc5a58785f4ade92a748a434e3f2806425
Staging location:
http://claym.mtv.corp.google.com:8082/index.html
-rw-r--r-- | src/devices/audio.jd | 2 | ||||
-rw-r--r-- | src/devices/camera.jd | 4 | ||||
-rw-r--r-- | src/devices/tech/input/input-device-configuration-files.jd | 2 | ||||
-rw-r--r-- | src/devices/tech/input/key-character-map-files.jd | 2 | ||||
-rw-r--r-- | src/devices/tech/input/key-layout-files.jd | 4 | ||||
-rw-r--r-- | src/devices/tech/input/keyboard-devices.jd | 10 | ||||
-rw-r--r-- | src/devices/tech/input/migration-guide.jd | 6 | ||||
-rw-r--r-- | src/devices/tech/input/touch-devices.jd | 2 | ||||
-rw-r--r-- | src/devices/tech/security/index.jd | 2 |
9 files changed, 16 insertions, 18 deletions
diff --git a/src/devices/audio.jd b/src/devices/audio.jd index 9f6cfd09..50be277b 100644 --- a/src/devices/audio.jd +++ b/src/devices/audio.jd @@ -172,7 +172,7 @@ audio_hw_modules { <h3 id="codecs">Media Codecs</h3> <p>Ensure that the audio codecs that your hardware and drivers support are properly declared for your product. See - <a href="{@docRoot}guide/media.html#expose"> Exposing Codecs to the Framework</a> for information on how to do this. + <a href="media.html#expose"> Exposing Codecs to the Framework</a> for information on how to do this. </p> <h2 id="configuring"> diff --git a/src/devices/camera.jd b/src/devices/camera.jd index 1e709c89..e85a23d2 100644 --- a/src/devices/camera.jd +++ b/src/devices/camera.jd @@ -138,7 +138,7 @@ frameworks/native/data/etc/android.hardware.camera.flash-autofocus.xml:system/et <li>Declare your camera’s media codec, format, and resolution capabilities in <code>device/<company_name>/<device_name>/media_profiles.xml</code> and <code>device/<company_name>/<device_name>/media_codecs.xml</code> XML files. - For more information, see <a href="{@docRoot}guide/media.html#expose"> Exposing + For more information, see <a href="media.html#expose"> Exposing Codecs and Profiles to the Framework</a> for information on how to do this. </p></code> @@ -171,4 +171,4 @@ Gallery2 \ </pre> </li> -</ol>
\ No newline at end of file +</ol> diff --git a/src/devices/tech/input/input-device-configuration-files.jd b/src/devices/tech/input/input-device-configuration-files.jd index e5629c38..06c89949 100644 --- a/src/devices/tech/input/input-device-configuration-files.jd +++ b/src/devices/tech/input/input-device-configuration-files.jd @@ -123,5 +123,5 @@ device to wake up and respond.</p> correctly for all internal input devices.</p> <h2 id="validation">Validation</h2> <p>Make sure to validate your input device configuration files using the -<a href="/tech/input/validate-keymaps.html">Validate Keymaps</a> tool.</p> +<a href="validate-keymaps.html">Validate Keymaps</a> tool.</p> diff --git a/src/devices/tech/input/key-character-map-files.jd b/src/devices/tech/input/key-character-map-files.jd index 7b1ac5bd..e60484e5 100644 --- a/src/devices/tech/input/key-character-map-files.jd +++ b/src/devices/tech/input/key-character-map-files.jd @@ -422,4 +422,4 @@ if they are designed for other languages.</p> or user-selectable keyboard layouts.</p> <h2 id="validation">Validation</h2> <p>Make sure to validate your key character map files using the -<a href="/tech/input/validate-keymaps.html">Validate Keymaps</a> tool.</p> +<a href="validate-keymaps.html">Validate Keymaps</a> tool.</p> diff --git a/src/devices/tech/input/key-layout-files.jd b/src/devices/tech/input/key-layout-files.jd index e9258818..ecab0ef2 100644 --- a/src/devices/tech/input/key-layout-files.jd +++ b/src/devices/tech/input/key-layout-files.jd @@ -239,7 +239,7 @@ not apply.</p> input system uses a virtual key map file to translate X / Y touch coordinates into Linux key codes, then uses the key layout file to translate Linux key codes into Android key codes.</p> -<p>Refer to the section on <a href="/tech/input/touch-devices.html">Touch Devices</a> +<p>Refer to the section on <a href="touch-devices.html">Touch Devices</a> for more details about virtual key map files.</p> <p>The key layout file for the touch screen input device must specify the appropriate key mapping and include the <code>VIRTUAL</code> flag for each key.</p> @@ -281,4 +281,4 @@ for the framework <code>config.xml</code> resource.</p> </code></pre> <h2 id="validation">Validation</h2> <p>Make sure to validate your key layout files using the -<a href="/tech/input/validate-keymaps.html">Validate Keymaps</a> tool.</p> +<a href="validate-keymaps.html">Validate Keymaps</a> tool.</p> diff --git a/src/devices/tech/input/keyboard-devices.jd b/src/devices/tech/input/keyboard-devices.jd index aa968aca..e7740fec 100644 --- a/src/devices/tech/input/keyboard-devices.jd +++ b/src/devices/tech/input/keyboard-devices.jd @@ -37,9 +37,7 @@ conditions hold:</p> </ul> <p>Joysticks are currently classified as keyboards because joystick and gamepad buttons are reported by <code>EV_KEY</code> events in the same way keyboard keys are reported. Thus -joysticks and gamepads also make use of key map files for configuration. -Refer to the section on <a href="/tech/input/joystick-devices.html">Joystick Devices</a> for -more information.</p> +joysticks and gamepads also make use of key map files for configuration.</p> <p>Once an input device has been classified as a keyboard, the system loads the input device configuration file and keyboard layout for the keyboard.</p> <p>The system then tries to determine additional characteristics of the device.</p> @@ -170,9 +168,9 @@ map and input device configuration.</p> <p>Refer to the following sections for more details about the files that participate in keyboard configuration:</p> <ul> -<li><a href="/tech/input/key-layout-files.html">Key Layout Files</a></li> -<li><a href="/tech/input/key-character-map-files.html">Key Character Map Files</a></li> -<li><a href="/tech/input/input-device-configuration-files.html">Input Device Configuration Files</a></li> +<li><a href="key-layout-files.html">Key Layout Files</a></li> +<li><a href="key-character-map-files.html">Key Character Map Files</a></li> +<li><a href="input-device-configuration-files.html">Input Device Configuration Files</a></li> </ul> <h3 id="properties">Properties</h3> <p>The following input device configuration properties are used for keyboards.</p> diff --git a/src/devices/tech/input/migration-guide.jd b/src/devices/tech/input/migration-guide.jd index dbdf6662..ff39dfd8 100644 --- a/src/devices/tech/input/migration-guide.jd +++ b/src/devices/tech/input/migration-guide.jd @@ -38,7 +38,7 @@ 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="/tech/input/dumpsys.html">Dumpsys</a> and look for devices that +is to run <a href="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 @@ -51,5 +51,5 @@ protocol "B". We also support digitizer tablets and stylus-based touch devices. multitouch input protocol correctly according to the standard.</p> <p>You will also need to update your input device configuration files because some properties have been changed to be simpler and more systematic.</p> -<p>Refer to <a href="/tech/input/touch-devices.html">Touch Devices</a> for more details about -driver requirements.</p>
\ No newline at end of file +<p>Refer to <a href="touch-devices.html">Touch Devices</a> for more details about +driver requirements.</p> diff --git a/src/devices/tech/input/touch-devices.jd b/src/devices/tech/input/touch-devices.jd index 21567d34..e7c909ab 100644 --- a/src/devices/tech/input/touch-devices.jd +++ b/src/devices/tech/input/touch-devices.jd @@ -545,7 +545,7 @@ input device configuration, virtual key map and key layout.</p> <p>Refer to the following sections for more details about the files that participate in keyboard configuration:</p> <ul> -<li><a href="/tech/input/input-device-configuration-files.html">Input Device Configuration Files</a></li> +<li><a href="input-device-configuration-files.html">Input Device Configuration Files</a></li> <li><a href="#virtual-key-map-files">Virtual Key Map Files</a></li> </ul> <h3 id="properties">Properties</h3> diff --git a/src/devices/tech/security/index.jd b/src/devices/tech/security/index.jd index 5a795986..2c0186cf 100644 --- a/src/devices/tech/security/index.jd +++ b/src/devices/tech/security/index.jd @@ -398,7 +398,7 @@ Android provides password complexity rules that can be set by the device administrator and enforced by the operating system. Filesystem encryption requires the use of a user password, pattern-based screen lock is not supported.</p> <p>More details on implementation of filesystem encryption are available at -<a href="/tech/encryption/android_crypto_implementation.html">https://source.android.com/tech/encryption/android_crypto_implementation.html</a></p> +<a href="/devices/tech/encryption/android_crypto_implementation.html">https://source.android.com/devices/tech/encryption/android_crypto_implementation.html</a></p> <h2 id="password-protection">Password Protection</h2> <p>Android can be configured to verify a user-supplied password prior to providing |