summaryrefslogtreecommitdiffstats
path: root/src/com/android/settings/ChooseLockPattern.java
Commit message (Collapse)AuthorAgeFilesLines
* Settings: use the actual user id to set pattern sizeScott Mertz2016-04-141-1/+1
| | | | | Ticket: CYNGNOS-2462 Change-Id: I1af2b69dabdc0aa010edb354c6274af57b442618
* Settings: allow rotation while setting new patternRoman Birg2015-12-111-6/+10
| | | | | Change-Id: I0fc9a7df686b8af0c60edf1916dc6fe02185f704 Signed-off-by: Roman Birg <roman@cyngn.com>
* Settings: forward port lock pattern grid size (2/2)Michael Bestas2015-12-111-12/+27
| | | | Change-Id: I7078d703c218cd096d9b77c003a94b52fbce6322
* Fix wrong stage exception in ChooseLockPatternXiyuan Xia2015-09-011-2/+2
| | | | | | | | ChooseLockPattern should updateStage instead of always enabling pattern view input. Bug:22760251 Change-Id: I3675c0aada293e168769147ba8e4203e9310e593
* Fix ChoosePat/Pin/Pwd crash from async taskXiyuan Xia2015-08-271-80/+87
| | | | | | | | | | Use a retained worker fragment to track the asynchronous save-and-finish task so that ChoosePattern/Password activity is properly dismissed after a configuration change. Bug:23424884 Bug:23521530 Change-Id: I328022c1603cfb0f6812cd8aa7916ae7b72c9950
* Gray out confirm button on pattern/pin/password set dialogPaul Lawrence2015-08-111-23/+35
| | | | | | | | | | | | | Setting a pin/pattern/password can take a second. Gray out the confirm button to avoid multiple submissions. Note that this requires async tasks so that the button is shown as gray in a timely way. Also don't add another stage - this causes a11y to repeat the title. Bug: 22882174 Change-Id: Ib8047fde9e12afa25e82ebfa3a1e799a4b7043f2
* Always announcing wrong pattern now for talkback in pattern settingsSelim Cinek2015-06-251-1/+4
| | | | | Bug: 21797216 Change-Id: If86078f2d711a80e4a4aa28ce8817aed8244d30b
* Enforce Keyguard policy in Notification SettingsAlex Chau2015-06-181-2/+8
| | | | | | | | | | | | | | | | | | | - Applied getKeyguardDisabledFeatures for notification settings and notification setup page (after settings a screenlock) - If a notification settings is disabled, the next least secure setting will be chosen - Although KEYGUARD_DISABLE_UNREDACTED_NOTIFICATIONS can be set be profile, it will not be reflected in both settings page. This is because it does not affect the owner (user 0), as mentioned in DevicePolicyManagerService.PROFILE_KEYGUARD_FEATURES_AFFECT_OWNER - Skip RedactionInterstitial if there is <= 1 options for the user - Tested with both Setup wizard and settings case, both pattern and password, as well as toggling the policy on and off Bug: 19307118 Bug: 17099898 Change-Id: If640d5576caa0163e9942569f7b4643a30bbfe0a
* Fix lockpattern weirdnessJorim Jaggi2015-06-041-11/+10
| | | | | | | | | - Pass back correct result when pressing cancel. - Make sure the start the interstitial activity after checking so we don't preempt the async thread we are still running. Bug: 21621918 Change-Id: I5558089abf02a00a268050fc48894cea86692fa0
* [LockSettings] pipe through HW throttle timeoutAndres Morales2015-05-261-1/+8
| | | | | Bug: 21118563 Change-Id: I23f5af2ebef9dac981281fb04c055a02f3b159b8
* Migrate settings UI to use async security checkXiyuan Xia2015-05-131-5/+50
| | | | | Bug: 20697812 Change-Id: Ieb0090ddb61198a60abb1e34ff9c6e8476c33789
* Require explicit userId in LockPatternUtilsAdrian Roos2015-04-281-5/+7
| | | | | Bug: 18931518 Change-Id: Ie2faa18918aaadf17a84287898438549a693b0cc
* pipe auth token through confirm and set passwordAndres Morales2015-04-141-3/+26
| | | | | | | | | | 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-2/+27
| | | | 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
* log visibility of viewsChris Wren2015-03-271-1/+7
| | | | | Depends-On: I5b1dccb5d103ece3112acf38889bae16273b092f Change-Id: I116aed2bb805f723a5bf2ec9eb94257de0b4a7b5
* Settings: Remove all unused imports.John Spurlock2015-03-181-2/+0
| | | | Change-Id: Iebfa52cb849d69974c94902b0b020893cf5618a3
* Remove usages of LPU.savedPatternExistsAdrian Roos2015-01-091-1/+0
| | | | | | | | | | The correct method to call is isLockPatternEnabled, which also checks whether we've actually selected a pattern. Also removes the code for the obsolete pattern enabled setting. Bug: 18931518 Change-Id: I6f369eb60f8f6bb1e33384cd06534c713ab52e79
* Purge biometric weak from internal codeAdrian Roos2015-01-071-6/+2
| | | | | Bug: 18931518 Change-Id: I5da41908b1d6895a69f981e139f2d268327fafcd
* [FRP] Notification screen slides in wrong directionLucky Zhang2014-12-111-3/+3
| | | | | | | | | | | | | | The method that launches notification screen from choose lock activity finished the original activity before starting the new activity. This made the system think it is a backward transition instead of a forward one. Swapping the order to start new activity first and then finish old activity fixed the problem. This also changes the behavior in settings. However, it seems like this is also the desired behavior for settings. Bug: 18723199 Change-Id: I90538fa52e0d62a2274c8e0333682035849802c6
* Merge "Fix race leading to spuriously disabled trust agents" into lmp-mr1-devAdrian Roos2014-12-051-1/+1
|\
| * Fix race leading to spuriously disabled trust agentsAdrian Roos2014-12-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | If TrustManagerService is able to refresh the trust agents before the Settings activity gets a chance to reenable the lock pattern, the TrustManagerService won't see a secure credential and won't load any agents. This was introduced when we switched to isSecure instead of getKeyguardStoredPasswordQuality. The latter ignored the lockPatternEnabled flag. Bug: 18596036 Change-Id: I2734899f7684916fc84bc3a07edca29310887103
* | [FRP] Use setup wizard nav bar buttonsMaurice Lam2014-12-041-36/+52
|/ | | | | | | | Use setup wizard nav bar buttons instead of custom button bar for lock screen setup. Bug: 18482708 Change-Id: I471f475ebe6bc7ba8cfbd179daddd854c1b6982a
* [FRP] Theme interstitials for lock screen setupMaurice Lam2014-12-011-1/+5
| | | | | | | | | 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] Theming for Pattern and Password screensMaurice Lam2014-12-011-4/+10
| | | | | | | | | | | | 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
* Don't show RedactionInterstitial when changing passwordAdrian Roos2014-11-241-1/+5
| | | | | | | Only show when going from an insecure to secure lock. Bug: 18467783 Change-Id: Ia73682d45b1dcd9ad61a00abeac099a94256e3b7
* Several fixes to new EncryptionInterstitial dialog.Jim Miller2014-10-171-0/+15
| | | | | | | | | | | | | | | | | 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
* Add a checkbox option to 'require password to decrypt'Jim Miller2014-10-141-1/+2
| | | | | | Fixes bug 17881324 Change-Id: I3f256f448a35cf8104ee6acb4de253874101f7c0
* Prevent saving credentials multiple timesAdrian Roos2014-09-241-0/+4
| | | | | Bug: 17610563 Change-Id: Ibb51889fc8085f8fad5e36481af2419576cda34a
* Ask about redacted notifications after setting up a secure lockAdrian Roos2014-08-051-0/+2
| | | | | Bug: 14437890 Change-Id: I54cf355242375e8c7968c7d27c441fbd0a54cef2
* 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
* Use Drawer in Settings appFabrice Di Meglio2014-02-031-4/+2
| | | | | | | | | | | | | | | | | | | | - 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-1/+4
| | | | | | | | | | | 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
* Whitelist fragments appropriate for an activityAmith Yamasani2013-07-301-0/+7
| | | | Change-Id: If4f8c4e9d9949b652946cffe0ebb09b587e5a042
* Move lockscreen to using haptic feedback setting.Jeff Sharkey2012-10-101-1/+0
| | | | | | | | This removes lockscreen-specific "Vibrate on touch" setting, and changes it to use the haptic feedback setting instead. Bug: 7318772 Change-Id: Id6931903b3ebeca6aeacef9b127490a381cd40b4
* Announce dynamic content changes in lock confirmation settings.alanv2012-10-031-0/+7
| | | | | | | | 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
* Adding an improve face matching settings option for Face UnlockDanielle Millett2011-11-071-3/+0
| | | | | | | | | | | | | | | | | Adding an option which will launch a version of setup where faces can be added to the current gallery. It requires the user to first confirm their password before launching addToSetup. Patch 3 - Updated for renaming of FackLockTutorial to SetupIntro. Now it is called every time regardless of it it's showing the tutorial and a flag is passed in to determine whether or not SetupIntro shows the tutorial. Patch 4 - Removed 'Setup Complete' toast at the end of screen lock setups since it was primarily for Face Unlock and the congratulations screen removes the need for it. Change-Id: Idc5f960809d992ec7bbce59ef1e13b95ef7cce45
* Toast when finished pattern or password setup.Jeff Sharkey2011-10-131-0/+3
| | | | | Bug: 5443781 Change-Id: I599ccbb9c535396e05a2a22ab6d3ef302fb9c623
* Fix 5185505: Add weak biometric sensors to security choices.Jim Miller2011-09-081-1/+3
| | | | | | | | This adds a simple biometric sensor (face lock) to the security choices. Updated to disable biometric sensor by default. Change-Id: I088e5e99cf5f8c7a06a1a992a9257940eb2cc07f
* Fix 5044847: Minor tweaks to SecuritySettings.Jim Miller2011-08-071-1/+1
| | | | | | | Fix for 5044847 removes "Press menu for help" which is no longer used on any device. Fix for 5092312 removes black background from pattern/pin/password settings. Change-Id: I849ea0296aa9f0e9ace65086f9b154a961959f00
* Fix 3409373: Don't grey out Cancel button on confirm pattern screenJim Miller2011-02-141-1/+1
| | | | Change-Id: I5832fd92cb71c91239326b295c36d207286263f2
* Fix 3281395: Fix duplicate title in LockScreen Settings.Jim Miller2011-01-071-0/+2
| | | | Change-Id: I3c53d1864e521f4245b94d39664266891a728615
* Fix 3315401: Prevent pattern confirmation screen from asking twiceJim Miller2011-01-051-1/+1
| | | | | | | | This fixes a bug where changing from PIN to pattern caused the lock pattern tutorial to ask for the PIN twice and ultimately crash due to ConfirmLockPattern getting into the wrong state. Change-Id: Ia3b3186dcd56f2b47a09f54d7636436ee80aa13c
* Fix 3148496: Initial pass at fragmentizing lockscreen settings.Jim Miller2010-12-081-370/+395
| | | | | | | | | | 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
* Fix 2594148: confirm PIN/Password before resetting deviceJim Miller2010-04-141-1/+2
| | | | | | | | | This fixes a bug where user was allowed to factory reset the device without entering their PIN/Password. It also fixes the same issue with MediaFormat (Settings->SD Card->Format). Change-Id: I0677a50aa771ad8663513fd7ec398a70953dcde2
* Fix 2579923: Make changing lock screen method more discoverable.Jim Miller2010-04-111-4/+12
| | | | | | | | | | | | | | | | | | | This changes the organization of lock screen security settings to make choosing an alternate unlock method more discoverable. Instead of having to disable the old lock method to use a new one, the user now just has one set/change option in lock settings, with a list of method-specific setting below it. In addition, we ask the user to confirm their old credentials before prompting them to choose a new one, which eliminates one source of confusion. Also, ChooseLockGeneric now shows a UI if quality isn't specified. Any unlock method less secure than minimum specified by DevicePolicyManager (if active) is greyed out. Change-Id: Iecc6f64d4d3368a583f06f8d5fe9655cc3d5bd3b
* Fix 2332563: Add password-lock support to lockscreenJim Miller2010-01-111-62/+46
|
* Fix for 2137900: Be more conservative about poking the wakelockJim Miller2009-09-291-0/+5
|
* auto import from //branches/cupcake_rel/...@140373The Android Open Source Project2009-03-181-0/+7
|
* auto import from //branches/cupcake_rel/...@138607The Android Open Source Project2009-03-131-8/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-20 00:30:54 +0000