See Also
-
+
- Adding + Picture-in-Picture
- Multi-Window Playground sample app @@ -28,7 +30,7 @@ page.keywords="multi-window", "android N", "split screen", "free-form"
- Handheld devices running Android N offer split-screen +
- Handheld devices running Android 7.0 offer split-screen mode. In this mode, the system fills the screen with two apps, showing them either side-by-side or one-above-the-other. The user can drag the dividing line separating the two to make one app larger and the other smaller. -
- On Nexus Player running Android N, apps can put themselves +
- On TV devices, apps can put themselves in picture-in-picture mode, allowing them to continue showing content while the user browses or interacts with other apps. @@ -72,9 +74,9 @@ page.keywords="multi-window", "android N", "split screen", "free-form"
-
-
Activity.isInMultiWindowMode()+ {@link android.app.Activity#isInMultiWindowMode isInMultiWindowMode()} - @@ -325,12 +329,14 @@ android:supportsPictureInPicture=["true" | "false"]
-
-
Activity.isInPictureInPictureMode()+ {@link android.app.Activity#isInPictureInPictureMode + isInPictureInPictureMode()} -
- Call to find out if the activity is in picture-in-picture mode.
-
+ Call to find out if the activity is in picture-in-picture
+ mode.
Note: Picture-in-picture mode is a special case of multi-window mode. If
myActivity.isInPictureInPictureMode()@@ -340,7 +346,8 @@ android:supportsPictureInPicture=["true" | "false"] -
-
Activity.onMultiWindowModeChanged()+ {@link android.app.Activity#onMultiWindowModeChanged + onMultiWindowModeChanged()} - @@ -351,7 +358,8 @@ android:supportsPictureInPicture=["true" | "false"]
-
-
Activity.onPictureInPictureModeChanged()+ {@link android.app.Activity#onPictureInPictureModeChanged + onPictureInPictureModeChanged()} - @@ -363,17 +371,21 @@ android:supportsPictureInPicture=["true" | "false"]
-
-
android.view.DropPermissions+ {@link android.view.DragAndDropPermissions} - @@ -440,20 +446,20 @@ android:supportsPictureInPicture=["true" | "false"]
-
-
View.startDragAndDrop()+ {@link android.view.View#startDragAndDrop View.startDragAndDrop()} -
- New alias for {@link android.view.View#startDrag View.startDrag()}. To
- enable cross-activity drag and drop, pass the new flag
-
View.DRAG_FLAG_GLOBAL. If you need to give URI permissions to - the recipient activity, pass the new flags -View.DRAG_FLAG_GLOBAL_URI_READor -View.DRAG_FLAG_GLOBAL_URI_WRITE, as appropriate. + Alias for {@link android.view.View#startDrag View.startDrag()}. To enable + cross-activity drag and drop, pass the flag {@link + android.view.View#DRAG_FLAG_GLOBAL}. If you need to give URI permissions to + the recipient activity, pass the flags {@link + android.view.View#DRAG_FLAG_GLOBAL_URI_READ} or {@link + android.view.View#DRAG_FLAG_GLOBAL_URI_WRITE}, as appropriate. -
-
View.cancelDragAndDrop()+ {@link android.view.View#cancelDragAndDrop View.cancelDragAndDrop()} - @@ -462,7 +468,7 @@ android:supportsPictureInPicture=["true" | "false"]
-
-
View.updateDragShadow()+ {@link android.view.View#updateDragShadow View.updateDragShadow()} - @@ -471,7 +477,8 @@ android:supportsPictureInPicture=["true" | "false"]
-
-
Activity.requestDragAndDropPermissions()+ {@link android.app.Activity#requestDragAndDropPermissions + Activity.requestDragAndDropPermissions()} -
@@ -483,29 +490,29 @@ android:supportsPictureInPicture=["true" | "false"]
Testing Your App's Multi-Window Support
- Whether or not you update your app for Android N, you should + Whether or not your app targets API level 24 or higher, you should verify how it behaves in multi-window mode in case a user tries to launch it - in multiwindow mode on a device running Android N. + in multi-window mode on a device running Android 7.0 or higher.
Configuring a Test Device
- If you install Android N on a device, split-screen mode is - automatically supported. + If a device runs Android 7.0 or higher, it automatically supports split-screen + mode.
-If your app was not built with the N Preview SDK
+If your app targets API level 23 or lower
- If you did not build your app with the N Preview SDK and the user attempts to use - the app in multi-window mode, the system forcibly resizes the app unless the app - declares a fixed orientation. + If your app targets API level 23 or lower and the user attempts to use + the app in multi-window mode, the system forcibly resizes the app unless the + app declares a fixed orientation.
If your app does not declare a fixed orientation, you should launch your app - on a device running Android N and attempt to put the app in + on a device running Android 7.0 or higher and attempt to put the app in split-screen mode. Verify that the user experience is acceptable when the app is forcibly resized.
@@ -519,7 +526,7 @@ android:supportsPictureInPicture=["true" | "false"]If you support multi-window mode
- If you built your app with the N Preview SDK and have not disabled + If your app targets API level 24 or higher and does not disable multi-window support, verify the following behavior under both split-screen and freeform modes.
@@ -593,7 +600,7 @@ android:supportsPictureInPicture=["true" | "false"]If you disabled multi-window support by setting
diff --git a/docs/html/training/basics/activity-lifecycle/pausing.jd b/docs/html/training/basics/activity-lifecycle/pausing.jd index 7ca97aa2d2924..64fa60bcb4a03 100644 --- a/docs/html/training/basics/activity-lifecycle/pausing.jd +++ b/docs/html/training/basics/activity-lifecycle/pausing.jd @@ -32,25 +32,34 @@ class="button">Download the demo -android:resizableActivity="false", you should launch your app on - a device running Android N and attempt to put the app in + a device running Android 7.0 or higher and attempt to put the app in freeform and split-screen modes. Verify that when you do so, the app remains in full-screen mode.During normal app use, the foreground activity is sometimes obstructed by other -visual components that cause the activity to pause. For example, when a semi-transparent -activity opens (such as one in the style of a dialog), the previous activity pauses. As long as the -activity is still partially visible but currently not the activity in focus, it remains paused.
++ During normal app use, the app sometimes loses focus, causing the activity to + pause. For example, when apps run in multi-window mode, only one + of the apps has the focus at any time; the system pauses all other apps. Similarly, + when a semi-transparent activity opens (such as one in the style of a + dialog), the previous activity pauses. As long as the activity is still + partially visible but currently not the activity in focus, it remains paused. +
However, once the activity is fully-obstructed and not visible, it stops (which is discussed in the next lesson).
As your activity enters the paused state, the system calls the {@link android.app.Activity#onPause onPause()} method on your {@link android.app.Activity}, which allows -you to stop ongoing actions that should not continue while paused (such as a video) or persist +you to stop ongoing actions that should not continue while paused or persist any information that should be permanently saved in case the user continues to leave your app. If the user returns to your activity from the paused state, the system resumes it and calls the {@link android.app.Activity#onResume onResume()} method.
-Note: When your activity receives a call to {@link -android.app.Activity#onPause()}, it may be an indication that the activity will be paused for a -moment and the user may return focus to your activity. However, it's usually the first indication -that the user is leaving your activity.
++ Note: When the system calls your activity's {@link + android.app.Activity#onPause()} method, the system may be signaling that the + activity will be paused for a moment and the user may return focus to your + activity, or that the app is running in multi-window mode. However, this + method call may also be the first indication that the user is leaving your + activity. +
Figure 1. When a semi-transparent activity obscures @@ -67,7 +76,11 @@ the user is leaving the activity and it will soon enter the Stopped state. You the {@link android.app.Activity#onPause()} callback to:
-
-
- Stop animations or other ongoing actions that could consume CPU. +
- Check if the activity is visible; if it is not, stop animations or other + ongoing actions that could consume CPU. Remember, beginning with Android + 7.0, a paused app might be running in multi-window mode. + In this case, you would not want to stop animations or video playback.
- Commit unsaved changes, but only if users expect such changes to be permanently saved when they leave (such as a draft email).
- Release system resources, such as broadcast receivers, handles to sensors (like
- Android N adds support for displaying more than one app at the + Android 7.0 adds support for displaying more than one app at the same time. On handheld devices, two apps can run side-by-side or one-above-the-other in split-screen mode. On TV devices, apps can use picture-in-picture mode to continue video playback while users @@ -36,7 +38,7 @@ page.keywords="multi-window", "android N", "split screen", "free-form"
- If you build your app with the N Preview SDK, you can configure how your app + If your app targets Android 7.0 (API level 24) or higher, you can configure how your app handles multi-window display. For example, you can specify your activity's minimum allowable dimensions. You can also disable multi-window display for your app, ensuring that the system only shows your app in full-screen @@ -46,20 +48,20 @@ page.keywords="multi-window", "android N", "split screen", "free-form"
Overview
- Android N allows several apps to share the screen at once. For + Android 7.0 allows several apps to share the screen at once. For example, a user could split the screen, viewing a web page on the left side while composing an email on the right side. The user experience depends on the device:
-
-
Figure 1. Two apps running side-by-side in split-screen mode. @@ -100,9 +102,7 @@ page.keywords="multi-window", "android N", "split screen", "free-form"
Users can drag and drop data from one activity to another while the activities are sharing - the screen. (Previously, users could only drag and drop data within a single - activity.) -
+ the screen.Multi-Window Lifecycle
@@ -163,7 +163,7 @@ page.keywords="multi-window", "android N", "split screen", "free-form"Configuring Your App for Multi-Window Mode
- If your app targets Android N, you can configure how and + If your app targets API level 24 or higher, you can configure how and whether your app's activities support multi-window display. You can set attributes in your manifest to control both size and layout. A root activity's attribute settings apply to all activities @@ -173,8 +173,8 @@ page.keywords="multi-window", "android N", "split screen", "free-form"
- Note: If you build a multi-orientation app with a version of the - SDK lower than Android N, and the user uses the app in + Note: If you build a multi-orientation app that targets API + level 23 or lower, and the user uses the app in multi-window mode, the system forcibly resizes the app. The system presents a dialog box warning the user that the app may behave unexpectedly. The system does not resize fixed-orientation apps; if @@ -183,10 +183,13 @@ page.keywords="multi-window", "android N", "split screen", "free-form"
android:resizeableActivity
+
- Set this attribute in your manifest's <activity> or
- <application> node to enable or disable multi-window
- display:
+ Set this attribute in your manifest's <activity>
+ or <application>
+ element to enable or disable multi-window display:
@@ -202,16 +205,19 @@ android:resizeableActivity=["true" | "false"]- If your app targets Android N, but you do not specify a value + If your app targets API level 24, but you do not specify a value for this attribute, the attribute's value defaults to true.
android:supportsPictureInPicture
- Set this attribute in your manifest's
<activity>node to - indicate whether the activity supports picture-in-picture display. This - attribute is ignored ifandroid:resizeableActivityis false. + Set this attribute in your manifest's<activity>+ node to indicate whether the activity supports Picture-in-Picture + display. This attribute is ignored ifandroid:resizeableActivity+ is false.@@ -221,7 +227,7 @@ android:supportsPictureInPicture=["true" | "false"]Layout attributes
- With Android N, the
@@ -283,8 +289,8 @@ android:supportsPictureInPicture=["true" | "false"]<layout>manifest element + With Android 7.0, the<layout>manifest element supports several attributes that affect how an activity behaves in multi-window mode:Running Your App in Multi-Window Mode
- Android N offers new functionality to support apps that can run - in multi-window mode. + Beginning with Android 7.0, the system offers functionality to support apps + that can run in multi-window mode.
Disabled features in multi-window mode
@@ -309,15 +315,13 @@ android:supportsPictureInPicture=["true" | "false"]Multi-window change notification and querying
- The following new methods have been added to the {@link android.app.Activity} - class to support multi-window display. For details on each method, see the - N Preview SDK - Reference. + {@link android.app.Activity} offers the following methods to support + multi-window display.
- There are also {@link android.app.Fragment} versions of each of these
- methods, for example Fragment.isInMultiWindowMode().
+ The {@link android.app.Fragment} class exposes versions of many of these
+ methods, for example {@link android.app.Fragment#onMultiWindowModeChanged
+ Fragment.onMultiWindowModeChanged()}.
Entering picture-in-picture mode
- To put an activity in picture-in-picture mode, call the new method
- Activity.enterPictureInPictureMode(). This method has no effect if
- the device does not support picture-in-picture mode. For more information,
- see the Picture-in-Picture documentation.
+ To put an activity in picture-in-picture mode, call {@link
+ android.app.Activity#enterPictureInPictureMode
+ Activity.enterPictureInPictureMode()}. This method has no effect if the
+ device does not support picture-in-picture mode. For more information, see
+ the Picture-in-Picture
+ documentation.
Launch New Activities in Multi-Window Mode
@@ -381,8 +393,8 @@ android:supportsPictureInPicture=["true" | "false"]
When you launch a new activity, you can hint to the system that the new
activity should be displayed adjacent to the current one, if possible. To do
- this, use the flag
- Intent.FLAG_ACTIVITY_LAUNCH_TO_ADJACENT. Passing
+ this, use the intent flag
+ {@link android.content.Intent#FLAG_ACTIVITY_LAUNCH_ADJACENT}. Passing
this flag requests the following behavior:
If a device is in freeform mode and you are launching a new activity, you can
specify the new activity's dimensions and screen location by calling
- ActivityOptions.setLaunchBounds(). This method has no effect if
+ {@link android.app.ActivityOptions#setLaunchBounds
+ ActivityOptions.setLaunchBounds()}. This method has no effect if
the device is not in multi-window mode.
Users can drag and drop data from one activity to another while the two activities are - sharing the screen. (Previously, users could only drag and drop data within a - single activity.) For this reason, you may want to add drag and drop + sharing the screen. (Prior to Android 7.0, users could only drag and drop data + within a single activity.) For this reason, you may want to add drag and drop functionality to your app if your app does not currently support it.
-
- The N Preview SDK extends the android.view
- package to support cross-app drag and drop. For details on the following
- classes and methods, see the N
- Preview SDK Reference.
-