Instead build a list and set it on the main thread to avoid
concurrent modification crashes.
Change-Id: I936fbeb70359583e55ae8ddcb0ea46b5753cb3b0
Fixes: 28794277
am: 9579274cda
* commit '9579274cda38c552b43febe0980f0ec6bd07277d':
Hide work profile key in user credentials screen
Change-Id: I1b0b50a5ff0cc8dd0bef132ac63790c677bba188
Now uses colorPrimary as its background color and sets colorAccent
directly. Some other mild cleanup as well.
BUG: 28760785
Change-Id: Ib8e5140b789449e518b498bc49438cb4a2bc6451
Previously the values were hardcoded. Now the default value
for left and middle are colorAccent. Also updated SummaryPreference
to not call LinearColorBar.setColors unless its own setColors is called.
BUG: 28760785
Change-Id: Id28e809e6b5f0f6508258c995d5dcfacbc9c8725
This theme is at least used by the Phone Status activity and probably
others as well.
BUG: 28760785
Change-Id: If3faa84ad9d291f007c7191f1c0dba8d98fe9bf8
The settings dialogs were all using the default colorAccent.
Now it uses the app's version.
BUG: 28760785
Change-Id: Ic9bf90745db7d2ef5b1fd047474bab5c6bbdab23
The current pngs are hardcoded to the green accent color.
Instead, the new vector drawable replacements have colorAccent
set as a tint.
BUG: 28760785
Change-Id: I01853d4e93bca6651460ad86505d0943dc68bf93
The first implementation simply had every file in the Downloads folder
be under a single checkbox. This iteration makes Downloads an
expandable dropdown preference listing every single file individually
for selection to be deleted.
Bug: 28621781
Change-Id: I5169caf718cee4c0fa7f0248bc4c443984766005
Introduces stock colors (primary_color, primary_dark_color, etc) to allow
overriding the colors via resource overlays.
Creates new colorSecondary attribute and updates switches to use theme
attributes for foreground/background colors rather than hardcoded values.
Some other mild color cleanup to make things more straightforward.
BUG: 28760785
Change-Id: I4deba962357217bdb2e08c08e8f83b9b57a683d4
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
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: b0054ec4e2
* commit 'b0054ec4e2275d8d0444b94c0560374630e077f6':
Fix Continous loop in unifed screenlock when trying to Trust a CA cert
Change-Id: I01cd2b287d78484c1653476b75b6d300dec0c34d
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: f8265a8f1e
* commit 'f8265a8f1ed751d93ef15596658b82748d2a8d28':
Defined help page for Data Saver.
Change-Id: I1430270ab4ac368a6909038ad90816ba67e1d664
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
