android/android_device_xiaomi_cupid
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cupid: overlay: Drop brightness backlight/nit mapping

Browse Source 
The max value probably takes HBM into account.
Despite the comment in config_autoBrightnessDisplayValuesNits
stating that these overlays are necessary, neither stock nor
modern pixels set these overlays. So remove the values instead
of guessing nit values :)

Change-Id: I973016599bd87ba1d18ae027a2b3259b346a4c1b
This commit is contained in:
Arian 2024-11-19 22:12:41 +01:00
parent 2ca01d63c2
commit 76c293c0ac
1 changed files with 0 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
overlay/Frameworks/res/values/config.xml
View File

@ -294,27 +294,6 @@
<item>1000.0</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. -->
<integer-array name="config_screenBrightnessBacklight">
<item>1</item>
<item>255</item>
</integer-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>3.0</item>
<item>1000.0</item>
</array>
<!-- Array of ambient lux threshold values. This is used for determining hysteresis constraint
values by calculating the index to use for lookup and then setting the constraint value
to the corresponding value of the array. The new brightening hysteresis constraint value