| 69bdee7c873c4a2295651efda2d0e79c515acc17 |
|
23-Oct-2012 |
Daniel Sandler <dsandler@android.com> |
Integrate new PIN pad.
Change-Id: I08d6551dfde501c5526eb6fd641ae08475c1365b
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| 63f9b81795559443e0376985f8aaaa97a359ef94 |
|
16-Oct-2012 |
Jim Miller <jaggies@google.com> |
Fix inoperative "Forgot pattern" button when face unlock enabled
This fixes a bug where the forgot pattern button wasn't working because
the logic for face unlock was interfering with determining the proper
backup to use.
The fix:
- adds a new state to SecurityMode so we have an initial condition
we can check for.
- passes the current mode to SecurityModel.getBackupSecurityMode() so
it relies on the current state.
- prevents face unlock from invoking callbacks that change state
once we're no longer showing face unlock.
Fixes bug 7346989
Change-Id: I4e64515efbbad712f11c820e690b458f352bf46c
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| d95c659a1d621dfbdd892759419ffc089e248672 |
|
12-Oct-2012 |
Danielle Millett <dmillett@google.com> |
Suppressing Face Unlock during phone call - fix b/7339069
Now that there isn't a swipe before launching face unlock, face unlock
needs to be suppressed during a phone call. If it isn't it will popup
on top of the phone call screen.
Change-Id: Id6c4165bf4df606ebf396c151f1c80603d5abca3
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| 0ff7f010f8bfd011f0915031b02739ae3bee401e |
|
12-Oct-2012 |
Jim Miller <jaggies@google.com> |
Change keyguard to use single-stage unlock.
Change-Id: Ica175a90ef4400941c7c4f05a494003b85d5e88c
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| cc4104fd71225ed092f16b11882d9a10084e34ac |
|
09-Oct-2012 |
Brian Colonna <bcolonna@google.com> |
Suppressing FUL after user switch (fix b/7316467)
When switching users, Face Unlock starts in onResume(). However,
there is no signal to indicate when the user actually sees their
unlock screen. This means Face Unlock could be running unseen, timing
out soon after it becomes visible, or letting the user in before they
see the preview.
This fix simply suppresses Face Unlock immediately after switching
users. This is not the ideal behavior, but there is no easy way to
make Face Unlock start only after the unlock screen becomes visible.
When the user changes screens it becomes unsuppressed, so if they go
back to the multi-select widget screen or login, Face Unlock works as
expected and is only suppressed again when the user is switched.
Change-Id: I80a302b0aefc1dee3c2dc77557978cbe062de435
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| 9ded0e1d48c016883858dd2dc574787524c6df84 |
|
08-Oct-2012 |
Brian Colonna <bcolonna@google.com> |
FUL fallback is no longer account login - fix b/7280196
When Face Unlock failed the maximum number of times (3), it was asking
for account login when it should have been asking for the backup lock
that the user chose when setting up Face Unlock.
This change splits the isBiometricUnlockEnabled() function into two.
One of them strictly checks whether it exists and is selected. The
other one checks whether too many attempts have occurred. When
deciding which backup to choose, the decision is now based only on
whether Face Unlock is enabled. Checking whether too many attempts
had occurred caused the bug because the check indicated it had already
'fallen back' to pattern, and the backup for pattern was being
selected instead of the backup for biometric unlock.
Change-Id: I6b9cf2c5155e8c14933cbfc8f5d58ebc007e53cb
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| 109f1fd80c90409c0d7f21d49989641dfdf2ad1b |
|
20-Sep-2012 |
Jim Miller <jaggies@google.com> |
Update keyguard selector view to match UX design spec
- Use new Roboto-Thin font
- Add new keyguard-specific date format
- Layout tweaks to keyguard selector screen.
- Add smart EmergencyButton class
- Add selective upper-casing of components on the display to enable later UX decision
- Work around SIM state bug
Bug: 7094419
Change-Id: Ic7e0f30697c14d4946372509d98ad81bf6a23c92
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| 47df44aad773fb2a46d4c07e20278c7d8c0b16be |
|
07-Sep-2012 |
Jim Miller <jaggies@google.com> |
Fix EmergencyDialer button on devices without telephony hardware
This fixes showing the emergency dialer on devices without telephony.
Two fixes were required: 1. Move emergency dialer code to the view
that contains it (KeyguardSelectorView). 2. Always call onPause()
or onResume() in onScreenTurnedOff() and onScreenTurnedOn(), respectively.
Fixes bug 7117895
Change-Id: I96769fdda8478b6b60f46f7470bed2279ea2de72
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| 258341c377b6aa9f1bd29a9b507a97967e432dfe |
|
31-Aug-2012 |
Jim Miller <jaggies@google.com> |
Lots of keyguard improvements
- Fix "too many attempts" dialogs
- Fix account unlock mechanism so the user can use email account as backup for pattern unlock
- Add mechanism to support future account recovery from non-pattern screen
- Tune animation timing for flipping security view.
- Move password field to the top of the security view
- Add padding and visual feedback to navigation area button
Fixes bugs 7088482, 7088631
Change-Id: I23099feae3b7446ec291d8f860601bfc12f9edd8
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|
| dcb3d84b82cc2448d04e73359a716581bfb657db |
|
24-Aug-2012 |
Jim Miller <jaggies@google.com> |
Replace keyguard with new implementation
This change refactors keyguard to be more modular and maintainable. More
specifically, it replaces the top-level view with just one device-dependent
view that contains two views: a widget area and a security area.
The widget area can be populated with custom widgets.
The security area contains the current security method as dictated by
the stored password quality.
This change contains both the old and the new keyguard with the old keyguard
still enabled. The new keyguard will be enabled in a subsequent change.
Change-Id: Id75286113771ca1407e9db182172b580f870b612
/frameworks/base/policy/src/com/android/internal/policy/impl/keyguard/KeyguardSecurityModel.java
|