Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit bec14528 authored by Andrew Solovay's avatar Andrew Solovay
Browse files

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

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
parent 0544462b

docs/html/preview/behavior-changes.jd

+17 −0
Original line number Diff line number Diff line
@@ -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>