From 5748bc4a1bd2fd98341710cacc6a7bfbd5bb40f6 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Sat, 6 Feb 2016 18:24:32 -0800 Subject: [PATCH] Add preview docs dir, toc, and basic files. Change-Id: I890dd21fed1217e4429f269eed5bada9a6faf2b4 --- Android.mk | 1 + docs/html/preview/api-overview.jd | 569 ++++++++++++++++++ docs/html/preview/behavior-changes.jd | 442 ++++++++++++++ docs/html/preview/download.jd | 371 ++++++++++++ docs/html/preview/guide.jd | 187 ++++++ .../images/m-preview-timeline-crop.png | Bin 0 -> 10205 bytes .../preview/images/m-preview-timeline.png | Bin 0 -> 13002 bytes docs/html/preview/index.jd | 73 +++ docs/html/preview/license.jd | 143 +++++ docs/html/preview/overview.jd | 389 ++++++++++++ docs/html/preview/preview_toc.cs | 126 ++++ docs/html/preview/samples.jd | 70 +++ docs/html/preview/setup-sdk.jd | 178 ++++++ docs/html/preview/support.jd | 533 ++++++++++++++++ 14 files changed, 3082 insertions(+) create mode 100644 docs/html/preview/api-overview.jd create mode 100644 docs/html/preview/behavior-changes.jd create mode 100644 docs/html/preview/download.jd create mode 100644 docs/html/preview/guide.jd create mode 100644 docs/html/preview/images/m-preview-timeline-crop.png create mode 100644 docs/html/preview/images/m-preview-timeline.png create mode 100644 docs/html/preview/index.jd create mode 100644 docs/html/preview/license.jd create mode 100644 docs/html/preview/overview.jd create mode 100644 docs/html/preview/preview_toc.cs create mode 100644 docs/html/preview/samples.jd create mode 100644 docs/html/preview/setup-sdk.jd create mode 100644 docs/html/preview/support.jd diff --git a/Android.mk b/Android.mk index 840fda01c7cf5..73d805513dc72 100644 --- a/Android.mk +++ b/Android.mk @@ -1042,6 +1042,7 @@ LOCAL_DROIDDOC_OPTIONS:= \ -hdf android.whichdoc online \ $(sample_groups) \ -useUpdatedTemplates \ + -includePreview \ -hdf android.hasSamples true \ -samplesdir $(samples_dir) diff --git a/docs/html/preview/api-overview.jd b/docs/html/preview/api-overview.jd new file mode 100644 index 0000000000000..599dc1e48ee38 --- /dev/null +++ b/docs/html/preview/api-overview.jd @@ -0,0 +1,569 @@ +page.title=API Overview +page.keywords=preview,sdk,compatibility +page.tags=previewresources, androidm +sdk.platform.apiLevel=22-mnc +page.image=images/cards/card-api-overview_16-9_2x.png +@jd:body + + +
+ +
+ +

The M Developer Preview gives you an advance look at the upcoming release +for the Android platform, which offers new features for users and app +developers. This document provides an introduction to the most notable APIs.

+ +

+ The M Developer Preview 3 release includes the final APIs for Android 6.0 (API level + 23). If you are preparing an app for use on Android 6.0, + download the latest SDK and to complete your + final updates and release testing. You can review the final APIs in the + API Reference and see the API differences in + the Android API Differences Report. +

+ +

+ +

Important: + You may now publish apps that target Android 6.0 (API level 23) to the Google Play store. +

+ +

Note: + If you have been working with previous preview releases and want to see the differences + between the final API and previous preview versions, download the additional difference + reports included in the preview docs + reference. +

+ +

Important behavior changes

+ +

If you have previously published an app for Android, be aware that your app might be affected +by changes in the platform.

+ +

Please see Behavior Changes for complete information.

+ +

App Linking

+

This preview enhances Android’s intent system by providing more powerful app linking. +This feature allows you to associate an app with a web domain you own. Based on this +association, the platform can determine the default app to use to handle a particular +web link and skip prompting users to select an app. To learn how to implement this feature, see +App Linking. + +

Auto Backup for Apps

+

The system now performs automatic full data backup and restore for apps. For the +duration of the M Developer Preview program, all +apps are backed up, independent of which SDK version they target. After the final M SDK release, +your app must target M to enable this behavior; you do not need to add any additional code. If users +delete their Google accounts, their backup data is deleted as well. To learn how this feature +works and how to configure what to back up on the file system, see +Auto Backup for Apps.

+ +

Authentication

+

This preview offers new APIs to let you authenticate users by using their fingerprint scans on +supported devices, and check how recently the user was last authenticated using a device unlocking +mechanism (such as a lockscreen password). Use these APIs in conjunction with +the Android Keystore system.

+ +

Fingerprint Authentication

+ +

To authenticate users via fingerprint scan, get an instance of the new +{@link android.hardware.fingerprint.FingerprintManager} class and call the +{@link android.hardware.fingerprint.FingerprintManager#authenticate(android.hardware.fingerprint.FingerprintManager.CryptoObject, android.os.CancellationSignal, int, android.hardware.fingerprint.FingerprintManager.AuthenticationCallback, android.os.Handler) authenticate()} +method. Your app must be running on a compatible +device with a fingerprint sensor. You must implement the user interface for the fingerprint +authentication flow on your app, and use the standard Android fingerprint icon in your UI. +The Android fingerprint icon ({@code c_fp_40px.png}) is included in the +sample app. If you are developing multiple apps that use fingerprint +authentication, note that each app must authenticate the user’s fingerprint independently. +

+ +

To use this feature in your app, first add the + {@link android.Manifest.permission#USE_FINGERPRINT} permission in your manifest.

+ +
+<uses-permission
+        android:name="android.permission.USE_FINGERPRINT" />
+
+ + +

To see an app implementation of fingerprint authentication, refer to the + + Fingerprint Dialog sample. For a demonstration of how you can use these authentication + APIs in conjunction with other Android APIs, see the video + + Fingerprint and Payment APIs.

+ +

If you are testing this feature, follow these steps:

+
    +
  1. Install Android SDK Tools Revision 24.3, if you have not done so.
    2. +
  2. Enroll a new fingerprint in the emulator by going to +Settings > Security > Fingerprint, then follow the enrollment instructions.
    3. +
  3. Use an emulator to emulate fingerprint touch events with the +following command. Use the same command to emulate fingerprint touch events on the lockscreen or +in your app. +
    +adb -e emu finger touch <finger_id>
+
    +

    On Windows, you may have to run {@code telnet 127.0.0.1 } followed by + {@code finger touch }. +

    +
    4. +
+ +

Confirm Credential

+

Your app can authenticate users based on how recently they last unlocked their device. This +feature frees users from having to remember additional app-specific passwords, and avoids the need +for you to implement your own authentication user interface. Your app should use this feature in +conjunction with a public or secret key implementation for user authentication.

+ +

To set the timeout duration for which the same key can be re-used after a user is successfully +authenticated, call the new +{@link android.security.keystore.KeyGenParameterSpec.Builder#setUserAuthenticationValidityDurationSeconds(int) setUserAuthenticationValidityDurationSeconds()} +method when you set up a {@link javax.crypto.KeyGenerator} or +{@link java.security.KeyPairGenerator}.

+ +

Avoid showing the re-authentication dialog excessively -- your apps should try using the +cryptographic object first and if the the timeout expires, use the +{@link android.app.KeyguardManager#createConfirmDeviceCredentialIntent(java.lang.CharSequence, java.lang.CharSequence) createConfirmDeviceCredentialIntent()} +method to re-authenticate the user within your app. +

+ +

To see an app implementation of this feature, refer to the + + Confirm Credential sample.

+ +

Direct Share

+ + + +

This preview provides you with APIs to make sharing intuitive and quick for users. You can now +define direct share targets that launch a specific activity in your app. These direct share +targets are exposed to users via the Share menu. This feature allows users to share +content to targets, such as contacts, within other apps. For example, the direct share target might +launch an activity in another social network app, which lets the user share content directly to a +specific friend or community in that app.

+ +

To enable direct share targets you must define a class that extends the +{@link android.service.chooser.ChooserTargetService} class. Declare your +service in the manifest. Within that declaration, specify the +{@link android.Manifest.permission#BIND_CHOOSER_TARGET_SERVICE} permission and an +intent filter using the +{@link android.service.chooser.ChooserTargetService#SERVICE_INTERFACE SERVICE_INTERFACE} action.

+

The following example shows how you might declare the +{@link android.service.chooser.ChooserTargetService} in your manifest.

+
+<service android:name=".ChooserTargetService"
+        android:label="@string/service_name"
+        android:permission="android.permission.BIND_CHOOSER_TARGET_SERVICE">
+    <intent-filter>
+        <action android:name="android.service.chooser.ChooserTargetService" />
+    </intent-filter>
+</service>
+
+ +

For each activity that you want to expose to +{@link android.service.chooser.ChooserTargetService}, add a +{@code } element with the name +{@code "android.service.chooser.chooser_target_service"} in your app manifest. +

+ +
+<activity android:name=".MyShareActivity”
+        android:label="@string/share_activity_label">
+    <intent-filter>
+        <action android:name="android.intent.action.SEND" />
+    </intent-filter>
+<meta-data
+        android:name="android.service.chooser.chooser_target_service"
+        android:value=".ChooserTargetService" />
+</activity>
+
+ +

Voice Interactions

+

+This preview provides a new voice interaction API which, together with +Voice Actions, +allows you to build conversational voice experiences into your apps. Call the +{@link android.app.Activity#isVoiceInteraction()} method to determine if a voice action triggered +your activity. If so, your app can use the +{@link android.app.VoiceInteractor} class to request a voice confirmation from the user, select +from a list of options, and more.

+ +

Most voice interactions originate from a user voice action. A voice interaction activity can +also, however, start without user input. For example, another app launched through a voice +interaction can also send an intent to launch a voice interaction. To determine if your activity +launched from a user voice query or from another voice interaction app, call the +{@link android.app.Activity#isVoiceInteractionRoot()} method. If another app launched your +activity, the method returns {@code false}. Your app may then prompt the user to confirm that +they intended this action.

+ +

To learn more about implementing voice actions, see the +Voice Actions developer site. +

+ +

Assist API

+

+This preview offers a new way for users to engage with your apps through an assistant. To use this +feature, the user must enable the assistant to use the current context. Once enabled, the user +can summon the assistant within any app, by long-pressing on the Home button.

+

Your app can elect to not share the current context with the assistant by setting the +{@link android.view.WindowManager.LayoutParams#FLAG_SECURE} flag. In addition to the +standard set of information that the platform passes to the assistant, your app can share +additional information by using the new {@link android.app.assist.AssistContent} class.

+ +

To provide the assistant with additional context from your app, follow these steps:

+ +
    +
  1. Implement the {@link android.app.Application.OnProvideAssistDataListener} interface.
    2. +
  2. Register this listener by using +{@link android.app.Application#registerOnProvideAssistDataListener(android.app.Application.OnProvideAssistDataListener) registerOnProvideAssistDataListener()}.
    3. +
  3. In order to provide activity-specific contextual information, override the +{@link android.app.Activity#onProvideAssistData(android.os.Bundle) onProvideAssistData()} +callback and, optionally, the new +{@link android.app.Activity#onProvideAssistContent(android.app.assist.AssistContent) onProvideAssistContent()} +callback. +
+ +

Notifications

+

This preview adds the following API changes for notifications:

+ + +

Bluetooth Stylus Support

+

This preview provides improved support for user input using a Bluetooth stylus. Users can pair +and connect a compatible Bluetooth stylus with their phone or tablet. While connected, position +information from the touch screen is fused with pressure and button information from the stylus to +provide a greater range of expression than with the touch screen alone. Your app can listen for +stylus button presses and perform secondary actions, by registering +{@link android.view.View.OnContextClickListener} and +{@link android.view.GestureDetector.OnContextClickListener} objects in your activity.

+ +

Use the {@link android.view.MotionEvent} methods and constants to detect stylus button +interactions:

+ + +

Improved Bluetooth Low Energy Scanning

+

+If your app performs performs Bluetooth Low Energy scans, use the new +{@link android.bluetooth.le.ScanSettings.Builder#setCallbackType(int) setCallbackType()} +method to specify that you want the system to notify callbacks when it first finds, or sees after a +long time, an advertisement packet matching the set {@link android.bluetooth.le.ScanFilter}. This +approach to scanning is more power-efficient than what’s provided in the previous platform version. +

+ +

Hotspot 2.0 Release 1 Support

+

+This preview adds support for the Hotspot 2.0 Release 1 spec on Nexus 6 and Nexus 9 devices. To +provision Hotspot 2.0 credentials in your app, use the new methods of the +{@link android.net.wifi.WifiEnterpriseConfig} class, such as +{@link android.net.wifi.WifiEnterpriseConfig#setPlmn(java.lang.String) setPlmn()} and +{@link android.net.wifi.WifiEnterpriseConfig#setRealm(java.lang.String) setRealm()}. In the +{@link android.net.wifi.WifiConfiguration} object, you can set the +{@link android.net.wifi.WifiConfiguration#FQDN} and the +{@link android.net.wifi.WifiConfiguration#providerFriendlyName} fields. +The new {@link android.net.wifi.ScanResult#isPasspointNetwork()} method indicates if a detected +network represents a Hotspot 2.0 access point. +

+ +

4K Display Mode

+

The platform now allows apps to request that the display resolution be upgraded to 4K rendering +on compatible hardware. To query the current physical resolution, use the new +{@link android.view.Display.Mode} APIs. If the UI is drawn at a lower logical resolution and is +upscaled to a larger physical resolution, be aware that the physical resolution the +{@link android.view.Display.Mode#getPhysicalWidth()} method returns may differ from the logical +resolution reported by {@link android.view.Display#getSize(android.graphics.Point) getSize()}.

+ +

You can request the system to change the physical resolution in your app as it runs, by setting +the {@link android.view.WindowManager.LayoutParams#preferredDisplayModeId} property of your app’s +window. This feature is useful if you want to switch to 4K display resolution. While in 4K display +mode, the UI continues to be rendered at the original resolution (such as 1080p) and is upscaled to +4K, but {@link android.view.SurfaceView} objects may show content at the native resolution.

+ +

Themeable ColorStateLists

+

Theme attributes are now supported in +{@link android.content.res.ColorStateList} for devices running the M Preview. The +{@link android.content.res.Resources#getColorStateList(int) getColorStateList()} and +{@link android.content.res.Resources#getColor(int) getColor()} methods have been deprecated. If +you are calling these APIs, call the new +{@link android.content.Context#getColorStateList(int) getColorStateList()} or +{@link android.content.Context#getColor(int) getColor()} methods instead. These methods are also +available in the v4 appcompat library via {@link android.support.v4.content.ContextCompat}.

+ +

Audio Features

+ +

This preview adds enhancements to audio processing on Android, including:

+ + +

Video Features

+

This preview adds new capabilities to the video processing APIs, including:

+ + +

Camera Features

+

This preview includes the following new APIs for accessing the camera’s flashlight and for +camera reprocessing of images:

+ +

Flashlight API

+

If a camera device has a flash unit, you can call the +{@link android.hardware.camera2.CameraManager#setTorchMode(java.lang.String, boolean) setTorchMode()} +method to switch the flash unit’s torch mode on or off without opening the camera device. The app +does not have exclusive ownership of the flash unit or the camera device. The torch mode is turned +off and becomes unavailable whenever the camera device becomes unavailable, or when other camera +resources keeping the torch on become unavailable. Other apps can also call +{@link android.hardware.camera2.CameraManager#setTorchMode(java.lang.String, boolean) setTorchMode()} +to turn off the torch mode. When the last app that turned on the torch mode is closed, the torch +mode is turned off.

+ +

You can register a callback to be notified about torch mode status by calling the +{@link android.hardware.camera2.CameraManager#registerTorchCallback(android.hardware.camera2.CameraManager.TorchCallback, android.os.Handler) registerTorchCallback()} +method. The first time the callback is registered, it is immediately called with the torch mode +status of all currently known camera devices with a flash unit. If the torch mode is turned on or +off successfully, the +{@link android.hardware.camera2.CameraManager.TorchCallback#onTorchModeChanged(java.lang.String, boolean) onTorchModeChanged()} +method is invoked.

+ +

Reprocessing API

+

The {@link android.hardware.camera2 Camera2} API is extended to support YUV and private +opaque format image reprocessing. To determine if these reprocessing capabilities are available, +call {@link android.hardware.camera2.CameraManager#getCameraCharacteristics(java.lang.String) +getCameraCharacteristics()} and check for the +{@link android.hardware.camera2.CameraCharacteristics#REPROCESS_MAX_CAPTURE_STALL} key. If a +device supports reprocessing, you can create a reprocessable camera capture session by calling +createReprocessableCaptureSession(), +and create requests for input buffer reprocessing.

+ +

Use the {@link android.media.ImageWriter} class to connect the input buffer flow to the camera +reprocessing input. To get an empty buffer, follow this programming model:

+ +
    +
  1. Call the {@link android.media.ImageWriter#dequeueInputImage()} method.
    2. +
  2. Fill the data into the input buffer.
    3. +
  3. Send the buffer to the camera by calling the +{@link android.media.ImageWriter#queueInputImage(android.media.Image) queueInputImage()} method.
    4. +
+ +

If you are using a {@link android.media.ImageWriter} object together with an +{@link android.graphics.ImageFormat#PRIVATE} image, your app cannot access the image +data directly. Instead, pass the {@link android.graphics.ImageFormat#PRIVATE} image directly to the +{@link android.media.ImageWriter} by calling the +{@link android.media.ImageWriter#queueInputImage(android.media.Image) queueInputImage()} method +without any buffer copy.

+ +

The {@link android.media.ImageReader} class now supports +{@link android.graphics.ImageFormat#PRIVATE} format image streams. This support allows your app to +maintain a circular image queue of {@link android.media.ImageReader} output images, select one or +more images, and send them to the {@link android.media.ImageWriter} for camera reprocessing.

+ +

Android for Work Features

+

This preview includes the following new APIs for Android for Work:

+ + +

+ For a detailed view of all API changes in the M Developer Preview, see the API Differences Report. +

diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd new file mode 100644 index 0000000000000..cab4163416857 --- /dev/null +++ b/docs/html/preview/behavior-changes.jd @@ -0,0 +1,442 @@ +page.title=Behavior Changes +page.keywords=preview,sdk,compatibility +sdk.platform.apiLevel=MNC +@jd:body + +
+ +
+ +

Along with new features and capabilities, the M Developer Preview includes a variety of +system changes and API behavior changes. This document highlights +some of the key changes that you should understand and account for in your apps.

+ +

If you have previously published an app for Android, be aware that these changes in the +platform affect your app.

+ +

Runtime Permissions

+

This preview introduces a new permissions model, where users can now directly manage +app permissions at runtime. This model gives users improved visibility and control over +permissions, while streamlining the installation and auto-update processes for app developers. +Users can grant or revoke permissions individually for installed apps.

+ +

On your apps that target the M Preview release or higher, make sure to check for and request +permissions at runtime. To determine if your app has been granted a permission, call the +new {@link android.content.Context#checkSelfPermission(java.lang.String) checkSelfPermission()} +method. To request a permission, call the new +{@link android.app.Activity#requestPermissions(java.lang.String[], int) requestPermissions()} +method. Even if your app is not targeting the M Preview release, you should test your app under +the new permissions model.

+ +

For details on supporting the new permissions model in your app, see the + +Permissions developer preview page. For tips on how to assess the impact on your app, +see the Testing Guide

+ +

Power-Saving Optimizations

+

This preview introduces new power-saving optimizations for idle devices and apps.

+ + +

To learn more about these power-saving changes, see +Power-Saving Optimizations.

+ +

Adoptable Storage Devices

+

+With this preview, users can adopt external storage devices such as SD cards. Adopting an +external storage device encrypts and formats the device to behave like internal storage. This +feature allows users to move both apps and private data of those apps between storage devices. When +moving apps, the system respects the +{@code android:installLocation} +preference in the manifest.

+ +

If your app accesses the following APIs or fields, be aware that the file paths they return +will dynamically change when the app is moved between internal and external storage devices. +When building file paths, it is strongly recommended that you always call these APIs dynamically. +Don’t use hardcoded file paths or persist fully-qualified file paths that were built previously.

+ + + +

To debug this feature in the developer preview, you can enable adoption of a USB drive that is +connected to an Android device through a USB On-The-Go (OTG) cable, by running this command:

+ +
+$ adb shell sm set-force-adoptable true
+
+ +

Apache HTTP Client Removal

+

This preview removes support for the Apache HTTP client. If your app is using this client and +targets Android 2.3 (API level 9) or higher, use the {@link java.net.HttpURLConnection} class +instead. This API is more efficient because it reduces network use through transparent compression +and response caching, and minimizes power consumption. To continue using the Apache HTTP APIs, you +must first declare the following compile-time dependency in your {@code build.gradle} file: +

+
+android {
+    useLibrary 'org.apache.http.legacy'
+}
+
+

Android is moving away from OpenSSL to the +BoringSSL +library. If you’re using the Android NDK in your app, don't link against cryptographic libraries +that are not a part of the NDK API, such as {@code libcrypto.so} and {@code libssl.so}. These +libraries are not public APIs, and may change or break without notice across releases and devices. +In addition, you may expose yourself to security vulnerabilities. Instead, modify your +native code to call the Java cryptography APIs via JNI or to statically link against a +cryptography library of your choice.

+ +

AudioManager Changes

+

Setting the volume directly or muting specific streams via the {@link android.media.AudioManager} +class is no longer supported. The {@link android.media.AudioManager#setStreamSolo(int,boolean) +setStreamSolo()} method is deprecated, and you should call the +{@link android.media.AudioManager#requestAudioFocus(android.media.AudioManager.OnAudioFocusChangeListener, int, int) requestAudioFocus()} +method instead. Similarly, the +{@link android.media.AudioManager#setStreamMute(int,boolean) setStreamMute()} method is +deprecated; instead, call the {@link android.media.AudioManager#adjustStreamVolume(int, int, int) +adjustStreamVolume()} method and pass in the direction value +{@link android.media.AudioManager#ADJUST_MUTE} or +{@link android.media.AudioManager#ADJUST_UNMUTE}.

+ +

Notifications

+

+This release removes the {@code Notification.setLatestEventInfo()} method. Use the +{@link android.app.Notification.Builder} class instead to construct notifications. To update a +notification repeatedly, reuse the {@link android.app.Notification.Builder} instance. Call the +{@link android.app.Notification.Builder#build()} method to get +updated {@link android.app.Notification} instances. +

+

The {@code adb shell dumpsys notification} command no longer prints out your notification text. +Use the {@code adb shell dumpsys notification --noredact} command instead to print out the text +in a notification object.

+ +

Text Selection

+ + + +

When users select text in your app, you can now display text selection actions such as +Cut, Copy, and Paste in a +floating toolbar. The user interaction implementation is similar to that +for the contextual action bar, as described in + +Enabling the contextual action mode for individual views.

+ +

To implement a floating toolbar for text selection, make the following changes in your existing +apps:

+
    +
  1. In your {@link android.view.View} or {@link android.app.Activity} object, change your +{@link android.view.ActionMode} calls from +{@code startActionMode(Callback)} to {@code startActionMode(Callback, ActionMode.TYPE_FLOATING)}.
    2. +
  2. Take your existing implementation of {@code ActionMode.Callback} and make it extend +{@link android.view.ActionMode.Callback2} instead.
    3. +
  3. Override the +{@link android.view.ActionMode.Callback2#onGetContentRect(android.view.ActionMode, android.view.View, android.graphics.Rect) onGetContentRect()} +method to provide the coordinates of the content {@link android.graphics.Rect} object +(such as a text selection rectangle) in the view.
    4. +
  4. If the rectangle positioning is no longer valid, and this is the only element to be invalidated, +call the {@link android.view.ActionMode#invalidateContentRect() invalidateContentRect()} method.
    5. +
+ +

If you are using +Android Support Library revision 22.2, be aware that floating toolbars are not +backward-compatible and appcompat takes control over {@link android.view.ActionMode} objects by +default. This prevents floating toolbars from being displayed. To enable +{@link android.view.ActionMode} support in an +{@link android.support.v7.app.AppCompatActivity}, call +{@link android.support.v7.app.AppCompatActivity#getDelegate()}, then call +{@link android.support.v7.app.AppCompatDelegate#setHandleNativeActionModesEnabled(boolean) +setHandleNativeActionModesEnabled()} on the returned +{@link android.support.v7.app.AppCompatDelegate} object and set the input +parameter to {@code false}. This call returns control of {@link android.view.ActionMode} objects to +the framework. In devices running the M Preview, that allows the framework to support +{@link android.support.v7.app.ActionBar} or floating toolbar modes, while on pre-M Preview devices, +only the {@link android.support.v7.app.ActionBar} modes are supported.

+ +

Android Keystore Changes

+

With this preview, the +Android Keystore provider no longer supports +DSA. ECDSA is still supported.

+ +

Keys which do not require encryption at rest will no longer be deleted when secure lock screen +is disabled or reset (for example, by the user or a Device Administrator). Keys which require +encryption at rest will be deleted during these events.

+ +

Wi-Fi and Networking Changes

+ +

This preview introduces the following behavior changes to the Wi-Fi and networking APIs.

+ + +

Camera Service Changes

+

In this preview, the model for accessing shared resources in the camera service has been changed +from the previous “first come, first serve” access model to an access model where high-priority +processes are favored. Changes to the service behavior include:

+ + +

Runtime

+

The ART runtime now properly implements access rules for the +{@link java.lang.reflect.Constructor#newInstance(java.lang.Object...) newInstance()} method. This +change fixes a problem where Dalvik was checking access rules incorrectly in previous versions. +If your app uses the +{@link java.lang.reflect.Constructor#newInstance(java.lang.Object...) newInstance()} method and you +want to override access checks, call the +{@link java.lang.reflect.Constructor#setAccessible(boolean) setAccessible()} method with the input +parameter set to {@code true}. If your app uses the +v7 appcompat library or the +v7 recyclerview library, +you must update your app to use to the latest versions of these libraries. Otherwise, make sure that +any custom classes referenced from XML are updated so that their class constructors are accessible.

+ +

This preview updates the behavior of the dynamic linker. The dynamic linker now understands the +difference between a library’s {@code soname} and its path +( +public bug 6670), and search by {@code soname} is now +implemented. Apps which previously worked that have bad {@code DT_NEEDED} entries +(usually absolute paths on the build machine’s file system) may fail when loaded.

+ +

The {@code dlopen(3) RTLD_LOCAL} flag is now correctly implemented. Note that +{@code RTLD_LOCAL} is the default, so calls to {@code dlopen(3)} that didn’t explicitly use +{@code RTLD_LOCAL} will be affected (unless your app explicitly used {@code RTLD_GLOBAL}). With +{@code RTLD_LOCAL}, symbols will not be made available to libraries loaded by later calls to +{@code dlopen(3)} (as opposed to being referenced by {@code DT_NEEDED} entries).

+

+ +

Access to Hardware Identifier

+

To provide users with greater data protection, starting in this release, Android +removes programmatic access to the device’s local hardware identifier for +apps using the Wi-Fi and Bluetooth APIs. The +{@link android.net.wifi.WifiInfo#getMacAddress() WifiInfo.getMacAddress()} and the +{@link android.bluetooth.BluetoothAdapter#getAddress() BluetoothAdapter.getAddress()} methods +now return a constant value of {@code 02:00:00:00:00:00}.

+ +

To access the hardware identifiers of nearby external devices via Bluetooth and Wi-Fi scans, +your app must now have the following permissions:

+ + +

Note: When a device running M Developer Preview initiates a +background Wi-Fi or Bluetooth scan, the operation is visible to external devices as +originating from a randomized MAC address.

+ +

APK Validation

+

The platform now performs stricter validation of APKs. An APK is considered corrupt if a file is +declared in the manifest but not present in the APK itself. An APK must be re-signed if any of the +contents are removed.

+ +

USB Connection

+

Device connections through the USB port are now set to charge-only mode by default. To access +the device and its content over a USB connection, users must explicitly grant permission for such +interactions. If your app supports user interactions with the device over a USB port, take into +consideration that the interaction must be explicitly enabled. +

+ +

Android for Work Changes

+

This preview includes the following behavior changes for Android for Work:

+ diff --git a/docs/html/preview/download.jd b/docs/html/preview/download.jd new file mode 100644 index 0000000000000..d00f90cbfd2d3 --- /dev/null +++ b/docs/html/preview/download.jd @@ -0,0 +1,371 @@ +page.title=Downloads +page.image=images/cards/card-download_16-9_2x.png + +@jd:body + +
+ + + + +
+ +
+
+

In this document

+
    +
  1. Android 6.0 SDK
    2. +
  2. Developer Documentation
    3. +
  3. Hardware System Images
    4. +
+ +

Legacy downloads

+
    +
  1. Developer Preview Archive
    2. +
+
+
+ + +

+ The Android M Preview SDK includes development tools, Android system images, and library files to + help you test your app and the new APIs coming in the next release of the platform. This document + describes how to get the downloadable components of the preview for testing your app. +

+ + +

Android 6.0 SDK

+ +

+ With Developer Preview 3, the official Android 6.0 SDK is now available for download through the Android SDK Manager. For more information on + downloading and configuring the SDK, see Set Up the SDK. +

+ + +

Developer Documentation

+ +

+ The developer documentation for Developer Preview 3 is released as Android 6.0 (API level 23) and + is available online, including the API level 23 + reference and diff report. The following + developer documentation download package provides additional, incremental difference reports + between the preview releases. +

+ + + + + + + + + + +
DescriptionDownload / Checksums
Android M Preview 3
Developer Docs		m-preview-3-developer-docs.zip
+ MD5: d99b14b0c06d31c8dfecb25072654ca3
+ SHA-1: 9cefeeda07676130da606a1796e1c00fffc667c1 +
+ + +

Hardware System Images

+ +

+ These system images allow you to install a preview version of the platform on a physical device for + testing. By configuring a device with one of these images, you can install and test your app to + see how it performs on the next version of the platform. The process of installing a system image + on a device removes all data from the device, so you should backup your data before + installing a system image. +

+ +

+ Warning: The following Android system images are previews and are subject to change. Your + use of these system images is governed by the Android SDK Preview License Agreement. The Android + preview system images are not stable releases, and may contain errors and defects that can result + in damage to your computer systems, devices, and data. The preview Android system images are not + subject to the same testing as the factory OS and can cause your phone and installed services and + applications to stop working. +

+ +
+ + + + + + + + + + + + + + + + + + + + + + +
DeviceDownload / Checksums
Nexus 5 (GSM/LTE)
"hammerhead"		hammerhead-MPA44I-preview-2ebbc049.tgz
+ MD5: 91a924fb0c9f8e716e3b4c9954fd0dbb
+ SHA-1: 2ebbc049b68c4da8baeee3e42bb94d7a965ba4a3 +
Nexus 6
"shamu"		shamu-MPA44I-preview-62b9c486.tgz
+ MD5: ac6e58da86125073d9c395257fd42664
+ SHA-1: 62b9c486fd7a5020e228d53ca5acd5c1857e48ff +
Nexus 9
"volantis"		volantis-MPA44I-preview-5c30a6e2.tgz
+ MD5: 7f83768757913d3fea945a661020d185
+ SHA-1: 5c30a6e2acd11a81f4105b12d23ff654f534f699 +
Nexus Player
"fugu"		fugu-MPA44I-preview-2860040a.tgz
+ MD5: 438da8d37da9e341a69cfb16a4001ac5
+ SHA-1: 2860040a326582f1ff5f702bf9a1ef002717fc98 +
+ +

Install an Image to a Device

+ +

+ In order to use a device image for testing, you must install it on a compatible device. Follow + the instructions below to install a system image: +

+ +
    +
  1. Download and uncompress one of the system image packages listed here.
    2. +
  2. Backup any data you want to preserve from the device.
    3. +
  3. Follow the instructions at + developers.google.com/android + to flash the image onto your device.
    4. +
+ +

Updating a Device with the Preview

+ +

+ Once you have installed a preview system image on a development device, the device is upgraded + automatically with the next preview release through over-the-air (OTA) updates. When the update + is available, the device displays notification that an update is available and allows you to + install it. You can also manually install the next preview image by repeating the procedure in + the previous section. +

+ +

Revert a Device to Factory Specifications

+ +

+ If you want to uninstall the preview and revert the device to factory specifications, go to + developers.google.com/android and + download the image you want to flash to for your device. Follow the instructions on that page to + flash the image to your device. +

+ +
+ +
+ + + + diff --git a/docs/html/preview/guide.jd b/docs/html/preview/guide.jd new file mode 100644 index 0000000000000..56bb4d994476d --- /dev/null +++ b/docs/html/preview/guide.jd @@ -0,0 +1,187 @@ +page.title=Testing Guide +page.image=images/cards/card-build_16x9_2x.png +page.keywords=previewresources,androidm,testing,permissions + +@jd:body + +
+ +
+ +

+ The Android M Developer Preview gives you an opportunity to ensure your apps work with the next + version of the platform. This preview includes a number of APIs and behavior changes that can + impact your app, as described in the API + Overview and Behavior Changes. In testing + your app with the preview, there are some specific system changes that you should focus on to + ensure that users have a good experience. +

+ +

+ This guide describes the what and how to test preview features with your app. You should + prioritize testing of these specific preview features, due to their high potential impact on your + app's behavior: +

+ + + +

+ For more information about how to set up devices or virtual devices with a preview system image + for testing, see Set up the Preview SDK. +

+ + +

Testing Permissions

+ +

+ The new Permissions model + changes the way that permissions are allocated to your app by the user. Instead of granting all + permissions during the install procedure, your app must ask the user for individual permissions + at runtime. For users this behavior provides more granular control over each app’s activities, as + well as better context for understanding why the app is requesting a specific permission. Users + can grant or revoke the permissions granted to an app individually at any time. This feature of + the preview is most likely to have an impact on your app's behavior and may prevent some of your + app features from working, or they may work in a degraded state. +

+ +

+ This change affects all apps running on the new platform, even those not targeting the new + platform version. The platform provides a limited compatibility behavior for legacy apps, but you + should begin planning your app’s migration to the new permissions model now, with a goal of + publishing an updated version of your app at the official platform launch. +

+ + +

Test tips

+ +

+ Use the following test tips to help you plan and execute testing of your app with the new + permissions behavior. +

+ + + +

Test strategy

+ +

+ The permissions change affects the structure and design of your app, as well as + the user experience and flows you provide to users. You should assess your app’s current + permissions use and start planning for the new flows you want to offer. The official release of + the platform provides compatibility behavior, but you should plan on updating your app and not + rely on these behaviors. +

+ +

+ Identify the permissions that your app actually needs and uses, and then find the various code + paths that use the permission-protected services. You can do this through a combination of + testing on the new platform and code analysis. In testing, you should focus on opting in to + runtime permissions by changing the app’s {@code targetSdkVersion} to the preview version. For + more information, see Set up the Preview SDK. +

+ +

+ Test with various combinations of permissions revoked and added, to highlight the user flows that + depend on permissions. Where a dependency is not obvious or logical you should consider + refactoring or compartmentalizing that flow to eliminate the dependency or make it clear why the + permission is needed. +

+ +

+ For more information on the behavior of runtime permissions, testing, and best practices, see the + Permissions developer + preview page. +

+ + +

Testing Doze and App Standby

+ +

+ The power saving features of Doze and App Standby limit the amount of background processing that + your app can perform when a device is in an idle state or while your app is not in focus. The + restrictions the system may impose on apps include limited or no network access, + suspended background tasks, suspended Notifications, ignored wake requests, and alarms. To ensure + that your app behaves properly with these power saving optimizations, you should test your app by + simulating these low power states. +

+ +

Testing your app with Doze

+ +

To test Doze with your app:

+ +
    +
  1. Configure a hardware device or virtual device with a M Preview system image.
    2. +
  2. Connect the device to your development machine and install your app.
    3. +
  3. Run your app and leave it active.
    4. +
  4. Simulate the device going into Doze mode by running the following commands: + +
    +$ adb shell dumpsys battery unplug
+$ adb shell dumpsys deviceidle step
+$ adb shell dumpsys deviceidle -h
+
    + +
    5. +
  5. Observe the behavior of your app when the device is re-activated. Make sure it + recovers gracefully when the device exits Doze.
    6. +
+ + +

Testing apps with App Standby

+ +

To test the App Standby mode with your app:

+ +
    +
  1. Configure a hardware device or virtual device with a M Preview system image.
    2. +
  2. Connect the device to your development machine and install your app.
    3. +
  3. Run your app and leave it active.
    4. +
  4. Simulate the app going into standby mode by running the following commands: + +
    +$ adb shell am broadcast -a android.os.action.DISCHARGING
+$ adb shell am set-idle <packageName> true
+
    + +
    5. +
  5. Simulate waking your app using the following command: + 
    $ adb shell am set-idle <packageName> false
    +
    6. +
  6. Observe the behavior of your app when it is woken. Make sure it recovers gracefully + from standby mode. In particular, you should check if your app's Notifications and background + jobs continue to function as expected.
    7. +
+ +

Auto Backup for Apps and Device-Specific Identifiers

+ +

If your app is persisting any device-specific identifiers, such as Google +Cloud Messaging registration ID, in internal storage, +make sure to follow best practices to exclude the storage +location from auto-backup, as described in Auto +Backup for Apps.

diff --git a/docs/html/preview/images/m-preview-timeline-crop.png b/docs/html/preview/images/m-preview-timeline-crop.png new file mode 100644 index 0000000000000000000000000000000000000000..724a6af8bc513583d0ee8fdad3ea7cc44f13fd3d GIT binary patch literal 10205 zcmc(FRa9JElXm0o?iL^kZoz3J1b24}5S+#vx8UyXfe_r?rGr~=_YmA^bjbJ3tTl5p z^REBquZvUX)RtAdYOmV0pE}{nic%P;q^JM@07FLlqbdLZJNfz^g^c+6)CkVu2LMnd ztRy6qWh5l1m7N?ctZdBz0FR|?HFxdATSAfbTXQT;@rARRRNDXmEnPYCPi&n6>;!;G zFgC8}z}GNTO?(2JENPAYz*$u3?69r8x6PJf5n;NK8v1-ER4XM7KAxw?#}D%l?fY5# zkK^D8EPotahWNb#YXHCMS0RA~s#qoI{-F+kSOVz{cxvpukzPxL0RZ3(4(#FUQVo2B zsd50o0vu;q-{3+vUxHed8MFY@@qi6l+1E!f#HVBz3b0#AHz9h5ZGo~wo0XbLhbO%cCqIr30FXkbdY<`!ar=8a zn|l`fwx?GE1&+VBd}udEwf0*ogGKd2M}O_B;cCGDOoW zx(kDzKqmHXm8voOBk-gN6Q_ugsCNr2z&BLGk>=rKY+~2EDv z#xtQ22*WXrS)d(9CQ6Tir!|r0PVg_HJ_y5Cp&j_?R0LZpZXItRO?ScKgwG$XFM1!h z{F9n9;xVFKiX$nYRt4@CtgC3tcPi3|!93?F7j7&A|C9ooDbjjMVgJU0k}0|0t}Xzd zh!`{fDGp4Fs6`X~s8C7caBWfs2%*`oHjid3j~RtFuNwhbcaF&^@*CJlf4n1P!(i-Q z+rYRuDQ$UeiSP7BboIEc$XX~t!5qDew29x9>ghdkq5U4F0yS~kpUN3dXeeoN=nWY$ z@r)9s-(U_U>?oqr(8qDgpvl-sFH5r&sTGM#V_Rj(GaSa*4Xy1U*ZP-Jr^YwMVZ|vW zJPh^iG~o*jgl);A6ueO_O2U=pF$eC#f6L_*PtW_IGFF=N3;9QwK(4NgU7njVn_6fo z9=B@-{a7ZU#7GfK;p}9Fm8I3~7q$bJR+QBsO3Bp8)M=aFNC*1|L09hR7$F!z5NXr5 zBsL^oBqhX6By8#O#RxO0=|9!k=Q+vJEz_{l95l4w-@NxGh#$sH7D(1i_D$aZp|0Vq z0h|T@KvOT%z$!D;^eO(NQK!6Jit>xFY_^m_qpkEq<+!T5YOL~vicw*w(No~P8Aff$ z*H3vN(uL|~O@k!SG=zhk=I7etb55FYhs-u<3Z{Cs&?9*_ga<7C06lOU;~hg++yL1@DsQQsbUu$G)3>cdcf>#Bua^gnE>5gm}zFE={fdVG`gK#l3CJw8Mn`7=w_&6_|QSARF}n& zGskZCbGct{qhrL&SU^PB{C@lZPGnF7HrF#Zw6nOAc3rrW&Uel?-52RG=Rxp(rf1pKNxL94%?8j4Qr;dB1tEL`ryBN z&-sJ(k4n9o3&`b`d9Hj%=fScg<~+7Eszq?wy3xtavfSEM)z<7Nv)RA-M{|Hj=$+(w zDy|FO8;qYx|*nQg!uB@F5^%NJg%H5TM7NWg_@sS*NAsrr_IB&kMX}GDi zz}+Bfab-4QrQH&H1q!^2;LNW|lAQ(71u8X7&9XuXd)b=FH+-vtJ`(p|LX;1dvIyswqNC^3hPxXl`#qB*}gM*=n?CAG)s3#>;B?ew|M>or9%rO^zMkOR&K7Y zTWI#sIp3h|l58WSi&P_WXXP+ZZT;+FbvErY@@1qpY0}V$edU#Iiy47Q@@I`x>(p62O~3a<$wuXl<=-pssy{XFZD}bQ&3a#h?Ut6- zWSfSM52X)_4(-ctb-Jo#JFLZKCqvFKD#*^Gcgc+GWY=8sJ*}@}#_Gq0$KZHOc#ic( z8_Sn3@;?;bcxL+mNcvpcPoD&? z#*&(nwRY|Kt~N`#D-GntdVTXkx{*9Rw03c@U8(BosztF={SZwlE#SDD>F=AeW4f ze4WOO@pxwao`aMtd4MSE+yOy49|AzUde2jrTC^&UG z<9Bb}J?lJwH_vL23+^}_JR)ndXILd~rffY&I1Y83t*`#pm(F&63&@ zyoq67%@^>YbJ_m-)7FFBg!bdY85%TlqN@^Idg*jpR$3(hp@UGhkAsEJiyte-mwir~ zPg~a^9aQOWA4Q*)FQ@L!ASIJZw<7!A&yQ@k!Iuv!{k*{d0ELFkM=^DerQ=nwH^FuO z^ZA7PUbzmkoGBolJ{TTnk*4Qc*l+=Y4Z-=3*&huz=1;Conl^UV^MC9d8m5HKI z510h?Uqz>VMKF3$XuTdq&jMMB!5>hQsnm3Jo#p54?(Q}}Zn-8^zB^1YSIugSpe%J?)=DWGMYy?qwmkY^ZBHEFvp_rqN&ZhgOf9Gp*#ETSY(4~)uJ5{OL0&k zH)?_x!6pRv&y(wdNL{dbo1XUWw z7vX{j-@f98HvG4{wTHPxQdcx_Zge3tWM(L$<2xE38=pdIYyaRez_DCn!&DxpRB1g= zmNs`fGz?c!{mgF1Go4Va_vY9*h&4dajrl0#dHU?P4LQAnG;^_cR>fz}MEW zj~pJP^HAB`x<;P!gVh;^Hb;6$VtcB(y-_)lHwM;Vc}0C(T-`nR8Nb~&`R5zIh#QPK zc^jhhTD>34R$#v_>lXIcNJ|=F-N8LNSD;2~haQy~$S(Nd#`vKQW{KsUx+>q4y=pl| zV%D~Ms1aGdFke%{n|X0KO#}f_Y(L<(fZyR02$cYx2)^*+(lgCbvYYdC)Dk+Yu0J@A z`mvu~&Bxx^<;E;2pLsWt@&(1 zu%*eE@_VKnx|ZAY<~{Wdj0iMbh!_U(2HnbwepF&)1E$BfUz%*2eXbhejLYpp?0w;q zM5?W|yJ$W)!CWBk#b0w>qbaky=pzrXm>Lz0aX>2)9W$wIw3z(PJtJGz$LfQJ+ClU| zqKs+l`*(CmxQgi!LJZuTvu2jL8ir{Ym6pA@gqEnQZy{PF3*+I~n(Ebb zCz17!Z_fAiN3C~SbZv>6o5hj#OpzXofIA7_t|pYD%pXlOhJ-S@FkpIjkh0Sz7g47A zYkeH+yhSci9LTUGC+oY^RIYuj&;**Dg^9p>Wl3eh@XZ;I68>=O=#?7q5_C0iPyUs# zW=TJo{^_C{CMnh7NHheK#b(raWiq{cNZUcs@QOlKtIK&Iw!sJpd{>ec3393qu32;Y zW0O)3UW3F}wxQO$oXj!dpc~s#pOe}vLO3iFQ*yEw4gvig7=X{1$C6I>EF0)BBJ%k1 zmbgP!GsK)XCAPXxIQ?|QFX-e(6zp9CwfZl+#zD3^!ffa2r{jP&iUp&*3z+_J!r{@#mi9LJLGjV-Qm?}h+DFU$) zV7bw?j3tZ3dlZ->C07ff!5j5ZeHh)?QCYXN*^DWyTN}fau{8?8tij>1LL7v`rg@$< znr793B)Epgy>b!)O9URZ>uM9uEY~oy&}|W{IZnWDzKt6%1h3ba3?wM(-Bw0LQ|8sClx`Bd`G`xwZuy5zS1yihdvKz4Ls~+=|bI?LdL=0*IbR zi09!#b{bZ!DTLvrAr~L8fxk%`EJ^5@){*pLdFb>+2)STvg=5k^y7AVL^HR3VCGV4& zg0d6D0C+~xJxYJx@hi+Ec*a0*;n4FZn~M*u;GDZ#J=_#RrG6)^ppz$tTJkn}SV|_1 zm?g@E!W1ge^1jH0YVtaA z4XUf@y--A~KhsFcIrI+Z0(!$Q9R#NQaY~6TaZ_{`p2R}AT&jg9V!SY7-W7O5=HId2 z;dt?`qT_D~5OI7~*9@g9W7~$^_}qR+hu`sJ@OLJ|>k3hVK|hN0^Z-R2_v3&Rx@jO| z#lbpEE*9QsKgM`JheVH8;@D|Z`}D{5XOj<=?`@%P92oq4g04qyPls4^psaltDcgKt zbjqpFT35lE8@s6Vo=H$p#+t7SY`Cf(75H+)FONcZP&bN1!qYP>B0>N$nk<5&BMd^c z(aM#Xk{yo&AF>5z!h~+U88((m#fdKOp~^u!k){Tr7aS_W%CZ+>yE6i+c!j>j0H{@G zrV@L-gS}R>JQQPueqg^#g>a{~K-U$^rRW?)1{k|#tXmRKt$4=ja6T}1Jm7WB*GVSf zANfh;Uv=2+>{Ru!r{ouU*3>xi_89x8-7<#x{0&{v>qC_tk-ulW6#EQk`&NEAKP2#Q zfI1Zcz`281*J2o}{z5<7);DHSoWJ(CR2(sl7ql)NXAoyz&ua1XOJw>NqUSSccOQjk zdC2I;=Rb4DM!CHd=p?tuzD9%$JSc7-V?0(h@^-_DZlDT!e)k^dl1D4opUb=ordC;+ zYJ?8K*LMk>5;oH-ou5pT4ZfXt!mLmC0gu(ys@Y6FXqs z4JHcQslR`(iFc*YzeHT)!?syG)_tx3{~_@MJCd1xSd|KLQjg-8@j(Ws)5Jp1VHT#4 zq^2fr+RT~hgh|$Ca%WZ&60z4a6O@Hx%p}l^v=}D{WfH|)0M>0{AF>RaYwd92g3-GC zxF*SL7&e-T5`}Bp$F_Z98Ru*cv6HkPIu~tx9&62ww$7;h-d78P(z|MT{rma(hc@Mz zg~N1$=tF3{7YOkI>yv$9T>3v5%gD;uUOsJSl5_Uw_%;il;U5VpyH3uwR>w_E& zAca3MLUYnC1OXd5!3kZmb9eh^Zk6B4%QFleJe2cyL0F*?Lo44iwgDPbw>^u*}lM!r)*(hL&B zIciI)SeCK(#TiUT77E%H#PIj=(#T8h86TtekFM(BQzPbMM<|(iTg@8NggOxd^5*)@ z@rAq5oo0c#+^0ceJ2}x0!I5FEQ~Z3|@2%+YF2{s?L%in zdeu>%C%?lG-){}zGTQcUk2w0wJ6?R3-%vMJE6Lqu9;Oyu(Tkqo4^{4(sg{R#Q>`z+ zcO*_R`Z@uOuip`f0)_W4b>XB6Z^A~UORhZd(j&ya6B;&e`f2WLZa%wn<3rJmE>0J~ zi(ee{*P4$_f!FLcMzxl=h>fX7Rtw6$Z_il|Huok@im$R26pXO4&v?C`4~L|4$0`#_ zummN>G_)YU!x2Pi37>qHB}H(B%OS1##wce35{&45&1Q~SLQyU8S&!lPY#mf*F<<^} zjx=W(@6Tms`X9>gb`sC63tkw8vLiv4?BjgZWQ)yiUL~w_dliGOth7lkh{mAX3R(Fo z!b{!9pfwUoskO0X_hZoDi0f@bi!vg>O&L*0Tk+=;v_WTZZSG(YsEx5{O z7raH%+*x*hL@JBw8!5sk*&>wEGMdhZaOjPw$D5nr9-+5F)O6j9NKU4PjY%`<&Nm6y z&ZtY?=f!QSUz3*gh{mxe9ulSh>+0Ye#h9|Qpxa03k$YkZ2kXX^T06aZJj$}ZxSBo= zLzZu+wx-(=w0X#PXf4nt<56wI=n>P)9|?52w`QVRn{g>W+`7x$SFg1Gi-NYE{BAMQWO&u^Zq4{N35*!$ z_x5*Ob}OmP1)*APGGcs5A#yaNGj#(yJ!Xn>@^#tJd^k`+d`SSHGpQvsJ72RMmRkN# zcckt&YQaw##|0!^R4$zWz$(+|cPFw?FMr z=D>%o?}A9Q9TqZ#$VD(JQd_%bEwD}0{kp5Y;5Jm$pl&5>g)X~@P7L$L@@(yQFuAw{ zMj_`0FzU4?8l}Dg!y76?)S}#-q`88ywgdwsbG!;{2AwG@Lk;15k?jb%%}3=k_nY^f z7;`WYG8Eo0r9pZVS_QFt8mw*XsfVdmrrN$ZG5o1nkJyIZ1ar=gPl+5B@P^(~j3;6* z^<@>ha!ys&QCx{xLclrufo2KzJ?3g-8Cdk}Yx|jE4TPONyI#<^#qVanYS8Rn->`CI zbgl5jbelWnU`tZg<1=v^sr-9(j&nsRS&B2+P|7kQFG5HM;kpd)v&X%7wMKsyvtxu#`O92f7p|)cA{gmcr#Y3~d=(ByPXoN=F)$?-5;Eg{`WMX&34QR8#s zIs%6bTz4?(&Dv7y_8v;7^=B=WQH(CMYQ z>*UW$kNlOdfz6T>@ywQBL5jnIb1+MGE=}z3owkTxcdMqv5w2+)u@d$~xE!5FOGRBu z=n!*SsTC121Si;HqC&8+@KS36wRsJ5WGO74wGH97M|)a%0UNL&2L#uKOWk%sr#FXd z1L)ijSETWpUL&;$)mFl#KNck=RaQZ5=qiZGVk)f5BPQLyT^`T1XKEUzIi8%Sk)eri zeNN3{c4>5_QfT^y3KeNJDNG=P!sNCSU@6MO*PQ7tsPvb&`gwRLf$QbI`M+U;cuYI< zh<|_q{P!;3MI--y{sSi62IYpIRv@WmR2XnA4&wXeZnR~bGNDfsDr<&0>+Rf!m={+2cDV53?XX6w6PZ2js>Dr^Gsk$8+i1F2)pOfogKHw9LXxBkWwMk? zWoyEXs2uNdk#jL+GFbAjR5GbdahgSu);o1^sQ?F{Sheyuf&uE;~MZ222yV z$0#jysr#`DWfS5Klryj^H@FN*a1vzUbuNa_@Y8vMOOm32)~v?jove1I+qh%>E?;@` z5=;ml&77DS>tb!rYH97dzS@@TiQQHyI4%!-_L!^j%|dz>iJ?CZApDEe8~_ZyO0=e~ zJW>UbEOn+Ie~L(1D;2~0FXL1e2~SRU^mhzMnH%E#72@p5BIqhg(~l6EY2SullFaew zuNeH7kzSibW|^n{gknOGRy|bQeK-@|MivOYk1f!rfD=H}ZFTr?T~koN9P##5Qu=R4 zlCQfUhyHg5|8J(p_V*F2Pua zWMgQ&6drywbuXqH^>5FCQQNx@nd?m8Y=qMoeMw%)wm?!iEnsXP{|pr!bXkoyyDa{PAF z#sHQ1Nz1zNa~alVtCotMLX)1bVq2hzK9P=Y3`W0-01dHy%+S;E``tzY2|&N?7hzu z)i2nij_h?P`JVbO4)e(;{13jTYp0iCHfc{F7E8;gKvz=GK^UmZteq{HiJ}iMp?au| zdW(PYaQz}Z;jpZnB-mS`<<{+P1foDu#I8ew!W6%?Zm zH}1At*ugZDw&zgt$%aWdL*^a<;RbBLtvmpQZ-L9iz_{S+EW%64Kb^8g&mqNn2CK0= zXHGx0bpu5cY;dbg2C+j@TCTowh$b|I>o0v2Neq1VaEpBMebjOC6e18CDt)udmp%kV_3O9(vbr> zRP^Uhq%_I+q>P}8`SLA)MO^ZO538L>15r;4VcVMcRrhJLKh2DP67gD_Vp6`M7VHY@oTNBCZ&+foEDt|TBnrdFjO|-w0mWlVLz{b_5)F= zReT&Ssb9!SpfavM!$6DWnHEkjC6f25XRzNY98 z+=+9Zd#o)h()XpFh%X511|Xh^@|Jj>wzWMOz&4{^;dfY;&>_<&j`psHd@H4k=&MUX zM-YAvj~%%aUa#R^PuIK}2NtqC^>y#y!-wiqKjy|(#(W1Bi={6_mb&<-O1ZnUvD`~e z>a(+cMDranz%G|@n*9+$Gh!@Y;*3isk6dW7Oe)x25D0Vg4FPJh$eX@FY9S>|Nq$Y% z_{F7&PPKLj-rF$gHdD#Sok_69`$zyC@b;c^x6Izc`Q$qI)0)JoVPZ2rwdRCsbOCBT zIYSW2G0hDxyTqF5{YQT?V&|NIoZTZm$BjoeM_(Y)?Gf_YrIu>-NZ*6|_eB$OXPsIu z#FsAd`seTJSZ$D0&aCiD7W97IQ+69HBuPgYf|)& zY)77`YR}Oim3+nTynCF%-xhkkOkka1#P9Yz&jukM-(zL900ZQDBAG2unE*IPXow8V zpO-cU!8w*sr#(qz#H94k8$>#qr6wt?Dk{EcA!=zNPvb%3YI=g9OG`QmO$}eEtT&37 zggfGqm~GwB`wq=kyrvS5X1_~IwWPF$)RNn3Z5vA6S-ce+n1_nM$=sQN$kp z=*tyJ8M~-ET7QD0yRt#;7*TXbJ^PDmC$b!ct%|+pKP#$RH4o>|&gktZ`%A{o8V?+; z3H=2ZuZ>D;j5-(Y)IEQFhUNbG7%RF|q`P6G@8?2>@Y*%WKpVbYNA*)kh5 z`7}i=p&$~fL%|m)5!en|)jZ+(3o5SvT}AyB>6i>cuZ#b)A0P@0#DbZPRc@T5pWO0H zaA4<}Fh(5Mq~h4}vuPH#%l|o`pRl@hYs2g>*FA$Qmr3aZLY-)DOoR{_&K_BHVHtz{ ztRzhz#tDN+x{q&fzGPUQb#DUtw-1*eTO34gxtR4ptA{*4r&aVEOolrJ7j!^mV{G6B zq(}qRPm;8r_+)+lT?P_rtV+V+n*f#AYl`<`$8T3??Z7XXZltltgAkppI=>+MBPwEZ zbYa`9Xh0(6envavo!ItM`XXOi$jeUi<_xxr((8`Aq_AKCvF{JmT>6c9T@y`K4G5Lq zvBIe}`B$vBMJMw_&!mESLfAVWsLb|sEUPzMql@cDLg`Nv1PNiEm+vkEoyceKAn8F3 z4i_6i4S-*>KuOi<*{E!xSYX!`8aXeD-)}}yf;P9V$-N1mvmRXrpPRPezRTryzhQ9h ze%9rm%+8okWp`VaMpJAb0c-1hZP0XVmlnHamZS&ot1JG|b99Ffh7&CegKEP1l_D?r zdv;HlU5*$sLt?(BEE>!2t>Q=ILNB0l_J!{pTsdTwT9hC;vL)5$x;ah>P>Z$b70Q+j zgv!_)`!J@OB)jy9-u`jK_b8m!)7$#nv$ew*mn7)<9!c)p!4RzDfRjP%^Jhe5iK1B( zqOQ;KwUI6Ciry-h7wFZ2KfW3tCZ3H=y_IcSJs&er*D{LX5b50{LJ8S3IVN?pe^Q+h zdX0@rrc+hMSt`M5gt+KHv=533*8?j;?w4YIH?v$XF_z1nLI&)2jIce78TOl>4NO%s zvR=I0G-g5k8;3Ys18=ACC@vpmK*GxoaL!~mV2LZp6( z&*Qrx2wrqk{l;@Hol{YY(S)8M50>$7BI!*{-u`IO2qLqCMk2h_e1n@8@Yc)qZ{Qx!6 zKF{4ec!53^G^x+pnIb|Z`Mv88N|GFZG2+@M*$M1tWlSS(R!a|#96euxSl%&5%#-iV zzg75RJCgGHm^A)XpDUW`hol`Go2(93T?TxT_;(R(M@DnmheBJCh6tEDU}%c$kk{>$!{)2JK-Kx z3Y;y25xqt$bK8wGb9P5TGc71u_n$C+c^aaI@aGvmJ>2g!B_$i|zCwFOj7n&T`g6_J z7DMq`4sGflDxRKRqSRA&dB`1N-MYZpp~d0>dkju^AtcL$h4MsxT2KtgLb-{StW)=! ziuVy?;5>zmH~bARMILT`#f$asYUj)1EsoayG!V;19<|X3RU3bHbgR}fn0c)r8Y9m% zjd|6sAQ0OIs;dk}*}Qr+IeDF_hVuGpy2a2oOP+Hiul!T0!^l%K6rAL4;Wl@|s2gGX zY!u%jyNz!ck;+y@Br|Can>&5BwWi|q& z+b6&)Y2k1q*p~fG$J`1%PzNF2=YOYn!g4U0EghY0wBmeF!2_j0xnwfVpsQ<7(L<>R zU`cJRRcIbDqMTx))GueA(T6*mCwBkAXT^&;IB@nr&2i%9*b%zR`Q$p#5iWd{K6rSi zFIq$?8TwM0oXeqpAa-^jkqFyT>mNTFx=n8nVIvG^5n~op7u^M?&nDR z)-PhAhVk6iPd*1vuLVC7WW}ZeW;s2z_p(3<`Xa2=q>SC?Dvl!i5}nCK(jP5o--P(h zlfL#g`^toBk2qfchwWPiJkxJ3YiiOjbha+>zFXGmGjS=J*k1D%5`rL*tX+M=Vne zgP#N+@$f?wrJjU$s=h{D4t2o!bWBX1FI^T-QAm_710$v}#_^Mt)_VIC{kLpnJaMAb z%@|9`Gxo5uJXtOA^Ov5~EjVUjx4GD3jQm&#)S%BKX=sy{1hXg&A#*jNv^a{t23O^L z$uqGje=e-4G*L(pHvXbqqd7+5{9^Gd2}i0A2Yp<@5QpYOPA1-v369h}N`f8M0g0{qbp*NqtTTTBc zGGwig^u`q=$%x_V)_))O-lPWf1AW%=K$MoS_b1gK+K<4dXQsR^0#z7|L^IK?A^Tkf zYb+3w+;lzI3rdDh}VrQk>lxbNslAbDuGf}={VoR?N)m3(UVa6iP0)3v;FJi6e z{>(_qT(gQPhtYzWC{a=?`4!7kO%+;snK=z%m1ZeFDL>io?+8jjbg zK|G2{e4sPXdVgh7d4f~QJ}7`$GkFH&1G3=GVYPT3tnyHF--M>!Db=YHT2P~(r?6K4 zOZZ=vlD$*+KkHBwj=C;Jp#70uhQmNgV3Fhz5sbwa=`%N^}tJjOn+swbF zQxqz^n@rmMea^50J;$|SwlUd!wMn~4y;(Q#4(r$J_t$*ysJ=%hMYl%Bo$+rqkFJj{ z2v$3oKen-@+_1Z_2d2D8u}wiui7QjnbDe%VomB=X)0}$k$l_?}IOljb&0QWdT0H8L zJ(^{~|G04ECqgc+s^dzL!J|rf#REqSm7Z@%IQ&fnC7;;7#y0e{a3LF&+fN zc++?rV*WZM{cuRvmborUIIpq_Ud%NvQMgntUiqP<&d{zvqi%%EERowpNV?IqQO8F{ zQ5R^jyl;6Omf4mCYad>gC6te|7Z?|a z_PqVj;P&lAV%>zLCNfJoQ8}hxU1xS`S@(U*X#FU@)0RC8f4M+wZ+^|9kx_*LELXTo ztS_*@FXM&-Pdv&nDvM%?!h#ddsl&C;$za50glPz<->bRpn(qcXnSBWA4R>7sP&ZPv zv<0aw>f%Ie7Rs8~WoB2pqo zf~?)Uy*!BL+7f|=@V;F-n>pUTow?J*c#BbiyYr+FLjgk{TLO<4mlV?rqpK6Ov-J}L z&x8e&=@bQ;%)PAl7cpD`d^7S}k7wMR{1q$*eocD5KwlpWE-QIC+3r@QxW0)##i$qx zRSF-4e#PJN(~9cy0rDVuRgfX4QQd|@v~e_JkvIhd4S4{Qw|nW;#FA>n`oW(k>xbNY zrm1xY^X`z%(!tTHc#BRWH+Fg&2D%mE$4IhYrJHJ1=N8RAn;0`mtr2&L+dUlHF(+o% zHunh_pwG3R$K^oXW|1G1tCY!=*U>bkA*)`s7N?;brOENh1#En!yK`C#b#hFtTk;i+xbLP>N>CU=B0Ft8=Vfwo|mp z8PFag**f08=4iDZ_88Kx!N`D@9pc3wt8fmWwh6zTq7og&cB_>o#9Kib(M|_pcm%j z7gmFRzWvc;UQFCyF$yxcSsJ?h42OQd{C?-N>W$;GxU}1HW|(eeWIi`mwQ5$mIdqzT z+SqDv(5`Q3;`W}%A4|p_R6yFV6MvP;Z5}8X5 z`M*WjBR(9g=d(W1WX~>>tVB#-&)Aki&ku5E-jCLOwTlaHlI3|!xvAFd!W=Cf=@K-%poRSuSZ8zJ*-^ zwyk$ICVd=^ii*E2m$yq^h9dIrKAiU^>>g-dYo_GHNcsfg-k#meRrcAH94eW(@KE`GVu$U;kAPV=VbUWBjWtS`3_Ax|+Uk|LFi( z1(o0Ce~yZcie`_^S^MJe7>vkiQ2lor|Iz7xwekPz*^nZ|n3jD%(~j;g!OFVv-jSKP z--dvX8R89(zd6aCZ3-%$($Gj16R z0tX3q=Src4X|;w%6L|%_)-&y4m#&RANj(!~ev<>WPSduMuRw>zyaA8Wa{wS|poGKR zIj@7|fUTZJ!hqEA3DY%cVNf}Rw|-ld!KB3FyXE_1kDE0g*A!G}3+9nV-@cCB$UwVn zgzVNX1e(xn`@I;3n|>rh0+(p2YAo7d4XI+WyN!DcH1IxLVmPq}^E)#(F1?n)x;UhF z^W(I0)OuW0O*&w>9UQ%9O3iRLZp6~X>oDf<097VewqEuf<@gT)8HFo94?Raqf#C0H zv`YrGtK|r29%g+kh^AhYwC>=r`je4VyfN(~5zp)-_}RJLB%3&w-rvanf#=vop`J9)Bwv}W^TY6 zI$z@zaewIQsxakf*pVI0AgmjHb;N;-%m3=@*QZ_S7-Mg`E5GVV-i$4U4sUI3^_zQa z-=4HFpRPQnvG=wMvk94tzp4?V=c#Wvx}>S%I?HnRgYSoSDZdwVb{IOoNJ_fg7%YnwjSggYFHXgd-`dg zPrKf|3j58(Dlc(c`SOafO{+QP(RvLKYSTw94(Eh697zVsNu+n^nx~7%)~EU}e$DHg z^P@w$=bg8Vy&hysq78U+rVRbHKE;~%dqk%_L!;KSDbRKLp;)>%Ox8KM)|=tOc|ub@eU^G zK2#;a=kBcGTY$?yvlVUyKY7iQ%|hIb+SXWfST2fOx_@$@bs8oq5EMGy3D!EUQy4Y5 zSBm*A%(5>{akb&gk(R2>l&>P3tiT__j~)ezwr+a2<|Qr)=6L=4LR6;3xO`X2_npvo z_WW(bVmTlh0IG?`h@rH)pMqy&z1?T}6%7oj>uMiGgMU-c)c_*!1$>&&{kPjo9L@iXp z^O*MV!@95-OClLM#0>b5g6nAjCOUK)#%^ioI-7_UzjLlsy1q9n!W}$dwoqQFGMac< z4h4yC_{_utHsdrUNv?C#Z+`!Z-&E^X$ju+jl}I%I@!+Hrey6mb>)pegBF%MIJ$kLn zyKmE%R$l$2GhJ|BRhd6d-L=K`W8eLi-Dr}lMpo+4B0swoS8eKKVYl2aRbI5W{n7;1 z*c~Aq3EB=ZEKN;|o2M40QDp;0$4>$-iI`e-cxbIp8r*O4P;7K{*G&3^1&&qoz3!{-^{7)0CQLiKgYm zg4(#|KTNZ>Q|s7ocFuWh!$mI6-oERIt3AA97NshnLR#IYO6T$mk-p81t$8z(I*0PW z=0K!=>i~?Ee4-8Qi`=4@!?-sW<&X6cOY_w-fPkb~joQO{Xlvn(O^h0sT%rSY?W{N9 zRBuq{?l6(vT!XdGlGwn=gYN_BT`%eVS2i%fK7)HH+&lUBQr4h^;r(rBUgx0MhiW2c z|Ad>6nR|oF9nv()hkO@f<7>{MbtbI@8!ZM^r@0+x?oZ|@bO5SFXYN%0H_eA-9Ow|& z`Eb8)Y}>ax2CkgY5wZEL;BTb_1CAbk-K$2WtfoE?L}WK`V^+xf(uRQdC6}!^KGLMW zl)$-NE!kC`h)!Vg-64Q;t}Z+E>&EK#84N(^#CuIiQSY>3*~j};9bw>~WPX7Zg#aRY z3g{NCU~pY01U5JWNM6y*X5TBK+a{tFW}mm#nmGw(2vDlmm!x28QnupH0sMxC9hNUE z*(aq^s8i1wuD#@QJve^O>o(N))1*Kg#Qx#}tvfm3+$PmlScAUWHuUyTjqLRSD7fRw zds3qA^|NW}w#VB+r_;DA$<&;{BhiM-3KxGcr#W<_0W^8#Fu_6^5l7c3Flp?et^3WE zrbUyjNZ%Shv#?=OQ1zpH;)79xcR^N%CpJIo^Mk!Y*4+AHX?+ZmXXigPEIObF9eLjP!GxE|NJ>>|4YA2U5-gF8@|8Dyt zZ}T+Ql!Bl{(}MqPrb~8-J+>DDA4Yu#1`EPxZF2H8nq1PL39y7W+4oC>`I`A{D8^y4 zl5G#Mh3P6ecJw#dL1^W%w}m=6*1IJ%lCKL~k_{&2-6|I+LhAL-SVE^2Jc0yGkJ)AiF{y(;fY-lY(1>CC{DINn5tKmyP}rXU zp<0`{s~XwJ8zxlGp~&@C)Jm$eMDs<+7$hrE*2|<9ks29%A1d1X0 zR35?~^OK!fiTaEBx+L?}i-efVhiPr`a}7O7Q>ZcYJEa2ovx&x(ySKoo-n0FZH4QYvsjaHatB>+Yv%o75O zN)>Dz8xb9ZIpbrDiRfk*Ntkg5O*v3LJ+WB+f>-@8yv UO&xkWl(B+l!M=M?Og+4mVYC6VO|&c`__3?7vrN1BkFY*Ls(?d) zKhN&Y`ztVzZ9#3wZRbTNq=WEHR_?_s-eldeP#Xu)Hjmr` z>>ooXx56wIE_MkrB@U;G8Dn_&g{K*vxON6@cV2UKti`28l-;X-Ad>82SAD*&& zs6SOsy7YScKAS!3HRAa_CNN-0#EJcrN=AME_XiACgz4?tQX}Rq_bxAJ-|4ueZDv6Y zUu&g)8phgxOO{zbS9m!(w&7k8G`ypDmRe0gXQ?D91W|{!2j{Zc-L8MHJ#1~v_C>IS z#DY9C8wvyl%qNJjD&1fjz;SQ$u~uVs5!k2GUDEztX0usu!Lsj|iR>Dk{GDsEl-^dZt@tS39Lj!9V1X!HjBbU`-kD7ed8eM-tTX3C>CBI=rzQ=-N~yaZUXWe6w?m5`eLon2Y*t<#I!D`)O7%W_ zyIej)sBWV?uPv7p%c!NxReRZYF%b_Ghpz(=Ma7#%yAeg5w%u`m5(fqOwP5r^BK07k zXliVbu(#Y=2{uCAP8v}DeOTAC=B9xwLouj8Yw_Vnh4cTXvG7<1@!sg;+7bTou?#^j z5M0e~63N@`%xlRsk*H?ot0?md||ytDPFZ3|NpNmi^<&74b_qEDl^hiXw6lF^Ird@bTT4DD(9; zw#dxJ9@wWEyDxP>9#Q*-y`cK@RjpwssZ?`T*k+Qa68P(Yn5aEA8-%*kC`pUzD- z%m$uZsjglB2d=48G&efgdz4`xwo`i$(5KPk@CijkV@%J6j|)rzv?<3zGww2ZN4;45 zIs|4*E25SLq;s59$m^Q_Qr+c66Qm}UPiI7t=B9KJXX5n0ziUr}G~WyWosH!p1fPk) z#f-ezY*0~bAh#h1)(aBxEPzQ_0MMSO8+*9RUukS@xh2707gC0}*p_tLCjy0kTTf1! zp&tfkyUV27yXjMa~ zWqV%KK$IAR75-{`E;{wc$4!yDzOtr~u;n|`#x;mjwv!`@m&vl0r!ij1ONt%ejE1ea z%Tao_ln1!6#2;-e_zri`0oNM{%k8TMi!rT8M1W^XQqh(}!VS&Ne4cu)ke?f?bWX|6 zOE$56P_m%j-^9|0n!DklMsIF(W^_ z0^1^IS5;^A9kPDRaL#Ih(H3?1#sTw;`yO=kPCVDZV1b{j4YwHU7cv!{AbgSQS0Jum zX?@MW$J_4_oN0X*=esa|v+SefD|?*sZ|5yAc9K~2Vqv^tVt($p+I6%>_B>h;zzfky zj-{+z=PAzUoxbG)mO^+4?Fub;Zb6O9jSx2xUPa}8FB-bxtWp=v1#`bHOuvP(=U(*$ zr44+OihG4+JgdeM=U+dVVR_NqGRcX;_CUD1z7ytqE{>T3KVe()1rdbDwv;y}5gilS zgy)|M1%gDnbqc%5Qk2-qg{oUXs_>ofFV*dfXFaw(4k+I_P)!ezz-h}Nnatv56-{+I z!VMLgW%d10v4P($8Y@50JN3Rr{NYs>ng5J6zHATy@~Xx@-(vx&lM%vAeY&OKibFrxrvl&k_Ls zGH*s5!R`q!FUZ34vd%eG@;A%&U03p3(@ffgTuCOdGPEpI!62DfM^RXPk2kYn4St0U zIxqyRklcZ2Nn(WGV*f+2S*%y`4TS=LK3{gj!6pNA>$UIPF(?i4E9Ja9tbA$S5hN@u zym_Ve+&o~|`wxrOEXP$cz~Xzb;SZ&gSq09^46hzVM*7W{^b23(C`=+jQep#YVhtqy zs!rJ#s=D>V9_rVZol00XS;gv%7xxYsf4<$je5y@;Udc66?KpU!NhEr;3e z$6;-BhI%j^AzfSHMaq>J+RiD3P0&BI?6h%+#^>qVbN7$`$Tqp8P|TL|D~SHGvAM>0 z#8L+PlY^bl|8lL#jVP#|eo?g&f4SjM$A2}f)a1dA_{-U9EhA~&O|F64f2iLw2(lqW z0!mB!AD%Kq$`9E;sPWal>|c7f1cq$*zjtEFn@|~8gp?o7H3FCp_5CtrUMo|3#ZX)B zJXik%|7gV^oM?wbBBxqRuuFvam3Bz2;R_O~Kd+?xqF;Iw%s<^6Kv>_oySpQKo^?8$ zZjDtW_C1Z5SxGkk$8A8D3ny72SPzx0ah>tAvlr)z!6~wg9Mua->!S7XV>_^lA zy(T5kN&dC3Bax+g^UbUbnK!r5dG=)j`+#PKv zA7JWY?czz>MXx=N42vzgv_rT_j3)rYDhAD>WK$@yKD2UPZg6tz32e)5&&eV5B zT{aOC7pJ?`?*ToT)NC~YraB3QJBRz;t_xh7+TQan0m6kkR;TA*1SYb>2+5!2KrQkS zA&b_hsRqscRHCnt7vDMRgz2{Vwoj~ce1FmUdfGe>nDJ(-cGuZ|-1r>w=-dx@J~?`o zL&|HW1Bzhq!BJt(o^5Zen`_;vYF@ZJO#LP?a(t?vP(NO(w?SVE_Q#!@y^XNkmLQ&4Q)=+{;>@}nj9PL!NvCt|!ZV8$hfW}>v%)1>N# zgaEs8fyydw()CyJ?140vn3=iM^~wWQ1R`^Kt6FSvdaF!&oo0omDG!C?SS{z?ZG7Qq zB2BHanx$P^$9l_eKHE++BUhoy^g@;v^HrQ%ca?NTzG-ugGn%~*-*V_b1{Q{C|4Tbe zQz9bvuWXfD3I*=cBl?fcIo2R;jzHpuR^+eEg|woe*0)j}{c~MX(up)Vf$I&Aoqv46 zAyRZ`+lKy+E5JgU>db1=Xx_`euAm7iYRxzy{JTe?)SO69@PBMluk;xk85Qq=!9V;) zwsW|=h4DD5k?Um^5sJvZjc`7?{YrcN@Tjm@4sCpx;Fi42xZ*YfZZxxb&&|napbZi} z_$E3ZU6y37#M7k}^AJAVanwS4iJ0upmg8^K7>T)$&%@2$J%;_R-9GSZweN0&Ot_Ae z#XGZ}odU8Ms^(m_CEFY`vVZ|c3Gso!b8bIJEIiMxl_bo9k4Hb&5s;$&#@!eN8oOJR z@H~(OI5)H@zht`F1U`2?$&qw8+X%jv6_tDpi@;k+3V8FrKjSha9mMv4UM{*8K(n?%kZTSxMP8SY&l|zNyR{5hpo?2?wksJes<7h&A5R z`vGsDr+$~oq+#%Q^4HpH$W0^%KH)wLk!01pxAWLIXSGmX?p&v&OfwM9xa@1TF*$G# zb^-SBKHiuL-&~@dWJqmon4F;x@-nn*duH{TXVRw?cb=DCQK-(BEGI7h@Ov-8L;RKL zWBX4YyHmWv)nC8rFfrZd)v#GBEyu-#DYv%M#6%EjxFvDhTbQ+5=6wbq^AvgpuijOA zpMoUl&?F^~JpES1+oTxtrLvpz2E||g>CmD$Q`5@y5aBE@z2Wn__Y?MRM^qjqLl#+rN(sE(>WdwU{qNS!u{hmlWW=zq-T2RN%PlwHbpSM2SzQ7aGF zoV}4fooIQC*J)mv)#F@z%nM9KgyTE97c6F76rQ{AtJxl9v8xgRsfStmbd-^IjU4@v z$KEf0xQQz}>l$c4p?w)P!8w_{7Kx&b#HA_Ecr92pf?HIcXk;Y~Dfaa35*f_Sh;-;@ z3>F?{b!`l>a%|quXNjoBB3!`N?-C0;*Vp0vk4P^bx`B~%?`dY)%;7?_o*@|TD&+d? zn#%G4O9`i2_UBA)7?bHq$hD9L*<(AochZeVHi@!YLigI15H2bCeO7vA`m*S9;**3G)yM9O%uKe2fTv1V7X4o-R#Gc&p_?tKKC?G-#f@*BV=Bo1 z6^_U47@hBcIv+q1mbs8+`IybUtq%b4vCLKltUwZ{+N2qYkh}inXLSoC!N7+uSvUgE$?V&F&(`Gj z2J$8cU9!0dE90|N8wP1OLXAn->~vd<12Z5sGI;VX@%5_q$@IFiQrn2M*WAds2R746 z4l97Shc{OSNe_Iy?n8B0wzbQ_S-VS?@v!>UJxyiQQ@ zF1z1$XI@X0PHaWwW}39j9WJGh8mM-jOePApj4}sgG#;g8BHY6Y_(K`flxEV<(F(EQ2p)zN^XuE%TX&r#wHu*HmRnQ9y0}$< zxv&q!GY7(ZTnAUP4A@^4Yg0gm*!KFK#E;Wte^$hFPK%d#-W7*3;lEKARl<4ugmzTe zc_ksi^fA$=Xr_#3#nkYSE70yv^>i@hk^Ssa6ZBlYSEcwi2r7SHg@!c9lmjM*fUS*+ zt;EI3l+4$|g8U9=F(R_9$}&q+s+al;5_gGY%<$V^t0IW4hlWbe!`QIUwu=XwLi@@1 z#mYP8v+*}1Gh}^3co+lPt20XreJ+!zC(Y`uQKtJ-9HRZvp=M~3Tu!W%=^#v;ZW%_) zu@5hH)#V9YlRxKaeybK7{%W;mx-^rXXt+Rc73*NYknJfKJFmR^ybfD{>g9^#RgLxZ zKF8Tr2Tw*UrQpja{oQik$r(ecoQr!rYbID|s8*<%iX{zMgjsgP`Ftv~V5=fxS(#;7 z*m%}g5J^xLI*?P*Jk7CgCyn^S6d!OZGipQe@Gv zhp!_@--P~X%oNz_Rb6q*(w1akd6=-Z<&s=lc?q0IZ=9)pr34w#P>dtKTRj~o7aYz zPv;M1Lv0k@-Q`s^3arU;(~?un6>Eo;-mrdBn3=Vo=W*I|PL)@YgwM(trx|Z{fG@|G zFibI@cn?8j2goacT*vy4RCF)KlZU1hzMN58M`rd>Jl;gfez{Qx)T+mbP(H+7KE6Ub zv^S7%2Q%javS`4J{?iG5MOJHn2$oXG$~V=PaUBw1%bx<9_K$cS*3VFBJE*q%bhGAy zL(|(z&e6UY{8s765OBqYz}@!*mgE;C?G`2ENZ&bPhLfK0d-jRs;HptS&MYOygZ~Vt zCfWLm0FDB^m$8)TU|g?rC~=;$j;+g(%KfQo~Y2BELX<$xQeY z`&oXrJKfmcB$OJ#*7kr6K#+Bs@p{IvJ#|82yMgG_<@SSprKruNAVp^8lRq(L;eJ6- z2T^qyDa=51f5Wf$Ji(S|TRktfh&vp7~ z{YiB@85$`?dvERc3fynSJ(>Yv5@a&_ZBpSPp^Gg^KEsVzN>N^&<>eS-b86chk1D;u zy3k6!eV721vq(|q80Ep|iQS^hWEKcmXyEOON9dhQk=L`T5}2@sX;;anrr z9T^&a{j4B6O%f?a1vEwVNdmx;X`}x5)$DxR%isLCD#gR@(IaT(1eC`);_O!QqId81 z!g-#kEo{*hh0ocA7rlJ0m4IeE zE@Q=QkJ4O2qw>`*#Y6_@i(Sj@f8*KQGCX^L$3k?~1QSG0Px9&I<0s_HAbHfk7!?H> zIkTzWzE2?kA0jmSfxiG5iChVhyGm$iE&n&+lnOxs^Ztdjj3FUmNPLV=VMOu|KxPan z!vE(%6XPoKxe+`>UjHxbMMa_rHuQhMGtOHaVky!8PUGJ>$A7i)f5X{$kWA>NWA&CD Tk4FAS1w~n2L#|5Z{ipv0mnB;- literal 0 HcmV?d00001 diff --git a/docs/html/preview/index.jd b/docs/html/preview/index.jd new file mode 100644 index 0000000000000..5988706c2db1c --- /dev/null +++ b/docs/html/preview/index.jd @@ -0,0 +1,73 @@ +page.title=Android N Developer Preview +page.tags="preview", +meta.tags="preview, devpreview", androidm +fullpage=true +forcelocalnav=true +header.hide=1 +footer.hide=1 +@jd:body + +
+
+
+
+ +
+
+

Android N Developer Preview

+

+ Get your apps ready for the next version of Android. + Test on Nexus 5, 6, 9, and + Player. Explore what's new — multiwindow UI, + Doze Lite and Background Check power-saving features, new + notification capabilities, and more. +

+ + + + Get started + +
+
+
+
+
+
+
+ +
+

Resources

+
+ Essential information to help you get your apps ready for Android M. +
+ +
+ + +
+
+ diff --git a/docs/html/preview/license.jd b/docs/html/preview/license.jd new file mode 100644 index 0000000000000..5ff52ba902cb0 --- /dev/null +++ b/docs/html/preview/license.jd @@ -0,0 +1,143 @@ +page.title=License Agreement + +@jd:body + +

+To get started with the Android SDK Preview, you must agree to the following terms and conditions. +As described below, please note that this is a preview version of the Android SDK, subject to change, that you use at your own risk. The Android SDK Preview is not a stable release, and may contain errors and defects that can result in serious damage to your computer systems, devices and data. +

+ +

+This is the Android SDK Preview License Agreement (the “License Agreement”). +

+
+1. Introduction + +1.1 The Android SDK Preview (referred to in the License Agreement as the “Preview” and specifically including the Android system files, packaged APIs, and Preview library files, if and when they are made available) is licensed to you subject to the terms of the License Agreement. The License Agreement forms a legally binding contract between you and Google in relation to your use of the Preview. + +1.2 "Android" means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL: http://source.android.com/, as updated from time to time. + +1.3 "Google" means Google Inc., a Delaware corporation with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States. + +2. Accepting the License Agreement + +2.1 In order to use the Preview, you must first agree to the License Agreement. You may not use the Preview if you do not accept the License Agreement. + +2.2 By clicking to accept and/or using the Preview, you hereby agree to the terms of the License Agreement. + +2.3 You may not use the Preview and may not accept the License Agreement if you are a person barred from receiving the Preview under the laws of the United States or other countries including the country in which you are resident or from which you use the Preview. + +2.4 If you will use the Preview internally within your company or organization you agree to be bound by the License Agreement on behalf of your employer or other entity, and you represent and warrant that you have full legal authority to bind your employer or such entity to the License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the Preview on behalf of your employer or other entity. + +3. Preview License from Google + +3.1 Subject to the terms of the License Agreement, Google grants you a royalty-free, non-assignable, non-exclusive, non-sublicensable, limited, revocable license to use the Preview, personally or internally within your company or organization, solely to develop applications to run on the Android platform. + +3.2 You agree that Google or third parties owns all legal right, title and interest in and to the Preview, including any Intellectual Property Rights that subsist in the Preview. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you. + +3.3 You may not use the Preview for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not: (a) copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the Preview or any part of the Preview; or (b) load any part of the Preview onto a mobile handset or any other hardware device except a personal computer, combine any part of the Preview with other software, or distribute any software or device incorporating a part of the Preview. + +3.4 You agree that you will not take any actions that may cause or result in the fragmentation of Android, including but not limited to distributing, participating in the creation of, or promoting in any way a software development kit derived from the Preview. + +3.5 Use, reproduction and distribution of components of the Preview licensed under an open source software license are governed solely by the terms of that open source software license and not the License Agreement. You agree to remain a licensee in good standing in regard to such open source software licenses under all the rights granted and to refrain from any actions that may terminate, suspend, or breach such rights. + +3.6 You agree that the form and nature of the Preview that Google provides may change without prior notice to you and that future versions of the Preview may be incompatible with applications developed on previous versions of the Preview. You agree that Google may stop (permanently or temporarily) providing the Preview (or any features within the Preview) to you or to users generally at Google's sole discretion, without prior notice to you. + +3.7 Nothing in the License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features. + +3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the Preview. + +4. Use of the Preview by You + +4.1 Google agrees that nothing in the License Agreement gives Google any right, title or interest from you (or your licensors) under the License Agreement in or to any software applications that you develop using the Preview, including any intellectual property rights that subsist in those applications. + +4.2 You agree to use the Preview and write applications only for purposes that are permitted by (a) the License Agreement, and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries). + +4.3 You agree that if you use the Preview to develop applications, you will protect the privacy and legal rights of users. If users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If users provide you with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, each user has given you permission to do so. + +4.4 You agree that you will not engage in any activity with the Preview, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of Google or any third party. + +4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so. + +4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under the License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach. + +4.7 The Preview is in development, and your testing and feedback are an important part of the development process. By using the Preview, you acknowledge that implementation of some features are still under development and that you should not rely on the Preview having the full functionality of a stable release. You agree not to publicly distribute or ship any application using this Preview as this Preview will no longer be supported after the official Android SDK is released. + +5. Your Developer Credentials + +5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials. + +6. Privacy and Information + +6.1 In order to continually innovate and improve the Preview, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the Preview are being used and how they are being used. Before any of this information is collected, the Preview will notify you and seek your consent. If you withhold consent, the information will not be collected. + +6.2 The data collected is examined in the aggregate to improve the Preview and is maintained in accordance with Google's Privacy Policy located at http://www.google.com/policies/privacy/. + +7. Third Party Applications + +7.1 If you use the Preview to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources. + +7.2 You should be aware the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners. + +7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party. + +8. Using Google APIs + +8.1 Google APIs + +8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service. + +8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. + +9. Terminating the License Agreement + +9.1 the License Agreement will continue to apply until terminated by either you or Google as set out below. + +9.2 If you want to terminate the License Agreement, you may do so by ceasing your use of the Preview and any relevant developer credentials. + +9.3 Google may at any time, terminate the License Agreement, with or without cause, upon notice to you. + +9.4 The License Agreement will automatically terminate without notice or other action upon the earlier of: +(A) when Google ceases to provide the Preview or certain parts of the Preview to users in the country in which you are resident or from which you use the service; and +(B) Google issues a final release version of the Android SDK. + +9.5 When the License Agreement is terminated, the license granted to you in the License Agreement will terminate, you will immediately cease all use of the Preview, and the provisions of paragraphs 10, 11, 12 and 14 shall survive indefinitely. + +10. DISCLAIMERS + +10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE PREVIEW IS AT YOUR SOLE RISK AND THAT THE PREVIEW IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND FROM GOOGLE. + +10.2 YOUR USE OF THE PREVIEW AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE PREVIEW IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE. WITHOUT LIMITING THE FOREGOING, YOU UNDERSTAND THAT THE PREVIEW IS NOT A STABLE RELEASE AND MAY CONTAIN ERRORS, DEFECTS AND SECURITY VULNERABILITIES THAT CAN RESULT IN SIGNIFICANT DAMAGE, INCLUDING THE COMPLETE, IRRECOVERABLE LOSS OF USE OF YOUR COMPUTER SYSTEM OR OTHER DEVICE. + +10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. + +11. LIMITATION OF LIABILITY + +11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING. + +12. Indemnification + +12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys’ fees) arising out of or accruing from (a) your use of the Preview, (b) any application you develop on the Preview that infringes any Intellectual Property Rights of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you of the License Agreement. + +13. Changes to the License Agreement + +13.1 Google may make changes to the License Agreement as it distributes new versions of the Preview. When these changes are made, Google will make a new version of the License Agreement available on the website where the Preview is made available. + +14. General Legal Terms + +14.1 the License Agreement constitutes the whole legal agreement between you and Google and governs your use of the Preview (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the Preview. + +14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in the License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google's rights and that those rights or remedies will still be available to Google. + +14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the License Agreement is invalid, then that provision will be removed from the License Agreement without affecting the rest of the License Agreement. The remaining provisions of the License Agreement will continue to be valid and enforceable. + +14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party beneficiaries to the License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of the License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party beneficiaries to the License Agreement. + +14.5 EXPORT RESTRICTIONS. THE PREVIEW IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE PREVIEW. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE. + +14.6 The License Agreement may not be assigned or transferred by you without the prior written approval of Google, and any attempted assignment without such approval will be void. You shall not delegate your responsibilities or obligations under the License Agreement without the prior written approval of Google. + +14.7 The License Agreement, and your relationship with Google under the License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from the License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction. + + +
\ No newline at end of file diff --git a/docs/html/preview/overview.jd b/docs/html/preview/overview.jd new file mode 100644 index 0000000000000..fb2e266fb0f7d --- /dev/null +++ b/docs/html/preview/overview.jd @@ -0,0 +1,389 @@ +page.title=Program Overview +page.metaDescription=Welcome to the Android M Developer Preview, a program that gives you everything you need to test and optimize your apps for the next version of Android. +page.image=images/cards/card-preview_16-9_2x.png +page.tags="preview", "developer", "android" + +@jd:body + +
+

+ Developer Preview 3 is now available +

+

Includes final SDK and near-final system images

+ +
+ +

+ Welcome to the Android M Developer Preview, a program that gives you + everything you need to test and optimize your apps for the next version of + Android. It's free, and you can get started right away just by downloading + the M Developer Preview tools. +

+ +
+
+
+
+
+ Hardware and emulator system images +
+ +

+ Run and test your apps on Nexus 5, 6, 9, and Player (for TV), as well + as emulator. +

+
+ +
+
+ Latest platform code +
+ +

+ We’ll provide multiple updates during the Preview, so you’ll be testing + against the latest platform changes. +

+
+ +
+
+ Updates delivered by OTA +
+ +

+ You can get updates over-the-air, once you’ve flashed a + device to the initial preview. +

+
+
+ +
+ + +
+
+ New behaviors and capabilities +
+ +

+ Start work early to support new platform behaviors such as + the new runtime permissions model and power-saving features. +

+
+ +
+
+ Priority window for developer-reported issues +
+ +

+ During the first several weeks we’ll give priority to developer-reported + issues, so test and give feedback as soon as possible. +

+
+ +
+
+ Feedback and support +
+ +

+ Report issues and give us feedback using our issue tracker. + Connect with other developers in the M Developer Community. + +

+
+
+
+
+ + + + +

+ Timeline and updates +

++"Preview +

+ The M Developer Preview runs from May 28 until the final Android M public release planned for Q3 + 2015. +

+ +

+ At key development milestones, we’ll deliver updates for your test devices. + The milestones are +

+ + + +

+ These updates culminate in the official Android 6.0 SDK (now available), + which lets you build with the final APIs for the new version of Android, as well as + near-final system images to let you test system behaviors and features. +

+ +

+ As you test and develop on Android M, we strongly recommend keeping + your development environment up-to-date as Preview updates are released. + To make the process easier, we'll deliver updates over-the-air + (OTA) to devices already flashed to a Preview build, as well as + providing system images that you can download and flash manually. +

+

+ Note: Developer Preview 3 includes final APIs and near-final + system images available by both download and OTA. At the full public release of + Android M later in Q3, final system images will be available by download only, + so you'll need to flash manually to + your test devices. +

+ +

+ We’ll notify you when Preview updates are available via the Android Developers Blog, as + well as this site and the + Android M Developer Community. +

+ +

+ What’s in the Preview? +

+ +

+ The M Developer Preview includes everything you need to test your existing + apps on a variety of screen sizes, network technologies, CPU/GPU chipsets, + and hardware architectures. +

+ +

+ SDK tools +

+ +

+ You can download these components through the SDK Manager in Android Studio: +

+ +
    +
  • Official Android 6.0 SDK and tools +
    • + +
  • M Developer Preview emulator system image (32-bit & + 64-bit) +
    • + +
  • M Developer Preview emulator system Image for Android TV + (32-bit) +
    • +
+ +

+ Hardware system images +

+ +

+ You can download these hardware system images for Nexus devices from the + Downloads page: +

+ +
    +
  • + Nexus 5 (GSM/LTE) “hammerhead” device system image +
    • + +
  • + Nexus 6 “shamu” device system image +
    • + +
  • + Nexus 9 (Wi-Fi) “volantis” device system image +
    • + +
  • + Nexus Player (Android TV) “fugu” device system image +
    • +
+ +

+ Documentation and sample code +

+ +

+ These documentation resources help you learn about the Preview: +

+ + + +

+ Support resources +

+ +

+ Use these support resources as you test and develop on the M + Developer Preview: +

+ +
    +
  • M + Developer Preview Issue Tracker is your primary feedback + channel. You can report bugs, performance issues, and general + feedback through the issue tracker. You can also check for known issues + and find workaround steps. +
    • + +
  • The Android M Developer + Community is a Google+ community where you can connect with + other developers working with Android M. You can share + observations or ideas or find answers to questions about Android M. +
    • +
+ + +

+ Final SDK, targeting, and publishing +

+ +

+

With Developer Preview 3, the platform APIs are now official (API level 23) and the + official Android 6.0 SDK is now available. We recommend updating your environment + right away through Android Studio. Once you've updated your environment, you can target + the new API level, compile against the new platform, and publish at your convenience + to Google Play (including alpha, beta, or release channels). + +

If you want to opt out + of compatibility behaviors (which is strongly recommended), + you can target the Android 6.0 platform by setting your app's targetSdkVersion + to “23”. +

+ +

Before releasing an app that targets API level 23, we strongly + recommend distributing it to a group of testers through the new + beta testing features available in the Google Play Developer Console. See the + Help + Center article for more information. +

+ +

+ How to get started +

+ +

+ To get started testing your app with Android M: +

+ +
    +
  1. Review the API Overview + and Behavior Changes to get an + idea of what's new and how it affects your apps. In particular, learn about + the new runtime + permissions model, power-saving features, and auto backup. +
    2. + +
  2. Set up your environment by following the instructions for + Setting up the Preview SDK + and configuring test devices. +
    3. + +
  3. Follow the + flashing instructions to flash the latest M developer preview system image + for Nexus 5, 6, 9, and Player. Once you've flashed your development device, + Preview updates will be delivered through over-the-air (OTA) updates. +
    4. + +
  4. Review the API + Reference and M Preview + samples to gain more insight into new API features and how to use them in + your app. +
    5. + +
  5. Join the Android M + Developer Community to get the latest news and connect with other + developers working with the new platform. +
    6. +
+ +

+ Thank you for your participation in the Android M Developer Preview program! +

diff --git a/docs/html/preview/preview_toc.cs b/docs/html/preview/preview_toc.cs new file mode 100644 index 0000000000000..a6101cd896d06 --- /dev/null +++ b/docs/html/preview/preview_toc.cs @@ -0,0 +1,126 @@ + diff --git a/docs/html/preview/samples.jd b/docs/html/preview/samples.jd new file mode 100644 index 0000000000000..7d47e0ed0e04b --- /dev/null +++ b/docs/html/preview/samples.jd @@ -0,0 +1,70 @@ +page.title=Samples +page.image=images/cards/samples-new_2x.png +@jd:body + +

+ The following code samples are provided for the M Developer Preview. To download + the samples in Android Studio, select the File > Import Samples menu option. +

+ +

+ Note: These downloadable projects are designed + for use with Gradle and Android Studio. +

+ + +

Runtime Permissions

+ +

+ Android M changes the way system permissions work. Users are asked to approve permission + requests at runtime instead of during installation. This sample shows how to request these + permissions. +

+ +

Get it on GitHub

+ +

Confirm Credential

+ +

+ This sample demonstrates how to use device credentials as an authentication method in your app. +

+ +

Get it on +GitHub

+ +

Fingerprint Dialog

+ +

+ This sample demonstrates how to recognize registered fingerprints to authenticate the user + in your app. +

+ +

Get it on GitHub

+ +

Auto Backup for Apps

+ +

+ Android M introduces automatic backup for app settings. This sample demonstrates how to add + filtering rules to an app in order to manage settings backup. +

+ +

Get it on GitHub

+ +

Camera 2 Raw

+ +

+ Demonstrates how to use the Camera2 API to capture RAW camera buffers and save + them as DNG files. +

+ +

Get it on GitHub

+ +

Active Notification

+ +

+ This sample demonstrates how the + NotificationManager + can tell you how many notifications your app is currently showing. +

+ +

Get it on GitHub

diff --git a/docs/html/preview/setup-sdk.jd b/docs/html/preview/setup-sdk.jd new file mode 100644 index 0000000000000..7a2a6660c013e --- /dev/null +++ b/docs/html/preview/setup-sdk.jd @@ -0,0 +1,178 @@ +page.title=Set Up the SDK +page.image=images/cards/card-set-up_16-9_2x.png + +@jd:body + + + + +

With Developer Preview 3, the official Android 6.0 SDK is now available from the Android SDK +Manager. This document assumes that you are familiar with Android app development, such +as using the Android SDK Manager and creating projects. If you are new to +Android, see Building Your First +App training lesson first.

+ + +

Get Android Studio 1.3

+ +

+ It is highly recommended that you install the Android Studio 1.3 to work best with + the Android 6.0 SDK. Please update your Android Studio installation to version 1.3 or + higher, or follow the instructions for + Installing Android Studio. +

+ + +

Get the Android 6.0 SDK

+ +

To add the Android 6.0 SDK components to your development environment:

+ +
    +
  1. Launch Android Studio 1.3 or higher. +
    2. + +
  2. Open the Settings window (on Windows, you can do this + by choosing File > Settings). Choose the + Appearance & Behavior > System + Settings > Updates panel. + +

    On Mac OS X, you can find the Appearance & + Behavior panel + in Android Studio's Preferences window.

    +
    3. + +
  3. On the Updates panel, choose the option for + Automatically check updates for Android SDK: Preview Channel. +
    4. + +
  4. Launch the Android SDK Manager. (With Android Studio 1.3, + the SDK Manager is integrated into Android Studio instead of being a + standalone application.) +
    5. + +
  5. Under the Platforms section, select Android 6.0. +
    6. + +
  6. In the Tools section, select the latest Android + SDK Tools, Platform-tools, and + Build-tools. +
    7. + +
  7. Click Install packages and accept the licensing + agreement for all of the packages. +
    8. + +
  8. Verify that the Android 6.0 SDK is installed by opening the + Settings window and choosing the Appearance & Behavior + > System Settings > Android SDK panel.
    9. + +
  9. On the Android SDK panel, choose + the SDK Platforms tab. Android 6.0 should be listed as Installed. Also, open the + SDK Tools tab to verify that the latest tools are + installed. +
    10. +
+

After completing these steps, the preview components are available in your development + environment.

+ + +

Create or Update a Project

+ +

+ In order to use the preview APIs, you must create or update a development project to use + the preview components. +

+ + +

Create a new project

+ +

+ We recommend using Android Studio to create a project with the preview. Follow the steps + described in Creating a Project + until you arrive at the Form Factors screen in the project wizard. Then perform + the following steps to create a project configured for the preview. +

+ +
    +
  • Check Phone and Tablet.
    • +
  • Select API 23: Android 6.0 (Marshmallow) in Minimum + SDK.
    • +
+ + +

Update an existing project

+ +

+ For existing projects, if you are using Android 6.0 APIs (API level 23) you must + modify the project configuration. In your development environment, open the + build.gradle file for your module and + set these values as follows: +

+ +
    +
  • compileSdkVersion is set to '23'
    • +
  • targetSdkVersion is set to '23'
    • +
+ + +

Set Up for Testing

+ +

+ Testing an app with the preview requires that you have a device or virtual device configured with + the preview version of the platform. If you have a compatible device, you can install the preview + platform for testing. Otherwise, you can configure a virtual device for testing. +

+ +

Set up a physical device

+ +

+ If you have a Nexus 5, Nexus 6, Nexus 9, or Android TV, you can install a preview + system image on these devices for testing your app. + You can set up a virtual device with the preview version of the platform from within Android Studio + using the Android Virtual Device Manager tool. +

+ +

+ Important: Installing a preview image on a device removes all data from + it, so you should backup any data before installing a preview image. +

+ +

Set up a virtual device

+ +

+ You can set up virtual device with the preview version of the platform from within Android Studio + using the Android Virtual Device Manager tool. +

+ +

To create an AVD with the AVD Manager:

+ +
    +
  1. Install the Preview SDK in your development environment, as described + in Setting Up the Preview + SDK.
    2. +
  2. Follow the steps in + Managing AVDs with AVD + Manager. Use the following settings: +
      +
    • Device: Nexus 5, Nexus 6, Nexus 9, or Android TV
      • +
    • Target: + Android M (Preview) - API Level M
      • +
    • ABI: x86
      • +
    +
    3. +
+ +

+ For more information about creating virtual devices for testing, see Managing Virtual Devices. +

diff --git a/docs/html/preview/support.jd b/docs/html/preview/support.jd new file mode 100644 index 0000000000000..cfd94671604fd --- /dev/null +++ b/docs/html/preview/support.jd @@ -0,0 +1,533 @@ +page.title=Support and Release Notes +page.tags="preview", "developer preview" +page.image=images/cards/card-support_16-9_2x.png + +@jd:body + +
+

+ Developer Preview 3 is now available +

+

Includes final SDK and near-final system images

+ +
+ +

+ Two primary support channels are available to you when developing and testing + with the Android M Developer Preview. If you've encountered bugs or have + feedback about the M Developer Preview, you can create an issue on + our issue tracker. We'll triage the issue for further review and provide + updates as needed. +

+ +

+ To discuss issues or ideas with other developers working with Android M, join + the M Developer Preview Google+ + community. +

+ +

+ Developer Preview 3 +

+ +
+
+
+

+ Date: August 2015
+ Build: MPA44I
+ Hardware support: Nexus 5, 6, 9, Player
+ Emulator support: x86 & ARM 32/64-bit
+ Google Play services: 7.8 +

+
+
+
+ +

+ Developer Preview 3 is the final incremental update + to the Android M preview platform that was originally released in May 2015. + The update includes final APIs and the official Android 6.0 SDK, + as well as near-final system images for testing your apps. The + updated system images bring a variety of fixes and enhancements across + the system, including those related to issues reported by developers + through the external issue tracker. +

+ +

+ If you are currently developing or testing on Android M, you should update + your environment as soon as possible, so that + you can begin final compatibility testing in preparation for + the public release to device manufacturers later this year.

+ +

Updating to the Android 6.0 SDK and the latest + system images 3 ensures that you are building against final + platform APIs in API level 23 and testing + against final behaviors. If you are just getting started, + follow the instructions in Set up the Preview SDK. +

+ +

+ What's included +

+ +

+ Developer Preview 3 includes the official Android 6.0 + SDK as well as updated preview system images, documentation, + and samples for developing against the Android 6.0 + development platform. +

+ +
    +
  • + SDK platform and system images (Nexus and + emulator) for building and testing. You can download the Android 6.0 SDK and tools from + the SDK Manager, and the system images are available by over-the-air (OTA) + update or download (see below). +
    • + +
  • + Updated documentation. The Behavior Changes, API Overview, and Permissions documents have + been updated to reflect the latest changes in the platform. An updated + Developer Documentation download + package is available, including full reference docs and API diff + reports. Reference documentation is also now available online. +
    • + +
  • + Translations of the documentation are available. Use + the language selector at the bottom right corner of any page to switch + languages. Note that some of the translated docs are not yet updated for + Developer Preview 3. +
    • + +
  • The Android M code samples are also + updated to account for API and behavior changes: +
      +
    • + RuntimePermissions + and RuntimePermissionsBasic + are updated to reflect latest permissions API changes, including + shouldShowRequestPermissionRationale(). +
      • +
    • + Other samples are updated to support runtime permissions. +
      • +
    +
    • +
+ +

+ Key changes +

+
    +
  • General +
      +
    • Updated the Fingerprint API to enables better error reporting, + better fingerprint enrollment experience, and enumeration support for greater + reliability.
      • +
    • Modified app access to BLE and Wi-Fi scans to require the location permisssion when they + target Android 6.0 (API level 23) or higher. Apps targeting API 22 or earlier can + still perform BTLE and WiFi scans, but only when they are in the foreground. While in the background, those apps will get no results from BTLE and WiFi scans.
      • +
    +
    • +
  • Permission changes +
      +
    • Updated the user interface for permissions and enhanced some of the permissions + behaviors.
      • +
    • The {@link android.Manifest.permission#GET_ACCOUNTS} permission is now a member of the + {@link android.Manifest.permission_group#CONTACTS} permission group and it has a + {@code android:protectionLevel} of {@code dangerous}. This change means that when + targeting Android 6.0 (API level 23), you must check for and request this permission if + your app requires it. +
      • + +
    • The {@code android.permission.READ_PROFILE} and {@code android.permission.WRITE_PROFILE} + permissions have been removed from the {@link android.Manifest.permission_group#CONTACTS} + permission group. +
      • +
    +
    • +
+ +

+ For a complete list of changes, including renamed and removed APIs, see the API Diff report for + API level 22 to 23. +

+ +

+ Known issues +

+ +
    +
  • General issues: +
      +
    • On LTE devices, including Nexus 9, GPS is not functioning properly, which may + interfere with navigation services. +
      • +
    • During Hangouts calls, users may experience distorted or low audio on some devices. +
      • +
    • The Google Apps Device Policy app bundled with MPA44G is unable to set up an Android for +Work Profile, so you cannot create a new Work Profile with that version of the app. This issue is +resolved in the Google Apps Device Policy app bundled with MPA44I. Other apps that provide Android +for Work functionality remain unaffected on either build. +
      • +
    +
    • +
+ +

+ For a complete list of reported issues, please refer to the open issues list on the + Developer Preview issue tracker. +

+ +

+ Get Developer Preview 3 +

+ +

+ You can download the official Android 6.0 SDK platform and + Developer Preview 3 emulator images from the SDK Manager. +

+ +

+ Developer Preview 3 system images for supported Nexus devices are available + by download and by over-the-air (OTA) update. The OTA update is available + only to supported devices that are currently running a Developer Preview build. + If your device is running a Developer Preview build, you should automatically receive + the OTA update within a few days of availability. +

+ +

+ For instructions on how to download and flash your device to the latest Developer + Preview, see the links and instructions on the Downloads page. +

+ +

+ For instructions on how to start developing and testing with Android 6.0 + Marshmallow, read Setting + up the SDK. +

+ +

+ Developer Preview 2 +

+ +
+
+
+

+ Date: July 2015
+ Builds: MPZ79M (Nexus 5, 6, 9), MPZ79N (Nexus Player)
+ Hardware support: Nexus 5, 6, 9, Player
+ Emulator support: x86 & ARM 32/64-bit
+ Google Play services: 7.6 +

+
+
+
+ +

+ Android M Developer Preview 2 is an incremental update to + the Android M preview platform that was originally released in May 2015. The + update includes a variety of enhancements and bug fixes made across the + system, including those related to issues reported by developers through the + external issue tracker. +

+ +

+ If you are currently developing or testing on Android M, you should + update your environment to Developer Preview 2 as soon as + possible. This ensures that you are building with the latest platform APIs + and testing against the latest behaviors. If you are just getting started + with the Android M Developer Preview SDK, follow the instructions in Set up the Preview SDK, then update your + environment for Developer Preview 2. +

+ +

+ What's included +

+ +

+ Developer Preview 2 includes an updated SDK with system images, + documentation, and samples for developing against the latest Android M + platform. +

+ +
    +
  • + SDK platform and system images (Nexus and + emulator) for building and testing. You can download the updated tools from + the SDK Manager, and the system images are available by over-the-air (OTA) + update or download (see below). +
    • + +
  • + Updated documentation. The Behavior Changes, API Overview, and Permissions documents have + been updated to reflect the latest changes in the platform. An updated + Developer Documentation download + package is available, including full reference docs and API diff + reports. +
    • + +
  • + Translations of the documentation are now available. Use + the language selector at the bottom right corner of any page to switch + languages. Note that some of the translated docs are not yet updated for + Developer Preview 2 (coming soon). +
    • + +
  • The Android M code samples are also + updated to account for API and behavior changes: +
      +
    • + RuntimePermissions + / RuntimePermissionsBasic + are updated to reflect latest permissions API changes, including + shouldShowRequestPermissionRationale(). +
      • +
    • + FingerprintDialog + adds a flow to ask for passwords when new fingerprints are added as + well as a preference if the app will use fingerprints as a method of + authentication. +
      • +
    +
    • +
+ +

+ Key changes +

+ +
    +
  • Permissions changes +
      +
    • The android.permission.USE_FINGERPRINT permission now + has "normal" protection level, so it is no longer necessary to request + this permission directly from the user. The USE_FINGERPRINT + permission enables fingerprints to be enabled for authentication, but + does not give the requesting app access to the enrollment/fingerprint + administration flow. +
      • + +
    • The android.permission.WRITE_EXTERNAL_STORAGE permission + has protection level "dangerous", meaning that apps wanting to write to + external storage will need to request permission from the user at + runtime. Both READ_EXTERNAL_STORAGE and + WRITE_EXTERNAL_STORAGE are members of the + STORAGE permission group. +
      • + +
    • Remote Bluetooth/Wi-Fi MAC's now require either the + android.permission.ACCESS_COARSE_LOCATION or + android.permission.ACCESS_FINE_LOCATION permission. +
      • + +
    • Some accounts and identity permissions are moved to + CONTACTS permissions group and others are removed or granted + based on account type. In particular, + android.permission.USE_CREDENTIALS, + android.permission.MANAGE_ACCOUNTS, and + android.permission.AUTHENTICATE_ACCOUNTS are ungrouped + pending further changes in a later release. +
      • + +
    • The Wi-Fi permissions + android.permission.CHANGE_WIFI_STATE, + android.permission.CHANGE_WIMAX_STATE, and + android.permission.CHANGE_WIFI_MULTICAST_STATE now have + protection level "normal". +
      • + +
    • The Bluetooth permissions android.permission.BLUETOOTH + and android.permission.BLUETOOTH_ADMIN now have protection + level "normal". +
      • + +
    • Bookmarks and subscribed feeds permissions are removed. +
      • + +
    • Apps included in the system image are no longer granted dangerous + permissions automatically. All apps should check for and request + permissions at runtime. +
      • + +
    • Introduces the utility method + Activity.shouldShowRequestPermissionRationale(String), which + lets your app see whether users have previously rejected a permission + request. This lets you know that your app should explain the the user why + it needs that permission. For more information see the Permissions + developer guide. +
      • +
    +
    • + +
  • Other changes +
      +
    • The android.app.AssistContent and + android.app.AssistStructure classes are moved into a new + package, android.app.assist. +
      • + +
    • Bluetooth Stylus APIs are updated and include new callback events. + The View.OnStylusButtonPressListener class is renamed to + View.OnContextClickListener and + GestureDetector.OnStylusButtonPressListener class to + GestureDetector.OnContextClickListener. +
      • +
    +
    • +
+ +

+ For a complete list of changes, including renamed and removed APIs, please + refer to the API Diff Reports included in the Developer Documentation download package. +

+ +

+ Known issues +

+ +
    +
  • General issues: +
      +
    • The system Messenger app crashes on the 64-bit emulator.
      • +
    • After updating to Developer Preview 2, Contacts sync experiences + intermittent issues. The workaround is to clear and re-sync Contact Storage + data after update. To clear data, go to Settings > Apps > Show + system > Contacts Storage. Select "Storage" and then + Clear data.
      • +
    • In YouTube app, it's not possible to share a video. The share window is + blank.
      • +
    • The bundled Google Apps Device Policy app included in Developer Preview 2 is unable to + properly set up an Android for Work Profile, so you cannot create a new Work Profile with this + app after you update. This issue is specific to the Google Apps Device Policy app, and not the + Android for Work platform (or our partner EMM providers). As a workaround for users of the + Google Apps Device Policy app, be sure to create a Work Profile in Developer Preview 1 before + updating to Developer Preview 2. +
      • +
    +
    • +
  • Issues specific to MPZ79N on Nexus Player: +
      +
    • Bluetooth share crashes after clearing data. Please do not + clear app data for system services, otherwise you will need to Factory + Reset your device
      • +
    • Remote control can experience intermittent connectivity issues.
      • +
    • Movies show black screen with some ANRs on exiting the video.
      • +
    • In YouTube app, lower-resolution videos have a green bar at the top + and some color-ghosting
      • + +
    +
    • +
+ +

+ For a complete list of reported issues, please refer to the open issues list on the + Developer Preview issue tracker. +

+ +

+ Get Developer Preview 2 +

+ +

+ You can download the Developer Preview 2 platform and emulator images from + the SDK Manager. +

+ +

+ Developer Preview 2 system images for supported Nexus devices are available + by download and by over-the-air (OTA) update. The OTA update is available + only to supported devices that are currently running Developer Preview 1. If + your devices are running Developer Preview 1, you should automatically receive + the OTA update within a few days of availability. +

+ +

+ If you are just getting started with Android M Developer Preview, and want + to receive Developer Preview 2 via OTA, download the appropriate + Developer Preview 1 + system image, and flash it to your device. Then, + leave the device powered on for several hours. It registers with the + OTA service, and receives Developer Preview 2 by OTA. +

+ +

+ For instructions on how to download and flash your device to the Developer + Preview, see the links and instructions on the Downloads page. +

+ +

+ For instructions on how to start developing and testing with Android M, read + Setting up the SDK. +

+ +

+ Developer Preview 1 +

+ +
+
+
+

+ Date: May 2015
+ Build: MPZ44Q
+ Hardware support: Nexus 5, 6, 9, Player
+ Emulator support: x86 & ARM (32/64-bit)
+ Google Play services: 7.5 +

+
+
+
+ +

+ Initial release. +

+ +