Also start using libbase style logging. Other log statements will
be converted in a follow up.
Test: make
Bug: 33579623
Change-Id: I34bb2ccab57e5bdd22aa35be8f8dcb68fdc4e097
mTask was a duplicate reference to the WindowContainer's parent. The
main benefit of this refenrece was type, as its callers require an
instance of type Task.
With the introduction of the method getTask, we can shift away from
this variable and instead directly cast the parent here. If the
window hierarchy changes in the future (such as AppWindowToken parent
types not being Task), we can re-evaluate and adjust how task is
returned.
Test: manual
Change-Id: Idd6bba1121056ed79745911efe838edfa685bbf2
We do not start an activity in the case of a lock task mode
violation. However, the activity is still associated with the task
and therefore participates in future interactions, such as
visibility checks.
This changelist addresses this issue by removing the assocation in
the case of failures.
Change-Id: Ibf7edd2bd4532de5e7f355311a808ffd21e542e3
Fixes: 35034729
Fixes: 35035258
Fixes: 34179495
Test: cts-tradefed run cts-dev --module DevicePolicyManager --test com.android.cts.devicepolicy.DeviceOwnerTest#testLockTask_deviceOwnerUser
- This was a regression in the original change to move the tasks to the
fullscreen stack when the pinned stack was removed. The task kept its
old bounds, which causes the next animation into the PiP to not run
since the stack bounds are taken from task bounds (which are the old
pinned stack bounds)
Bug: 35326108
Test: run-test CtsServicesHostTestCases
Change-Id: I234910107cf62cc23b2d663161d250b9d59b3934
Per Java documentation "Iterator.remove is the only safe way to
modify a collection during iteration; the behavior is unspecified
if the underlying collection is modified in any other way while
the iteration is in progress."
Test: updated gmscore to check that onPackageRemoved() works correctly
Bug: 35846264
Change-Id: I878e581db3bf60b9c6b2cf861f66d8b427202b02
We clean up surfaces from apps which were stopping (mDestroying=true)
but not stopped when we resume, as described in commit 45e6d2d. The removal
of preserved surfaces was added earlier in eb66557 for a use case where
an app is stopped without an animation pass. It seems the clean up of preserved
surfaces on resume may be more coincidental than intentional, so let's try
disabling it! This fixes flicker at the end of the PiP animation when we use
preserved surfaces for switching in to fullscreen.
Bug: 35396882
Test: Move PiP to fullscreen. No flickers?
Change-Id: I0df55b11774c826027b0982fca7a28f4d8322d1d
Stop relying on the file marker recorded by the runtime. We have the
same data available from the DexManager.
The clean up CL to remove the handling of the file markers will follow.
Test: verify that "shared packages" (e.g. gmscore) are not compiled with speed-profile.
Bug: 32871170
Change-Id: I6cc5834ac88489e69896cd5fba9ed9968aa7f5a2
During the pinned animation from fullscreen we
layout the window for as if it were fullscreen. However
this logic determines that we then overlap the content area
and unhelpfully tries to adjust us.
Test: Manual.
Change-Id: I1cbeb47731062f95c631e8cbd1f0601085d1762f
Also kills off one user of GraphicsJNI.h!
Change-Id: Icbf979e485b3b6ec2f37e18ff654b8ff1e44fb35
Fixes: 34712423
Test: cts CtsGraphicsTestCases --test android.graphics.cts.BitmapTest#testNdkAccessAfterRecycle passes
Add javadoc comments for the getMetrics() functions that
we've added to android.media.Media{Codec,Extractor,Player}.
This describes the currently implemented functionality.
Bug: 35096098
Test: Compilation
