941363 - [B2G][SMS] Delivery Report does not give an indication that a message is sent correctly even if it is set to ON.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[Harvey]

Description:
When the user sets Delivery Report to ON and sends a text message, no tick icon notification will appear to tell the user that the text message was sent correctly.

Repro Steps:
1) Updated Buri to BuildID: 20131120004000
2) Select Settings.
3) Select Cellular & Data.
4) Select Message Settings.
5) Open the messaging app. 
6) Send a message to another device.
7) Observe that the message was successfully sent to the second device.
8) Observe the DUT.

Actual:
There is no indication that the message was sent correctly when Delivery Report is turned on.

Expected:
There is an indication that the message was sent correctly when Delivery Report is turned on.

Environmental Variables:
Device: Buri v1.2 COM RIL
BuildID: 20131120004000
Gaia: 5ec2963fff60492c840707df8d8090f9908a5251
Gecko: 2d454e0de2ed
Version: 26.0
Firmware Version: v1.2_20131115

Notes:

Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/9015/

Comment 1

[Harvey]

This issue reproduces on Leo v1.1, when the user sets Delivery Report to ON and sends a text message, no tick icon notification will appear to tell the user that the text message was sent correctly.

Environmental Variables:
Device: Leo v1.1 MOZRIL
BuildID: 20131030041204
Gaia: 39b0203fa9809052c8c4d4332fef03bbaf0426fc
Gecko: 41c15ddb7216
Version: 18.0

Comment 2

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

Steve, could you have a look here? Seems to be your field ;)

Comment 3

[Steve Chung [:steveck]]

(In reply to jharvey from comment #1)
> This issue reproduces on Leo v1.1, when the user sets Delivery Report to ON
> and sends a text message, no tick icon notification will appear to tell the
> user that the text message was sent correctly.
> 
> Environmental Variables:
> Device: Leo v1.1 MOZRIL
> BuildID: 20131030041204
> Gaia: 39b0203fa9809052c8c4d4332fef03bbaf0426fc
> Gecko: 41c15ddb7216
> Version: 18.0

I haven't tested it on v1.1, but it works on master(at least on my device). Need qa support for other version since you also tag regression for others(I'll also test it by myself).

Comment 4

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

Steve, the report was done on 1.2 initially.

Comment 5

[sarsenyev]

As per comment 0 and 1, the issue does reproduce on 1.1 and 1.3, also I see the same issue on 1.3 master build. No any notification of delivery appears for each sent message, even when the "Delivery Reports" option is on

Device: Buri 1.3 Central
BuildID: 20131121040202
Gaia: 71063dd91bc8cbb15ba335236ed67a1c5058bd58
Gecko: cf378dddfac8
Version: 28.0a1

Comment 6

[Steve Chung [:steveck]]

(In reply to Julien Wajsberg [:julienw] from comment #4)
> Steve, the report was done on 1.2 initially.

Not exactly. We have delivery report for text message in v1.1 and mms in v1.2. Since the bug only metioned the text message, it should be testable from v1.1.

I still can't reproduce in v1.1, but the device I tested was unagi:
Device: unagi
BuildID: 20131121041214
Gaia: b7610870ec71495685557744bfbcbce357032251
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/a9fa9a04390d
platform version: 18.1

Master is also unreproducible:
Device: unagi
BuildID: 20131121041214
Gaia: ba955cd6b21da71086c6311f64b4e5de10bec9bb
Gecko: http://hg.mozilla.org/mozilla-central/rev/597287004ff5
platform version: 28.0a1

Comment 7

[Paul Yang [:pyang] (away)]

Hi reporter,
Can you please reproduce the bug and give a snapshot of actual result?  thanks.

Comment 8

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

(In reply to Steve Chung [:steveck] from comment #6)
> (In reply to Julien Wajsberg [:julienw] from comment #4)
> > Steve, the report was done on 1.2 initially.
> 
> Not exactly. We have delivery report for text message in v1.1 and mms in
> v1.2. Since the bug only metioned the text message, it should be testable
> from v1.1.
> 

Was not clear because of the word "report" ;) What I meant, is that comment 0 was for v1.2 :)

Comment 9

[Harvey]

Attachment: screenshot.png

No tick mark is seen even when Delivery report is ON.

Comment 10

[Paul Yang [:pyang] (away)]

Thanks reporter,
Just tried the same build on buri, still not reproducible.
Gene, can your provide some way to collect debug info?

Comment 11

[Gene Lian (I already quit Mozilla)]

(In reply to jharvey from comment #0)
> Repro Steps:
> 1) Updated Buri to BuildID: 20131120004000
> 2) Select Settings.
> 3) Select Cellular & Data.
> 4) Select Message Settings.
> 5) Open the messaging app. 
> 6) Send a message to another device.
> 7) Observe that the message was successfully sent to the second device.

Note that the second device which receives the SMS should have the ability of sending the delivery report back. For most of the Android phones, you need to turn it on in the settings.

Did you try to send an SMS from self to self (FFOS)?

> 8) Observe the DUT.

Comment 12

[Angela Hubenya]

Attachment: receiving/sending logcats

I just checked this issue using AT&T SIM's and I was able to reproduce this issue. Both devices were Buri's, and I tested both 1.2 and 1.3 (separately). There was no tick mark indicating message has been sent, and the receiving device did not receive the option to send a delivery report back. "Delivery reports" was enabled during all tests. I have attached logcats when sending sms, as well as receiving sms. 

I tested on the following environments:
Device: Buri v 1.2 COM RIL
Build ID: 20131125004001
Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/368ea26d2136
Gaia: c2dea53b36bb9d4331a94976344515f60dc5a3d4
Platform Version: 26.0
RIL Version: 01.02.00.019.102 
Firmware Version: v1.2_20131115 


Device: Buri v 1.3 Moz RIL
Build ID: 20131120040202
Gecko: http://hg.mozilla.org/mozilla-central/rev/4f993fa378eb
Gaia: c26480b22ce28c812c347290dd4bad090d83db6f
Platform Version: 28.0a1
Firmware Version: v1.2_20131115

Comment 13

[Angela Hubenya]

I just checked this issue using a T-mobile SIM, as well as the roaming SIM from Taiwan. I am actually seeing the green tick mark on the sending devices indicating my messages has been sent from both carriers. There was still no option to send a delivery report back on the receiving device tho. 

Device: Buri v 1.2 COM RIL
Build ID: 20131125004001
Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/368ea26d2136
Gaia: c2dea53b36bb9d4331a94976344515f60dc5a3d4
Platform Version: 26.0
RIL Version: 01.02.00.019.102 
Firmware Version: v1.2_20131115

Comment 14

[Gene Lian (I already quit Mozilla)]

Hi Bevis, are you interested in this issue? Because you used to handle delivery report and SIM card independent issue, this one might be perfectly suitable for you. ;)

Comment 15

[Paul Yang [:pyang] (away)]

ni? Bevis, please correct if I ping wrong person ;)

Comment 16

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

Hi Angela,

Thanks for your information for clarifying the issue.
1. I've checked the log you provide, I only found that there is a SEND_SMS request out and there is no corresponding SMS_STATUS_REPORT delivery from network.
2. However, because the log information is not sufficient to get the raw data of the sent SMS, I can not tell if the delivery report flag is set when sending to the network.

In addition, from comment#12 and #13 you menioned, it seems that the symptom is only reproducible in AT&T Network.
I am wondering if this is a network-issue during that time-frame instead.
Hence, would you please kindly do me a favor to:
1. Use the MOZ RIL build with the DEBUG_ALL in ril_consts.js set to true to capture the log again.
   - This can help us to check if the delivery request is set in the sending SMS PDU and if the correspinding SMS_STATUS_REPORT is delivered from network after the 2nd device receives the message.
2. Compare the behavior with the same phone numbers in other reference phone to see if the symptom is the same.

Thanks & regards,
Bevis Tseng

Comment 17

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

Hi Harvey,

May I know if the network you tested in also in AT&T?
If NO, would you please kindly do me a favour to:
1. Use the MOZ RIL build with the DEBUG_ALL in ril_consts.js set to true to capture the log again.
   - This can help us to check if the delivery request is set in the sending SMS PDU and if the correspinding SMS_STATUS_REPORT is delivered from network after the 2nd device receives the message.
2. Compare the behavior with the same phone numbers in other reference phone to see if the symptom is the same.

Thanks & regards,
Bevis Tseng

Comment 18

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Created a build for this bug with DEBUG_ALL on in ril_consts.js.
File is found : https://drive.google.com/a/mozilla.com/file/d/0B_0LdM1CVycINjNzcERzWDlhYVU/edit?usp=sharing
1. Download it and unzip and go inside the folder
2. then run: ./fullflash_gecko_ril_gaia.sh 

Symbol files are also in the zip file for dev.

Comment 19

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I removed the last build and placed in a new build as the old build seemed to have some issues with the keyboard.
Not sure why…

https://drive.google.com/a/mozilla.com/file/d/0B_0LdM1CVycINjhHZ1g4cTVyc3c/edit?usp=sharing

Comment 20

[Angela Hubenya]

Attachment: Sending- receiving logcats

(In reply to Bevis Tseng [:bevistseng] ([e-mail]) from comment #16)
> Hi Angela,
> 
> Thanks for your information for clarifying the issue.
> 1. I've checked the log you provide, I only found that there is a SEND_SMS
> request out and there is no corresponding SMS_STATUS_REPORT delivery from
> network.
> 2. However, because the log information is not sufficient to get the raw
> data of the sent SMS, I can not tell if the delivery report flag is set when
> sending to the network.
> 
> In addition, from comment#12 and #13 you menioned, it seems that the symptom
> is only reproducible in AT&T Network.
> I am wondering if this is a network-issue during that time-frame instead.
> Hence, would you please kindly do me a favor to:
> 1. Use the MOZ RIL build with the DEBUG_ALL in ril_consts.js set to true to
> capture the log again.
>    - This can help us to check if the delivery request is set in the sending
> SMS PDU and if the correspinding SMS_STATUS_REPORT is delivered from network
> after the 2nd device receives the message. 
I have attached logcats for when sending and receiving SMS using an AT&T sim card, as well as a T-mobile sim card. 

> 2. Compare the behavior with the same phone numbers in other reference phone
> to see if the symptom is the same.
I have tested this with 3 different Buri's, using the same number. I also tried it with other phone numbers as well, and the results are the same. 
> 
> Thanks & regards,
> Bevis Tseng

Comment 21

[Angela Hubenya]

Harvey is in the same environment as me and he was using the AT&T sim when he logged this issue. Clearing his needinfo flag since his results would be the same as mine.

Comment 22

[Angela Hubenya]

(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #19)
> I removed the last build and placed in a new build as the old build seemed
> to have some issues with the keyboard.
> Not sure why…
> 
> https://drive.google.com/a/mozilla.com/file/d/0B_0LdM1CVycINjhHZ1g4cTVyc3c/
> edit?usp=sharing

Thank you Naoki! :)

Comment 23

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

It's more likely to be a network issue from comment#12, comment#13, and comment#20.

Because the new log in comment#20 was still captured from device with COM RIL,
I'd like to invite QCT contact window for help to double confirm if there is anything wrong from the device's viewpoint.

BTW, because the timestamp of MO/MT device look different, I can not found the corresponding message is received in MT side.

--
Sending:
11-25 13:49:06.919: D/SMS_QC_B2G(136): Single segment message
11-25 13:49:06.919: D/SMS_QC_B2G(136): Sending SMS, Recipient 6502728383, Body 5577jchg
11-25 13:49:06.919: D/SMS_UTIL_QC_B2G(136): Requesting status report
11-25 13:49:09.239: D/SMS_QC_B2G(136): Received success response for RIL_REQUEST_SEND_SMS
--
Receiving
11-25 14:36:20.659: D/SMS_QC_B2G(136): Done notifying DOM of received SMS message: sender [phone], body Hvbjhg

Comment 24

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

Sorry.
Please ignore in log analysis in comment#23. It's the obsolete log on 11-25.

Comment 25

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

Attachment: enable_ril_debug.sh

Hi Angela,

Thanks for your verification. It seems more likely to be an network issue because other reference phone behaves the same.

Unfortunately, I still found that the RIL related logs are not enabled in the latest log you captured.

Hence, I upload a script for you to enable the debug flag of RIL.
You can run the script based on the build that Naoki provided in comment#19.
Then, we can analyze the log again to double confirm if there is anything abnormal in the device side.

To make sure the the RIL related log is captured, you can check if the log tag of "RIL Worker[0]" is available in the log.
For example,
12-05 11:04:16.712 I/Gecko   (  478): RIL Worker[0]: Received signal network info.

Regards,
Bevis

(In reply to Angela Hubenya from comment #20)
> Created attachment 8342758 [details]
> Sending- receiving logcats
> 
> (In reply to Bevis Tseng [:bevistseng] ([e-mail]) from comment #16)
> > Hi Angela,
> > 
> > Thanks for your information for clarifying the issue.
> > 1. I've checked the log you provide, I only found that there is a SEND_SMS
> > request out and there is no corresponding SMS_STATUS_REPORT delivery from
> > network.
> > 2. However, because the log information is not sufficient to get the raw
> > data of the sent SMS, I can not tell if the delivery report flag is set when
> > sending to the network.
> > 
> > In addition, from comment#12 and #13 you menioned, it seems that the symptom
> > is only reproducible in AT&T Network.
> > I am wondering if this is a network-issue during that time-frame instead.
> > Hence, would you please kindly do me a favor to:
> > 1. Use the MOZ RIL build with the DEBUG_ALL in ril_consts.js set to true to
> > capture the log again.
> >    - This can help us to check if the delivery request is set in the sending
> > SMS PDU and if the correspinding SMS_STATUS_REPORT is delivered from network
> > after the 2nd device receives the message. 
> I have attached logcats for when sending and receiving SMS using an AT&T sim
> card, as well as a T-mobile sim card. 
> 
> > 2. Compare the behavior with the same phone numbers in other reference phone
> > to see if the symptom is the same.
> I have tested this with 3 different Buri's, using the same number. I also
> tried it with other phone numbers as well, and the results are the same. 
> > 
> > Thanks & regards,
> > Bevis Tseng

Comment 26

[Angela Hubenya]

Attachment: sms delivery report logcats

Ok I did as you said, and "RIL Worker[0]" is displaying in the logcat. Hopefully I got it this time :)

Comment 27

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

Hi Angela,

Thanks for your update! :)

From the log, our device did set the requestStatusReport to true when sending SMS in both AT&T & T-Mobile network.
[AT&T]
12-05 16:08:27.549: I/Gecko(590): RIL Worker[0]: writeMessage: {"dcs":0,"encodedFullBodyLength":7,"userDataHeaderLength":0,"langIndex":0,"langShiftIndex":0,"segmentMaxSeq":1,"segmentChars":160,"segments":[{"body":"Aaaaaaa","encodedBodyLength":7}],"number":"2067789302","requestStatusReport":true,"rilMessageToken":27,"rilMessageType":"sendSMS","retryCount":0,"segmentSeq":1,"body":"Aaaaaaa","encodedBodyLength":7,"rilRequestType":25,"rilRequestError":null}
[T-Mobile]
12-05 16:21:20.649: I/Gecko(136): RIL Worker[0]: writeMessage: {"dcs":0,"encodedFullBodyLength":6,"userDataHeaderLength":0,"langIndex":0,"langShiftIndex":0,"segmentMaxSeq":1,"segmentChars":160,"segments":[{"body":"Cccccc","encodedBodyLength":6}],"number":"2067789302","requestStatusReport":true,"rilMessageToken":8,"rilMessageType":"sendSMS","retryCount":0,"segmentSeq":1,"body":"Cccccc","encodedBodyLength":6,"rilRequestType":25,"rilRequestError":null}

However, we only received the corresponding SMS_STATUS_REPORT in T-Mobile network.

It's more likely to be a network issue inclusion with comment#12, comment#13, and comment#20 and the log provided in comment#26.

Currently, there is not much we can do from device side.

It is possible to contact AT&T customer service to see if this feature is not available now in their network since even other reference phone is not working as well?

Thanks & regards,
Bevis Tseng

(In reply to Angela Hubenya from comment #26)
> Created attachment 8343888 [details]
> sms delivery report logcats
> 
> Ok I did as you said, and "RIL Worker[0]" is displaying in the logcat.
> Hopefully I got it this time :)

Comment 28

[Angela Hubenya]

I called the AT&T costumer service and did some googling and looks like AT&T does not support SMS Delivery Reports. T-mobile does support it tho. 
I have made a note of this in test case # 9015.

Comment 29

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

Thanks for your feedback, Angela! :)

Set to WONTFIX according to comment#28.