2eb84b28779b35da8e410564db33a8aab1f3fbcb - platform_frameworks_base

commit	2eb84b28779b35da8e410564db33a8aab1f3fbcb	[log] [tgz]
author	Andrii Kulian <akulian@google.com>	Thu Dec 13 18:18:54 2018 -0800
committer	Andrii Kulian <akulian@google.com>	Tue Dec 18 15:07:04 2018 -0800
tree	9a02c1fcbae1ea3cfe38dde1a901b5e6726f30ee
parent	009bd1bfe357418d993a93f3b28adb56d8ea01e5 [diff]

Add API to check if activity can be started on a display

Some activity launch restrictions apply to virtual displays, which
are not communicated to apps. Currently there is no way to check
this in advance before starting an activity. This means that an app
get an unexpected SecurityException after calling startActivity and
therefore cannot know when to show in their UI a possible option to
launch on a secondary display.

This CL gives adds a public API to check the possibility of launch
on a specific display.

Test: ActivityManagerMultiDisplayTests
Bug: 119575501
Change-Id: Ieb70f0bb79b1a88b7284a19af2efeeb1fcb90f75

api/current.txt[diff]
core/java/android/app/ActivityManager.java[diff]
core/java/android/app/IActivityTaskManager.aidl[diff]
services/core/java/com/android/server/wm/ActivityStartController.java[diff]
services/core/java/com/android/server/wm/ActivityTaskManagerService.java[diff]

5 files changed

tree: 9a02c1fcbae1ea3cfe38dde1a901b5e6726f30ee