OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
defs:SpecialCharSequenceMgr
(Results
1 - 3
of
3
) sorted by null
/packages/services/Telephony/src/com/android/phone/
SpecialCharSequenceMgr.java
47
* *This* version of
SpecialCharSequenceMgr
is used for only a few
57
public class
SpecialCharSequenceMgr
{
65
private
SpecialCharSequenceMgr
() {
259
Log.d(TAG, "[
SpecialCharSequenceMgr
] " + msg);
/packages/apps/Dialer/java/com/android/dialer/dialpadview/
SpecialCharSequenceMgr.java
85
public class
SpecialCharSequenceMgr
{
117
* complication is that we have
SpecialCharSequenceMgr
in Phone package too, which has *slightly*
125
private
SpecialCharSequenceMgr
() {}
272
LogUtil.w("
SpecialCharSequenceMgr
.handleAdnQuery", "queryAdn parameters incorrect");
433
LogUtil.e("
SpecialCharSequenceMgr
.getDecimalFromHex", "unable to parse hex", e);
443
LogUtil.e("
SpecialCharSequenceMgr
.getDecimalFromHex", "unable to parse hex", e);
482
LogUtil.e("
SpecialCharSequenceMgr
.generateBarcode", "error generating barcode", e);
490
"
SpecialCharSequenceMgr
.handleRegulatoryInfoDisplay", "sending intent to settings app");
496
"
SpecialCharSequenceMgr
.handleRegulatoryInfoDisplay", "startActivity() failed: ", e);
DialpadFragment.java
178
*
SpecialCharSequenceMgr
actions can be triggered by user input but *not* by a tel: URI passed by
315
// When DTMF dialpad buttons are being pressed, we delay
SpecialCharSequenceMgr
sequence,
316
// since some of
SpecialCharSequenceMgr
's behavior is too abrupt for the "touch-down"
319
&&
SpecialCharSequenceMgr
.handleChars(getActivity(), input.toString(), digits)) {
756
SpecialCharSequenceMgr
.cleanup();
[
all
...]
Completed in 4747 milliseconds