Closed Bug 871691 Opened 12 years ago Closed 12 years ago

[v1.0.1] Cost Control reset wifi does not work

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

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. 4. Click settings cog to go to settings. 5. Click the "Reset" button. 6. Click the "Yes" button on the Confirmation screen. 7. Click "Done" on the settings screen. 8. View wifi usage. Expected results: Wifi usage at step 8 == 0 B. Actual results: Wifi usage at step 8 is the same as wifi usage at step 3. Tested on an Inari on v1.0.1 with the commercial RIL Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/6e1dbf036d34 Gaia 54dfb62735c81152eef74eb1768e2bf621c0a258 BuildID 20130513070209 Version 18.0
Can reproduce on Unagi v1train, too. Gaia: a503d9a1d0a588f3689243c1ddc0f016ede51b9d Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/50726fbdc25e BuildID 20130513070206 Version 18.0
Can't reproduce in a newer version for me. PVT V1Train Unagi BuildID 20130514070207
Can't reproduce in a newer version again PVT v101 Unagi Gaia: e2187565da22df0c85b2eb501ced4efd342b7bc2 B-D 2013-05-13 18:22:17 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/d40d1831ff41 BuildID 20130514230202 Version 18.0
Unagi v1-train Gaia: f4a59b245ea762eea2e9a30fc136229c0fe6f73f Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/ad04d81b3eeb BuildID 20130514230207 Version 18.0 Unagi v1.0.1 Gaia: e2187565da22df0c85b2eb501ced4efd342b7bc2 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/d40d1831ff41 BuildID 20130514230202 Version 18.0 WFM now.
Blocks: 872868
This is working now :P If you ever see our comments O.o
I tried to verify this, but encountered bug 872868, which prevents me from doing so. Are you folks not seeing that bug?
This is now fixed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.