This setting allows users to always show a single-line format clock,
regardless of notification status.
Fixes: 194905512
Test: atest KeyguardClockSwitchControllerTest
Change-Id: I77269988447fc5732ff6b8774654ce4bf9c026de
Root Cause: Accessibility Settings reorganize its pages structure. It
can not be accessed in first layer of accessibility settings page anymore.
Solution: Directly add intent ACTION_REDUCE_BRIGHT_COLORS_SETTINGS to
that settings page.
Bug: 202480583
Test: atest ColorInversionTileTest
Change-Id: I49dc154ea12a3247b5405f1c46c1b6b57932837c
- Added a telephony provider entry for storing the user's settings.
- Added new vonr_enabled_bool config to determine whether
VoNR should be enabled for carrier
Bug: 202150953
Test: manual
Change-Id: Ie56a7de3fdb978353af77bafb55b0e37c22b58a4
Merged-In: Ie56a7de3fdb978353af77bafb55b0e37c22b58a4
Avoid using 'two pane' and 'large screen' because
they are implementation details exposure.
Bug: 201662312
Test: build pass
Change-Id: I67e4b07ab957285ac0410f307030c491b3f6e95d
Privacy checks in Settings.getStringForUser are using reflection to find
secured values, so move constant definition to proper place.
Test: verified against PoC
Bug: 172838801
Change-Id: I2d94101b677e71011273c2674edc197840fb1411
For the Intent ACTION_SETTINGS_LARGE_SCREEN_DEEP_LINK,
EXTRA_SETTINGS_LARGE_SCREEN_DEEP_LINK_PENDING_INTENT is for partner
apps to tell target Activity the private Activity to start.
However, developers feedback that customization extra data are
preferred, so a later CL supports customized extra data for
ACTION_SETTINGS_LARGE_SCREEN_DEEP_LINK.
Developers will not need
EXTRA_SETTINGS_LARGE_SCREEN_DEEP_LINK_PENDING_INTENT to specify
a private Activity.
Bug: 197048599
Test: build pass
Change-Id: Icc949b897ff36755004cc34b31caf5b06974bfae
Use property ro.audio.spatializer_enabled to optimize the
AudioService initialization of Spatializer.
Persist the state of the spatial audo feature whenever its state
changes. Read it at start or whenever AudioService needs to
re-initialize the feature (after audio_server restart)
Bug: 188502620
Test: adb shell dumpsys audio | grep -A 4 Spatial
Change-Id: I667ff7f0247396aad698765455e400337d9c6dcb
For experiment flag testing, adding lmkd flag in DeviceConfig.
Bug: 194316048
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: I1f13d6bbb4a9a7fd8825d7e5acde416750271df4
Merged-In: I1f13d6bbb4a9a7fd8825d7e5acde416750271df4
System or preinstalled apps can use the intent to show it's Activity
in split mode of Settings app for large screen devices.
Bug: 197048599
Test: build pass
Change-Id: Icb709f12a51687679b23ac7920e60873c537b8bb
Remove support for ANGLE's libfeature_support_angle.so.
This also removes all of the logic related to checking the rules file,
since libfeature_support_angle.so is what parsed the JSON rules file.
Bug: b/187342779
Bug: b/184757175
Test: make and manual verification ANGLE is loaded
Change-Id: I02ac083fb8144465b60ac0ed2738c73b31addda1
Merged-In: I02ac083fb8144465b60ac0ed2738c73b31addda1
Test: Cherrypick ag/15542611
Test: Ensure Assistant invocation is set as the LPP action
Test: Adjust LPP sensitivity
Test: Hold LPP for the set time
Test: Observe activation duration matches set time
BUG: 192995149
FIX: 197080361
FIX: 197081640
Merged-In: I820a9d83fd56bfa9ca978e82eb779cf3d519a5ab
Change-Id: I820a9d83fd56bfa9ca978e82eb779cf3d519a5ab
Test: Cherrypick ag/15542611
Test: Ensure Assistant invocation is set as the LPP action
Test: Adjust LPP sensitivity
Test: Hold LPP for the set time
Test: Observe activation duration matches set time
BUG: 192995149
Merged-In: I820a9d83fd56bfa9ca978e82eb779cf3d519a5ab
Change-Id: I820a9d83fd56bfa9ca978e82eb779cf3d519a5ab
This will be flagged with config_perDeviceStateRotationLock.
If true, a distinct rotation lock settings can be maintained for each
device state. Some device states won't need their own rotation lock
setting and in those cases, the setting of the previous device state
will be used.
The existing global setting "Settings.System.ACCELEROMETER_ROTATION"
still works the same and reflects the setting for the currently active
state.
Test: atest SystemUiTests:RotationLockControllerImplTest
Test: atest SystemUiTests:DeviceStateRotationLockSettingControllerTest
Bug: 183001527
Change-Id: I1cbcfae7db7c01745ea7ad665432f8651d8f1546
* changes:
Add the log for new supported accessibility button type 'Accessibility Gesture'
Update the supported type in ACCESSIBILITY_BUTTON_MODE according to navigation gestural mode or button mode
Add a supported type 'gesture' under ACCESSIBILITY_BUTTON_MODE
Remove setting option and show lockdown button by default in the power menu
Fixes: 185618694
Test: atest GlobalActionsDialogLiteTest
Test: flash device, set PIN, observe button present
Change-Id: I7c8f976fd73f6edf3edb26c8de31fd83eb9ac296
Root cause: From the user feedback, accessibiltiy gesture has more
benifits than floating accessibility button especially to low vision users.
Solution: Bring back accessibility gesture to be one of the options of
the accessibility button.
Bug: 190563948
Test: install new SettingsProvider.apk & adb reboot & manual test
Change-Id: I59952c744cddfbdc01b906d39b2681858f0bb2ea
App processes might need to read the Settings value using system code.
Therefore this key is @hide but should be @Readable.
BUG: 191519696
Test: atest android.appsecurity.cts.ReadableSettingsFieldsTest
Change-Id: Idf1512ebf3487d74a18ad2dc13ee7cbb2c7643d0
Some users had a bad default value from a previous build. This renames
the flag so that they will still get the correct default when upgrading.
Fixes: 191786947
Test: manual, atest
Change-Id: I8fa3077bf7c8a4414ebc259174214538684f6560
This reverts commit 516cb2d025.
Reason for revert: Add back after merging f2fs/f2fs-tools changes removing immutable bit stuffs
Bug: 188928405
Change-Id: I6a6fcde1190bff14abe1a67a75b8e7be95d89072
This reverts commit e41b029d85.
Reason for revert: b/189985437
com.android.tradefed.targetprep.TargetSetupError[APK_INSTALLATION_FAILED|520001|DEPENDENCY_ISSUE]: Failed to install com.android.devicehealthchecks with ...
Change-Id: I06fe7d94f6dab474c74b093de8692f08d4031b62
Modern f2fs implementations starting in S support compression
natively within the file system. The data blocks of specific
installation artifacts [eg. .apk, .so, ...] can be compressed
at the file system level, making them look and act like any
other uncompressed file, but consuming a fraction of the space.
However, the unused space is not free'd automatically. Instead,
we must manually tell the file system to release the extra
blocks [the delta between the compressed and uncompressed block
counts] back to the free pool.
Because of how compression works within the file system, once
the blocks have been released, the file becomes read-only and
cannot be modified until the free'd blocks have again been
reserved from the free pool. For these installation artifacts,
that is not a concern.
Test: atest CtsAppSecurityHostTestCases:SplitTests
Test: atest CtsAppSecurityHostTestCases:IsolatedSplitsTests
Test: atest CtsAppSecurityHostTestCases:PkgInstallSignatureVerificationTest
Test: atest CtsLibnativehelperTestCases
Test: atest PackageManagerTests
Test: Manual. Boot the device and see cblocks for stub APKs are released
Test: Manual. Disable and re-enable stub APK and see cblocks are released
Bug: 188928405
Change-Id: I4b29dab263d02a79d7b1593d35ae28101d33679a
New annotation field that allows Settings key owners to specify the
maximum target sdk level of the caller app allowed to read the
hidden settings key.
Test: atest android.appsecurity.cts.ReadableSettingsFieldsTest
BUG: 187314081
Change-Id: Ibb603df4c8bca75e3788258e69862595c22e5154
