25jiNekogram-de/android_device_tecno_LG8n
3
0
Fork 0
mirror of https://github.com/Anything-at-25-00/android_device_tecno_LG8n.git synced 2024-11-22 21:56:26 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

LG8n: overlay: Rework Overlays

Browse source 
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
This commit is contained in:
Shirayuki39 2024-07-19 19:12:05 +08:00
parent d9a92609ae
commit b03fd12f64
5 changed files with 153 additions and 107 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
device.mk
View file

@ -316,6 +316,7 @@ PRODUCT_PACKAGES += \
CarrierConfigOverlay \ CarrierConfigOverlay \
FrameworksResOverlay \ FrameworksResOverlay \
SettingsResOverlay \ SettingsResOverlay \
SystemUIOverlay \
TelephonyOverlay TelephonyOverlay
# Lineage-Specific Overlays # Lineage-Specific Overlays

179
overlay/FrameworksResOverlay/res/values/config.xml
View file

@ -26,75 +26,39 @@
Software implementation will be used if config_hardware_auto_brightness_available is not set --> Software implementation will be used if config_hardware_auto_brightness_available is not set -->
<bool name="config_automatic_brightness_available">true</bool> <bool name="config_automatic_brightness_available">true</bool>
<!-- Array of hysteresis constraint values for brightening, represented as tenths of a <!-- Array of desired screen brightness in nits corresponding to the lux values
percent. The length of this array is assumed to be one greater than in the config_autoBrightnessLevels array. The display brightness is defined as the measured
config_ambientThresholdLevels. The brightening threshold is calculated as brightness of an all-white image.
lux * (1.0f + CONSTRAINT_VALUE). When the current lux is higher than this threshold,
the screen brightness is recalculated. See the config_ambientThresholdLevels
description for how the constraint value is chosen. -->
<integer-array name="config_ambientBrighteningThresholds">
<item>100</item>
</integer-array>
<!-- Array of hysteresis constraint values for darkening, represented as tenths of a If this is defined then:
percent. The length of this array is assumed to be one greater than - config_autoBrightnessLcdBacklightValues should not be defined
config_ambientThresholdLevels. The darkening threshold is calculated as - config_screenBrightnessNits must be defined
lux * (1.0f - CONSTRAINT_VALUE). When the current lux is lower than this threshold, - config_screenBrightnessBacklight must be defined
the screen brightness is recalculated. See the config_ambientThresholdLevels
description for how the constraint value is chosen. --> This array should have size one greater than the size of the config_autoBrightnessLevels
<integer-array name="config_ambientDarkeningThresholds"> array. The brightness values must be non-negative and non-decreasing. This must be
<item>200</item> overridden in platform specific overlays -->
</integer-array> <integer-array name="config_autoBrightnessLcdBacklightValues">
<!-- An array describing the screen's backlight values corresponding to the brightness <item>8</item>
values in the config_screenBrightnessNits array. --> <item>64</item>
<integer-array name="config_screenBrightnessBacklight"> <item>98</item>
<item>1</item> <item>104</item>
<item>15</item> <item>110</item>
<item>30</item> <item>116</item>
<item>45</item> <item>122</item>
<item>60</item> <item>128</item>
<item>75</item> <item>134</item>
<item>90</item> <item>182</item>
<item>105</item> <item>255</item>
<item>120</item> <item>255</item>
<item>135</item> <item>255</item>
<item>150</item> <item>255</item>
<item>165</item> <item>255</item>
<item>180</item> <item>255</item>
<item>195</item> <item>255</item>
<item>210</item>
<item>225</item>
<item>240</item>
<item>255</item> <item>255</item>
</integer-array> </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>1</item>
<item>15</item>
<item>30</item>
<item>45</item>
<item>60</item>
<item>75</item>
<item>90</item>
<item>105</item>
<item>120</item>
<item>135</item>
<item>150</item>
<item>165</item>
<item>180</item>
<item>195</item>
<item>210</item>
<item>225</item>
<item>240</item>
<item>255</item>
</array>
<!-- Array of light sensor lux values to define our levels for auto backlight brightness <!-- Array of light sensor lux values to define our levels for auto backlight brightness
support. support.
The N entries of this array define N + 1 control points as follows: The N entries of this array define N + 1 control points as follows:
@ -136,26 +100,6 @@
<item>18432</item> <item>18432</item>
</integer-array> </integer-array>
<!-- Array of hysteresis constraint values for brightening, represented as tenths of a
percent. The length of this array is assumed to be one greater than
config_screenThresholdLevels. The brightening threshold is calculated as
screenBrightness * (1.0f + CONSTRAINT_VALUE). When the new screen brightness is higher
than this threshold, it is applied. See the config_screenThresholdLevels description for
how the constraint value is chosen. -->
<integer-array name="config_screenBrighteningThresholds">
<item>100</item>
</integer-array>
<!-- Array of hysteresis constraint values for darkening, represented as tenths of a
percent. The length of this array is assumed to be one greater than
config_screenThresholdLevels. The darkening threshold is calculated as
screenBrightness * (1.0f - CONSTRAINT_VALUE). When the new screen brightness is lower than
this threshold, it is applied. See the config_screenThresholdLevels description for how
the constraint value is chosen. -->
<integer-array name="config_screenDarkeningThresholds">
<item>200</item>
</integer-array>
<!-- Minimum screen brightness setting allowed by power manager. <!-- Minimum screen brightness setting allowed by power manager.
The user is forbidden from setting the brightness below this level. --> The user is forbidden from setting the brightness below this level. -->
<item type="dimen" name="config_screenBrightnessSettingMinimumFloat">0.003921569</item> <item type="dimen" name="config_screenBrightnessSettingMinimumFloat">0.003921569</item>
@ -257,6 +201,18 @@
<!-- Flag specifying whether WFC over IMS is available on device --> <!-- Flag specifying whether WFC over IMS is available on device -->
<bool name="config_device_wfc_ims_available">true</bool> <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 <!-- 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 carrier provisioning. If false: hard disabled. If true: then depends on carrier
provisioning, availability etc --> provisioning, availability etc -->
@ -270,6 +226,10 @@
provisioning, availability etc --> provisioning, availability etc -->
<bool name="config_carrier_volte_available">true</bool> <bool name="config_carrier_volte_available">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>
<!-- Flag specifying whether VoLTE TTY is supported --> <!-- Flag specifying whether VoLTE TTY is supported -->
<bool name="config_carrier_volte_tty_supported">true</bool> <bool name="config_carrier_volte_tty_supported">true</bool>
@ -281,6 +241,9 @@
available on some devices. --> available on some devices. -->
<bool name="config_enableHapticTextHandle">true</bool> <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 --> <!-- Default list of files pinned by the Pinner Service -->
<string-array translatable="false" name="config_defaultPinnerServiceFiles"> <string-array translatable="false" name="config_defaultPinnerServiceFiles">
<item>"/system/framework/framework.jar"</item> <item>"/system/framework/framework.jar"</item>
@ -293,6 +256,23 @@
<item>"/system/bin/surfaceflinger"</item> <item>"/system/bin/surfaceflinger"</item>
</string-array> </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? --> <!-- Should the pinner service pin the Home application? -->
<bool name="config_pinnerHomeApp">true</bool> <bool name="config_pinnerHomeApp">true</bool>
@ -306,8 +286,31 @@
<!-- Pulled from Ren's TrebleDroid Pova 4 Pro overlay --> <!-- Pulled from Ren's TrebleDroid Pova 4 Pro overlay -->
<bool name="config_dozeAfterScreenOff">true</bool> <bool name="config_dozeAfterScreenOff">true</bool>
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool> <integer name="config_defaultPeakRefreshRate">90</integer>
<integer name="config_defaultPeakRefreshRate">121</integer> <integer name="config_defaultRefreshRate">90</integer>
<integer name="config_defaultRefreshRate">121</integer>
<integer name="config_screenBrightnessDoze">5</integer> <integer name="config_screenBrightnessDoze">5</integer>
<!-- Determines whether the shell features all run on another thread. -->
<bool name="config_enableShellMainThread">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">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>
</resources> </resources>

6
overlay/FrameworksResOverlay/res/values/dimens.xml
View file

@ -15,10 +15,6 @@
orientation. If zero, the value of rounded_corner_radius is used. --> orientation. If zero, the value of rounded_corner_radius is used. -->
<dimen name="rounded_corner_radius_bottom">0.0dip</dimen> <dimen name="rounded_corner_radius_bottom">0.0dip</dimen>
<!-- The default height of the status bar used in {@link SystemBarUtils#getStatusBarHeight} to
calculate the status bar height. -->
<dimen name="status_bar_height_default">36.0dip</dimen>
<!-- Height of the status bar. <!-- Height of the status bar.
Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead. Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead.
--> -->
@ -32,5 +28,5 @@
<!-- Height of the status bar in landscape. <!-- Height of the status bar in landscape.
Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead. Do not read this dimen directly. Use {@link SystemBarUtils#getStatusBarHeight} instead.
--> -->
<dimen name="status_bar_height_landscape">28.0dip</dimen> <dimen name="status_bar_height_landscape">26.0dip</dimen>
</resources> </resources>

34
overlay/SystemUIOverlay/res/values/config.xml Executable file
View file

@ -0,0 +1,34 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
/*
** Copyright 2017, 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. -->
<resources>
<!-- Doze: check proximity sensor before pulsing? -->
<bool name="doze_proximity_check_before_pulse">false</bool>
<!-- Doze: does this device support STATE_DOZE? -->
<bool name="doze_display_state_supported">true</bool>
<!-- If not zero, limits the internal screen recorder's framerate to the set value. -->
<integer name="config_screenRecorderMaxFramerate">90</integer>
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool>
</resources>

40
overlay/SystemUIOverlay/res/values/dimens.xml
View file

@ -16,24 +16,36 @@
*/ */
--> -->
<resources> <resources>
<!-- Location on the screen of the center of the fingerprint sensor. For devices with under <!-- Location on the screen of the center of the physical volume up/down buttons -->
display fingerprint sensors, this directly corresponds to the fingerprint sensor's location. <dimen name="physical_volume_down_button_center_screen_location_y">1150px</dimen>
For devices with sensors on the back of the device, this corresponds to the location on the <dimen name="physical_volume_up_button_center_screen_location_y">950px</dimen>
screen directly in front of the sensor.
By default, this is set to @null to use the horizontal center of the screen. -->
<dimen name="physical_fingerprint_sensor_center_screen_location_x">1080px</dimen>
<!-- Location on the screen of the center of the fingerprint sensor. For devices with under <!-- Location on the screen of the center of the physical power button. This is a reasonable
default that should be overridden by device-specific overlays. -->
<dimen name="physical_power_button_center_screen_location_y">1100px</dimen>
<!-- Location on the screen of the center of the fingerprint sensor. For devices with under
display fingerprint sensors, this directly corresponds to the fingerprint sensor's location. display fingerprint sensors, this directly corresponds to the fingerprint sensor's location.
For devices with sensors on the back of the device, this corresponds to the location on the For devices with sensors on the back of the device, this corresponds to the location on the
screen directly in front of the sensor. --> screen directly in front of the sensor. -->
<dimen name="physical_fingerprint_sensor_center_screen_location_y">1100px</dimen> <dimen name="physical_fingerprint_sensor_center_screen_location_y">1100px</dimen>
<!-- Location on the screen of the center of the physical power button. This is a reasonable <!-- Margin on the right side of the system icon group on Keyguard. -->
default that should be overridden by device-specific overlays. --> <dimen name="system_icons_keyguard_padding_end">0dp</dimen>
<dimen name="physical_power_button_center_screen_location_y">1100px</dimen>
<!-- Starting padding for a left-aligned status bar clock -->
<dimen name="rounded_corner_content_padding">47.0px</dimen> <dimen name="status_bar_left_clock_starting_padding">0.0px</dimen>
<dimen name="status_bar_padding_end">4.0dip</dimen>
<dimen name="status_bar_padding_start">4.0dip</dimen> <!-- Margin on the left side of the carrier text on Keyguard -->
<dimen name="keyguard_carrier_text_margin">20dp</dimen>
<!-- Location on the screen of the center of the fingerprint sensor -->
<dimen name="physical_fingerprint_sensor_center_screen_location_x">1080px</dimen>
<!-- The padding on the side of the navigation bar. Must be greater than or equal to
navigation_extra_key_width -->
<dimen name="navigation_side_padding">85.0dip</dimen>
<dimen name="rounded_corner_content_padding">10dp</dimen>
<dimen name="status_bar_padding_end">5dp</dimen>
<dimen name="status_bar_padding_start">16dp</dimen>
</resources> </resources>