Closed Bug 840066 Opened 13 years ago Closed 13 years ago

[MMS][User Story] Automatic download retry on failure

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:leo+, firefox21 wontfix, firefox22 wontfix, firefox23 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 wontfix)

RESOLVED FIXED
blocking-b2g leo+
Tracking Status
firefox21 --- wontfix
firefox22 --- wontfix
firefox23 --- fixed
b2g18 --- fixed
b2g18-v1.0.0 --- wontfix
b2g18-v1.0.1 --- wontfix

People

(Reporter: pdol, Assigned: airpingu)

References

Details

(Keywords: feature, Whiteboard: [LOE:M] [fixed-in-birch])

Attachments

(1 file, 1 obsolete file)

UCID: Messages-044 User Story: As a user, I will not have to manually retry downloads if the download of media attached to an MMS message fails. Should a download of media fail the application will automatically retry downloading the content a minimum of four times when the network is active at intervals of 1, 5, 10, and 30 minutes, and an indication that content downloads are in progress will be presented to me. Should the content download fail, the failure should be anounced to me in the form of a message notification in the inbox to simplify the viewing of MMS message status for me.
Depends on: 810097
My suggestion is let user manual download media content. If user download media content fail and then that user go to another area (Roaming), That will be a problem.
Assignee: nobody → boaz
Whiteboard: u=user c=messaging s=v1.1-sprint-3
Within the MMS spec we have a in-app setting "Auto retrieve messages" when toggled On should automatically retry the messages as per the user story. If Auto receive messages is toggled Off, the user will be prompted to manually download message contents each time they receive a MMS message. There is also a "Roaming auto-retrieve" which when toggled On will automatically download message if the user is roaming. This is by default toggled Off and the user will be manually prompted to download message contents. You can see this within the MMS spec on page 15: https://www.dropbox.com/s/zc3hhd1mxi16p4w/MMS.pdf
Assignee: boaz → cassie
Whiteboard: u=user c=messaging s=v1.1-sprint-3 → [LOE:M] u=user c=messaging s=v1.1-sprint-3
Assignee: cassie → waldron.rick
Depends on: 846002
Whiteboard: [LOE:M] u=user c=messaging s=v1.1-sprint-3 → [LOE:M]
Blocks: mms-p1
Per partner and release-driver discussions, marking blocking- until all MMS functionality in bug 849867 is complete, allowing it all to be uplifted at once to avoid SMS bustage.
blocking-b2g: leo+ → -
Flags: in-moztrap?
Can you clarify this flag? "in-moztrap"
leo+ as this is a part of MMS and part of v1.1 to be included in leo+ queries. No_UPLIFT for now before the whole MMS is completed
blocking-b2g: - → leo+
Whiteboard: [LOE:M] → [LOE:M] [NO_UPLIFT]
Depends on: 856085
#6674
Flags: in-moztrap? → in-moztrap+
This part should be solved in the Gecko part. Let me try it.
Assignee: waldron.rick → gene.lian
Attached patch Patch (obsolete) — Splinter Review
Hi Vicamo, this patch is not yet tested but completed. Need your feedback. Thanks!
Attachment #738012 - Flags: feedback?(vyang)
Attachment #738012 - Flags: feedback?(ctai)
Comment on attachment 738012 [details] [diff] [review] Patch Looks good to me.
Attachment #738012 - Flags: feedback?(ctai) → feedback+
Attachment #738012 - Flags: feedback?(vyang) → review?(vyang)
Comment on attachment 738012 [details] [diff] [review] Patch Review of attachment 738012 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/mms/src/ril/MmsService.js @@ +70,5 @@ > + Services.prefs.getCharPref("dom.mms.retrievalRetryIntervals").split(","); > +for (let i = 0; i < intervals.length; ++i) { > + intervals[i] = parseInt(intervals[i], 10); > +} > +const PREF_RETRIEVAL_RETRY_INTERVALS = intervals; const PREF_RETRIEVAL_RETRY_INTERVALS = (function () { // Please also ensure intervals.length equals to PREF_RETRIEVAL_RETRY_COUNT. })(); So that we don't pollute global scope with temporary variables.
Attachment #738012 - Flags: review?(vyang)
Attached patch Patch, V1.1Splinter Review
parseInt() doesn't throw exception when failing to parse. It returns Nan.
Attachment #738012 - Attachment is obsolete: true
Attachment #738530 - Flags: review?(vyang)
Attachment #738530 - Flags: review?(vyang) → review+
Whiteboard: [LOE:M] [NO_UPLIFT] → [LOE:M] [NO_UPLIFT] [fixed-in-birch]
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Already uplifted to b2g18.
Whiteboard: [LOE:M] [NO_UPLIFT] [fixed-in-birch] → [LOE:M] [fixed-in-birch]
Depends on: 901992
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: