diff options
Diffstat (limited to 'overlay/aosp-common/frameworks/base/core/res/res/values/config.xml')
| -rw-r--r-- | overlay/aosp-common/frameworks/base/core/res/res/values/config.xml | 249 |
1 files changed, 0 insertions, 249 deletions
diff --git a/overlay/aosp-common/frameworks/base/core/res/res/values/config.xml b/overlay/aosp-common/frameworks/base/core/res/res/values/config.xml deleted file mode 100644 index 673a541..0000000 --- a/overlay/aosp-common/frameworks/base/core/res/res/values/config.xml +++ /dev/null @@ -1,249 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!-- -/* -** 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. -** 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. Do not translate. --> -<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2"> - - <!-- 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> - - <!-- 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 - 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> - - <!-- 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> - - <!-- Minimum allowable screen brightness to use in a very dark room. - This value sets the floor for the darkest possible auto-brightness - adjustment. It is expected to be somewhat less than the first entry in - config_autoBrightnessLcdBacklightValues so as to allow the user to have - some range of adjustment to dim the screen further than usual in very - dark rooms. The contents of the screen must still be clearly visible - in darkness (although they may not be visible in a bright room). --> - <integer name="config_screenBrightnessDark">5</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 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>6</item> - <item>12</item> - <item>18</item> - <item>28</item> - <item>40</item> - <item>65</item> - <item>100</item> - <item>150</item> - <item>250</item> - <item>350</item> - <item>500</item> - <item>800</item> - <item>1200</item> - <item>1800</item> - <item>3000</item> - <item>6000</item> - <item>12000</item> - <item>24000</item> - <item>36000</item> - <item>42700</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. - 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> - <item>36</item> - <item>40</item> - <item>45</item> - <item>50</item> - <item>55</item> - <item>60</item> - <item>70</item> - <item>80</item> - <item>90</item> - <item>100</item> - <item>120</item> - <item>150</item> - <item>180</item> - <item>200</item> - <item>210</item> - <item>220</item> - <item>230</item> - <item>240</item> - <item>250</item> - </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. - 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> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - </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. - - Note: Galaxy Tab 2 has no keyboard so all values are zero. - --> - <integer-array name="config_autoBrightnessKeyboardBacklightValues"> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - <item>0</item> - </integer-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> - - <!-- Maximum number of supported users --> - <integer name="config_multiuserMaximumUsers">5</integer> - <!-- Whether UI for multi user should be shown --> - <bool name="config_enableMultiUserUI">true</bool> -</resources> |