config.xml revision 5df82ba65b57ef3458b7211d2b5846fb1351ac3c
1<?xml version="1.0" encoding="utf-8"?> 2<!-- 3/* 4** Copyright 2009, The Android Open Source Project 5** 6** Licensed under the Apache License, Version 2.0 (the "License"); 7** you may not use this file except in compliance with the License. 8** You may obtain a copy of the License at 9** 10** http://www.apache.org/licenses/LICENSE-2.0 11** 12** Unless required by applicable law or agreed to in writing, software 13** distributed under the License is distributed on an "AS IS" BASIS, 14** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 15** See the License for the specific language governing permissions and 16** limitations under the License. 17*/ 18--> 19 20<!-- These resources are around just to allow their values to be customized 21 for different hardware and product builds. Do not translate. --> 22<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2"> 23 <!-- Do not translate. Defines the slots for the right-hand side icons. That is to say, the 24 icons in the status bar that are not notifications. --> 25 <string-array name="config_statusBarIcons"> 26 <item><xliff:g id="id">ime</xliff:g></item> 27 <item><xliff:g id="id">sync_failing</xliff:g></item> 28 <item><xliff:g id="id">sync_active</xliff:g></item> 29 <item><xliff:g id="id">cast</xliff:g></item> 30 <item><xliff:g id="id">location</xliff:g></item> 31 <item><xliff:g id="id">bluetooth</xliff:g></item> 32 <item><xliff:g id="id">nfc</xliff:g></item> 33 <item><xliff:g id="id">tty</xliff:g></item> 34 <item><xliff:g id="id">speakerphone</xliff:g></item> 35 <item><xliff:g id="id">zen</xliff:g></item> 36 <item><xliff:g id="id">mute</xliff:g></item> 37 <item><xliff:g id="id">volume</xliff:g></item> 38 <item><xliff:g id="id">wifi</xliff:g></item> 39 <item><xliff:g id="id">cdma_eri</xliff:g></item> 40 <item><xliff:g id="id">data_connection</xliff:g></item> 41 <item><xliff:g id="id">phone_evdo_signal</xliff:g></item> 42 <item><xliff:g id="id">phone_signal</xliff:g></item> 43 <item><xliff:g id="id">battery</xliff:g></item> 44 <item><xliff:g id="id">alarm_clock</xliff:g></item> 45 <item><xliff:g id="id">secure</xliff:g></item> 46 <item><xliff:g id="id">clock</xliff:g></item> 47 </string-array> 48 49 <!-- Flag indicating whether the surface flinger has limited 50 alpha compositing functionality in hardware. If set, the window 51 manager will disable alpha trasformation in animations where not 52 strictly needed. --> 53 <bool name="config_sf_limitedAlpha">false</bool> 54 55 <!-- Default value used to block data calls if ims is not 56 connected. If you use the ims apn DCT will block 57 any other apn from connecting until ims apn is connected--> 58 <bool name="ImsConnectedDefaultValue">false</bool> 59 60 <!-- Flag indicating whether the surface flinger is inefficient 61 at performing a blur. Used by parts of the UI to turn off 62 the blur effect where it isn't worth the performance hit. 63 As of Honeycomb, blurring is not supported anymore. --> 64 <bool name="config_sf_slowBlur">true</bool> 65 66 <!-- Flag indicating that the media framework should allow changing 67 master volume stream and nothing else . --> 68 <bool name="config_useMasterVolume">false</bool> 69 70 <!-- Flag indicating that the media framework should support playing of sounds on volume 71 key usage. This adds noticeable additional overhead to volume key processing, so 72 is disableable for products for which it is irrelevant. --> 73 <bool name="config_useVolumeKeySounds">true</bool> 74 75 <!-- Array of integer pairs controlling the rate at which the master volume changes 76 in response to volume up and down key events. 77 The first integer of each pair is compared against the current master volume 78 (in range 0 to 100). 79 The last pair with first integer <= the current volume is chosen, 80 and the second integer of the pair indicates the amount to increase the master volume 81 when volume up is pressed. --> 82 <integer-array name="config_masterVolumeRamp"> 83 <item>0</item> <item>5</item> <!-- default: always increase volume by 5% --> 84 </integer-array> 85 86 <!-- The attenuation in dB applied to the sound effects played 87 through AudioManager.playSoundEffect() when no volume is specified. --> 88 <integer name="config_soundEffectVolumeDb">-6</integer> 89 90 <!-- The attenuation in dB applied to the lock/unlock sounds. --> 91 <integer name="config_lockSoundVolumeDb">-6</integer> 92 93 <!-- Flag indicating whether the AUDIO_BECOMING_NOISY notification should 94 be sent during a change to the audio output device. --> 95 <bool name="config_sendAudioBecomingNoisy">true</bool> 96 97 <!-- The duration (in milliseconds) of a short animation. --> 98 <integer name="config_shortAnimTime">200</integer> 99 100 <!-- The duration (in milliseconds) of a medium-length animation. --> 101 <integer name="config_mediumAnimTime">400</integer> 102 103 <!-- The duration (in milliseconds) of a long animation. --> 104 <integer name="config_longAnimTime">500</integer> 105 106 <!-- The duration (in milliseconds) of the activity open/close and fragment open/close animations. --> 107 <integer name="config_activityShortDur">150</integer> 108 <integer name="config_activityDefaultDur">220</integer> 109 110 <!-- Duration for the dim animation behind a dialog. This may be either 111 a percentage, which is relative to the duration of the enter/open 112 animation of the window being shown that is dimming behind, or it may 113 be an integer for a constant duration. --> 114 <fraction name="config_dimBehindFadeDuration">100%</fraction> 115 116 <!-- The maximum width we would prefer dialogs to be. 0 if there is no 117 maximum (let them grow as large as the screen). Actual values are 118 specified for -large and -xlarge configurations. --> 119 <dimen name="config_prefDialogWidth">320dp</dimen> 120 121 <!-- Enables or disables fading edges when marquee is enabled in TextView. 122 Off by default, since the framebuffer readback used to implement the 123 fading edges is prohibitively expensive on most GPUs. --> 124 <bool name="config_ui_enableFadingMarquee">false</bool> 125 126 <!-- Whether dialogs should close automatically when the user touches outside 127 of them. This should not normally be modified. --> 128 <bool name="config_closeDialogWhenTouchOutside">true</bool> 129 130 <!-- Device configuration indicating whether we should avoid using accelerated graphics 131 in certain places to reduce RAM footprint. This is ignored if ro.config.low_ram 132 is true (in that case this is assumed true as well). It can allow you to tune down 133 your device's memory use without going to the point of causing applications to turn 134 off features. --> 135 <bool name="config_avoidGfxAccel">false</bool> 136 137 <!-- Device configuration setting the minfree tunable in the lowmemorykiller in the kernel. 138 A high value will cause the lowmemorykiller to fire earlier, keeping more memory 139 in the file cache and preventing I/O thrashing, but allowing fewer processes to 140 stay in memory. A low value will keep more processes in memory but may cause 141 thrashing if set too low. Overrides the default value chosen by ActivityManager 142 based on screen size and total memory for the largest lowmemorykiller bucket, and 143 scaled proportionally to the smaller buckets. -1 keeps the default. --> 144 <integer name="config_lowMemoryKillerMinFreeKbytesAbsolute">-1</integer> 145 146 <!-- Device configuration adjusting the minfree tunable in the lowmemorykiller in the 147 kernel. A high value will cause the lowmemorykiller to fire earlier, keeping more 148 memory in the file cache and preventing I/O thrashing, but allowing fewer processes 149 to stay in memory. A low value will keep more processes in memory but may cause 150 thrashing if set too low. Directly added to the default value chosen by 151 ActivityManager based on screen size and total memory for the largest lowmemorykiller 152 bucket, and scaled proportionally to the smaller buckets. 0 keeps the default. --> 153 <integer name="config_lowMemoryKillerMinFreeKbytesAdjust">0</integer> 154 155 <!-- Device configuration setting the /proc/sys/vm/extra_free_kbytes tunable in the kernel 156 (if it exists). A high value will increase the amount of memory that the kernel 157 tries to keep free, reducing allocation time and causing the lowmemorykiller to kill 158 earlier. A low value allows more memory to be used by processes but may cause more 159 allocations to block waiting on disk I/O or lowmemorykiller. Overrides the default 160 value chosen by ActivityManager based on screen size. 0 prevents keeping any extra 161 memory over what the kernel keeps by default. -1 keeps the default. --> 162 <integer name="config_extraFreeKbytesAbsolute">-1</integer> 163 164 <!-- Device configuration adjusting the /proc/sys/vm/extra_free_kbytes tunable in the kernel 165 (if it exists). 0 uses the default value chosen by ActivityManager. A positive value 166 will increase the amount of memory that the kernel tries to keep free, reducing 167 allocation time and causing the lowmemorykiller to kill earlier. A negative value 168 allows more memory to be used by processes but may cause more allocations to block 169 waiting on disk I/O or lowmemorykiller. Directly added to the default value chosen by 170 ActivityManager based on screen size. --> 171 <integer name="config_extraFreeKbytesAdjust">0</integer> 172 173 <!-- The duration (in milliseconds) that the radio will scan for a signal 174 when there's no network connection. If the scan doesn't timeout, use zero --> 175 <integer name="config_radioScanningTimeout">0</integer> 176 177 <!-- XXXXX NOTE THE FOLLOWING RESOURCES USE THE WRONG NAMING CONVENTION. 178 Please don't copy them, copy anything else. --> 179 180 <!-- This string array should be overridden by the device to present a list of network 181 attributes. This is used by the connectivity manager to decide which networks can coexist 182 based on the hardware --> 183 <!-- An Array of "[Connection name],[ConnectivityManager.TYPE_xxxx], 184 [associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] --> 185 <!-- the 5th element "resore-time" indicates the number of milliseconds to delay 186 before automatically restore the default connection. Set -1 if the connection 187 does not require auto-restore. --> 188 <!-- the 6th element indicates boot-time dependency-met value. --> 189 <string-array translatable="false" name="networkAttributes"> 190 <item>"wifi,1,1,1,-1,true"</item> 191 <item>"mobile,0,0,0,-1,true"</item> 192 <item>"mobile_mms,2,0,2,60000,true"</item> 193 <item>"mobile_supl,3,0,2,60000,true"</item> 194 <item>"mobile_hipri,5,0,3,60000,true"</item> 195 <item>"mobile_fota,10,0,2,60000,true"</item> 196 <item>"mobile_ims,11,0,2,60000,true"</item> 197 <item>"mobile_cbs,12,0,2,60000,true"</item> 198 <item>"wifi_p2p,13,1,0,-1,true"</item> 199 <item>"mobile_ia,14,0,2,-1,true"</item> 200 <item>"mobile_emergency,15,0,2,-1,true"</item> 201 </string-array> 202 203 <!-- Array of ConnectivityManager.TYPE_xxxx constants for networks that may only 204 be controlled by systemOrSignature apps. --> 205 <integer-array translatable="false" name="config_protectedNetworks"> 206 <item>10</item> 207 <item>11</item> 208 <item>12</item> 209 <item>14</item> 210 <item>15</item> 211 </integer-array> 212 213 <!-- This string array should be overridden by the device to present a list of radio 214 attributes. This is used by the connectivity manager to decide which networks can coexist 215 based on the hardware --> 216 <!-- An Array of "[ConnectivityManager connectionType], 217 [# simultaneous connection types]" --> 218 <string-array translatable="false" name="radioAttributes"> 219 <item>"1,1"</item> 220 <item>"0,1"</item> 221 </string-array> 222 223 <!-- Set of NetworkInfo.getType() that reflect data usage. --> 224 <integer-array translatable="false" name="config_data_usage_network_types"> 225 <item>0</item> <!-- TYPE_MOBILE --> 226 <item>2</item> <!-- TYPE_MOBILE_MMS --> 227 <item>3</item> <!-- TYPE_MOBILE_SUPL --> 228 <item>4</item> <!-- TYPE_MOBILE_DUN --> 229 <item>5</item> <!-- TYPE_MOBILE_HIPRI --> 230 <item>10</item> <!-- TYPE_MOBILE_FOTA --> 231 <item>11</item> <!-- TYPE_MOBILE_IMS --> 232 <item>12</item> <!-- TYPE_MOBILE_CBS --> 233 <item>14</item> <!-- TYPE_MOBILE_IA --> 234 </integer-array> 235 236 <!-- The maximum duration (in milliseconds) we expect a network transition to take --> 237 <integer name="config_networkTransitionTimeout">60000</integer> 238 239 <!-- List of regexpressions describing the interface (if any) that represent tetherable 240 USB interfaces. If the device doesn't want to support tething over USB this should 241 be empty. An example would be "usb.*" --> 242 <string-array translatable="false" name="config_tether_usb_regexs"> 243 </string-array> 244 245 <!-- List of regexpressions describing the interface (if any) that represent tetherable 246 Wifi interfaces. If the device doesn't want to support tethering over Wifi this 247 should be empty. An example would be "softap.*" --> 248 <string-array translatable="false" name="config_tether_wifi_regexs"> 249 </string-array> 250 251 <!-- List of regexpressions describing the interface (if any) that represent tetherable 252 WiMAX interfaces. If the device doesn't want to support tethering over Wifi this 253 should be empty. An example would be "softap.*" --> 254 <string-array translatable="false" name="config_tether_wimax_regexs"> 255 </string-array> 256 257 <!-- List of regexpressions describing the interface (if any) that represent tetherable 258 bluetooth interfaces. If the device doesn't want to support tethering over bluetooth this 259 should be empty. --> 260 <string-array translatable="false" name="config_tether_bluetooth_regexs"> 261 </string-array> 262 263 <!-- Max number of Bluetooth tethering connections allowed. If this is 264 updated config_tether_dhcp_range has to be updated appropriately. --> 265 <integer translateable="false" name="config_max_pan_devices">5</integer> 266 267 <!-- Dhcp range (min, max) to use for tethering purposes --> 268 <string-array translatable="false" name="config_tether_dhcp_range"> 269 </string-array> 270 271 <!-- Regex of wired ethernet ifaces --> 272 <string translatable="false" name="config_ethernet_iface_regex">eth\\d</string> 273 274 <!-- If the mobile hotspot feature requires provisioning, a package name and class name 275 can be provided to launch a supported application that provisions the devices. 276 277 Example Usage: 278 279 String[] appDetails = getStringArray(R.array.config_mobile_hotspot_provision_app); 280 Intent intent = new Intent(Intent.ACTION_MAIN); 281 intent.setClassName(appDetails[0], appDetails[1]); 282 startActivityForResult(intent, 0); 283 284 public void onActivityResult(int requestCode, int resultCode, Intent intent) { 285 super.onActivityResult(requestCode, resultCode, intent); 286 if (requestCode == 0) { 287 if (resultCode == Activity.RESULT_OK) { 288 //Mobile hotspot provisioning successful 289 } else { 290 //Mobile hotspot provisioning failed 291 } 292 } 293 294 See src/com/android/settings/TetherSettings.java for more details. 295 --> 296 <!-- The first element is the package name and the second element is the class name 297 of the provisioning app --> 298 <string-array translatable="false" name="config_mobile_hotspot_provision_app"> 299 <!-- 300 <item>com.example.provisioning</item> 301 <item>com.example.provisioning.Activity</item> 302 --> 303 </string-array> 304 305 <!-- Array of ConnectivityManager.TYPE_xxxx values allowable for tethering --> 306 <!-- Common options are [1, 4] for TYPE_WIFI and TYPE_MOBILE_DUN or 307 <!== [0,1,5,7] for TYPE_MOBILE, TYPE_WIFI, TYPE_MOBILE_HIPRI and TYPE_BLUETOOTH --> 308 <integer-array translatable="false" name="config_tether_upstream_types"> 309 <item>0</item> 310 <item>1</item> 311 <item>5</item> 312 <item>7</item> 313 <item>9</item> 314 </integer-array> 315 316 <!-- If the DUN connection for this CDMA device supports more than just DUN --> 317 <!-- traffic you should list them here. --> 318 <!-- If this device is not CDMA this is ignored. If this list is empty on --> 319 <!-- a DUN-requiring CDMA device, the DUN APN will just support just DUN. --> 320 <string-array translatable="false" name="config_cdma_dun_supported_types"> 321 </string-array> 322 323 <!-- String containing the apn value for tethering. May be overriden by secure settings 324 TETHER_DUN_APN. Value is a comma separated series of strings: 325 "name,apn,proxy,port,username,password,server,mmsc,mmsproxy,mmsport,mcc,mnc,auth,type" 326 note that empty fields can be ommitted: "name,apn,,,,,,,,,310,260,,DUN" --> 327 <string translatable="false" name="config_tether_apndata"></string> 328 329 <!-- Boolean indicating whether the wifi chipset has dual frequency band support --> 330 <bool translatable="false" name="config_wifi_dual_band_support">false</bool> 331 332 <!-- Device type information conforming to Annex B format in WiFi Direct specification. 333 The default represents a dual-mode smartphone --> 334 <string translatable="false" name="config_wifi_p2p_device_type">10-0050F204-5</string> 335 336 <!-- Boolean indicating whether the wifi chipset supports background scanning mechanism. 337 This mechanism allows the host to remain in suspend state and the dongle to actively 338 scan and wake the host when a configured SSID is detected by the dongle. This chipset 339 capability can provide power savings when wifi needs to be always kept on. --> 340 <bool translatable="false" name="config_wifi_background_scan_support">false</bool> 341 342 <!-- Integer indicating wpa_supplicant scan interval in milliseconds --> 343 <integer translatable="false" name="config_wifi_supplicant_scan_interval">15000</integer> 344 345 <!-- Integer indicating wpa_supplicant scan interval when p2p is connected in milliseconds --> 346 <integer translatable="false" name="config_wifi_scan_interval_p2p_connected">60000</integer> 347 348 <!-- Integer indicating the framework scan interval in milliseconds. This is used in the scenario 349 where the chipset does not support background scanning (config_wifi_background_scan_suport 350 is false) to set up a periodic wake up scan so that the device can connect to a new access 351 point on the move. A value of 0 means no periodic scans will be used in the framework. --> 352 <integer translatable="false" name="config_wifi_framework_scan_interval">300000</integer> 353 354 <!-- Integer indicating associated scan interval in milliseconds --> 355 <integer translatable="false" name="config_wifi_framework_associated_scan_interval">10000</integer> 356 357 <!-- Boolean indicating associated scan are allowed --> 358 <bool translatable="false" name="config_wifi_framework_enable_associated_autojoin_scan">true</bool> 359 360 <!-- Boolean indicating associated network selection is allowed --> 361 <bool translatable="false" name="config_wifi_framework_enable_associated_network_selection">true</bool> 362 363 <!-- Boolean indicating that wifi only link configuratios that have exact same credentials (i.e PSK) --> 364 <bool translatable="false" name="config_wifi_only_link_same_credential_configurations">true</bool> 365 366 <!-- Wifi driver stop delay, in milliseconds. 367 Default value is 2 minutes. --> 368 <integer translatable="false" name="config_wifi_driver_stop_delay">120000</integer> 369 370 <!-- Wifi driver supports batched scan --> 371 <bool translatable="false" name="config_wifi_batched_scan_supported">false</bool> 372 373 <!-- Flag indicating whether the we should enable the automatic brightness in Settings. 374 Software implementation will be used if config_hardware_auto_brightness_available is not set --> 375 <bool name="config_automatic_brightness_available">false</bool> 376 377 <!-- Don't name config resources like this. It should look like config_annoyDianne --> 378 <bool name="config_annoy_dianne">true</bool> 379 380 <!-- XXXXXX END OF RESOURCES USING WRONG NAMING CONVENTION --> 381 382 <!-- If this is true, the screen will come on when you unplug usb/power/whatever. --> 383 <bool name="config_unplugTurnsOnScreen">false</bool> 384 385 <!-- Set this true only if the device has separate attention and notification lights. --> 386 <bool name="config_useAttentionLight">false</bool> 387 388 <!-- If this is true, the screen will fade off. --> 389 <bool name="config_animateScreenLights">false</bool> 390 391 <!-- If this is true, key chords can be used to take a screenshot on the device. --> 392 <bool name="config_enableScreenshotChord">true</bool> 393 394 <!-- Auto-rotation behavior --> 395 396 <!-- If true, enables auto-rotation features using the accelerometer. 397 Otherwise, auto-rotation is disabled. Applications may still request 398 to use specific orientations but the sensor is ignored and sensor-based 399 orientations are not available. Furthermore, all auto-rotation related 400 settings are omitted from the system UI. In certain situations we may 401 still use the accelerometer to determine the orientation, such as when 402 docked if the dock is configured to enable the accelerometer. --> 403 <bool name="config_supportAutoRotation">true</bool> 404 405 <!-- If true, the screen can be rotated via the accelerometer in all 4 406 rotations as the default behavior. --> 407 <bool name="config_allowAllRotations">false</bool> 408 409 <!-- If true, the direction rotation is applied to get to an application's requested 410 orientation is reversed. Normally, the model is that landscape is 411 clockwise from portrait; thus on a portrait device an app requesting 412 landscape will cause a clockwise rotation, and on a landscape device an 413 app requesting portrait will cause a counter-clockwise rotation. Setting 414 true here reverses that logic. --> 415 <bool name="config_reverseDefaultRotation">false</bool> 416 417 <!-- Lid switch behavior --> 418 419 <!-- The number of degrees to rotate the display when the keyboard is open. 420 A value of -1 means no change in orientation by default. --> 421 <integer name="config_lidOpenRotation">-1</integer> 422 423 <!-- Indicate whether the lid state impacts the accessibility of 424 the physical keyboard. 0 means it doesn't, 1 means it is accessible 425 when the lid is open, 2 means it is accessible when the lid is 426 closed. The default is 0. --> 427 <integer name="config_lidKeyboardAccessibility">0</integer> 428 429 <!-- Indicate whether the lid state impacts the accessibility of 430 the navigation buttons. 0 means it doesn't, 1 means it is accessible 431 when the lid is open, 2 means it is accessible when the lid is 432 closed. The default is 0. --> 433 <integer name="config_lidNavigationAccessibility">0</integer> 434 435 <!-- Indicate whether closing the lid causes the device to go to sleep and opening 436 it causes the device to wake up. 437 The default is false. --> 438 <bool name="config_lidControlsSleep">false</bool> 439 440 <!-- Desk dock behavior --> 441 442 <!-- The number of degrees to rotate the display when the device is in a desk dock. 443 A value of -1 means no change in orientation by default. --> 444 <integer name="config_deskDockRotation">-1</integer> 445 446 <!-- Control whether being in the desk dock (and powered) always 447 keeps the screen on. By default it stays on when plugged in to 448 AC. 0 will not keep it on; or together 1 to stay on when plugged 449 in to AC and 2 to stay on when plugged in to USB. (So 3 for both.) --> 450 <integer name="config_deskDockKeepsScreenOn">1</integer> 451 452 <!-- Control whether being in the desk dock should enable accelerometer 453 based screen orientation. This defaults to true because it is 454 common for desk docks to be sold in a variety of form factors 455 with different orientations. Since we cannot always tell these docks 456 apart and the docks cannot report their true orientation on their own, 457 we rely on gravity to determine the effective orientation. --> 458 <bool name="config_deskDockEnablesAccelerometer">true</bool> 459 460 <!-- Car dock behavior --> 461 462 <!-- The number of degrees to rotate the display when the device is in a car dock. 463 A value of -1 means no change in orientation by default. --> 464 <integer name="config_carDockRotation">-1</integer> 465 466 <!-- Control whether being in the car dock (and powered) always 467 keeps the screen on. By default it stays on when plugged in to 468 AC. 0 will not keep it on; or together 1 to stay on when plugged 469 in to AC and 2 to stay on when plugged in to USB. (So 3 for both.) --> 470 <integer name="config_carDockKeepsScreenOn">1</integer> 471 472 <!-- Control whether being in the car dock should enable accelerometer based 473 screen orientation. This defaults to true because putting a device in 474 a car dock make the accelerometer more a physical input (like a lid). --> 475 476 <bool name="config_carDockEnablesAccelerometer">true</bool> 477 478 <!-- HDMI behavior --> 479 480 <!-- The number of degrees to rotate the display when the device has HDMI connected 481 but is not in a dock. A value of -1 means no change in orientation by default. 482 Use -1 except on older devices whose Hardware Composer HAL does not 483 provide full support for multiple displays. --> 484 <integer name="config_undockedHdmiRotation">-1</integer> 485 486 <!-- Control the default UI mode type to use when there is no other type override 487 happening. One of the following values (See Configuration.java): 488 1 UI_MODE_TYPE_NORMAL 489 4 UI_MODE_TYPE_TELEVISION 490 5 UI_MODE_TYPE_APPLIANCE 491 6 UI_MODE_TYPE_WATCH 492 Any other values will have surprising consequences. --> 493 <integer name="config_defaultUiModeType">1</integer> 494 495 <!-- Indicate whether to allow the device to suspend when the screen is off 496 due to the proximity sensor. This resource should only be set to true 497 if the sensor HAL correctly handles the proximity sensor as a wake-up source. 498 Otherwise, the device may fail to wake out of suspend reliably. 499 The default is false. --> 500 <bool name="config_suspendWhenScreenOffDueToProximity">false</bool> 501 502 <!-- Control the behavior when the user long presses the power button. 503 0 - Nothing 504 1 - Global actions menu 505 2 - Power off (with confirmation) 506 --> 507 <integer name="config_longPressOnPowerBehavior">1</integer> 508 509 <!-- Control the behavior when the user short presses the power button. 510 0 - Nothing 511 1 - Go to sleep (doze) 512 2 - Really go to sleep (don't doze) 513 3 - Really go to sleep and go home (don't doze) 514 --> 515 <integer name="config_shortPressOnPowerBehavior">1</integer> 516 517 <!-- Package name for default keyguard appwidget [DO NOT TRANSLATE] --> 518 <string name="widget_default_package_name"></string> 519 520 <!-- Class name for default keyguard appwidget [DO NOT TRANSLATE] --> 521 <string name="widget_default_class_name"></string> 522 523 <!-- Indicate whether the SD card is accessible without removing the battery. --> 524 <bool name="config_batterySdCardAccessibility">false</bool> 525 526 <!-- List of file paths for USB host busses to exclude from USB host support. 527 For example, if the first USB bus on the device is used to communicate 528 with the modem or some other restricted hardware, add "/dev/bus/usb/001/" 529 to this list. If this is empty, no parts of the host USB bus will be excluded. 530 --> 531 <string-array name="config_usbHostBlacklist" translatable="false"> 532 </string-array> 533 534 <!-- List of paths to serial ports that are available to the serial manager. 535 for example, /dev/ttyUSB0 536 --> 537 <string-array translatable="false" name="config_serialPorts"> 538 </string-array> 539 540 <!-- Vibrator pattern for feedback about a long screen/key press --> 541 <integer-array name="config_longPressVibePattern"> 542 <item>0</item> 543 <item>1</item> 544 <item>20</item> 545 <item>21</item> 546 </integer-array> 547 548 <!-- Vibrator pattern for feedback about touching a virtual key --> 549 <integer-array name="config_virtualKeyVibePattern"> 550 <item>0</item> 551 <item>10</item> 552 <item>20</item> 553 <item>30</item> 554 </integer-array> 555 556 <!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap --> 557 <integer-array name="config_keyboardTapVibePattern"> 558 <item>40</item> 559 </integer-array> 560 561 <!-- Vibrator pattern for feedback when selecting an hour/minute tick of a Clock --> 562 <integer-array name="config_clockTickVibePattern"> 563 <item>125</item> 564 <item>5</item> 565 </integer-array> 566 567 <!-- Vibrator pattern for feedback when selecting a day/month/year date of a Calendar --> 568 <integer-array name="config_calendarDateVibePattern"> 569 <item>125</item> 570 <item>5</item> 571 </integer-array> 572 573 <!-- Vibrator pattern for feedback about booting with safe mode disabled --> 574 <integer-array name="config_safeModeDisabledVibePattern"> 575 <item>0</item> 576 <item>1</item> 577 <item>20</item> 578 <item>21</item> 579 </integer-array> 580 581 <!-- Vibrator pattern for feedback about booting with safe mode disabled --> 582 <integer-array name="config_safeModeEnabledVibePattern"> 583 <item>0</item> 584 <item>1</item> 585 <item>20</item> 586 <item>21</item> 587 <item>500</item> 588 <item>600</item> 589 </integer-array> 590 591 <!-- Vibrator pattern for feedback about hitting a scroll barrier --> 592 <integer-array name="config_scrollBarrierVibePattern"> 593 <item>0</item> 594 <item>15</item> 595 <item>10</item> 596 <item>10</item> 597 </integer-array> 598 599 <bool name="config_use_strict_phone_number_comparation">false</bool> 600 601 <!-- Display low battery warning when battery level dips to this value. 602 Also, the battery stats are flushed to disk when we hit this level. --> 603 <integer name="config_criticalBatteryWarningLevel">5</integer> 604 605 <!-- Shutdown if the battery temperature exceeds (this value * 0.1) Celsius. --> 606 <integer name="config_shutdownBatteryTemperature">680</integer> 607 608 <!-- Display low battery warning when battery level dips to this value --> 609 <integer name="config_lowBatteryWarningLevel">15</integer> 610 611 <!-- Close low battery warning when battery level reaches the lowBatteryWarningLevel 612 plus this --> 613 <integer name="config_lowBatteryCloseWarningBump">5</integer> 614 615 <!-- Default color for notification LED. --> 616 <color name="config_defaultNotificationColor">#ffffffff</color> 617 618 <!-- Default LED on time for notification LED in milliseconds. --> 619 <integer name="config_defaultNotificationLedOn">500</integer> 620 621 <!-- Default LED off time for notification LED in milliseconds. --> 622 <integer name="config_defaultNotificationLedOff">2000</integer> 623 624 <!-- Default value for led color when battery is low on charge --> 625 <integer name="config_notificationsBatteryLowARGB">0xFFFF0000</integer> 626 627 <!-- Default value for led color when battery is medium charged --> 628 <integer name="config_notificationsBatteryMediumARGB">0xFFFFFF00</integer> 629 630 <!-- Default value for led color when battery is fully charged --> 631 <integer name="config_notificationsBatteryFullARGB">0xFF00FF00</integer> 632 633 <!-- Default value for LED on time when the battery is low on charge in miliseconds --> 634 <integer name="config_notificationsBatteryLedOn">125</integer> 635 636 <!-- Is the notification LED intrusive? Used to decide if there should be a disable option --> 637 <bool name="config_intrusiveNotificationLed">false</bool> 638 639 <!-- Default value for LED off time when the battery is low on charge in miliseconds --> 640 <integer name="config_notificationsBatteryLedOff">2875</integer> 641 642 <!-- Number of notifications to keep in the notification service historical archive --> 643 <integer name="config_notificationServiceArchiveSize">100</integer> 644 645 <!-- Allow the menu hard key to be disabled in LockScreen on some devices --> 646 <bool name="config_disableMenuKeyInLockScreen">false</bool> 647 648 <!-- Don't show lock screen before unlock screen (PIN/pattern/password) --> 649 <bool name="config_enableLockBeforeUnlockScreen">false</bool> 650 651 <!-- Disable lockscreen rotation by default --> 652 <bool name="config_enableLockScreenRotation">false</bool> 653 654 <!-- Enable lockscreen translucent decor by default --> 655 <bool name="config_enableLockScreenTranslucentDecor">true</bool> 656 657 <!-- Enable translucent decor by default --> 658 <bool name="config_enableTranslucentDecor">true</bool> 659 660 <!-- Is the device capable of hot swapping an UICC Card --> 661 <bool name="config_hotswapCapable">false</bool> 662 663 <!-- Enable puk unlockscreen by default. 664 If unlock screen is disabled, the puk should be unlocked through Emergency Dialer --> 665 <bool name="config_enable_puk_unlock_screen">true</bool> 666 667 <!-- Enable emergency call when sim is locked or puk locked. Some countries/carriers do not 668 allow emergency calls to be placed without the IMSI, which is locked in the SIM. 669 If so, this should be set to 'false' in an overlay. --> 670 <bool name="config_enable_emergency_call_while_sim_locked">true</bool> 671 672 <!-- Control the behavior when the user long presses the home button. 673 0 - Nothing 674 1 - Recent apps view in SystemUI 675 2 - Launch assist intent 676 This needs to match the constants in 677 policy/src/com/android/internal/policy/impl/PhoneWindowManager.java 678 --> 679 <integer name="config_longPressOnHomeBehavior">1</integer> 680 681 <!-- Control the behavior when the user double-taps the home button. 682 0 - Nothing 683 1 - Recent apps view in SystemUI 684 This needs to match the constants in 685 policy/src/com/android/internal/policy/impl/PhoneWindowManager.java 686 --> 687 <integer name="config_doubleTapOnHomeBehavior">0</integer> 688 689 <!-- Minimum screen brightness setting allowed by the power manager. 690 The user is forbidden from setting the brightness below this level. --> 691 <integer name="config_screenBrightnessSettingMinimum">10</integer> 692 693 <!-- Maximum screen brightness allowed by the power manager. 694 The user is forbidden from setting the brightness above this level. --> 695 <integer name="config_screenBrightnessSettingMaximum">255</integer> 696 697 <!-- Default screen brightness setting. 698 Must be in the range specified by minimum and maximum. --> 699 <integer name="config_screenBrightnessSettingDefault">102</integer> 700 701 <!-- Screen brightness used to dim the screen while dozing in a very low power state. 702 May be less than the minimum allowed brightness setting 703 that can be set by the user. --> 704 <integer name="config_screenBrightnessDoze">1</integer> 705 706 <!-- Screen brightness used to dim the screen when the user activity 707 timeout expires. May be less than the minimum allowed brightness setting 708 that can be set by the user. --> 709 <integer name="config_screenBrightnessDim">10</integer> 710 711 <!-- Minimum allowable screen brightness to use in a very dark room. 712 This value sets the floor for the darkest possible auto-brightness 713 adjustment. It is expected to be somewhat less than the first entry in 714 config_autoBrightnessLcdBacklightValues so as to allow the user to have 715 some range of adjustment to dim the screen further than usual in very 716 dark rooms. The contents of the screen must still be clearly visible 717 in darkness (although they may not be visible in a bright room). --> 718 <integer name="config_screenBrightnessDark">1</integer> 719 720 <!-- Array of light sensor LUX values to define our levels for auto backlight brightness support. 721 The N entries of this array define N + 1 control points as follows: 722 (1-based arrays) 723 724 Point 1: (0, value[1]): lux <= 0 725 Point 2: (level[1], value[2]): 0 < lux <= level[1] 726 Point 3: (level[2], value[3]): level[2] < lux <= level[3] 727 ... 728 Point N+1: (level[N], value[N+1]): level[N] < lux 729 730 The control points must be strictly increasing. Each control point 731 corresponds to an entry in the brightness backlight values arrays. 732 For example, if LUX == level[1] (first element of the levels array) 733 then the brightness will be determined by value[2] (second element 734 of the brightness values array). 735 736 Spline interpolation is used to determine the auto-brightness 737 backlight values for LUX levels between these control points. 738 739 Must be overridden in platform specific overlays --> 740 <integer-array name="config_autoBrightnessLevels"> 741 </integer-array> 742 743 <!-- Array of output values for LCD backlight corresponding to the LUX values 744 in the config_autoBrightnessLevels array. This array should have size one greater 745 than the size of the config_autoBrightnessLevels array. 746 The brightness values must be between 0 and 255 and be non-decreasing. 747 This must be overridden in platform specific overlays --> 748 <integer-array name="config_autoBrightnessLcdBacklightValues"> 749 </integer-array> 750 751 <!-- Array of output values for button backlight corresponding to the LUX values 752 in the config_autoBrightnessLevels array. This array should have size one greater 753 than the size of the config_autoBrightnessLevels array. 754 The brightness values must be between 0 and 255 and be non-decreasing. 755 This must be overridden in platform specific overlays --> 756 <integer-array name="config_autoBrightnessButtonBacklightValues"> 757 </integer-array> 758 759 <!-- Array of output values for keyboard backlight corresponding to the LUX values 760 in the config_autoBrightnessLevels array. This array should have size one greater 761 than the size of the config_autoBrightnessLevels array. 762 The brightness values must be between 0 and 255 and be non-decreasing. 763 This must be overridden in platform specific overlays --> 764 <integer-array name="config_autoBrightnessKeyboardBacklightValues"> 765 </integer-array> 766 767 <!-- Amount of time it takes for the light sensor to warm up in milliseconds. 768 For this time after the screen turns on, the Power Manager 769 will not debounce light sensor readings --> 770 <integer name="config_lightSensorWarmupTime">0</integer> 771 772 <!-- Enables swipe versus poly-finger touch disambiguation in the KeyboardView --> 773 <bool name="config_swipeDisambiguation">true</bool> 774 775 <!-- Specifies the amount of time to disable virtual keys after the screen is touched 776 in order to filter out accidental virtual key presses due to swiping gestures 777 or taps near the edge of the display. May be 0 to disable the feature. 778 It is recommended that this value be no more than 250 ms. 779 This feature should be disabled for most devices. --> 780 <integer name="config_virtualKeyQuietTimeMillis">0</integer> 781 782 <!-- Component name of the default wallpaper. This will be ImageWallpaper if not 783 specified --> 784 <string name="default_wallpaper_component" translatable="false">@null</string> 785 786 <!-- Component name of the built in wallpaper used to display bitmap wallpapers. This must not be null. --> 787 <string name="image_wallpaper_component" translatable="false">com.android.systemui/com.android.systemui.ImageWallpaper</string> 788 789 <!-- True if WallpaperService is enabled --> 790 <bool name="config_enableWallpaperService">true</bool> 791 792 <!-- Whether to enable network location overlay which allows network 793 location provider to be replaced by an app at run-time. When disabled, 794 only the config_networkLocationProviderPackageName package will be 795 searched for network location provider, otherwise packages whose 796 signature matches the signatures of config_locationProviderPackageNames 797 will be searched, and the service with the highest version number will 798 be picked. Anyone who wants to disable the overlay mechanism can set it 799 to false. 800 --> 801 <bool name="config_enableNetworkLocationOverlay" translatable="false">true</bool> 802 <!-- Package name providing network location support. Used only when 803 config_enableNetworkLocationOverlay is false. --> 804 <string name="config_networkLocationProviderPackageName" translatable="false">@null</string> 805 806 <!-- Whether to enable fused location provider overlay which allows fused 807 location provider to be replaced by an app at run-time. When disabled, 808 only the config_fusedLocationProviderPackageName package will be 809 searched for fused location provider, otherwise packages whose 810 signature matches the signatures of config_locationProviderPackageNames 811 will be searched, and the service with the highest version number will 812 be picked. Anyone who wants to disable the overlay mechanism can set it 813 to false. 814 --> 815 <bool name="config_enableFusedLocationOverlay" translatable="false">true</bool> 816 <!-- Package name providing fused location support. Used only when 817 config_enableFusedLocationOverlay is false. --> 818 <string name="config_fusedLocationProviderPackageName" translatable="false">com.android.location.fused</string> 819 820 <!-- Whether to enable Hardware FLP overlay which allows Hardware FLP to be 821 replaced by an app at run-time. When disabled, only the 822 config_hardwareFlpPackageName package will be searched for Hardware Flp, 823 otherwise packages whose signature matches the signatures of 824 config_locationProviderPackageNames will be searched, and the service 825 with the highest version number will be picked. Anyone who wants to 826 disable the overlay mechanism can set it to false. 827 --> 828 <bool name="config_enableHardwareFlpOverlay" translatable="false">true</bool> 829 <!-- Package name providing Hardware Flp. Used only when 830 config_enableHardwareFlpOverlay is false. --> 831 <string name="config_hardwareFlpPackageName" translatable="false">com.android.location.fused</string> 832 833 <!-- Whether to enable geocoder overlay which allows geocoder to be replaced 834 by an app at run-time. When disabled, only the 835 config_geocoderProviderPackageName package will be searched for 836 geocoder, otherwise packages whose signature matches the signatures of 837 config_locationProviderPackageNames will be searched, and the service 838 with the highest version number will be picked. Anyone who wants to 839 disable the overlay mechanism can set it to false. 840 --> 841 <bool name="config_enableGeocoderOverlay" translatable="false">true</bool> 842 <!-- Package name providing geocoder API support. Used only when 843 config_enableGeocoderOverlay is false. --> 844 <string name="config_geocoderProviderPackageName" translatable="false">@null</string> 845 846 <!-- Whether to enable geofence overlay which allows geofence to be replaced 847 by an app at run-time. When disabled, only the 848 config_geofenceProviderPackageName package will be searched for 849 geofence implementation, otherwise packages whose signature matches the 850 signatures of config_locationProviderPackageNames will be searched, and 851 the service with the highest version number will be picked. Anyone who 852 wants to disable the overlay mechanism can set it to false. 853 --> 854 <bool name="config_enableGeofenceOverlay" translatable="false">true</bool> 855 <!-- Package name providing geofence API support. Used only when 856 config_enableGeofenceOverlay is false. --> 857 <string name="config_geofenceProviderPackageName" translatable="false">@null</string> 858 859 <!-- Whether to enable Hardware Activity-Recognition overlay which allows Hardware 860 Activity-Recognition to be replaced by an app at run-time. When disabled, only the 861 config_activityRecognitionHardwarePackageName package will be searched for 862 its implementation, otherwise packages whose signature matches the 863 signatures of config_locationProviderPackageNames will be searched, and 864 the service with the highest version number will be picked. Anyone who 865 wants to disable the overlay mechanism can set it to false. 866 --> 867 <bool name="config_enableActivityRecognitionHardwareOverlay" translatable="false">true</bool> 868 <!-- Package name providing Hardware Activity-Recognition API support. Used only when 869 config_enableActivityRecognitionHardwareOverlay is false. --> 870 <string name="config_activityRecognitionHardwarePackageName" translatable="false">@null</string> 871 872 <!-- Package name(s) containing location provider support. 873 These packages can contain services implementing location providers, 874 such as the Geocode Provider, Network Location Provider, and 875 Fused Location Provider. They will each be searched for 876 service components implementing these providers. 877 It is strongly recommended that the packages explicitly named 878 below are on the system image, so that they will not map to 879 a 3rd party application. 880 The location framework also has support for installation 881 of new location providers at run-time. The new package does not 882 have to be explicitly listed here, however it must have a signature 883 that matches the signature of at least one package on this list. 884 --> 885 <string-array name="config_locationProviderPackageNames" translatable="false"> 886 <!-- The standard AOSP fused location provider --> 887 <item>com.android.location.fused</item> 888 </string-array> 889 890 <!-- This string array can be overriden to enable test location providers initially. --> 891 <!-- Array of "[locationProviderName],[requiresNetwork], 892 [requiresSatellite],[requiresCell],[hasMonetaryCost], 893 [supportAltitute],[supportsSpeed],[supportsBearing], 894 [powerRequirement],[accuracy]" --> 895 <!-- powerRequirement is defined in android.location.Criteria 896 0 = NO_REQUIREMENT / 1 = POWER_LOW / 2 = POWER_MEDIUM / 3 = POWER_HIGH --> 897 <!-- accuracy is defined in anroid.location.Criteria 898 1 = ACCURACY_FINE / 2 = ACCURACY_COARSE --> 899 <string-array name="config_testLocationProviders" translatable="false"> 900 <!-- Example test network location provider 901 <item>network,false,false,false,false,true,true,true,1,2</item> 902 --> 903 </string-array> 904 905 <!-- Boolean indicating if current platform supports bluetooth SCO for off call 906 use cases --> 907 <bool name="config_bluetooth_sco_off_call">true</bool> 908 909 <!-- Boolean indicating if current platform supports bluetooth wide band 910 speech --> 911 <bool name="config_bluetooth_wide_band_speech">true</bool> 912 913 <!-- Boolean indicating if current platform need do one-time bluetooth address 914 re-validation --> 915 <bool name="config_bluetooth_address_validation">false</bool> 916 917 <!-- Boolean indicating if current platform supports BLE peripheral mode --> 918 <bool name="config_bluetooth_le_peripheral_mode_supported">false</bool> 919 920 <!-- Max number of scan filters supported by blutooth controller. 0 if the 921 device does not support hardware scan filters--> 922 <integer translatable="false" name="config_bluetooth_max_scan_filters">0</integer> 923 924 <!-- Max number of advertisers supported by bluetooth controller. 0 if the 925 device does not support multiple advertisement--> 926 <integer translatable="false" name="config_bluetooth_max_advertisers">0</integer> 927 928 <!-- The default data-use polling period. --> 929 <integer name="config_datause_polling_period_sec">600</integer> 930 931 <!-- The default data-use threshold in bytes. 0 disables--> 932 <integer name="config_datause_threshold_bytes">0</integer> 933 934 <!-- The default reduced-datarate value in kilobits per sec --> 935 <integer name="config_datause_throttle_kbitsps">300</integer> 936 937 <!-- The default iface on which to monitor data use --> 938 <string name="config_datause_iface" translatable="false">rmnet0</string> 939 940 <!-- The default reduced-datarate notification mask --> 941 <!-- 2 means give warning --> 942 <integer name="config_datause_notification_type">2</integer> 943 944 <!-- If Voice Radio Technology is RIL_RADIO_TECHNOLOGY_LTE:14 this is the value 945 that should be used instead. A value of RIL_RADIO_TECHNOLOGY_UNKNOWN:0 means 946 there is no replacement value and VoLTE is assumed to be supported --> 947 <integer name="config_volte_replacement_rat">0</integer> 948 949 <!-- Flag indicating whether the current device is "voice capable". 950 If true, this means that the device supports circuit-switched 951 (i.e. voice) phone calls over the telephony network, and is 952 allowed to display the in-call UI while a cellular voice call is 953 active. This can be overridden to false for "data only" devices 954 which can't make voice calls and don't support any in-call UI. 955 956 Note: this flag is subtly different from the 957 PackageManager.FEATURE_TELEPHONY system feature, which is 958 available on *any* device with a telephony radio, even if the 959 device is data-only. --> 960 <bool name="config_voice_capable">true</bool> 961 962 <!-- Flag indicating whether the current device allows sms service. 963 If true, this means that the device supports both sending and 964 receiving sms via the telephony network. 965 This can be overridden to false for "data only" devices 966 which can't send and receive sms message. 967 968 Note: Disable SMS also disable voicemail waiting sms, 969 cell broadcasting sms, and MMS. --> 970 <bool name="config_sms_capable">true</bool> 971 972 <!-- Default SMS Application. This will be the default SMS application when 973 the phone first boots. The user can then change the default app to oe 974 of their choosing. 975 This can be overridden for devices where a different default SMS 976 application is desired. --> 977 <string name="default_sms_application" translatable="false">com.android.mms</string> 978 979 <!-- Enable/disable default bluetooth profiles: 980 HSP_AG, ObexObjectPush, Audio, NAP --> 981 <bool name="config_bluetooth_default_profiles">true</bool> 982 983 <!-- IP address of the dns server to use if nobody else suggests one --> 984 <string name="config_default_dns_server" translatable="false">8.8.8.8</string> 985 986 <!-- The default mobile provisioning apn. Empty by default, maybe overridden by 987 an mcc/mnc specific config.xml --> 988 <string name="mobile_provisioning_apn" translatable="false"></string> 989 990 <!-- The default mobile provisioning url. Empty by default, maybe overridden by 991 an mcc/mnc specific config.xml --> 992 <string name="mobile_provisioning_url" translatable="false"></string> 993 994 <!-- This url is used as the default url when redirection is detected. Any 995 should work as all url's get redirected. But maybe overridden by 996 if needed. --> 997 <string name="mobile_redirected_provisioning_url" translatable="false">http://google.com</string> 998 999 <!-- The default character set for GsmAlphabet --> 1000 <!-- Empty string means MBCS is not considered --> 1001 <string name="gsm_alphabet_default_charset" translatable="false"></string> 1002 1003 <!-- Enables SIP on WIFI only --> 1004 <bool name="config_sip_wifi_only">false</bool> 1005 1006 <!-- Enables built-in SIP phone capability --> 1007 <bool name="config_built_in_sip_phone">true</bool> 1008 1009 <!-- Boolean indicating if restoring network selection should be skipped --> 1010 <!-- The restoring is handled by modem if it is true--> 1011 <bool translatable="false" name="skip_restoring_network_selection">false</bool> 1012 1013 <!-- Maximum number of database connections opened and managed by framework layer 1014 to handle queries on each database when using Write-Ahead Logging. --> 1015 <integer name="db_connection_pool_size">4</integer> 1016 1017 <!-- The default journal mode to use use when Write-Ahead Logging is not active. 1018 Choices are: OFF, DELETE, TRUNCATE, PERSIST and MEMORY. 1019 PERSIST may improve performance by reducing how often journal blocks are 1020 reallocated (compared to truncation) resulting in better data block locality 1021 and less churn of the storage media. --> 1022 <string name="db_default_journal_mode">PERSIST</string> 1023 1024 <!-- Maximum size of the persistent journal file in bytes. 1025 If the journal file grows to be larger than this amount then SQLite will 1026 truncate it after committing the transaction. --> 1027 <integer name="db_journal_size_limit">524288</integer> 1028 1029 <!-- The database synchronization mode when using the default journal mode. 1030 FULL is safest and preserves durability at the cost of extra fsyncs. 1031 NORMAL also preserves durability in non-WAL modes and uses checksums to ensure 1032 integrity although there is a small chance that an error might go unnoticed. 1033 Choices are: FULL, NORMAL, OFF. --> 1034 <string name="db_default_sync_mode">FULL</string> 1035 1036 <!-- The database synchronization mode when using Write-Ahead Logging. 1037 FULL is safest and preserves durability at the cost of extra fsyncs. 1038 NORMAL sacrifices durability in WAL mode because syncs are only performed before 1039 and after checkpoint operations. If checkpoints are infrequent and power loss 1040 occurs, then committed transactions could be lost and applications might break. 1041 Choices are: FULL, NORMAL, OFF. --> 1042 <string name="db_wal_sync_mode">FULL</string> 1043 1044 <!-- The Write-Ahead Log auto-checkpoint interval in database pages (typically 1 to 4KB). 1045 The log is checkpointed automatically whenever it exceeds this many pages. 1046 When a database is reopened, its journal mode is set back to the default 1047 journal mode, which may cause a checkpoint operation to occur. Checkpoints 1048 can also happen at other times when transactions are committed. 1049 The bigger the WAL file, the longer a checkpoint operation takes, so we try 1050 to keep the WAL file relatively small to avoid long delays. 1051 The size of the WAL file is also constrained by 'db_journal_size_limit'. --> 1052 <integer name="db_wal_autocheckpoint">100</integer> 1053 1054 <!-- Max space (in MB) allocated to DownloadManager to store the downloaded 1055 files if they are to be stored in DownloadManager's data dir, 1056 which typically is /data/data/com.android.providers.downloads/files --> 1057 <integer name="config_downloadDataDirSize">200</integer> 1058 1059 <!-- Max number of downloads allowed to proceed concurrently --> 1060 <integer name="config_MaxConcurrentDownloadsAllowed">5</integer> 1061 1062 <!-- When the free space available in DownloadManager's data dir falls 1063 below the percentage value specified by this param, DownloadManager 1064 starts removing files to try to make percentage of available 1065 free space above this threshold value. --> 1066 <integer name="config_downloadDataDirLowSpaceThreshold">10</integer> 1067 1068 <!-- The URL that should be sent in an x-wap-profile header with an HTTP request, 1069 as defined in the Open Mobile Alliance User Agent Profile specification 1070 OMA-TS-UAProf-V2_0-20060206-A Section 8.1.1.1. If the URL contains a '%s' 1071 format string then that substring will be replaced with the value of 1072 Build.MODEL. The format string shall not be escaped. --> 1073 <string name="config_useragentprofile_url" translatable="false"></string> 1074 1075 <!-- When a database query is executed, the results retuned are paginated 1076 in pages of size (in KB) indicated by this value --> 1077 <integer name="config_cursorWindowSize">2048</integer> 1078 1079 <!-- Sets whether menu shortcuts should be displayed on panel menus when 1080 a keyboard is present. --> 1081 <bool name="config_showMenuShortcutsWhenKeyboardPresent">false</bool> 1082 1083 <!-- Do not translate. Defines the slots is Two Digit Number for dialing normally not USSD --> 1084 <string-array name="config_twoDigitNumberPattern" translatable="false"> 1085 </string-array> 1086 1087 <!-- The VoiceMail default value is displayed to my own number if it is true --> 1088 <bool name="config_telephony_use_own_number_for_voicemail">false</bool> 1089 1090 <!-- If this value is true, Sms encoded as octet is decoded by utf8 decoder. 1091 If false, decoded by Latin decoder. --> 1092 <bool name="config_sms_utf8_support">false</bool> 1093 1094 <!-- If this value is true, The mms content-disposition field is supported correctly. 1095 If false, Content-disposition fragments are ignored --> 1096 <bool name="config_mms_content_disposition_support">true</bool> 1097 1098 <!-- MMS user agent string --> 1099 <string name="config_mms_user_agent" translatable="false"></string> 1100 1101 <!-- MMS user agent prolfile url --> 1102 <string name="config_mms_user_agent_profile_url" translatable="false"></string> 1103 1104 <!-- National Language Identifier codes for the following two config items. 1105 (from 3GPP TS 23.038 V9.1.1 Table 6.2.1.2.4.1): 1106 0 - reserved 1107 1 - Turkish 1108 2 - Spanish (single shift table only) 1109 3 - Portuguese 1110 4 - Bengali 1111 5 - Gujarati 1112 6 - Hindi 1113 7 - Kannada 1114 8 - Malayalam 1115 9 - Oriya 1116 10 - Punjabi 1117 11 - Tamil 1118 12 - Telugu 1119 13 - Urdu 1120 14+ - reserved --> 1121 1122 <!-- National language single shift tables to enable for SMS encoding. 1123 Decoding is always enabled. 3GPP TS 23.038 states that this feature 1124 should not be enabled until a formal request is issued by the relevant 1125 national regulatory body. Array elements are codes from the table above. 1126 Example 1: devices sold in Turkey must include table 1 to conform with 1127 By-Law Number 27230. (http://www.btk.gov.tr/eng/pdf/2009/BY-LAW_SMS.pdf) 1128 Example 2: devices sold in India should include tables 4 through 13 1129 to enable use of the new Release 9 tables for Indic languages. --> 1130 <integer-array name="config_sms_enabled_single_shift_tables"></integer-array> 1131 1132 <!-- National language locking shift tables to enable for SMS encoding. 1133 Decoding is always enabled. 3GPP TS 23.038 states that this feature 1134 should not be enabled until a formal request is issued by the relevant 1135 national regulatory body. Array elements are codes from the table above. 1136 Example 1: devices sold in Turkey must include table 1 after the 1137 Turkish Telecommunication Authority requires locking shift encoding 1138 to be enabled (est. July 2012). (http://www.btk.gov.tr/eng/pdf/2009/BY-LAW_SMS.pdf) 1139 See also: http://www.mobitech.com.tr/tr/ersanozturkblog_en/index.php?entry=entry090223-160014 1140 Example 2: devices sold in India should include tables 4 through 13 1141 to enable use of the new Release 9 tables for Indic languages. --> 1142 <integer-array name="config_sms_enabled_locking_shift_tables"></integer-array> 1143 1144 <!-- Set to true if the RSSI should always display CDMA signal strength even on EVDO --> 1145 <bool name="config_alwaysUseCdmaRssi">false</bool> 1146 1147 1148 <!-- If this value is true, duplicate Source/Destination port fields 1149 in WDP header of some carriers OMADM wap push are supported. 1150 ex: MSGTYPE-TotalSegments-CurrentSegment 1151 -SourcePortDestPort-SourcePortDestPort-OMADM PDU 1152 If false, not supported. --> 1153 <bool name="config_duplicate_port_omadm_wappush">false</bool> 1154 1155 <!-- Maximum numerical value that will be shown in a status bar 1156 notification icon or in the notification itself. Will be replaced 1157 with @string/status_bar_notification_info_overflow when shown in the 1158 UI. --> 1159 <integer name="status_bar_notification_info_maxnum">999</integer> 1160 1161 <!-- Path to an ISO image to be shared with via USB mass storage. 1162 This is intended to allow packaging drivers or tools for installation on a PC. --> 1163 <string translatable="false" name="config_isoImagePath"></string> 1164 1165 <!-- Whether a software navigation bar should be shown. NOTE: in the future this may be 1166 autodetected from the Configuration. --> 1167 <bool name="config_showNavigationBar">false</bool> 1168 1169 <!-- Whether action menu items should be displayed in ALLCAPS or not. 1170 Defaults to true. If this is not appropriate for specific locales 1171 it should be disabled in that locale's resources. --> 1172 <bool name="config_actionMenuItemAllCaps">true</bool> 1173 1174 <!-- Whether action menu items should obey the "withText" showAsAction 1175 flag. This may be set to false for situations where space is 1176 extremely limited. --> 1177 <bool name="config_allowActionMenuItemTextWithIcon">false</bool> 1178 1179 <!-- Remote server that can provide NTP responses. --> 1180 <string translatable="false" name="config_ntpServer">2.android.pool.ntp.org</string> 1181 <!-- Normal polling frequency in milliseconds --> 1182 <integer name="config_ntpPollingInterval">864000000</integer> 1183 <!-- Try-again polling interval in milliseconds, in case the network request failed --> 1184 <integer name="config_ntpPollingIntervalShorter">60000</integer> 1185 <!-- Number of times to try again with the shorter interval, before backing 1186 off until the normal polling interval. A value < 0 indicates infinite. --> 1187 <integer name="config_ntpRetry">3</integer> 1188 <!-- If the time difference is greater than this threshold in milliseconds, 1189 then update the time. --> 1190 <integer name="config_ntpThreshold">5000</integer> 1191 <!-- Timeout to wait for NTP server response. --> 1192 <integer name="config_ntpTimeout">20000</integer> 1193 1194 <!-- Default network policy warning threshold, in megabytes. --> 1195 <integer name="config_networkPolicyDefaultWarning">2048</integer> 1196 1197 <!-- Set and Unsets WiMAX --> 1198 <bool name="config_wimaxEnabled">false</bool> 1199 <!-- Location of the wimax framwork jar location --> 1200 <string name="config_wimaxServiceJarLocation" translatable="false"></string> 1201 <!-- Location of the wimax native library locaiton --> 1202 <string name="config_wimaxNativeLibLocation" translatable="false"></string> 1203 <!-- Name of the wimax manager class --> 1204 <string name="config_wimaxManagerClassname" translatable="false"></string> 1205 <!-- Name of the wimax service class --> 1206 <string name="config_wimaxServiceClassname" translatable="false"></string> 1207 <!-- Name of the wimax state tracker clas --> 1208 <string name="config_wimaxStateTrackerClassname" translatable="false"></string> 1209 1210 <!-- Specifies whether the dreams feature should be supported. 1211 When true, the system will allow the user to configure dreams (screensavers) 1212 to launch when a user activity timeout occurs or the system is told to nap. 1213 When false, the dreams feature will be disabled (this does not affect dozing). 1214 1215 Consider setting this resource to false or disabling dreams by default when a 1216 doze component is specified below since dreaming will supercede dozing and 1217 will prevent the system from entering a low power state until the dream ends. --> 1218 <bool name="config_dreamsSupported">true</bool> 1219 1220 <!-- If supported, are dreams enabled? (by default) --> 1221 <bool name="config_dreamsEnabledByDefault">true</bool> 1222 <!-- If supported and enabled, are dreams activated when docked? (by default) --> 1223 <bool name="config_dreamsActivatedOnDockByDefault">true</bool> 1224 <!-- If supported and enabled, are dreams activated when asleep and charging? (by default) --> 1225 <bool name="config_dreamsActivatedOnSleepByDefault">false</bool> 1226 <!-- ComponentName of the default dream (Settings.Secure.DEFAULT_SCREENSAVER_COMPONENT) --> 1227 <string name="config_dreamsDefaultComponent">com.google.android.deskclock/com.android.deskclock.Screensaver</string> 1228 1229 <!-- Are we allowed to dream while not plugged in? --> 1230 <bool name="config_dreamsEnabledOnBattery">false</bool> 1231 <!-- Minimum battery level to allow dreaming when powered. 1232 Use -1 to disable this safety feature. --> 1233 <integer name="config_dreamsBatteryLevelMinimumWhenPowered">-1</integer> 1234 <!-- Minimum battery level to allow dreaming when not powered. 1235 Use -1 to disable this safety feature. --> 1236 <integer name="config_dreamsBatteryLevelMinimumWhenNotPowered">15</integer> 1237 <!-- If the battery level drops by this percentage and the user activity timeout 1238 has expired, then assume the device is receiving insufficient current to charge 1239 effectively and terminate the dream. Use -1 to disable this safety feature. --> 1240 <integer name="config_dreamsBatteryLevelDrainCutoff">5</integer> 1241 1242 <!-- ComponentName of a dream to show whenever the system would otherwise have 1243 gone to sleep. When the PowerManager is asked to go to sleep, it will instead 1244 try to start this dream if possible. The dream should typically call startDozing() 1245 to put the display into a low power state and allow the application processor 1246 to be suspended. When the dream ends, the system will go to sleep as usual. 1247 Specify the component name or an empty string if none. 1248 1249 Note that doze dreams are not subject to the same start conditions as ordinary dreams. 1250 Doze dreams will run whenever the power manager is in a dozing state. --> 1251 <string name="config_dozeComponent"></string> 1252 1253 <!-- Power Management: Specifies whether to decouple the auto-suspend state of the 1254 device from the display on/off state. 1255 1256 When false, autosuspend_disable() will be called before the display is turned on 1257 and autosuspend_enable() will be called after the display is turned off. 1258 This mode provides best compatibility for devices using legacy power management 1259 features such as early suspend / late resume. 1260 1261 When true, autosuspend_display() and autosuspend_enable() will be called 1262 independently of whether the display is being turned on or off. This mode 1263 enables the power manager to suspend the application processor while the 1264 display is on. 1265 1266 This resource should be set to "true" when a doze component has been specified 1267 to maximize power savings but not all devices support it. 1268 1269 Refer to autosuspend.h for details. 1270 --> 1271 <bool name="config_powerDecoupleAutoSuspendModeFromDisplay">false</bool> 1272 1273 <!-- Power Management: Specifies whether to decouple the interactive state of the 1274 device from the display on/off state. 1275 1276 When false, setInteractive(..., true) will be called before the display is turned on 1277 and setInteractive(..., false) will be called after the display is turned off. 1278 This mode provides best compatibility for devices that expect the interactive 1279 state to be tied to the display state. 1280 1281 When true, setInteractive(...) will be called independently of whether the display 1282 is being turned on or off. This mode enables the power manager to reduce 1283 clocks and disable the touch controller while the display is on. 1284 1285 This resource should be set to "true" when a doze component has been specified 1286 to maximize power savings but not all devices support it. 1287 1288 Refer to power.h for details. 1289 --> 1290 <bool name="config_powerDecoupleInteractiveModeFromDisplay">false</bool> 1291 1292 <!-- User activity timeout: Minimum screen off timeout in milliseconds. 1293 1294 Sets a lower bound for the {@link Settings.System#SCREEN_OFF_TIMEOUT} setting 1295 which determines how soon the device will go to sleep when there is no 1296 user activity. 1297 1298 This value must be greater than zero, otherwise the device will immediately 1299 fall asleep again as soon as it is awoken. 1300 --> 1301 <integer name="config_minimumScreenOffTimeout">10000</integer> 1302 1303 <!-- User activity timeout: Maximum screen dim duration in milliseconds. 1304 1305 Sets an upper bound for how long the screen will dim before the device goes 1306 to sleep when there is no user activity. The dim duration is subtracted from 1307 the overall screen off timeout to determine the screen dim timeout. 1308 When the screen dim timeout expires, the screen will dim, shortly thereafter 1309 the device will go to sleep. 1310 1311 If the screen off timeout is very short, the dim duration may be reduced 1312 proportionally. See config_maximumScreenDimRatio. 1313 1314 This value may be zero in which case the screen will not dim before the 1315 device goes to sleep. 1316 --> 1317 <integer name="config_maximumScreenDimDuration">7000</integer> 1318 1319 <!-- User activity timeout: Maximum screen dim duration as a percentage of screen off timeout. 1320 1321 This resource is similar to config_maximumScreenDimDuration but the maximum 1322 screen dim duration is defined as a ratio of the overall screen off timeout 1323 instead of as an absolute value in milliseconds. This is useful for reducing 1324 the dim duration when the screen off timeout is very short. 1325 1326 When computing the screen dim duration, the power manager uses the lesser 1327 of the effective durations expressed by config_maximumScreenDimDuration and 1328 config_maximumScreenDimRatio. 1329 1330 This value must be between 0% and 100%. If the value is zero, the screen will not 1331 dim before the device goes to sleep. 1332 --> 1333 <fraction name="config_maximumScreenDimRatio">20%</fraction> 1334 1335 <!-- Base "touch slop" value used by ViewConfiguration as a 1336 movement threshold where scrolling should begin. --> 1337 <dimen name="config_viewConfigurationTouchSlop">8dp</dimen> 1338 1339 <!-- Minimum velocity to initiate a fling, as measured in dips per second. --> 1340 <dimen name="config_viewMinFlingVelocity">50dp</dimen> 1341 1342 <!-- Maximum velocity to initiate a fling, as measured in dips per second. --> 1343 <dimen name="config_viewMaxFlingVelocity">8000dp</dimen> 1344 1345 <!-- Amount of time in ms the user needs to press the relevant key to bring up the global actions dialog --> 1346 <integer name="config_globalActionsKeyTimeout">500</integer> 1347 1348 <!-- Maximum number of grid columns permitted in the ResolverActivity 1349 used for picking activities to handle an intent. --> 1350 <integer name="config_maxResolverActivityColumns">3</integer> 1351 1352 <!-- Array of OEM specific USB mode override config. 1353 OEM can override a certain USB mode depending on ro.bootmode. 1354 Specify an array of below items to set override rule. 1355 [bootmode]:[original USB mode]:[USB mode used]--> 1356 <integer-array translatable="false" name="config_oemUsbModeOverride"> 1357 </integer-array> 1358 1359 <!-- Set to true to add links to Cell Broadcast app from Settings and MMS app. --> 1360 <bool name="config_cellBroadcastAppLinks">false</bool> 1361 1362 <!-- The default value if the SyncStorageEngine should sync automatically or not --> 1363 <bool name="config_syncstorageengine_masterSyncAutomatically">true</bool> 1364 1365 <!-- Maximum number of supported users --> 1366 <integer name="config_multiuserMaximumUsers">1</integer> 1367 <!-- Whether UI for multi user should be shown --> 1368 <bool name="config_enableMultiUserUI">false</bool> 1369 1370 <!-- If true, then we do not ask user for permission for apps to connect to USB devices. 1371 Do not set this to true for production devices. Doing so will cause you to fail CTS. --> 1372 <bool name="config_disableUsbPermissionDialogs">false</bool> 1373 1374 <!-- Minimum span needed to begin a touch scaling gesture. 1375 If the span is equal to or greater than this size, a scaling gesture 1376 will begin, where supported. (See android.view.ScaleGestureDetector) 1377 1378 This also takes into account the size of any active touch points. 1379 Devices with screens that deviate too far from their assigned density 1380 bucket should consider tuning this value in a device-specific overlay. 1381 For best results, care should be taken such that this value remains 1382 larger than the minimum reported touchMajor/touchMinor values 1383 reported by the hardware. --> 1384 <dimen name="config_minScalingSpan">27mm</dimen> 1385 1386 <!-- Minimum accepted value for touchMajor while scaling. This may be tuned 1387 per-device in overlays. --> 1388 <dimen name="config_minScalingTouchMajor">48dp</dimen> 1389 1390 <!-- Safe headphone volume index. When music stream volume is below this index 1391 the SPL on headphone output is compliant to EN 60950 requirements for portable music 1392 players. --> 1393 <integer name="config_safe_media_volume_index">10</integer> 1394 1395 <!-- Configure mobile network MTU. The standard default is set here but each carrier 1396 may have a specific value set in an overlay config.xml file. --> 1397 <integer name="config_mobile_mtu">1500</integer> 1398 1399 <!-- Configure mobile tcp buffer sizes in the form: 1400 rat-name:rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max 1401 If no value is found for the rat-name in use, the system default will be applied. 1402 --> 1403 <string-array name="config_mobile_tcp_buffers"> 1404 </string-array> 1405 1406 <!-- Configure ethernet tcp buffersizes in the form: 1407 rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max --> 1408 <string name="config_ethernet_tcp_buffers" translatable="false">524288,1048576,3145728,524288,1048576,2097152</string> 1409 1410 <!-- Configure wifi tcp buffersizes in the form: 1411 rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max --> 1412 <string name="config_wifi_tcp_buffers" translatable="false">524288,1048576,2097152,262144,524288,1048576</string> 1413 1414 <!-- Whether WiFi display is supported by this device. 1415 There are many prerequisites for this feature to work correctly. 1416 Here are a few of them: 1417 * The WiFi radio must support WiFi P2P. 1418 * The WiFi radio must support concurrent connections to the WiFi display and 1419 to an access point. 1420 * The Audio Flinger audio_policy.conf file must specify a rule for the "r_submix" 1421 remote submix module. This module is used to record and stream system 1422 audio output to the WiFi display encoder in the media server. 1423 * The remote submix module "audio.r_submix.default" must be installed on the device. 1424 * The device must be provisioned with HDCP keys (for protected content). 1425 --> 1426 <bool name="config_enableWifiDisplay">false</bool> 1427 1428 <!-- When true use the linux /dev/input/event subsystem to detect the switch changes 1429 on the headphone/microphone jack. When false use the older uevent framework. --> 1430 <bool name="config_useDevInputEventForAudioJack">false</bool> 1431 1432 <!-- Whether safe headphone volume is enabled or not (country specific). --> 1433 <bool name="config_safe_media_volume_enabled">true</bool> 1434 1435 <!-- Set to true if the wifi display supports compositing content stored 1436 in gralloc protected buffers. For this to be true, there must exist 1437 a protected hardware path for surface flinger to composite and send 1438 protected buffers to the wifi display video encoder. 1439 1440 If this flag is false, we advise applications not to use protected 1441 buffers (if possible) when presenting content to a wifi display because 1442 the content may be blanked. 1443 1444 This flag controls whether the {@link Display#FLAG_SUPPORTS_PROTECTED_BUFFERS} 1445 flag is set for wifi displays. 1446 --> 1447 <bool name="config_wifiDisplaySupportsProtectedBuffers">false</bool> 1448 1449 <!-- Whether camera shutter sound is forced or not (country specific). --> 1450 <bool name="config_camera_sound_forced">false</bool> 1451 1452 <!-- Set to true if we need to not prefer an APN. 1453 This is being added to enable a simple scenario of pre-paid 1454 provisioning on some carriers, working around a bug (7305641) 1455 where if the preferred is used we don't try the others. --> 1456 <bool name="config_dontPreferApn">false</bool> 1457 1458 <!-- The list of ril radio technologies (see ServiceState.java) which only support 1459 a single data connection at one time. This may change by carrier via 1460 overlays (some don't support multiple pdp on UMTS). All unlisted radio 1461 tech types support unlimited types (practically only 2-4 used). --> 1462 <integer-array name="config_onlySingleDcAllowed"> 1463 <item>4</item> <!-- IS95A --> 1464 <item>5</item> <!-- IS95B --> 1465 <item>6</item> <!-- 1xRTT --> 1466 <item>7</item> <!-- EVDO_0 --> 1467 <item>8</item> <!-- EVDO_A --> 1468 <item>12</item> <!-- EVDO_B --> 1469 </integer-array> 1470 1471 <!-- Set to true if after a provisioning apn the radio should be restarted --> 1472 <bool name="config_restartRadioAfterProvisioning">false</bool> 1473 1474 <!-- Boolean indicating if RADIO POWER OFF is required on receiving SIM REFRESH with RESET. 1475 This will be handled by modem if it is false. --> 1476 <bool name="config_requireRadioPowerOffOnSimRefreshReset">false</bool> 1477 1478 <!-- Vibrator pattern to be used as the default for notifications 1479 that specify DEFAULT_VIBRATE. 1480 --> 1481 <integer-array name="config_defaultNotificationVibePattern"> 1482 <item>0</item> 1483 <item>350</item> 1484 <item>250</item> 1485 <item>350</item> 1486 </integer-array> 1487 1488 <!-- Vibrator pattern to be used as the default for notifications 1489 that do not specify vibration but vibrate anyway because the device 1490 is in vibrate mode. 1491 --> 1492 <integer-array name="config_notificationFallbackVibePattern"> 1493 <item>0</item> 1494 <item>100</item> 1495 <item>150</item> 1496 <item>100</item> 1497 </integer-array> 1498 1499 <!-- Flag indicating if the speed up audio on mt call code should be executed --> 1500 <bool name="config_speed_up_audio_on_mt_calls">false</bool> 1501 1502 <!-- Class name of the framework account picker activity. 1503 Can be customized for other product types --> 1504 <string name="config_chooseAccountActivity" 1505 >android/android.accounts.ChooseAccountActivity</string> 1506 <!-- Class name of the account type and account picker activity. 1507 Can be customized for other product types --> 1508 <string name="config_chooseTypeAndAccountActivity" 1509 >android/android.accounts.ChooseTypeAndAccountActivity</string> 1510 1511 <!-- Component name of a custom ResolverActivity (Intent resolver) to be used instead of 1512 the default framework version. If left empty, then the framework version will be used. 1513 Example: com.google.android.myapp/.resolver.MyResolverActivity --> 1514 <string name="config_customResolverActivity"></string> 1515 1516 <!-- Name of the activity or service that prompts the user to reject, accept, or whitelist 1517 an adb host's public key, when an unwhitelisted host connects to the local adbd. 1518 Can be customized for other product types --> 1519 <string name="config_customAdbPublicKeyConfirmationComponent" 1520 >com.android.systemui/com.android.systemui.usb.UsbDebuggingActivity</string> 1521 1522 <!-- Name of the CustomDialog that is used for VPN --> 1523 <string name="config_customVpnConfirmDialogComponent" 1524 >com.android.vpndialogs/com.android.vpndialogs.ConfirmDialog</string> 1525 1526 <!-- Apps that are authorized to access shared accounts, overridden by product overlays --> 1527 <string name="config_appsAuthorizedForSharedAccounts">;com.android.settings;</string> 1528 1529 <!-- Flag indicating that the media framework should not allow changes or mute on any 1530 stream or master volumes. --> 1531 <bool name="config_useFixedVolume">false</bool> 1532 1533 <!-- The list of IMEs which should be disabled until used. 1534 This function suppresses update notifications for these pre-installed apps. 1535 We need to set this configuration carefully that they should not have functionarities 1536 other than "IME" or "Spell Checker". In InputMethodManagerService, 1537 the listed IMEs are disabled until used when all of the following conditions are met. 1538 1. Not selected as an enabled IME in the Settings 1539 2. Not selected as a spell checker in the Settings 1540 3. Installed 1541 4. A pre-installed IME 1542 5. Not enabled 1543 And the disabled_until_used state for an IME is released by InputMethodManagerService 1544 when the IME is selected as an enabled IME. --> 1545 <string-array name="config_disabledUntilUsedPreinstalledImes" translatable="false"> 1546 <item>com.android.inputmethod.latin</item> 1547 </string-array> 1548 1549 <!-- The list of classes that should be added to the notification ranking pipline. 1550 See {@link com.android.server.notification.NotificationSignalExtractor} --> 1551 <string-array name="config_notificationSignalExtractors"> 1552 <item>com.android.server.notification.ValidateNotificationPeople</item> 1553 <item>com.android.server.notification.PackagePriorityExtractor</item> 1554 <item>com.android.server.notification.NotificationIntrusivenessExtractor</item> 1555 <item>com.android.server.notification.PackageVisibilityExtractor</item> 1556 </string-array> 1557 1558 <!-- Flag indicating that this device does not rotate and will always remain in its default 1559 orientation. Activities that desire to run in a non-compatible orientation will be run 1560 from an emulated display within the physical display. --> 1561 <bool name="config_forceDefaultOrientation">false</bool> 1562 1563 <!-- Default Gravity setting for the system Toast view. Equivalent to: Gravity.CENTER_HORIZONTAL | Gravity.BOTTOM --> 1564 <integer name="config_toastDefaultGravity">0x00000051</integer> 1565 1566 <!-- set to false if we need to show user confirmation 1567 when alpha identifier is not provided by the UICC --> 1568 <bool name="config_stkNoAlphaUsrCnf">true</bool> 1569 1570 <!-- Don't use roaming icon for considered operators. 1571 Can use mcc or mcc+mnc as item. For example, 302 or 21407. 1572 If operators, 21404 and 21407, make roaming agreements, user of 21404 should not see 1573 the roaming icon as using 21407 network. 1574 To do this, add 21407 item to values-mcc214-mnc04/config.xml --> 1575 <string-array translatable="false" name="config_operatorConsideredNonRoaming"> 1576 </string-array> 1577 1578 <!-- Threshold (in ms) under which a screen off / screen on will be considered a reset of the 1579 immersive mode confirmation prompt.--> 1580 <integer name="config_immersive_mode_confirmation_panic">5000</integer> 1581 1582 <!-- For some operators, PDU has garbages. To fix it, need to use valid index --> 1583 <integer name="config_valid_wappush_index">-1</integer> 1584 1585 <!-- Show roaming icon though same named operators. 1586 Uses "startsWith" so you can use a leading substring like the mcc or 1587 use the complete mcc+mnc string. 1588 Though same mcc and same operator name, some operator want to roam. 1589 user of 40485 should see the roaming icon as using 40483 network 1590 though same Reliance network. 1591 To do this, add 40483 item to values-mcc404-mnc85/config.xml --> 1592 <string-array translatable="false" name="config_sameNamedOperatorConsideredRoaming"> 1593 </string-array> 1594 <!-- call barring MMI code from TS 22.030 Annex B --> 1595 <string-array translatable="false" name="config_callBarringMMI"> 1596 <item>33</item> 1597 <item>331</item> 1598 <item>332</item> 1599 <item>35</item> 1600 <item>351</item> 1601 <item>330</item> 1602 <item>333</item> 1603 <item>353</item> 1604 </string-array> 1605 1606 <!-- Override the default detection behavior for the framework method 1607 android.view.ViewConfiguration#hasPermanentMenuKey(). 1608 Valid settings are: 1609 0 - No change. Use the default autodetection behavior. 1610 1 - The device DOES have a permanent menu key; ignore autodetection. 1611 2 - The device DOES NOT have a permanent menu key; ignore autodetection. --> 1612 <integer name="config_overrideHasPermanentMenuKey">0</integer> 1613 1614 <!-- default window inset isRound property --> 1615 <bool name="config_windowIsRound">false</bool> 1616 1617 <!-- Package name for default network scorer app; overridden by product overlays. --> 1618 <string name="config_defaultNetworkScorerPackageName"></string> 1619 1620 <!-- default device has recents property --> 1621 <bool name="config_hasRecents">true</bool> 1622 1623 <!-- default window ShowCircularMask property --> 1624 <bool name="config_windowShowCircularMask">false</bool> 1625 1626 <!-- default value for whether circular emulators (ro.emulator.circular) 1627 should show a display overlay on the screen --> 1628 <bool name="config_windowEnableCircularEmulatorDisplayOverlay">false</bool> 1629 1630 <!-- Defines the default set of global actions. Actions may still be disabled or hidden based 1631 on the current state of the device. 1632 Each item must be one of the following strings: 1633 "power" = Power off 1634 "settings" = An action to launch settings 1635 "airplane" = Airplane mode toggle 1636 "bugreport" = Take bug report, if available 1637 "silent" = silent mode 1638 "users" = list of users 1639 --> 1640 <string-array translatable="false" name="config_globalActionsList"> 1641 <item>power</item> 1642 <item>bugreport</item> 1643 <item>users</item> 1644 </string-array> 1645 1646 <!-- default telephony hardware configuration for this platform. 1647 --> 1648 <!-- this string array should be overridden by the device to present a list 1649 telephony hardware resource. this is used by the telephony device controller 1650 (TDC) to offer the basic capabilities of the hardware to the telephony 1651 framework 1652 --> 1653 <!-- an array of "[hardware type],[hardware-uuid],[state],[[hardware-type specific]]" 1654 with, [[hardware-type specific]] in: 1655 - "[[ril-model],[rat],[max-active-voice],[max-active-data],[max-active-standby]]" 1656 for 'modem' hardware 1657 - "[[associated-modem-uuid]]" 1658 for 'sim' hardware. 1659 refer to HardwareConfig in com.android.internal.telephony for specific details/values 1660 those elements can carry. 1661 --> 1662 <string-array translatable="false" name="config_telephonyHardware"> 1663 <!-- modem --> 1664 <item>"0,modem,0,0,0,1,1,1"</item> 1665 <!-- sim --> 1666 <item>"1,sim,0,modem"</item> 1667 </string-array> 1668 1669 <!-- This string array can be overriden to add an additional DRM support for WebView EME. --> 1670 <!-- Array of "[keySystemName],[UuidOfMediaDrm]" @hide @SystemApi --> 1671 <string-array name="config_keySystemUuidMapping" translatable="false"> 1672 <!-- Example: 1673 <item>"x-com.microsoft.playready,9A04F079-9840-4286-AB92-E65BE0885F95"</item> 1674 --> 1675 </string-array> 1676 1677 <!-- Flag indicating which package name can access the persistent data partition --> 1678 <string name="config_persistentDataPackageName" translatable="false"></string> 1679 1680 <!-- Flag indicating apps will skip sending hold request before merge. In this case 1681 IMS service implementation will do both.i.e.hold followed by merge. --> 1682 <bool name="skipHoldBeforeMerge">true</bool> 1683 1684 <!-- Flag indicating emergency calls will always use IMS irrespective of the state of 1685 the IMS connection --> 1686 <bool name="useImsAlwaysForEmergencyCall">true</bool> 1687 1688 <!-- Flag indicating whether the IMS service can be turned off. If false then 1689 the service will not be turned-off completely (the ImsManager.turnOffIms() will 1690 be disabled) but individual Features can be disabled using ImsConfig.setFeatureValue() --> 1691 <bool name="imsServiceAllowTurnOff">true</bool> 1692 1693 <!-- Flag specifying whether VoLTE & VT is availasble on device --> 1694 <bool name="config_device_volte_vt_available">false</bool> 1695 1696 <!-- Flag specifying whether VoLTE & VT should be available for carrier: independent of 1697 carrier provisioning. If false: hard disabled. If true: then depends on carrier 1698 provisioning, availability etc --> 1699 <bool name="config_carrier_volte_vt_available">false</bool> 1700 1701 <bool name="config_networkSamplingWakesDevice">true</bool> 1702 1703 <string-array translatable="false" name="config_cdma_home_system" /> 1704 1705 <!-- Default text encoding for WebSettings. @hide @SystemApi --> 1706 <string name="config_webSettingsDefaultTextEncoding">UTF-8</string> 1707 1708 <!--From SmsMessage--> 1709 <!--Support decoding the user data payload as pack GSM 8-bit (a GSM alphabet 1710 string that's stored in 8-bit unpacked format) characters.--> 1711 <bool translatable="false" name="config_sms_decode_gsm_8bit_data">false</bool> 1712 1713 <!-- Package name providing WebView implementation. --> 1714 <string name="config_webViewPackageName" translatable="false">com.android.webview</string> 1715 1716 <!-- If EMS is not supported, framework breaks down EMS into single segment SMS 1717 and adds page info " x/y". This config is used to set which carrier doesn't 1718 support EMS and whether page info should be added at the beginning or the end. 1719 We use tag 'prefix' for position beginning and 'suffix' for position end. 1720 And use gid to distinguish different carriers which using same mcc and mnc. 1721 Examples: <item>simOperatorNumber;position;gid(optional)</item>> 1722 --> 1723 <string-array translatable="false" name="no_ems_support_sim_operators"> 1724 <!-- VZW --> 1725 <item>20404;suffix;BAE0000000000000</item> 1726 </string-array> 1727 1728 <bool name="config_auto_attach_data_on_creation">true</bool> 1729 1730 <!-- Values for GPS configuration --> 1731 <string-array translatable="false" name="config_gpsParameters"> 1732 <item>SUPL_HOST=supl.google.com</item> 1733 <item>SUPL_PORT=7275</item> 1734 <item>NTP_SERVER=north-america.pool.ntp.org</item> 1735 <item>SUPL_VER=0x20000</item> 1736 </string-array> 1737 1738 <!-- If there is no preload VM number in the sim card, carriers such as 1739 Verizon require to load a default vm number from the configurantion. 1740 Define config_default_vm_number for this purpose. And there are two 1741 optional formats for this configuration as below: 1742 (1)<item>voicemail number</item> 1743 (2)<item>voicemail number;gid</item> 1744 The logic to pick up the correct voicemail number: 1745 (1) If the config_default_vm_number array has no gid special item, the last one will be 1746 picked 1747 (2) If the config_default_vm_number array has gid special item and it matches the current 1748 sim's gid, it will be picked. 1749 (3) If the config_default_vm_number array has gid special item but it doesn't match the 1750 current sim's gid, the last one without gid will be picked --> 1751 <string-array translatable="false" name="config_default_vm_number" /> 1752</resources> 1753