These should mirror IccConstants usage for consistency.
Test: Manual build and flash
Bug: 170653527
Change-Id: I5ff335eeae99cd5b6f8ebfb809c826843d6abd77
One sample usage is to toggle between server based or HAL based
implementation for resume on reboot.
Bug: 172780686
Test: adb shell device_config put ota server_based_ror_enabled true；
Check the value in system server code
Change-Id: Ia9d3cae788e9316850ce1fc417c12b5fc109b1a3
Add APIs for Telephony to store pictures for call composer in the call
log.
Test: atest android.provider.cts.contacts.CallLogTest#testCallComposerImageStorage
Bug: 174798736
Change-Id: I5baf6d3751f3ed6edc77515e5eeb97906dc66758
Previously we were only able to expose whether bubbles
were "all" allowed rather than the selected state. Since
we can change APIs again lets expose the specific prefs.
Bug: 170267239
Test: atest NotificationManagerTest in CTS CL
Change-Id: Ie83934fe1a6b1639fad54967b67e86f6eeeff7cf
Bug: 174932174
Test: I solemnly swear I tested this conflict resolution.
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Change-Id: I9262a08ffc1ccede8e519d0eed90ed2bfcf0232c
As general background, OWNERS files expedite code reviews by helping
code authors quickly find relevant reviewers, and they also ensure
that stakeholders are involved in code changes in their areas.
Some teams under frameworks/base/ have been using OWNERS files
successfully for many years, and we're ready to expand them to cover
more areas. Here's the historical coverage statistics for the last
two years of changes before these new OWNERS changes land:
-- 56% of changes are fully covered by OWNERS
-- 17% of changes are partially covered by OWNERS
-- 25% of changes have no OWNERS coverage
Working closely with team leads, we've now identified clear OWNERS on
a per-package basis, and we're using "include" directives whenever
possible to to simplify future maintenance. With this extensive
effort, we've now improved our coverage as follows:
-- 98% of changes are fully covered by OWNERS
-- 1% of changes are partially covered by OWNERS
-- 1% of changes have no OWNERS coverage
This specific change is automatically generated by a script that
identifies relevant "include" directives.
Bug: 174932174
Test: manual
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Merged-In: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
Change-Id: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
Via flag value, allow user to select one conversation or see all
conversations. Updates UX to make single conversation fit a 2x1 tile.
Test: PeopleSpaceWidgetManagerTest
Change-Id: I2fac077f4fab32a9a597437a3834dab27539ba75
Bug: 174850448
Updated the name to better represent the usage of this setting.
The values of the constants remain the same to ensure compatibility.
Bug: 169145038
Test: atest HdmiCecLocalDevicePlaybackTest
Change-Id: Ieba3d94d5db52d39f717b525a8b8ed6e6587b132
Move battery saver to retrieve remote configuration values via
DeviceConfig. Some products allow users to customize which battery saver
toggles are active, so leave the Global settings flag around to track
the user's choices. The user's choices will override anything sent from
the server.
Also renaming some of the flag names since we don't need to support
backwards compatibility for server-side pushes.
Bug: 79580230
Bug: 124466289
Test: atest com.android.server.power.batterysaver.BatterySaverPolicyTest
Test: atest com.android.server.power.batterysaver.BatterySaverStateMachineTest
Test: atest com.android.server.power.batterysaver.BatterySavingStatsTest
Test: atest com.android.server.power.PowerManagerServiceTest
Test: atest CtsBatterySavingTestCases
Test: atest CtsLocationFineTestCases
Change-Id: I47684efa5c4426e1c524fb9c1d4d407ee66fa3b7
Ideally we would use an undefined value like
Configuration.FONT_WEIGHT_ADJUSTMENT_UNDEFINED to represent the undefined
setting but undefined config values do not trigger configuration updates
(which we need on a user change)
Bug: 174605763
Test: switch to new user
Change-Id: I73e6456427e3f05d02182e9544fe54cd44640e2e
DisplayWindowSettingsProvider currently only supports reading display
window settings from a single file location. However, this doesn't
support the use case where a device may want to ship with multiple
vendor display setting experiences and allow switching between them at
runtime.
This updates DisplayWindowSettingsProvider to allow overriding the file
path that's used to read display settings. The default is still to read
from the main settings file stored at /vendor/etc/display_settings.xml
but can be changed by setting the global setting:
DEVELOPMENT_WM_DISPLAY_SETTINGS_PATH.
This also removes the flag DEVELOPMENT_IGNORE_VENDOR_DISPLAY_SETTINGS to
since ignoring vendor display settings entirely is no longer needed.
Test: atest WindowManagerSettingsTests
Test: atest DisplayWindowSettingsProviderTests
Bug: 172342357
Bug: 173540615
Change-Id: I11fd2945a4dacef80e1ab921d585c712f20ae55b
Isolated storage was added in Q (and enabled by default) and has been
replaced by FUSE in R
Additionally, we can remove the ExternalStorageMountPolicy concept
which is only required if isolated storage is false
Cleanup in preparation to introduce DeviceConfig changes for
transcoding
Bug: 169327180
Test: Builds
Change-Id: Ie2686d8efa6654ea6c4b4ca8c121c0c1841a6356
This functionality is no longer needed as all battery saver related
logic is handled within location code.
Bug: 69373668
Test: presubmits
Change-Id: Ie79d6334e0aff5a6562ae0014b9274c81434b977
Add statsd_native and statsd_native boot namespaces, and sync them to
DeviceConfig.
Test: manually checked that statsd could receive flags with selinux
changes in
Bug: 172842175
Change-Id: I9b61e78e9131cf9733d46e73d9ea92e72d1ce1b7
This setting will store an emergency number locally if government
provided emergency number (such as 911, 110) are not desired by user,
used by emergency apps such as EmergencyInfo and Personal Safety on
Pixel.
Bug: 172609395
Test: manual/rebuild
Change-Id: I8732c20f0438e521eaec73758242015794c80c3b
