Forums - Error during MSDC initialization

3 posts / 0 new
Last post
Error during MSDC initialization
giuseppe.merlino
Join Date: 15 Jan 19
Posts: 2
Posted: Mon, 2019-05-06 05:30

Hello,

I'm using a Sonim XP8 and MSDC SDK 4.2.03.03.

During the initialization I got the following error:

Unable to start service Intent { act=com.qualcomm.ltebc.aidl.ILTERootService flg=0x10000000 pkg=com.qualcomm.ltebc (has extras) } U=0: not found

 

Does it mean that  LTE Broadcast Manager MSDC is not installed?

Thank you for your support,

Giuseppe

 

 

 

  • Up0
  • Down0
pcheekat
Join Date: 20 May 19
Posts: 3
Posted: Wed, 2019-07-03 04:31

Please check below package is installed or not. Due to this it not able to find com.qualcomm.ltebc.aidl.ILTERootService.

com.qualcomm.ltebc

  • Up0
  • Down0
giuseppe.merlino
Join Date: 15 Jan 19
Posts: 2
Posted: Fri, 2019-07-05 01:15

I got from Sonim an OTA update including the middleware.

Using your sample app (but also our implementation) I got a crash in the Lte Broadcas Manager during the init procedure for a Group Call.

 

This is the crash report:

 

2019-06-25 11:32:29.664 20971-21005/? I/LTE Application: getCellPLMN() invoked from Android L or higher
2019-06-25 11:32:29.664 20971-21005/? I/LTE Application: getCellPLMN: 
2019-06-25 11:32:29.665 20971-21005/? I/LTE Application: getCellPLMN: cellList size = 1
2019-06-25 11:32:29.665 20971-21005/? I/LTE Application: getCellPLMN: print all available CellInfo = [CellInfoLte:{mRegistered=YES mTimeStampType=oem_ril mTimeStamp=63827466817628ns CellIdentityLte:{ mMcc=1 mMnc=1 mCi=257 mPci=201 mTac=201 mEarfcn=2800} CellSignalStrengthLte: ss=17 rsrp=-102 rsrq=-6 rssnr=2147483647 cqi=2147483647 ta=3}]
2019-06-25 11:32:29.665 20971-21005/? I/LTE Application: getCellPLMN: Candidate Cell CellInfoLte:{mRegistered=YES mTimeStampType=oem_ril mTimeStamp=63827466817628ns CellIdentityLte:{ mMcc=1 mMnc=1 mCi=257 mPci=201 mTac=201 mEarfcn=2800} CellSignalStrengthLte: ss=17 rsrp=-102 rsrq=-6 rssnr=2147483647 cqi=2147483647 ta=3}
2019-06-25 11:32:29.665 20971-21005/? I/LTE Application: LTE Cell :CellInfoLte:{mRegistered=YES mTimeStampType=oem_ril mTimeStamp=63827466817628ns CellIdentityLte:{ mMcc=1 mMnc=1 mCi=257 mPci=201 mTac=201 mEarfcn=2800} CellSignalStrengthLte: ss=17 rsrp=-102 rsrq=-6 rssnr=2147483647 cqi=2147483647 ta=3} isReg:true mcc:1 mnc:1
2019-06-25 11:32:29.665 20971-21005/? I/LTE Application: We're registered with this LTE Cell. mcc:1 mnc:1
2019-06-25 11:32:29.665 20971-21005/? I/LTE Application: Found cellPLMN: 001001 from mcc/mnc: 1/1
2019-06-25 11:32:29.665 20971-21005/? I/LTE Application: getCurrentPLMNsAndRoamingState: getIsRoamingForSub sub = 1
2019-06-25 11:32:29.666 20971-21005/? I/LTE Application: getCurrentPLMNsAndRoamingState: getIsRoamingForSub(API Level 22) isRoaming = false
2019-06-25 11:32:29.667 2372-2440/? I/TelephonyManager: getMultiSimConfiguration(): uid =10098
2019-06-25 11:32:29.668 20971-21005/? I/LTE Application: SubscriptionManager New API. simStateID:5 simPLMN:001001 cellPLMN:001001 isRoaming:false
2019-06-25 11:32:29.668 20971-21005/? I/LTE Application: enableUnicastInRoaming:false isRoamingFlag:false
2019-06-25 11:32:29.668 20971-21005/? I/LTE Application: mRoamingTimerTask: CellPLMN: 001001 isRoaming: false simState: 5 simPLMN: 001001
2019-06-25 11:32:29.668 20971-21005/? I/LTE Application: mNewCellPLMN = 001001, mCellPLMN = 001001, mIsRoaming = false, mNewIsRoaming = false, mNewIsWiFiConnected = false, mIsWiFiConnected = false, mNewIsLTEConnected = true, mIsLTEConnected = false
2019-06-25 11:32:29.668 20971-21005/? I/LTE Application: Detected changed cellPLMN/roaming. PLMN:001001, was:001001. isRoaming:false, was:false. mNewIsWiFiConnected = false, was: mIsWiFiConnected = false, mNewIsLTEConnected = true , mIsLTEConnected was : false while in state mIsMSPInitialized(true) mIsMSPInitPending(false)
2019-06-25 11:32:29.669 20971-21005/? I/LTE Application:  calling .. jNetworkStateUpdate 
2019-06-25 11:32:29.669 20971-21005/? I/LTE Application:  calling jNetworkStateUpdate with cellPLMN:001001 isRoamingState: 0 isWiFiConnected: 0 isLTEConnected: 1
2019-06-25 11:32:29.669 20971-21005/? I/MSP-JNI: networkStateUpdate CELLPLMN - 001001 , RoamingState - 0, lteConnState -1 
2019-06-25 11:32:29.669 20971-21005/? I/MSP-JNI: networkStateUpdate() invoked with data aCELLPLMNString - lteConnecetdState - %d ,Roaming State from platform - -284226900 ,wifiConnectedState - 0
2019-06-25 11:32:29.670 20971-21005/? I/LTE Application:  called .. jNetworkStateUpdate
2019-06-25 11:32:29.921 20916-20916/com.qualcomm.msdc_api_examples I/MSDC_API_MSDCGroupCallController: startGroupCallService: 69: startGroupCallService: 3741380880
2019-06-25 11:32:29.922 20916-20916/com.qualcomm.msdc_api_examples I/MSDC_API_MSDCGroupCallModelImpl: addGroupCallServiceToModel: 42: addGroupCallServiceToModel
2019-06-25 11:32:29.923 20916-20969/com.qualcomm.msdc_api_examples I/AIDL: ServiceParameter CreateBody added:{"saiNumber":1}
2019-06-25 11:32:29.924 20916-20969/com.qualcomm.msdc_api_examples I/AIDL: ServiceParameter CreateBody added:{"saiNumber":2}
2019-06-25 11:32:29.924 20916-20969/com.qualcomm.msdc_api_examples I/AIDL: ServiceParameter CreateBody added:{"freqNumber":5000}
2019-06-25 11:32:29.924 20916-20969/com.qualcomm.msdc_api_examples I/AIDL: ServiceParameter CreateBody added:{"freqNumber":5001}
2019-06-25 11:32:29.924 20916-20969/com.qualcomm.msdc_api_examples I/AIDL: ServiceParameter toJsonString {"message":{"appInstanceId":"10117com.qualcomm.msdc_api_examples1676918901_GC_1561455144255","header":{"type":"startService","version":"20.10.00","typeId":58,"serviceType":3},"body":{"tmgi":3741380880,"saiList":[{"saiNumber":1},{"saiNumber":2}],"freqList":[{"freqNumber":5000},{"freqNumber":5001}]}}}
2019-06-25 11:32:29.925 20971-21033/? I/LTE Service: startService: app instance id: 10117com.qualcomm.msdc_api_examples1676918901_GC_1561455144255
2019-06-25 11:32:29.925 20971-21033/? I/LTE Service: processServiceRequest: app instance id: 10117com.qualcomm.msdc_api_examples1676918901_GC_1561455144255
2019-06-25 11:32:29.925 20971-21033/? I/LTE Service: processServiceRequest: requestName: startService
2019-06-25 11:32:29.925 20971-21033/? I/LTE Service: processServiceRequest : startService:{"message":{"appInstanceId":"10117com.qualcomm.msdc_api_examples1676918901_GC_1561455144255","header":{"type":"startService","version":"20.10.00","typeId":58,"serviceType":3},"body":{"tmgi":3741380880,"saiList":[{"saiNumber":1},{"saiNumber":2}],"freqList":[{"freqNumber":5000},{"freqNumber":5001}]}}}
2019-06-25 11:32:29.925 20971-21033/? E/LTE Service: sendJsonRequest: Sending msg. Id: 10117com.qualcomm.msdc_api_examples1676918901_GC_1561455144255
2019-06-25 11:32:29.925 20971-21033/? W/SOCKET: addoutbuffer is called
2019-06-25 11:32:29.926 20971-21033/? W/SOCEKT: add buffer to queue
2019-06-25 11:32:29.926 20971-21033/? W/SOCKET: data has been put in a queue{"message":{"appInstanceId":"10117com.qualcomm.msdc_api_examples1676918901_GC_1561455144255","header":{"type":"startService","version":"20.10.00","typeId":58,"serviceType":3},"body":{"tmgi":3741380880,"saiList":[{"saiNumber":1},{"saiNumber":2}],"freqList":[{"freqNumber":5000},{"freqNumber":5001}]}}}
2019-06-25 11:32:29.926 20971-21038/? W/SOCKET: Waiting on selector 
2019-06-25 11:32:29.926 20971-21038/? W/SOCKET: handleSockets either key is not valie or key is not connectible  
2019-06-25 11:32:29.926 20971-21038/? W/SOCKET: handleSockets key is not readable 
2019-06-25 11:32:29.926 20971-21038/? W/SOCKET: take out the buffer from the identifier10117com.qualcomm.msdc_api_examples1676918901_GC_1561455144255
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: Size of the buffer1
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: Size of the reduced to buffer0
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: Size of the buffer reading it again0
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: send the data
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: Data has be send java.nio.HeapByteBuffer[pos=300 lim=300 cap=300]
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: Socket is writeable so write to it
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: Waiting on selector 
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: handleSockets either key is not valie or key is not connectible  
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: handleSockets key is not readable 
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: take out the buffer from the identifier10117com.qualcomm.msdc_api_examples1676918901_GC_1561455144255
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: buffer has no data
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: write data is null
2019-06-25 11:32:29.927 20971-21038/? W/SOCKET: Socket is writeable so write to it
2019-06-25 11:32:29.928 20971-21038/? W/SOCKET: Waiting on selector 
2019-06-25 11:32:29.928 20971-21038/? W/SOCKET: Waiting on selector 
2019-06-25 11:32:29.928 20971-21033/? I/LTE Service: startService: result: 0
2019-06-25 11:32:29.929 20916-20969/com.qualcomm.msdc_api_examples I/MSDC_API_MSDCAppManagerImpl: isMSDCTerminated: 467: isMSDCTerminated : false
2019-06-25 11:32:29.957 20971-21030/? A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 21030 (Thread-10)
2019-06-25 11:32:30.026 21051-21051/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG: Build fingerprint: 'Sonim/XP8861/XP8800:7.1.1/8A.0.0-01-7.1.1-31.00.18/25:user/release-keys'
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG: Revision: '0'
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG: ABI: 'arm'
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG: pid: 20971, tid: 21030, name: Thread-10  >>> com.qualcomm.ltebc <<<
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG:     r0 00000000  r1 00005226  r2 00000006  r3 00000008
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG:     r4 d47ff978  r5 00000006  r6 d47ff920  r7 0000010c
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG:     r8 d6f361a8  r9 d47fea84  sl f0762290  fp d47fea5c
2019-06-25 11:32:30.027 21051-21051/? A/DEBUG:     ip 0000000b  sp d47fe990  lr f1461cd3  pc f14645ec  cpsr 600f0010
2019-06-25 11:32:30.038 21051-21051/? A/DEBUG: backtrace:
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #00 pc 0004a5ec  /system/lib/libc.so (tgkill+12)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #01 pc 00047ccf  /system/lib/libc.so (pthread_kill+34)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #02 pc 0001da5d  /system/lib/libc.so (raise+10)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #03 pc 00019455  /system/lib/libc.so (__libc_android_abort+34)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #04 pc 000174b0  /system/lib/libc.so (abort+4)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #05 pc 00916300  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN9__gnu_cxx27__verbose_terminate_handlerEv+344)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #06 pc 00914be8  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN10__cxxabiv111__terminateEPFvvE+4)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #07 pc 00914c30  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZSt9terminatev+24)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #08 pc 00914d90  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (__cxa_throw+156)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #09 pc 00903d5c  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZNK4Json5Value5asIntEv+328)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #10 pc 005163eb  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3adp18MspStartServiceMsg6unpackERN4Json5ValueE+1762)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #11 pc 005130b9  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3adp11msg_handler14handle_messageERN4Json5ValueERN3csw4base10shared_ptrINS_12base_messageEEE+1236)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #12 pc 004f2989  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3adp11mss_manager14handle_messageERN4Json5ValueERKi+512)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #13 pc 004f361d  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3adp32msdc_socket_server_callback_impl7receiveERN4Json5ValueERKi+272)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #14 pc 00879117  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3adp15client_conn_mgr14handle_messageEi+722)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #15 pc 00879a27  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3adp27transport_mgr_callback_impl14receive_notifyEN3csw4base10shared_ptrISsEEii+370)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #16 pc 00882f03  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3adp13transport_mgr10handleReadEi+2030)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #17 pc 008839d9  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3adp13transport_mgr12handle_eventEN3csw4base10shared_ptrINS1_3net15tcpclientsocketEEEi+652)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #18 pc 00883b85  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3csw3net22fdiomultiplexermanager17fd_object_wrapperINS_4base10shared_ptrINS0_15tcpclientsocketEEEPN3adp13transport_mgrEE19handle_object_eventEi+36)
2019-06-25 11:32:30.039 21051-21051/? A/DEBUG:     #19 pc 0089e7b7  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3csw3net22fdiomultiplexermanager16poll_multiplexerEi+254)
2019-06-25 11:32:30.040 21051-21051/? A/DEBUG:     #20 pc 0089e88b  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3csw3net22fdiomultiplexermanager5startEv+50)
2019-06-25 11:32:30.040 21051-21051/? A/DEBUG:     #21 pc 005e0819  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3csw4base6thread7executeEv+28)
2019-06-25 11:32:30.040 21051-21051/? A/DEBUG:     #22 pc 005e07ed  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZN3csw4base6thread3runEPv+28)
2019-06-25 11:32:30.040 21051-21051/? A/DEBUG:     #23 pc 003dd8d9  /system/app/QAS_DVC_MSP/lib/arm/libmsp.so (_ZL26mfosal_thread_main_wrapperPv+20)
2019-06-25 11:32:30.040 21051-21051/? A/DEBUG:     #24 pc 000477a3  /system/lib/libc.so (_ZL15__pthread_startPv+22)
2019-06-25 11:32:30.040 21051-21051/? A/DEBUG:     #25 pc 00019eb1  /system/lib/libc.so (__start_thread+6)
2019-06-25 11:32:30.999 1716-1788/? I/BootReceiver: Copying /data/tombstones/tombstone_01 to DropBox (SYSTEM_TOMBSTONE)
 
 
 

 

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.