Revert submission 25108596-va-special-access
Reason for revert: voice activation is not going in V
Reverted changes: /q/submissionid:25108596-va-special-access
Bug: 306447565
Bug: 393727896
Test: presubmit
Change-Id: I4977e7d543cb800fc9fb6962bba3afebb9480dcc
This reverts commit d2c91b587e.
Reason for revert: Landing the original cl as the test passes locally with changes and failed test looks to be flaky and not related to the change.
Failure is not seen in the ABTD test run results with this CL b/331935387#comment10
Change-Id: I744e11a04b70e265c5dcfe5aa8db7237561f3a08
The title string was approved by UX as it is, so mark it as ready to
translate, and add a summary line.
Screenshot: go/b-324058706-strings-screenshot
Bug: 324058706
Bug: 321978150
Change-Id: Iaa757be16b58b23fba8a6841621ad8000b51c250
Test: Open touchpad settings, check new summary line appears
- For MATCH_WIFI, only shown non carrier warning when has SIM
- For others, restore the previous operator warning
Bug: 331184249
Test: manual - on DataUsageList
Change-Id: I5d5c6b36c6874a547cc635c025aa77acadf6e1e3
This reverts commit 7b0b26ec92.
Reason for revert: b/331935387. ACA has already verified the revert.
Change-Id: Idf28854f25c4bad3563408dbb7b5c84f0cdbe2f2
guidance url link are vary per each carrier, therefore makes it carrier configurable
Bug: 330948681
Test: manually test whether URL works as intended on pixel with TMO/SKT SIM
Change-Id: I062b1e9267c6edf3289d85dc58f9ab2d9cff64d8
At the end of PS setup just before showing the final sucess screen this
change adds a new screen with loading layout which enables profile quiet
mode.
After enabling quiet mode checks if user is stopped before removing the
loading layout screen. Until user is stopped loading screen will be
shown.
Bug: 329042236
Bug: 328393532
Test: Manual verify new delay screen is shown
Change-Id: Iac3fd2f0f5c75a64719fbce32ff4dbfb533322d5
As b/328787031, we make the MagnificationAlwaysOnPreferenceController observe the magnification capabilities then update the preference enabled state. Therefore, when changing the capabilities to window mode only, the preference will become unavailable.
We use the bug-fix flag to verify the fix with rollout process.
Bug: 328787031
Flag: ACONFIG com.android.settings.accessibility.hide_magnification_always_on_toggle_when_window_mode_only DEVELOPMENT
Test: manually flip the flag
atest MagnificationCapabilitiesTest
atest ToggleScreenMagnificationPreferenceFragmentTest
atest MagnificationAlwaysOnPreferenceControllerTest
Change-Id: I1a25f80131d84ecdd927030e40a18ebb32b7862f
The feature is behind a release flag. It is also behind an experiment
flag so it can be trialed with Googlers before general release even
after being enabled in a release.
The feedback button only shows up if there is an intent URI configured,
which should be handled via an overlay. The design means that the intent
is potentially dependent on the manufacturer (good!), though I expect we
will suggest a standard one for GMS devices so we get feedback from a
variety of devices with different form factors / capabilities.
In this default, GMS core (Google Play Services) will handle the intent
and take the user through a feedback UI flow.
Testing:
To enable the button you need to build with one of release variants that
supports dynamic flags, e.g. trunk_food.
Then release flag:
$ adb shell device_config put location com.android.settings.flags.datetime_feedback true
It still won't work without the experiment flag:
$ adb shell device_config put settings_ui time_help_and_feedback_feature_supported true
Finally, the settings entry will launch an intent when pressed which has
to have a receiver. The receiver will be in GMS core but will be subject
to its own review / launch process. Until then, this feature will remain
quiet, biding its time.
Bug: 283239837
Test: Manual (see above)
Test: atest SettingsRoboTests:com.android.settings.datetime
Change-Id: I68798798fc0a47ae4c6755174ce509fbaee24142
Reformatted xml files and added constraints to make sure texts do not go
out of bound.
Test: local raven device
Screenshot: attached on bug
Bug: 329176991, 329169251
Flag: aconfig
com.android.settings.accessibility.enable_color_contrast_control
Change-Id: I7cb15a46557f54833c77fe41928fb6e98d5ec519
Update the guideline string to the latest from UX team.
Bug: 330961550
Test: manually testing from pixel device
Change-Id: Ic6eb4ba2a85cbfc5544182f30fe645283084084a
This takses care to add an entry point in Settings->System->Reset
options->Delete private space when private space feature is supported on
the device. Entry point appears both when private space exists and also
when private is not created.
On selecting asks for user authentication and on successful
authentication using device lock shows a dialog asking for
confirmation and calls for deletion private space.
Based on this entrypoint it would not be possible to guess if private
space exists on the device.
Recording link : b/329041740#comment3
Bug: 329041740
Test: atest ResetOptionsDeletePrivateSpaceControllerTest and verified
this doesn't give away existence of private space
Change-Id: I9a5b908e7a3f9edaf609cf7e6a87f9842d689ce6
This allows for controller-backed preferences to be added or
overridden via xml.
Similarly, if the controllers cause all of the preferences for
2 or 3 button nav to be unavailable, we hide the settings button.
Bug: 324036308
Test: Manual and unit tests
Flag: NA
Change-Id: I2371f3173076172489966728ac69c8767570cd56
Merged-In: I2371f3173076172489966728ac69c8767570cd56
Change to add message in the dialog shown on selecting to choose a new
profile lock for private space.
screenshot : go/ss/ASkBCFJuCzp7dkf.png
Bug: 330218365
Test: Manual. Diaog shown as per UX mock
Change-Id: I17f4d7ebf515dc7c95fcae7a5ec5edeb9918ded3
