Closed Bug 947176 Opened 7 years ago Closed 4 years ago

[DSDS][Message] Retrieve MMS from both SIMs

Categories

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

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: wmathanaraj, Unassigned)

References

Details

(Whiteboard: [needs UX], ux-tracking)

Attachments

(1 file)

As a user I want a method to automatically retrieve MMS messages received on any SIM

Acceptance Criteria

AC1: I want the MMS to be retrieved even when recevied via the SIM that does not have data enabled
AC2: I want to be informed before the retrieval is done on the non-default-for-data SIM
AC3: I want an option to disable this feature in settings
Summary: [DSDS] Retrieve MMS from both SIMs → [DSDS][Message] Retrieve MMS from both SIMs
Duplicate of this bug: 938430
Flags: in-moztrap?(pyang)
AC1, AC2 are done, but do we want to change how this behaves? See also my question in bug 947139.

AC3: so, what happens in the Messages app when this is disabled ?

I clearly needs some UX here.

We'll also need separate bugs for the Messages app and the Settings app.
Flags: needinfo?(aymanmaat)
Whiteboard: [needs UX]
oops, i did not upload the latest specs to the bug. attaching now
(In reply to Julien Wajsberg [:julienw] from comment #2)
> AC1, AC2 are done, but do we want to change how this behaves? See also my
> question in bug 947139.
> 
> AC3: so, what happens in the Messages app when this is disabled ?
> 

As far as i am aware AC3 would be the same behaviour as is already designed by Carrie for V1.3. DSDS 1.4 has not changed this. ni? to Carrie to clarify specified behaviour
Flags: needinfo?(aymanmaat) → needinfo?(cawang)
Hi Wilfred,

Has this user story been removed from 1.4 based on the discussion in UX workweek in Paris? I checked the etherpad of the meeting and it's been deleted.
Flags: needinfo?(wmathanaraj)
I think this user story is different from what I've done for 1.3. In 1.3, the user needs to manually agree on switching SIM with a confirm window and switch it back in SIM manager. We need Wilfred to confirm which approach that we are going to adopt in 1.4.
Flags: needinfo?(cawang)
To me, AC2 is exactly this. But I may have understood wrongly.
the feature remains as in v1.3
blocking-b2g: 1.4+ → ---
Flags: needinfo?(wmathanaraj)
Hi guys, do we have a conclusion for this?
Yes Paul, the current behavior is what we'll have in 1.4.
Remove in-moztrap, can be re-flagged if further change is proposed
Flags: in-moztrap?(pyang)
Blocks: 1096862
ux-b2g: --- → 2.2
Whiteboard: [needs UX] → [needs UX], ux-most-wanted-nov2014
Is this still a valid bug?
ux-b2g: 2.2 → ---
Flags: needinfo?(felash)
Whiteboard: [needs UX], ux-most-wanted-nov2014 → [needs UX], ux-tracking
I'm not sure of what was even asked at the start of the bug. I think something around automatic MMS retrieving in DSDS situation, but it's never been clear to me what the changes over the current behavior would be.

I think this should be a question to our UX. Hey Bryant, here is a question for you... Sorry it's not a really easy one, especially that you probably don't know our DSDS behavior yet. Maybe you can ask Steve to give you some quick training on this topic ;)
Flags: needinfo?(felash) → needinfo?(bmao)
ok, I'll check that out and reply to you soon.
Hi Julien,

I've talked with Steve, he say currently we did not have the auto retrieve MMS feature yet, which echo to what I've test on my flame.    

So here are two questions need to be clarify:
1.Does this feature had been done yet? (in higher version?)
2.If not, do we want to build it? In which version?

In UX perspective, I do see value in this feature since auto retrieve MMS help user to skip many daunting steps of data setting in order to get a MMS.

If user disable the feature in settings, we can ask user if they want to download the MMS "in another data rate" or not, then do one time data setting switching in the background (SIM1>SIM2>SIM1), so the user experience should just like they use default SIM to download the MMS.
Flags: needinfo?(bmao)
Hey Bryant,

I'm confused, of course we have the auto retrieve MMS feature... At least if the MMS comes from the configured default SIM ? Or are you talking about the case when we receive a MMS from the not default SIM ?

There are problems with this feature IMO.
1. When we switch the data SIM, all existing connections are closed. This means that if the user is currently navigating the web, the navigation will stop.
2. Retrieving a MMS can take many seconds, or even minutes when the connection is bad. Then should we have a timeout ?
3. Merely registering to the GSM+data network takes many seconds.

For these reasons, I think we can't auto-switch the SIM automatically. Or maybe do it only when the phone is idle, but I don't really know how to know this.

(In reply to Bryant Mao [:bryantmao] from comment #15)

> If user disable the feature in settings, we can ask user if they want to
> download the MMS "in another data rate" or not, then do one time data
> setting switching in the background (SIM1>SIM2>SIM1), so the user experience
> should just like they use default SIM to download the MMS.

I think the current flow is already as convenient. We get a notification, the user can tap it, then we enter the right conversation, then the user can tap the "download" link and accept the SIM switch (for the aforementioned reasons).
Flags: needinfo?(bmao)
(In reply to Julien Wajsberg [:julienw] from comment #16)
> Hey Bryant,
> 
> I'm confused, of course we have the auto retrieve MMS feature... At least if
> the MMS comes from the configured default SIM ? Or are you talking about the
> case when we receive a MMS from the not default SIM ?

When we say auto retrieve MMS, do we mean download the MMS from server to local device?
yes, I am considering the case of receive a MMS from the not default SIM.

> 
> There are problems with this feature IMO.
> 1. When we switch the data SIM, all existing connections are closed. This
> means that if the user is currently navigating the web, the navigation will
> stop.
> 2. Retrieving a MMS can take many seconds, or even minutes when the
> connection is bad. Then should we have a timeout ?

I do think we need a timeout, like 10 mins. After that we can give option for user to download again. (but does download again usually help?)

> 3. Merely registering to the GSM+data network takes many seconds.
> 
> For these reasons, I think we can't auto-switch the SIM automatically. Or
> maybe do it only when the phone is idle, but I don't really know how to know
> this.

Good point! I didn't really though about these issues. We may do it when the screen is locked, but this might confuse user since the download behaviors is inconsistent (the rule is too hidden for them). 

> 
> (In reply to Bryant Mao [:bryantmao] from comment #15)
> 
> > If user disable the feature in settings, we can ask user if they want to
> > download the MMS "in another data rate" or not, then do one time data
> > setting switching in the background (SIM1>SIM2>SIM1), so the user experience
> > should just like they use default SIM to download the MMS.
> 
> I think the current flow is already as convenient. We get a notification,
> the user can tap it, then we enter the right conversation, then the user can
> tap the "download" link and accept the SIM switch (for the aforementioned
> reasons).

Do user need to switch SIM manually in the settings if they want to receive MMS from the not default SIM? Also, when we download the MMS, can we show progress to our user?
Flags: needinfo?(bmao)
(In reply to Bryant Mao [:bryantmao] from comment #17)
> (In reply to Julien Wajsberg [:julienw] from comment #16)
> > Hey Bryant,
> > 
> > I'm confused, of course we have the auto retrieve MMS feature... At least if
> > the MMS comes from the configured default SIM ? Or are you talking about the
> > case when we receive a MMS from the not default SIM ?
> 
> When we say auto retrieve MMS, do we mean download the MMS from server to
> local device?

Yes we do this for the default SIM.

> yes, I am considering the case of receive a MMS from the not default SIM

OK, so we don't have this, for the previously mentioned reasons.


> > 
> > There are problems with this feature IMO.
> > 1. When we switch the data SIM, all existing connections are closed. This
> > means that if the user is currently navigating the web, the navigation will
> > stop.
> > 2. Retrieving a MMS can take many seconds, or even minutes when the
> > connection is bad. Then should we have a timeout ?
> 
> I do think we need a timeout, like 10 mins. After that we can give option
> for user to download again. (but does download again usually help?)

I think we already have a timeout in Gecko... but remember the user can't use the other SIM while the download happens.
That's why we had this design decision (let the user choose when to download + explain him what will happen) in the first place.

> 
> > 3. Merely registering to the GSM+data network takes many seconds.
> > 
> > For these reasons, I think we can't auto-switch the SIM automatically. Or
> > maybe do it only when the phone is idle, but I don't really know how to know
> > this.
> 
> Good point! I didn't really though about these issues. We may do it when the
> screen is locked, but this might confuse user since the download behaviors
> is inconsistent (the rule is too hidden for them). 

Yes.
Note: if we do it when the screen is locked, we should also cancel it as soon as the screen is unlocked, so that the user can recover his default SIM.


> 
> > 
> > (In reply to Bryant Mao [:bryantmao] from comment #15)
> > 
> > > If user disable the feature in settings, we can ask user if they want to
> > > download the MMS "in another data rate" or not, then do one time data
> > > setting switching in the background (SIM1>SIM2>SIM1), so the user experience
> > > should just like they use default SIM to download the MMS.
> > 
> > I think the current flow is already as convenient. We get a notification,
> > the user can tap it, then we enter the right conversation, then the user can
> > tap the "download" link and accept the SIM switch (for the aforementioned
> > reasons).
> 
> Do user need to switch SIM manually in the settings if they want to receive
> MMS from the not default SIM? Also, when we download the MMS, can we show
> progress to our user?

So, when the user taps the "download" button:
1. we display a confirm dialog to warn him about what happens while we switch the SIM.
2. We auto-switch the data SIM.
3. We download the MMS.
4. When the download is over or in error, we auto-switch the data SIM back.

If for some reason the app is killed at step 3, I think the previously non-default SIM is left as the default.

Note the full spec for DSDS is at [1] ("DSDS" directory, page 49 for this functionality).
[1] https://mozilla.app.box.com/13-uxspecs/1/1206603879

So in my opinion we can't really do better than what's already done. Except maybe the auto-retrieve while the screen is locked, but I don't think it's worth the trouble...
Flags: needinfo?(bmao)
Hi Julien, 

I think what you said make sense. So here are two questions left. First, can we estimate the download progress and display to user. Second, if user stuck in step 3, can we auto switch the non-default SIM back to default SIM? (trigger by error code or timeout)
Flags: needinfo?(bmao)
(In reply to Bryant Mao [:bryantmao] from comment #19)
> Hi Julien, 
> 
> I think what you said make sense. So here are two questions left. First, can
> we estimate the download progress and display to user. 

Not really as it depends more on the network condition. However maybe we know the size of the message ? Bevis do we have this information ?

> Second, if user stuck
> in step 3, can we auto switch the non-default SIM back to default SIM?
> (trigger by error code or timeout)

Yes, I wrote it in step 4 :) "on in error" :)
Flags: needinfo?(btseng)
(In reply to Julien Wajsberg [:julienw] (PTO -> 2016) from comment #20)
> Not really as it depends more on the network condition. However maybe we
We are not able to know the progress of the retrieving status. :(
> know the size of the message ? Bevis do we have this information ?
The size of a mms message in octets is represented in the "X-Mms-Message-Size" of a M-Notification.ind PDU.
See "Table 3: Header fields of M-Notification.ind PDU." in [1] for more detail information.
However, this information is not exposed to MmsMessage.webidl.

[1] http://technical.openmobilealliance.org/Technical/release_program/docs/MMS/V1_3-20110913-A/OMA-TS-MMS_ENC-V1_3-20110913-A.pdf
Flags: needinfo?(btseng)
Thx, so this is something we might be able to do if we want to, but needs quite significant engineer time.
Flags: needinfo?(bmao)
(In reply to Julien Wajsberg [:julienw] from comment #22)
> Thx, so this is something we might be able to do if we want to, but needs
> quite significant engineer time.

I am thinking how to keep minimal effort to deal with it. Can we at least show text status like "downloading" in the thread? Will that cost great deal of time?
Flags: needinfo?(bmao)
Mass closing of Gaia::SMS bugs. End of an era :(
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Mass closing of Gaia::SMS bugs. End of an era :(
You need to log in before you can comment on or make changes to this bug.