Adds the conditionally used xml ui definition and removes it at runtime when it's not
wanted. Ported from GB.
bug:5237167
Change-Id: I89a67e1033ddc7099563732e839c08fbadb4fd75
The option is not functional yet.
Also, this change simplifies a little the inner workings by
preventing mLocale from being null.
Step 9
Bug: 5306641
Change-Id: Id2284976d34d9d8ac61cbdb2348893989c47da84
With this, the word is actually inserted with the right locale
inside the user dictionary.
Step 8.
Bug: 5306641
Change-Id: Idf6cf3dd807e86c29faf8a701c03c1e6ea39ec68
This populates the language list. The option looks like it works,
but is not implemented yet.
Step 6.
Bug: 5306641
Change-Id: I6ef84dea9a26e450add1d91b44238d86fe49200a
The interface is not functional yet, aside from the "Manage"
button. This will come in a later change.
Step 5
Bug: 5306641
Change-Id: I4bdea099eece7ba8a50bbfb47e173036334064ea
By default we do not speak passwords if the user has no headset. However,
many users find this too restrictive and would like a way to enable
password announcement. While we cannot speak the passwords all the time
,to avoid leaking them, we expose a preference so each user can choose
the option that best works for him/her.
bug:5712607
Change-Id: I1a6e95c392c18dc8d7406b1cef49705756b31254
This fixes a bug where the SIM enable checkbox was showing the
wrong state. The code now registers for state changes and updates
the checkbox state appropriately.
Change-Id: Icd4f040140e9f71e75e288968ee7ae616dfd08ce
We go back to the old style of toggling between Mute/Vibrate/Normal.
There is an addition of a checkbox to indicate Vibrate on ring/notif.
Icons in volume dialogs are no longer touchable.
Bug: 5586083
This simplifies the logic in SoundSettings quite a bit, since there's a 1-1 mapping
with ringer mode.
Don't disable volume sliders when muted, so you can go to zero and back up by sliding
your finger. This is because the icons are not clickable anymore.
Change-Id: Ia7ce7e1bf108419eb107f03b7720101efe1598b1
We need to allow FaceUnlock if the backup lock supports encryption (PIN).
This requires changing the way the minimum encryption quality is enforced
to allow FaceUnlock as long as the backup lock is a PIN, as FaceUnlock
is considered a lower security than the minimum for encrypted drives.
This change adds some complexity to upgradeQualityForEncryption because it's
used in two places: once to grey out selections that aren't sufficient
security level, and second to force the user to use a higher security level.
This still increases the minimum security level,
but makes an exception for FaceUnlock if it's allowed without encryption.
This uses a MutableBoolean to provide a mutable boolean capability.
We could instead write a custom one or use some other type of mutable
boolean if it exists.
In CryptKeeperSettings, using getKeyguardStoredPasswordQuality directly instead
of getActivePasswordQuality is simpler, but this uses a more complex approach
with a minor tweak as jaggies suggested it and it is clear about the
biometric exception being made.
Change-Id: Ia2645d6bd98857c79c6a9be45eda98087bfe517a
- Use switch for toggling
- Follow string and UI suggestions from UX folks
The goal is to keep the interaction minimal - PBC is used when possible and keypad/display
are used only if really necessary
Bug: 5332330
Change-Id: I83e91ad3a393c143e70f1f2b6a842b95eacde404
Bug 5646340.
'Title' and 'scanning' text are on the same line as a PreferenceCategory.
The first one has a 0dp width, compensated by a 1 weight.
When scanning is not displayed, it should be GONE rather than INVISIBLE
to let the title take the whole space.
When both are visible, they should split the space, or else, with long
texts in foreign languages, scanning takes the whole space, leaving the
title with an almost 0 width that generates a very high text because
of wrapping.
Distributing size among the two texts to accomodate for such cases.
Changed padding and alignment to get reasonnable results for Slovenian
language (i.e. very long text), when both title and scanning are displayed.
Strangely, the right scanning alignment is not enforced, although I checked
it is correctly set on the TextView. Not investigating further now since it
may not be desired by UX anyway.
Change-Id: I6b4c6fcbc350d3664749f58eee34ec0867720626
