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