| e4044bb617ea849939058d953e250fcd540c75cc |
|
11-May-2016 |
Jim Miller <jaggies@google.com> |
Fix KeyguardManager.isSecure() to observe work profile
The fix passes the calling userId instead of the current userId to
allow apps running as managed profiles to work.
Fixes bug 28666104
Change-Id: I9f8676ab11bd581d9e67b2b9f385036d4d3576ee
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| f1cdf9558d2b7f8fe5b8cf3d309b48809f04403b |
|
06-Apr-2016 |
Jorim Jaggi <jjaggi@google.com> |
Don't lock device when double tapping
Bug: 24265204
Change-Id: Ia19e956def454604ed3f3e3e9815fc1872ef649a
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 691546e5b7f94a6e2d76630ee1287e0b9c69e7a8 |
|
09-Feb-2016 |
Adrian Roos <roosa@google.com> |
Isolate Keyguard from main thread badness
Adds a bindService variant to run the ServiceConnection callbacks
on a dedicated Handler.
Changes KeyguardService binding to use the foreground thread
instead of the main thread and changes state to the
KeyguardScrim on the UI thread.
Bug: 26954967
Change-Id: I9d7bd85382816cd0e23772b14ff6518266a9d232
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 2f3e35376ada0327b34a71d7c45ac6e6d955d7dc |
|
21-Dec-2015 |
Jeff Sharkey <jsharkey@android.com> |
More work towards triaging missing app behavior.
Many places across the platform query package details without
gracefully handling packages or components that go missing for
various reasons. This can cause annoying user data loss, such as
resetting back to built-in apps or dropping of accounts, etc.
This change verifies that system callers have thought about these
edge cases by logging if they use default matching behaviors without
explicitly marking themselves as being "triaged." (The logging is
currently disabled by default.)
Also creates explicit definitions of supported flags for various
incoming PackageManager calls, and defines a clear distinction
between flag types:
-- GET-style flags are used to request additional data that may have
been elided to save wire space.
-- MATCH-style flags are used to include components or packages that
would have otherwise been omitted from a result set by current system
state.
There are a handful of existing GET flags that better fit under the
MATCH definition, so this change clones them to new constants and
marks the old ones as deprecated.
Fixes bug in JobSchedulerService to consider jobs from apps on
external storage. Revert some dialer behavior back to being
untriaged.
Change-Id: I9b6ab0968241e3479bddbd78de0c51e3b9917318
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 5217cacbd9f382068bb9e176cd5a0b15388a335c |
|
20-Dec-2015 |
Jeff Sharkey <jsharkey@android.com> |
Make JobSchedulerService encryption aware.
When a user is started, but a persisted job component doesn't appear
in the normal resolution list, we avoid enqueuing the job. Later
when the user is unlocked, we take another pass over the pending
jobs to see if they became available.
Load keyboard layouts from XML metadata regardless of crypto status,
since we don't need to spin up any remote code.
Add MATCH_SYSTEM_ONLY to make system logic easier to write when
looking for trusted components.
Sprinkle more annotations on ArrayUtils methods.
Bug: 26279465
Change-Id: Iec28e0bb46862b07d740b12a79f6360de68dab0f
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| e4de5a0d3b6e0c897c1cea0912b58e11db962365 |
|
23-Sep-2015 |
Xiaohui Chen <xiaohuic@google.com> |
Cleanup OWNER references.
Bug: 19913735
Change-Id: I2150c6baaab80fe11312e4401394a2a8da52e595
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 84dc08a208eea7a4ddf043cadbb28987cf90ae22 |
|
12-Sep-2015 |
Jorim Jaggi <jjaggi@google.com> |
Dump Keyguard state in SystemUI and PhoneWindowManager
Bug: 23970549
Change-Id: Iec1e8ac507268086e0e2935847eda606ea1fb700
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| c04960733110cac07c9aaa2e75ec5dc83e3a36f0 |
|
20-Aug-2015 |
Jorim Jaggi <jjaggi@google.com> |
Save interactive/screen-on state in KeyguardServiceDelegate
So when SystemUI/Keyguard crashes, we only call onStartedWakingUp and
onScreenTurnedOn when the device is interactive and/or the screen is
on.
Bug: 23344236
Change-Id: I0d0be91ff15d6c552304659956770ab88bb26ba4
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 4a0e791cc0a71df2b0c6bae6e92a5f2100fb5841 |
|
30-Jul-2015 |
Jorim Jaggi <jjaggi@google.com> |
Workaround View.post issues to fix runtime crash
Using View.post was really dangerous because when the view wasn't
attached, it got posted on the run queue of the *calling* thread.
However, that run queue was never executed until power down, and
then it was executed from the PowerManagerService thread, because
that was the calling thread when we posted it. Work around this by
using a solid Handler.
Bug: 22820787
Change-Id: Id60e49e859558993256fae0403236f2e4b6f1075
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 0d210f6395072db4a4c53d4cb8fac4a59a3965b4 |
|
10-Jul-2015 |
Jorim Jaggi <jjaggi@google.com> |
Animation for touch, wake and unlock
- Add callback to inform SysUI when the screen has been unblocked
and turned on.
- Cleanup inconsistent messaging about device interactive/screen on
and off.
- Add callbacks to inform SysUI about screen states
- Implement a quick fade for the scrim after touch, wake, and unlock.
First, start with a black scrim on top of everything, and then fade
it out.
- Make sure we play the normal unlock animation when device is pulsing
- Override navigation bar animations for touch, wake and unlock: Fade
in the same manner as the scrim.
Bug: 22571198
Bug: 21855614
Change-Id: I8ff08d72cced1e0f03c78d71ff710d8a4f6b848c
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 740452e8756cb7f51ed185c3906a5ca61b8fcdd4 |
|
09-Jul-2015 |
Jorim Jaggi <jjaggi@google.com> |
Touch, wake and unlock
- Add onFingerprintAcquired, so Keyguard can grab a wakelock to prevent
the device from sleeping.
- If we get a successful fingerprint, wake the device up, immediately
dismiss the keyguard and tell PWM that we kicked off our frame that
will represent the correct state.
- PWM then waits for this frame to be drawn, and then turns on the
screen, which results in unlocking directly to the previsouly
opened app.
Bug: 21855614
Change-Id: I5f43df17fa5e4e9c6a6392eef4a4590b07df4f96
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 3542f7de3333f57bf0d01d8cfbd91a2a42038bf9 |
|
14-Jul-2015 |
Adrian Roos <roosa@google.com> |
Fix stuck scrim on keyguard-less devices
Bug: 22413062
Change-Id: I6da6438ec54d33a1aa82d5575eb29e9bc4dbdd58
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| d175b6cfe0b35dfe251cc9315aacb048bf6e54c5 |
|
28-May-2015 |
Jorim Jaggi <jjaggi@google.com> |
Cleanup Keyguard handling when turning off screen
Before, Keyguard was shown whenever PhoneWindowManager went to sleep.
However, this was too early on some devices, and too late on others.
Now, the callbacks are split up into two phases: startedGoingToSleep
and finishedGoingToSleep. In the first callback, we decide what to
do and play the lock sound if necessary. In the second callback, we
actually show the Keyguard, or reset its state necessary, so it
doesn't interfere with the screen off animation.
Bug: 17929748
Bug: 20782303
Change-Id: I4c4406595b07b7589d64f380cd3fa96bed3d20ee
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| f253eeb9d3d23d02746406b2b0e721ba3b4563ce |
|
16-Apr-2015 |
Adrian Roos <roosa@google.com> |
Fix lockscreen bugs with SHOW_WHEN_LOCKED
When unlocking to a SHOW_WHEN_LOCKED activity by clicking
a notification, we don't get a the startKeyguardExitAnimation
because Keyguard is not actually going away. Instead, we start
it ourselves.
Also fixes the bug where restarting Keyguard while it's occluded
lead to an inconsistent state where the user got stuck on the
lockscreen.
Bug: 16481924
Change-Id: Iebc5bdd1287bbb81415ae01c7428850acc16c53f
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|
| 2a18cbcffaa7e8e34f7cd8b91e930eb2c08a6ef6 |
|
09-Mar-2015 |
Bryce Lee <brycelee@google.com> |
am 1b8df04b: am 8aeab6c8: Allow the keyguard service to be configurable.
* commit '1b8df04b8d754f68dc6bfa6caa9e0a2666d16933':
Allow the keyguard service to be configurable.
|
| b10e33ff804a831c71be9303146cea892b9aeb5d |
|
04-Feb-2015 |
Jorim Jaggi <jjaggi@google.com> |
Split up android.policy into framework.jar and services.jar 1/3
Change-Id: Ifd69f1f3dd308a7e17a1442e2f3950da8b03cec4
/frameworks/base/services/core/java/com/android/server/policy/keyguard/KeyguardServiceDelegate.java
|