When cancelling, the exception will be eaten by FutureTask, but
onCancelled would end up never being called due to the exception
causing the code to skip calling postResult.
b/30304893
Change-Id: I47d859d9ef77245889816b2b6e10bb380bc4979b
In the locked shade, we were returning to the lockscreen when
the last notification was clicked and removed due to autocancel.
We're now not going back there anymore if we're closing.
Change-Id: Idc4c2c145fb2ca308f236b99408cc6096dd02302
Fixes: 30642902
- Reverts the change to draw the drop targets opposite of the nav bar
- Fixes the issue with the drop divider being occluded by the nav bar
when the phone is in landscape orientation. Instead, expand the
drag overlay to include the nav bar space.
Bug: 30548794
Change-Id: I70ed3513547e101e49c8eba114a153c5a1f36bee
When activity process is force-stopped (like in the case we need to stop
it to allow debugger), activity record is removed and a new instance is
added. Depending on timing, adding of new record could happen before
or after old record is removed. If it added after old record is removed,
then the removal could cause AM to also remove the task AND the stack
(if the activity is the last one).
On WM side however, the task/stack removal could be delayed due to
animation. So when AM attaches a new stack, we end up with two stacks
with the same stack id in the DisplayContent. Also, AM reuses the last
used taskId after it's deleted. So WM is confused and didn't add a new
task record. Then when the delayed stack removal fires everything is gone.
We need to use a different task id when creating a new task record, even
if the last created task is already deleted. Also when attaching a new
stack to WM, first check if we already have such a stack in DisplayContent,
if so, reattach it and don't create a duplicate.
bug: 30465601
Change-Id: Ic399a32c54f6acdcbb9a0c6155599331d55df232
Adding a new connection event which Telephony can use to inform upper
layers of a failure to handover to WIFI.
Bug: 30697460
Change-Id: I75da2f956a6b70a9bf4cf7128f29968e08172dc3
In the case of no activity options we won't initialize
it again later, and so we will override the apps request
with a hint of 0 (ROTATION_ANIMATION_ROTATE).
Bug: 30683604
Change-Id: I5eed12adfbb241859503bcd40f15ee82141436d8
Generic types, such as List<String>, must be escaped when they are
used in XML. For example, List<String>. This commit adds
escape characters to the XML samples in the data binding page.
Bug: 30691285
Change-Id: If55ed55d13fb11038e2495884c79698e67219108
This lead to a whole area being accessibilityfocusable even though
it shouldn't have been.
Change-Id: I49ab58c3da768930576880d8793b2fe2657a0aa8
Fixes: 30315141
An accidental side-effect of introducing the XML content file and its
domain semantic checking was that the shared-storage domain got
dropped on the floor. Now the mechanism understands what it means
again.
Bug 29999884
Change-Id: I22b99c96869683d1a92430f237dda54b170b8f60
Smoothly unlocks device when going from a SHOW_WHEN_LOCKED activity
to a DISMISS_KEYGUARD activity while the device is trusted.
This change suppresses the jank from going briefly through the
lockscreen if the device is trusted and unlockable without entering
a credential.
Bug: 27410215
Change-Id: Idd86e825d37a89538a0a1f690daf6afcf94a0699
If someone calls removeActiveAdminLocked more than once, it is possible
for the device policy data to end up with more than one copy of an admin
in the list mRemovingAdmins. Due to extra entries, once the admin
component is removed, it is not being allowed to be set as an admin again,
until the device reboots or mRemovingAdmins is cleared from the memory
due to some other reason. Fixing this by making sure we do not add
duplicate entries to mRemovingAdmins
Bug: 30369197
Change-Id: I1d53c41312171425bbd6e6e4153148276f1b098d
- Adds a trusted signal from Keyguard to PhoneWindowManager
- Allows PhoneWindowManager to exempt DISMISS_KEYGUARD windows from force hiding
- Allows PhoneWindowManager to dismiss Keyguard while occluded
Bug: 27410215
Change-Id: I3ad490b64a5805b6f3888a9f37fcfbdd0116395e
We've seen some jitter in motion events with accessibility
enabled. We can eliminate it by not passing motion events
through the filter if we know they won't be affected.
Bug: 30183085
Change-Id: I0ecc8d5a39c8e370fc3a8ab85c6357251a31f8ad
We were confusing handling of services that were unbound with
those that had crashed. We would lose track of services that
has crashed, start new ones, and then when the system restarted
a killed services we would have multiple instances running. It
was possible for this to get very out of hand.
Bug: 30306689
Change-Id: I4e63d25b6d2fec3ec68f450a4602898c43a2b2ad
DNM becuase Code has moved in master.
Symptom:
A source file is deleted even if a move operation is cancled
Root cause:
MoveJob doesn't check whether a move operation is canceled or not
after copying file
Solution:
Add cancel condition check before deleting a source file
Bug: 30240042
Author: Shiotani Kouji <kouji.x.shiotani@sonymobile.com>
Change-Id: Ie68e5d96304a125c07d46a2fd5e4c9d84903d1e7
