1030980 - [B2G][Dialer] The user is unable to pull down the utility tray while in a call

Status: RESOLVED DUPLICATE of bug 1021857

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

Description

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

Attachment: logcat_20140626_Utility Tray.txt

Description:
The user is unable to display the notification page while in a call

Repro Steps:
1) Update a Flame to BuildID: 20140610000223
2) Receive or make a call on the DUT
3) Answer the call
4) Try to pull down the utility tray

Actual:
The utility tray will be completely unresponsive

Expected:
The utility tray comes down smoothly 

Flame 2.0

2.0 Environmental Variables:
Device: Flame 2.0
Build ID: 20140625000201
Gaia: de77f794db22a45f9d575de2c6e266a30a50de3b
Gecko: 79712bd7b60d
Version: 32.0a2 (2.0)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Keywords: notification bar, utility tray, status bar, dialer, call, phone, incoming

Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/13203/
See attached: Logcat, Video - http://youtu.be/wAKu8iipzPU

Comment 1

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

This issue DOES reproduce on Flame 2.1, Buri 2.1, Open C 2.1, Buri 2.0, and Open C 2.0

While the user is in a phone call, they are not able to pull down the utility tray to view notifications

Flame 2.1

2.1 Environmental Variables:
Device: Flame Master
Build ID: 20140625040202
Gaia: 57da30f405ba37a5d4844f32bb292271b81faee2
Gecko: a19e0434ea52
Version: 33.0a1 (Master)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Buri 2.1

2.1 Environmental Variables:
Device: Buri Master
Build ID: 20140625040202
Gaia: 57da30f405ba37a5d4844f32bb292271b81faee2
Gecko: a19e0434ea52
Version: 33.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Open_C 2.1

2.1 Environmental Variables:
Device: Open_C Master
Build ID: 20140625040202
Gaia: 57da30f405ba37a5d4844f32bb292271b81faee2
Gecko: a19e0434ea52
Version: 33.0a1 (Master)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Open_C 2.0

2.0 Environmental Variables:
Device: Open_C 2.0
Build ID: 20140625000201
Gaia: de77f794db22a45f9d575de2c6e266a30a50de3b
Gecko: 79712bd7b60d
Version: 32.0a2 (2.0)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Buri 2.0

2.0 Environmental Variables:
Device: Buri 2.0
Build ID: 20140625000201
Gaia: de77f794db22a45f9d575de2c6e266a30a50de3b
Gecko: 79712bd7b60d
Version: 32.0a2 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


This issue does NOT reproduce on Buri 1.4, Flame 1.4, or Open C 1.4

The utility tray is pulled down while on a phone call as expected

Buri 1.4

1.4 Environmental Variables:
Device: Buri 1.4
Build ID: 20140625000201
Gaia: c9416de14acf9e94ab006619cd2418c768422fcb
Gecko: cddf88f78632
Version: 30.0 (1.4)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0


Flame 1.4

1.4F Environmental Variables:
Device: Flame 1.4
Build ID: 20140625000201
Gaia: c9416de14acf9e94ab006619cd2418c768422fcb
Gecko: cddf88f78632
Version: 30.0 (1.4)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0


Open_C 1.4

1.4 Environmental Variables:
Device: Open_C 1.4
Build ID: 20140625000201
Gaia: c9416de14acf9e94ab006619cd2418c768422fcb
Gecko: cddf88f78632
Version: 30.0 (1.4)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Comment 2

[KTucker [:KTucker][Inactive 3/4/2016]]

Nominating this 2.0? since this a major regression. Users should always be able to pull down the status bar while in a call to see there message notifications etc...

Comment 3

[Doug Sherk (:drs) (inactive)]

The regressing commit is: https://github.com/mozilla-b2g/gaia/commit/f2b7236f28d528cd2a12691fba004e1a2afa929d

Comment 4

[Doug Sherk (:drs) (inactive)]

Alright, I don't think it's best if I try to fix this. The original fix didn't even fix the issue, as I was able to repro the original issue, and it caused this. I'm going to back them out and dupe this to bug 1021857.