Adjust all config from Huawei stock framework res

Tested on POT-LX1 (P Smart 2019) with erofs
This commit is contained in:
Raphael Mounier 2023-03-03 11:36:48 +01:00
parent fe0a5705fc
commit 4c3db2c1f3

View file

@ -45,15 +45,11 @@
Must be overridden in platform specific overlays -->
<integer-array name="config_autoBrightnessLevels">
<item>1</item>
<item>40</item>
<item>100</item>
<item>325</item>
<item>600</item>
<item>1250</item>
<item>2200</item>
<item>4000</item>
<item>10000</item>
<item>8</item>
<item>55</item>
<item>350</item>
<item>1600</item>
<item>2550</item>
</integer-array>
<!-- Array of output values for LCD backlight corresponding to the LUX values
@ -62,35 +58,36 @@
The brightness values must be between 0 and 255 and be non-decreasing.
This must be overridden in platform specific overlays -->
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>11</item> <!-- 0-1 -->
<item>22</item> <!-- 1-40 -->
<item>47</item> <!-- 40-100 -->
<item>61</item> <!-- 100-325 -->
<item>84</item> <!-- 325-600 -->
<item>107</item> <!-- 600-1250 -->
<item>154</item> <!-- 1250-2200 -->
<item>212</item> <!-- 2200-4000 -->
<item>245</item> <!-- 4000-10000 -->
<item>255</item> <!-- 10000+ -->
<item>6</item>
<item>47</item>
<item>150</item>
<item>180</item>
<item>250</item>
<item>255</item>
</integer-array>
<integer name="config_screenBrightnessDark">4</integer>
<!-- Minimum screen brightness allowed by the power manager. -->
<integer name="config_screenBrightnessDim">6</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">1</integer>
<integer name="config_screenBrightnessSettingMinimum">4</integer>
<integer name="config_screenBrightnessSettingDefault">33</integer>
<integer name="config_screenBrightnessSettingMaximum">255</integer>
<!-- Flag indicating whether the we should enable the automatic brightness in Settings.
Software implementation will be used if config_hardware_auto_brightness_available is not set -->
<bool name="config_automatic_brightness_available">true</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 BLE peripheral mode -->
<bool name="config_bluetooth_le_peripheral_mode_supported">false</bool>
<!-- 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_dozeAfterScreenOff">true</bool>
<bool name="config_dozeAfterScreenOff">false</bool>
<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
device from the display on/off state.
@ -106,14 +103,14 @@
to maximize power savings but not all devices support it.
Refer to autosuspend.h for details.
-->
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">true</bool>
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">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>
<bool name="config_suspendWhenScreenOffDueToProximity">false</bool>
<!-- Power Management: Specifies whether to decouple the interactive state of the
device from the display on/off state.
@ -128,13 +125,13 @@
to maximize power savings but not all devices support it.
Refer to power.h for details.
-->
<bool name="config_powerDecoupleInteractiveModeFromDisplay">true</bool>
<bool name="config_powerDecoupleInteractiveModeFromDisplay">false</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">17</integer>
<integer name="config_screenBrightnessDoze">4</integer>
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveNotificationLed">true</bool>
@ -150,9 +147,8 @@
<!-- List of regexpressions describing the interface (if any) that represent tetherable
Wifi interfaces. If the device doesn't want to support tethering over Wifi this
should be empty. An example would be "softap.*" -->
<string-array translatable="false" name="config_tether_wifi_regexs">
<item>"wlan0"</item>
<item>"softap.*"</item>
<string-array translatable="false" name="config_tether_wifi_regexs">
<item>wlan0|ap0</item>
</string-array>
<!-- List of regexpressions describing the interface (if any) that represent tetherable
@ -165,22 +161,21 @@
<!-- Array of allowable ConnectivityManager network types for tethering -->
<!-- Common options are [1, 4] for TYPE_WIFI and TYPE_MOBILE_DUN or
[0,1,5,7] for TYPE_MOBILE, TYPE_WIFI, TYPE_MOBILE_HIPRI and TYPE_BLUETOOTH -->
<integer-array translatable="false" name="config_tether_upstream_types">
<item>0</item>
<integer-array translatable="false" name="config_tether_upstream_types">
<item>1</item>
<item>5</item>
<item>7</item>
<item>0</item>
</integer-array>
<!-- Boolean indicating whether the wifi chipset has dual frequency band support -->
<bool translatable="false" name="config_wifi_dual_band_support">true</bool>
<!-- Is the device capable of hot swapping an UICC Card -->
<bool name="config_hotswapCapable">true</bool>
<bool name="config_hotswapCapable">false</bool>
<!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
in hardware. -->
<bool name="config_setColorTransformAccelerated">true</bool>
<bool name="config_setColorTransformAccelerated">false</bool>
<!-- Flag specifying whether VoLTE is available on device -->
<bool name="config_device_volte_available">true</bool>
@ -202,10 +197,16 @@
This mechanism allows the host to remain in suspend state and the dongle to actively
scan and wake the host when a configured SSID is detected by the dongle. This chipset
capability can provide power savings when wifi needs to be always kept on. -->
<bool name="config_wifi_background_scan_support">true</bool>
<bool name="config_wifi_background_scan_support">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. -->
<!-- New values from POT stock -->
<integer name="config_screenBrightnessForVrSettingDefault">86</integer>
<integer name="config_screenBrightnessForVrSettingMaximum">255</integer>
<integer name="config_screenBrightnessForVrSettingMinimum">79</integer>
</resources>