电话接通与未接通，下层上报的状态

在

反复拨打电话，电话测试小程序，紧急电话与普通电话分枝判断

中遇到这样一个问题，在压力测试电话拨打时，如果没有接通，该如何判断此状态呢，该如何统计拨打成功多少次？

从log日志中发现有：

01-01 08:26:43.507: DEBUG/InCallScreen(1409): - mLastDisconnectCause = NORMAL
01-01 08:27:01.515: DEBUG/InCallScreen(1409): - mLastDisconnectCause = LOCAL

01-02 17:21:36.304: DEBUG/InCallScreen(1383): - mLastDisconnectCause = ERROR_UNSPECIFIED

其中： // DisconnectCause values in the most common scenarios:
                // - INCOMING_MISSED: incoming ringing call times out, or the other end hangs up while still ringing
                // - INCOMING_REJECTED: user rejects the call while ringing
                // - LOCAL: user hung up while a call was active (after answering an incoming call, or after making an outgoing call)
                // - NORMAL: the other end hung up (after answering an incoming   call, or after making an outgoing call)

如果：mLastDisconnectCause = ERROR_UNSPECIFIED 表示连接不成功--失败。

在代码：InCallScreen.java里得到体现，见如下代码：

    private void delayedCleanupAfterDisconnect() {
if (VDBG) log("delayedCleanupAfterDisconnect()...  Phone state = " + mCM.getState());
// Clean up any connections in the DISCONNECTED state.
//
// [Background: Even after a connection gets disconnected, its
// Connection object still stays around, in the special
// DISCONNECTED state.  This is necessary because we we need the
// caller-id information from that Connection to properly draw the
// "Call ended" state of the CallCard.
//   But at this point we truly don't need that connection any
// more, so tell the Phone that it's now OK to to clean up any
// connections still in that state.]
mCM.clearDisconnected();
if (!phoneIsInUse()) {
// Phone is idle!  We should exit this screen now.
if (DBG) log("- delayedCleanupAfterDisconnect: phone is idle...");
// And (finally!) exit from the in-call screen
// (but not if we're already in the process of pausing...)
if (mIsForegroundActivity) {
if (DBG) log("- delayedCleanupAfterDisconnect: finishing InCallScreen...");
// In some cases we finish the call by taking the user to the
// Call Log.  Otherwise, we simply call endInCallScreenSession,
// which will take us back to wherever we came from.
//
// UI note: In eclair and earlier, we went to the Call Log
// after outgoing calls initiated on the device, but never for
// incoming calls.  Now we do it for incoming calls too, as
// long as the call was answered by the user.  (We always go
// back where you came from after a rejected or missed incoming
// call.)
//
// And in any case, *never* go to the call log if we're in
// emergency mode (i.e. if the screen is locked and a lock
// pattern or PIN/password is set.)
if (VDBG) log("- Post-call behavior:");
if (VDBG) log("  - mLastDisconnectCause = " + mLastDisconnectCause);
if (VDBG) log("  - isPhoneStateRestricted() = " + isPhoneStateRestricted());
mNumberAll ++;
Log.e("mNumber", "mNumberAll==="+mNumberAll);
if(mLastDisconnectCause.toString().equals("ERROR_UNSPECIFIED")){
mNumberFail ++;
Log.e("mNumber", "Failure number==="+mNumberFail);
}
Log.e("mNumber", "mNumberFail/mNumberAll==="+mNumberAll +"/"+ mNumberAll);
// DisconnectCause values in the most common scenarios:
// - INCOMING_MISSED: incoming ringing call times out, or the
//                    other end hangs up while still ringing
// - INCOMING_REJECTED: user rejects the call while ringing
// - LOCAL: user hung up while a call was active (after
//          answering an incoming call, or after making an
//          outgoing call)
// - NORMAL: the other end hung up (after answering an incoming
//           call, or after making an outgoing call)
//Mod by kylin 2011.10.21 begin     //Open by kylin 2012.03.22
if ((mLastDisconnectCause != Connection.DisconnectCause.INCOMING_MISSED)
&& (mLastDisconnectCause != Connection.DisconnectCause.INCOMING_REJECTED)
&& !isPhoneStateRestricted()) {
if (VDBG) log("- Show Call Log after disconnect...");
final Intent intent = PhoneApp.createCallLogIntent();
intent.addFlags(Intent.FLAG_ACTIVITY_NO_ANIMATION);
startActivity(intent);
// Even in this case we still call endInCallScreenSession (below),
// to make sure we don't stay in the activity history.
}
endInCallScreenSession();
finish();
//Mod by kylin 2011.10.21 begin
}
} else {
// The phone is still in use.  Stay here in this activity, but
// we don't need to keep the screen on.
if (DBG) log("- delayedCleanupAfterDisconnect: staying on the InCallScreen...");
if (DBG) PhoneUtils.dumpCallState();
}
}

电话接通与未接通，下层上报的状态相关推荐

通话未接通显示无法连接服务器,未接通分析报告-20210719181140.docx-原创力文档
精品资料精品资料可编辑修改可编辑修改 3.4月份未接通分析报告一.概述: 从3月份以来,TEMS测试的十轮测试结果来看,未接通事件共发生了 86次,有些事件是连续发生两次未接通,指标也不理想 ...
QCI1建立不及时导致未接通
1.专用业务承载的建立在VoLTE呼叫的过程中需要建立QCI=1的语音专用承载.如果在发起呼叫的过程中,QCI=1的语音专用承载建立不及时就很容易导致呼叫失败,造成通话未接通. 1.1专用业务承载建 ...
windows 7 系统显示电池电量95% 可用（电源已接通，未充电）解决办法
网友解释: 这就是最好的充电保护功能,居然被忽视了,电池在平时不使用的时候是会自动放电的,为保护电池不要重复充电,所以才有此保护,低于95%才会进行充电,一般为一个月充电一次. 网络上有 ...
计算机电源已接通但未充电,笔记本电源,详细教您电源已连接未充电怎么解决...
笔记本虽好,但是也会碰到不少的麻烦,这不,最近,有用户反映自己的联想笔记本电脑在插上电源充电时,任务栏中的电源图标提示"电源已接通,未充电",仔细查看后确实发现笔记本的电量没有增加 ...
计算机电源接通显示未充电怎么办,笔记本电脑显示“电源已接通，未充电”怎么办？...
刚买了一台微星笔记本电脑,装完win7系统之后发现右下角电源那里显示"电源已接通,未充电",此时电脑的的电量是96%可用,并没有充满电,而且一直保持这种电量不变.可是明明已经接入电 ...
计算机电源接通但未充电,笔记本电脑电源已接通却显示未充电怎么办？
原标题:笔记本电脑电源已接通却显示未充电怎么办? 相信大家都有遇到过这样的情况,就是使用笔记本电脑久后,会提示电池电量不足,插入电源后,却显示"电源已接通,未充电",且一段时间过后 ...
Thinkpad x1“电源已接通，未充电”解决办法
现象 Windows电池管理提示:"电源已接通,未充电" 或 "plugged in but not charging". 修改电源管理计划无效,重启无效. 风 ...
关于ThinkPad笔记本电脑显示“电源已接通，未充电”
ThinkPad系列的笔记本经常会有电池方面的问题,最多的就是"电源已接通,未充电"这样令人头痛的问题(我已遇到三次,换了一次电源) 对于这种问题,我们基本尝试以下几种做法: 1. ...
计算机电源接通显示未充电怎么办,win10已接通电源,但不显示充电怎么办_win10电脑电源接通但未充电是怎么回事...
相信已经有许多用户已经使用win10系统电脑了,在使用过程中难免会出现一些问题.有些用户会遇到在给电脑接通电源时电脑却不显示充电的情况.遇到这个情况要怎么办,许多用户都不知道要怎么办,那么win10已 ...

电话接通与未接通，下层上报的状态

反复拨打电话，电话测试小程序，紧急电话与普通电话分枝判断

电话接通与未接通，下层上报的状态相关推荐

最新文章

热门文章