8b2baed2be04b4a8973bdd0bd404216b65c64452 |
|
03-Oct-2016 |
Fan Zhang <zhfan@google.com> |
Fix a NPE in confirm lock screen. The NPE happens is when using pin later. It's too late to recover if we just catch the NPE where it happens, so we should early terminate the call by adding TextUtil.isEmpty(pin) check. Change-Id: Id280cd1b8781678540c9ea281b3186edd04d61f9 Fixes: 31895774 Test: make RunSettingsRoboTests Test: manually enter correct/wrong/empty password/pin in confirm lock UI (cherry picked from commit 774e1d8443fa551bdcfb54de2fd478db42e70a16)
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
5e0a46bff6d801a52d9c50d19e25286a2afc8b40 |
|
13-May-2016 |
Victor Chang <vichang@google.com> |
Fix Continous loop in unifed screenlock when trying to Trust a CA cert Cause: with unified screenlock, ConfirmDeviceCredentialActivity didn't forward result with FLAG_ACTIVITY_FORWARD_RESULT Also, fixed that ConfirmDeviceCredentialActivity didn't allow fingerprint authenication in unified screenlock after keystore unlocked. In ChooseLockSettingsHelper, add one new util function to allow extra option to set returnCredentials to false while external to true. Set StrongAuth to "not required" when it has been successfully unlocked. Test: 1. PO Unified Screenlock/Work Challenge x fingerprint -> ok to trust cert (Also, no credential is returned in intent) 2. WorkMode off -> Reboot -> turn on Work mode -> no fingerprint option, PIN unlock successful to turn work mode on Bug: 28752364 Change-Id: I6dc8865e8f005545f8577d7731afb4495647062b
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
7655be05c1476ac2e3834e7757f56e18aa2a1713 |
|
21-Apr-2016 |
Tony Mak <tonymak@google.com> |
New UI to hint user about strong auth Instead of having a separate textview, we now reuse the detail textview to show the hint. Fix: 28204828 Change-Id: I3eff3240bf7ecb1495fbf11a073a273a0de603ae
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
a6fb46621b1c9375b51333e7ebe2126636d69126 |
|
14-Apr-2016 |
Oleksandr Peletskyi <peletskyi@google.com> |
Fixed stopped countdown when PIN entered incorrect. When device is locked CountDownTimer.onFinish() is not called after countdown finished. Thus some logic was copied to onResume(). BUG:28160696 Change-Id: I1906e7ab2202b437b909afc12b7b3628692a00f1
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
6655e1b6f594af7e3d12e8dfdd976f7249abea75 |
|
07-Apr-2016 |
Daniel U <uda@google.com> |
Hint user that fingerprint cannot unlock FBE keys Show a hint text to user noting that pattern/PIN/password is required when decrypting the credential based storage when file based encryption is turned on. The hint text is the same as that of the device unlock screen after device reboot. Bug: 27964055 Change-Id: I0d5a493bab69eae5ce4742bd07d4851387863cac
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
e7d6e4ddb2371dc49015e17e2d6b9dc604fbbf58 |
|
30-Mar-2016 |
Toni Barzic <tbarzic@google.com> |
Teach settings about PASSWORD_QUALITY_MANAGED constant Add hooks for adding an option for selecting a managed password as lock credential. By default this option will not be visible. BUG=27923581 Change-Id: Id17bd8074bf23cbcffb96d8576cc760df6f2298a
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
996d0dfa6e42e6249853397fafe4a93e7ffeb3f3 |
|
05-Apr-2016 |
Ricky Wai <rickywai@google.com> |
Fingerprint should confirm device lock when unified When unified and adding a fingerprint, the user is prompted to set up a backup Bug:27419438 Change-Id: I6cfa8c276ae69a0af51580be390c3da4e9596874
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
9d357ea072d5ebc0c9fb3798e80dc16c5fd78077 |
|
28-Jan-2016 |
Clara Bayarri <clarabayarri@google.com> |
Call reportFailedPasswordAttempt from Work Challenge Entering the wrong credential in ConfirmDeviceCredentials should also count as failed attempts for the password, after which the DPC have set a restriction to wipe the work profile. Fixed related issues, such as the CredentialChecker re-sending the result after onResume causing additional attempts to be counted. The new error message String is also displayed initially when there are pending attempts to inform the user that they are not starting from fresh. Bug: 26677759 Change-Id: I70cfae4c05e705ad7fe93bc071426459b79e7d0c
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
9d1bfd1e8de6e46137a9571507c03526880d6a46 |
|
27-Jan-2016 |
Chris Wren <cwren@android.com> |
port settings over to new metrics enum Change-Id: I0b3efd2f4db773ccbc52bfe59ee8eb0dab9584fb
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
40db4bbbb5dd262d801b0247fbfac39c7ab383b0 |
|
07-Jan-2016 |
Clara Bayarri <clarabayarri@google.com> |
Profile Challenge Fingerprint Support Change-Id: Ic83c479f645776dd0678721bfb732b399f09c992
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
34ec5f97feaf8d73d533f104cfc2c2e68e995ae3 |
|
22-Jan-2016 |
Clara Bayarri <clarabayarri@google.com> |
Fix Confirm/Choose Credentials strings related to profile The messages in ConfirmDeviceCredentials have been updated to inform the user that the pattern/pin/password to be entered is the profile one. The strings in the confirmation dialog when the user removes the lock have also been updated. Ideally we would have a parametrized approach to strings here, but capitalization makes it a hard problem. Bug: 26706338, 26709116 Change-Id: I9f5508d6f449f9e572d65e5b2dcb15cca23832b3
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
194300dff340d67255d12762ffb376b7ba201c87 |
|
13-Jan-2016 |
Benjamin Franz <bfranz@google.com> |
Add background image for work challenge If the challenge shown is for a work profile, add the default image and color to the background of the fragment. Change-Id: I148c6cd3a835a84c7bac78b020839dfdae4a6c36
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
c5cde055629a55475601b7e077c432e563258507 |
|
22-Oct-2015 |
Clara Bayarri <clarabayarri@google.com> |
Fire pending intent from Confirm Credentials flow Add support in the Confirm Credentials flow to read an Intent extra and fire it when authentication succeeds. This is part of the Separate Work Challenge feature. Change-Id: I52c203735fa9b53fd2f7df971824747eeb930f36
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
fe432e838e5588cd4ac664d7e74f3d70a99d7df1 |
|
12-Oct-2015 |
Clara Bayarri <clarabayarri@google.com> |
Refactor Choose/Confirm Lock flow to take user id This is a first step to allow this flow to be reused for setting a work profile-specific lock, to be used with the work challenge. Change-Id: Iaa65fdab9021cda5f0a1d3bc526a6b54f8a7dd16
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
39b467482d1bf256a111c757e9b7621c6f523271 |
|
10-Sep-2015 |
Jason Monk <jmonk@google.com> |
Depend on support lib preferences Bug: 24576551 Change-Id: Ic6190bacd3f7582c9bbc8de972da4612bd92421e
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
00b17fa3c36399dfa26f3d44f8ed369336c231a3 |
|
31-Aug-2015 |
Xiyuan Xia <xiyuan@google.com> |
Fix races in ConfirmPassword/Pattern - Add a CheckLockResultTracker to track result of async lock check so that it can finish on configuration change; - Let the pending lock check finish and ignore subsequent check requests; - Add a mDisappearing flag to prevent running disappear animation multiple times; - Check whether activity is still active after disappear animation before setting result and finishing it; - Remove no longer used mNumWrongConfirmAttempts; Bug:23190499 Change-Id: If1784d3d1fcc152ac06137b12748b9def5726692
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
7bdffd85ebae7b5b14eef07059cb501451476c7d |
|
05-Aug-2015 |
Andres Morales <anmorales@google.com> |
fix CC for work profiles Bug: 22257554 Change-Id: I09f62956d01f91d3014d9fa250aaff68ab5e1a9b
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
ce25af48383b26535ec07312ab0db6928bba1fe3 |
|
08-Jul-2015 |
Julia Reynolds <juliacr@google.com> |
Talkback improvements for Settings screens. Bug: 21164141 Change-Id: I7444261ccf967f6db70c9fe44a00bd3f19ceb975
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
ff41a9a5a6e307ca6dcbc45361854b5ac4e59857 |
|
10-Jun-2015 |
Jorim Jaggi <jjaggi@google.com> |
Animations/success state for external confirm device credentials (2/2) Bug: 20929186 Change-Id: I4489dd37f1148fb03315ec337a546eee04660cb5
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
4458fd6e57e39a8008a2d7de4014357288c134cb |
|
03-Jun-2015 |
Xiyuan Xia <xiyuan@google.com> |
Use accessibilityLiveRegion for ConfirmLockPassword/Pattern errorText - Revert previous "Add announceForAccessibility to ConfirmLockPattern"; - Add android:accessibilityLiveRegion="polite" for errorText in ConfirmLockPassword/Pattern; Bug:20282779 Change-Id: I4b9c0d461d0dd0504bd88a8a2144e09a42d5f64e
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
b5746cb19bef50036eae2353714bc50ff491ba68 |
|
27-May-2015 |
Andres Morales <anmorales@google.com> |
Merge "[LockSettings] pipe through HW throttle timeout" into mnc-dev
|
91e6c499ca8f33cc093fed4277d2b48ab780b309 |
|
16-May-2015 |
Andres Morales <anmorales@google.com> |
[LockSettings] pipe through HW throttle timeout Bug: 21118563 Change-Id: I23f5af2ebef9dac981281fb04c055a02f3b159b8
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
4f8102d4f2ef6057b5a8328d7eb7858f1ec4a2c8 |
|
21-May-2015 |
Xiyuan Xia <xiyuan@google.com> |
No auto soft keyboard when fp is in use Bug:20861013 Change-Id: Ia788e4c5dbabef374d08c7cb063ef2c07bbdb078
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
4a8edaf8b0b2f9313739ad434c3f409ac037f990 |
|
20-May-2015 |
Xiyuan Xia <xiyuan@google.com> |
Do not show soft keyboard when locked out - Remove stateVisible for ConfirmLockPassword activity so that soft keyboard does not auto show up when the activity starts; - Programatically show/hide soft keyboard when ConfirmLockPassword activity window gains focus; Bug:20542149 Change-Id: I3faa20312d2d25752bd35b70dc8ed785e7687f0a
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
f2c2c19339b5d821cb6196911cee04dc9ac647ad |
|
15-May-2015 |
Xiyuan Xia <xiyuan@google.com> |
No input instead of disabling password/pin entry So that the keyboard does not come and go all the time. Bug:21271425 Change-Id: If73109fca1417c43307dc6069307789031ffc607
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
bf9ac6b4fb6428d0194a5163181b30cccaedb8eb |
|
06-May-2015 |
Xiyuan Xia <xiyuan@google.com> |
Migrate settings UI to use async security check Bug: 20697812 Change-Id: Ieb0090ddb61198a60abb1e34ff9c6e8476c33789
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
5437588abd69bf3eff59684528aaf50e09b6cffc |
|
17-Apr-2015 |
Adrian Roos <roosa@google.com> |
Require explicit userId in LockPatternUtils Bug: 18931518 Change-Id: Ie2faa18918aaadf17a84287898438549a693b0cc
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
59f5976e15699df713369564c92cda3941f74dce |
|
17-Apr-2015 |
Andres Morales <anmorales@google.com> |
Unbreak CC screen Re-add logic in authenticationSucceeded Change-Id: Iac1925f5e2f2f67dd5d7c7f5d454f32691d51b61
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
e29dae683e8334c18d1449fca3b0e27bc5ff7aaa |
|
14-Apr-2015 |
Andres Morales <anmorales@google.com> |
Request enroll or verify lock before FP enroll Also pipe through challenge token Change-Id: I9d6afdbadf3832aeeb18a0b5a9620277e2070872
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
6609b0c22ae89a24d1b07dc3c4143452616d4450 |
|
13-Apr-2015 |
Andres Morales <anmorales@google.com> |
pipe auth token through confirm and set password ConfirmDeviceCredentialsActivity and ChooseLockGeneric now understand CLSH.EXTRA_KEY_HAS_CHALLENGE and CLSH.EXTRA_KEY_CHALLENGE in their launching intents. If present, they return a hw_auth_token_t verifying the challenge passed in as a field in keyed by CLSH.EXTRA_KEY_CHALLENGE_TOKEN in their result intents. Change-Id: I0b4e02b6a798a9e57d02522880a180dffadfcde1
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
8a09b619aeb233e2aab1919301f162d8acf1f0f0 |
|
07-Apr-2015 |
Jorim Jaggi <jjaggi@google.com> |
Update confirm device credentials to spec, add fingerprint - New strings in the screen. - New layout/style. - Clean up internal API's around it. - Add fingerprint support if launched from externally - Separate theme if launched from externally - If launched from above Keyguard, use SHOW_WHEN_LOCKED flag Change-Id: Icdf9bf9e0506841f24e8aab5f0f1d1f4b688951f
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
8a963babe2e36b7a41f77b8d2598c97658196e58 |
|
20-Mar-2015 |
Chris Wren <cwren@android.com> |
log visibility of views Depends-On: I5b1dccb5d103ece3112acf38889bae16273b092f Change-Id: I116aed2bb805f723a5bf2ec9eb94257de0b4a7b5
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
3ea423ae0ff56d249b6844b3a68c67ee5eba243d |
|
16-Oct-2014 |
Svetoslav <svetoslavganov@google.com> |
User to confirm credentials if an accessibility service changes encryption. When an accessibility service is enabled we are not using the user secure lock when encrypting the data. If the latter is already used for encryption we are decreasing the encryption level and therefore shall challenge the user with their secure lock. bug:17881324 Change-Id: If8905c05e20bc6bb6a6415e501871e5ad83f3d86
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
0cb467afe12c675fdfe4f349f83dd2bc4fe7cf79 |
|
09-Sep-2014 |
Jorim Jaggi <jjaggi@google.com> |
Keep unlock attempt count after configuration change Bug: 17416448 Change-Id: I79839a5e8020b184dd8928b47fc018d5209988ed
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
204440427aa198a836d55418060759a1e964abcc |
|
07-Jul-2014 |
Paul Lawrence <paullawrence@google.com> |
Don't put credentials in results from externally accessible activities ConfirmLockPattern and ConfirmLockPassword return an intent that contains the password, and as such are dangerous. Create internal versions that are locked down, and don't put this info in the externally accessible versions. Bug: 13741939 Change-Id: I0df4d1e720b3c33d2c9ca086636dc54f17b19bf0
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
15826d4ea1428b3d1edb86866ca57a93c2252bda |
|
13-May-2014 |
Fabrice Di Meglio <fdimeglio@google.com> |
Mode code cleaning: remove obsolete references to EXTRA_NO_HEADERS - the EXTRA_NO_HEADERS flag as no more meaning as we are showing the Tiles (previously named "Headers") only in the Dashboard (which is the main Settings screen) Change-Id: I55656de0d28ca9c84adbe6647d870838b4ac230b
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
d71c31ef946b35f73a0dded0a32c6ad6afc12227 |
|
03-Apr-2014 |
Paul Lawrence <paullawrence@google.com> |
Allow encryption when keyguard is set to pattern or no protection Don't block based on keyguard type, and pass type to encryption function. Circular dependency on https://googleplex-android-review.git.corp.google.com/#/c/444200/ Bug: 13749169 Change-Id: Ica95713adca9552ae56341ff33badd1d4b748af8
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
5de92cca6f79caa6ba48fe38a062099d63e5ae06 |
|
03-Apr-2014 |
Adrian Roos <roosa@google.com> |
Merge commit 'e63ac36f' into master Add lockout after trying to enter PIN / Password too often Bug: 13647935 Conflicts: src/com/android/settings/ConfirmLockPassword.java Change-Id: I0bf69d6d7fa8d5be9ad0fb42fe500e0a377af53b
|
a52a37b0fe17109877abbc25943d0d74232f3e5f |
|
03-Apr-2014 |
Adrian Roos <roosa@google.com> |
am 1b0b38cf: am 5d3c8c89: am 90630f6a: am 09235d10: am 82b3e62a: am 4692a48c: am c4bfea20: am 3f38173f: am 3a7690b1: am 8184ea52: Add lockout after trying to enter PIN / Password too often * commit '1b0b38cfeb54638899ddab48ff9198590f951a55': Add lockout after trying to enter PIN / Password too often
|
3f38173fadc1423d4c36b265a2ab5fdc09d88271 |
|
03-Apr-2014 |
Adrian Roos <roosa@google.com> |
am 3a7690b1: am 8184ea52: Add lockout after trying to enter PIN / Password too often * commit '3a7690b157c100f3a36b6fdc2578a12845875e06': Add lockout after trying to enter PIN / Password too often
|
8184ea524519a67b1284266844e6e186f3a74cab |
|
31-Mar-2014 |
Adrian Roos <roosa@google.com> |
Add lockout after trying to enter PIN / Password too often Enforce the same lockout that is already enforced when entering the pattern. Bug: 13647935 Change-Id: Ia60a2235ad526c293b7a8d5600f406f187004df7
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
263bcc8b732dbb47d3ce63904e0e05191fabbad6 |
|
18-Jan-2014 |
Fabrice Di Meglio <fdimeglio@google.com> |
Use Drawer in Settings app - get rid of PreferenceActivity as much as we can and use fragments instead - add Drawer widget - add Dashboard high level entry into the Drawer (but this is work in progress and would be done in another CL) - add bypass of fragment's Header validation when launched from the Drawer but *force* validation if external call thru an Intent Be aware that WifiPickerActivity should remain for now a PreferenceActivity. It is used by SetupWizard and should not trigger running the SettingsActivity's header building code. SetupWizard is a Home during the provisionnig process and then deactivate itself as a Home but would make the Home header to appear in the Drawer (because momentarily we would have two Home). Also, verified that: - the WiFi settings still work when called from SetupWizard - when you have multiple Launchers, the Home header will appear in the list of Headers in the Drawer Change-Id: I407a5e0fdd843ad7615d3d511c416a44e3d97c90
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
a677ee210c67d13d15ba0663887675bda16354d8 |
|
26-Jul-2013 |
Amith Yamasani <yamasani@google.com> |
Whitelist fragments appropriate for an activity Change-Id: If4f8c4e9d9949b652946cffe0ebb09b587e5a042
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
eef72c39ae83697b1beaa148ec56aced67382fec |
|
04-Oct-2012 |
alanv <alanv@google.com> |
Announce dynamic content changes in lock confirmation settings. Also re-orders updateStage() and setText/Selection calls so that text events don't flush announcements. This does not change functionality. Bug: 7256500 Change-Id: I8b10d66e9f73c7a630a8c3c5128372e18f26234c
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
0e88f4dd19a80e9e4d759595439773fb3e1f0c50 |
|
03-Jun-2011 |
Brian Carlstrom <bdc@google.com> |
Bulletproof CredentialStorage state handling As noted by the class javadoc, CredentialStorage has seen the number of cases to cope with grow. This change tries to address those cases. src/com/android/settings/CredentialStorage.java Added ChooseLockSettingsHelper.EXTRA_KEY_PASSWORD to coordinate additional producer and consumer. constant declaration here, since its used by callers of ChooseLockSettingsHelper.launchConfirmationActivity src/com/android/settings/ChooseLockSettingsHelper.java old producer src/com/android/settings/ConfirmLockPassword.java new producer (CredentialStorage wants passwords and patterns) src/com/android/settings/ConfirmLockPattern.java new consumer src/com/android/settings/CredentialStorage.java old consumer src/com/android/settings/CryptKeeperSettings.java Made class final and removed protected from method to make it clear ChooseLockSettingsHelper is not to be used by subclassing. src/com/android/settings/ChooseLockSettingsHelper.java Change-Id: Ib2d65398fe44573168a6267a0376c3b0388b16c8
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
29c9073595e7ab25a4528d14873bb88627a48135 |
|
19-Apr-2011 |
Jim Miller <jaggies@google.com> |
Fix 3402408: Manage "continue" button in ConfirmPassword screen This disables the "continue" button until the user has entered at least one character. Change-Id: I3192e1789ba89031ac4cc90f388b32b7af19a445
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
74b1e0a7330af195621ad0965748bee66c46f4b6 |
|
16-Apr-2011 |
Jim Miller <jaggies@google.com> |
Fix 4283049: Restore continue/cancel buttons in LockScreen Settings This fixes a bug where the continue/cancel buttons were missing from LockScreen settings in landscape mode. The change also includes a minor change to enable using the IME enter key to proceed to the next step. Change-Id: I2dca0b40e38a128cc0aa637f573da01e779edb73
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
025269df25d6094454a638c6f5eed0397580479c |
|
09-Mar-2011 |
Jim Miller <jaggies@google.com> |
Fix 3510307: Hide PIN passwords in ConfirmLockPassword Change-Id: I9389cc37f013fe027df7a0eb0035fc0db8678792
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
3e8b76319d34e2e96819ec9e62d4f19ee7d4e2b4 |
|
17-Jan-2011 |
Jason parks <jparks@google.com> |
Encrypt inplace settings. Change-Id: I5b9cb94c987dedecf3bf31cb67a42e2f24866d3b
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
7da8cae44b622518fbffd6d265f291c39e9fc722 |
|
07-Jan-2011 |
Jim Miller <jaggies@google.com> |
Fix 3281395: Fix duplicate title in LockScreen Settings. [DO NOT MERGE] Manual merge of Change-Id: I3c53d1864e521f4245b94d39664266891a728615 Change-Id: I59eedd81af226949ac0df10390ae0642e1812c5a
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
9757e30dfa0ab691c4c15366568367e166071a7d |
|
18-Dec-2010 |
Jim Miller <jaggies@google.com> |
Fix 3281395: Use breadcrumb area to display title for LockScreen Change-Id: Icd631b4c70e7b9f6b9a8c24dd513aed259a22d6a
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
2e28acedc623527aa5e84ba66635700d6547569a |
|
15-Dec-2010 |
Jim Miller <jaggies@google.com> |
Fix 3148496: Update LockScreen layouts on large device This updates the layouts to conform to the latest UX spec on large devices and fixes a bug where the IME shown for PIN selection was the QWERTY keyboard. Change-Id: Ib9f0b1631f11c8eff6898bfff9447d3dad75cc42
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
17e9e1933055b207473b488595b2887bfcaea32e |
|
08-Dec-2010 |
Jim Miller <jaggies@google.com> |
Fix 3148496: Initial pass at fragmentizing lockscreen settings. This converts most of the existing activities to fragments and wraps them in PreferenceActivities so they can be launched as before (e.g. by a DevicePolicyManager) Upload after sync/rebase. Change-Id: I4f351b75d9fca0498bcb04b4e11ff3b70765a4ba
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
57fbf694a53afb9c1924d81272179dceb3acfa4d |
|
28-May-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
Change I546ee2fb: Fix 2677197: Adding minimum complex character support. Change-Id: I5590ec2743b84e34098871507dbcc2f49e5a4e9f
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
af366a3ed66dcb3c3ecb1dd101e5d8869b518598 |
|
26-Mar-2010 |
Jim Miller <jaggies@google.com> |
Fix 2535700: Add support for enforcing password quality Change-Id: I908b4229d46061f3d450adec72b04276fe10afc1
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
122b6c85a9bc7076eacc388142f8c4fccc5462c9 |
|
11-Feb-2010 |
Jim Miller <jaggies@google.com> |
Fix 2332563: Update logic for lockscreen in Settings.
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
2f9dbcb49174d85218dd18e3b2097d3b9fc789c7 |
|
10-Feb-2010 |
Jim Miller <jaggies@google.com> |
Fix 2373088: Update SecuritySettings with new layout and minor logic tweaks.
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
47d380f1e6c823cea444004cb799d4c791145cc6 |
|
20-Jan-2010 |
Jim Miller <jaggies@google.com> |
Fix 2385283: Add DevicePolicyManager calls to LockScreen.
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|
00d2476d8fc122b4eef59d6be6f7aa41e9c56fde |
|
23-Dec-2009 |
Jim Miller <jaggies@google.com> |
Fix 2332563: Add password-lock support to lockscreen
/packages/apps/Settings/src/com/android/settings/ConfirmLockPassword.java
|