Closed Bug 981529 Opened 11 years ago Closed 11 years ago

[Tarako][Dialer]After dialing, phone will keep vibrating until call out number is connected

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3T+)

RESOLVED WORKSFORME
blocking-b2g 1.3T+

People

(Reporter: mlien, Assigned: kk1fff)

Details

(Keywords: smoketest)

[Device] Tarako --------------------------------------------- [Reproduction build] - Mozilla Central - V1.4 Gaia 7f434a8799b8c7b2b419ea118b2de7c2682c170d Gecko 8da7b6293d63b140932893fed6a45f91bfa93631 BuildID 20140310075556 Version 28.0 --------------------------------------------- [Reproduce Steps] 1. Launch Dialer app 2. Make a phone call to any number 3. Verify dialing status --------------------------------------------- [Expected Result] Dialing should be normally --------------------------------------------- [Actual Result] After dialing, phone will keep vibrating until call out number is connected
version: V1.3T
What I saw on tarako v1.3 build 20140310152650: After dialing, phone will keep vibrating forever even when MT device answered/end the call.
This looks a lot like the symptoms of the (feedback-) gaia patch on bug 973596. Patrick, do you know if it landed on a tarako branch?
Flags: needinfo?(pwang)
No, I don't think it goes into our code base. Actually, I don't see the version number on comment 0 (7f434a8799b8c7b2b419ea118b2de7c2682c170d) in Gaia code. Mike, is this a daily build? If yes, could you check if patch on bug 973596 in this build?
Flags: needinfo?(pwang) → needinfo?(mlien)
blocking-b2g: --- → 1.3T?
Patrick passing this onto you to not have any unassigned bugs and this seems related to 973596, feel free to reassign if needed or resolve works for me depending on the investigation.
Assignee: nobody → pwang
blocking-b2g: 1.3T? → 1.3T+
(In reply to Patrick Wang (Chih-Kai Wang) (:kk1fff) from comment #4) > No, I don't think it goes into our code base. Actually, I don't see the > version number on comment 0 (7f434a8799b8c7b2b419ea118b2de7c2682c170d) in > Gaia code. > > Mike, is this a daily build? If yes, could you check if patch on bug 973596 > in this build? the Gaia number must be 4179695b
Flags: needinfo?(mlien)
(In reply to Mike Lien[:mlien] from comment #6) > (In reply to Patrick Wang (Chih-Kai Wang) (:kk1fff) from comment #4) > > No, I don't think it goes into our code base. Actually, I don't see the > > version number on comment 0 (7f434a8799b8c7b2b419ea118b2de7c2682c170d) in > > Gaia code. > > > > Mike, is this a daily build? If yes, could you check if patch on bug 973596 > > in this build? > > the Gaia number must be 4179695b above gaia version number is incomplete, below might be the correct one Gaia version number: 4179695bac2cbc7b39062de9b80f658f77738fd6
FYI I can't reproduce this issue on the current v1.3t branch.
I cannot reproduce on the latest version either : Gaia 7329446974f0ea3b14d61bd38f205eb17a5ce62d caution: filename not matched: chrome/toolkit/content/global/buildconfig.html BuildID 20140313135844 Version 28.0 ro.build.version.incremental=104 ro.build.date=Thu Mar 13 14:02:18 CST 2014 Tarako Mike, can you try again please with the latest version?
Flags: needinfo?(mlien)
I also cannot reproduce on the latest version: Gaia 34f7557cca7ab240cbb093e554bf8528b3fcc1af caution: filename not matched: chrome/toolkit/content/global/buildconfig.html ##### Unzip deoptimized omni.ja error. BuildID 20140313135707 Version 28.0 ro.build.version.incremental=74 ro.build.date=Thu Mar 13 13:58:11 CST 2014 Tarako
Flags: needinfo?(mlien)
I cannot reproduce this either. The call seems to be able to establish in this bug. But what I saw is different. I have filed Bug 983517.
Not able to reproduce this with Gaia 4179695bac2cbc7b39062de9b80f658f77738fd6 (comment 7) + Gecko 8da7b6293d63b140932893fed6a45f91bfa93631 (comment 0). Closing WFM for now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.