1122325 - [FFOS2.0][Woodduck][GCF][STK]Display text->27.22.4.1.1/2 executed not ok.

Status: RESOLVED DUPLICATE of bug 1117609

(Firefox OS Graveyard :: RIL, defect, P2)

Description

[sync-1]

DEFECT DESCRIPTION:[STK]Display text->27.22.4.1.1/2 executed not ok.
 
  REPRODUCING PROCEDURES:
 1. Load a simcard to the phone which can send"display text";
 2. Execute "DISPLAY TEXT, normal priority, Unpacked 8 bit data for Text String, screen busy->27.22.4.1.1/2";
 3. Terminal response is:81 03 01 21 00 02 02 82 81 83 01 20--ko;
 
  EXPECTED BEHAVIOUR:
 3. Terminal response should be :81 03 01 21 80 82 02 82 81 83 02 20 01.
 
 Reporter's phone number: 0752-2639695
 ps: this issue block GCF.
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Attachment: displaytext-PR903560.rar

Comment 2

[pengfei.huang]

Dear Mozilla,
  When VAL execute case "27.22.4.1.1/2" , "Display Text" command will execute after a while. And when screen is busy such as editing message, the TR of "Display Text" command is not correct exactly.
  
  Spec 31.124:
Expected Sequence 1.2 (DISPLAY TEXT normal priority, Unpacked 8 bit data for Text String, screen busy)
See ETSI TS 102 384 [26] in subclause 27.22.4.1.1.4.2, Expected Sequence 1.2.
  
  Spec 27.22.4.1.1.4.2 Expected Sequence 1.2:
Result
General Result:Terminal currently unable to process command
Additional information: Screen is busy
Coding:
BER-TLV:81 03 01 21 80 82 02 82 81 83 02 20 01.

Comment 3

[Bevis Tseng[:bevis][:btseng](Exited)]

Hi,

From the description in comment 0, it seem that we didn't provide the additional information: Screen is busy (0x01) at the end of the terminal response.

This has been addressed in bug 1117609.
Would you please apply the modification of ril_worker.js in the patch part#1 of bug 1117609 and give it a trial?

If the test case is passed, I'd like suggest to set this as duplicated to bug 1117609 and keep tracking on bug 1117609 instead.

Thanks!

Comment 4

[pengfei.huang]

Hi Bevis Tseng,
  Thanks your advice. I am trying your code and wil feedback in time.

Comment 5

[pengfei.huang]

Dear Bevis Tseng,
  what is the usage of file end by .webild ? I haven't modify related code yet.

Comment 6

[Bevis Tseng[:bevis][:btseng](Exited)]

Hi,

It's the interface definition of DOM APIs to be used by App(Gaia).
The major modification of .webidl is to define a |additionalInformation| attribute in MozStkResponse in MozStkCommandEvent.webidl.

However, the method of |sendStkResponse| in MozIcc.webidl accept response in |any| types.
(The implementation of the structures defined in MozStkCommandEvent.webidl will be done in the future to restrict the data format of the parameter in |sendStkResponse|.)
Hence, the modification of MozStkCommandEvent.webidl is just a reference for gaia to follow.

In addition, gaia has already provided |additionalInformation| in bug 1015833 for |Screen is busy|.

Hence, the modification in ril_worker shall be enough for you to verify this test case.

Comment 7

[pengfei.huang]

Hi,
  Great help, Bevis. VAL test pass.
  Thanks for your help and your information. :)

Comment 8

[Josh Cheng [:josh]]

Thanks Bevis,
Dup this to bug 1117609

Comment 9

[sync-1]

Dear Dengwei,
   we can close this bug. see bug903560.
   Thanks.