Docs: Wear Preview - Release Notes and more am: 289e9c1d am: 58b364da am: dd632a90

- title: API Overview

  path: /wear/preview/api-overview.html

  section:

  - title: Notification Improvements

    path: /wear/preview/features/notifications.html

  - title: Input Method Framework

    path: /wear/preview/features/ime.html

  - title: Complications

    path: /wear/preview/features/complications.html

  - title: Navigation and Actions

    path: /wear/preview/features/ui-nav-actions.html

  - title: Curved Layout

    path: /wear/preview/features/wearable-recycler-view.html

  - title: Notification Improvements

    path: /wear/preview/features/notifications.html

  - title: Bridging for Notifications

    path: /wear/preview/features/bridger.html

  - title: Input Method Framework

    path: /wear/preview/features/ime.html

  - title: Wrist Gestures

    path: /wear/preview/features/gestures.html

  - title: Standalone apps

    path: /wear/preview/features/standalone-apps.html

  - title: App Distribution

    path: /wear/preview/features/app-distribution.html

- title: Get Started

  path: /wear/preview/start.html

<ul>

  <li><a href="#activity-dismissal">Activity Dismissal</a></li>

  <li><a href="#invalid-fields">Invalid Fields for a Complication Type</a></li>

  <li><a href="#empty">Complication Types for Empty Data</a></li>

</ul>

</div>

  <a href="{@docRoot}wear/preview/features/ui-nav-actions.html">navigation

  drawers</a>.

</p>

<h2 id="invalid-fields">Invalid Fields for a Complication Type</h2>

<p>

  When a watch face uses the <a href="{@docRoot}wear/preview/features/complications.html">

  Complications API</a>, the watch face requests data from a chosen provider.

  A <code>ComplicationData</code> object, which contains

  complication types, is returned.

</p>

<p>

  A complication type determines the

  kinds of data that a watch face can render. This section describes

  a behavior change related to the <code>ComplicationData</code> object.

</p>

<p>

  Starting with

  <a href="https://developer.android.com/wear/preview/support.html#dp3">

  Developer Preview 3</a>, when a watch face requests a field that is invalid

  for a complication type, a default value for the field is returned.

  For example, if a watch face tries to access a <code>Long text</code>

  field in a <code>SHORT_TEXT</code> type, the default value for the

  <code>Long text</code> field is returned.

  In previous releases, such a request for an invalid field

  (for a type) resulted in an exception.

</p>

<h2 id="empty">Complication Types for Empty Data</h2>

<p>

  Starting with

  <a href="https://developer.android.com/wear/preview/support.html#dp3">

  Developer Preview 3</a>, the complication types used for "empty" data are

  changed. Apps that use the Complications API

  may need to be updated to use

  <code>TYPE_NO_DATA</code>. See the information

  about <code>TYPE_NO_DATA</code> in the

  <a href="{@docRoot}wear/preview/features/complications.html#types_and_fields">

  Types and fields</a> section.

</p>

          <li>

            <a href="#set_up_a_watch">Set Up a Watch</a>

          </li>

          <li>

            <a href="#set_up_a_phone">Set Up a Phone</a>

          </li>

          <li>

            <a href="#set_up_an_emulator">Set Up an Emulator</a>

          </li>

    </div>

    <p>

      You can run and test your app with the Android Wear 2.0 Developer Preview

      You can run and test your app with the Android Wear 2.0 Preview

      in either of these ways:

    </p>

      following tables and flash it to the corresponding device.

    </p>

    <p class="caution"><strong>Caution:</strong>

      After you flash an image to a watch, follow the steps for

      <a href="#set_up_a_phone">setting up a phone</a> with the beta version of

      the Android Wear companion app. To use a Wear 2.0 image on a watch,

      you must have the beta companion app on a paired phone.

    </p>

    <p>

      To restore your device to its original state during the preview,

      you can flash the appropriate retail system image, below, to the device.

        <td>

          Preview image for testing

        </td>

        <td><a href="#top" onclick="onDownload(this)">nemo-nvd83h-factory-48ac950c.tgz</a><br>

          MD5: dd351884cce9fb5bf1bdec0a8e5f56e3<br>

          SHA-1: 48ac950c48faef96a7770e3c1acb56d23a28d859

        <td><a href="#top" onclick="onDownload(this)">nemo-nve68j-factory-302a33ea.tgz</a><br>

          MD5: ddfccc3e050c7e2db8d657c82f7d6291<br>

          SHA-1: 302a33eac348c401fcb165bad4b9aaa40c7beb2b

        </td>

      </tr>

        <td>

          Non-preview image (for after testing)

        </td>

        <td><a href="#top" onclick="onDownload(this)">nemo-mnc40x-factory-fa528bec.tgz</a><br>

          MD5: 0b8ba3653d5a93cb854f4d7409d7b6c9<br>

          SHA-1: fa528bec8aba3bf6c7d901ba63cd6ea0a08dbeb0

        <td><a href="#top" onclick="onDownload(this)">nemo-mfd18l-factory-3faf6f2d.tgz</a><br>

          MD5: f3a0090c0e99da82ad095b5d2a9acc6d<br>

          SHA-1: 3faf6f2d7f422a17a5f6c54cf5e1d2c5622689b0

        </td>

      </tr>

        <td>

          Preview image for testing

        </td>

        <td><a href="#top" onclick="onDownload(this)">sturgeon-nvd83h-factory-cb5a11ab.tgz</a><br>

          MD5: 38c1047992b1d28f6833d9f6c8470cdc<br>

          SHA-1: cb5a11ab0260ea3ca7da5894e73e41f70357da6b

        <td><a href="#top" onclick="onDownload(this)">sturgeon-nve68j-factory-6607cd31.tgz</a><br>

          MD5: f78ac6ba8bb84038d163cc2d7ca85040<br>

          SHA-1: 6607cd31858af1bfd50b905c68f7cf1f0b6e570e

        </td>

      </tr>

      <tr id="sturgeon-non-preview">

        <td>

          Non-preview image (for after testing)

        </td>

        <td><a href="#top" onclick="onDownload(this)">sturgeon-mec23l-factory-48003078.tgz</a><br>

          MD5: 417b5cbddb29a2262bce133e283d2732<br>

          SHA-1: 4800307843580f818557dd7c43d8ba2161e289b2

        <td><a href="#top" onclick="onDownload(this)">sturgeon-m6e69f-factory-e659286a.tgz</a><br>

          MD5: 12ce6cb0b0e43b67ea46a886eae052ae<br>

          SHA-1: e659286aa9004f4555a476ede4e8b690f56cfefd

        </td>

      </tr>

    </table>

    <h4 id="set_up_watch">

      Set up the watch and begin testing

      Set up the watch

    </h4>

      <p>

        After the <code>flash-all</code> script finishes, your watch reboots.

        Pair the watch with a phone or tablet. The preview now is available

        for testing on the watch. Before installing an app, perform the

        Only pair the watch with a phone (so you can begin testing the preview)

        by using the instructions in <a href="#set_up_a_phone">Set Up a Phone</a>.

        Additionally, before installing an app, perform the

        following steps on the watch to re-secure the watch's bootloader:

    </p>

    </ol>

    <p>

      Your watch is ready for you to <a href=

      After you follow the instructions in

      <a href="#set_up_a_phone">Set Up a Phone</a>,

      your watch will be ready for you to <a href=

      "{@docRoot}training/wearables/apps/creating.html#Install">install and run

      your app</a>:

    </p>

      device reset and removes all user data on the device.

    </p>

    <h2 id="set_up_a_phone">

      Set Up a Phone

    </h2>

    <p>

      On a phone, follow the instructions in this section to install the beta

      version of the Android Wear companion app. The beta version cannot be run

      on a phone at the same time as the non-beta version. Additionally, the

      beta version is English-only.

    </p>

    <p>

      <p class="caution"><strong>Caution:</strong> If you have an existing

      pairing of the phone to a Wear 1.x

      watch, installation of the beta companion app will cause a loss of that

      pairing.

    </p>

    <h3 id="join-the-wear-2-0-preview-group">

      Join the Wear 2.0 preview group

    </h3>

    <p>

      To access the beta companion app, you must <a href=

      "https://groups.google.com/forum/#!forum/android-wear-developer-preview">join

      the preview group in Google Groups</a>.

    </p>

    <h3>

      Opt in for beta testing

    </h3>

    <p>

      On the <a href=

      "https://play.google.com/apps/testing/com.google.android.wearable.app">Testing

      Opt-in</a> page, select <strong>Become a Tester</strong>.

    </p>

    <h3 id="download-and-install-the-beta-version-of-the-companion-app">

      Download and install the beta version of the companion app

    </h3>

    <p>

      On the Play Store on your phone, go to the <a href=

      "https://play.google.com/store/apps/details?id=com.google.android.wearable.app">

      Android Wear app listing</a>. Tap <strong>Update</strong> to download and

      install the beta version of the app. After installation, confirm that

      <strong>Auto-update</strong> is selected for the app (see

      the "Set up automatic updates for specific apps" section of <a href=

      "https://support.google.com/googleplay/answer/113412">Update downloaded

      apps</a>). Tap <strong>Open</strong> to start the app.

    </p>

    <h3 id="pairing">

      Pair the phone to the watch

    </h3>

    <p>

      After you install the beta version of the companion app on a phone,

      you can pair the phone to the watch:

    </p>

    <ol>

      <li>On the phone, select your device name from the list of devices.

      A pairing code is displayed on the phone and on the watch.

      Ensure that the codes match.

      </li>

      <li>Tap <strong>Pair</strong> to

      continue the pairing process. When the watch is connected to

      the phone, a confirmation message is displayed.

      On the phone, a screen is displayed that lists

      the accounts on the phone.

      </li>

      <li>Choose a Google account to add and sync to your watch.

      </li>

      <li>Confirm the screen lock and enter the password to start the copying of

      the account from the phone to the watch.

      </li>

      <li>Follow the instructions in the wizard to finish the

      pairing process.

      </li>

    </ol>

    <p>

      You can begin testing your app with the preview.

    </p>

    <h2 id="set_up_an_emulator">

      Set Up an Emulator

    </h2>

       Click <strong>Next</strong>.

      </li>

      <li>Select an <strong>N</strong> image to download. The images may be on

      <li>Select a <strong>Nougat</strong> image to download. The images may be on

      the <strong>x86</strong> tab instead of the <strong>Recommended</strong>

      tab, until installed. For example, select the image with the

      <strong>Release Name</strong> of N, the <strong>API Level</strong> of N,

      and the <strong>Target</strong> of "Android 6.X (with Android Wear)".

      <strong>Release Name</strong> of Nougat, the <strong>API Level</strong> of 24,

      and the <strong>Target</strong> of "Android 7.0 (with Android Wear)".

      When the download and installation are complete, click

      <strong>Finish</strong> and then click <strong>Next</strong>.

      </li>

    <p>

      At milestone 4, you'll have access to the final Android Wear 2.0

      APIs and SDK to develop with, as well as near-final system images to test

      system behaviors and features. Android Wear 2.0 will use the Android N

      API level at this time. You can begin final compatibility testing of your

      system behaviors and features. Android Wear 2.0 will use the

      Android 7.0 API level at this time.

      You can begin final compatibility testing of your

      legacy apps and refine any new code that is using the Android Wear 2.0

      APIs or features.

    </p>