Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Late-breaking Behavior Changes addition for N Preview 5

Browse Source 
Noted that several methods behave differently if called on devices
with work profiles with separate work challenges.

See first comment for doc stage location.

Change-Id: I33d93491d9a2b086f8b8e33feb42b9d531e90fde
This commit is contained in:
Andrew Solovay
2016-07-18 10:52:53 -07:00
parent 0544462bf1
commit bec14528ed
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/html/preview/behavior-changes.jd
View File

@@ -765,6 +765,23 @@ JavaVM::AttachCurrentThread from <jni.h>.
is returned, even if the encryption key is specific to the user or profile.
</li>
<li>In Android N, several methods that would ordinarily affect the entire
device behave differently if the device has a work profile installed with a
separate work challenge. Rather than affecting the entire device, these
methods apply only to the work profile. (The complete list of such methods is
in the {@link android.app.admin.DevicePolicyManager#getParentProfileInstance
DevicePolicyManager.getParentProfileInstance()} documentation.) For example,
{@link android.app.admin.DevicePolicyManager#lockNow
DevicePolicyManager.lockNow()} locks just the work profile, instead of
locking the entire device. For each of these methods, you can get the old
behavior by calling the method on the parent instance of the
{@link android.app.admin.DevicePolicyManager}; you can get this parent by
calling {@link android.app.admin.DevicePolicyManager#getParentProfileInstance
DevicePolicyManager.getParentProfileInstance()}. So for example, if you call
the parent instance's {@link android.app.admin.DevicePolicyManager#lockNow}
method, the entire device is locked.
</li>
</ul>
<p>