mirror of
https://github.com/AetherDroid/android_device_samsung_universal7570-common.git
synced 2025-09-04 23:47:47 -04:00
universal7870: rework overlay again and move some values to specific
We move more values to specific, some of them related with doze and autobrightness
This commit is contained in:
parent
0db7207b5e
commit
558d7d3353
1 changed files with 92 additions and 249 deletions
|
@ -18,70 +18,33 @@
|
|||
-->
|
||||
|
||||
<resources>
|
||||
|
||||
|
||||
<!-- Array of light sensor LUX values to define our levels for auto backlight brightness support.
|
||||
The N entries of this array define N 1 zones as follows:
|
||||
Zone 0: 0 <= LUX < array[0]
|
||||
Zone 1: array[0] <= LUX < array[1]
|
||||
...
|
||||
Zone N: array[N - 1] <= LUX < array[N]
|
||||
Zone N + 1 array[N] <= LUX < infinity
|
||||
Must be overridden in platform specific overlays -->
|
||||
<integer-array name="config_autoBrightnessLevels">
|
||||
<item>2</item>
|
||||
<item>7</item>
|
||||
<item>15</item>
|
||||
<item>50</item>
|
||||
<item>100</item>
|
||||
<item>200</item>
|
||||
<item>400</item>
|
||||
<item>1000</item>
|
||||
<item>2000</item>
|
||||
<item>3000</item>
|
||||
<item>5000</item>
|
||||
<item>10000</item>
|
||||
</integer-array>
|
||||
|
||||
<!-- Array of output values for LCD backlight corresponding to the LUX values
|
||||
in the config_autoBrightnessLevels array. This array should have size one greater
|
||||
than the size of the config_autoBrightnessLevels array.
|
||||
This must be overridden in platform specific overlays -->
|
||||
<integer-array name="config_autoBrightnessLcdBacklightValues">
|
||||
<item>12</item> <!-- 0-2 -->
|
||||
<item>22</item> <!-- 3-7 -->
|
||||
<item>32</item> <!-- 5-15 -->
|
||||
<item>42</item> <!-- 15-50 -->
|
||||
<item>52</item> <!-- 50-100 -->
|
||||
<item>62</item> <!-- 100-200 -->
|
||||
<item>72</item> <!-- 200-400 -->
|
||||
<item>82</item> <!-- 400-1000 -->
|
||||
<item>96</item> <!-- 1000-2000 -->
|
||||
<item>134</item> <!-- 2000-3000 -->
|
||||
<item>178</item> <!-- 3000-5000 -->
|
||||
<item>225</item> <!-- 5000-10000 -->
|
||||
<item>255</item> <!-- 10000+ -->
|
||||
</integer-array>
|
||||
|
||||
<!-- Screen brightness used to dim the screen when the user activity
|
||||
timeout expires. May be less than the minimum allowed brightness setting
|
||||
that can be set by the user. -->
|
||||
<integer name="config_screenBrightnessDim">56</integer>
|
||||
|
||||
<!-- Default screen brightness setting.
|
||||
Must be in the range specified by minimum and maximum. -->
|
||||
<integer name="config_screenBrightnessSettingDefault">128</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">4</integer>
|
||||
|
||||
<!-- Boolean indicating whether we want button brightness support -->
|
||||
<bool name="config_button_brightness_support">false</bool>
|
||||
|
||||
<!-- Maximum screen brightness allowed by the power manager.
|
||||
The user is forbidden from setting the brightness above this level. -->
|
||||
<integer name="config_screenBrightnessSettingMaximum">255</integer>
|
||||
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
|
||||
<bool name="config_unplugTurnsOnScreen">true</bool>
|
||||
|
||||
<!-- Indicate whether closing the lid causes the device to go to sleep and opening
|
||||
it causes the device to wake up.
|
||||
The default is false. -->
|
||||
<bool name="config_lidControlsSleep">true</bool>
|
||||
|
||||
<!-- Disable lockscreen translucent decor by default -->
|
||||
<bool name="config_enableLockScreenTranslucentDecor">true</bool>
|
||||
|
||||
<!-- 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">
|
||||
<!-- DEFAULT -->
|
||||
<item>"1,1"</item>
|
||||
<!-- MOBILE -->
|
||||
<item>"0,1"</item>
|
||||
<!-- BLUETOOTH -->
|
||||
<item>"7,1"</item>
|
||||
</string-array>
|
||||
|
||||
<!-- List of regexpressions describing the interface (if any) that represent tetherable
|
||||
USB interfaces. If the device doesn't want to support tething over USB this should
|
||||
|
@ -118,23 +81,9 @@
|
|||
<item>9</item>
|
||||
</integer-array>
|
||||
|
||||
<integer-array name="config_data_usage_network_types">
|
||||
<item>0</item>
|
||||
<item>2</item>
|
||||
<item>3</item>
|
||||
<item>4</item>
|
||||
<item>5</item>
|
||||
<item>10</item>
|
||||
<item>12</item>
|
||||
<item>14</item>
|
||||
</integer-array>
|
||||
|
||||
<!-- The default iface on which to monitor data use -->
|
||||
<string name="config_datause_iface" translatable="false">rmnet0</string>
|
||||
|
||||
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
|
||||
<bool name="config_unplugTurnsOnScreen">true</bool>
|
||||
|
||||
<!-- 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 -->
|
||||
|
@ -197,15 +146,21 @@
|
|||
<item>192.168.51.254</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>
|
||||
</string-array>
|
||||
<!-- These resources are around just to allow their values to be customized
|
||||
for different hardware and product builds. -->
|
||||
<string name="config_radio_access_family">GSM | WCDMA | LTE</string>
|
||||
|
||||
<!-- Boolean indicating whether the wifi chipset has dual frequency band support -->
|
||||
<bool translatable="false" name="config_wifi_dual_band_support">false</bool>
|
||||
|
||||
<!-- Boolean indicating whether the wifi chipset has background scan support -->
|
||||
<bool translatable="false" name="config_wifi_background_scan_support">true</bool>
|
||||
|
||||
<!-- Wifi driver supports batched scan -->
|
||||
<bool translatable="false" name="config_wifi_batched_scan_supported">false</bool>
|
||||
|
||||
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
|
||||
<bool name="config_bluetooth_le_peripheral_mode_supported">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 -->
|
||||
|
@ -228,36 +183,9 @@
|
|||
-->
|
||||
<bool name="config_enableWifiDisplay">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">false</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>
|
||||
|
||||
<!-- Indicate whether closing the lid causes the device to go to sleep and opening
|
||||
it causes the device to wake up.
|
||||
The default is false. -->
|
||||
<bool name="config_lidControlsSleep">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>
|
||||
|
||||
<!-- Disable lockscreen translucent decor by default -->
|
||||
<bool name="config_enableLockScreenTranslucentDecor">true</bool>
|
||||
|
||||
<!-- Flag specifying whether WFC over IMS is available on device -->
|
||||
<bool name="config_device_wfc_ims_available">true</bool>
|
||||
|
||||
|
@ -268,49 +196,10 @@
|
|||
|
||||
<!-- Maximum number of supported users -->
|
||||
<integer name="config_multiuserMaximumUsers">4</integer>
|
||||
|
||||
<!-- Whether Multiuser UI should be shown -->
|
||||
<bool name="config_enableMultiUserUI">true</bool>
|
||||
|
||||
<!-- Screen brightness when dozing -->
|
||||
<integer name="config_screenBrightnessDoze">40</integer>
|
||||
|
||||
<!-- Dream of notifications -->
|
||||
<string name="config_dozeComponent">com.android.systemui/com.android.systemui.doze.DozeService</string>
|
||||
<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>
|
||||
|
||||
<!-- Whether the display blanks itself when going from a doze to a non-doze state -->
|
||||
<bool name="config_displayBlanksAfterDoze">true</bool>
|
||||
|
||||
<!-- Specify custom blanking delay of the display -->
|
||||
<integer name="config_screen_off_delay">0</integer>
|
||||
|
||||
<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
|
||||
device from the display on/off state.
|
||||
|
||||
When false, autosuspend_disable() will be called before the display is turned on
|
||||
and autosuspend_enable() will be called after the display is turned off.
|
||||
This mode provides best compatibility for devices using legacy power management
|
||||
features such as early suspend / late resume.
|
||||
|
||||
When true, autosuspend_display() and autosuspend_enable() will be called
|
||||
independently of whether the display is being turned on or off. This mode
|
||||
enables the power manager to suspend the application processor 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 autosuspend.h for details.
|
||||
-->
|
||||
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">true</bool>
|
||||
|
||||
<!-- Power Management: Specifies whether to decouple the interactive state of the
|
||||
device from the display on/off state.
|
||||
|
||||
|
@ -328,34 +217,28 @@
|
|||
|
||||
Refer to power.h for details.
|
||||
-->
|
||||
<bool name="config_powerDecoupleInteractiveModeFromDisplay">true</bool>
|
||||
<bool name="config_powerDecoupleInteractiveModeFromDisplay">false</bool>
|
||||
|
||||
<!-- enable doze powersaving mode -->
|
||||
<!-- 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>
|
||||
|
||||
<!-- Control the behavior when the user long presses the home button.
|
||||
0 - Nothing
|
||||
1 - Recent apps view in SystemUI
|
||||
2 - Launch assist intent
|
||||
This needs to match the constants in
|
||||
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
|
||||
<!-- 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.
|
||||
-->
|
||||
<integer name="config_longPressOnHomeBehavior">2</integer>
|
||||
|
||||
<!-- Control the behavior when the user long presses the menu button.
|
||||
0 - Nothing
|
||||
1 - Recent apps view in SystemUI
|
||||
2 - Launch assist intent
|
||||
This needs to match the constants in
|
||||
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
|
||||
-->
|
||||
<!--<integer name="config_longPressOnMenuBehavior">1</integer>-->
|
||||
|
||||
<!-- Flag indicating if device supports EAP SIM, AKA, AKA' -->
|
||||
<bool name="config_eap_sim_based_auth_supported">true</bool>
|
||||
|
||||
<string-array name="config_mobile_tcp_buffers">
|
||||
<item>lte:1048576,3145728,4194304,524288,1572864,2097152</item>
|
||||
<item>lte:1048576,3145728,4194304,1048576,3145728,4194304</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>
|
||||
</string-array>
|
||||
|
||||
<!-- Values for GPS configuration -->
|
||||
|
@ -368,9 +251,13 @@
|
|||
<item>SUPL_ES=1</item>
|
||||
</string-array>
|
||||
|
||||
<!-- Boolean indicating if restoring network selection should be skipped -->
|
||||
<!-- The restoring is handled by modem if it is true -->
|
||||
<bool translatable="false" name="skip_restoring_network_selection">true</bool>
|
||||
|
||||
<!-- Configure wifi tcp buffersizes in the form:
|
||||
rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max -->
|
||||
<string name="config_wifi_tcp_buffers" translatable="false">524288,1048576,4194304,524288,1048576,4194304</string>
|
||||
<string name="config_wifi_tcp_buffers" translatable="false">524288,1048576,2097152,262144,524288,1048576</string>
|
||||
|
||||
<!-- Flag specifying whether VoLTE & VT is available on device -->
|
||||
<bool name="config_device_volte_available">true</bool>
|
||||
|
@ -386,10 +273,29 @@
|
|||
<!-- Flag specifying whether VoLTE TTY is supported -->
|
||||
<bool name="config_carrier_volte_tty_supported">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>
|
||||
<!-- Flag indicating which package name can access the persistent data partition -->
|
||||
<string name="config_persistentDataPackageName" translatable="false">com.google.android.gms</string>
|
||||
|
||||
<!-- Control the behavior when the user long presses the home button.
|
||||
0 - Nothing
|
||||
1 - Recent apps view in SystemUI
|
||||
2 - Launch assist intent
|
||||
This needs to match the constants in
|
||||
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
|
||||
-->
|
||||
<integer name="config_longPressOnHomeBehavior">2</integer>
|
||||
|
||||
<!-- Control the behavior when the user double-taps the home button.
|
||||
0 - Nothing
|
||||
1 - Menu
|
||||
2 - Recent apps view in SystemUI
|
||||
3 - Launch assist intent
|
||||
4 - Voice Search
|
||||
5 - In-app Search
|
||||
This needs to match the constants in
|
||||
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
|
||||
-->
|
||||
<integer name="config_doubleTapOnHomeBehavior">2</integer>
|
||||
|
||||
<!-- Vibrator pattern for feedback about a long screen/key press -->
|
||||
<integer-array name="config_longPressVibePattern">
|
||||
|
@ -412,92 +318,29 @@
|
|||
<item>40</item>
|
||||
</integer-array>
|
||||
|
||||
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
|
||||
<bool name="config_bluetooth_le_peripheral_mode_supported">false</bool>
|
||||
|
||||
<!-- Max number of scan filters supported by blutooth controller. 0 if the
|
||||
device does not support hardware scan filters-->
|
||||
<integer translatable="false" name="config_bluetooth_max_scan_filters">1</integer>
|
||||
|
||||
<!-- Max number of advertisers supported by bluetooth controller. 0 if the
|
||||
device does not support multiple advertisement-->
|
||||
<integer translatable="false" name="config_bluetooth_max_advertisers">4</integer>
|
||||
|
||||
<!-- Operating volatage for bluetooth controller. -->
|
||||
<integer name="config_bluetooth_operating_voltage_mv">3300</integer>
|
||||
|
||||
<!-- Boolean indicating if current platform supports HFP inband ringing -->
|
||||
<!--<bool name="config_bluetooth_hfp_inband_ringing_support">true</bool>-->
|
||||
|
||||
<!-- Enable overlay for all location components. -->
|
||||
<bool name="config_enableNetworkLocationOverlay" translatable="false">false</bool>
|
||||
<bool name="config_enableFusedLocationOverlay" translatable="false">false</bool>
|
||||
|
||||
<!-- Should the pinner service pin the Camera application? -->
|
||||
<bool name="config_pinnerCameraApp">true</bool>
|
||||
|
||||
<!-- If this is true, device supports Sustained Performance Mode. -->
|
||||
<bool name="config_sustainedPerformanceModeSupported">true</bool>
|
||||
<!-- Display low battery warning when battery level dips to this value.
|
||||
Also, the battery stats are flushed to disk when we hit this level. -->
|
||||
<integer name="config_criticalBatteryWarningLevel">5</integer>
|
||||
|
||||
<!-- Display low battery warning when battery level dips to this value -->
|
||||
<integer name="config_lowBatteryWarningLevel">15</integer>
|
||||
|
||||
<!-- Shutdown if the battery temperature exceeds (this value * 0.1) Celsius. -->
|
||||
<integer name="config_shutdownBatteryTemperature">680</integer>
|
||||
<integer name="config_shutdownBatteryTemperature">600</integer>
|
||||
|
||||
<!-- True if Unprocessed audio source supports the required frequency range and level -->
|
||||
<bool name="config_supportAudioSourceUnprocessed">true</bool>
|
||||
|
||||
<!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
|
||||
in hardware. -->
|
||||
<bool name="config_setColorTransformAccelerated">true</bool>
|
||||
|
||||
<integer translatable="false" name="config_wifi_wakeup_available">1</integer>
|
||||
|
||||
<bool name="config_proxiSensorWakupCheck">true</bool>
|
||||
|
||||
<!-- Allow automatic adjusting of the screen brightness while dozing in low power state. -->
|
||||
<bool name="config_allowAutoBrightnessWhileDozing">false</bool>
|
||||
|
||||
<!-- Enable system navigation keys. -->
|
||||
<bool name="config_supportSystemNavigationKeys">true</bool>
|
||||
|
||||
<!-- Indicate whether the SD card is accessible without removing the battery. -->
|
||||
<bool name="config_batterySdCardAccessibility">true</bool>
|
||||
|
||||
<!-- Hardware keys present on the device, stored as a bit field.
|
||||
This integer should equal the sum of the corresponding value for each
|
||||
of the following keys present:
|
||||
1 - Home
|
||||
2 - Back
|
||||
4 - Menu
|
||||
8 - Assistant (search)
|
||||
16 - App switch
|
||||
32 - Camera
|
||||
64 - Volume rocker
|
||||
For example, a device with Home, Back and Menu keys would set this
|
||||
config to 7. -->
|
||||
<integer name="config_deviceHardwareKeys">83</integer>
|
||||
|
||||
<!-- Hardware keys present on the device with the ability to wake, stored as a bit field.
|
||||
This integer should equal the sum of the corresponding value for each
|
||||
of the following keys present:
|
||||
1 - Home
|
||||
2 - Back
|
||||
4 - Menu
|
||||
8 - Assistant (search)
|
||||
16 - App switch
|
||||
32 - Camera
|
||||
64 - Volume rocker
|
||||
For example, a device with Home, Back and Menu keys would set this
|
||||
config to 7. -->
|
||||
<integer name="config_deviceHardwareWakeKeys">65</integer>
|
||||
|
||||
<!-- Flag indicating whether we should enable smart battery. -->
|
||||
<bool name="config_smart_battery_available">true</bool>
|
||||
|
||||
<!-- Smart charge sysfs node and value for suspend/resume charging and specify support-->
|
||||
<bool name="config_SmartChargingAvailable">true</bool>
|
||||
<string name="config_SmartChargingSysfsNode" translatable="false">/sys/class/power_supply/battery/input_suspend</string>
|
||||
<string name="config_SmartChargingSupspendValue" translatable="false">1</string>
|
||||
<string name="config_SmartChargingResumeValue" translatable="false">0</string>
|
||||
|
||||
</resources>
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue