Forums - Difference between MSDC API stub .jar and MSDC API LA .aar for embms

4 posts / 0 new
Last post
Difference between MSDC API stub .jar and MSDC API LA .aar for embms
sashwatkumar.p
Join Date: 14 Nov 17
Posts: 9
Posted: Mon, 2018-03-12 06:39

Hello,

When we download the entire SDK, there is one .jar file which is for stub testing and a .aar file named msdc_api-MSDC_LA_4.2.01.04.0.aar. When i add .jar as a library I am able to get the appropriate callbacks for groupcall service(like groupCallServiceStarted) even if MSDC middleware is not installed on the device. However when i use .aar file , even if the middleware is installed on the device , groupcall service state is returning null (using the api mGroupCallModel.getGroupCallServiceState). Can you please mention the basic difference between this stub .jar file and msdc_api .aar file? How come appropriate call backs for groupcall service comes even if middleware is not installed in case of stub .jar? If i use .aar file , will the callbacks for groupcallservice work only if proper LTE Network and Middleware is setup? 

  • Up0
  • Down0
AnkitK Moderator
Join Date: 20 Aug 14
Posts: 61
Posted: Wed, 2018-03-14 11:40

Dear Customer,

 

STUB (jar) : Is designed & given to UI developers to test their UI Application. The stub doesn’t require the middleware. The Stub returns success values for the APIs queried by the UI.

 

MSDC_API (aar) : This is the actual SDK which works only with Middleware and LTE Network.

 

Thanks

Ankit

  • Up0
  • Down0
bereket
Join Date: 1 May 18
Posts: 11
Posted: Tue, 2018-05-22 01:31

For the eMBMS isn't it .aar is enough ? do we need another Middleware to be installed on the mobile device ?

  • Up0
  • Down0
AnkitK Moderator
Join Date: 20 Aug 14
Posts: 61
Posted: Tue, 2018-05-22 13:17

.aar is required to communicate with MSDC (middleware).

In case of absense of MSDC on the device, STUB (.jar) should be used.

  • 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.