| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
vold will store password securely until KeyGuard requests it
and hands it on to KeyStore.
This is a revision of
https://googleplex-android-review.git.corp.google.com/#/c/418123/
which was reverted. It had two bugs in LockSettingsService.checkVoldPassword.
1) We were not checking password for null, which caused an exception
2) checkPattern/checkPassword return true if there is no saved pattern or password.
This leads to situations where we get true returned even when the password
doesn't match. Call the correct one based on what is there, not what vold
thinks ought to be there.
Bug: 12990752
Change-Id: I05315753387b1e508de5aa79b5a68ad7315791d4
|
|/
|
|
|
| |
Bug: 13723878
Change-Id: If1f54de4112a120848df72192b82e35b341e8ed3
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 493e3e7e6523fd94cc1acae3e45935a1227d58c3.
Should fixes
Bug: 13611885
Bug: 13656830
Change-Id: I117c988bb6679f44f8add4fcc18f45cb8238dfb4
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
vold will store password securely until KeyGuard requests it
and hands it on to KeyStore.
Needs matching vold changes from
https://googleplex-android-review.git.corp.google.com/#/c/432050/
Bug: 12990752
Change-Id: I930ed8180cf0b8feb1e58db043d5fb6dff1bab20
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
"Attempt to fix a bug where SIM progress dialog gets stuck." into klp-dev
* commit '1d6c2573d4b2824511354d651d7350df327f454f':
Attempt to fix a bug where SIM progress dialog gets stuck.
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
progress dialog gets stuck." into klp-dev
* commit 'abde0aaa7958976b8f3a66e348d6a5152b0d838e':
Attempt to fix a bug where SIM progress dialog gets stuck.
|
| | |\ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
dialog gets stuck." into klp-dev
* commit '375ff2c4a7b42d6dfd333e0ffa351be88fdab034':
Attempt to fix a bug where SIM progress dialog gets stuck.
|
| | | |\ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The fix makes sure onPause() is called when KeyguardHostView
is removed.
Bug 10323372
Change-Id: I20dd1f68c270adbd4582f2cd8ed9b03964b4477c
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | /
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
Lockscreen album art from activating FLAG_KEEP_SCREEN_ON"
* commit '99689a6874c7c465ed97dba625d38e3f1599963f':
Prevent Lockscreen album art from activating FLAG_KEEP_SCREEN_ON
|
| |\ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
activating FLAG_KEEP_SCREEN_ON"
* commit '00efaea980c7a9f84f326b22aef740cb5438d282':
Prevent Lockscreen album art from activating FLAG_KEEP_SCREEN_ON
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a small fix to the showWallpaper method, in which a power
consumption problem has been introduced. This showWallpaper method
toggles the window flag FLAG_SHOW_WALLPAPER, when album art is being
shown in Lockscreen. It is important to set pixel format to
PixelFormat.OPAQUE if flag FLAG_SHOW_WALLPAPER is not being set.
If not, an application that uses window flag FLAG_KEEP_SCREEN_ON
will prevent the keyguard from going to sleep and drain battery.
Change-Id: I1808be28047977ae5ac4dd1168ea25cac8a55a78
|
| |\ \ \ \
| | |/ / /
| |/| / /
| | |/ /
| | | |
| | | |
| | | | |
bug" into klp-dev
* commit '16858164c73f0696d12161e97bad9cb22c55e603':
DO NOT MERGE - Fix keyguard pattern lockout bug
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(cherry picked from commit 7c11f8b4659c3444d5037b756b6e5f45a2ea61a6)
Conflicts:
packages/Keyguard/src/com/android/keyguard/KeyguardPatternView.java
Bug: 13302967
Change-Id: Ifa4c01e630bd3aa8cadfea8dbbbb4686d50eb945
|
|\ \ \
| | | |
| | | |
| | | | |
entered."
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 13302967
Change-Id: I78404acd700c338e58270471ba307dad9a6884d6
|
|/ / /
| | |
| | |
| | | |
Change-Id: I6fce6640e391d5f78468212aac7d14a8a6170115
|
| | |
| | |
| | |
| | |
| | |
| | | |
On eng and userdebug builds, adds the possibility to track touch and sensor events on the Keyguard.
Change-Id: I9ff9fe5545cb9b7e6833a6af0b5a97a6c204dbd2
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Enabling notifications on keyguard tripped keyguard into simple
mode which isn't ready for prime-time. Disabled with variable.
Fixes bug 13172958
Change-Id: Ia281b06d754cd62455010f9e31c0ee81e4937977
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Hide managed profiles from lockscreen user switcher on tablets.
Hide managed profiles from power menu user switcher on phones.
Add flag to enable multi user ui turned off by default.
Change-Id: I4c69a6f7b0f39c249fc85fd940318df1ddab073f
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
$ adb shell settings put global lock_screen_show_notifications 1
Previously a per-user secure setting
(Settings.Secure.LOCK_SCREEN_ALLOW_NOTIFICATIONS), but this
doesn't really make a lot of sense since this behavior
pertains to areas of the system (keyguard, status bar) that
exist outside of any one user.
This setting now effectively enables notifications on the
secure lockscreen for all users.
Change-Id: I9c5179498dbbba9343184efdedb1587ea862cf96
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes a bug where input wasn't being enabled when the security
method changed. The solution is to propagate changes back to the parent
Add missing copyright header to simplified keyguard view.
Bugs 12135931, 12879769
Change-Id: I0fc6cf8ef3b628c96a045797a5b9cdecd3a1007a
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds a simplified KeyguardHostView that's intended to
be used as an overlay or dialog for asking the user's
credentials.
Bug 12135931
Change-Id: Iecede0715d671e88024e7bb77e7432cd1c7ec356
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Add simplified KeyguardHostView
- Move common functions to KeyguardViewBase.java
- Create new KeyguardSimpleHostView class for simplified view
implementation.
Bug 12135931
Change-Id: I8d6b0a61c36a0c7ceb87da4da54b1dfbed0054ff
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In this implementation, DISABLE_NOTIFICATION_TICKER (which was never
really used on its own and can be safely subsumed by
DISABLE_NOTIFICATION_ICONS) is now DISABLE_PRIVATE_NOTIFICATIONS;
when this SystemUI bit is set by the keyguard, SystemUI knows to switch
its presentation into "public" mode, in which
VISIBILITY_PRIVATE notifications are replaced with their
publicVersion's contentView (or a placeholder view,
synthesized by SystemUI, that leaks no additional
information about the notification). VISIBILITY_SECRET
notifications are suppressed altogether in this mode.
This behavior is enabled but not activated by default. To
turn it on, run:
$ adb shell settings put secure lock_screen_allow_notifications 1
and restart SystemUI.
Change-Id: Id660bef7737580e16a83f60567c22b53ee81c602
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug 12135931
Change-Id: I9f2e20fb4c1a2cb6a9fb49f4b6939fd7687ef262
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to KeyguardSecurityContainer.
This removes and/or simplifies the interface between modules to
allow easier separation of KeyguardSecurityContainer into a stand-alone
component.
Bug 12135931
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
"Telephony: Modify code to check that PUK code length is always 8."
* commit 'dafb2420a34a5b39aca6ddf993e86778edd76b5d':
Telephony: Modify code to check that PUK code length is always 8.
|
| |/
| |
| |
| |
| |
| |
| | |
As per 3GPP TS 31.101 Release 11 section 9.6, the number of digits
for UNBLOCK PIN (PUK) is always 8.
Change-Id: I4ea69fd8e2e8e96330d10a67b2d1f5a1859c1016
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
did not properly trigger abortion of the camera animation.
Also minorly simplified the touch slop calculation
BUG: 12036618
Change-Id: If01b48c815200066b32a37ffc44949edde1376f9
|
| |
| |
| |
| | |
Change-Id: Ie55a5d4bb58c2944952fc84cce32d3573a3a1a22
|
|/
|
|
| |
Change-Id: Ia1f99bd2c1105b0b0f70aa614f1f4a67b2840906
|
|
|
|
|
|
|
|
|
|
| |
The previous code was looking for just the display to turn off.
It should wait until keyguard is actually shown before enabling
the external presentations.
Fix for bug 11694904
Change-Id: Iebf3aa04fc094cd4e5c8f56bc771aca1e5921d04
|
|
|
|
|
|
|
|
| |
This fixes a bug where we'd show keyguard on top of setup.
Fixes bug 11689756
Change-Id: I38ecdafc00fc34fdd79e3ac517042a1e5eea93de
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a bug where keyguard was attempting to set up
external presentation displays from the binder thread instead
of the UI thread. Bad dog.
Fixes bug 11676486
Change-Id: Iadbe485691acc56a41b23219fe399f7eda40cb7c
|
|\ \
| |/
|/|
| | |
klp-dev
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a bug where an app calls KeyguardManager.isLocked()
before keyguard has had a chance to show. The fix is to assume
keyguard is showing and secure until we know otherwise.
Fixes bug 11670159
Change-Id: Ifbe4cdf40e3b76d2069ecace940f85fa58f31187
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
This reduces the camera transition timeout to 0 if launched
from the navigation bar. The transition cannot be aborted once
launched.
Change-Id: I7c376fbb90fd51cd301ef49fbd3411370bc2e4b5
|
|/
|
|
|
|
|
|
|
|
|
|
| |
This reduces the amount of time available to the user to cancel
launching the camera in order to improve average launch time.
It also increases the threshhold for flings and motions to prevent
unintentional launches which are costly in terms of falsing.
Fixes bug b/11657355
Change-Id: I852abbe3ce8ddddcb65f3a48a2f8111d20126189
|
|
|
|
|
|
|
|
|
| |
This waits until the keyguard window is actually removed before turning
off external presentations to avoid flashing the user's password.
Fixes bug 11562369
Change-Id: I74bfc0d5e23dccc5a8628abfe02868c71c371f6e
|
|
|
|
|
|
| |
Fixes bug 11562369
Change-Id: I577f9d3683e62689954b4640601b3f360b78cb31
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a bug where the music scrub position would snap
back to a previous position. The problem was caused by latency
in the music application responding to scrub position changes.
The latency would mean that we'd get a response periodically
to some historical scrub position change.
Since we can't know when the state will become stable, we
just wait a little bit since the last update change before
continuing to update the scroll position.
In order to keep the music client from falling behind, we
throttle scrub updates.
Fixes bug 11351267
Change-Id: I6204833328751d1da781b4e078a2d557c1f93ff3
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 11063890
- Workaround for bug 11063890. Avoids the acquire/release
race when resuming face unlock while pausing the camera
widget.
Change-Id: I0a58f3a07f346da72ea55772242b4f9c54537235
|
|\ \ \
| |_|/
|/| | |
|