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
Type and trigger description on creation; trigger description on update.
Bug: 317370174
Bug: 320997361
Test: atest ZenModeScheduleRuleSettingsTest ZenModeEventRuleSettingsTest
Change-Id: Idb1edcc8829b54ec85494966eb391e52012a5348
- Disable even dimmer settings option if autobrightness is not enabled
on the device
Bug:179428400
Test: manual
Change-Id: I8f7add839022fc7c27694fd8daa83a608cf2736a
- gray out the next button
- add the format for phone number
Bug: 329535069
Test: manual test. To verify the UI
atest SimOnboardingSelectSimTest
Change-Id: I8dd62e3da9567a518d22d615f6974659900ef1bb
Instead of directly stop audio sharing, clicking on media devices will
lead to different sharing dialogs based on different scenarios. The
scenarios are align to cases when a new device is connected.
Test: atest
Bug: 305620450
Fix: 327259953
Change-Id: Ibb591cb1a59f31c8f0be4f3e72e45378b17e3809
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
Some enabled not set correctly.
Remove the enabled values, and check readOnlyApnFields directly to fix.
Fix: 330566517
Test: manual with carrier config KEY_READ_ONLY_APN_FIELDS_STRING_ARRAY
Test: unit test
Change-Id: Ifd6d4a0d9a96a900c9d124c9e357562e84bbc6c7
Flag has been in Trunkfood for over a month.
Includes one mechanical refactor to move a method from a now-removed
file into a private method in the class that uses it: createDisableDialog
(This flag guarded a preliminary cleanup and minor bug fix for
b/303511250, but the actual feature for b/303511250 is tracked in a
different flag 'skip_accessibility_warning_dialog_for_trusted_services')
Bug: 303511250
Test: existing tests in Presubmit (no change to behavior)
Change-Id: Iccf439adb2806e988310f503fb3891a6bd022054
Split into AutomaticDataSwitchingPreference.kt, and use
isMobileDataPolicyEnabledFlow.
Bug: 329061940
Test: manual - Set Automatic data switching
Test: unit test
Change-Id: I878ed70328307c0a5dba6dfb461ff5a85efbcf88
The issue is caused by SettingsDropdownCheckBox's interface is updated,
but ApnNetworkTypeCheckBox not updated.
Update ApnNetworkTypeCheckBox to fix.
Bug: 329547692
Test: manual - update network type
Test: unit test
Change-Id: I4a5a1ad7d9d97960799f5ba0d89b5178ce410b6e
These permissions are required for any Settings tests to run, otherwise
the tests will fails.
Instead of adding these permissions to each of the tests, add it to the
Settings-core.
Bug: 329046490
Test: unit tests
Change-Id: I54dc1ebfdd062acc224021429dce318d7c12809b
