| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 20697812
Change-Id: Ieb0090ddb61198a60abb1e34ff9c6e8476c33789
|
|
|
|
|
| |
Bug: 18931518
Change-Id: Ie2faa18918aaadf17a84287898438549a693b0cc
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: Ia98b93d1cdb8c2d0bff42de7ecb59f5b80fb780e
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
| |
Depends-On: I5b1dccb5d103ece3112acf38889bae16273b092f
Change-Id: I116aed2bb805f723a5bf2ec9eb94257de0b4a7b5
|
|
|
|
|
|
|
| |
There is absolutely no advantage to doing this.
Bug: 18817878
Change-Id: Ibb386696e67c316e65f53c28f9249ef2a2a48db6
|
|
|
|
|
|
|
| |
Follow-up to I6f369eb60f8f6bb1e33384cd06534c713ab52e79
Bug: 18931518
Change-Id: I311b255a034b0cec8fee70b0f4938e6ebb20d95e
|
|
|
|
|
| |
Bug: 18931518
Change-Id: I5da41908b1d6895a69f981e139f2d268327fafcd
|
|
|
|
|
|
|
|
| |
Use setup wizard nav bar buttons instead of custom button bar for
lock screen setup.
Bug: 18482708
Change-Id: I471f475ebe6bc7ba8cfbd179daddd854c1b6982a
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Only show when going from an insecure to secure lock.
Bug: 18467783
Change-Id: Ia73682d45b1dcd9ad61a00abeac099a94256e3b7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Fixes bug 17881324
Change-Id: I3f256f448a35cf8104ee6acb4de253874101f7c0
|
|
|
|
|
| |
Bug: 17610563
Change-Id: Ibb51889fc8085f8fad5e36481af2419576cda34a
|
|
|
|
|
| |
Bug: 14437890
Change-Id: I54cf355242375e8c7968c7d27c441fbd0a54cef2
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: If4f8c4e9d9949b652946cffe0ebb09b587e5a042
|
|
|
|
|
|
|
|
|
| |
When adding a new restricted profile, user must enter some lockscreen
security. For PIN/password, return the result code (instead of cancelled)
so that UserSettings can proceed with adding the profile.
Bug: 8909229
Change-Id: I3567d7dfac869e38762f9e2a45d8ec83c51fa657
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
This fixes http://code.google.com/p/android/issues/detail?id=35988
Change-Id: I1880d7e41028f034e75a048226cce3bf96845a09
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Bug: 5443781
Change-Id: I599ccbb9c535396e05a2a22ab6d3ef302fb9c623
|
|
|
|
|
|
|
|
| |
Bug: 5422788
Converted the runnable to a message and removed any pending messages in onPause.
Change-Id: I048413ae2abd69a359b1fa2c648d98df3c3ae343
|
|
|
|
|
|
|
|
|
|
| |
This is done when the backup lock is complete or canceled.
If successful, the permanent gallery is replaced with the new one.
The temporary gallery is always deleted
Also deletes the main gallery if the lock type is changed from facial recognition
Change-Id: Id7b066fd852c7ba188d6e46b47391a362cbab40f
|
|
|
|
|
|
|
|
| |
This adds a simple biometric sensor (face lock) to the security choices.
Updated to disable biometric sensor by default.
Change-Id: I088e5e99cf5f8c7a06a1a992a9257940eb2cc07f
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: I5828dc0127b0296d87bdc0c9e251fd9c9a92bd0d
|
|
|
|
|
|
|
| |
This configures the password entry EditText to numeric password mode
to hide PIN entry characters.
Change-Id: I0e97210f6499c6557c1f0e9e861559a5f8ac1f07
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the above bug by allowing the PIN and password
screens to shrink to reveal the continue/cancel buttons
when the IME is shown.
This also fixes a minor resource bug where the title was
showing "confirm your password/pin" instead of "choose your password/pin".
Change-Id: I610c6018085e0c4ef1b6dc384566d06d1211f8ea
|
|
|
|
|
|
| |
Manual merge of Change-Id: I3c53d1864e521f4245b94d39664266891a728615
Change-Id: I59eedd81af226949ac0df10390ae0642e1812c5a
|
|
|
|
| |
Change-Id: Icd631b4c70e7b9f6b9a8c24dd513aed259a22d6a
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: I1eb96e3b88a368f1d92acdf71974fcd8fda1caab
|
|
|
|
| |
Change-Id: I5590ec2743b84e34098871507dbcc2f49e5a4e9f
|
|
|
|
| |
Change-Id: I6198833e099ec1f33309dc26b28e0fd4a6edb288
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: I908b4229d46061f3d450adec72b04276fe10afc1
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes a bug where the system was defaulting to 8 digits max password length.
The UI is best for N <=12, but works for more. I set the default limit to 16 which is
more than most humans can remember. That also seems to be the practical limit for the small
sample of DevicePolicyManagers I checked.
DevicePolicyManagers can always specify more digits if they really want.
Change-Id: I8637e0c9366800886759424b5a28f48dca15c535
|
| |
|
| |
|
|
|
|
|
|
|
| |
This introduces a new activity for changing the password, which takes
care of launching the correct password activity based on the caller's
request and active policy. The security settings activity now uses
this, and it implements the API action for launching the password UI.
|
| |
|