893616 - [Helix]When send a mmi:"*#06#", it display error! (we use QCOM B2G_Telephony, ver:1230)

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Vendcom, defect)

Description

[wangchao]

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; Tablet PC 2.0)

Steps to reproduce:

1.open dialer: dial *#06# and call


Actual results:

1. it should display the IMEI Number


Expected results:

1. display error.

That i do:
1. according to the log:mmi.txt (in the attachement), the mmi command return 'OK' with the IMEI number, but it is not the struct that mozilla need.
2. The mozilla gaia and QC b2g_telephony are not adapt to each other. 


Thanks!

Comment 1

[wangchao]

Attachment: log for ap

Comment 2

[Wayne Chang [:wchang]]

Hi Shawn,
Can you check this one? Keven may have some info.

Comment 3

[shawn ku [:sku]]

07-11 17:52:54.649 I/Gecko   (  451): -*- RILContentHelper: Sending MMI *#06#
07-11 17:52:54.659 I/Gecko   (  148): -*- QCContentHelper_QC_B2G: receiveMessage: 'RIL:SendMMI' arrived from content process
07-11 17:52:54.659 I/Gecko   (  148): -*- QCContentHelper_QC_B2G: saveRequestTarget: RIL:SendMMI
07-11 17:52:54.659 I/Gecko   (  148): -*- QCContentHelper_QC_B2G: SendMMI dialstring: *#06#
07-11 17:52:54.659 I/Gecko   (  148): -*- QCContentHelper_QC_B2G: _parseMMI dialstring: *#06#
07-11 17:52:54.659 I/Gecko   (  148): -*- QCContentHelper_QC_B2G: SendMMI poundString:*#06# action:*# serviceCode:06 sia:undefined sib:undefined sic:undefined pwd:undefined dialingNumber:
07-11 17:52:54.659 D/PHONE_QC_B2G(  148): dialing w/ mmi MmiCode { action=*# serviceCode=06 poundString=*#06#}
07-11 17:52:54.659 D/MMI_CODE_QC_B2G(  148): Dial string is IMEI command
07-11 17:52:54.659 I/Gecko   (  148): -*- QCContentHelper_QC_B2G: sendMessage to content process: RIL:SendMMI:Return:OK{ requestId : 'id{3991d87a-2290-4964-9552-7775851e3ace}', result : '222222222222228',  }
07-11 17:52:54.669 I/Gecko   (  148): -*- QCContentHelper_QC_B2G: sendRequestResults: RIL:SendMMI:Return:OK
07-11 17:52:54.679 I/Gecko   (  451): -*- RILContentHelper: Received message 'RIL:SendMMI:Return:OK': {"requestId":"id{3991d87a-2290-4964-9552-7775851e3ace}","result":"222222222222228"}
07-11 17:52:54.679 I/Gecko   (  451): -*- RILContentHelper: handleSendCancelMMI {"requestId":"id{3991d87a-2290-4964-9552-7775851e3ace}","result":"222222222222228"}

Comment 4

[shawn ku [:sku]]

from attached log, it looks like *#06# + call was parsed as IMEI request, not USSD.
hence, there is no any error(error due to operator do not recognize *#06# USSD request) displayed on UI.

Comment 5

[wangchao]

*#06# is just used as IMEI request.

The following is the struct that pass to RILContentHelper.js
07-11 17:52:54.679 I/Gecko   (  451): -*- RILContentHelper: handleSendCancelMMI {"requestId":"id{3991d87a-2290-4964-9552-7775851e3ace}","result":"222222222222228"}

But the function that handle it can not prase it. The interface is not correct.
case "RIL:SendMMI:Return:OK":
      case "RIL:CancelMMI:Return:OK":
      case "RIL:SendMMI:Return:KO":
      case "RIL:CancelMMI:Return:KO":
        this.handleSendCancelMMI(msg.json);  //you can see the details
        break;

So it fireError and the UI display error.

Comment 6

[wangchao]

Please check the latest version for the code. It's just the interface mismatch.

Comment 7

[Fernando Jiménez Moreno [:ferjm]]

I can confirm that this looks like an interface mismatch because of the changes introduced in bug 883178.

The RILContentHelper expects a message like:

{"mmi":"*#06#","requestId":"id{3991d87a-2290-4964-9552-7775851e3ace}","rilMessageType":"sendMMI","mmiServiceCode":"scImei","success":true,"statusMessage":"222222222222228"}

Carol, are the required changes already done in the QC RIL?

Comment 8

[Carol Yang [:cyang]]

The changes in commerical RIL are already in. I believe an old AU was being used to test. Please use AU 157 or later.

Comment 9

[wangchao]

But QC ask we to use M76XXUSNEKNFYA1230.xml to match its B2G_Telephony!

It means we have to change to use AU 157 or later?

Thanks!

Comment 10

[Wayne Chang [:wchang]]

wangchao,

Please do try a new AU as Carol suggested.

Comment 11

[Carol Yang [:cyang]]

Hi wangchao, please raise an SR to get the changes mentioned in Comment 8.

Comment 12

[wangchao]

Please provide the full name of AU 157, Such as M76XXUSNEKNFYA1230.xml.

Thanks!

Comment 13

[Carol Yang [:cyang]]

Hi wangchao, please raise an SR and we can discuss the build ID you'll need there.

Comment 14

[wangchao]

I have raise a SR:01255276。

Thanks！

Comment 15

[Michael Vines [:m1] [:evilmachines]]

Perfect, thanks.  I'll resolved this bug as there is no action here.

For the future please try to create SRs for RIL issues as this is not supported via Bugzilla.

Comment 16

[wangchao]

TO Carol Yang: 

Our tam can't find solution for this problem, please give some advices in SR:01255276。

Thanks!