ConfirmDeviceCredentialBaseFragment.SHOW_WHEN_LOCKED has been abused.
We should not set onfirmDeviceCredentialBaseFragment.SHOW_WHEN_LOCKED
for work challenge and most other cases.
It's temp fix for the rotation bug. Because it's inconsistent the activity is shown
on top of keyguard with/without rotation (or any config change). In long term,
SHOW_WHEN_LOCKED should be set only if it's truly on purpose, and remove
isKeyguardLocked checking.
Bug: 28878075
Change-Id: I19db913f5bcaf2644c8c46c25e9584103d7fee8a
- Update settings to use GLIF versions for margins and styles
- Removed learn more link from AOSP Fingerprint intro screen because
it won't have a link to show.
Bug: 28885476
Change-Id: I5d2fd730a1bca2c5da8626da066da3a3f03b4428
am: 64b25588b7
* commit '64b25588b7aa1f377ffb1585c1a9f07c1705b7f0':
Materialize the button bar in the Deletion Helper.
Change-Id: Iece17635fc4c7a0ffd112381068b39a84bc3daeb
When trust button is clicked, if ConfirmCredential (CC) is shown,
and user successfully unlock CC, trust the cert immediately
Bug: 28752364
Change-Id: Ied4aeda59a668a9dd2bf079a385b1fecd8eabb9e
am: e8df0892d4
* commit 'e8df0892d427cd8eec0f43970e1241f8e42bc918':
Fix Continous loop in unifed screenlock when trying to Trust a CA cert
Change-Id: Iac21f081af2d0cbad3c1174134854cdbcc204ec6
am: b0054ec4e2
* commit 'b0054ec4e2275d8d0444b94c0560374630e077f6':
Fix Continous loop in unifed screenlock when trying to Trust a CA cert
Change-Id: I01cd2b287d78484c1653476b75b6d300dec0c34d
am: b0054ec4e2
* commit 'b0054ec4e2275d8d0444b94c0560374630e077f6':
Fix Continous loop in unifed screenlock when trying to Trust a CA cert
Change-Id: If02ac2e8ddb0438e3b96491686fcd57a646d5a1f
Older Android style buttons were used for the bottom button bar.
By changing them to use the buttonBarBottomStyle, they are updated
to flat buttons. The bottom button bar for settings preference
fragments now more closely tracks the Material Design spec as seen
here in [0].
The other Settings views which use the button bar buttons are the
Redaction settings and WiFi network picker in some contexts. These
should be unaffected as they are based on the SettingsActivity,
rather than the SettingsFragment, and inflate a different view.
[0] https://material-design.storage.googleapis.com/publish/material_v_8/material_ext_publish/0B7WCemMG6e0VaDdZWXpLXzNicjg/components_buttons_usage6.png
Bug: 28845586
Change-Id: I9ea55aa2fe1e76f8f952880675501cbb0f76719d
am: d21e63fe4b
* commit 'd21e63fe4b381354a2033bac1251f4152a7e14a3':
Defined help page for Data Saver.
Change-Id: Ie8761cd677ee5a14a92ba52419d1ee21dfa1befa
am: f8265a8f1e
* commit 'f8265a8f1ed751d93ef15596658b82748d2a8d28':
Defined help page for Data Saver.
Change-Id: I1430270ab4ac368a6909038ad90816ba67e1d664
am: f8265a8f1e
* commit 'f8265a8f1ed751d93ef15596658b82748d2a8d28':
Defined help page for Data Saver.
Change-Id: I8ee0281525ab7b606bec6262ac2b115cbe31ca2e
This was caused by a change I made to the extraInfo on the app.
The extra info used to be a long which was the last usage time.
I changed it to a UsageStatsState and missed this usage of it.
The attempted cast to long caused a crash.
Bug: 28885317
Change-Id: Ie0d6bcea5d0afccd2762acd19d628c742c7e3db9
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
