When an activity is moved to a stack using the
ActivityStack#moveActivityToStack API a new task is created to
hold the activity in the stack. However, when the new task is
created in the window manager side it uses the stack id of the
previous stack the activity was in. We now pass the stack to use
from activity manager to window manager.
Bug: 25987309
Bug: 25961636
Change-Id: Iecc71f6d9b3e70a8d88e134b42f7532ba5327bad
By adding a file named NO_DOCS to a directory, all
java files under that directory will be ignored for
javadoc builds. This is especially useful for marking
test projects as not participating in the javadoc
build.
Change-Id: I3b0259f4bb3c8460c3560fdcf97c6cac11d8001d
This allows us to tell lock checks from FBE checks separately,
and will be useful when dealing with password unification.
Change-Id: Ifbea425f749fee4d6d51faddd8b64bf717a1a5f8
When the Work Challenge is in place, re-route the
enforcing of Admin policies on the password to the
work profile. The Admin should not be allowed to
dictate policies on the device lock in this case.
This is part of the Separate Work Challenge feature.
Change-Id: I757973e540797b5fb10bea7a2fd1925561655bc9
Add a TYPE_QS_DIALOG window type, that is in the same layer as
apps and dialogs and such. It is guarded by having a token
that is granted by SysUI after a click has occured. If the
app shows a dialog before listening finishes (QS closes) then
the token will stay granted until the tile is removed by the
user, otherwise the token will be removed immediately to avoid
later dialogs.
Also fix a couple tiny TileService issues:
- Stop/Start listening reversed
- Fix javadoc referencing wrong action
Change-Id: Iedcdd5fd9a2af2b33eb7f6f17bb0e6c997879876
The work challenge should be locked whenever the device goes to sleep + admin
timeout or when the power button is pressed if the lock setting is on.
This change creates the infrastructure to lock a specific user instead of the
device and uses it in these cases. Then, the current code that brings up the
work challenge can check to only show it if the user is locked.
Change-Id: I89b4342b1458d97734d7afa66be52bf04ec3a3d4
- Moving the focused state back into the stack, since the task view
is transient and can be rebound. Also ensuring that we update the
task view focus state as we return and pick up views from the view
pool
- Fixing issue where going back from recents would not go back home
- Properly calculating the task visibility (regression)
Bug: 25975225
Change-Id: Ica861f0d8996e4e254e875199a2d704a65bf8e58
- Updating layout for freeform workspaces
- Consolidates the clipping and bitmap scale with the transform to make
the transitions more unified
- Updating clipping as we synchronize scroll instead of afterwards
Change-Id: I33de4e2646c75f0bc0eb75bd6909fe94557196b5
- This allows us to choose which layout to show, either freeform, stack,
or a combination of the two
- Fixing crash with null bitmap
Change-Id: I659e66d89f7205ccb0c2ba22c57aee95c8d4b3ab
Just assign mUri directly instead of calling setUri()
to avoid flipping mIsAppProvidedWebUri to true exactly
when it shouldn't be.
Also, make sure the boolean gets un/parceled.
Bug: 25952056
Change-Id: I973e585d04a73c2b7eab5975ea7f2b447b270c26
Make the meaning of CONTENTS_FILE_DESCRIPTOR more explicit, and
emphasize that describeContents() applies to the current object
instance, not to the class generically.
Change-Id: Ie5010e24c2e57bdc6c982249adb9d4c871d46f5a
Use MAINDEXCLASSES defined by the build system instead of manually using
$(HOST_OUT_EXECUTABLES)/mainDexClasses.
Change-Id: Iede13c243ef0c4e374c8e80bab4a995cea76b9b1
The center position of a drag handle can be outside of the
screen. In such cases, selection handle tests can be failed.
Changed to drag the visible position to deal with it.
Bug: 25730231
Change-Id: Id9270fc03d0f39041f243c9e9d17deca19925e09
