In order to avoid layering violation, LocaleList needs to be moved from
android.util package to android.os package [1]. This CL follows up that
package change.
No behavior change is intended.
[1]: Ia8de2ee9df3dd0a42b1fe84574439519b680fe18
Bug: 28819696
Change-Id: Ib331cc3a63f7a1e656573f032a1e69eb906f7c14
Adds options to exercise the newly added KEYGUARD_DISABLE_REMOTE_INPUT
and not so newly added KEYGUARD_DISABLE_FINGERPRINT.
Change-Id: I0e2a05f2a668b7d8ceacde3abcf5f8c80cb4bdb9
Fixes: 26981262
This is now much more like one would write to look for
photos being added/changed. It looks at the URIs that have
changed and filters them to only files that it cares about
(in this case those under DCIM, that is photos added by the
camera), and also explicitly understands the difference
between individual URIs changing and a more general change
requiring a full re-query of the provider.
Change-Id: I509570aa66839f8b84b5a065c4b4e49fbd0f1c29
This CL adds some sample entries so that IME developers can test their
IMEs with various EditorInfo#hintLocales.
Bug: 22859862
Change-Id: Ic0bc98bc4c9cb7b874ca8d54433bde76d05e8e03
Adds examples for a variety of Material-only control styles including
underlined Spinner and discrete SeekBar. Groups controls into cards.
For the old-style controls, moves some run-time setup tasks into XML.
Bug: 19352193
Change-Id: Ibb1c82ac6ecaca3b93f3acfd65ef67cd9784fef4
At least on AOSP InputMethodManager#showInputMethodAndSubtypeEnabler()
has been broken for long time. Also, there has been a valid alternative
way to do the same thing.
This CL adds an API sample to officially encourage people to use
Settings.ACTION_INPUT_METHOD_SUBTYPE_SETTINGS intent rather than trying
to rely on InputMethodManager#showInputMethodAndSubtypeEnabler(), which
is highly likely to be broken.
Bug: 26189558
Change-Id: I915a2d81948598ed08b4ef9111bdd128fd93f3df
There are many more variants of TextView and EditText than are shown
in Views/Controls. Add new pages with some of the variants and move
all the text examples to Views/Text.
Bug: 21518721
Change-Id: Ie839e9c964d019ffbe8be2170e124276b087916d
The plaintext and ciphertext fields weren't showing up on Nexus 7
(possibly other devices too) because of some unresolvable dependencies
between UI elements.
Also stopped leaving these fields editable when no key was selected
and corresponding action buttons were switched off.
Change-Id: I32ed3e2f24c134504a02db6fdfb9905ec147fbdd
The UI now shows these input fields:
* A normal field with buttons for programmatic SetText, append and insert.
* A field with undo disabled.
* A field with a length limit (via InputFilter).
* A field with a credit card input formatter (via TextWatcher)
Bug: 19332904
Change-Id: I41df56c84dd5232918e7ee5e6ed5874b2023cc78
This reverts commit 18c5fb7c2c, which
disabled the trust agent whitelisting in the sample device admin. Now
that the API is re-enabled, that code should be too.
Bug: 19461292
Change-Id: I85e3b4dcaab500ea9dd4b7e75490ca840ff396be
