1190563 - [Dialer] Hanging up on an outgoing call from your device, button does not flash to indicate it was tapped

Status: RESOLVED WONTFIX

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

Description

[Oliver Nelson [:oliverthor]]

Description:
When a user taps the large 'hangup' red button when making an outgoing call, they will observe the button will not flash to give an indication to the user that it has been interacted with. This behavior is inconsistent with many buttons across the device, but immediately comparable to when the user is receiving a incoming call, where answer or denying a call will flash their respective buttons.

Repro Steps:
1) Update a Flame to 20150803030210
2) Open the Dialer app
3) Call another phone number
4) While call is in progress, tap large 'hangup' button to end call

Actual:
Button does not flash when user hangs up

Expected:
Button flashes when user hangs up, indicating to user that it has been interacted with


Environmental Variables:
-----------------------------

Device: Flame 2.5
Build ID: 20150803030210
Gaia: 2ca27bbdd84526c6a3b198d9cf10f2caff1dadde
Gecko: 32712cd01159
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Device: Flame 2.2
BuildID: 20150803032504
Gaia: f8b119ac30e97df991c97682ac4d4f9ca22e1793
Gecko: 429b9d2d4566
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
**********************

Issue DOES NOT REPRODUCE on 2.1 for flame devices
Results: Button flashes when user hangs up, indicating to user that it has been interacted with

Device: Flame 2.1
BuildID: 20150724001207
Gaia: 9dba58d18006e921546cec62c76074ce81e16518
Gecko: 41e10c6740be
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------

Repro frequency: 5/5
See attached: 
video- https://youtu.be/lbVbLzRQezo
logcat

Comment 1

[Oliver Nelson [:oliverthor]]

Attachment: logcat_20150803_1351.txt

Comment 2

[Peter Bylenga [:PBylenga]]

NI on component owner for nomination decision.

Comment 3

[Johan Lorenzo [:jlorenzo]]

The rest of the screen reacts to the user interaction. I would say having the button blinking is better for consistency. Harly, this is a regression, would you block on it, from a UX standpoint?

Comment 4

[Harly Hsu[:harly]]

I didn't have this issue on my Flame (20150805150207), it should have an on press state when user tap on the end call button, if not, then it is definitely a bug. Thanks

Comment 5

[Johan Lorenzo [:jlorenzo]]

I don't repro either on [1]. Do you see it on your side, Oliver?

[1] Build ID               20150805150207
Gaia Revision          581de383687dc441a878d2c91a0167c6ec688fef
Gaia Date              2015-08-05 01:48:40
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/b12a261ee32e
Gecko Version          42.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150805.195702
Firmware Date          Wed Aug  5 19:57:12 EDT 2015
Bootloader             L1TC000118D0

Comment 6

[Oliver Nelson [:oliverthor]]

I am still seeing this issue reproduce. It appears to be an issue regarding state of the device. Uploading another video with actual STR:
* once the Dialer app has turned off it's display (from face proximity during a call), the 'end call' buttons will stop blinking until the app has been closed and restarted.

Repro Steps:
1) Update a Flame to 20150803030210
2) Open the Dialer app
3) Call another phone number
4) While call is in progress, cover receiver to trigger display time off by proximity.
5) Remove obstruction, and tap end call button.

Device: Flame 2.5
BuildID: 20150806030207
Gaia: 4ede0c6bf5fb0c2896d5393032b395999a154619
Gecko: 07befc6f54e7
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Repro: 10/10

Comment 7

[Oliver Nelson [:oliverthor]]

Bug of new STR: https://youtu.be/a1ls0QMnl8w

Comment 8

[Johan Lorenzo [:jlorenzo]]

With the new STR 2.2[1] is affected, but not 2.1[2] (even after 5 repro attempt.)

[1] Build ID               20150810032504
Gaia Revision          102f1299e9eafe3760e1deb44d556b5c4f36b5af
Gaia Date              2015-08-06 20:46:56
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/da29b5af4232
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150810.065425
Firmware Date          Mon Aug 10 06:54:37 EDT 2015
Bootloader             L1TC000118D0

[2] Build ID               20150724001207
Gaia Revision          9dba58d18006e921546cec62c76074ce81e16518
Gaia Date              2015-07-23 12:36:57
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/41e10c6740be
Gecko Version          34.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150724.035246
Firmware Date          Fri Jul 24 03:52:57 EDT 2015
Bootloader             L1TC000118D0

Comment 9

[Johan Lorenzo [:jlorenzo]]

[Blocking Requested - why for this release]: Covering the proximity sensor is a common use case. As Harly mentioned, the pressed state should be present.

Comment 10

[Johan Lorenzo [:jlorenzo]]

Comms triage: We missed it in 2.2. User feedback is important, but not enough to hold the entire relase on it.

Comment 11

[BMO Automation]

Firefox OS is not being worked on