Closed Bug 883746 Opened 11 years ago Closed 6 years ago

[MMS] Sending MMS: customization when data off

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WONTFIX
blocking-b2g -

People

(Reporter: noemi, Unassigned)

References

Details

(Keywords: feature, Whiteboard: MMS_TEF, )

Have the chance to customize if MMS will be sent or not when data off:
1.In case yes("sent"=true): MMS will be transparently sent (without user interaction) 
2.In case not("sent"=false): MMS won’t be sent
Nominating to leo? in order to have enough flexibility to adapt to different markets and pricing schemas
blocking-b2g: --- → leo?
Blocks: 883772
Whiteboard: MMS_TEF
Summary: [MMS] MMS customization when data off → [MMS] Sending MMS customization when data off
Summary: [MMS] Sending MMS customization when data off → [MMS] Sending MMS: customization when data off
blocking-b2g: leo? → leo+
Do we need to notify user when MMS won't be sent?
Please give more detailed information about the necessity, radio/legislative regulations of such requirement.  That's not a previously defined behaviour and Gecko is not prepared for this.
blocking-b2g: leo+ → leo?
Vicamo - partner is asking for this to be customizable by OEM within the customization settings. 
So OEM can set for a build to customise behaviours when:

1. if data is off
- 1.a if not roaming
- 1.b if roaming
2. if data is on

Can you estimate the effort here?

adding juren for customization comments
Whiteboard: MMS_TEF → MMS_TEF, TaipeiWW
Keywords: feature
Triage awaiting results from discussion with partners.
(In reply to Wayne Chang [:wchang] from comment #4)

> adding juren for customization comments

See https://bugzilla.mozilla.org/show_bug.cgi?id=862764#c28 please.
Conversations are happening in email about whether or not this will block. Please do not set blocking unless you are on those emails.
I had discussed this customization with Vicamo and Chia-Hung before. We all agree that this
customization should owned by service, but not RIL. That means we should implement this
customization items in MMS service.
Assignee: nobody → ctai
Blocks: 884739
Triage - Leo+ per partner request/discussion
blocking-b2g: leo? → leo+
need testcases for late feature
Flags: in-moztrap?(isabelrios)
Created test case: #8941
Flags: in-moztrap?(isabelrios) → in-moztrap+
I want to create a flag called "bundleSendingMMSWithData". It is operator dependent. So bundleSendingMMSWithData is false for TEF. Can be true for other operator. But what should be the default value?
Flags: in-moztrap+ → in-moztrap?
Removing leo+ on this after further discussions with partner. This (being able to customize) is a desired but not release blocking feature.
blocking-b2g: leo+ → ---
Whiteboard: MMS_TEF, TaipeiWW → MMS_TEF,
Assignee: ctai → nobody
Component: DOM: Device Interfaces → RIL
Product: Core → Firefox OS
I think I mislabel the flag  in-moztrap?. Revert it. Please see comment 11.
Flags: in-moztrap? → in-moztrap+
blocking-b2g: --- → backlog
blocking-b2g: backlog → -
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.