Implement path parsing from string to skia path in native. The parsing
contains two main stages:
1) Parse string into a list of nodes that contains one operation (such
as move) and a vector of floats as params for that operation.
2) Interpret the operations defined in the nodes into SkPath operations,
and create a skia path
Also provided unit test for parsing a string path into a list of nodes,
and then to a skia path.
Change-Id: I0ce13df5e3bb90987dcdc80fe8b039af175ad2e2
When starting the runtime from app_process, we only pass JDWP options
if starting zygote. It prevents from opening a JDWP connection in
non-zygote programs while Android apps (forked from zygote) remain
debuggable.
Bug: 23050463
(cherry picked from commit 7a09b8322cab26d6e3da1362d3c74964ae66b5d4)
Change-Id: Ib5b6d3bc4d45389993c3c54226df5a7b72479d19
(cherry picked from commit ff8dc21278b19b22ed8dc9f9475850838336d351)
It seems common for apk to not have launcher activity. I see it quite
a lot during SUW. It does not seems to be an error.
Change-Id: Iee417b0614ef17940371da9710ff14adbad82e3a
This will allow AMS to call into DPMS within the AMS lock instead,
which will help I1537bd57b34696768ee81a979d53bb396efbc12a.
- AM.clearApplicationUserData() will not be allowed for any DA
apps.
Bug 25567963
Change-Id: I9f0d071c815a011be4f4c85c502c39d0fe0fe5e8
Prevent early trimming of documents with distinct
intents. Otherwise when launching a document
from a given activity, existing recent entries
will always be pruned even if they are distinct
documents. We don't have to worry about overflowing
recents, a seperate codepath (from addLocked)
takes care of second pass trimming when we have
exceeded our total max recents.
Bug: 25460953
Change-Id: I71f8c3d46570df2c999f0d986e05515074e0a098
If the app is already removed, don't apply any more dim on the window
that's pending removal. It causes invalid DimState to be added back
to the controller, and we crash as these don't have valid dimlayers.
bug: 25570092
Change-Id: I7e3c56c6eb636fdcb01d9bba90f77b3885e216fb
When AMS.positionTaskInStack API is called we need to make sure
the task has the right bounds and configuration if it is moving
to a different stack.
Bug: 25501082
Change-Id: I2a80aa08a4ee52d860502ab16b6cdb432c954084
Debug overrides are only used if the application is debuggable in
order to help local debugging and development by trusting additional
CAs. In a non-debuggable version of the application the debug-overrides
are ignored.
Trust anchors in the debug override configuration have two key
differences from those in base-config and domain-config:
1) trust anchors in the debug-overrides are trusted for all connections
in addition to any trust anchors included in the relevant base/domain
configs.
2) By default trust anchors in the debug config override pins, as their
purpose is for connecting to non-standard servers for debugging and
testing and those servers should not be pinned in the production
configuration.
Change-Id: I15ee98eae182be0ffaa49b06bc5e1c6c3d22baee
In the hardware accelerated case, RenderThread needs
to be the authority of information on the geometry of
the SurfaceView (this will occur via moving the
repositionWindow call to RenderThread). In order
to support this we have to enable calling relayoutWindow
without geometry (so that it will not fight with
repositionWindow). Add such a mode to relayoutWindow
and use it from SurfaceView. Add size to repositionChild
while we are here.
Bug: 22802885
Change-Id: Ie45132c22f34cc6ecfe2446912b30bd1df414406
- Always set the docked stack mode when starting a task from recents
even if the task is already in the docked stack. The caller might want
to change the docked stack location.
- Return last persisted bounds for task that hasn't be restored into a
stack yet when AMS.getTaskBounds is called.
- Make sure there is a valid top activity when moving a task to a stack
before trying to preserve the window.
Bug: 25590206
Change-Id: Id115fc62c28913f999c62cdbbaccd887daa0fab5
- Only update the focused task as you scroll if we are in touch
exploration mode.
- Use stack's notion of focused task as the currently focused task may
not have a TaskView and can be scrolled offscreen.
Bug: 25590404
Change-Id: I5ef1b66ec74aa1a3131993ed84905210f1e45f18
Because we set it already in the future, it was called already
when we fetched the contents of the future, because it looked
like we overrided the callback. Instead, don't do callbacks
when calling the future, and save the callback in a separate
field.
Bug: 25568693
Change-Id: I8b7fd4248a2336470f8b7e12b64b0577dee96f6f
Because we didn't reset it after sending it to window manager,
they were used again in the next transition, leading to a
wrong animation.
Also fix a bug where we waited forever because
getAppTransitionAnimationSpecs returned null.
Bug: 25583739
Change-Id: Ifcccf2d3cee649f66b4ded1d92c059acfa02ba5b
When the window gets resized, we need to synchronize the
views with the model.
Bug: 25584567
Bug: 25584399
Change-Id: I27d6738cb4984ce91ce79671298bcdc0d317c6e1
In some intent handling modes folders shouldn't be selectable.
Note: There are probably *other* conditions where this should be true too.
Bug: 23936872
Change-Id: I5a1f6853df265d65415cc09e95005720bf5f91d7
This fixes a problem where recents would never be removed, because they
would run a dummy animation.
Bug: 25472312
Change-Id: I5767dc700966a49513e6338f4728c2ff275628ad
- Save the original task size and screen orientation. This ensures that
we will be able to display the screenshots in the right orientation if
we start taking non-square thumbnails.
Change-Id: I17ffe1fc05a447f67753149695a4eaf0baa36e8e
The CLs adds new table to MtpDatabase that contains additional
information to provide DocumentContract.Roots.COLUMN_*. Client code can
obtain these information by using the newly added queryRoots method.
BUG=25162822
Change-Id: Ib6596d38cbb4a42b689c75fffbd73585c0fb524c
The message being logged is "Unknown error" even for
known error types. This change provides more descriptive
error strings, for the case when the message isn't
explicitly provided by the DRM plugin.
Change-Id: Ic86478d7685cd33e21ecd2f875ef7dbed351e52e
related-to-bug: 25477595
