993470 - [B2G][Dailer] No notification of incoming call when phone is on silent with vibration off

Status: RESOLVED DUPLICATE of bug 993732

(Core :: DOM: Core & HTML, defect)

Description

[Josh Schmitt [Joshs]]

Description:
When the phone is set to silent and with vibration off there is no notification of an incoming call

Repro Steps:
1) Update a Buri to BuildID: 20140408040204
2) With the test device on the homescreen press the volume key down to silent and no vibration
3) With another device call the test device

Actual:
No notification is present

Expected:
Notification is shown

1.5 Environmental Variables:
Device: Buri 1.5 MOZ
BuildID: 20140408040204
Gaia: 1958454595b1fa0e061f0652ae965629993f5708
Gecko: 8883360b1edb
Version: 31.0a1
Firmware Version: v1.2-device.cfg


Keywords:
Dialer, outbound, inbound, phone call, notification, incoming.

Notes:
Repro frequency: 100%
See attached: Video

Comment 1

[Josh Schmitt [Joshs]]

Attachment: log.txt

I have attached a logcat of the issue.

Comment 2

[Natalya Kot [:nkot]]

The issue does not reproduce on the latest 1.4 build - able to receive incoming call notification when the phone is set to silent and with vibration off

Buri v1.4 (aurora) Mozilla RIL
BuildID: 20140408000202
Gaia: 26983f356ecb1bcf30e862d334b5de790071803e
Gecko: 70b076fc7558
Version: 30.0a2
Firmware Version: v1.2-device.cfg

Comment 3

[J Zimbrick]

Mozilla Inbound Regression Window:

Last Working Environmental Variables: 
Device: Buri
BuildID: 20140407034726
Gaia: f1a98bfaa3ab2480945bd7018831fd56c61cdc24
Gecko: d459cc1b5a94
Version: 31.0a1
Base Image: V1.2-device.cfg

First Broken Environmental Variables:
Device: Buri
BuildID: 20140407040527
Gaia: f1a98bfaa3ab2480945bd7018831fd56c61cdc24
Gecko: f94df8c36ab3
Version: 31.0a1
Base Image: V1.2-device.cfg

The Gaia IDs are the same, so this looks to be a Gecko issue.

Gecko Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=d459cc1b5a94&tochange=f94df8c36ab3

Comment 4

[Jason Smith [:jsmith]]

Looks like bug 993462 & this bug have the same window.

Comment 5

[Jason Smith [:jsmith]]

The two possible bugs here that could have caused this are both DOM-related, so sending this over to the DOM component.

Comment 6

[Jason Smith [:jsmith]]

No-Jun tested a local backout of bug 906164 and was unable to reproduce the bug.

Comment 7

[Jason Smith [:jsmith]]

Resolved as part of bug 993732.