Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove config_displayUsiVersionArray from config.xml

Browse Source 
This was remove in the following CL:
I9ea5a635fbbb0dc57abb869f2f8fcb509a76a58d

But was brought back accidentally in the following CL:
I782ea11b90f2cb5bcea5189d4824483d2b4621d5

Bug: None
Test: Presubmit
Change-Id: I3ad7c032fb56c5df7b51013750a978d3f37e36fd
This commit is contained in:
Prabir Pradhan
2023-03-27 21:40:09 +00:00
parent 8246587377
commit 53d9c8279d
1 changed files with 0 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
core/res/res/values/config.xml
View File

@@ -6352,23 +6352,6 @@
<!-- Package name of Health Connect data migrator application. -->
<string name="config_healthConnectMigratorPackageName"></string>
<!-- The Universal Stylus Initiative (USI) protocol version supported by each display.
(@see https://universalstylus.org/).
The i-th value in this array corresponds to the supported USI version of the i-th display
listed in config_displayUniqueIdArray. On a single-display device, the
config_displayUniqueIdArray may be empty, in which case the only value in this array should
be the USI version for the main built-in display.
If the display does not support USI, the version value should be an empty string. If the
display supports USI, the version must be in the following format:
"<major-version>.<minor-version>"
For example, "", "1.0", and "2.0" are valid values. -->
<string-array name="config_displayUsiVersionArray" translatable="false">
<item>""</item>
</string-array>
<!-- Whether system apps should be scanned in the stopped state during initial boot.
Packages can be added by OEMs in an allowlist, to prevent them from being scanned as
"stopped" during initial boot of a device, or after an OTA update. Stopped state of