72a7ab0b82
The partition reserved sizes were taking from stock ROM IE, blockdev --getsize64 /dev/block/mapper/system_a Also add TARGET_IS_VAB cflag as ro.virtual_ab.enabled is true on stock so that our commonized tree can enable VAB-specific changes. Change-Id: I922f61e5a0380d16eba5967f6c77346437290eb6
346 lines
15 KiB
XML
346 lines
15 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
Copyright (C) 2022-2023 The LineageOS Project
|
|
SPDX-License-Identifier: Apache-2.0
|
|
-->
|
|
<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 -->
|
|
<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>1600</item>
|
|
<item>1800</item>
|
|
<item>2000</item>
|
|
<item>3000</item>
|
|
<item>4000</item>
|
|
<item>8000</item>
|
|
</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>2</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>350</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. -->
|
|
<array name="config_screenBrightnessBacklight">
|
|
<item>0</item>
|
|
<item>1</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>198</item>
|
|
<item>215</item>
|
|
<item>238</item>
|
|
<item>255</item>
|
|
</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>2</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>350</item>
|
|
<item>380</item>
|
|
<item>420</item>
|
|
<item>450</item>
|
|
</array>
|
|
|
|
<!-- Stability requirements in milliseconds for accepting a new brightness level. This is used
|
|
for debouncing the light sensor. Different constants are used to debounce the light sensor
|
|
when adapting to brighter or darker environments. This parameter controls how quickly
|
|
brightness changes occur in response to an observed change in light level that exceeds the
|
|
hysteresis threshold. -->
|
|
<integer name="config_autoBrightnessBrighteningLightDebounce">500</integer>
|
|
<integer name="config_autoBrightnessDarkeningLightDebounce">500</integer>
|
|
|
|
<!-- 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 -50,0
|
|
L 50,0
|
|
L 50,115
|
|
L -50,115
|
|
Z
|
|
</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>
|
|
|
|
<!-- 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">2</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 -->
|
|
<array name="config_longPressVibePattern">
|
|
<item>0</item>
|
|
<item>67</item>
|
|
</array>
|
|
|
|
<!-- Vibrator pattern for feedback about touching a virtual key -->
|
|
<array name="config_virtualKeyVibePattern">
|
|
<item>0</item>
|
|
<item>67</item>
|
|
</array>
|
|
|
|
<!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap -->
|
|
<array name="config_keyboardTapVibePattern">
|
|
<item>0</item>
|
|
<item>30</item>
|
|
</array>
|
|
|
|
<!-- Vibrator pattern for feedback about booting with safe mode enabled -->
|
|
<array name="config_safeModeEnabledVibePattern">
|
|
<item>0</item>
|
|
<item>0</item>
|
|
<item>94</item>
|
|
</array>
|
|
|
|
<!-- Vibrator pattern for feedback about hitting a scroll barrier -->
|
|
<array name="config_scrollBarrierVibePattern">
|
|
<item>0</item>
|
|
<item>15</item>
|
|
<item>30</item>
|
|
<item>15</item>
|
|
</array>
|
|
|
|
<!-- ComponentName of a dream to show whenever the system would otherwise have
|
|
gone to sleep. When the PowerManager is asked to go to sleep, it will instead
|
|
try to start this dream if possible. The dream should typically call startDozing()
|
|
to put the display into a low power state and allow the application processor
|
|
to be suspended. When the dream ends, the system will go to sleep as usual.
|
|
Specify the component name or an empty string if none.
|
|
Note that doze dreams are not subject to the same start conditions as ordinary dreams.
|
|
Doze dreams will run whenever the power manager is in a dozing state. -->
|
|
<string name="config_dozeComponent">com.android.systemui/com.android.systemui.doze.DozeService</string>
|
|
|
|
<!-- If true, the doze component is not started until after the screen has been
|
|
turned off and the screen off animation has been performed. -->
|
|
<bool name="config_dozeAfterScreenOffByDefault">true</bool>
|
|
|
|
<!-- An array of arrays of side fingerprint sensor properties relative to each display.
|
|
Note: this value is temporary and is expected to be queried directly
|
|
from the HAL in the future. -->
|
|
<array name="config_sfps_sensor_props" translatable="false">
|
|
<item>@array/config_sfps_sensor_props_0</item>
|
|
</array>
|
|
|
|
<array name="config_sfps_sensor_props_0" translatable="false">
|
|
<item>local:4630946747577212034</item> <!--item>displayId</item-->
|
|
<item>1080</item> <!--item>sensorLocationX</item-->
|
|
<item>800</item> <!--item>sensorLocationY</item-->
|
|
<item>50</item> <!--item>sensorRadius</item-->
|
|
</array>
|
|
|
|
<!-- Indicates whether device has a power button fingerprint sensor. -->
|
|
<bool name="config_is_powerbutton_fps" translatable="false">true</bool>
|
|
|
|
<!-- The default refresh rate for a given device. Change this value to set a higher default
|
|
refresh rate. If the hardware composer on the device supports display modes with a higher
|
|
refresh rate than the default value specified here, the framework may use those higher
|
|
refresh rate modes if an app chooses one by setting preferredDisplayModeId or calling
|
|
setFrameRate().
|
|
If a non-zero value is set for config_defaultPeakRefreshRate, then
|
|
config_defaultRefreshRate may be set to 0, in which case the value set for
|
|
config_defaultPeakRefreshRate will act as the default frame rate. -->
|
|
<integer name="config_defaultRefreshRate">0</integer>
|
|
|
|
<!-- The default peak refresh rate for a given device. Change this value if you want to prevent
|
|
the framework from using higher refresh rates, even if display modes with higher refresh
|
|
rates are available from hardware composer. Only has an effect if the value is
|
|
non-zero. -->
|
|
<integer name="config_defaultPeakRefreshRate">120</integer>
|
|
|
|
<!-- MMS user agent string -->
|
|
<string name="config_mms_user_agent" translatable="false">motorolag2005G</string>
|
|
<!-- MMS user agent profile url -->
|
|
<string name="config_mms_user_agent_profile_url" translatable="false">http://uaprof.motorola.com/phoneconfig/motov1/Profile/motov1.rdf</string>
|
|
|
|
<!-- Type of the double tap sensor. Empty if double tap is not supported. -->
|
|
<string name="config_dozeDoubleTapSensorType" translatable="false">org.lineageos.sensor.double_tap</string>
|
|
|
|
<!-- Whether the device enable the standalone (SA) mode of 5G NR.-->
|
|
<bool name="config_telephony5gStandalone">true</bool>
|
|
|
|
<!-- Whether the device enable the non-standalone (NSA) mode of 5G NR.-->
|
|
<bool name="config_telephony5gNonStandalone">true</bool>
|
|
</resources>
|