docs: delete preview pages

Change-Id: I76b6b8545bfed3ad0604043105ccf4795ab8be62

1 files changed, 0 insertions, 120 deletions

diff --git a/docs/html/preview/support.jd b/docs/html/preview/support.jd
deleted file mode 100644
index 3220d63..0000000
--- a/docs/html/preview/support.jd
+++ /dev/null
@@ -1,120 +0,0 @@
-page.title=Support
-
-@jd:body
-
-<p>If you've encountered bugs or have feedback about the L Developer Preview,
-<a href="https://code.google.com/p/android-developer-preview/">create an issue</a> on
-our issue tracker.</p>
-
-<p>For more support,
-<a href="https://plus.google.com/communities/101985907812750684586">join
-the L Developer Preview Google+ community</a> to discuss your development experiences.
-
-
-<h2 id="ReleaseNotes">Release Notes</h2>
-<p>June 25, 2014 - Initial Release of the L Developer Preview</p>
-
-<h3 id="UserInterface">User interface</h3>
-<ul>
-<li>If your app launches an activity with
-{@link android.app.Activity#startActivity startActivity()}
-and an {@link android.content.Intent} set to
-{@link android.content.Intent#FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET}, the
-activity shows up as a separate task in the Recent apps screen. This is the
-same behavior as though your app used {@code Intent.FLAG_ACTIVITY_NEW_DOCUMENT}
-(see <a href="{@docRoot}preview/api-overview.html#Recents">Concurrent
-documents and activities in the Recents screen</a>). If you want your activity
-to remain in the same task that launched it, use
-{@link android.app.Activity#startActivityForResult
-startActivityForResult()} instead.</li>
-<li>System-rendered shadows for user interface (UI) elements in views may
-appear with visible spiky edges. To avoid this visual artifact, use a higher
-<a href="{@docRoot}preview/material/views-shadows.html#elevation">view
-elevation</a>.</li>
-<li>On very tall or wide views, view shadows may appear with additional rough
-visual artifacts around the view edges. To minimize this, avoid using view
-shadows with very narrow views.</li>
-<li>The {@code android.graphics.drawable.RippleDrawable} class does not
-respond to pointer location changes, except when the drawable is set as a
-{@link android.view.View} background.</li>
-</ul>
-
-<h3 id="Multimedia">Multimedia</h3>
-<ul>
-<li>The {@code android.hardware.camera2} APIs are supported only on Nexus 5
-devices.</li>
-<li>Saving a DNG file with the new {@code android.hardware.camera2.DngCreator}
-API fails if lens shading compensation map generation is not enabled. To
-capture images to DNG files, add the following code when creating your capture
-requests:
-<pre>
-CaptureRequest.Builder stillCaptureRequest =
-        mCameraDevice.createCaptureRequest(CameraDevice.TEMPLATE_STILL_CAPTURE);
-
-stillCaptureRequest.set(CaptureRequest.STATISTICS_LENS_SHADING_MAP_MODE,
-        CaptureRequest.STATISTICS_LENS_SHADING_MAP_MODE_ON);
-</pre></li>
-<li>The {@code android.media.AudioTrack.write(float[], int, int, int)} method
-currently does not work. Use the
-{@link android.media.AudioTrack#write(short[], int, int)
-AudioTrack.write(short[], int, int)} method instead.</li>
-<li>Lockscreen security is currently not enforced when users start a Android
-mirroring session from the Quick Settings shade.</li>
-</ul>
-
-<h3 id="UserInput">User input</h3>
-<ul><li>The System UI may crash unexpectedly while the device is charging, if
-	the locale is set to {@code fr} (FRENCH).</li></ul>
-
-<h3 id="Wireless">Wireless and Connectivity</h3>
-<ul>
-<li>The {@code android.bluetooth.le} APIs are supported only on Nexus 5
-devices.</li>
-<li>You might encounter these issues while using Bluetooth LE scanning:
-	<ul>
-	<li><em>Settings</em> does not show all Bluetooth LE devices when a scan
-		filter is set.</li>
-	<li>System returns non-intuitive error messages during a Bluetooth LE scan,
-		when Bluetooth is off.</li>
-	<li>The {@code BluetoothLeScanner.startScan()} method starts failing after
-		six concurrent scans with different callbacks.</li>
-	</ul>
-</li>
-<li>You might encounter these issues while using Bluetooth LE advertising:
-	<ul>
-		<li>The device MAC address does not change for multiple advertising
-		when the application processor is asleep.</li>
-		<li>The TX Power Level is always 0 in advertising packets.</li>
-	</ul>
-</li>
-</ul>
-
-<h3 id="Enterprise">Enterprise</h3>
-<ul>
-<li>The device may crash unexpectedly in these situations when using
-Android work functionality:
-<ul>
-<li>The user attempts to share a web page (via <strong>Menu &gt; Share</strong>)
-from a non-Android work Chrome app to a Android work profile Gmail app.</li>
-<li>The user attempts to share a web page via Bluetooth from a
-Android work profile
-Chrome app.</li>
-<li>The user attempts to share a web page via Android Beam from a
-Android work profile Chrome app.</li>
-</ul>
-</li>
-<li>Deleting a Android work profile may take several minutes to complete. You
-cannot create a new Android work profile until the deletion operation is over.</li>
-</ul>
-
-<h3 id="64bitsupport">64-bit support</h3>
-<ul>
-<li><p>If you are using the NDK to compile apps for 32- or 64-bit systems and
-want to use the features provided in the L Developer Preview, download the
-{@code android-ndk64-r10} package for your target platform from the
-<a href="{@docRoot}tools/sdk/ndk/index.html">Android NDK page</a>. The
-{@code android-ndk64-r10} package contains the L Developer Preview API
-library (located under the {@code platforms/android-L/} API directory) for both
-32- and 64-bit systems. The package also includes the {@code gcc-4.9} compiler
-for both 32- and 64-bit apps.</p></li>
-</ul>