From 95f6c758ae176747cf6675e37b984a8aece29dcd Mon Sep 17 00:00:00 2001 From: Joe Fernandez Date: Tue, 14 May 2013 16:10:58 -0700 Subject: [PATCH] Search tag additions Adding more search tags for feature areas (tools, adk, gcm, etc.) Change-Id: I34b9b6e220b19f6adaf532e39eebb0d30b1573c7 --- docs/html/google/gcm/index.jd | 13 +-- docs/html/guide/appendix/media-formats.jd | 1 + docs/html/guide/topics/media/camera.jd | 2 +- docs/html/tools/adk/adk.jd | 1 + docs/html/tools/adk/adk2.jd | 1 + docs/html/tools/adk/index.jd | 1 + docs/html/tools/help/adb.jd | 107 +++++++++++----------- docs/html/tools/help/adt.jd | 1 + docs/html/tools/samples/index.jd | 2 +- docs/html/training/camera/index.jd | 8 +- 10 files changed, 72 insertions(+), 65 deletions(-) diff --git a/docs/html/google/gcm/index.jd b/docs/html/google/gcm/index.jd index f9c3ed36e8b6a..aeba86ffa1b06 100644 --- a/docs/html/google/gcm/index.jd +++ b/docs/html/google/gcm/index.jd @@ -1,10 +1,11 @@ page.title=Google Cloud Messaging for Android +page.tags="gcm" header.hide=1 @jd:body
- +
@@ -15,7 +16,7 @@ header.hide=1 Google Cloud Messaging for Android (GCM) is a service that allows you to send data from your server to your users' Android-powered device, and also to receive messages from devices on the same connection. The GCM service handles all aspects of queueing of messages and delivery to the target Android application running on the target device. GCM is completely free no matter how big your messaging needs are, and there are no quotas.

- +
@@ -27,12 +28,12 @@ from your server to your users' Android-powered device, and also to receive mess message telling your app there is new data to be fetched from the server (for instance, a movie uploaded by a friend), or it could be a message containing up to 4kb of payload data (so apps like instant messaging can consume the message directly). GCM Architectural Overview.

- +

Send "send-to-sync" messages

-

A send-to-sync (collapsible) message is often a "tickle" that tells a mobile application to sync data from the server. For example, suppose you have an email application. When a user receives new email on the server, the server pings the mobile application with a "New mail" message. This tells the application to sync to the server to pick up the new email. +

A send-to-sync (collapsible) message is often a "tickle" that tells a mobile application to sync data from the server. For example, suppose you have an email application. When a user receives new email on the server, the server pings the mobile application with a "New mail" message. This tells the application to sync to the server to pick up the new email. Send-to-sync messages.

- +

Send messages with payload

Unlike a send-to-sync message, every "message with payload" (non-collapsible message) is delivered. The payload the message contains can be up to 4kb. Messages with payload.

@@ -45,7 +46,7 @@ up to 4kb of payload data (so apps like instant messaging can consume the messag

Streamlined registration makes it simple and fast to add GCM support to your Android app. Learn more »

Upstream messaging over XMPP

GCM's Cloud Connection Service (CCS) lets you communicate with Android devices over a persistent XMPP connection. The primary advantages of CCS are speed, and the ability to receive upstream messages (that is, messages from a device to the cloud). You can use the service in tandem with existing GCM APIs. Use this form to sign up for CCS. Learn more »

- +

Seamless multi-device messaging

Maps a single user to a notification key, which you can then use to send a single message to multiple devices owned by the user. Use this form to sign up for User Notifications. Learn more »

diff --git a/docs/html/guide/appendix/media-formats.jd b/docs/html/guide/appendix/media-formats.jd index feacdc6cffbb4..23420877d38f8 100644 --- a/docs/html/guide/appendix/media-formats.jd +++ b/docs/html/guide/appendix/media-formats.jd @@ -1,4 +1,5 @@ page.title=Android Supported Media Formats +page.tags="video","audio","mpeg","mp4","m4a","mp3","3gp","3gpp","flac","wave","wav" @jd:body
diff --git a/docs/html/guide/topics/media/camera.jd b/docs/html/guide/topics/media/camera.jd index 8ebb349357ead..e48109a0193c5 100644 --- a/docs/html/guide/topics/media/camera.jd +++ b/docs/html/guide/topics/media/camera.jd @@ -1,5 +1,5 @@ page.title=Camera -page.tags="mediarecorder" +page.tags="photo","video","picture","mediarecorder" @jd:body
diff --git a/docs/html/tools/adk/adk.jd b/docs/html/tools/adk/adk.jd index 049b6e92804a6..16517473e30ac 100644 --- a/docs/html/tools/adk/adk.jd +++ b/docs/html/tools/adk/adk.jd @@ -1,4 +1,5 @@ page.title=Accessory Development Kit 2011 Guide +page.tags="adk" @jd:body
diff --git a/docs/html/tools/adk/adk2.jd b/docs/html/tools/adk/adk2.jd index 0b185833823e2..c60e9203a8d08 100644 --- a/docs/html/tools/adk/adk2.jd +++ b/docs/html/tools/adk/adk2.jd @@ -1,4 +1,5 @@ page.title=Accessory Development Kit 2012 Guide +page.tags="adk" @jd:body
diff --git a/docs/html/tools/adk/index.jd b/docs/html/tools/adk/index.jd index d492e96692522..e035115a5b2e8 100644 --- a/docs/html/tools/adk/index.jd +++ b/docs/html/tools/adk/index.jd @@ -1,4 +1,5 @@ page.title=Accessory Development Kit +page.tags="adk" @jd:body

The Accessory Development Kit (ADK) is a reference implementation for hardware manufacturers and diff --git a/docs/html/tools/help/adb.jd b/docs/html/tools/help/adb.jd index c8afca5ded1c2..74f6c07f6b520 100644 --- a/docs/html/tools/help/adb.jd +++ b/docs/html/tools/help/adb.jd @@ -1,6 +1,7 @@ page.title=Android Debug Bridge parent.title=Tools parent.link=index.html +page.tags="adb" @jd:body

@@ -101,10 +102,10 @@ option to specify the target device to which the command should be directed.

Table 1. Available adb commands

- - - - + + + + @@ -191,7 +192,7 @@ Commands to a Specific Emulator/Device Instance. - -
CategoryCommandDescriptionCommentsCategoryCommandDescriptionComments
Ports and Networking forward <local> <remote> Forwards socket connections from a specified local port to a specified remote port on the emulator/device instance. Port specifications can use these schemes: +Port specifications can use these schemes:
  • tcp:<portnum>
  • local:<UNIX domain socket name>
  • dev:<character device name>
    • @@ -226,10 +227,10 @@ Commands to a Specific Emulator/Device Instance.
wait-for-device Blocks execution until the device is online — that is, until the instance state is device.You can prepend this command to other adb commands, in which case adb will wait until the emulator/device instance is connected before issuing the other commands. Here's an example: +You can prepend this command to other adb commands, in which case adb will wait until the emulator/device instance is connected before issuing the other commands. Here's an example: 
adb wait-for-device shell getprop
-Note that this command does not cause adb to wait until the entire system is fully booted. For that reason, you should not prepend it to other commands that require a fully booted system. As an example, the install requires the Android package manager, which is available only after the system is fully booted. A command such as +Note that this command does not cause adb to wait until the entire system is fully booted. For that reason, you should not prepend it to other commands that require a fully booted system. As an example, the install requires the Android package manager, which is available only after the system is fully booted. A command such as 
adb wait-for-device install <app>.apk
@@ -280,34 +281,34 @@ would issue the install command as soon as the emulator or device i

Before issuing adb commands, it is helpful to know what emulator/device instances are connected to the adb server. You can generate a list of attached emulators/devices using the devices command:

- 
adb devices
+ 
adb devices

In response, adb prints this status information for each instance:

    -
  • Serial number — A string created by adb to uniquely identify an emulator/device instance by its - console port number. The format of the serial number is <type>-<consolePort>. - Here's an example serial number: emulator-5554
    • -
  • State — The connection state of the instance may be one of the following: -
      -
    • offline — the instance is not connected to adb or is not responding.
      • -
    • device — the instance is now connected to the adb server. Note that this state does not - imply that the Android system is fully booted and operational, since the instance connects to adb - while the system is still booting. However, after boot-up, this is the normal operational state of - an emulator/device instance.
      • -
    • no device — there is no emulator/device connected. -
    -
    • +
  • Serial number — A string created by adb to uniquely identify an emulator/device instance by its + console port number. The format of the serial number is <type>-<consolePort>. + Here's an example serial number: emulator-5554
    • +
  • State — The connection state of the instance may be one of the following: +
      +
    • offline — the instance is not connected to adb or is not responding.
      • +
    • device — the instance is now connected to the adb server. Note that this state does not + imply that the Android system is fully booted and operational, since the instance connects to adb + while the system is still booting. However, after boot-up, this is the normal operational state of + an emulator/device instance.
      • +
    • no device — there is no emulator/device connected. +
    +

The output for each instance is formatted like this:

- 
[serialNumber] [state]
+ 
[serialNumber] [state]

Here's an example showing the devices command and its output:

- 
adb devices
-List of devices attached 
+  
adb devices
+List of devices attached
 emulator-5554  device
 emulator-5556  device
 emulator-5558  device

@@ -323,13 +324,13 @@ emulator-5558  device
when issuing adb commands. To do so, use the -s option in the commands. The usage for the -s option is:

- 
adb -s <serialNumber> <command>
- +
adb -s <serialNumber> <command>
+

As shown, you specify the target instance for a command using its adb-assigned serial number. You can use the devices command to obtain the serial numbers of running emulator/device instances. For example:

- 
adb -s emulator-5556 install helloWorld.apk
+
adb -s emulator-5556 install helloWorld.apk

Note that, if you issue a command without specifying a target emulator/device instance while multiple devices are available, adb generates an error. @@ -377,10 +378,10 @@ commands let you copy arbitrary directories and files to any location in an emulator/device instance.

To copy a file or directory (and its sub-directories) from the emulator or device, use

-
adb pull <remote> <local>
+
adb pull <remote> <local>

To copy a file or directory (and its sub-directories) to the emulator or device, use

- 
adb push <local> <remote>
+ 
adb push <local> <remote>

In the commands, <local> and <remote> refer to the paths to the target files/directory on your development machine (local) and on the @@ -397,8 +398,8 @@ emulator/device instance (remote). For example:

Issuing Shell Commands

-

Adb provides a Unix shell that you can use to run a variety of commands on an emulator -or connected device. The command binaries are stored in the file system of the emulator or device, +

Adb provides a Unix shell that you can use to run a variety of commands on an emulator +or connected device. The command binaries are stored in the file system of the emulator or device, at /system/bin/...

Two of the most common command tools are activity manager ({@code am}) and @@ -408,11 +409,11 @@ at /system/bin/... the adb remote shell on the emulator/device. To issue a single command without entering a remote shell, use the shell command like this:

- 
adb [-d|-e|-s <serialNumber>] shell <shell_command>
- + 
adb [-d|-e|-s <serialNumber>] shell <shell_command>
+

Or enter a remote shell on an emulator/device like this:

- 
adb [-d|-e|-s <serialNumber>] shell
+ 
adb [-d|-e|-s <serialNumber>] shell

When you are ready to exit the remote shell, press CTRL+D or type exit.

@@ -441,8 +442,8 @@ adb shell am start -a android.intent.action.VIEW

Table 2. Available activity manager commands

- - + + @@ -641,7 +642,7 @@ screen resolution using a device with a large screen, and vice versa. -
CommandDescriptionCommandDescription
display-density <dpi> Override emulator/device display density. +Override emulator/device display density. This command is helpful for testing your app across different screen densities on high-density screen environment using a low density screen, and vice versa.

Example:
am display-density 480 @@ -662,7 +663,7 @@ to-uri <INTENT> to-intent-uri <INTENT>

Print the given intent specification as an {@code intent:} URI.

See the -Specification for <INTENT> arguments. +Specification for <INTENT> arguments.

@@ -688,7 +689,7 @@ specify the intent with the following options:

{@code -d <DATA_URI>}
Specify the intent data URI, such as "content://contacts/people/1". You can declare this only once. - +
{@code -t <MIME_TYPE>}
Specify the intent MIME type, such as "image/png". You can declare this only once. @@ -843,8 +844,8 @@ adb shell pm uninstall com.example.MyApp

Table 3. Available package manager commands.

- - + + @@ -1097,12 +1098,12 @@ get-max-users

Examining sqlite3 databases from a remote shell

-

From an adb remote shell, you can use the -sqlite3 command-line program to -manage SQLite databases created by Android applications. The -sqlite3 tool includes many useful commands, such as -.dump to print out the contents of a table and -.schema to print the SQL CREATE statement for an existing table. +

From an adb remote shell, you can use the +sqlite3 command-line program to +manage SQLite databases created by Android applications. The +sqlite3 tool includes many useful commands, such as +.dump to print out the contents of a table and +.schema to print the SQL CREATE statement for an existing table. The tool also gives you the ability to execute SQLite commands on the fly.

To use sqlite3, enter a remote shell on the emulator instance, as described above, then invoke the tool using the sqlite3 command. Optionally, when invoking sqlite3 you can specify the full path to the database you want to explore. Emulator/device instances store SQLite3 databases in the folder /data/data/<package_name>/databases/.

@@ -1126,7 +1127,7 @@ sqlite> .exit

UI/Application Exerciser Monkey

The Monkey is a program that runs on your emulator or device and generates pseudo-random -streams of user events such as clicks, touches, or gestures, as well as a number of system-level +streams of user events such as clicks, touches, or gestures, as well as a number of system-level events. You can use the Monkey to stress-test applications that you are developing, in a random yet repeatable manner.

@@ -1135,7 +1136,7 @@ application and sends 500 pseudo-random events to it.

adb shell monkey -v -p your.package.name 500
-

For more information about command options for Monkey, see the complete +

For more information about command options for Monkey, see the complete UI/Application Exerciser Monkey documentation page.

@@ -1155,15 +1156,15 @@ application and sends 500 pseudo-random events to it.

Table 4. Some other adb shell commands

CommandDescriptionCommandDescription
- - - + + + - diff --git a/docs/html/tools/help/adt.jd b/docs/html/tools/help/adt.jd index 18e7443f165e6..4dac574bd5d24 100644 --- a/docs/html/tools/help/adt.jd +++ b/docs/html/tools/help/adt.jd @@ -1,4 +1,5 @@ page.title=Android Developer Tools +page.tags="adt" @jd:body
diff --git a/docs/html/tools/samples/index.jd b/docs/html/tools/samples/index.jd index ed416e6a82db3..76ba37af10b5d 100644 --- a/docs/html/tools/samples/index.jd +++ b/docs/html/tools/samples/index.jd @@ -1,5 +1,5 @@ page.title=Samples - +page.tags="example","code" @jd:body

To help you understand some fundamental Android APIs and coding practices, a variety of sample diff --git a/docs/html/training/camera/index.jd b/docs/html/training/camera/index.jd index fa754a0aec3a9..d6305d6425526 100644 --- a/docs/html/training/camera/index.jd +++ b/docs/html/training/camera/index.jd @@ -1,5 +1,5 @@ page.title=Capturing Photos -page.tags="camera","video" +page.tags="camera","video","picture" trainingnavtop=true startpage=true @@ -42,7 +42,7 @@ prevalent. Remember Gopher? We don't, either. For your app to become part of your users' lives, give them a way to put their lives into it. Using the on-board cameras, your application can enable users to augment what they see around them, make unique avatars, look for zombies around the corner, -or simply share their experiences.

+or simply share their experiences.

This class gets you clicking fast with some super-easy ways of leveraging existing camera applications. In later lessons, you dive deeper @@ -50,7 +50,7 @@ and learn how to control the camera hardware directly.

Lessons

- +
Taking Photos Simply
Leverage other applications and capture photos with just a few lines of code.
@@ -58,5 +58,5 @@ and learn how to control the camera hardware directly.

Leverage other applications and record videos with just a few lines of code.
Controlling the Camera
Control the camera hardware directly and implement your own camera application.
-
+
Shell CommandDescriptionCommentsShell CommandDescriptionComments
dumpsys Dumps system data to the screen.The Dalvik Debug Monitor Server +The Dalvik Debug Monitor Server (DDMS) tool offers integrated debug environment that you may find easier to use.