Closed Bug 872868 Opened 13 years ago Closed 13 years ago

[v1.0.1] Cost Control does not report wifi usage

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bsilverberg, Unassigned)

References

Details

(Whiteboard: [fromAutomation])

STR: 1. Enable wifi and connect to a network. 2. Browse to a web site to generate some wifi activity. 3. Go to Usage (Cost Control) app and view wifi usage. Expected results: Wifi usage at step 3 > 0 B. Actual results: Wifi usage at step 3 == 0 B. Tested on an Inari on v1.0.1 with the commercial RIL Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/0b6bcb1f4175 Gaia 9648799c2e45917ff150fa9eef8aeac79a9ac008 BuildID 20130515070203 Version 18.0
Severity: normal → major
This was discussed before. My previous raised bug when making cost control app automation got closed. They told me that this is normal. Wifi for settings looks like disabled, but it is actually enabled in the very beginning:P The truth is that even if you get into Settings app and see wi-fi showing as disabled. Once you entered that section. You will see Wi-Fi is enabled actually. -------------------------------------------------------------------------------- So, the expected result should be: Wi-fi disabled and shown as disabled in Settings app when actual Wi-fi is enabled. :P
Sorry, my fault, I was wrong. I accidentally take actual results as expected result, and expected result as actual result. After that, I came up with a wrong comment/conclusion. Please ignore my comment 1.
Inari from pvt Gaia: 0ddb515f15cbc6b74fc2742b7599d6ae74c6413f Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/d06cfe7d67c2 BuildID 20130515070208 Version 18.0 Unagi v1.0.1 from pvt Gaia: 9648799c2e45917ff150fa9eef8aeac79a9ac008 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/0b6bcb1f4175 BuildID 20130515070203 Version 18.0 WFM.
WFM too. Unagi v1.0.1 from pvt Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/0b6bcb1f4175 Gaia 41eb1834798384a0ba4f64dcb19f987ac6c66d55 BuildID 20130515230203 Version 18.0
Yes, this does appear to be fixed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
QA Contact: atsai
Change solution to WFM because there's nothing to be fixed.
Resolution: FIXED → WORKSFORME
(In reply to Al Tsai [:atsai] from comment #6) > Change solution to WFM because there's nothing to be fixed. Well, it was failing consistently for me on a build, which suggests that there was a bug, which has since been fixed.
You need to log in before you can comment on or make changes to this bug.