From ecf63e4d546d1946a3aa0cb3c9a50665839623f7 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Wed, 8 Jul 2015 20:10:49 -0700 Subject: Doc change: minor updates to KIs and AFW behavior changes. Change-Id: If1af0f85593db48b241d81dcb6df9d4a5c703105 --- docs/html/preview/behavior-changes.jd | 31 +++++++++++-------- docs/html/preview/support.jd | 57 ++++++++++++++++++----------------- 2 files changed, 47 insertions(+), 41 deletions(-) (limited to 'docs') diff --git a/docs/html/preview/behavior-changes.jd b/docs/html/preview/behavior-changes.jd index cb526fa..6ee0af0 100644 --- a/docs/html/preview/behavior-changes.jd +++ b/docs/html/preview/behavior-changes.jd @@ -386,15 +386,21 @@ default, it is set to {@code true}. (for example, through calls to the {@link android.net.wifi.WifiManager#addNetwork(android.net.wifi.WifiConfiguration) addNetwork()} method) are now removed if that work profile is deleted. -
  • WiFi configuration lockdown: Any WiFi configuration created by an active Device -Owner can no longer be modified or deleted by the user. The user can still create and -modify their own WiFi configurations, so long as the {@link android.os.UserManager} constant -{@link android.os.UserManager#DISALLOW_CONFIG_WIFI} has not been set for that user.
    • + +
  • WiFi configuration lockdown: Any WiFi configuration created by + an active Device Owner can no longer be modified or deleted by the user if + Settings.Global.WIFI_DEVICE_OWNER_CONFIGS_LOCKDOWN is non-zero. + The user can still create and modify their own WiFi configurations. Active Device + Owners have the privilege of editing/removing any WiFi configurations, including + those not created by them. +
    • + +
  • Download Work Policy Controller via Google account addition: When a Google account that requires management via a Work Policy Controller (WPC) app is added to a device outside of a managed context, the add account flow now prompts the user to install the appropriate WPC. This behavior also applies to accounts added via -Settings > Accounts in the initial device setup wizard.
    • +Settings > Accounts and in the initial device setup wizard.
  • Changes to specific DevicePolicyManager API behaviors:
    • -
  • The {@link android.app.admin.DevicePolicyManager#createAndInitializeUser(android.content.ComponentName, java.lang.String, java.lang.String, android.content.ComponentName, android.os.Bundle)} and {@link android.app.admin.DevicePolicyManager#createUser(android.content.ComponentName, java.lang.String) methods createAndInitializeUser have been deprecated.
    • -
  • Android for Work APIs are optimized for M runtime permssions, including Work profiles, assist layer, and others. DevicePolicyManager APIs support runtime permissions without affecting pre-M apps.
    • +
  • The {@link android.app.admin.DevicePolicyManager#createAndInitializeUser(android.content.ComponentName, java.lang.String, java.lang.String, android.content.ComponentName, android.os.Bundle) createAndInitializeUser()} and {@link android.app.admin.DevicePolicyManager#createUser(android.content.ComponentName, java.lang.String) createUser()} methods have been deprecated.
    • +
  • The {@link android.app.admin.DevicePolicyManager#setScreenCaptureDisabled(android.content.ComponentName, boolean) setScreenCaptureDisabled()} method now also blocks the assist structure when an app of the given user is in the foreground.
    • +
  • EXTRA_PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM now defaults to SHA-256. SHA-1 is still supported for backwards compatibility but will be removed in future. EXTRA_PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM now only accepts SHA-256.
    • +
  • Device initializer APIs which existed in the MNC preview are now removed. They will not appear in the final M release.
    • +
  • Android for Work APIs are optimized for M runtime permissions, including Work profiles, assist layer, and others. New DevicePolicyManager permission APIs don't affect pre-M apps.
    • -
  • Changes to global settings — the settings below can no longer be set via setGlobalSettings: +
  • Changes to global settings — the settings below can no longer be set via {@link android.app.admin.DevicePolicyManager#setGlobalSetting(android.content.ComponentName, java.lang.String, java.lang.String) setGlobalSettings()}:
    • - - - - - + diff --git a/docs/html/preview/support.jd b/docs/html/preview/support.jd index 90da200..9c75008 100644 --- a/docs/html/preview/support.jd +++ b/docs/html/preview/support.jd @@ -58,7 +58,7 @@ page.image=images/cards/card-support_16-9_2x.png Build: MPZ79M
    Hardware support: Nexus 5,6,9, Player
    Emulator support: ARM 32/64-bit
    - Google Play services: 7.5 + Google Play services: 7.6

    @@ -129,7 +129,6 @@ page.image=images/cards/card-support_16-9_2x.png are updated to reflect latest permissions API changes, including shouldShowRequestPermissionRationale(). -
  • FingerprintDialog @@ -137,15 +136,6 @@ page.image=images/cards/card-support_16-9_2x.png well as a preference if the app will use fingerprints as a method of authentication.
    • - -
  • The Android Wear samples (AgendaData / - DataLayer / - Quiz / - - XYZTouristAttractions) show a simplified usage of Data Items. -
    • @@ -246,24 +236,35 @@ page.image=images/cards/card-support_16-9_2x.png -- cgit v1.1