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
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
These are APIs that have @UnsupportedAppUsage but for which we don't
have any evidence of them currently being used, so should be safe to
remove from the unsupported list.
Bug: 170729553
Test: Treehugger
Merged-In: I626caf7c1fe46c5ab1f39c2895b42a34319f771a
Change-Id: I54e5ecd11e76ca1de3c5893e3a98b0108e735413
* changes:
Add global development setting to enable/disable vendor display settings. (2/n)
Seperate out DisplayWindowSettings persistence from retreival/policy logic. (1/n)
(2/n)
This change introduces the DEVELOPMENT_IGNORE_VENDOR_DISPLAY_SETTINGS
setting which controls whether or not WindowManagerService should return
display vendor settings provided in the vendor/ partition. This will be
added as an entry in Developer Options to allow ignoring vendor settings
and using the default settings.
Test: atest WmTests:WindowManagerSettingsTests
Bug: 168808369
Change-Id: Iece0b76e4861be56186333134d7d5b25cab5c7e0
These are APIs that have @UnsupportedAppUsage but for which we don't
have any evidence of them currently being used, so should be safe to
remove from the unsupported list.
Bug: 170729553
Test: Treehugger
Merged-In: I8285daa8530260251ecad6f3f38f98e263629ca7
Change-Id: I626caf7c1fe46c5ab1f39c2895b42a34319f771a
This flag will enable the BLASTBufferQueue adapter for use by ViewRootImpl.
BLASTSync and the BLASTBufferQueue in SurfaceView are still behind seperate flags.
Bug: 168506246
Test: Days of manual testing on multiple devices (stressed: app switching, rotation, SurfaceView, PIP, Split-screen). Multiple presubmits. 5 passing runs of flicker. Systrace inspection. App startup perf tests. Inspection of jankstats from experiment based flip in R dogfood.
Change-Id: I2b6e37884d938d327479977becbbce8e38e521f0
These are APIs that have @UnsupportedAppUsage but for which we don't
have any evidence of them currently being used, so should be safe to
remove from the unsupported list.
This is a resubmit of ag/12929664 with some APIs excluded that caused
test failures; see bugs 171886397, 171888296, 171864568.
APIs excluded:
Landroid/bluetooth/le/ScanRecord;->parseFromBytes([B)Landroid/bluetooth/le/ScanRecord;
Landroid/os/Process;->myPpid()I
Landroid/os/SharedMemory;->getFd()I
Landroid/hardware/input/InputManager;->INJECT_INPUT_EVENT_MODE_WAIT_FOR_FINISH:I
Bug: 170729553
Test: Treehugger
Change-Id: I8285daa8530260251ecad6f3f38f98e263629ca7
