Closed Bug 912510 Opened 6 years ago Closed 6 years ago

[Cost Control] Initial values for Calls and SMSs are not 0 for a little while

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(blocking-b2g:koi+, b2g-v1.2 fixed)

VERIFIED FIXED
1.2 C5(Nov22)
blocking-b2g koi+
Tracking Status
b2g-v1.2 --- fixed

People

(Reporter: isabelrios, Assigned: salva)

References

Details

(Keywords: regression, Whiteboard: burirun3, qaregressexclude, burirun4, burirun1.3-1)

Attachments

(1 file)

Tested on ZTE Ikura/Open with:

build id: 20130823171628
software: OPEN_LATAM_FFOS_V1.1.0B01

PROCEDURE
1. Using a SIM card with ballance account, launch Usage app
2. Check the Telephony screen when it is open

EXPECTED
Values for minutes of calls and SMSs are 0.

ACTUAL
For less than one second it is possible to see 30 and 50 as the initial values for minutes of calls and SMSs. After that, the values are 0 till calls are made or SMSs sent.
https://hg.mozilla.org/mozilla-central/rev/8bceed557a76
Assignee: nobody → liuche
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Hey :Tomcat, what have you done here? I think you got the wrong bug. Could it be?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: liuche → salva
Seen this problem with:
1.2 buri testrun3 build:
Gecko-9150851
Gaia-606517c

The defaults values are 0 for SMS and Calls but after an event, a call made or a SMS sent, it appears 30/50 for a while and then the value
blocking-b2g: --- → koi?
Whiteboard: burirun3
blocking-b2g: koi? → koi+
Whiteboard: burirun3 → burirun3, qaregressexclude
Getting a regression window here is not going to be easy if this is not possible to reproduce globally.
(In reply to Jason Smith [:jsmith] from comment #4)
> Getting a regression window here is not going to be easy if this is not
> possible to reproduce globally.

Globally meaning happening in a SIM independent manner.
Attached file pr13552.html
Attachment #829869 - Flags: review?(francisco.jordano)
Target Milestone: --- → 1.2 C5(Nov22)
Attachment #829869 - Flags: review?(francisco.jordano) → review+
Master: 1b5247170863865327ea31480bec5469a747d435
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
I was not able to uplift this bug to v1.2.  If this bug has dependencies which are not marked in this bug, please comment on this bug.  If this bug depends on patches that aren't approved for v1.2, we need to re-evaluate the approval.  Otherwise, if this is just a merge conflict, you might be able to resolve it with:

  git checkout v1.2
  git cherry-pick -x -m1 1b5247170863865327ea31480bec5469a747d435
  <RESOLVE MERGE CONFLICTS>
  git commit
Flags: needinfo?(salva)
The bug depends on bug 908947

If you don't want those changes in 1.2, I have no problem in preparing a new v1.2-only patch. What do you prefer?
Flags: needinfo?(salva)
Flags: needinfo?(jhford)
Depends on: 908947
v1.2: 17652d483cac2827bae668b5ab87591525a1011a
Flags: needinfo?(jhford)
Whiteboard: burirun3, qaregressexclude → burirun3, qaregressexclude, burirun4
Status: RESOLVED → VERIFIED
Whiteboard: burirun3, qaregressexclude, burirun4 → burirun3, qaregressexclude, burirun4, burirun1.3-1
You need to log in before you can comment on or make changes to this bug.