mirror of
https://github.com/PixelExperience-Devices/device_xiaomi_miatoll.git
synced 2025-08-03 07:06:30 +09:00
sm6250-common: Rearrange common and target device trees
Change-Id: I5ce121204a9ba81d11f30bd1ddf57aeafc6b8f54
This commit is contained in:
@ -50,6 +50,7 @@ TARGET_NO_BOOTLOADER := true
|
||||
TARGET_DISABLED_UBWC := true
|
||||
|
||||
# Display
|
||||
TARGET_SCREEN_DENSITY := 440
|
||||
TARGET_USES_COLOR_METADATA := true
|
||||
TARGET_USES_DISPLAY_RENDER_INTENTS := true
|
||||
TARGET_USES_DRM_PP := true
|
||||
@ -87,7 +88,6 @@ BOARD_MKBOOTIMG_ARGS += --header_version $(BOARD_BOOT_HEADER_VERSION)
|
||||
BOARD_INCLUDE_DTB_IN_BOOTIMG := true
|
||||
|
||||
TARGET_KERNEL_ADDITIONAL_FLAGS += LD=ld.lld AR=llvm-ar NM=llvm-nm STRIP=llvm-strip OBJCOPY=llvm-objcopy OBJDUMP=llvm-objdump
|
||||
TARGET_KERNEL_CONFIG := cust_defconfig
|
||||
TARGET_KERNEL_SOURCE := kernel/xiaomi/sm6250
|
||||
|
||||
BOARD_KERNEL_CMDLINE += androidboot.console=ttyMSM0
|
||||
|
8
atoll.mk
8
atoll.mk
@ -16,6 +16,10 @@ $(call inherit-product, $(SRC_TARGET_DIR)/product/gsi_keys.mk)
|
||||
# Setup dalvik vm configs
|
||||
$(call inherit-product, frameworks/native/build/phone-xhdpi-4096-dalvik-heap.mk)
|
||||
|
||||
# AAPT
|
||||
PRODUCT_AAPT_CONFIG := normal
|
||||
PRODUCT_AAPT_PREF_CONFIG := xxhdpi
|
||||
|
||||
# AID/fs configs
|
||||
PRODUCT_PACKAGES += \
|
||||
fs_config_files
|
||||
@ -250,6 +254,7 @@ PRODUCT_ENFORCE_RRO_TARGETS := *
|
||||
PRODUCT_PACKAGES += \
|
||||
CarrierConfigResCommon \
|
||||
SM6250Frameworks \
|
||||
SM6250SystemUI \
|
||||
TelephonyResCommon \
|
||||
WifiOverlay
|
||||
|
||||
@ -358,6 +363,9 @@ PRODUCT_PACKAGES += \
|
||||
PRODUCT_PACKAGES += \
|
||||
libsensorndkbridge
|
||||
|
||||
# Shipping API level
|
||||
PRODUCT_SHIPPING_API_LEVEL := 29
|
||||
|
||||
# Soong namespaces
|
||||
PRODUCT_SOONG_NAMESPACES += \
|
||||
$(LOCAL_PATH) \
|
||||
|
@ -6,68 +6,285 @@
|
||||
|
||||
<resources>
|
||||
|
||||
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
|
||||
<bool name="config_unplugTurnsOnScreen">true</bool>
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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_ambientThresholdLevels. The brightening threshold is calculated as
|
||||
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>11373</item>
|
||||
<item>5000</item>
|
||||
<item>4333</item>
|
||||
<item>3666</item>
|
||||
<item>3000</item>
|
||||
<item>2760</item>
|
||||
<item>2520</item>
|
||||
<item>2280</item>
|
||||
<item>2040</item>
|
||||
<item>1800</item>
|
||||
<item>800</item>
|
||||
<item>527</item>
|
||||
<item>500</item>
|
||||
<item>470</item>
|
||||
<item>396</item>
|
||||
<item>322</item>
|
||||
<item>248</item>
|
||||
<item>174</item>
|
||||
<item>99</item>
|
||||
<item>99</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_ambientThresholdLevels. The darkening threshold is calculated as
|
||||
lux * (1.0f - CONSTRAINT_VALUE). When the current lux is lower than this threshold,
|
||||
the screen brightness is recalculated. See the config_ambientThresholdLevels
|
||||
description for how the constraint value is chosen. -->
|
||||
<integer-array name="config_ambientDarkeningThresholds">
|
||||
<item>853</item>
|
||||
<item>700</item>
|
||||
<item>683</item>
|
||||
<item>666</item>
|
||||
<item>650</item>
|
||||
<item>640</item>
|
||||
<item>630</item>
|
||||
<item>620</item>
|
||||
<item>610</item>
|
||||
<item>600</item>
|
||||
<item>500</item>
|
||||
<item>500</item>
|
||||
<item>440</item>
|
||||
<item>385</item>
|
||||
<item>348</item>
|
||||
<item>311</item>
|
||||
<item>274</item>
|
||||
<item>237</item>
|
||||
<item>200</item>
|
||||
<item>200</item>
|
||||
</integer-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
|
||||
is the n-th element of config_ambientBrighteningThresholds, and the new darkening
|
||||
hysteresis constraint value is the n-th element of config_ambientDarkeningThresholds.
|
||||
The (zero-based) index is calculated as follows: (MAX is the largest index of the array)
|
||||
condition calculated index
|
||||
value < level[0] 0
|
||||
level[n] <= value < level[n+1] n+1
|
||||
level[MAX] <= value MAX+1 -->
|
||||
<integer-array name="config_ambientThresholdLevels">
|
||||
<item>1</item>
|
||||
<item>2</item>
|
||||
<item>3</item>
|
||||
<item>4</item>
|
||||
<item>5</item>
|
||||
<item>6</item>
|
||||
<item>7</item>
|
||||
<item>8</item>
|
||||
<item>9</item>
|
||||
<item>10</item>
|
||||
<item>20</item>
|
||||
<item>30</item>
|
||||
<item>40</item>
|
||||
<item>50</item>
|
||||
<item>60</item>
|
||||
<item>70</item>
|
||||
<item>80</item>
|
||||
<item>90</item>
|
||||
<item>100</item>
|
||||
</integer-array>
|
||||
|
||||
<!-- 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">4000</integer>
|
||||
|
||||
<!-- Array of desired screen brightness in nits corresponding to the lux values
|
||||
in the config_autoBrightnessLevels array. As with config_screenBrightnessMinimumNits and
|
||||
config_screenBrightnessMaximumNits, 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_autoBrightnessDisplayValuesNits">
|
||||
<item>5</item> <!-- 0 - 1 -->
|
||||
<item>10</item> <!-- 1 - 2 -->
|
||||
<item>18</item> <!-- 2 - 3 -->
|
||||
<item>22</item> <!-- 3 - 4 -->
|
||||
<item>24</item> <!-- 4 - 8 -->
|
||||
<item>31</item> <!-- 8 - 12 -->
|
||||
<item>35</item> <!-- 12 - 20 -->
|
||||
<item>41</item> <!-- 20 - 33 -->
|
||||
<item>48</item> <!-- 33 - 55 -->
|
||||
<item>56</item> <!-- 55 - 90 -->
|
||||
<item>66</item> <!-- 90 - 148 -->
|
||||
<item>80</item> <!-- 148 - 245 -->
|
||||
<item>98</item> <!-- 245 - 403 -->
|
||||
<item>125</item> <!-- 403 - 665 -->
|
||||
<item>162</item> <!-- 665 - 1097 -->
|
||||
<item>208</item> <!-- 1097 - 1808 -->
|
||||
<item>265</item> <!-- 1808 - 2981 -->
|
||||
<item>328</item> <!-- 2981 - 5000 -->
|
||||
<item>450</item> <!-- 5000+ -->
|
||||
</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>1</item>
|
||||
<item>2</item>
|
||||
<item>3</item>
|
||||
<item>4</item>
|
||||
<item>8</item>
|
||||
<item>12</item>
|
||||
<item>20</item>
|
||||
<item>33</item>
|
||||
<item>55</item>
|
||||
<item>90</item>
|
||||
<item>148</item>
|
||||
<item>245</item>
|
||||
<item>403</item>
|
||||
<item>665</item>
|
||||
<item>1097</item>
|
||||
<item>1808</item>
|
||||
<item>2981</item>
|
||||
<item>5000</item>
|
||||
</integer-array>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- Boolean indicating if current platform supports HFP inband ringing -->
|
||||
<bool name="config_bluetooth_hfp_inband_ringing_support">true</bool>
|
||||
|
||||
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
|
||||
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
|
||||
|
||||
<!-- Operating volatage for bluetooth controller. 0 by default-->
|
||||
<integer name="config_bluetooth_operating_voltage_mv">3300</integer>
|
||||
|
||||
<!-- 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>
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
<!-- Flag specifying whether VoLTE is available on device -->
|
||||
<bool name="config_device_volte_available">true</bool>
|
||||
|
||||
<!-- 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>
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- Flag specifying whether or not IMS will use the ImsResolver dynamically -->
|
||||
<bool name="config_dynamic_bind_ims">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
|
||||
@ -80,14 +297,88 @@
|
||||
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>
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
<!-- Whether or not wcg mode should be enabled on this device -->
|
||||
<bool name="config_enableWcgMode">true</bool>
|
||||
|
||||
<!-- Is the device capable of hot swapping an ICC Card -->
|
||||
<bool name="config_hotswapCapable">true</bool>
|
||||
|
||||
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
|
||||
<bool name="config_intrusiveNotificationLed">true</bool>
|
||||
|
||||
<!-- Indicates whether device has a power button fingerprint sensor. -->
|
||||
<bool name="config_is_powerbutton_fps">true</bool>
|
||||
|
||||
<!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap -->
|
||||
<integer-array name="config_keyboardTapVibePattern">
|
||||
<item>40</item>
|
||||
</integer-array>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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.
|
||||
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" translatable="false">
|
||||
M 0,0 H -36 V 102 H 36 V 0 H 0 Z
|
||||
</string>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- Should the pinner service pin the Home application? -->
|
||||
<bool name="config_pinnerHomeApp">true</bool>
|
||||
|
||||
<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
|
||||
device from the display on/off state.
|
||||
@ -124,70 +415,94 @@
|
||||
-->
|
||||
<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>
|
||||
<!-- An array describing the screen's backlight values corresponding to the brightness
|
||||
values in the config_screenBrightnessNits array. -->
|
||||
<integer-array name="config_screenBrightnessBacklight">
|
||||
<item>1</item>
|
||||
<item>255</item>
|
||||
</integer-array>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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 -->
|
||||
<integer-array name="config_screenBrightnessNits">
|
||||
<item>2</item>
|
||||
<item>450</item>
|
||||
</integer-array>
|
||||
|
||||
<!-- Default screen brightness setting
|
||||
Must be in the range specified by minimum and maximum.
|
||||
Equivalent to 67/255 (default for this device) -->
|
||||
<item name="config_screenBrightnessSettingDefaultFloat" format="float" type="dimen">0.26274509804</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>
|
||||
|
||||
<!-- Minimum screen brightness setting allowed by power manager.
|
||||
The user is forbidden from setting the brightness below this level.
|
||||
Equivalent to 1/255. -->
|
||||
<item name="config_screenBrightnessSettingMinimumFloat" format="float" type="dimen">0.0</item>
|
||||
|
||||
<!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
|
||||
in hardware. -->
|
||||
<bool name="config_setColorTransformAccelerated">true</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">
|
||||
<item>@array/config_sfps_sensor_props_0</item>
|
||||
</array>
|
||||
|
||||
<array name="config_sfps_sensor_props_0">
|
||||
<item></item> <!-- displayId -->
|
||||
<item>1080</item> <!-- sensorLocationX -->
|
||||
<item>760</item> <!-- sensorLocationY -->
|
||||
<item>100</item> <!-- sensorRadius -->
|
||||
</array>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- Shutdown if the battery temperature exceeds (this value * 0.1) Celsius. -->
|
||||
<integer name="config_shutdownBatteryTemperature">600</integer>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- Whether the Unprocessed audio source supports the required frequency range and level -->
|
||||
<bool name="config_supportAudioSourceUnprocessed">true</bool>
|
||||
|
||||
<!-- Whether device supports double tap to wake -->
|
||||
<bool name="config_supportDoubleTapWake">true</bool>
|
||||
|
||||
<!-- True if the device supports Sustained Performance Mode-->
|
||||
<bool name="config_sustainedPerformanceModeSupported">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>
|
||||
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
|
||||
<bool name="config_unplugTurnsOnScreen">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>
|
||||
<!-- 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>
|
||||
|
||||
<!-- Vibrator pattern for feedback about touching a virtual key -->
|
||||
<integer-array name="config_virtualKeyVibePattern">
|
||||
@ -197,134 +512,59 @@
|
||||
<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>
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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 -->
|
||||
<!-- 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>
|
||||
|
||||
<!-- 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>
|
||||
<!-- 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>
|
||||
|
||||
</resources>
|
||||
|
22
overlay/SM6250Frameworks/res/values/dimens.xml
Normal file
22
overlay/SM6250Frameworks/res/values/dimens.xml
Normal file
@ -0,0 +1,22 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!--
|
||||
Copyright (C) 2022 The LineageOS Project
|
||||
SPDX-License-Identifier: Apache-2.0
|
||||
-->
|
||||
<resources>
|
||||
|
||||
<!-- Radius of the software rounded corners at the bottom of the display in its natural
|
||||
orientation. If zero, the value of rounded_corner_radius is used. -->
|
||||
<dimen name="rounded_corner_radius_bottom">93px</dimen>
|
||||
|
||||
<!-- Radius of the software rounded corners at the top of the display in its natural
|
||||
orientation. If zero, the value of rounded_corner_radius is used. -->
|
||||
<dimen name="rounded_corner_radius_top">93px</dimen>
|
||||
|
||||
<!-- Height of the status bar in landscape -->
|
||||
<dimen name="status_bar_height_landscape">24dp</dimen>
|
||||
|
||||
<!-- Height of the status bar in portrait -->
|
||||
<dimen name="status_bar_height_portrait">102px</dimen>
|
||||
|
||||
</resources>
|
101
overlay/SM6250Frameworks/res/xml/power_profile.xml
Normal file
101
overlay/SM6250Frameworks/res/xml/power_profile.xml
Normal file
@ -0,0 +1,101 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<device name="Android">
|
||||
<item name="battery.capacity">5020</item>
|
||||
<array name="cpu.clusters.cores">
|
||||
<value>6</value>
|
||||
<value>2</value>
|
||||
</array>
|
||||
<item name="cpu.suspend">4.65</item>
|
||||
<item name="cpu.idle">0.52</item>
|
||||
<item name="cpu.active">1</item>
|
||||
<item name="cpu.cluster_power.cluster0">12.10</item>
|
||||
<item name="cpu.cluster_power.cluster1">16.43</item>
|
||||
<array name="cpu.core_speeds.cluster0">
|
||||
<value>300000</value>
|
||||
<value>576000</value>
|
||||
<value>768000</value>
|
||||
<value>1017600</value>
|
||||
<value>1248000</value>
|
||||
<value>1324800</value>
|
||||
<value>1516800</value>
|
||||
<value>1612800</value>
|
||||
<value>1708800</value>
|
||||
<value>1804800</value>
|
||||
</array>
|
||||
<array name="cpu.core_speeds.cluster1">
|
||||
<value>652800</value>
|
||||
<value>825600</value>
|
||||
<value>979200</value>
|
||||
<value>1113600</value>
|
||||
<value>1267200</value>
|
||||
<value>1555200</value>
|
||||
<value>1708800</value>
|
||||
<value>1843200</value>
|
||||
<value>1900800</value>
|
||||
<value>1996800</value>
|
||||
<value>2112000</value>
|
||||
<value>2208000</value>
|
||||
</array>
|
||||
<array name="cpu.core_power.cluster0">
|
||||
<value>4.2</value>
|
||||
<value>8.28</value>
|
||||
<value>11.99</value>
|
||||
<value>15.06</value>
|
||||
<value>23.81</value>
|
||||
<value>27.99</value>
|
||||
<value>38.22</value>
|
||||
<value>51.99</value>
|
||||
<value>62.37</value>
|
||||
<value>71.82</value>
|
||||
</array>
|
||||
<array name="cpu.core_power.cluster1">
|
||||
<value>11.06</value>
|
||||
<value>23.81</value>
|
||||
<value>35.09</value>
|
||||
<value>44.08</value>
|
||||
<value>73.08</value>
|
||||
<value>87.18</value>
|
||||
<value>134.31</value>
|
||||
<value>192.47</value>
|
||||
<value>216.45</value>
|
||||
<value>257.83</value>
|
||||
<value>289.78</value>
|
||||
<value>337.24</value>
|
||||
</array>
|
||||
<item name="screen.on.display0">82.45</item>
|
||||
<item name="screen.full.display0">242.93</item>
|
||||
<item name="camera.flashlight">245.859</item>
|
||||
<item name="camera.avg">500</item>
|
||||
<item name="video">83.29</item>
|
||||
<item name="audio">37.41</item>
|
||||
<item name="wifi.controller.idle">2</item>
|
||||
<item name="wifi.controller.rx">220</item>
|
||||
<item name="wifi.controller.tx">150</item>
|
||||
<item name="wifi.controller.voltage">3700</item>
|
||||
<item name="modem.controller.sleep">1</item>
|
||||
<item name="modem.controller.idle">1</item>
|
||||
<item name="modem.controller.rx">100</item>
|
||||
<array name="modem.controller.tx">
|
||||
<value>90</value>
|
||||
<value>100</value>
|
||||
<value>110</value>
|
||||
<value>120</value>
|
||||
<value>130</value>
|
||||
</array>
|
||||
<item name="modem.controller.voltage">3700</item>
|
||||
<array name="gps.signalqualitybased">
|
||||
<value>100</value>
|
||||
<value>110</value>
|
||||
</array>
|
||||
<item name="gps.voltage">3700</item>
|
||||
<item name="bluetooth.controller.idle">1</item>
|
||||
<item name="bluetooth.controller.rx">50</item>
|
||||
<item name="bluetooth.controller.tx">50</item>
|
||||
<item name="bluetooth.controller.voltage">3300</item>
|
||||
<item name="radio.active">100</item>
|
||||
<item name="radio.scanning">50</item>
|
||||
<array name="radio.on">
|
||||
<value>7</value>
|
||||
<value>5</value>
|
||||
</array>
|
||||
</device>
|
9
overlay/SM6250SystemUI/Android.bp
Normal file
9
overlay/SM6250SystemUI/Android.bp
Normal file
@ -0,0 +1,9 @@
|
||||
//
|
||||
// Copyright (C) 2022 The LineageOS Project
|
||||
// SPDX-License-Identifier: Apache-2.0
|
||||
//
|
||||
|
||||
runtime_resource_overlay {
|
||||
name: "SM6250SystemUI",
|
||||
vendor: true,
|
||||
}
|
13
overlay/SM6250SystemUI/AndroidManifest.xml
Normal file
13
overlay/SM6250SystemUI/AndroidManifest.xml
Normal file
@ -0,0 +1,13 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!--
|
||||
Copyright (C) 2022 The LineageOS Project
|
||||
SPDX-License-Identifier: Apache-2.0
|
||||
-->
|
||||
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
||||
package="com.android.systemui.xiaomi_sm6250">
|
||||
|
||||
<overlay
|
||||
android:isStatic="true"
|
||||
android:priority="100"
|
||||
android:targetPackage="com.android.systemui" />
|
||||
</manifest>
|
18
overlay/SM6250SystemUI/res/values/dimens.xml
Normal file
18
overlay/SM6250SystemUI/res/values/dimens.xml
Normal file
@ -0,0 +1,18 @@
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!--
|
||||
Copyright (C) 2022 The LineageOS Project
|
||||
SPDX-License-Identifier: Apache-2.0
|
||||
-->
|
||||
<resources>
|
||||
|
||||
<!-- Location on the screen of the center of the fingerprint sensor. -->
|
||||
<dimen name="physical_fingerprint_sensor_center_screen_location_x">1080px</dimen>
|
||||
<dimen name="physical_fingerprint_sensor_center_screen_location_y">760px</dimen>
|
||||
|
||||
<!-- Location on the screen of the center of the physical power button. -->
|
||||
<dimen name="physical_power_button_center_screen_location_y">760px</dimen>
|
||||
|
||||
<!-- Pad content in navbar for rounded corners -->
|
||||
<dimen name="rounded_corner_content_padding">16dp</dimen>
|
||||
|
||||
</resources>
|
Reference in New Issue
Block a user