mirror of
https://github.com/PixelExperience-Devices/device_xiaomi_miatoll.git
synced 2025-08-06 00:33:55 +09:00
331 lines
17 KiB
XML
331 lines
17 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
Copyright (C) 2022 The LineageOS Project
|
|
SPDX-License-Identifier: Apache-2.0
|
|
-->
|
|
|
|
<resources>
|
|
|
|
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
|
|
<bool name="config_unplugTurnsOnScreen">true</bool>
|
|
|
|
<!-- Boolean indicating if restoring network selection should be skipped -->
|
|
<!-- The restoring is handled by modem if it is true-->
|
|
<bool name="skip_restoring_network_selection">true</bool>
|
|
|
|
<!-- Set to true to add links to Cell Broadcast app from Settings and MMS app. -->
|
|
<bool name="config_cellBroadcastAppLinks">true</bool>
|
|
|
|
<!-- Controls the navigation bar interaction mode:
|
|
0: 3 button mode (back, home, overview buttons)
|
|
1: 2 button mode (back, home buttons + swipe up for overview)
|
|
2: gestures only for back, home and overview -->
|
|
<integer name="config_navBarInteractionMode">2</integer>
|
|
|
|
<!-- This string array should be overridden by the device to present a list of network
|
|
attributes. This is used by the connectivity manager to decide which networks can coexist
|
|
based on the hardware -->
|
|
<!-- An Array of "[Connection name],[ConnectivityManager.TYPE_xxxx],
|
|
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
|
|
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
|
|
before automatically restore the default connection. Set -1 if the connection
|
|
does not require auto-restore. -->
|
|
<!-- the 6th element indicates boot-time dependency-met value. -->
|
|
<string-array translatable="false" name="networkAttributes">
|
|
<item>wifi,1,1,1,-1,true</item>
|
|
<item>mobile,0,0,0,-1,true</item>
|
|
<item>mobile_mms,2,0,4,60000,true</item>
|
|
<item>mobile_supl,3,0,2,60000,true</item>
|
|
<item>mobile_dun,4,0,2,60000,true</item>
|
|
<item>mobile_hipri,5,0,3,60000,true</item>
|
|
<item>mobile_fota,10,0,2,60000,true</item>
|
|
<item>mobile_ims,11,0,2,60000,true</item>
|
|
<item>mobile_cbs,12,0,2,60000,true</item>
|
|
<item>bluetooth,7,7,2,-1,true</item>
|
|
<item>mobile_emergency,15,0,5,-1,true</item>
|
|
<item>ethernet,9,9,9,-1,true</item>
|
|
</string-array>
|
|
|
|
<!-- This string array should be overridden by the device to present a list of radio
|
|
attributes. This is used by the connectivity manager to decide which networks can coexist
|
|
based on the hardware -->
|
|
<!-- An Array of "[ConnectivityManager connectionType],
|
|
[# simultaneous connection types]" -->
|
|
<string-array translatable="false" name="radioAttributes">
|
|
<item>"1,1"</item>
|
|
<item>"0,1"</item>
|
|
<item>"7,1"</item>
|
|
</string-array>
|
|
|
|
<!-- Set to true if the wifi display supports compositing content stored
|
|
in gralloc protected buffers. For this to be true, there must exist
|
|
a protected hardware path for surface flinger to composite and send
|
|
protected buffers to the wifi display video encoder.
|
|
If this flag is false, we advise applications not to use protected
|
|
buffers (if possible) when presenting content to a wifi display because
|
|
the content may be blanked.
|
|
This flag controls whether the {@link Display#FLAG_SUPPORTS_PROTECTED_BUFFERS}
|
|
flag is set for wifi displays.
|
|
-->
|
|
<bool name="config_wifiDisplaySupportsProtectedBuffers">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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- 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">12</integer>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Configure mobile tcp buffer sizes in the form:
|
|
rat-name:rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max
|
|
If no value is found for the rat-name in use, the system default will be applied.
|
|
-->
|
|
<string-array name="config_mobile_tcp_buffers">
|
|
<item>5gnr:2097152,6291456,16777216,512000,2097152,8388608</item>
|
|
<item>lte:2097152,4194304,8388608,262144,524288,1048576</item>
|
|
<item>lte_ca:4096,6291456,12582912,4096,1048576,2097152</item>
|
|
<item>umts:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>hspa:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>hsupa:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>hsdpa:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>hspap:4094,87380,1220608,4096,16384,1220608</item>
|
|
<item>edge:4093,26280,35040,4096,16384,35040</item>
|
|
<item>gprs:4092,8760,11680,4096,8760,11680</item>
|
|
<item>evdo:4094,87380,524288,4096,16384,262144</item>
|
|
</string-array>
|
|
|
|
<!-- Flag specifying whether VoLTE is available on device -->
|
|
<bool name="config_device_volte_available">true</bool>
|
|
|
|
<!-- Flag specifying whether VT is available on device -->
|
|
<bool name="config_device_vt_available">true</bool>
|
|
|
|
<!-- Flag specifying whether WFC over IMS is available on device -->
|
|
<bool name="config_device_wfc_ims_available">true</bool>
|
|
|
|
<!-- IWLAN network service package name to bind to by default. If none is specified in an overlay, an
|
|
empty string is passed in -->
|
|
<string name="config_wlan_network_service_package" translatable="false">vendor.qti.iwlan</string>
|
|
|
|
<!-- Telephony qualified networks service package name to bind to by default. -->
|
|
<string name="config_qualified_networks_service_package" translatable="false">vendor.qti.iwlan</string>
|
|
|
|
<!-- Flag specifying whether or not IMS will use the ImsResolver dynamically -->
|
|
<bool name="config_dynamic_bind_ims">true</bool>
|
|
|
|
<!-- Config determines whether to update phone object when voice registration
|
|
state changes. Voice radio tech change will always trigger an update of
|
|
phone object irrespective of this config -->
|
|
<bool name="config_switch_phone_on_voice_reg_state_change">false</bool>
|
|
|
|
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
|
|
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
|
|
|
|
<!-- Boolean indicating if current platform supports HFP inband ringing -->
|
|
<bool name="config_bluetooth_hfp_inband_ringing_support">true</bool>
|
|
|
|
<!-- Flag indicating if the speed up audio on mt call code should be executed -->
|
|
<bool name="config_speed_up_audio_on_mt_calls">true</bool>
|
|
|
|
<!-- Shutdown if the battery temperature exceeds (this value * 0.1) Celsius. -->
|
|
<integer name="config_shutdownBatteryTemperature">600</integer>
|
|
|
|
<!-- Operating volatage for bluetooth controller. 0 by default-->
|
|
<integer name="config_bluetooth_operating_voltage_mv">3300</integer>
|
|
|
|
<!-- Vibrator pattern for feedback about a long screen/key press -->
|
|
<integer-array name="config_longPressVibePattern">
|
|
<item>0</item>
|
|
<item>1</item>
|
|
<item>20</item>
|
|
<item>21</item>
|
|
</integer-array>
|
|
|
|
<!-- Vibrator pattern for feedback about touching a virtual key -->
|
|
<integer-array name="config_virtualKeyVibePattern">
|
|
<item>0</item>
|
|
<item>10</item>
|
|
<item>20</item>
|
|
<item>30</item>
|
|
</integer-array>
|
|
|
|
<!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap -->
|
|
<integer-array name="config_keyboardTapVibePattern">
|
|
<item>40</item>
|
|
</integer-array>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
|
|
<bool name="config_intrusiveNotificationLed">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">2</integer>
|
|
|
|
<!-- Is the device capable of hot swapping an ICC Card -->
|
|
<bool name="config_hotswapCapable">true</bool>
|
|
|
|
<!-- Whether the Unprocessed audio source supports the required frequency range and level -->
|
|
<bool name="config_supportAudioSourceUnprocessed">true</bool>
|
|
|
|
<!-- True if the device supports Sustained Performance Mode-->
|
|
<bool name="config_sustainedPerformanceModeSupported">true</bool>
|
|
|
|
<!-- Whether device supports double tap to wake -->
|
|
<bool name="config_supportDoubleTapWake">true</bool>
|
|
|
|
<!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
|
|
in hardware. -->
|
|
<bool name="config_setColorTransformAccelerated">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>
|
|
|
|
<!-- The default journal mode to use use when Write-Ahead Logging is not active.
|
|
Choices are: OFF, DELETE, TRUNCATE, PERSIST and MEMORY.
|
|
PERSIST may improve performance by reducing how often journal blocks are
|
|
reallocated (compared to truncation) resulting in better data block locality
|
|
and less churn of the storage media.
|
|
The PERSIST mode results in data persisting in the journal beyond the life of
|
|
a transaction, so it interacts poorly with SECURE_DELETE. -->
|
|
<string name="db_default_journal_mode" translatable="false">MEMORY</string>
|
|
|
|
<!-- The database synchronization mode when using the default journal mode.
|
|
FULL is safest and preserves durability at the cost of extra fsyncs.
|
|
NORMAL also preserves durability in non-WAL modes and uses checksums to ensure
|
|
integrity although there is a small chance that an error might go unnoticed.
|
|
Choices are: FULL, NORMAL, OFF. -->
|
|
<string name="db_default_sync_mode" translatable="false">OFF</string>
|
|
|
|
<!-- The database synchronization mode when using Write-Ahead Logging.
|
|
From https://www.sqlite.org/pragma.html#pragma_synchronous:
|
|
WAL mode is safe from corruption with synchronous=NORMAL, and probably DELETE mode is safe
|
|
too on modern filesystems. WAL mode is always consistent with synchronous=NORMAL, but WAL
|
|
mode does lose durability. A transaction committed in WAL mode with
|
|
synchronous=NORMAL might roll back following a power loss or system crash.
|
|
Transactions are durable across application crashes regardless of the synchronous setting
|
|
or journal mode. The synchronous=NORMAL setting is a good choice for most applications
|
|
running in WAL mode.
|
|
Choices are: FULL, NORMAL, OFF. -->
|
|
<string name="db_wal_sync_mode" translatable="false">OFF</string>
|
|
|
|
<!-- Indicate available ColorDisplayManager.COLOR_MODE_xxx. -->
|
|
<integer-array name="config_availableColorModes">
|
|
<item>0</item> <!-- COLOR_MODE_NATURAL -->
|
|
<item>1</item> <!-- COLOR_MODE_BOOSTED -->
|
|
<item>3</item> <!-- COLOR_MODE_AUTOMATIC -->
|
|
</integer-array>
|
|
|
|
<!-- Color mode to use when accessibility transforms are enabled. This color mode must be
|
|
supported by the device, but not necessarily appear in config_availableColorModes. The
|
|
regularly selected color mode will be used if this value is negative. -->
|
|
<integer name="config_accessibilityColorMode">2</integer>
|
|
|
|
<!-- The following two arrays specify which color space to use for display composition when a
|
|
certain color mode is active.
|
|
Composition color spaces are defined in android.view.Display.COLOR_MODE_xxx, and color
|
|
modes are defined in ColorDisplayManager.COLOR_MODE_xxx and
|
|
ColorDisplayManager.VENDOR_COLOR_MODE_xxx.
|
|
The color space COLOR_MODE_DEFAULT (0) lets the system select the most appropriate
|
|
composition color space for currently displayed content. Other values (e.g.,
|
|
COLOR_MODE_SRGB) override system selection; these other color spaces must be supported by
|
|
the device for for display composition.
|
|
If a color mode does not have a corresponding color space specified in this array, the
|
|
currently set composition color space will not be modified.-->
|
|
<integer-array name="config_displayCompositionColorModes">
|
|
<item>0</item> <!-- COLOR_MODE_NATURAL -->
|
|
<item>1</item> <!-- COLOR_MODE_BOOSTED -->
|
|
<item>3</item> <!-- COLOR_MODE_AUTOMATIC -->
|
|
</integer-array>
|
|
<integer-array name="config_displayCompositionColorSpaces">
|
|
<item>0</item> <!-- COLOR_MODE_DEFAULT -->
|
|
<item>0</item> <!-- COLOR_MODE_DEFAULT -->
|
|
<item>9</item> <!-- COLOR_MODE_DISPLAY_P3 -->
|
|
</integer-array>
|
|
|
|
<!-- Whether or not wcg mode should be enabled on this device -->
|
|
<bool name="config_enableWcgMode">true</bool>
|
|
|
|
<!-- Enables or disables haptic effect when the text insertion/selection handle is moved
|
|
manually by the user. Off by default, since the expected haptic feedback may not be
|
|
available on some devices. -->
|
|
<bool name="config_enableHapticTextHandle">true</bool>
|
|
|
|
</resources>
|