Merge "docs: Wear Preview 2.0 support page updates" into mnc-io-docs

@jd:body

@jd:body

  <p>If you experience problems when developing and testing with

<p>

  the Wear 2.0 Developer Preview, please file bugs at <a href=

  If you experience problems when developing and testing with the

  "https://developer.android.com/wear/preview/bug">https://developer.android.com/wear/preview/bug</a>

  Wear 2.0 Developer Preview, please file bugs at

  .</p>

  <a href="https://g.co/wearpreviewbug">https://g.co/wearpreviewbug</a>.

</p>

  <p>To discuss issues or ideas with other developers working with Android Wear, 

<p>

  join the <a href="https://plus.sandbox.google.com/communities/113381227473021565406">

  To discuss issues or ideas with other developers working with Android Wear,

  join the <a href="https://plus.google.com/communities/113381227473021565406">

  Wear Developer Google+ community</a>.

  Wear Developer Google+ community</a>.

</p>

<h2 id="dp">Developer Preview 1</h2>

<h2 id="dp">Developer Preview 1</h2>

  </div>

  </div>

</div>

</div>

  <h3>General advisories</h3>

  <p>This Developer Preview release is for app developers only and is designed 

<h3 id="general_advisories">General advisories</h3>

  for use in compatibility testing and early development only.</p>

  <h3>Wear 2.0 Notifications</h3>

<p>

  This Developer Preview release is for app developers only and is designed for

  use in compatibility testing and early development only.

</p>

  <h4>Notification groups</h4>

<h4 id="deprecations">Deprecations</h4>

  <p>The current release of Android Wear 2.0 does not include support for notification

  groups, also known as <a href="{@docRoot}training/wearables/notifications/stacks.html">

  stacks</a> and bundles. You should continue to use notification groups because

   that support will be coming in a future version of Android Wear 2.0.</p>

   <h4>Smart Reply</h4>

<p>The following fields are deprecated in the Preview:</p>

   <p>The current version of Wear 2.0 does not generate any Smart Reply responses

<ul>

    even if you call <a href="https://android-dot-devsite.googleplex.com/wear/preview/start.html#get_the_preview_reference_documentation">{@code setAllowGeneratedReplies()}</a>.

  <li>The <code>Notification.WearableExtender#setCustomSizePreset(int)</code>

    This functionality will be added in a later version of Wear 2.0.

  method no longer accepts <code>SIZE_FULL_SCREEN</code> and this value is now

    </p>

  undefined.

  </li>

  <li>The <code>Notification.WearableExtender#setContentIcon(int)</code> method

  is deprecated.

  </li>

</ul>

<h3 id="known_issues">Known Issues</h3>

<h4 id="notifications">Notifications</h4>

  <h4>Fields that are deprecated in Wear 2.0</h4>

<ul>

<ul>

    <li>Notification.WearableExtender#setCustomSizePreset(int) no longer accepts

  <li>This preview release does not include support for notification groups,

    SIZE_FULL_SCREEN as it has no meaning in Wear 2.0.</li>

  but will be supported in a future release.

  </li>

  <li>Tapping on next and previous controls in a notification while playing

  music does not work.

  </li>

  <li>Bottom drawer actions user interface overlaps with media card

  notifications.

  </li>

  <li>The system does not generate Smart Reply responses even if

  <code>setAllowGeneratedReplies(true)</code> is set.

  </li>

</ul>

    <li>Notification.WearableExtender#setContentIcon(int) is deprecated as it has no

<h4 id="complications">Complications</h4>

    meaning in Wear 2.0.</li>

<ul>

  <li>Battery information is not synchronized between watch face and drop down

  quick menu.

  </li>

  <li>Play music crashes when tapping on music complication in watch face.

  </li>

</ul>

</ul>

<h4 id="system_user_interface">System User Interface</h4>

<ul>

  <li>Pressing the hardware button in ambient mode triggers active mode with

  the app launcher instead of active mode only.

  </li>

  <li>Double pressing the power hardware button while on the launcher causes

  the watch screen to turn black.

  </li>

  <li>Dismissing multiple notifications can cause app to force close.

  </li>

  <li>Turning screen lock to off (Enable and disable) functionality is not

  reliable.

  </li>

  <li>Airplane mode does not work from quick settings.

  </li>

  <li>Tapping Google keyboard English (United States) displays a <em>Settings

  under construction</em> message.

  </li>

  <li>First calendar event notification must be dismissed in order to show the

  rest of the event card.

  </li>

  <li>Unable to turn off the Wifi on wearable.

  </li>

</ul>

<h4 id="companion_app">Companion App</h4>

<ul>

  <li>'More actions' via Companion app shows a blank screen on phone running

  nyc-release and watch running feldspar-release.

  </li>

  <li>Select watch face on companion wear app will not change watch face on

  wearable.

  </li>

</ul>

<h4 id="devices">Devices</h4>

<ul>

  <li>On the Huawei Watch, selecting the language, followed by multiple

  acknowledgement dialogues results in a black screen.

  </li>

  <li>On the LG Watch Urbane LTE, when answering call from the watch, the watch

  does not provide audio from the caller.

  </li>

</ul>