1093446 - [FFOS2.0][Woodduck][Protocol-SMS05718&SMS05711]MS can not display the send sms failed.

Status: RESOLVED INVALID

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

Description

[sync-1]

Created an attachment (id=981713)
   
 
 DEFECT DESCRIPTION:
 
 MS can not prompt the infomation of "message send failed" when receive the "CM_Service_Reject" and "CP_ERROR". 
 
  REPRODUCING PROCEDURES:
 run Protocol-SMS05718&SMS05711，see the attachment.
 
  EXPECTED BEHAVIOUR:
 SMS05718：
     First message send failed and prompt failed message.
    Second message can send normally.
 
 SMS05711：
     Message send failed and prompt failed message.
 
 >The same case can run normally on Soul3.5 FF.
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:2611692(61692).

Comment 1

[sync-1]

Attachment: Soul 3.5 FF Logs

Comment 2

[sync-1]

Attachment: Case content

Comment 3

[sync-1]

Attachment: Fire2d3.5 Logs

Comment 4

[Julien Wajsberg [:julienw]]

Can you please share the Reproducing Procedures on the bug? We can't open these files.

Comment 5

[sync-1]

Created an attachment (id=1003262)
 SMS05718

Comment 6

[sync-1]

Created an attachment (id=1003262)
 SMS05718

Comment 7

[sync-1]

Attachment: SMS05718

Created an attachment (id=1003262)
 SMS05718

Comment 8

[sync-1]

Created an attachment (id=1003260)
 SMS05711

Comment 9

[sync-1]

Created an attachment (id=1003260)
 SMS05711

Comment 10

[sync-1]

Attachment: SMS05711

Created an attachment (id=1003260)
 SMS05711

Comment 11

[sync-1]

(In reply to comment #1)
 > Comment from Mozilla:Can you please share the Reproducing Procedures on the
 > bug? We can't open these files.
 
 SMS05711、SMS05718

Comment 12

[Josh Cheng [:josh]]

Hi Reporter,
Can you provide STR? Thanks!

Comment 13

[sync-1]

(In reply to comment #5)
 > Comment from Mozilla:Hi Reporter,
 > Can you provide STR? Thanks!
 
 Sorry. What is STR? Is that means the steps to reproduce?

Comment 14

[Julien Wajsberg [:julienw]]

Yes :)

Please share them in text format here. Thanks!

Comment 15

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

Hi all,

After checking the log, the symptom I saw is that
1. device sent 1 SMS with ERROR_SMS_SEND_FAIL_RETRY from RILD.
2. device retried and got successful response.
3. device send another new SMS with successful response.

The flow looks normal from gecko perspective.
We need modem vendor's help to clarify what happened in the modem side instead.

Comment 16

[sync-1]

Dears，
 此PR复现的具体过程是：
 Case SMS05711：
 手机使用白卡在SAS上跑SMS05711，手机搜网成功后，手机给网络发送一条短信，仪器给手机返回CP_ERROR.
 ->测试机行为：短信正常发送，未收到短信发送失败提示.
 ->期望结果：手机发送短信失败，提示相应的信息发送失败提示.
 
 Case SMS05718：
 手机使用白卡在SAS上跑SMS05718，手机搜网成功后，手机给网络发送两条短信，仪器在手机发送第一条信息后给手机返回CM_Service_Reject，第二条返回正常参数.
 ->测试机行为：两条短信均正常发送，未收到短信发送失败提示.
 ->期望结果：手机发送第一条短信失败，提示相应的信息发送失败提示，发送第二条信息成功.

Comment 17

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

(In reply to sync-1 from comment #16)
> Dears，
>  此PR复现的具体过程是：
>  Case SMS05711：
>  手机使用白卡在SAS上跑SMS05711，手机搜网成功后，手机给网络发送一条短信，仪器给手机返回CP_ERROR.
>  ->测试机行为：短信正常发送，未收到短信发送失败提示.
>  ->期望结果：手机发送短信失败，提示相应的信息发送失败提示.
>  
>  Case SMS05718：
>  手机使用白卡在SAS上跑SMS05718，手机搜网成功后，手机给网络发送两条短信，仪器在手机发送第一条信息后给手机返回CM_Service_Reject
> ，第二条返回正常参数.
>  ->测试机行为：两条短信均正常发送，未收到短信发送失败提示.
>  ->期望结果：手机发送第一条短信失败，提示相应的信息发送失败提示，发送第二条信息成功.

Hi reporter,

After compared with the log analysis in comment 15 and test description in comment 16,
Please have modem vendor's help to clarify instead.

The reasons are 
1. From the log analysis, we were requested to retry the SMS according to the error cause ERROR_SMS_SEND_FAIL_RETRY reported from modem.
2. However, from the test description, it seems that a permanent error cause shall be reported by modem.
   In that case, we'll set this sent SMS as failed and report failure to the application layer.

Comment 18

[sync-1]

Fixed by TCL. 
 By coding to set this.SMS_RETRY_MAX = 0 
 in file gecko/dom/system/gonk/ril_consts.js.
 
 
 Dear SPM, 
 
 The bug has been resolved, you can close it please.
 
 Thanks!

Comment 19

[Julien Wajsberg [:julienw]]

Bevis, what do you think of comment 18?

Comment 20

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

This is vendor-specific fix by their own because the retry scenario was done by modem instead. :)