988026 - [B2G][SMS] Delivery reports are being received even when the target device is turned off

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect)

Description

[demerick]

Attachment: logcat.txt

Description:
If the device under test (DUT) has delivery reports turned on and sends a text to a device that is turned off they will receive the tick icon in the SMS thread indicating delivery.

The tick icon should not appear until the target device is turned on.

Repro Steps:
1) Update a Buri to BuildID: 20140324004001
2) You will need two devices, Device Under Test (DUT) and Target Device
3) DUT: Use any sim/carrier other than AT&T (does not support Delivery reports)
4) Target Device: Power off this device
5) DUT: Navigate to Settings > Messaging Settings > Turn on Delivery Reports
6) DUT: Send a text to the Target Device
7) DUT: Observe the sms message thread

Actual:
A tick/checkmark icon indicating delivery appears next to the latest message

Expected:
A tick icon should not appear until the Target Device is turned on

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140324000202
Gaia: 730670951e40b2317a167fcd07c398bb662d6e87
Gecko: a44f8b39c2c8
Version: 30.0a2
Firmware Version: v1.2-device.cfg

Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/9017/
See attached: logcat
Video URL: https://www.youtube.com/watch?v=6JrPpySqqBE&

Comment 1

[demerick]

This issue also occurs on the Buri v 1.3.0 Mozilla RIL

1.3 Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140324004001
Gaia: f7742fb4929cc57c9f72955ce5cebb8279745ac0
Gecko: e42b778a010f
Version: 28.0
Firmware Version: v1.2-device.cfg

With delivery reports on the device under test will see a tick icon after sending an sms to a device that is already powered off.

Comment 2

[Jason Smith [:jsmith]]

Does this happen on 1.1?

Comment 3

[Steve Chung [:steveck]]

Hi Bevis, we might need your help about any possibility to receive a delivery report when device is off, thanks.

Comment 4

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

Hi,

I suggest to have the following 2 tests to clarify if this is a network problem or the MT device problem which was turned off.

1. Test it again with the same 2 devices under different network.
2. Use another reference phone to send a short message to the same MT device under the same network.

Comment 5

[Julien Wajsberg [:julienw]]

(In reply to Jason Smith [:jsmith] from comment #2)
> Does this happen on 1.1?

AFAIK we don't have delivery reports in 1.1.

Wikipedia [1] says:
The exact meaning of confirmations varies from reaching the network, to being queued for sending, to being sent, to receiving a confirmation of receipt from the target device, and users are often not informed of the specific type of success being reported.

To me, that means that this bug could really be a network issue.

[1] http://en.wikipedia.org/wiki/Short_Message_Service#GSM

Comment 6

[demerick]

(In reply to Bevis Tseng [:bevistseng] ([e-mail]) from comment #4)
> 1. Test it again with the same 2 devices under different network.

Hello,

This issue reproduced using a Buri with a T-Mobile SIM as the device under test and a Buri with an AT&T SIM as the powered off phone. I also tested it using my own personal Sprint phone as the powered off phone. 

This issue did not reproduce using two Buri's with T-Mobile SIMs.

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140326000201
Gaia: 7e705dd4718d528974d99ac31866318d7e201152
Gecko: 4889124accfa
Version: 30.0a2
Firmware Version: v1.2-device.cfg

Comment 7

[Harvey]

This issue does reproduce on 1.1  (DUT: T-mobile to Target: AT&T)

1.1 Environmental Variables:
Device: Buri 1.1 MOZ
BuildID: 20140318041202
Gaia: 44a2ddf63373f8e95c784faf4ed4d60081699c61
Gecko: 2c70ef07c5b3
Version: 18.0
Firmware Version: v1.2-device.cfg

Note: This issue does not reproduce on 1.1 using T-mobile to T-mobile.

Comment 8

[Julien Wajsberg [:julienw]]

I wonder if we get a delivery report when the SMS crosses the AT&T/T-Mobile network boundary.

Comment 9

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

(In reply to demerick from comment #6)
> (In reply to Bevis Tseng [:bevistseng] ([e-mail]) from comment #4)
> > 1. Test it again with the same 2 devices under different network.
> 
> Hello,
> 
> This issue reproduced using a Buri with a T-Mobile SIM as the device under
> test and a Buri with an AT&T SIM as the powered off phone. I also tested it
> using my own personal Sprint phone as the powered off phone. 

Hi,

Can you help to use another reference phone with a T-Mobile SIM as the test device 
and same Buri with AT&T SIM as the powered off phone?
This is the 2nd test I mentioned in comment 4.
With these 2 tests, we can clearly identify if it is a network issue between T-Mobile and AT&T.

Comment 10

[demerick]

(In reply to Bevis Tseng [:bevistseng] ([e-mail]) from comment #9)
> 2. Use another reference phone to send a short message to the same MT device under the same network.

This issue reproduces using another reference phone with a T-Mobile SIM as the DUT and the same Buri with an AT&T SIM as the powered off phone.


1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140326000201
Gaia: 7e705dd4718d528974d99ac31866318d7e201152
Gecko: 4889124accfa
Version: 30.0a2
Firmware Version: v1.2-device.cf

Comment 11

[Julien Wajsberg [:julienw]]

So, can we safely conclude this is a network behavior?

Comment 12

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

According to comment 6 and comment 10, this shall be network issue instead.