summaryrefslogtreecommitdiffstats
path: root/src/com/android/settings/ChooseLockGeneric.java
Commit message (Collapse)AuthorAgeFilesLines
* Lockscreen: Show redaction interstitial when swipe selectedd34d2016-02-021-1/+19
| | | | | | | | | | If the user is switching from a secure lock screen to an insecure one and they have chosen to redact sensitive/all notififcations, show the RedactionInterstitial so the user has the option to change this setting. Change-Id: I2bcfd01fb322eb66a10a0f29feb9da696c524cdf TICKET: YAM-103
* settings: Avoid an NPESteve Kondik2015-11-101-1/+2
| | | | Change-Id: I81281703ee590d0c9dc5961832c0195eccb3175f
* Merge tag 'android-6.0.0_r26' into HEADRicardo Cerqueira2015-11-051-7/+19
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Android 6.0.0 release 26 Conflicts: res/values-fr/strings.xml res/values-it/strings.xml res/values-ja/strings.xml res/values-nl/strings.xml res/values-pl/strings.xml res/values-ro/strings.xml res/values-ru/strings.xml res/values-zh-rCN/strings.xml res/values/bools.xml res/values/strings.xml res/xml/development_prefs.xml src/com/android/settings/DevelopmentSettings.java src/com/android/settings/DeviceInfoSettings.java src/com/android/settings/DisplaySettings.java Change-Id: I9fd9e793cf6097d950f8a1e30771c8bdf5067906
| * To hide none security option, use config_hide_none_security_option configSungmin Choi2015-09-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | Use mcc config overlay mechanism to hide none security option in countries where it is mandatory. To hide none security option, set config_hide_none_security_option config true as mcc config overlay. Bug: 22209425 Bug: 22975388 Change-Id: I774c53e17d3b50393816622134e58f8e06b76fab
| * Don't attempt to remove fp templates if none are enrolledJim Miller2015-08-211-1/+2
| | | | | | | | | | | | | | | | | | The code was blindly calling fpm.remove(0) to remove all fingerprint templates and then waiting for them to be removed. Fixes bug 23183484 Change-Id: Ie510097d85bba32d965ba3c7f324f6c042e08300
| * Wait with finishing until fingerprints are removedJorim Jaggi2015-08-121-6/+13
| | | | | | | | | | Bug: 22863210 Change-Id: I490157cc2f9b52ac87cc52e13c7eb57cb4a4a377
* | Clear traces of temporary stored password after updating passwordDinesh K Garg2015-10-061-0/+2
|/ | | | | | | | | | If HW accelerated FDE is in use, LockSettingService would store old password temporarily in memory untill password update is completed. Once password update is complete, it resets the old password. This change would additionally reset password everytime password update process is started and completed. Change-Id: I9a92b44678b023336a5d51b61c89cb102166de6c
* [Fingerprint] Help text for backup screen lockMaurice Lam2015-08-031-0/+15
| | | | | | | | | | | Show a help text saying "Choose your backup screen lock method" when asking the user for backup screen lock during fingerprint enrollment. A backup translation is specified, using the source string "Set up your backup screen lock method". Bug: 22879473 Change-Id: I9b9348141227103e695d1fc78601745cac0309a7
* Update FRP warning to specAdrian Roos2015-07-241-13/+22
| | | | | Bug: 22672924 Change-Id: Ie275d5099553539707f86bf0e8cec5d5022ad227
* [Fingerprint] Change message in encryptionMaurice Lam2015-07-201-0/+5
| | | | | | | | | | Change the message for encryption interstitial when enrollin fingerprint, to make it clear that fingerprint unlock is still used, just that the backup unlock PIN / password / pattern will be needed to start the device. Bug: 22559146 Change-Id: Ia134e0d9b118151833a9118ff44667dcc9122185
* No longer upgrade password quality based on keystoreChad Brubaker2015-05-121-10/+0
| | | | | | | | | Keystore no longer requires a password to operate and only deletes encrypted at rest entries when the user removes their password, so blocking password downgrade is no longer required. Bug: 20764363 Change-Id: I6f06acc71a4165282985082203ae1194491844c7
* Added support for DO_NOT_ASK_CREDENTIALS_ON_BOOT DPM flagAndrei Kapishnikov2015-04-291-1/+3
| | | | | | | | | | | | | | | When DO_NOT_ASK_CREDENTIALS_ON_BOOT flag is set in DevicePolicyManager, the Settings UI: 1) Should not encrypt the device with password when the user encrypts the device for the first time. The default encryption type should be used instead. 2) Should not give the choice to the user whether to encrypt the device with password/PIN or not but always encrypt the device without password. Related CL: https://googleplex-android-review.git.corp.google.com/#/c/665371/ Change-Id: Ic09f02c033a0b16b7ffc45bf6d675b62d1be4bd8
* Require explicit userId in LockPatternUtilsAdrian Roos2015-04-281-6/+8
| | | | | Bug: 18931518 Change-Id: Ie2faa18918aaadf17a84287898438549a693b0cc
* [LockScreenSetup] Start SUW-style screens in setup flowMaurice Lam2015-04-161-2/+2
| | | | | | | | | Implement the new overloaded methods in the setup-specific screens so that the SUW-styled screens will be started instead of the regular ones as seen in Settings. Bug: 20304053 Change-Id: I68e778e6421cfe08e20c9b4af9ed98e0f5ebcee1
* pipe auth token through confirm and set passwordAndres Morales2015-04-141-6/+33
| | | | | | | | | | 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
* [LockSettings] pipe old password through when setting new oneAndres Morales2015-04-131-3/+22
| | | | Change-Id: Ia98b93d1cdb8c2d0bff42de7ecb59f5b80fb780e
* Update confirm device credentials to spec, add fingerprintJorim Jaggi2015-04-131-1/+2
| | | | | | | | | | | - 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
* Merge "Allow none lockscreen with multiple users"Adrian Roos2015-04-081-13/+2
|\
| * Allow none lockscreen with multiple usersAdrian Roos2015-04-071-13/+2
| | | | | | | | | | Bug: 19962043 Change-Id: Ic7dcbd371d700bf8796f50469a7ac7d529ec491d
* | Merge "Show current screen lock as summary"Jason Monk2015-04-031-0/+28
|\ \
| * | Show current screen lock as summaryJason Monk2015-03-301-0/+28
| |/ | | | | | | | | Bug: 19819290 Change-Id: Iefdacd6b86f96e6f3577351e7f92b86217b1b7ad
* | Prepare to make Fingerprint API public.Jim Miller2015-04-011-3/+3
|/ | | | | | | | | - moved fingerprint support files into hardware area - moved jni into services/core Bug 16487912 Change-Id: Id111ee89771fc208a9365fd06c57b3dbf85b5356
* log visibility of viewsChris Wren2015-03-271-0/+6
| | | | | Depends-On: I5b1dccb5d103ece3112acf38889bae16273b092f Change-Id: I116aed2bb805f723a5bf2ec9eb94257de0b4a7b5
* Update Settings to use new fingerprint APIJim Miller2015-03-241-12/+17
| | | | | | Bug 16487912 Change-Id: I99ac78f476d43f6b87f5dd20e597c51ed08d2c0e
* Settings: Remove all unused imports.John Spurlock2015-03-181-7/+0
| | | | Change-Id: Iebfa52cb849d69974c94902b0b020893cf5618a3
* Merge "Add flag to hide disabled keyguard options."Jim Miller2015-03-121-10/+12
|\
| * Add flag to hide disabled keyguard options.Jim Miller2015-03-121-10/+12
| | | | | | | | | | | | | | | | | | | | | | | | Normally keyguard options are disabled by things like credential storage and device admins, so we show the reason in ChooseLockGeneric. However, in the case of fingerprint we want to limit the scope to just those options that have security (pin,password,pattern). Bug 19592835 Change-Id: I6832ff692bad538adeec2f2575fca4f8f04f40cf
* | Don't reset fingerprint storage on devices without fingerprint hw.Jim Miller2015-03-121-2/+2
|/ | | | | | Fixes bug 19707354 Change-Id: I26144dc855bff83cdc9c9544c8ab7449274d7b5e
* Implement additional fingerprint flows in Settings.Jim Miller2015-03-111-0/+28
| | | | | | | | | | | | | | | | | | | - new onboarding flow ("locate sensor") - changed sensor location image - changed in-app sensor icon - remove fingerprint animation since it caused people to want to tap on it. - remove enrolled fingerprint templates when switching back to "none" or "slide" - use real in-app icon for fingerprint - much improved layout - basic landscape layout working - added 250ms delay to final enrollment step so it's not so jarring - delete is now working - rename wired, but not functional yet Bug 19592835 Change-Id: Ie3e73a2fc8f834f1b90e2746c4cc841216aa6031
* Setup lock screen go back one screen at a timeMaurice Lam2015-02-121-19/+6
| | | | | | | | SetupChooseLockGeneric no longer finishes itself when it receives a RESULT_CANCELED result from an activity it started. Bug: 18631770 Change-Id: I892b76847904225fe607b9406d6e76f932daa062
* Purge biometric weak from internal codeAdrian Roos2015-01-071-104/+21
| | | | | Bug: 18931518 Change-Id: I5da41908b1d6895a69f981e139f2d268327fafcd
* [FRP] Remove None and Swipe from screen lock optionsLucky Zhang2014-12-051-3/+22
| | | | | | | | | | | | | | Removed "None" and "Swipe" from screen lock options in the choosing lock screen during setup wizard, because at this step, the user has already chosen to pick a screen lock, hence it's unnecessory to show "none" and "swipe". Implemented this by overriding the DisableUnusablePreferences in SetupChooseLockGenericFragment to disable the insecure lock methods and adding a flag to hide disabled methods for setup wizard. Bug: 18631416 Change-Id: I3feccf591da25bd6eadcc03c75b28cfc1d069db7
* Merge "[FRP] Theme interstitials for lock screen setup" into lmp-mr1-devMaurice Lam2014-12-031-3/+8
|\
| * [FRP] Theme interstitials for lock screen setupMaurice Lam2014-12-011-3/+8
| | | | | | | | | | | | | | | | | | Use the setup wizard theme for EncryptionInterstital and RedactionInterstitial as they will show during the lock screen setup as part of setup wizard. Bug: 18482708 Change-Id: I65c8924952345a4e17fcf4ffb7d68df53244c5d7
* | [FRP] Show FRP warning when disabling secure unlockLucky Zhang2014-12-011-23/+122
|/ | | | | | | | | Added a dialog fragment to display warning message about disabling device protection features when changing from a secure unlock method to an insecure one. Bug: 18509782 Change-Id: I0eaa9ff55c14092d8b3361d10da8b4530dd79bee
* [FRP] Theming for Pattern and Password screensMaurice Lam2014-12-011-7/+18
| | | | | | | | | | | | Basic theming for pattern and password screens. Create subclasses for ChooseLockPassword and ChooseLockPattern, and copied their XML layouts. This CL mainly uses the buttons in the original screens as-is, with a follow-up CL coming to change to use the nav bar buttons. Bug: 18482708 Change-Id: I81751f781de633aff23fc68657589360007c235a
* [Setup] Theme ChooseLockGeneric for setup wizardMaurice Lam2014-11-251-1/+6
| | | | | | | | | | | | | This is step one of theming the set-up lock screen flow to match the setup wizard theme. This shows the general approach of creating a subclass of both the activity and fragment and overriding methods to achieve the desired behavior for setup. ag/594000 is a much more comprehensive change for what the final change will look like. Bug: 18482708 Change-Id: Idff34937f39f46a0c488df2cae4c46155b80cab7
* Merge "Several fixes to new EncryptionInterstitial dialog." into lmp-devJim Miller2014-10-171-14/+19
|\
| * Several fixes to new EncryptionInterstitial dialog.Jim Miller2014-10-171-14/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code now observes whether accessibility is turned on when deciding the default state. Additionally, it fixes a bug where the user can back out of EncryptionInterstitial and leave the setting in a bad state. We now propagate the state until the place where it ultimately gets stored. Also fixes problem where Encryption was ignoring the state where the device was already encrypted. Fixes bug 17881324 Change-Id: Iec09e4464832a506bb2a78bb14a38b3531971fa0
* | Accessibility no longer overrides strong encryption (Settings).Svetoslav2014-10-171-0/+4
|/ | | | | | | | | | | Updating the accessibility layer behavior to reflect the new model where accessibility no longer overrides strong encryption. Now enabling an accessibility service lowers the encryption level but the user can bump it up in settings if desired. bug:17881324 Change-Id: Iaf46cbabf1c19c193ea39b35add27aaa4ff509e4
* Add a checkbox option to 'require password to decrypt'Jim Miller2014-10-141-5/+40
| | | | | | Fixes bug 17881324 Change-Id: I3f256f448a35cf8104ee6acb4de253874101f7c0
* Use default encryption password if an accessibility service is enabled.Svetoslav2014-09-301-0/+25
| | | | | | | | | | | | | If accessibility is on and the user selectes a secure lock we use weaker encryption to enable running accessibility layer at the time the user authenticates. This change adds a warning message to the enable accessibility service dialog if there is a secure lock and also adds a warning as a summary for the secure lock in the lock chooser activity. Both warning mention the weaker encryption to be used. bug:17671790 Change-Id: Ib5cc9d3a78f751e18362bb9238fd2804c3b600f8
* Add new "pin complex" type to supported keyguard PINsNicolas Prevot2014-07-091-1/+1
| | | | | | | | | | This adds a feature to allow DevicePolicyAdmins to prevent using simple PINs, which are defined as those containing more than 3 repeated values. Examples include '1234', '2468', '1111', '9876', etc. Bug 12081139 Change-Id: I68d8fe2459837cb5e083724e1740e65f0519f7e1
* Add Indexing and Search for ChooseLockGenericFragmentFabrice Di Meglio2014-05-231-2/+0
| | | | | | | | - clean some imports - add key and title to security_settings_picker.xml - add ChooseLockGenericFragment in SearchIndexableResources Change-Id: I867a1e11905cc4059d6eccabeab04d55cc3d799e
* Mode code cleaning: remove obsolete references to EXTRA_NO_HEADERSFabrice Di Meglio2014-05-131-1/+0
| | | | | | | | - 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
* resolved conflicts for merge of f90b5141 to masterElliott Hughes2014-04-241-2/+1
|\ | | | | | | Change-Id: I666b2fcde034f6dc9f7b69409facf88a4feb5309
| * Track MutableBoolean's new package.Elliott Hughes2014-04-231-2/+1
| | | | | | | | Change-Id: I96df3fcbc3b94186a36617dfc1df5b195880be13
* | Support default, pattern, pin and password encryption typesPaul Lawrence2014-02-111-35/+1
| | | | | | | | | | | | | | | | | | | | | | Use plumbing provided by dependant change to bring up correct dialog at boot time. Needs matching framework changes from https://googleplex-android-review.googlesource.com/#/c/412885/ Bug: 8769627 Change-Id: Ib04a2875e051a7cccca035fadb25978dfec22491
* | Use Drawer in Settings appFabrice Di Meglio2014-02-031-4/+1
|/ | | | | | | | | | | | | | | | | | | | - 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
* Make sure that external callers cannot pass in the confirm bypass extraAmith Yamasani2013-09-251-2/+8
| | | | | | | | | | | Security fix for vulnerability where an app could launch into the screen lock change dialog without first confirming the existing password/pattern. Also, make sure that the fragments are launched with the correct corresponding activity. Bug: 9858403 Change-Id: I0f2c00a44abeb624c6fba0497bf6036a6f1a4564