1000635 - [Sora][STK]Can not execute 'Refresh' command with type=04 normally.

Status: RESOLVED DUPLICATE of bug 999235

(Firefox OS Graveyard :: Gaia::Settings, defect, P1)

Description

[sync-1]

Created an attachment (id=715888)
 soul 3.5 fail adb log
 
 +++ This bug was initially created as a clone of Bug #656564 +++
 Created an attachment (id=715856)
 Miata 3G FF fail adb log
 
 DEFECT DESCRIPTION:
 Can not execute 'Refresh' command with type=04 normally.
 
  REPRODUCING PROCEDURES:
 Precondition:
 MS load simulated SIM card and SATK application which can send "Refresh"
 procative SIM command.
 1.Enter to 'Refresh' Menu,run the test case STM07009->Reset,after execute refresh command.
 2.Repeat step2 again,sometimes will find it won't execute normally,and MS no response->KO.
 
 Note:Bettle lite FF SW186 has the same issue.
 
  EXPECTED BEHAVIOUR:
 It should can execute Refresh command with type=04 normally.
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 3GPP TS 11.14
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 Middle.
 
  REPRODUCING RATE:
 3/5.
 
  For FT PR, Please list reference mobile's behavior:
 ++++++++++ end of initial bug #656564 description ++++++++++

Comment 1

[sync-1]

Attachment: Miata 3G FF fail qxdm log

Comment 2

[sync-1]

Attachment: soul 3.5 fail adb log

Comment 3

[sync-1]

Attachment: soul 3.5 fail qxdm log

Comment 4

[xiaokang.chen]

Attachment: log_0424.txt

Comment 5

[xiaokang.chen]

Dear Fernando,
Please help to check this. Thanks a lot!

Comment 6

[Fernando R. Sela (no CC, needinfo please) [:frsela]]

I think this isn't a Gaia issue since when it fails, no Gaia code received the message it has been dropped before...

First call worked as expected (Gaia sent a good response):



I/Gecko   (  291): -*- [SUB0] QCContentHelper_QC_B2G: sendMessage to content process: icc-stkcommand{ iccId : '89441000000400617452', command : { commandNumber : 1, typeOfCommand : 1, commandQualifier : 4,  } }

I/Gecko   (  291): -*- [SUB0] QCContentHelper_QC_B2G: sendMessage to content process: RIL:StkCommand{ commandNumber : 1, typeOfCommand : 1, commandQualifier : 4,  }

I/Gecko   (  291): -*- QCMessageManager_QC_B2G: Received sendTargetMessage with topic='icc', message='RIL:StkCommand'

I/Gecko   ( 1118): -*- RILContentHelper: Received message 'RIL:StkCommand': {"clientId":0,"data":{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}}

I/GeckoDump(  291): [system] STK Proactive Command:{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}

I/GeckoDump(  291): [system] STK_CMD_REFRESH

I/GeckoDump(  291): STK_CMD_REFRESH --> cmdQualifier:4

I/GeckoDump(  291): [system] sendStkResponse to command: {"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}

I/GeckoDump(  291): [system] sendStkResponse -- # response = {"resultCode":0}

I/GeckoDump(  291): [system] normal sendStkResponse

I/setupmenu--------------------(  291): Icc::SendStkResponse

I/Gecko   (  291): -----------------response.command = 1

I/Gecko   (  291): -*- RILContentHelper: Received message 'RIL:StkCommand': {"clientId":0,"data":{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}}

I/Gecko   (  968): -*- RILContentHelper: Received message 'RIL:StkCommand': {"clientId":0,"data":{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}}

I/Gecko   (  291): -*- QCMessageManager_QC_B2G: receiveMessage: RIL:SendStkResponse arrived from content process




Second call didn't arrive Gaia code so a lower level issue:


I/Gecko   (  985): -*- RILContentHelper: Received message 'RIL:StkCommand': {"clientId":0,"data":{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}}

D/SST_QC_B2G(  291): Received unsolicited response UNSOL_RESPONSE_VOICE_NETWORK_STATE_CHANGED



Third call arrived to Gaia and it was processed again with good results


I/Gecko   (  291): -*- [SUB0] QCContentHelper_QC_B2G: sendMessage to content process: RIL:StkCommand{ commandNumber : 1, typeOfCommand : 1, commandQualifier : 4,  }

I/Gecko   (  291): -*- QCMessageManager_QC_B2G: Received sendTargetMessage with topic='icc', message='RIL:StkCommand'

I/Gecko   ( 1118): -*- RILContentHelper: Received message 'RIL:StkCommand': {"clientId":0,"data":{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}}

I/GeckoDump(  291): [system] STK Proactive Command:{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}

I/GeckoDump(  291): [system] STK_CMD_REFRESH

I/GeckoDump(  291): STK_CMD_REFRESH --> cmdQualifier:4

I/GeckoDump(  291): [system] sendStkResponse to command: {"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}

I/GeckoDump(  291): [system] sendStkResponse -- # response = {"resultCode":0}

I/GeckoDump(  291): [system] normal sendStkResponse

I/setupmenu--------------------(  291): Icc::SendStkResponse

I/Gecko   (  291): -----------------response.command = 1

I/Gecko   (  291): -*- RILContentHelper: Received message 'RIL:StkCommand': {"clientId":0,"data":{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}}

I/Gecko   (  291): -*- QCMessageManager_QC_B2G: receiveMessage: RIL:SendStkResponse arrived from content process

I/Gecko   (  291): -*- QCMessageManager_QC_B2G: Forwarding message to clientId = 0

I/Gecko   (  985): -*- RILContentHelper: Received message 'RIL:StkCommand': {"clientId":0,"data":{"commandNumber":1,"typeOfCommand":1,"commandQualifier":4}}

Comment 7

[Fernando R. Sela (no CC, needinfo please) [:frsela]]

@Yoshi: Per previous comment, We don't recieve some msg. in gaia, can you take a look at gecko level? Thanks

Comment 8

[Yoshi Cheng-Hao Huang [:allstars.chh][:allstarschh][:yoshi]]

Partner's RIL should handle this.

Comment 9

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Anshul -

Could you also help to check this problem from your side?

Thanks

Vance

Comment 10

[Anshul]

Reporter, please don't upload QXDM logs to the bugzilla bug. Please file an SR so we can support you.

Comment 11

[xiaokang.chen]

(In reply to Anshul from comment #10)
> Reporter, please don't upload QXDM logs to the bugzilla bug. Please file an
> SR so we can support you.

Hi Anshul,
Sorry for the mistake.( The log uploaded automatically when I clone a case to Mozilla). I'll take care of it in the future.

Comment 12

[Nivi]

I will take a look and update the thread.

Thanks,
Nivi.

Comment 13

[Nivi]

Hi guys,

This could be related to an issue our internal team is looking at the moment.
I will forward them the QXDM logs and see if they have an analysis on this issue.

I have seen similar issues where a STK command works the first time and the messages don't get propagated the second time.
Will update this thread when we find something.

Thanks,
Nivi.

Comment 14

[xiaokang.chen]

Dear All,
The SR is 01541192.

Comment 15

[Fernando R. Sela (no CC, needinfo please) [:frsela]]

Due to comment #13 "This could be related to an issue our internal team is looking at the moment." we decided to close this bug.

Reopen it if necessary after the analysis.