"Remove all fingerprints?" dialog should only be shown when removing the
last finger print. Fixed.
Changed the Dialog description for the same.
Bug: 26903306
Change-Id: I11b11a9173fa9b09e3fb20bb8a8e7a64594a7d81
You can't choose to use a disabled WebView package as WebView
implementation (this ensures that without interference from the user the
system will always try choose a package which will eventually become
updated, rather than a package that does not receive updates) and there
are cases where a package cannot/should not be enabled (to save e.g.
bandwidth).
Therefore, with this change we no longer show disabled WebView packages
as potential WebView implementations in the WebView implementation
Developer setting.
Bug: 27188851
Change-Id: I19a9b16118703d8a54d8215c186fc99ffefc4b6d
The enabled-state of a package is already being accounted for when
creating an ApplicationInfo from the package manager, so checking it
again in Developer Settings to figure out whether a package is enabled
is unnecessary.
Change-Id: I1b057a28bb33fc2bbc5ea750bfa04a75860ff1d1
OnStop gets called after an activity behind it on the stack is resumed
when the user pressed the back button on the navigation bar. Because of
this, we need to disable the cancelEnrollment call inside onBackPressed
instead of onStop so that on the find sensor page, the auto next advance
on pressing the fingerprint sensor will still work.
bug:27151472
Change-Id: I1e440f1f7cd91c0711dd31b8bf65a567d4d39f8b
The privilege for an app to write to the system settings is protected
by an app-op signature permission. App-op permissions are special: if
the app-op is deny/allow we deny/allow write access; if the app-op is
default holding the permission determies write access. The settings
code assumes that CHANGE_NETWORK_STATE is an app op permission
(system|appop) while it is a normal permission which any app gets by
declaring it used in the manifest.
The side effect is that the state of the toggle in the UI for write
system settings will initially be in the wrong state if the app uses
both WRITE_SETTINGS and CHANGE_NETWORK_STATE. However, the code in
the public API an app uses to check write settings access would return
the opposite since it checks the WRITE_SETTINGS permission and its
app op. Hence, if an app requires write settings to start the user
will see in the settings UI it has access but the app will not have
access, so the app would prompt the user to allow write settings.
The non-obvious fix is for the user to toggle the setting off and on
to get the app op in the right state and be able to launch the app.
bug:25843134
Change-Id: I3d726a66c7f9857bc7dbd5946fdbb8f340c6eb4d
(cherry picked from commit 356fb2d10d)
(cherry picked from commit 119d589ea5)
This reverts commit a95e7c3c09.
This causes a bug where you cannot access fingerprint from settings.
bug:27152471
Change-Id: I4f3078a81b66d44bb6f29ed3afc501e0b56a369e
am: 20975797b7
* commit '20975797b7a0262b9fa65a32766dfdfba93afdb0':
Remove 'Higher speech rate' button based on the results of the speech rate slider a11y UX study.
am: 5433496186
* commit '5433496186856aa16a8092801a073e4971a97536':
Remove 'Higher speech rate' button based on the results of the speech rate slider a11y UX study.
rate slider a11y UX study.
Also, group speech rate, sample sentence synthesis and default language
status into a single preference category as they all fall under the
general TTS settings category.
Bug: 24527715
Change-Id: If7253e2e8a468393afcb4c24f5a775cb9af79db9
