ca9375e755
Prior to 12L: - values: sbh links to sbh_port - values-land: sbh links to sbh_land However, in 12L this was flipped around: - values: sbh_port links to sbh - values-land: defines sbh standalone To fix for 12L without breaking them for prior versions, break the link and define each of them Also, while we're at it, remove a few links in my own overlays, as they might break similarly in the future Change-Id: Ib4d1896599f47a39274c4930fd765891bf143f7d
278 lines
12 KiB
XML
278 lines
12 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<resources>
|
|
|
|
<!-- Array of light sensor LUX values to define our levels for auto backlight brightness support.
|
|
The N entries of this array define N + 1 control points as follows:
|
|
(1-based arrays)
|
|
Point 1: (0, value[1]): lux <= 0
|
|
Point 2: (level[1], value[2]): 0 < lux <= level[1]
|
|
Point 3: (level[2], value[3]): level[2] < lux <= level[3]
|
|
...
|
|
Point N+1: (level[N], value[N+1]): level[N] < lux
|
|
The control points must be strictly increasing. Each control point
|
|
corresponds to an entry in the brightness backlight values arrays.
|
|
For example, if LUX == level[1] (first element of the levels array)
|
|
then the brightness will be determined by value[2] (second element
|
|
of the brightness values array).
|
|
Spline interpolation is used to determine the auto-brightness
|
|
backlight values for LUX levels between these control points.
|
|
Must be overridden in platform specific overlays -->
|
|
<integer-array name="config_autoBrightnessLevels">
|
|
<item>1</item>
|
|
<item>2</item>
|
|
<item>5</item>
|
|
<item>10</item>
|
|
<item>29</item>
|
|
<item>50</item>
|
|
<item>90</item>
|
|
<item>100</item>
|
|
<item>150</item>
|
|
<item>200</item>
|
|
<item>300</item>
|
|
<item>400</item>
|
|
<item>500</item>
|
|
<item>800</item>
|
|
<item>1000</item>
|
|
<item>1300</item>
|
|
<item>1500</item>
|
|
<item>1800</item>
|
|
<item>2000</item>
|
|
<item>3000</item>
|
|
<item>4000</item>
|
|
<item>8000</item>
|
|
</integer-array>
|
|
|
|
<!-- Array of desired screen brightness in nits corresponding to the lux values
|
|
in the config_autoBrightnessLevels array. As with config_screenBrightnessMinimumNits and
|
|
config_screenBrightnessMaximumNits, the display brightness is defined as the measured
|
|
brightness of an all-white image.
|
|
If this is defined then:
|
|
- config_autoBrightnessLcdBacklightValues should not be defined
|
|
- config_screenBrightnessNits must be defined
|
|
- config_screenBrightnessBacklight must be defined
|
|
This array should have size one greater than the size of the config_autoBrightnessLevels
|
|
array. The brightness values must be non-negative and non-decreasing. This must be
|
|
overridden in platform specific overlays -->
|
|
<array name="config_autoBrightnessDisplayValuesNits">
|
|
<item>3</item>
|
|
<item>10</item>
|
|
<item>20</item>
|
|
<item>50</item>
|
|
<item>70</item>
|
|
<item>85</item>
|
|
<item>110</item>
|
|
<item>130</item>
|
|
<item>150</item>
|
|
<item>180</item>
|
|
<item>180</item>
|
|
<item>180</item>
|
|
<item>180</item>
|
|
<item>225</item>
|
|
<item>270</item>
|
|
<item>300</item>
|
|
<item>315</item>
|
|
<item>330</item>
|
|
<item>380</item>
|
|
<item>420</item>
|
|
<item>450</item>
|
|
<item>450</item>
|
|
<item>450</item>
|
|
</array>
|
|
|
|
<!-- An array describing the screen's backlight values corresponding to the brightness
|
|
values in the config_screenBrightnessNits array.
|
|
This array should be equal in size to config_screenBrightnessBacklight. -->
|
|
<integer-array name="config_screenBrightnessBacklight">
|
|
<item>0</item>
|
|
<item>2</item>
|
|
<item>6</item>
|
|
<item>11</item>
|
|
<item>28</item>
|
|
<item>40</item>
|
|
<item>48</item>
|
|
<item>62</item>
|
|
<item>74</item>
|
|
<item>85</item>
|
|
<item>102</item>
|
|
<item>128</item>
|
|
<item>153</item>
|
|
<item>170</item>
|
|
<item>179</item>
|
|
<item>187</item>
|
|
<item>215</item>
|
|
<item>238</item>
|
|
<item>255</item>
|
|
</integer-array>
|
|
|
|
<!-- An array of floats describing the screen brightness in nits corresponding to the backlight
|
|
values in the config_screenBrightnessBacklight array. On OLED displays these values
|
|
should be measured with an all white image while the display is in the fully on state.
|
|
Note that this value should *not* reflect the maximum brightness value for any high
|
|
brightness modes but only the maximum brightness value obtainable in a sustainable manner.
|
|
This array should be equal in size to config_screenBrightnessBacklight -->
|
|
<array name="config_screenBrightnessNits">
|
|
<item>0</item>
|
|
<item>3</item>
|
|
<item>10</item>
|
|
<item>20</item>
|
|
<item>50</item>
|
|
<item>70</item>
|
|
<item>85</item>
|
|
<item>110</item>
|
|
<item>130</item>
|
|
<item>150</item>
|
|
<item>180</item>
|
|
<item>225</item>
|
|
<item>270</item>
|
|
<item>300</item>
|
|
<item>315</item>
|
|
<item>330</item>
|
|
<item>380</item>
|
|
<item>420</item>
|
|
<item>450</item>
|
|
</array>
|
|
|
|
<!-- The bounding path of the cutout region of the main built-in display.
|
|
Must either be empty if there is no cutout region, or a string that is parsable by
|
|
{@link android.util.PathParser}.
|
|
The path is assumed to be specified in display coordinates with pixel units and in
|
|
the display's native orientation, with the origin of the coordinate system at the
|
|
center top of the display. Optionally, you can append either `@left` or `@right` to the
|
|
end of the path string, in order to change the path origin to either the top left,
|
|
or top right of the display.
|
|
To facilitate writing device-independent emulation overlays, the marker `@dp` can be
|
|
appended after the path string to interpret coordinates in dp instead of px units.
|
|
Note that a physical cutout should be configured in pixels for the best results.
|
|
Example for a 10px x 10px square top-center cutout:
|
|
<string ...>M -5,0 L -5,10 L 5,10 L 5,0 Z</string>
|
|
Example for a 10dp x 10dp square top-center cutout:
|
|
<string ...>M -5,0 L -5,10 L 5,10 L 5,0 Z @dp</string>
|
|
@see https://www.w3.org/TR/SVG/paths.html#PathData
|
|
-->
|
|
<string translatable="false" name="config_mainBuiltInDisplayCutout">
|
|
M 0,0
|
|
h 240
|
|
v 115
|
|
h -240
|
|
Z
|
|
@left
|
|
</string>
|
|
|
|
<!-- Indicate whether to allow the device to suspend when the screen is off
|
|
due to the proximity sensor. This resource should only be set to true
|
|
if the sensor HAL correctly handles the proximity sensor as a wake-up source.
|
|
Otherwise, the device may fail to wake out of suspend reliably.
|
|
The default is false. -->
|
|
<bool name="config_suspendWhenScreenOffDueToProximity">true</bool>
|
|
|
|
<!-- Whether device supports double tap to wake -->
|
|
<bool name="config_supportDoubleTapWake">true</bool>
|
|
|
|
<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
|
|
device from the display on/off state.
|
|
When false, autosuspend_disable() will be called before the display is turned on
|
|
and autosuspend_enable() will be called after the display is turned off.
|
|
This mode provides best compatibility for devices using legacy power management
|
|
features such as early suspend / late resume.
|
|
When true, autosuspend_display() and autosuspend_enable() will be called
|
|
independently of whether the display is being turned on or off. This mode
|
|
enables the power manager to suspend the application processor while the
|
|
display is on.
|
|
This resource should be set to "true" when a doze component has been specified
|
|
to maximize power savings but not all devices support it.
|
|
Refer to autosuspend.h for details.
|
|
-->
|
|
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">true</bool>
|
|
|
|
<!-- Power Management: Specifies whether to decouple the interactive state of the
|
|
device from the display on/off state.
|
|
When false, setInteractive(..., true) will be called before the display is turned on
|
|
and setInteractive(..., false) will be called after the display is turned off.
|
|
This mode provides best compatibility for devices that expect the interactive
|
|
state to be tied to the display state.
|
|
When true, setInteractive(...) will be called independently of whether the display
|
|
is being turned on or off. This mode enables the power manager to reduce
|
|
clocks and disable the touch controller while the display is on.
|
|
This resource should be set to "true" when a doze component has been specified
|
|
to maximize power savings but not all devices support it.
|
|
Refer to power.h for details.
|
|
-->
|
|
<bool name="config_powerDecoupleInteractiveModeFromDisplay">true</bool>
|
|
|
|
<!-- List of biometric sensors on the device, in decreasing strength. Consumed by AuthService
|
|
when registering authenticators with BiometricService. Format must be ID:Modality:Strength,
|
|
where: IDs are unique per device, Modality as defined in BiometricAuthenticator.java,
|
|
and Strength as defined in Authenticators.java -->
|
|
<string-array name="config_biometric_sensors" translatable="false" >
|
|
<item>0:2:15</item> <!-- ID0:Fingerprint:Strong -->
|
|
</string-array>
|
|
|
|
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
|
|
<bool name="config_intrusiveNotificationLed">true</bool>
|
|
|
|
<!-- Screen brightness used to dim the screen when the user activity
|
|
timeout expires. May be less than the minimum allowed brightness setting
|
|
that can be set by the user. -->
|
|
<integer name="config_screenBrightnessDim">4</integer>
|
|
|
|
<!-- Minimum screen brightness setting allowed by the power manager.
|
|
The user is forbidden from setting the brightness below this level. -->
|
|
<integer name="config_screenBrightnessSettingMinimum">2</integer>
|
|
|
|
<!-- Vibrator pattern for feedback about a long screen/key press -->
|
|
<integer-array name="config_longPressVibePattern">
|
|
<item>0</item>
|
|
<item>67</item>
|
|
</integer-array>
|
|
|
|
<!-- Vibrator pattern for feedback about touching a virtual key -->
|
|
<integer-array name="config_virtualKeyVibePattern">
|
|
<item>0</item>
|
|
<item>67</item>
|
|
</integer-array>
|
|
|
|
<!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap -->
|
|
<integer-array name="config_keyboardTapVibePattern">
|
|
<item>0</item>
|
|
<item>30</item>
|
|
</integer-array>
|
|
|
|
<!-- Vibrator pattern for feedback about booting with safe mode enabled -->
|
|
<integer-array name="config_safeModeEnabledVibePattern">
|
|
<item>0</item>
|
|
<item>0</item>
|
|
<item>94</item>
|
|
</integer-array>
|
|
|
|
<!-- Vibrator pattern for feedback about hitting a scroll barrier -->
|
|
<integer-array name="config_scrollBarrierVibePattern">
|
|
<item>0</item>
|
|
<item>15</item>
|
|
<item>30</item>
|
|
<item>15</item>
|
|
</integer-array>
|
|
|
|
<!-- True if the device supports system navigation keys. -->
|
|
<bool name="config_supportSystemNavigationKeys">true</bool>
|
|
|
|
<!-- Specify if the fingerprint hardware support gestures-->
|
|
<bool name="config_fingerprintSupportsGestures">true</bool>
|
|
|
|
|
|
|
|
<!-- Default radius of the software rounded corners. -->
|
|
<dimen name="rounded_corner_radius">105px</dimen>
|
|
|
|
<!-- Height of the status bar -->
|
|
<dimen name="status_bar_height">120px</dimen>
|
|
<!-- Height of the status bar in portrait. The height should be
|
|
Max((status bar content height + waterfall top size), top cutout size) -->
|
|
<dimen name="status_bar_height_portrait">120px</dimen>
|
|
<!-- Height of the status bar in landscape. The height should be
|
|
Max((status bar content height + waterfall top size), top cutout size) -->
|
|
<dimen name="status_bar_height_landscape">24dp</dimen>
|
|
|
|
|
|
|
|
</resources>
|