928208 - [B2G][Helix][tongxiao]The ussd msg will not disappear after a while .

Status: RESOLVED DUPLICATE of bug 905577

(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)

Description

[lecky]

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; MALC; aff-kingsoft-ciba; .NET4.0C; .NET4.0E; Tablet PC 2.0)

Steps to reproduce:

Steps to reproduce:

【Detail Description*】：The received ussd msg will not disappear after several minutes If you do nothing.
【Repro Steps*】：
1. The UE receive a ussd msg .
2. do nothing for several minutes.
3. check the interface.

【Expect Result*】：The ussd msg will disappear .
【Real Result*】：The ussd msg will not  disappear .but after a while the interface will display "Generic failure"
【Test Count*】：10
【Found Count*】：10
【Gaia commit ID*】:c0ea0a4943dc8d3751b07f5b5c5d3abe06364a14 
【Gecko commit ID*】: 170f9e477571127cd40997fa2abe262ed43f0e4d
【Log*】：
【Network environment】：
【Resume operation】：
【Carrier】：

Comment 1

[lecky]

Hi,
   Do you think this is a feature or a blocker? Will you modify it in v1.1?

Comment 2

[shawn ku [:sku]]

Hi Lecky:
 Please provide logcat log (adb logcat -b main -b radio -v threadtime > c:/temp/logcat.log) for us to check this issue.

I would like to know what modem report to gecko/gaia.

Thanks!!
sku

Comment 3

[lecky]

Attachment: 1018log.txt

Comment 4

[lecky]

Hi,
  I have uploaded the log --"1018log.txt".

Comment 5

[shawn ku [:sku]]

Hi Lecky:
  I did not see any "RIL Worker" (for gecko), and "RIL" for RILD part.
The only thing is below.

10-18 15:55:09.693: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendMessage to content process: RIL:USSDReceived{ message : '@*100@0123456789012345678901234567890123456789012345678901234567890123456789012', sessionEnded : false,  }


Are you concenring about "The received ussd msg will not disappear"?
If yes, this is by design.

Besides, I would like to check the problem - "but after a while the interface will display "Generic failure".
however, there isn't too mush I can see from your attachment regarding USSD.

Please provide me more detail information (eq: steps, screenshot, log wth "RIL" keyword etc...) if you are available to do so.
Thanks!!
sku

Comment 6

[lecky]

Hi shawn ku  ,
  Do you find this problem in the ussd test?

Thanks!

Comment 7

[shawn ku [:sku]]

Hi Lecky:
 I did not get the point about "ussd test".

There is no such failure reported so far.
Besides, we can not test this item in live network@TW.

Please provide me more RIL related log to check this case if possible.

Thanks!!
sku

Comment 8

[lecky]

Hi ,
   As the ffos design,will the ussd msg disappear after several minutes If you do nothing ?

Comment 9

[shawn ku [:sku]]

No, USSD will not be dimssied w/o user input.

As reply on Comment 5.

"Are you concenring about "The received ussd msg will not disappear"?
If yes, this is by design."

Comment 10

[lecky]

Attachment: 2013-10-21-14-37-16.png

Comment 11

[lecky]

Attachment: 2013-10-21-14-40-11.png

Comment 12

[lecky]

Hi,
   I have upload the screenshot for you.

Comment 13

[shawn ku [:sku]]

Hi Lecky:
 I re-cehck the log you provided.

The "Generic failure" was due to "10-18 15:58:12.703: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendMessage to content process: RIL:SendMMI:Return:OK{requestId : 'id{fe3ffd12-97a5-4d68-85fc-26abd50caf04}', errorMsg : null}"

However, there is no mmi request between 10-18 15:55:06.913 and 10-18 15:58:12.703.
It was suspected as an unsolicited event.


Please enable RIL log to get necessary information. We need it to check what modem report to gecko.

Note: Please make sure RILD log is enabled too. It will do great help on checking the message between RILD and Gecko.

Thanks!!
sku




// Code [e-mail]
  // We always expect an MMIResult object even for USSD requests.
  if (!mmiResult) {             
    message = {                                                              
      type: 'mmi-error',                                                     
      error: this._('GenericFailure')                                        
    };
  ...
  }


// Log
10-18 15:55:06.913: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: receiveMessage: 'RIL:SendMMI' arrived from content process
10-18 15:55:06.913: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: saveRequestTarget: RIL:SendMMI
10-18 15:55:06.913: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: SendMMI dialstring: *100#
10-18 15:55:06.913: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: _parseMMI dialstring: *100#
10-18 15:55:06.913: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: SendMMI poundString:*100# action:* serviceCode:100 sia:undefined sib:undefined sic:undefined pwd:undefined dialingNumber:
...
10-18 15:58:12.703: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendMessage to content process: RIL:SendMMI:Return:OK{requestId : 'id{fe3ffd12-97a5-4d68-85fc-26abd50caf04}', errorMsg : null}
10-18 15:58:12.703: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendRequestResults: RIL:SendMMI:Return:OK

Comment 14

[lecky]

Hi,
  the log is all info that i can catch from the logcat. please tell me the log from which  module you want to check. So i can insert code to catch the log.

Comment 15

[shawn ku [:sku]]

Please make sure you do *not* use USER build, that will cause not RILD log.

Besides, please make sure you enable ril gecko log by following below steps.


1.1 adb pull /system/b2g/defaults/pref/user.js /tmp
1.2 Modify the value of ril.debugging.enabled to true.
      pref("ril.debugging.enabled", true);
1.3 adb remount
1.3 adb push /tmp/user.js /system/b2g/defaults/pref/
1.4 adb reboot

Comment 16

[lecky]

Attachment: 928208log.txt

Comment 17

[shawn ku [:sku]]

Hi Michael:
 Could you please have your team to check this issue?

there is no sending/cancel MMI around 10-22 10:57:16. however, we saw RIL:SendMMI:Return:OK from QCContentHelper_QC_B2G.
Need commercial RIL to check why trigger "RIL:SendMMI:Return:OK" at 10-22 10:57:16.399.



10-22 10:54:10.739: INFO/Gecko(1342): -*- RILContentHelper: Sending MMI *100#
10-22 10:54:10.769: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: receiveMessage: 'RIL:CancelMMI' arrived from content process
10-22 10:54:10.769: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: saveRequestTarget: RIL:CancelMMI
10-22 10:54:10.769: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: receiveMessage: 'RIL:SendMMI' arrived from content process
10-22 10:54:10.779: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: saveRequestTarget: RIL:SendMMI
10-22 10:54:10.779: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: SendMMI dialstring: *100#
10-22 10:54:10.779: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: _parseMMI dialstring: *100#
10-22 10:54:10.779: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: SendMMI poundString:*100# action:* serviceCode:100 sia:undefined sib:undefined sic:undefined pwd:undefined dialingNumber:
10-22 10:54:10.799: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendMessage to content process: RIL:CancelMMI:Return:OK{ requestId : 'id{5bd15ba5-1e53-47bd-ae28-db969594591e}', errorMsg : null,  }
10-22 10:54:10.799: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendRequestResults: RIL:CancelMMI:Return:OK
10-22 10:54:10.899: INFO/Gecko(1342): -*- RILContentHelper: Received message 'RIL:CancelMMI:Return:OK': {"requestId":"id{5bd15ba5-1e53-47bd-ae28-db969594591e}","errorMsg":null}
10-22 10:54:10.899: INFO/Gecko(1342): -*- RILContentHelper: handleSendCancelMMI {"requestId":"id{5bd15ba5-1e53-47bd-ae28-db969594591e}","errorMsg":null}
...
10-22 10:57:16.399: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendMessage to content process: RIL:SendMMI:Return:OK{requestId : 'id{438fffb6-349d-4aa5-a44c-8103250978ca}', errorMsg : null}
10-22 10:57:16.399: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendRequestResults: RIL:SendMMI:Return:OK
10-22 10:57:16.419: INFO/Gecko(1342): -*- RILContentHelper: Received message 'RIL:SendMMI:Return:OK': {"requestId":"id{438fffb6-349d-4aa5-a44c-8103250978ca}","errorMsg":null}
10-22 10:57:16.419: INFO/Gecko(1342): -*- RILContentHelper: handleSendCancelMMI {"requestId":"id{438fffb6-349d-4aa5-a44c-8103250978ca}","errorMsg":null}

Comment 18

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

Please use the SR system for commercial RIL support, thanks!

Comment 19

[lecky]

hi,
  Do you have any idea about this?

Comment 20

[shawn ku [:sku]]

Hi Lecky:
 the problem is below message. and it comes from commercial RIL.


10-22 10:57:16.399: INFO/Gecko(160): -*- QCContentHelper_QC_B2G: sendMessage to content process: RIL:SendMMI:Return:OK{requestId : 'id{438fffb6-349d-4aa5-a44c-8103250978ca}', errorMsg : null}

Besides,
I do not see any sendMMI/cancelMMI from gaia.
Therefore, we migth need SR to tracking this case.

Thanks!!
sku