963149 - [DSDS][MMS] When data is off for both SIMs card no notification is received about a pending MMS

Status: RESOLVED WORKSFORME

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

Description

[isabelrios]

Build:
29.0a1
20140116105426
b6784673

STR
Disable data for both SIMs card.
Receive an MMS

EXPECTED
A text message is received informing that there is a pending MMS.

ACTUAL
There is not any warning or notification to let user know about a pending MMS.

Comment 1

[Julien Wajsberg [:julienw]]

Isabel, just to be sure: this works as expected in a single sim scenario?

Comment 2

[isabelrios]

Hi Julien,

In a single sim scenario, when data is off, the MMS is received without user interaction. The context is opened transparently to user and closed once the MMS is received.

Dot know if there is an special/specific requirement for DSDS with this regard, ni product, Wilfred to shed some light on this if he knows.
Thanks

Comment 3

[Julien Wajsberg [:julienw]]

Isabel, would be nice to know:

* which SIM you received the MMS on
* whether the MMS was seen in the Messages app, and with which status (eg: downloaded, not-downloaded, pending, etc)?

Thanks !

Comment 4

[isabelrios]

(In reply to Julien Wajsberg [:julienw] from comment #3)
> Isabel, would be nice to know:
> 
> * which SIM you received the MMS on
In case of DSDS both data set to off, it does not matter, I sent the MMS to both SIMs, first, I tried with SIM 1, then with SIM 2. The result was the same, nothing was received.

> * whether the MMS was seen in the Messages app, and with which status (eg:
> downloaded, not-downloaded, pending, etc)?
Nothing was received, there was not a warning, or a message in messaging app.

> Thanks !

Comment 5

[Julien Wajsberg [:julienw]]

Hey Hsin-Yi, 

do you have an idea of what could trigger this bug?

Comment 6

[Hsin-Yi Tsai (she/her) | away [:hsinyi]]

(In reply to Julien Wajsberg [:julienw] from comment #5)
> Hey Hsin-Yi, 
> 
> do you have an idea of what could trigger this bug?

Hi Julien and Isabel,

I don't see a obvious point triggering this bug, and I haven't got a chance to try to reproduce it and get more debug messages.

Isabel, could you please attach a log with RIL and MMS debugging enabled for us? To enable debugger, you could follow https://bugzilla.mozilla.org/show_bug.cgi?id=960537#c27

Thanks!

Comment 7

[isabelrios]

Hi Hsing-Yi,

Thank you, I followed those steps and the script to enable the RIL an MMS logs was successfully executed. The problem is that we are blocked by this bug 965239. Once we are able to send/receive MMSs, will reproduce the bug and attach the log.

Thanks,
Isabel

Comment 8

[isabelrios]

Hi Hsing-Yi,

Attached the log file. Now with the latest build the behaviour is a little bit different.
With Data OFF in both SIMs but SIM 1 selected as default SIM for data:
-MMS received in SIM 1, the MMS is downloaded and the content shown directly
-MMS received in SIM 2, there is an SMS with the option to download the content

We would need feedback to know whether this is the correct behaviour or another one is expected. 
Build tested:
gecko 094ac53
gaia 4a9a286
Version=30.0a1

Comment 9

[isabelrios]

Attachment: Received_MMS.txt

Comment 10

[Julien Wajsberg [:julienw]]

Isabel, I think this is the expected behavior.

Note that we also have bug 965107 when attempting to download the MMS received on SIM2.

Therefore I think we should close this as WORKSFORME, what do you think?

Comment 11

[Hsin-Yi Tsai (she/her) | away [:hsinyi]]

(In reply to Julien Wajsberg [:julienw] from comment #10)
> Isabel, I think this is the expected behavior.
> 
> Note that we also have bug 965107 when attempting to download the MMS
> received on SIM2.
> 
> Therefore I think we should close this as WORKSFORME, what do you think?

Agree with Julien!

Comment 12

[Julien Wajsberg [:julienw]]

Before closing, Isabel, I'd like to be sure it works as expected on 1.3. Can you confirm?

Comment 13

[isabelrios]

Hi Julien,

Yes, currently in master and in 1.3 the behaviour is the same and seems to be the expected one.
So, this bug can be closed as WFM.

The only thing is that there is an US with a different criteria, bug 947176, not expected so far to be implemented, but when it lands, it should be necessary to review the expected behaviour according to the new requirements specified there.

Thanks for your feedback.