mirror of
https://github.com/Anything-at-25-00/android_device_tecno_LG8n.git
synced 2024-11-25 23:16:26 -08:00
Shirayuki39
e5c90ec146
* Only for rising because the X Reality engine in rising actually works on LG8n Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
362 lines
18 KiB
XML
362 lines
18 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
/*
|
|
** Copyright 2009, The Android Open Source Project
|
|
**
|
|
** Licensed under the Apache License, Version 2.0 (the "License");
|
|
** you may not use this file except in compliance with the License.
|
|
** You may obtain a copy of the License at
|
|
**
|
|
** http://www.apache.org/licenses/LICENSE-2.0
|
|
**
|
|
** Unless required by applicable law or agreed to in writing, software
|
|
** distributed under the License is distributed on an "AS IS" BASIS,
|
|
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
** See the License for the specific language governing permissions and
|
|
** limitations under the License.
|
|
*/
|
|
-->
|
|
<!-- These resources are around just to allow their values to be customized
|
|
for different hardware and product builds. Do not translate.
|
|
NOTE: The naming convention is "config_camelCaseValue". Some legacy
|
|
entries do not follow the convention, but all new entries should. -->
|
|
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Array of desired screen brightness in nits corresponding to the lux values
|
|
in the config_autoBrightnessLevels array. 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 -->
|
|
<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>
|
|
|
|
<!-- 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>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>
|
|
|
|
<!-- Minimum screen brightness setting allowed by power manager.
|
|
The user is forbidden from setting the brightness below this level. -->
|
|
<item type="dimen" name="config_screenBrightnessSettingMinimumFloat">0.003921569</item>
|
|
|
|
<!-- Maximum screen brightness allowed by the power manager.
|
|
The user is forbidden from setting the brightness above this level. -->
|
|
<item name="config_screenBrightnessSettingMaximumFloat" format="float" type="dimen">1.0</item>
|
|
|
|
<!-- Default screen brightness setting
|
|
Must be in the range specified by minimum and maximum. -->
|
|
<item name="config_screenBrightnessSettingDefaultFloat" format="float" type="dimen">0.4</item>
|
|
|
|
<!-- 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">2000</integer>
|
|
<integer name="config_autoBrightnessDarkeningLightDebounce">3000</integer>
|
|
|
|
<!-- Light sensor event rate in milliseconds for automatic brightness control. -->
|
|
<integer name="config_autoBrightnessLightSensorRate">250</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 name="config_mainBuiltInDisplayCutout">M -24,0 L -24,36 L 24,36 L 24,0 Z @dp</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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- 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">
|
|
<item>0:2:15</item>
|
|
</string-array>
|
|
|
|
<!-- Specifies whether to decouple the auto-suspend state of the device from the display on/off state. -->
|
|
<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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Display settings screen, Color mode options. Must be the same length and order as
|
|
config_color_mode_options_values below. Only the values that also appear in
|
|
frameworks/base/core/res/res/values/config.xml's config_availableColorModes are shown. -->
|
|
<string-array name="config_color_mode_options_strings" translatable="false">
|
|
<item>Natural</item>
|
|
<item>Boosted</item>
|
|
</string-array>
|
|
|
|
<!-- Display settings screen, Color mode options. Must be the same length and order as
|
|
config_color_mode_options_strings above. Only the values that also appear in
|
|
frameworks/base/core/res/res/values/config.xml's config_availableColorModes are shown. -->
|
|
<integer-array name="config_color_mode_options_values">
|
|
<item>0</item>
|
|
<item>1</item>
|
|
</integer-array>
|
|
|
|
<!-- Indicate available ColorDisplayManager.COLOR_MODE_xxx. -->
|
|
<integer-array name="config_availableColorModes">
|
|
<item>0</item>
|
|
<item>1</item>
|
|
</integer-array>
|
|
|
|
<!-- Is the device capable of hot swapping an UICC Card -->
|
|
<bool name="config_hotswapCapable">true</bool>
|
|
|
|
<!-- Whether device supports double tap to wake -->
|
|
<bool name="config_supportDoubleTapWake">true</bool>
|
|
|
|
<!-- Whether device uses power button fingerprint sensor or not -->
|
|
<bool name="config_is_powerbutton_fps">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>
|
|
|
|
<!-- Set this to true to enable the platform's auto-power-save modes like doze and
|
|
app standby. These are not enabled by default because they require a standard
|
|
cloud-to-device messaging service for apps to interact correctly with the modes
|
|
(such as to be able to deliver an instant message to the device even when it is
|
|
dozing). This should be enabled if you have such services and expect apps to
|
|
correctly use them when installed on your device. Otherwise, keep this disabled
|
|
so that applications can still use their own mechanisms. -->
|
|
<bool name="config_enableAutoPowerModes">true</bool>
|
|
|
|
<!-- True if the device supports Sustained Performance Mode -->
|
|
<bool name="config_sustainedPerformanceModeSupported">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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Boolean indicating whether the wifi chipset has dual frequency band support -->
|
|
<bool name="config_wifi_dual_band_support">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>"/system/framework/arm64/boot.oat"</item>
|
|
<item>"/system/framework/arm64/boot-core-libart.oat"</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>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Enable Zram writeback feature to allow unused pages in zram be written to flash. -->
|
|
<bool name="config_zramWriteback">true</bool>
|
|
|
|
<!-- Should the pinner service pin the Home application? -->
|
|
<bool name="config_pinnerHomeApp">true</bool>
|
|
|
|
<!-- Should the pinner service pin the Camera application? -->
|
|
<bool name="config_pinnerCameraApp">false</bool>
|
|
|
|
<!-- Flag indicating whether the surfaceflinger has limited
|
|
alpha compositing functionality in hardware. If set, the window
|
|
manager will disable alpha trasformation in animations where not
|
|
strictly needed. -->
|
|
<bool name="config_sf_limitedAlpha">true</bool>
|
|
<!-- Amount of time in ms the user needs to press the relevant keys to trigger the screenshot chord -->
|
|
<integer name="config_screenshotChordKeyTimeout">0</integer>
|
|
|
|
<!-- Pulled from Ren's TrebleDroid Pova 4 Pro overlay -->
|
|
<bool name="config_dozeAfterScreenOff">true</bool>
|
|
<integer name="config_defaultPeakRefreshRate">90</integer>
|
|
<integer name="config_defaultRefreshRate">90</integer>
|
|
<integer name="config_screenBrightnessDoze">5</integer>
|
|
<!-- Determines whether the shell features all run on another thread. -->
|
|
<bool name="config_enableShellMainThread">true</bool>
|
|
|
|
<!-- List of comma separated package names for which we the system will not show crash like
|
|
tts, etc. dialogs. -->
|
|
<string name="config_appsNotReportingCrashes">com.google.android.tts</string>
|
|
|
|
<!-- The max scale for the wallpaper when it's zoomed in -->
|
|
<item name="config_wallpaperMaxScale" format="float" type="dimen">1</item>
|
|
|
|
<!-- 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>
|
|
|
|
<!-- Whether the always on display mode is available. -->
|
|
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool>
|
|
|
|
<!-- Control whether the always on display mode is enabled by default. This value will be used
|
|
during initialization when the setting is still null. -->
|
|
<bool name="config_dozeAlwaysOnEnabled">false</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></item> <!-- displayId -->
|
|
<item>1080</item> <!-- sensorLocationX -->
|
|
<item>1050</item> <!-- sensorLocationY -->
|
|
<item>210</item> <!-- sensorRadius -->
|
|
</array>
|
|
</resources>
|