Android Telephony —— 手機信號實時變化源碼分析過程記錄

時間 2019-11-18

標籤 android telephony 手機信號實時變化源碼分析過程記錄欄目 Android 简体版

原文原文鏈接

源碼版本：4.4java

跳過InCallActivity等UI實現。先看service以及底層。android

1，在frameworks/opt下面會發現以下文件列表：app

./telephony/src/java/com/android/internal/telephony/cdma/CdmaServiceStateTracker.java
./telephony/src/java/com/android/internal/telephony/cdma/CdmaLteServiceStateTracker.java
./telephony/src/java/com/android/internal/telephony/gsm/GsmServiceStateTracker.java
./telephony/src/java/com/android/internal/telephony/gsm/GsmLteServiceStateTracker.java
./telephony/src/java/com/android/internal/telephony/ServiceStateTracker.java

2，能夠直接進入./telephony/src/java/com/android/internal/telephony/ServiceStateTracker.java 分析，很容易發現相似於以下的代碼：函數

619     /**
620      * send signal-strength-changed notification if changed Called both for
621      * solicited and unsolicited signal strength updates
622      *
623      * @return true if the signal strength changed and a notification was sent.
624      */
625     protected boolean onSignalStrengthResult(AsyncResult ar, boolean isGsm) {
626         SignalStrength oldSignalStrength = mSignalStrength;
627 
628         // This signal is used for both voice and data radio signal so parse
629         // all fields
630 
631         if ((ar.exception == null) && (ar.result != null)) {
632             mSignalStrength = (SignalStrength) ar.result;
633             mSignalStrength.validateInput();
634             mSignalStrength.setGsm(isGsm);
635         } else {
636             log("onSignalStrengthResult() Exception from RIL : " + ar.exception);
637             mSignalStrength = new SignalStrength(isGsm);
638         }
639 
640         return notifySignalStrength();
641     }

　　這裏主要是結構體的初始化以及上下文環境的簡單判斷。咱們繼續追蹤notifySignalStrength（）學習

229     private SignalStrength mLastSignalStrength = null;
230     protected boolean notifySignalStrength() {
231         boolean notified = false;
232         synchronized(mCellInfo) {
233             if (!mSignalStrength.equals(mLastSignalStrength)) {
234                 try {
235                     mPhoneBase.notifySignalStrength();
236                     notified = true;
237                 } catch (NullPointerException ex) {
238                     loge("updateSignalStrength() Phone already destroyed: " + ex
239                             + "SignalStrength not notified");
240                 }
241             }
242         }
243         return notified;
244     }

這裏有mSignalStrength 和 mLastSignalStrength 兩個和信號強度相關的量。算是找到切入點了，信號強度更新的中間點就是這裏了。this

3，咱們先向下分析看有什麼能夠學習的。 onSignalStrengthResult 是被　　frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmServiceStateTracker.java中handleMessage在Message Type是　　　　EVENT_GET_SIGNAL_STRENGTH的時候調用的：spa

 424             case EVENT_GET_SIGNAL_STRENGTH:
 425                 // This callback is called when signal strength is polled
 426                 // all by itself
 427 
 428                 if (!(mCi.getRadioState().isOn())) {
 429                     // Polling will continue when radio turns back on
 430                     return;
 431                 }
 432                 ar = (AsyncResult) msg.obj;
 433                 onSignalStrengthResult(ar, true);
 434                 queueNextSignalStrengthPoll();
 435 
 436                 break;

4，到這裏就須要對RIL有必定的瞭解纔好繼續追下去。RIL的event傳到上層以後主要經過一個叫作Registrant的機制分發的。code

　　咱們跳到frameworks/opt/telephony/src/java/com/android/internal/telephony/RIL.java中去。blog

　　這裏有主動去獲得signalstrength的方法：ci

1127     getSignalStrength (Message result) {
1128         RILRequest rr
1129                 = RILRequest.obtain(RIL_REQUEST_SIGNAL_STRENGTH, result, mIs2ndRil);
1130 
1131         if (RILJ_LOGD) riljLog(rr.serialString() + "> " + requestToString(rr.mRequest));
1132 
1133         send(rr);
1134     }

　　繼續往下看，接受到底層發來的數據後經過Registrant Notification：

2811             case RIL_UNSOL_SIGNAL_STRENGTH:
2812                 // Note this is set to "verbose" because it happens
2813                 // frequently
2814                 if (RILJ_LOGV) unsljLogvRet(response, ret);
2815 
2816                 if (mSignalStrengthRegistrant != null) {
2817                     mSignalStrengthRegistrant.notifyRegistrant(
2818                                         new AsyncResult (null, ret, null));
2819                 }
2820             break;

5，繼續追下去，咱們看到有主動經過RIL_REQUEST_SIGNAL_STRENGTH去request signal strength的。

　　因此直接在hardware/ril下搜關鍵字：RIL_REQUEST_SIGNAL_STRENGTH獲得結果以下：

./include/telephony/ril.h:1388: * RIL_REQUEST_SIGNAL_STRENGTH
./include/telephony/ril.h:1402:#define RIL_REQUEST_SIGNAL_STRENGTH 19
./libril/ril.cpp:3758:        case RIL_REQUEST_SIGNAL_STRENGTH: return "SIGNAL_STRENGTH";
./libril/ril_commands.h:36:    {RIL_REQUEST_SIGNAL_STRENGTH, dispatchVoid, responseRilSignalStrength},
./reference-ril/reference-ril.c:2093:        case RIL_REQUEST_SIGNAL_STRENGTH:
./reference-ril/ril.h:1388: * RIL_REQUEST_SIGNAL_STRENGTH
./reference-ril/ril.h:1402:#define RIL_REQUEST_SIGNAL_STRENGTH 19

　　很明顯是hardware/ril/reference-ril/reference-ril.c裏面以下函數被調用去查詢信號強度了，調用AT command等一看便知：

 839 static void requestSignalStrength(void *data, size_t datalen, RIL_Token t)
 840 {
 841     ATResponse *p_response = NULL;
 842     int err;
 843     char *line;
 844     int count =0;
 845     int numofElements=sizeof(RIL_SignalStrength_v6)/sizeof(int);
 846     int response[numofElements];
 847 
 848     err = at_send_command_singleline("AT+CSQ", "+CSQ:", &p_response);
 849 
 850     if (err < 0 || p_response->success == 0) {
 851         RIL_onRequestComplete(t, RIL_E_GENERIC_FAILURE, NULL, 0);
 852         goto error;
 853     }
 854 
 855     line = p_response->p_intermediates->line;
 856 
 857     err = at_tok_start(&line);
 858     if (err < 0) goto error;
 859 
 860     for (count =0; count < numofElements; count ++) {
 861         err = at_tok_nextint(&line, &(response[count]));
 862         if (err < 0) goto error;
 863     }
 864 
 865     RIL_onRequestComplete(t, RIL_E_SUCCESS, response, sizeof(response));
 866 
 867     at_response_free(p_response);
 868     return;