diff options
| author | Ryan Mitchell <rtmitchell@google.com> | 2020-02-27 16:50:44 -0800 |
|---|---|---|
| committer | Ryan Mitchell <rtmitchell@google.com> | 2020-03-02 23:46:07 +0000 |
| commit | 8c4aab3af6564dae17f924c576dd19c829657dbb (patch) | |
| tree | 0cc899d89ed692c1eb9a12f23042c642892bb259 /graphics/java/android/renderscript/ProgramVertexFixedFunction.java | |
| parent | cb2d2ec786140c9ff001868308d5ffb1c0456d2a (diff) | |
Allow mutable overlays to be enabled by default
When an overlay is not specified as immutable through OverlayConfig,
enabling the overlay using the OverlayConfig `enable` attribute makes
the overlay enabled by default.
When an overlay is scanned by the OverlayManagerService for the first
time, the default-enabled state will be applied to the overlay. If the
configured default-enabled state changes in a subsequent boot, the
default-enabled state will not be applied to the overlay.
This means OTAs cannot change a mutable overlay from default-enabled
to default-disabled (or vice-versa) and except the configured enabled
state to take effect.
When the device is factory reset, then the configured enabled state
will be applied. If a package is removed from the device in one OTA
and added back to the device in a future OTA, the configured enabled
state will be applied. If an overlay changes its target package or
target overlayable, then the configured enabled state will be applied.
If an immutable overlay becomes mutable, then the configured enabled
state will be applied.
Bug: 149499802
Test: atest OverlayManagerServiceImplRebootTests
Change-Id: I24f86591ac811ef2b836da36ef5574a82628b151
Diffstat (limited to 'graphics/java/android/renderscript/ProgramVertexFixedFunction.java')
0 files changed, 0 insertions, 0 deletions