标签：
《Android 4.4 Kitkat Phone工作流程浅析(二)__UI结构分析》
《Android 4.4 Kitkat Phone工作流程浅析(三)__MO(去电)流程分析》
《Android 4.4 Kitkat Phone工作流程浅析(四)__RILJ工作流程简析》
《Android 4.4 Kitkat Phone工作流程浅析(五)__MT(来电)流程分析》
而在Android 4.4中。InCallActivity的显示则是由Call状态来决定的，Call的状态能够分为6种：ACTIVE、HOLDING、DIALING、ALERTING、INCOMING、WAITING。当发起MO流程而且对方还未接通这段时间。Call的状态是DIALING。
01-01 18:11:47.039 1061 1061 D RILJ : RIL(1) :[0147]> DIAL
... ...省略
01-01 18:11:47.044 682 692 D use-Rlog/RLOG-AT: AT> ATD13800138000;
01-01 18:11:47.044 682 696 I use-Rlog/RLOG-RIL: RIL_URC2_PROXY wakeup
01-01 18:11:47.044 682 692 D use-Rlog/RLOG-AT: ATD13800138000;
... ...省略
01-01 18:11:47.047 682 707 D use-Rlog/RLOG-AT: OK
01-01 18:11:47.047 682 707 D use-Rlog/RLOG-AT: AT< OK
01-01 18:11:47.047 682 707 D use-Rlog/RLOG-AT: RIL_CMD_READER_2:OK
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT:
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: +CIEV: 5, 1
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT:
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: +ECPI: 1,130,0,0,0,0,"13800138000",129,""
01-01 18:11:47.047 682 707 D use-Rlog/RLOG-AT: RIL_CMD_READER_2 Enter processLine
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: AT< +CIEV: 5, 1
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: RIL_URC_READER:+CIEV: 5, 1
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: RIL_URC_READER Enter processLine
01-01 18:11:47.047 682 707 I use-Rlog/RLOG-AT: AT read start
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-RIL: Nw URC:+CIEV: 5, 1
01-01 18:11:47.047 682 705 E use-Rlog/RLOG-RIL: Unhandled unsolicited result code: +CIEV: 5, 1
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: AT< +ECPI: 1,130,0,0,0,0,"13800138000",129,""
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: RIL_URC_READER:+ECPI: 1,130,0,0,0,0,"13800138000",129,""
01-01 18:11:47.047 682 692 D use-Rlog/RLOG-AT: response received on RIL_CMD_READER_2, tid:3086469296
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: RIL_URC_READER Enter processLine
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-RIL: Nw URC:+ECPI: 1,130,0,0,0,0,"13800138000",129,""
... ...省略
01-01 18:11:47.048 1061 1274 D RILJ : RIL(1) :[0147]< DIAL
01-01 18:11:47.048 1061 1274 V RILJ : RIL(1) :[UNSL RIL]< UNSOL_CALL_PROGRESS_INFO {1, 130, 0, 0, 0, 0, 13800138000, 129, }这里简单的分析一下重要的log信息：RIL(1) :[0147]> DIAL这表示发起DIAL请求。紧接着运行ATD即AT拨号指令：
01-01 18:11:47.044 682 692 D use-Rlog/RLOG-AT: AT> ATD13800138000;我们在《Android 4.4 Kitkat Phone工作流程浅析(四)__RILJ工作流程简析》文章中有讲过。能够依据serial号查看AT指令的配对。同一时候也提到了Log中的“＞”和“＜”所代表的含义。即“＞”表示request，“＜”表示response，上面两条log信息能够解释为RILJ发起了两次request请求。
依据第一条AT指令的serial号"0147"我们能够在后面找到相应的response：
01-01 18:11:47.048 1061 1274 D RILJ : RIL(1) :[0147]< DIAL这表明整个拨号的request和response已经完毕，在此期间Modem主动返回了下面信息：
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: AT< +ECPI: 1,130,0,0,0,0,"13800138000",129,""该条AT指令+ECPI是MTK加入的。在标准AT指令中查询不到，详细含义例如以下：
相应着这个表我们来梳理一下
01-01 18:11:47.047 682 705 D use-Rlog/RLOG-AT: AT< +ECPI: 1,130,0,0,0,0,"13800138000",129,""以上log重要信息例如以下：
01-01 18:11:47.048 1061 1274 V RILJ : RIL(1) :[UNSL RIL]< UNSOL_CALL_PROGRESS_INFO {1, 130, 0, 0, 0, 0, 13800138000, 129, }这是一条UnSolicited response消息，处理方法是RIL.java中的processUnsolicited()，类型为：UNSOL_PROGRESS_INFO。RIL.java将处理之后的消息通过notifyRegistrants()的方式传递给GsmCallTracker。在GsmCallTracker的handleCallProcessInfo()方法中能够看到是怎样定义Call状态为DIALING的。代码例如以下：
//... ... 省略部分代码
if (msgType == 132 || msgType == 6)
dc.state = DriverCall.State.ACTIVE;
else if (msgType == 131)
dc.state = DriverCall.State.HOLDING;
else if (msgType == 130 && callId != 254)
//从log中能够看到msgType=130,call_id=1
dc.state = DriverCall.State.DIALING;
else if (msgType == 2)
dc.state = DriverCall.State.ALERTING;
else if (msgType == 0)
{
for (j = 0; j < MAX_CONNECTIONS; j++) {
if (mConnections[j] != null) {
count ++;
}
}
if (mState == PhoneConstants.State.IDLE ||
(count == 0 && mForegroundCall.getState() == GsmCall.State.DIALING))
{
/* if the 2nd condition is true, that means we make a MO call, receiving +ECPI: 130,
* then receiving +ECPI: 133 immediately due to MT call (+ECPI: 0) is receiving*/
if (count == 0 && mForegroundCall.getState() == GsmCall.State.DIALING)
log("MO/MT conflict!!");
dc.state = DriverCall.State.INCOMING;
}
else
dc.state = DriverCall.State.WAITING;
}当状态改变之后便会通过GsmPhone的notifyPreciseCallStateChanged()方法发起响应。例如以下：if ((hasNonHangupStateChanged || newRinging != null) && crssAction != CrssAction.SWAP && !(hasPendingReplaceRequest && msgType == 133)) {
log("notify precise call state changed");
mPhone.notifyPreciseCallStateChanged();
}之后会通过观察者模式方式调用到CallManager的handleMessage()方法中，case为EVENT_PRECISE_CALL_STATE_CHANGED。代码例如以下：case EVENT_PRECISE_CALL_STATE_CHANGED:
//... ...省略部分代码
index = (msg.what - EVENT_PRECISE_CALL_STATE_CHANGED) / NOTIFICATION_ID_OFFSET;
mPreciseCallStateRegistrantsGemini[index].notifyRegistrants((AsyncResult) msg.obj);
mPreciseCallStateRegistrants.notifyRegistrants((AsyncResult) msg.obj);
handle3GSwitchLock();这里会有MTK的Gemini处理，即双卡处理，通过相同的观察者模式将状态改变信息通过notifyRegistrants()方法发送到TeleService中。整个流程例如以下图：
同一时候CallNotifier和CallModeler均注冊了CallStateMonitor的状态改变回调。一旦Call状态改变便会通知CallNotifier和CallModeler。这里CallNotifier并没有做什么大的动作，仅仅是更新了近距离感应器的状态，推断是否接通假设接通则震动这类。跟界面相关的调用则在CallModeler中。
if (!ignoreUpdate()) {
if (updatedCalls.size() > 0) {
for (int i = 0; i < mListeners.size(); ++i) {
mListeners.get(i).onUpdate(updatedCalls);
}
}
}这里会触发BluetoothManager、CallHandlerServiceProxy、DTMFTonePlayer三个类中的onUpdate()方法回调，这里我们查看CallHandlerServiceProxy中的onUpdate()方法就可以。对于上面的代码再多说几句，原生Android 4.4中，CallModeler的onPhoneStateChanged方法并没有ignoreUpdate()方法，这是MTK增加的主要目的是用于推断是否忽略本次界面更新。用于自己主动拒接和高速挂断正在响铃的电话两种场景。代码例如以下： /*
* The function to judge whether should skip update calls to InCallUI,
* for auto reject case, or quick hang up ringing case.
* When 1A + 1R, if ringing call is hanged up while query(ringtone),
* CallNotifier will not notify InCallUI the onIncoming(), then we should ignore update calls to InCallUI;
* or will show callcard with ringing call information but no AnswerFragment shown.
*/
private boolean ignoreUpdate() {
boolean shouldIgnore = false;
final boolean hasActiveFgCall = mCallManager.hasActiveFgCall();
final boolean hasActiveBgCall = mCallManager.hasActiveBgCall();
shouldIgnore = (hasActiveFgCall || hasActiveBgCall) && PhoneGlobals.getInstance().notifier.hasPendingCallerInfoQuery();
Log.i(TAG, "ignoreUpdate()... shouldIgnore: " + shouldIgnore);
return shouldIgnore;
}通过代码能够非常清楚的知道，当CallerInfo没有查询完成时hasPendingCallerInfoQuery()返回true，则忽略本次界面更新。@Override
public void onUpdate(List<Call> calls) {
synchronized (mServiceAndQueueLock) {
if (mCallHandlerServiceGuarded == null) {
//设置更新类型为METHOD_UPDATE
enqueueUpdate(calls);
//与CallHandlerService建立连接
setupServiceConnection();
return;
}
}
//运行更新
processUpdate(calls);
}更新类型包含：
@Override
public void onUpdate(List<Call> calls) {
try {
Log.i(TAG, "onUpdate: " + calls);
//注意：这里的类型是ON_UPDATE_MULTI_CALL
mMainHandler.sendMessage(mMainHandler.obtainMessage(ON_UPDATE_MULTI_CALL, calls));
} catch (Exception e) {
Log.e(TAG, "Error processing onUpdate() call.", e);
}
}这里非常奇怪的一点是。类型竟然是ON_UPDATE_MULTI_CALL，而代码中也有ON_UPDATE_CALL类型。这是google原生的。MTK没有改过。不知道是何用意。 /**
* Sends a generic notification to all listeners that something has changed.
* It is up to the listeners to call back to determine what changed.
*/
private void notifyListenersOfChange() {
for (Listener listener : mListeners) {
listener.onCallListChange(this);
}
}这里会运行listener的回调，分别在AnswerPresenter和InCallPresenter中。CallList仅仅是负责将状态改变通知到listener，是否处理则由listener们自己决定。AnswerPresenter仅仅有在incoming的时候才会处理。因此这里应该查看InCallPresenter的onCallListChange()方法： @Override
public void onCallListChange(CallList callList) {
if (callList == null) {
return;
}
InCallState newState = getPotentialStateFromCallList(callList);
//这里去推断是否显示/关闭InCallActivity
newState = startOrFinishUi(newState);
//... ...省略部分代码
}这里会跳转到startOrFinishUi()中进行推断，由于是第一次启动InCallActivity界面。最后会通过startActivity()的方式启动InCallActivity，到此整个InCallActivity的界面显示流程就结束了。兴许Modem側状态改变则依据该流程传递到InCallPresenter，由InCallPresenter来响应不同的状态所须要启动/关闭的界面。整个流程例如以下图：
public void updateCalls() {
final List<Call> updatedCalls = Lists.newArrayList();
doUpdate(true, updatedCalls);
if (!ignoreUpdate()) {
if (updatedCalls.size() > 0) {
for (int i = 0; i < mListeners.size(); ++i) {
mListeners.get(i).onUpdate(updatedCalls);
}
}
}
} 注意：该方法是MTK自己加入的，原生AOSP并没有，假设想使用也能够仿照这样的方式加入。Android 4.4 Kitkat Phone工作流程浅析(六)__InCallActivity显示更新流程
标签：
原文地址：http://www.cnblogs.com/yxwkf/p/5236263.html
