Closed Bug 1089976 Opened 10 years ago Closed 7 years ago

[User Story] Disable background data in data savings mode

Categories

(Firefox OS Graveyard :: Gaia::Cost Control, defect)

x86
macOS
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: pdol, Unassigned)

References

Details

(Keywords: feature, Whiteboard: [ucid:SMRTDATA-5-1][NaBfT])

User Story

When I am getting low on data or when I want to conserve my data (in general or when enabling roaming), I don't want apps on my device using my data in the background without me explicitly allowing them to so that I can use data only for what matters most to me. 

Acceptance Criteria:
1. When in Data Savings Mode (with background data disabled), only the app in the foreground is able to use mobile data.
2. When in Data Savings Mode (with background data disabled), apps in the background see themselves as being offline.
3. When an app in the background is consuming mobile data when Data Savings Mode is enabled (with background data disabled), the data transfer for that app should immediately cease.
4. When in Data Savings Mode (with background data disabled), when a foreground app is consuming mobile data is moved to the background, the data transfer for that app should immediately cease.
5. Interaction and visual design matches the UX spec.
No description provided.
Whiteboard: [ucid:SMRTDATA-5-1] → [ucid:SMRTDATA-5-1][NaBfT]
feature-b2g: --- → 2.2?
User Story: (updated)
Summary: [User Story] Disable background data in data savings mode [DRAFT] → [User Story] Disable background data in data savings mode
blocking-b2g: --- → backlog
feature-b2g: 2.2? → 2.2+
QA Contact: jlorenzo
Assignee: nobody → chrislord.net
Status: NEW → ASSIGNED
[Tracking Requested - why for this release]:
feature-b2g: 2.2+ → ---
tracking-b2g: --- → ?
Assignee: chrislord.net → nobody
Status: ASSIGNED → NEW
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.