Modify the back stack and result code propagation in the screen lock
scenarios.
- EncryptionInterstitial now propagates the result of ChooseLock*
request instead of always returning RESULT_OK.
- ChooseLockGeneric now treats CHOOSE_LOCK_REQUEST and
ENABLE_ENCRYPTION_REQUEST the same (since encryption can be a proxy
for ChooseLock*). This means ChooseLockGeneric will now stay on
back stack when going back from ChooseLock*, just like the case
(indirectly) through EncryptionInterstitial.
Bug: 26177240
Change-Id: Id7f1256dcbff00d552a3e7db60c285f53f1e63e6
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
This adds an optional overlay to specify a per-device
movie to illustrate enrolling a fingerprint. To enable,
create a new layout overlay for
fingerprint_enroll_find_sensor_graphic.xml using
FingerprintLocationAnimationVideoView
Fixes bug 22954305
Change-Id: I59294f71617ecf7a9bf09603fc0b068cc5aa8ff9
provided ConnectionManager method to do that, instead of changing
it directly using Settings.Global.putInt() - because that doesn't
case ACTION_AIRPLANE_MODE_CHANGED intent to be broadcast.
This breaks Google Search App (GSA) code that relies on the above
broadcast to do a variety of things.
Change-Id: I2aa61643ed23b373aa362a59af83427a4548c492
For settings disabled by user restrictions show
the user a lock icon and allow them to click to
find more info.
Bug: 22543585
Change-Id: Ie8b02ac26f2b22db386a9044f3c6570098f6e14b
L10N team requested that the text might not fit within the
CHAR_LIMIT=35 in some languages. Rather than increasing the limit,
I think it's better to simplify the original text so that
its translations are unlikely to break the limit of chars.
Bug: 26123263
Change-Id: If9b338d2f051c161a71e8b20c9526be2d10e0cc1
Also cleans up unnecessary 0s and moves tint to the proper place in
relevant vector drawable XML files.
Preview layout is still WIP pending UX input, but I wanted to get this
CL in place so that we can test/demo the feature ASAP.
Bug: 22450672
Change-Id: Ic3f1500006c763df99fba2d1d16782b89d6fcae1
'bugreportplus' is more user-friendly (it shows a system notification
with the progress, allow user to cancel, etc...), at the cost of
consuming more resources. As such, the "Take Bug Report" UI will be
changed to offer the user a combo with these 2 options, but for now it's
always going to be 'bugreportplus'
BUG: 26034608
Change-Id: Idbb325fe7cd18e487197b2fb79cfc264e9859570
The old way was garbage-heavy. To add to that some changes to the way
PreferenceScreens are redrawn was leading to some artifacts with items
fading in/out every tick.
Bug: 25588385
Change-Id: Idabf7546ab519bf196ad3b8582caa2ec6bf9e084
