From 4d93a21980f7e82bd346ad9c3a18c0c932d09253 Mon Sep 17 00:00:00 2001 From: Andrew Solovay Date: Fri, 13 May 2016 13:33:55 -0700 Subject: [PATCH] docs: Updates to multi-window and related docs. Clarified behavior when activity is resized or put in fullscreen mode, per b/28580007 . Also (per email from o-o) removed misleading statement about when onStop() might or might not be called. Both changes can go live now (multiwindow update applies to DP1 & 2, and onStop() clarification applies to all versions of API), so I'll submit as soon as this is approved. See first comment for doc stage location. bug: 28580007 Change-Id: Ib008f24e5796ec7810b67c91e512e679680d4afd --- core/java/android/app/Activity.java | 4 ---- docs/html/preview/features/multi-window.jd | 4 +++- 2 files changed, 3 insertions(+), 5 deletions(-) diff --git a/core/java/android/app/Activity.java b/core/java/android/app/Activity.java index a5565638278cc..b772bc9db65f4 100644 --- a/core/java/android/app/Activity.java +++ b/core/java/android/app/Activity.java @@ -1593,10 +1593,6 @@ public class Activity extends ContextThemeWrapper * receive either {@link #onRestart}, {@link #onDestroy}, or nothing, * depending on later user activity. * - *

Note that this method may never be called, in low memory situations - * where the system does not have enough memory to keep your activity's - * process running after its {@link #onPause} method is called. - * *

Derived classes must call through to the super class's * implementation of this method. If they do not, an exception will be * thrown.

diff --git a/docs/html/preview/features/multi-window.jd b/docs/html/preview/features/multi-window.jd index 0773b329bd7fb..fec016861e80b 100644 --- a/docs/html/preview/features/multi-window.jd +++ b/docs/html/preview/features/multi-window.jd @@ -138,7 +138,9 @@ page.keywords="multi-window", "android N", "split screen", "free-form" When the user puts an app into multi-window mode, the system notifies the activity of a configuration change, as specified in Handling Runtime - Changes. Essentially, this change has the same activity-lifecycle + Changes. This also happens when the user resizes the app, or puts the app + back into full-screen mode. + Essentially, this change has the same activity-lifecycle implications as when the system notifies the app that the device has switched from portrait to landscape mode, except that the device dimensions are changed instead of just being swapped. As discussed in