Closed Bug 1075604 Opened 5 years ago Closed 5 years ago

[Dialer][Call Log] Calls are not recorded in the Call Log

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(blocking-b2g:-, b2g-v2.1 unaffected, b2g-v2.2 verified)

VERIFIED FIXED
blocking-b2g -
Tracking Status
b2g-v2.1 --- unaffected
b2g-v2.2 --- verified

People

(Reporter: Marty, Unassigned)

Details

(Keywords: regression, smoketest)

Attachments

(1 file)

Attached file logcat-Call_Log.txt
Description:
Calls received, missed, or made by the user are not recorded in the call log.
   
Repro Steps:
1) Update a Flame device to BuildID: 20141001040205
2) Open the Dialer app and make an outbound call.
3) End the call, then open the Call Log
  
Actual:
Calls are not recorded in the Call Log
  
Expected: 
All calls received, missed, or made are recorded in the Call Log
  
Environmental Variables:
Device: Flame 2.2 Master 319MB
BuildID: 20141001040205 (Full Flash)
Gaia: 0e280591881d44b80f456bc27e12d9114c218868
Gecko: 14665b1de5ee
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
  
  
Repro frequency: 7/7
Link to failed test case: https://moztrap.mozilla.org/manage/case/1306/
See attached: screenshot, logcat

--------------------------------

This issue does NOT occur on Flame 2.1
Calls are recorded properly in the Call Log

Environmental Variables:
Device: Flame 2.1 319MB
BuildID: 20141001000202 (Full Flash)
Gaia: 86a3626055ed58b39525424126870dc0a503e79f
Gecko: c20912812877
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Fixed by the backout of bug 1037354.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
[Blocking Requested - why for this release]:
Functional regression of a core feature failing smoketests.

Requesting a window to confirm Comment 1
blocking-b2g: --- → 2.2?
Flags: needinfo?(pbylenga)
QA Whiteboard: [QAnalyst-Triage?]
I'm completely certain that this is fixed now as I knew exactly what caused it and I looked at the Gaia commit used, which was 0e280591881d44b80f456bc27e12d9114c218868. The backout was several commits later. I don't mind if you insist on getting a regression window, but I don't think it's worth the cost.
Sounds good, we have to leave smoketest keyword there as it breaks a build designated for a smoke report.
Keywords: smoketest
QAWanted to verify this is working with latest Master Gaia.
Keywords: qaurgent, qawanted
Verified that this is fixed in the latest master. Used Shallow Flash to test.

Environmental Variables:
Device: Flame Master KK
BuildID: 20141001060621
Gaia: a23d2c490b39c4699c9375e25c4acdf396a2fa85
Gecko: 835ef55e175e
Version: 35.0a1 (Master) 
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
QA Contact: croesch
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Status: RESOLVED → VERIFIED
already fixed.
blocking-b2g: 2.2? → -
Setting status flag to verified given Comment 6
You need to log in before you can comment on or make changes to this bug.