In order for users to toggle complications on/off in Settings, we need
to categorize complications by type and store user preferences in
Settings.
Bug: 214038424
Bug: 214039192
Bug: 214038263
Test: make -j64 RunSettingsLibRoboTests ROBOTEST_FILTER="com.android.settingslib.dream.DreamBackendTest"
Change-Id: I2db4f2f9c1e08c6cfac3687fa3809662f30a3561
accesses. This is needed for aligning the location indicator to the
recent location accesses page in location settings.
Bug: 191503437
Test: manual
Change-Id: I9d2f473a75e3bfdfef59e675d2f6849e66cbbd94
This CL expands the existing UiModeManager APIs to allow users activate
dark mode at their configured bedtime schedule on supported devices,
i.e. devices with Digital Wellbeing preinstalled.
The CL added granular types for NIGHT_MODE_CUSTOM. There are two types
1. MODE_NIGHT_CUSTOM_TYPE_SCHEDULE
This is the type for a schedule set up by users via the Settings
app.
2. MODE_NIGHT_CUSTOM_TYPE_BEDTIME
This is the type for a bedtime schedule set up by users via the
Digital Wellbeing bedtime settings. Unlike
MODE_NIGHT_CUSTOM_TYPE_SCHEDULE, Android framework doesn't have
any information of the bedtime schedule. The activation of dark
theme lives inside Digital Wellbeing
Test: unit tests: atest FrameworksUiServicesTests:UiModeManagerServiceTest
CTS: atest CtsAppTestCases:UiModeManagerTest
Manual testing via a system app integration
Bug: 210975231
Change-Id: I3b16e649a048f8a485b9e9d6464d4f251839320d
Deprecate HAPTIC_FEEDBACK_ENABLED in favor or HAPTIC_FEEDBACK_INTENSITY,
and VIBRATE_WHEN_RINGING in favor or RING_VIBRATION_INTENSITY.
Introduce hidden flag
VibrationAttributes.FLAG_BYPASS_USER_VIBRATION_INTENSITY_OFF
to represent HapticFeedbackConstants.FLAG_IGNORE_GLOBAL_SETTING in the
vibrator service. This is applied by:
- PhoneWindowManager, that converts HapticFeedbackConstants into
(VibrationEffect, VibrationAttributes).
- CellBroadcastAlertAudio, that triggers alerts using AudioAttributes
with flags FLAG_BYPASS_INTERRUPTION_POLICY (that translates to same flag
in VibratorManager, to bypass DnD) and FLAG_BYPASS_MUTE (that translates
to this new flag, to bypass the new alarm intensity settings).
The new flag is erased from request that are not from privileged apps,
similar to the other bypass flag. The public
HapticFeedbackConstants.FLAG_IGNORE_GLOBAL_SETTING has also been
deprecated in T with a documentation explaining the removal of platform
support.
Remove SysUI dependencies on the deprecated settings, it should use the
USAGE_TOUCH attribute and rely on the vibrator service to apply the user
settings.
Keep other SysUI dependencies that needs to run in older Android
versions (like Launcher3).
Bug: 185351540
Test: VibrationSettingsTest + manual
Change-Id: I0372e4db19e09523795d7e79b9f7a15ae48a8cd9
This will be followed-up by a CL moving it to SettingsLib so it can be
shared with Settings
Bug: 195757480
Test: atest SystemUITests:DeviceStateRotationLockSettingControllerTest
Change-Id: Ic9c720d7c911d9b8db70ea6bb7fbab209a602abe
Introduce new setting keys for media and alarm vibration intensity.
Merge all default vibration intensity getters into a helper class that
receives the VibrationAttributes usage int and applies the default logic
to all usages.
Also update the usage of boolean settings for haptic feedback and ringtone
to disable vibrations in VibrationSettings.
Bug: 198346559
Bug: 207477604
Test: VibratorTest & VibrationSettingsTest
Change-Id: I69ba05a8bc35657637b1f351f4c19d2d96efc9e3
We will no longer be shipping shared apps in Android T
Test: atest CommunalManagerServiceTest
Test: locally on device
Bug: 211633044
Change-Id: I96ff51f1e10801722dd74de110f5c2caacf0d8d3
There are 3 milestones in this feature.
1. Refactor the callbacks for Accessibility in WindowManagerInternal.
2. Implement this feature in such new architecture.
3. Implement the setting choice in preference page.
This CL is for the 3rd milestone.
We add a ACCESSIBILITY_MAGNIFICATION_FOLLOW_TYPING_ENABLED key to store
a user preference for following typing focus. The default value of
preference is true.
If the value is false, we wouldn't do anything in
onRectangleOnScreenRequested and just return.
If the value is true, we would dispatch the event to an activated
magnification controller.
Bug: 194668976
Test: atest AccessibilityManagerServiceTest
atest AccessibilityUserStateTest
atest FullScreenMagnificationControllerTest
atest MagnificationControllerTest
atest WindowMagnificationManagerTest
atest SettingsBackupTest
Change-Id: I7203698d2edcc474ab1638ac81e72e054a61d6fd
- Disables recents in taskbar.
- Changes back and home icons and centers them in the taskbar.
Test: manual
Bug: 203749295
Change-Id: I9aa2a213728549509da4cf7f50abceb690ba31cf
Adds a new setting key, ODI_CAPTIONS_VOLUME_UI_ENABLED, in the
secure settings, to indicate the live caption button show or hide
in the volume rocker.
Bug: 136282740
Test: atest SettingsBackupTest
Change-Id: Ibcf3be36903450538696c75325c4a866942ce693
The dialog is shown if the app is not a signature app, the system is
ready, and the app has created at least one notification channel.
Also applies the SHOULD_SHOW_REQUEST flag to all packages with implicit
POST_NOTIFICATIONS permissions
Bug: 194833441
Test: atest NotificationPermissionTest
Change-Id: I4cb8cc7bcc3635f55e291f176f722dd420a4a1bb
Add a namespace definition for selection toolbar.
Bug: 190030331
Bug: 205822301
Test: manual. Can set and get correct value via this namespace
Change-Id: Icb56cafee3576b6df083aeab68d04cd05e6ee95e
