This CL alone doens't fix the whole bug, see the bug
for the AI list.
In normal mode, clicking at application icon on a task view
is ignored to avoid accidental clicks. To open app properties,
we need a long click.
In accessibility mode, we want to make it easier to open app
properties, and accidental clicks are less likely. Hence, allowing
"simple" clicks.
Bug: 20945599
Change-Id: Iec3f911dced1eda09175500fc1e798dd09b6f9e2
Creating the thumbnail of the header for the transition was on the
critical path for starting the activity. This moves it off this path
by doing it after onPause().
Change-Id: Ic54a104d5ad4c40e88638566a3a69cc265a0a0fe
Because we created a bunch of layers, this delayed calling start
activity in the window manager. Disable these layers, as they are
not really needed.
Change-Id: I59343a92726665f72215a0699c52ead76e78a4b3
- Precache the bitmap for the window animation in the preload phase
- Remove some post's so we have a faster path from UP -> startActivity
- Don't dim the headers in the first frame drawn, because layer
creation is slow. Instead, do it in the second frame, when the window
animation is already running.
All these changes combined make going to recents about 40-50ms faster.
Change-Id: I3e4060af1ac57b3f359fe7f86f9e3814c6490323
Don't refresh the state if its not different.
(This way setAllowAnimation won't get called when it shouldn't)
Bug: 21335624
Change-Id: Id6f8961b32d12141db5ac0bb847e4751b8a159b8
Previously going to the full shade and expanding notifications
where disabled when QS was expanded even though there was enough
space to allow it. This is now allowed again in order to have
a consistent experience.
Bug: 19712809
Change-Id: Ie756d9c3fbf9dc2e60a05d02f0f4cc5dd6c7ebe0
Now the preview clipper animation and our own circle drawing
are in sync again when launching an affordance!
Bug: 21440634
Change-Id: I96cda04926fb9ae62db6690ddebaf73df38e9ca9
When a notification came in dreamMode and would become a HUN
we were firing its fullscreen intent imediatelly. If that notification
got updated again a moment later, it would also show an additional
HUN even though we just launched the fullscreen intent. This is very
troublesome to handle on the app level, as the notification state
is the same. We are now introducing a cooldown for HUNs when it just
launched a fullscreen intent.
Bug: 19377091
Change-Id: Ib32341c8983f0e977354432ea8d8e98909a13829
Changes the brightness slider to have no visible steps
when in auto brightness mode. Also changes mirror
logic to dispatching touches instead of forwarding values.
Bug: 19516826
Change-Id: Ib0233c2dcc6807da96a71d1f5619a117ca2a73bd
- Move "End now" button to its own line, below the condition lines.
- Add the feature name "Do Not Disturb" to the condition summary
for the indef condition.
- Fix found RTL issues with the footer.
Bug: 21171893
Change-Id: Ia12fe57d46a5547beec82cf76e175982bfa3fd6c
Taking connect/disconnect events into accounts results in frequent jank
while trying to show the icon.
Bug: 21504588
Change-Id: If271980cc46cfc20f80083de17a4b57c42439069
1. Also notify input is restricted or not when IKeyguardStateCallback callback is added.
When first Keyguard is showing after boot, the mInputRestricted is not updated. So,
inKeyguardRestrictedInputMode still returns false, although device is locked.
2. If mShowing remains false during setup time of KeyguardViewMediator, mInputRestricted
is not updated. This is because updateInputRestrictedLocked is called only if showing
value is changed during setup time.
For this reason, when device is not provisioned, inKeyguardRestrictedInputMode returns
false, and device does not restrict key.
3. If one of callbacks causes RemoteException, the other callbacks are not called.
This is because catching RemoteException breaks for-loop.
(cherry-picked from commit 516dad062580201d7a4ad6c112b23434385d5268)
Change-Id: I0281405127bcc75285b908d01485da3ac9b40b52
Signed-off-by: Dooyoung Hwang <dooyoung.hwang@lge.com>
Let the intent receiver of a camea launch intent declare a prewarm
service instead of sending broadcasts.
Bug: 21347653
Change-Id: I11e31aad4f788ad90eb46a661b819d3e808ddb51
