285 lines
14 KiB
XML
285 lines
14 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
Copyright (C) 2022 The Linux Foundation
|
|
SPDX-License-Identifier: BSD-3-Clause
|
|
-->
|
|
<resources>
|
|
|
|
<!-- <array name="config_availableColorModes"> -->
|
|
<!-- <!-\- ColorDisplayManager.COLOR_MODE_NATURAL -\-> -->
|
|
<!-- <item>0</item> -->
|
|
<!-- <!-\- ColorDisplayManager.COLOR_MODE_BOOSTED -\-> -->
|
|
<!-- <item>1</item> -->
|
|
<!-- <!-\- ColorDisplayManager.COLOR_MODE_SATURATED -\-> -->
|
|
<!-- <item>2</item> -->
|
|
<!-- <!-\- ColorDisplayManager.COLOR_MODE_AUTOMATIC -\-> -->
|
|
<!-- <item>3</item> -->
|
|
<!-- </array> -->
|
|
|
|
<!-- <!-\- Boolean indicating whether the HWC setColorTransform function can be performed efficiently -->
|
|
<!-- in hardware. -\-> -->
|
|
<!-- <bool name="config_setColorTransformAccelerated">true</bool> -->
|
|
|
|
<string name="config_displayLightSensorType">android.sensor.light</string>
|
|
|
|
<!-- Flag indicating whether we should enable the automatic brightness.
|
|
Software implementation will be used if config_hardware_auto_brightness_available is not set -->
|
|
<bool name="config_automatic_brightness_available">true</bool>
|
|
|
|
<!-- Maximum screen brightness allowed by the power manager.
|
|
-2 is invalid so setting will resort to int value specified above.
|
|
Set this to 1.0 for maximum brightness range.
|
|
The user is forbidden from setting the brightness above this level. -->
|
|
<item name="config_screenBrightnessSettingMaximumFloat" format="float" type="dimen">1.0</item>
|
|
|
|
<integer-array name="config_autoBrightnessLevels">
|
|
<item>128</item>
|
|
<item>256</item>
|
|
<item>384</item>
|
|
<item>512</item>
|
|
<item>640</item>
|
|
<item>768</item>
|
|
<item>896</item>
|
|
<item>1024</item>
|
|
<item>2048</item>
|
|
<item>4096</item>
|
|
<item>6144</item>
|
|
<item>8192</item>
|
|
<item>10240</item>
|
|
<item>12288</item>
|
|
<item>14336</item>
|
|
<item>16384</item>
|
|
<item>18432</item>
|
|
</integer-array>
|
|
|
|
<integer-array name="config_autoBrightnessLcdBacklightValues">
|
|
<item>8</item>
|
|
<item>64</item>
|
|
<item>98</item>
|
|
<item>104</item>
|
|
<item>110</item>
|
|
<item>116</item>
|
|
<item>122</item>
|
|
<item>128</item>
|
|
<item>134</item>
|
|
<item>182</item>
|
|
<item>255</item>
|
|
<item>255</item>
|
|
<item>255</item>
|
|
<item>255</item>
|
|
<item>255</item>
|
|
<item>255</item>
|
|
<item>255</item>
|
|
<item>255</item>
|
|
</integer-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">1000</integer>
|
|
<integer name="config_autoBrightnessDarkeningLightDebounce">1000</integer>
|
|
|
|
<!-- Fast brightness animation ramp rate in brightness units per second-->
|
|
<integer name="config_brightness_ramp_rate_fast">500</integer>
|
|
|
|
<!-- Slow brightness animation ramp rate in brightness units per second-->
|
|
<integer name="config_brightness_ramp_rate_slow">270</integer>
|
|
|
|
<!-- 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_defaultPeakRefreshRate">90</integer>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Default strength, in percentage, of bright color reduction when activated. -->
|
|
<integer name="config_reduceBrightColorsStrengthDefault">40</integer>
|
|
|
|
<!-- Minimum strength, in percentage, supported by bright color reduction. -->
|
|
<integer name="config_reduceBrightColorsStrengthMax">50</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.
|
|
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.
|
|
-->
|
|
<string translatable="false" name="config_mainBuiltInDisplayCutout">
|
|
M 0,0
|
|
L -46, 0
|
|
L -10, 26
|
|
L 10, 26
|
|
L 46, 0
|
|
Z
|
|
@dp
|
|
</string>
|
|
|
|
<string translatable="false" name="config_mainBuiltInDisplayCutoutRectApproximation">@string/config_mainBuiltInDisplayCutout</string>
|
|
|
|
<!-- Whether the display cutout region of the main built-in display should be forced to
|
|
black in software (to avoid aliasing or emulate a cutout that is not physically existent).
|
|
-->
|
|
<bool name="config_fillMainBuiltInDisplayCutout">false</bool>
|
|
<!-- 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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- 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>
|
|
|
|
|
|
<!-- Control whether the always on display mode is available. This should only be enabled on
|
|
devices where the display has been tuned to be power efficient in DOZE and/or DOZE_SUSPEND
|
|
states. -->
|
|
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool>
|
|
|
|
<!-- 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" translatable="false">com.android.systemui/com.android.systemui.doze.DozeService</string>
|
|
|
|
<!-- Screen brightness used to dim the screen while dozing in a very low power state.
|
|
May be less than the minimum allowed brightness setting
|
|
that can be set by the user. -->
|
|
<integer name="config_screenBrightnessDoze">17</integer>
|
|
|
|
<!-- Whether a software navigation bar should be shown. NOTE: in the future this may be
|
|
autodetected from the Configuration. -->
|
|
<bool name="config_showNavigationBar">true</bool>
|
|
|
|
<!-- Whether device supports double tap to wake -->
|
|
<bool name="config_supportDoubleTapWake">false</bool>
|
|
|
|
<!-- Whether this device is supporting the camera toggle -->
|
|
<bool name="config_supportsCamToggle">false</bool>
|
|
|
|
<!-- Whether this device is supporting the software microphone toggle -->
|
|
<bool name="config_supportsMicToggle">true</bool>
|
|
|
|
<!-- Whether UI for multi user should be shown -->
|
|
<bool name="config_enableMultiUserUI">true</bool>
|
|
|
|
<!-- When true use the linux /dev/input/event subsystem to detect the switch changes
|
|
on the headphone/microphone jack. When false use the older uevent framework. -->
|
|
<bool name="config_useDevInputEventForAudioJack">true</bool>
|
|
|
|
<!-- Boolean indicating USSD over IMS is allowed.
|
|
If it is not supported due to modem limitations, USSD send over the CS pipe instead.-->
|
|
<bool name="config_allow_ussd_over_ims">true</bool>
|
|
|
|
<!-- Flag specifying whether WFC over IMS is available on device -->
|
|
<bool name="config_device_wfc_ims_available">true</bool>
|
|
|
|
<!-- Flag specifying whether WFC over IMS should be available for carrier: independent of
|
|
carrier provisioning. If false: hard disabled. If true: then depends on carrier
|
|
provisioning, availability etc -->
|
|
<bool name="config_carrier_wfc_ims_available">true</bool>
|
|
|
|
<!-- Flag specifying whether VoLTE is available on device -->
|
|
<bool name="config_device_volte_available">true</bool>
|
|
|
|
<!-- Flag specifying whether VoLTE should be available for carrier: independent of
|
|
carrier provisioning. If false: hard disabled. If true: then depends on carrier
|
|
provisioning, availability etc -->
|
|
<bool name="config_carrier_volte_available">true</bool>
|
|
|
|
<!-- Flag specifying whether VoLTE TTY is supported -->
|
|
<bool name="config_carrier_volte_tty_supported">true</bool>
|
|
|
|
<!-- Flag specifying whether VT is available on device -->
|
|
<bool name="config_device_vt_available">true</bool>
|
|
|
|
<!-- Default list of files pinned by the Pinner Service -->
|
|
<string-array translatable="false" name="config_defaultPinnerServiceFiles">
|
|
<item>"/system/framework/framework.jar"</item>
|
|
<item>"/system/framework/services.jar"</item>
|
|
<item>"/apex/com.android.art/javalib/core-oj.jar"</item>
|
|
<item>"/apex/com.android.art/javalib/core-libart.jar"</item>
|
|
<item>"/system_ext/priv-app/SystemUI/SystemUI.apk"</item>
|
|
<item>"/system/bin/surfaceflinger"</item>
|
|
</string-array>
|
|
|
|
<!-- Should the pinner service pin the Home application? -->
|
|
<bool name="config_pinnerHomeApp">true</bool>
|
|
|
|
<!-- Number of physical SIM slots on the device. This includes both eSIM and pSIM slots, and
|
|
is not necessarily the same as the number of phones/logical modems supported by the device.
|
|
For example, a multi-sim device can have 2 phones/logical modems, but 3 physical slots,
|
|
or a single SIM device can have 1 phones/logical modems, but 2 physical slots (one eSIM
|
|
and one pSIM) -->
|
|
<integer name="config_num_physical_slots">1</integer>
|
|
|
|
<!-- Set to true to add links to Cell Broadcast app from Settings and MMS app. -->
|
|
<bool name="config_cellBroadcastAppLinks">true</bool>
|
|
|
|
<!-- Is the device capable of hot swapping an UICC Card -->
|
|
<bool name="config_hotswapCapable">true</bool>
|
|
|
|
<!-- Whether WiFi display is supported by this device.
|
|
There are many prerequisites for this feature to work correctly.
|
|
Here are a few of them:
|
|
* The WiFi radio must support WiFi P2P.
|
|
* The WiFi radio must support concurrent connections to the WiFi display and
|
|
to an access point.
|
|
* The Audio Server audio_policy_configuration.xml file must specify a rule for
|
|
the "r_submix" remote submix module. This module is used to record and stream system
|
|
audio output to the WiFi display encoder in the media server.
|
|
* The remote submix module "audio.r_submix.default" must be installed on the device.
|
|
* The device must be provisioned with HDCP keys (for protected content).
|
|
-->
|
|
<bool name="config_enableWifiDisplay">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">
|
|
<item>@array/config_sfps_sensor_props_0</item>
|
|
</array>
|
|
|
|
<array name="config_sfps_sensor_props_0">
|
|
<item>local:4627039422300187648</item> <!--item>displayId</item-->
|
|
<item>760</item> <!--item>sensorLocationX</item-->
|
|
<item>660</item> <!--item>sensorLocationY</item-->
|
|
<item>100</item> <!--item>sensorRadius</item-->
|
|
</array>
|
|
|
|
<!-- Indicates whether device has a power button fingerprint sensor. -->
|
|
<bool name="config_is_powerbutton_fps">true</bool>
|
|
</resources>
|