diff options
Diffstat (limited to 'common-overlay/frameworks/base/core/res/res/values/config.xml')
| -rw-r--r-- | common-overlay/frameworks/base/core/res/res/values/config.xml | 236 |
1 files changed, 137 insertions, 99 deletions
diff --git a/common-overlay/frameworks/base/core/res/res/values/config.xml b/common-overlay/frameworks/base/core/res/res/values/config.xml index 79b95b2..fcca2b9 100644 --- a/common-overlay/frameworks/base/core/res/res/values/config.xml +++ b/common-overlay/frameworks/base/core/res/res/values/config.xml @@ -1,7 +1,9 @@ <?xml version="1.0" encoding="utf-8"?> <!-- -/* -** Copyright 2011, The Android Open Source Project +/* Copyright (c) 2013, The Linux Foundation. All rights reserved. +** Not a Contribution. +** +** Copyright 2009, 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. @@ -16,39 +18,135 @@ ** limitations under the License. */ --> - <!-- These resources are around just to allow their values to be customized - for different hardware and product builds. --> -<resources> + for different hardware and product builds. Do not translate. --> +<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2"> - <!-- If true, the screen can be rotated via the accelerometer in all 4 - rotations as the default behavior. --> + <!-- Flag indicating whether the surface flinger has limited + alpha compositing functionality in hardware. If set, the window + manager will disable alpha trasformation in animations where not + strictly needed. --> <bool name="config_sf_limitedAlpha">true</bool> - - <bool name="config_allowAllRotations">true</bool> - <!-- Enable lockscreen rotation by default --> - <bool name="config_enableLockScreenRotation">true</bool> + <!-- 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 + be empty. An example would be "usb.*" --> + <string-array translatable="false" name="config_tether_usb_regexs"> + <item>"rndis0"</item> + </string-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> + <!-- List of regexpressions describing the interface (if any) that represent tetherable + WiMAX 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> + </string-array> + + <!-- List of regexpressions describing the interface (if any) that represent tetherable + bluetooth interfaces. If the device doesn't want to support tethering over bluetooth this + should be empty. --> + <string-array translatable="false" name="config_tether_bluetooth_regexs"> + <item>"bt-pan"</item> + </string-array> + + <!-- Boolean indicating whether the wifi chipset has dual frequency band support --> + <bool translatable="false" name="config_wifi_dual_band_support">true</bool> + + <!-- Boolean indicating whether the wifi chipset supports background scanning mechanism. + 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 translatable="false" name="config_wifi_background_scan_support">true</bool> <!-- 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> + <!-- If this is true, the screen will come on when you unplug usb/power/whatever. --> + <bool name="config_unplugTurnsOnScreen">true</bool> + + <!-- If this is true, the screen will fade off. --> + <bool name="config_animateScreenLights">true</bool> + + <!-- If true, the screen can be rotated via the accelerometer in all 4 + rotations as the default behavior. --> + <bool name="config_allowAllRotations">true</bool> + + <!-- Indicate whether the SD card is accessible without removing the battery. --> + <bool name="config_batterySdCardAccessibility">true</bool> + + <!-- Vibrator pattern for feedback about a long screen/key press --> + <integer-array name="config_longPressVibePattern"> + <item>20</item> + <item>40</item> + </integer-array> + + <!-- Vibrator pattern for feedback about touching a virtual key --> + <integer-array name="config_virtualKeyVibePattern"> + <item>0</item> + <item>15</item> + <item>25</item> + <item>35</item> + </integer-array> + + <!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap --> + <integer-array name="config_keyboardTapVibePattern"> + <item>50</item> + </integer-array> + + <!-- Hardware keys present on the device, stored as a bit field. +s 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">64</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">64</integer> + + <!-- 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">20</integer> + <!-- 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: + The N entries of this array define N + 1 control points as follows: + (1-based arrays) - 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 + 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 - Must be overridden in platform specific overlays - --> + 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>6</item> <item>12</item> @@ -73,9 +171,10 @@ </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. - --> + in the config_autoBrightnessLevels array. This array should have size one greater + than the size of the config_autoBrightnessLevels array. + 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>30</item> <item>33</item> @@ -101,9 +200,10 @@ </integer-array> <!-- Array of output values for button 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. - --> + in the config_autoBrightnessLevels array. This array should have size one greater + than the size of the config_autoBrightnessLevels array. + 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_autoBrightnessButtonBacklightValues"> <item>0</item> <item>0</item> @@ -129,9 +229,10 @@ </integer-array> <!-- Array of output values for keyboard 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. - i9300 has no keyboard so all values are zero. + in the config_autoBrightnessLevels array. This array should have size one greater + than the size of the config_autoBrightnessLevels array. + + Note: Galaxy Tab 2 has no keyboard so all values are zero. --> <integer-array name="config_autoBrightnessKeyboardBacklightValues"> <item>0</item> @@ -157,77 +258,14 @@ <item>0</item> </integer-array> - <!-- Minimum screen brightness allowed by the power manager. --> - <integer name="config_screenBrightnessDim">20</integer> - - <!-- 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 - be empty. An example would be "usb.*" --> - <string-array translatable="false" name="config_tether_usb_regexs"> - <item>"rndis0"</item> - </string-array> - - <!-- 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> - </string-array> - - <!-- List of regexpressions describing the interface (if any) that represent tetherable - bluetooth interfaces. If the device doesn't want to support tethering over bluetooth this - should be empty. --> - <string-array translatable="false" name="config_tether_bluetooth_regexs"> - <item>"bt-pan"</item> - </string-array> - - <!-- Boolean indicating whether the wifi chipset has dual frequency band support --> - <bool translatable="false" name="config_wifi_dual_band_support">true</bool> - - <!-- Boolean indicating whether the wifi chipset has background scan support --> - <bool translatable="false" name="config_wifi_background_scan_support">true</bool> - - <!-- Vibrator pattern for feedback about a long screen/key press --> - <integer-array name="config_longPressVibePattern"> - <item>20</item> - <item>40</item> - </integer-array> - - <!-- Vibrator pattern for feedback about touching a virtual key --> - <integer-array name="config_virtualKeyVibePattern"> - <item>0</item> - <item>15</item> - <item>25</item> - <item>35</item> - </integer-array> - - <!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap --> - <integer-array name="config_keyboardTapVibePattern"> - <item>50</item> - </integer-array> - - <!-- Workaround for devices with broken keyboards --> - <bool name="config_forceDisableHardwareKeyboard">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> <!-- Maximum number of supported users --> <integer name="config_multiuserMaximumUsers">5</integer> - <!-- Hardware 'face' 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 - For example, a device with Home, Back and Menu keys would set this - config to 7. --> - <integer name="config_deviceHardwareKeys">0</integer> - - <!-- If this is true, the screen will fade off. --> - <bool name="config_animateScreenLights">false</bool> - - <!-- Indicate whether the SD card is accessible without removing the battery. --> - <bool name="config_batterySdCardAccessibility">true</bool> + <!-- Whether UI for multi user should be shown --> + <bool name="config_enableMultiUserUI">true</bool> </resources> |