Clarify that preview system images can receive ota updates.
Change-Id: Idce5a1049c5221c1a78f6bb2c0f5f7d24bbf94b7
diff --git a/docs/html/preview/download.jd b/docs/html/preview/download.jd
index 614c274..ac37704 100644
--- a/docs/html/preview/download.jd
+++ b/docs/html/preview/download.jd
@@ -220,14 +220,13 @@
<ul>
<li><strong>Enroll the device in automatic OTA system updates</strong> through the
- Android Beta program. Once enrolled, your device will receive regular
+ <a href="https://g.co/androidbeta">Android Beta Program</a>. Once enrolled, your device will receive regular
over-the-air (OTA) updates of all milestone builds in the N Developer Preview. This
approach is recommended because it lets you seamlessly transition from your current
environment through the various releases of the N Developer Preview.</li>
<li><strong>Download a Developer Preview system image and flash the device</strong>.
- OTA updates are not provided automatically for devices that you flash manually. This
- approach is recommended if you need precise control over the test environment or need
- to reinstall frequently, such as for automated testing. </li>
+ OTA updates are not provided automatically for devices that you flash manually, but
+ you can enroll those devices in Android Beta Program to get OTA updates. </li>
</ul>
<h3 id="ota">Enroll the device in automatic OTA updates</h3>
@@ -235,7 +234,7 @@
<p>
If you have access to a supported device (see the list in the Downloads
table), you can receive over-the-air updates to preview versions of Android
- by enrolling that device in the Android Beta Program. These updates are
+ by enrolling that device in the <a href="https://g.co/androidbeta">Android Beta Program</a>. These updates are
automatically downloaded and will update your device just like official
system updates.
</p>
@@ -263,10 +262,12 @@
<p>
At any time you can download the latest Developer Preview system image and
manually flash it to your device. See the table below to download the system
- image for your test device.
+ image for your test device. Manually flashing a device is useful if you need
+ precise control over the test environment or need to reinstall frequently,
+ such as for automated testing.
</p>
-<p>
+<!-- You can flash by ota or system image --><p>
Installing a system image on a device <strong>removes all data from the
device</strong>, so you should back up your data first.
</p>
@@ -278,13 +279,20 @@
to flash the image onto your device.
</p>
-<p class="note"><strong>Note:</strong>
- Manually flashed system images <em>will not</em>
- automatically receive subsequent OTA updates to later Developer Preview
+<p>
+ Manually flashed system images <strong>do not
+ automatically receive OTA updates</strong> to later Developer Preview
milestone builds. Make sure to keep your environment up-to-date and flash a
new system image at each Developer Preview milestone.
</p>
+<p>
+ If you decide you want to get OTA updates after manually flashing a device,
+ all you need to do is enroll the device in the <a href="https://g.co/androidbeta">Android
+ Beta Program</a>. You can enroll the device at any time to receive the next Preview
+ update over the air.
+</p>
+
<table>
<tr>
<th scope="col">Device</th>
diff --git a/docs/html/preview/index.jd b/docs/html/preview/index.jd
index fddb950..bce5dec 100644
--- a/docs/html/preview/index.jd
+++ b/docs/html/preview/index.jd
@@ -62,7 +62,7 @@
</a>
<ul class="dac-actions">
<li class="dac-action">
- <a class="dac-action-link" href="{@docRoot}preview/bug">
+ <a class="dac-action-link" href="https://developer.android.com/preview/bug">
<i class="dac-action-sprite dac-sprite dac-auto-chevron-large"></i>
Report an issue
</a>
@@ -87,7 +87,7 @@
<div class="wrap dac-offset-parent">
<div class="actions">
- <div><a href="{@docRoot}preview/bug">
+ <div><a href="https://developer.android.com/preview/bug">
<span class="dac-sprite dac-auto-chevron-large"></span>
Report an issue
</a></div>
diff --git a/docs/html/preview/support.jd b/docs/html/preview/support.jd
index 01de958..ee71d8b 100644
--- a/docs/html/preview/support.jd
+++ b/docs/html/preview/support.jd
@@ -8,7 +8,7 @@
<p>
Two primary support channels are available to you when developing and testing
with the Android N Developer Preview: Please file bugs at <a href=
- "{@docRoot}preview/bug">https://developer.android.com/preview/bug</a> for
+ "https://developer.android.com/preview/bug">https://developer.android.com/preview/bug</a> for
device-specific, system, and Google App bugs. For issues in other apps,
please contact the developer directly.
</p>
@@ -93,6 +93,12 @@
</li>
</ul>
+<h4 id="microphone">Microphone</h4>
+
+<ul>
+ <li>The system may incorrect persists the microphone mute state across apps and reboots. If you mute the microphone in an app and the state is persisted, open any app that has microphone mute controls and unmute the microphone.</li>
+</ul>
+
<h4 id="ui">System UI</h4>
<ul>
@@ -227,6 +233,7 @@
</ul>
</li>
</ul>
+
<h4 id="keyboard">Keyboard</h4>
<ul>
@@ -345,29 +352,21 @@
</li>
</ul>
+
<h4 id="accessibility">Accessibility</h4>
<ul>
- <li>TalkBack exhibits issues with features including Notifications, Quick
- Settings Tiles and Multi-window display that may cause system crashing or
- lack of spoken feedback from TalkBack. Future releases of the preview will
- address these issues.
- </li>
+ <li>TalkBack exhibits issues with features including Notifications, Quick Settings Tiles and Multi-window display that may cause system crashing or lack of spoken feedback from TalkBack. Future releases of the preview will address these issues.</li>
</ul>
<h3 id="device-sp">Device-Specific Notes and Issues</h3>
<h4 id="player">Nexus Player</h4>
-
<ul>
- <li>Video playback, app compatibility and stability issues are expected on
- Nexus Player in this release of the Preview.
- </li>
+<li>Video playback, app compatibility and stability issues are expected on Nexus Player in this release of the Preview.</li>
</ul>
<h4 id="pixelc">Pixel C</h4>
-
<ul>
- <li>Multi-window resizing may cause crashing.
- </li>
+<li>Multi-window resizing may cause crashing.</li>
</ul>