- Between the time that the task view is bound and the thumbnail is
loaded, we should still draw the background color instead of nothing.
Bug: 27971061
Change-Id: I5b7a607b86a0da20fc6ca183b1d7bc4e9db9e377
If AlarmManager.cancel is called before any component has had a chance
to register an alarm, sWrappers will not have been set, as it is only
initialized in setImpl.
When cancelling an alarm and sWrappers does not exist, log a warning and
return early.
BUG: 27972657
Change-Id: Ied10719ba1d154f97eecfc32f429fd9ce39bf747
Also:
- Fix cross profile pinning. Now ShortcutLauncher correctly keeps
track of target package user IDs.
- Add performance stats for package manager calls and show them on
dumpsys.
Bug 27548047
Change-Id: I2472980b2955b6c70947aaaa9b76f75d0616db6e
Update configuration with WM first and check if the stacks need to be
resized due to the update. If so, let activity manager resize the stacks
inline, instead of letting WM schedule another pass of resizeStack. This
way the configuration will be updated to the latest before ensureActivity-
ConfigurationLocked, and we don't need another relaunch there.
bug: 27834014
Change-Id: Ib761a96cada0c3247b0480f18370670c593159da
Bug 27969302
mCalledExitCoordinator can be nulled before the onResume is called,
so it cannot be used to determine whether or not the Activity is
a caller or called.
Change-Id: Ie3696ed59b89cfc8c6145d22bc230111f0813701
There are now three rules that guard intent filter priorities:
1) Only privileged applications will be granted a >0 priority
filter [previously, _all_ system applications could do this]
2) There are certain actions that are considered protected [eg
ACTION_VIEW, ACTION_SEND, ...] and even privileged applications
will NOT be granted a >0 priority filter. There is one, and
only one, exception for the SetupWizard.
3) Updates will NOT be granted a priority greater than the priority
defined on the system image.
Bug: 27450489
Change-Id: Ifcec4d7a59e684331399abc41eea1bd6876155a4
Forgot to cache the creating of ResourcesImpl during an Activity
override config update.
Bug:27644297
Change-Id: I65d9086f6d32f5adc7231aa3a1797d4f00c4b9a9
- We rely on the last-active-times of the task records to order tasks
in Recents, but for affiliated tasks, their last-active-time was never
set until the task was launched. This change just ensures that all
tasks have a valid last-active-time, and for affiliated tasks, ensures
that the task that they were launched behind always has a later
last-active-time.
Bug: 27597746
Change-Id: I9692c2b48ac6d12266de90bdf423f689402a94c2
- Workaround for crash in RecentsImpl where we could be retrieving the
transform for a task that is not at the front of the stack (can happen
if time changes, etc.) However, since we only use the size for the
transition, we can always force-update the transform.
Bug: 27849282
Change-Id: I86eee4c158748e4f13a2daeac5cf040c0874f967
Also add some tests to the notification manager service
to make the refactor more palatable.
Bug: 27742532
Change-Id: I745915299aa2b92ab077e0c801d47864cb562325
Default writeType for GATT characteristic was not being
serialized into Parcel. This cause errors when trying to
write into Characteristic.
Bug: 27910548
Change-Id: Ib2f88cf991123eaea244f16fa36deb0d773c5a33
Added handling of app query reponse from context hub.
Exposed the maximum message size to clients.
Change-Id: I8d8ecaa2e75f6ef86ee65a3a050538cbbadc32eb
Sets default gravity value to the aptly-named DEFAULT_CHILD_GRAVITY.
Also cleans up FrameLayout lint warnings, annotations, and whitespace.
Bug: 27576632
Change-Id: I457b13791ff85f2228e61e85e44a502a28439e01
refactored button inflate code and add a logic to handle selected style update.
Change-Id: I61f9c77396bea63a24fc78bf02ebad54a426a3ed
(cherry picked from commit b865ae2a4c892e2ffd83947e40ebd27d35b18fa6)
Rename AudioRecordingCallback.onRecordConfigChanged() to
onRecordingConfigChanged() after API council review
Bug 27952000
Change-Id: I362a973781e029bca921181934599dcf60e13136
