Closed Bug 826861 Opened 13 years ago Closed 13 years ago

[Cost Control] Data Usage app doesn't track my data usage

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 827198
B2G C4 (2jan on)

People

(Reporter: nkot, Assigned: salva)

References

Details

Attachments

(3 files)

refer to bug #809608 - issue reproduces in buid 1-3 for unagi STR: 1-Pull down notification tray 2-Tap in data usage module 3-Set to alert when 0.1MB used 4-Download any apps (over 0.1MB) 5-Pull down notification tray 6-Tap in data usage module Expected result --> Verify that data used is increased Actual result --> Wifi data used is 0.00 and 3G - 0.00, it doesn´t matter what you do *Settings - Device storage reflects current data usage, used app storage increased from 11.9MB to 14MB
blocking-basecamp: --- → ?
I think in 2012-1-6 build in pvt server works fine now.
Corretion: 2012-12-28 shira gecko build(v1.1) from pvt is fine. It does show correct data usage information 2013-1-6 b2g18 gecko build(v1.0) from pvt is bad. However, 2012-1-6 mozilla central gecko build is bad. It doesn't show correct data usage information
Hardware: x86_64 → ARM
blocking-basecamp: ? → +
Priority: -- → P1
Target Milestone: --- → B2G C4 (2jan on)
Assignee: nobody → salva
Is this bug only about Wifi? If yes I guess it could be a duplicate of bug 827198
Flags: needinfo?(nkot)
in build 1-3 - it was tested with both - WiFi On and 3G only ==> failed to display data usage in both cases No repro in build 1-4 1. set WiFi to On - open email or browser ==> Wifi data usage increases, 3G - shows same numbers 2. set WiFi to Off - open email or browser ==> 3G data usage increases, WiFi - shows same numbers Graph reflects changes as well...
Flags: needinfo?(nkot)
Hi, I rechecked it again. https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi-eng/latest/unagi.zip 07-Jan-2013 08:43 100M 3G data works in cost control calculation now. (It used to not work in some situation or 1/5?1/6? version) Wifi data usage doesn't work as far as I know. (bug 827198)
Resolved WFM per comment #5. For any ongoing wifi issues, use bug 827198.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Reopening this bug Verified on Unagi device Build ID: 20130113070202 v 1.0.0-Prerelease STR: 1. Go to settings and disable wifi and enable cellular and data 2. Go to cost control and on the usage screen "disable wifi" 3. Hit home button 4. Go to a browser app to browser through few pages so that cellular data is used 4. go to cost control app again to see the data usage 5. go to home 6. Pull down the notification tray to see the data usage Expected result: Data usage seen by the user on both on cost control app and notification tray Actual result: Data usage is not seen by the user on seen on notification tray
Status: RESOLVED → REOPENED
blocking-b2g: --- → tef?
Resolution: WORKSFORME → ---
Your screenshots show "Not Available" in the dropdown tray -- not "0.00" as this bug's original comment described. So -- you're seeing something different. Not this bug. Rather than reopening this bug (when it's been WFM for almost a week), please file a new bug on what you're seeing, as we suggested over in bug 809608. (Unless you find an existing bug about the "Not Available" UI.)
Hi, It now shows "not available" in the notification bar for me, too. I believe that's a patch from something to mess this up.
Good to know that it's reproducible. It sounds (IMHO) like an important bug that we may want to block on. So: Could one of you please file a separate bug for it? This bug here had different symptoms, and was resolved WORKSFORME because those symptoms no longer reproduced. The new issue deserves to be tracked independently. [re-resolving WFM -- meant to do that in comment 11]
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → WORKSFORME
Resolution: WORKSFORME → DUPLICATE
blocking-b2g: tef? → ---
blocking-basecamp: + → ---
Unagi device, build ID 20130211070202, Dec 5th Kernel Verified as a duplicate of bug 827198
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: