PageRenderTime 25ms CodeModel.GetById 17ms app.highlight 3ms RepoModel.GetById 1ms app.codeStats 1ms

XML | 122 lines | 22 code | 18 blank | 82 comment | 0 complexity | 5a71d27f32d226538b6d388d201e5b68 MD5 | raw file
  1<?xml version="1.0" encoding="utf-8"?>
  2<!-- Copyright (C) 2009 The Android Open Source Project
  4     Licensed under the Apache License, Version 2.0 (the "License");
  5     you may not use this file except in compliance with the License.
  6     You may obtain a copy of the License at
 10     Unless required by applicable law or agreed to in writing, software
 11     distributed under the License is distributed on an "AS IS" BASIS,
 12     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 13     See the License for the specific language governing permissions and
 14     limitations under the License.
 17<!-- Phone app resources that may need to be customized
 18     for different hardware or product builds. -->
 20    <!-- Flag indicating whether the Phone app should ignore
 21         EVENT_SIM_NETWORK_LOCKED events from the Sim.  If true, this will
 22         prevent the IccNetworkDepersonalizationPanel from being shown,
 23         and effectively disable the "Sim network lock" feature. -->
 24    <bool name="ignore_sim_network_locked_events">true</bool>
 26    <!-- Flag indicating whether the Phone app should provide
 27         a "Dismiss" button on the SIM network unlock screen.
 28         The default value is true.
 29         If set to false, there will be *no way* to dismiss the SIM
 30         network unlock screen if you don't enter the correct unlock code.
 31         (One important consequence: there will be no way to make an
 32         Emergency Call if your SIM is network-locked and you don't know
 33         the PIN.) -->
 34    <bool name="sim_network_unlock_allow_dismiss">true</bool>
 36    <!-- If true, enable the onscreen touch UI for incoming calls.
 37         This feature is necessary for devices with no hard SEND/END keys,
 38         and optional on all other devices. -->
 39    <bool name="allow_incoming_call_touch_ui">true</bool>
 41    <!-- If true, enable the onscreen touch UI for regular "ongoing call"
 42         states of the in-call UI.
 43         In general, the touch UI is used for regular calls only on
 44         devices with a proximity sensor.  (On other devices, we can't
 45         have touchable UI onscreen during a call because of the risk of
 46         false cheek touches.)
 47         TODO: maybe this can be determined algorithmically based on
 48         specific properties of the device, perhaps by detecting the
 49         presence of a proximity sensor and/or hard SEND/END keys.  (If
 50         so, we wouldn't need this flag at all.) -->
 51    <bool name="allow_in_call_touch_ui">true</bool>
 53    <!-- OTA configuration values, used when provisioning CDMA devices.
 54         Following defaults values of zero means OTA UI is completely disabled.
 55         These OTA UI can be enabled by setting config value to one in the product
 56         specific overlay file -->
 58    <!-- Determine whether we want to display the OTA activation screen, which
 59         gives the user option to activate or cancel -->
 60    <integer name="OtaShowActivationScreen">1</integer>
 61    <!-- Determine whether we should show the "listen for instructions" screen after
 62         successfully placing the OTA call -->
 63    <integer name="OtaShowListeningScreen">0</integer>
 64    <!-- The number of times we should show the activation screen/allow the provisioning
 65         to fail before just showing an unsuccessful dialog -->
 66    <integer name="OtaShowActivateFailTimes">0</integer>
 67    <!-- Determine whether or not we should play the success/failure tone -->
 68    <integer name="OtaPlaySuccessFailureTone">0</integer>
 70    <!-- Flag indicating if the phone is a world phone -->
 71    <bool name="world_phone">false</bool>
 73    <!-- If true, enable vibration (haptic feedback) for key presses
 74         in the EmergencyDialer activity. The pattern is set on a
 75         per-platform basis using config_virtualKeyVibePattern.  To be
 76         consistent with the regular Dialer, this value should agree
 77         with the corresponding values from config.xml under
 78         apps/Contacts. -->
 79    <bool name="config_enable_dialer_key_vibration">true</bool>
 81    <!-- Flag indicating if the tty is enabled -->
 82    <bool name="tty_enabled">false</bool>
 84    <!-- Flag indicating if hac is enabled -->
 85    <bool name="hac_enabled">false</bool>
 87    <!-- Flag indicating if dtmf tone type is enabled -->
 88    <bool name="dtmf_type_enabled">false</bool>
 90    <!-- Flag indicating if auto retry is enabled -->
 91    <bool name="auto_retry_enabled">false</bool>
 93    <!-- Determine whether we want to play local DTMF tones in a call, or
 94         just let the radio/BP handle playing of the tones. -->
 95    <bool name="allow_local_dtmf_tones">true</bool>
 97    <!-- While an incoming call is ringing, this flag specifies whether
 98         the BACK key should reject the current call (just like the
 99         ENDCALL button does.)
100         This was originally the default behavior for all platforms, but
101         it's a bad idea on devices where the BACK key is a capacitive
102         button (since it's too easy to press the key accidentally as you
103         pull the phone out of your pocket.)  So devices that *don't* want
104         this behavior should set this flag to false via the resource
105         overlay.  -->
106    <bool name="allow_back_key_to_reject_incoming_call">true</bool>
108    <!-- If true, show an onscreen "Dial" button in the dialer.
109         In practice this is used on all platforms even the ones with hard SEND/END
110         keys, but for maximum flexibility it's controlled by a flag here
111         (which can be overridden on a per-product basis.) -->
112    <bool name="config_show_onscreen_dial_button">true</bool>
114    <!-- Determine whether calls to mute the microphone in PhoneUtils
115         are routed through the class (true) or through
116         the interface (false). -->
117    <bool name="send_mic_mute_to_AudioManager">true</bool>
119    <!-- Determines if device implements a noise suppression device for in call audio-->
120    <bool name="has_in_call_noise_suppression">false</bool>