Closed Bug 1183389 Opened 9 years ago Closed 6 years ago

[Call Screen][Emergency Call] Notification banners are not visible when in an emergency call.

Categories

(Firefox OS Graveyard :: Gaia::System::Status bar, Utility tray, Notification, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-, b2g-v2.2 unaffected, b2g-master affected)

RESOLVED WONTFIX
blocking-b2g -
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- affected

People

(Reporter: Marty, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [2.5-Daily-Testing][Spark])

Attachments

(2 files, 1 obsolete file)

Description:
When the user is in an emergency call with an ICE contact, any notifications (screenshot, received sms) will not be displayed at the top of the screen.

Repro Steps:
1) Update a Aries to 20150713103207
2) In the Settings app, enable a lockscreen passcode
3) In the Contacts app, create a contact and set it as an ICE contact.
4) Lock the device
5) At the lockscreen, swipe to the right to bring up the passcode keypad, and select 'Emergency Call'
6) Call the ICE contact using the red option above the dial pad.
7) Receive an sms or take a screenshot on the phone.

Actual:
Notification banners do not appear during an emergency call.

Expected:
Notification banners appear properly during an emergency call.

Environmental Variables:
Device: Aries 2.5
Build ID: 20150713103207
Gaia: a7439b6ca88264734171ff5ea0b6a0b8df3f258e
Gecko: 38d03bf4616e
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Repro frequency: 10/10
See attached: Logcat
This issue DOES occur on Flame 2.5 builds.
Notification banners do not appear during an emergency call.

Environmental Variables:
Device: Flame 2.5
Build ID: 20150713010204
Gaia: e4b63559eba364892867eb381c3002d6518e5d6a
Gecko: eab21ec484bb
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

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

This issue does NOT occur on Flame 2.2 builds.
Notification banners appear properly during an emergency call.

Environmental Variables:
Device: Flame 2.2
Build ID: 20150710002505
Gaia: 84d0c76370dcd3d25813b00de55194730884355b
Gecko: e002005dc994
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
[Blocking Requested - why for this release]:
Functional regression.

Requesting a window.
blocking-b2g: --- → 2.5?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
QA Whiteboard: [QAnalyst-Triage+]
QA Contact: pcheng
b2g-inbound regression window:

Last Working
Device: Flame 2.5
BuildID: 20150520035741
Gaia: d910608af507188e612dc55ee730ef9233c0e777
Gecko: fc1b9ceab6be
Version: 41.0a1 (2.5) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

First Broken
Device: Flame 2.5
BuildID: 20150520064142
Gaia: b830fde437465bc80fe960b1fd8b038d30ddcdc8
Gecko: 1a857bf3997e
Version: 41.0a1 (2.5)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Last Working Gaia & First Broken Gecko - no repro
Gaia: d910608af507188e612dc55ee730ef9233c0e777
Gecko: 1a857bf3997e

Last Working Gecko & First Broken Gaia - repro
Gaia: b830fde437465bc80fe960b1fd8b038d30ddcdc8
Gecko: fc1b9ceab6be

Gaia pushlog:
https://github.com/mozilla-b2g/gaia/compare/d910608af507188e612dc55ee730ef9233c0e777...b830fde437465bc80fe960b1fd8b038d30ddcdc8

Caused by changes made in Bug 1157822.
Blocks: 1157822
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Alberto, can you take a look at this please? This might have been caused by the landing for bug 1157822.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(apastor)
Assignee: nobody → apastor
Flags: needinfo?(apastor)
I'm not sure about this behavior. Can we receive SMS in emergency mode? Are notifications important in this scenario? They won't be accessible when clicking, as the phone is locked. Flagging UX. May be we need somebody that knows the certification process well.

Thanks!
Flags: needinfo?(rmacdonald)
UX ping
Hi Alberto...

I'm not familiar with this feature but Carrie handled it previously. She's no longer with Mozilla but I'm NI'ing Harly to see if he has additional information. Also flagging Wilfred to see if he's familiar with the requirement.

- Rob

(In reply to Alberto Pastor [:albertopq] from comment #5)
> I'm not sure about this behavior. Can we receive SMS in emergency mode? Are
> notifications important in this scenario? They won't be accessible when
> clicking, as the phone is locked. Flagging UX. May be we need somebody that
> knows the certification process well.
Flags: needinfo?(wmathanaraj)
Flags: needinfo?(rmacdonald)
Flags: needinfo?(hhsu)
NI Morpheus to have a look at this.
Flags: needinfo?(hhsu) → needinfo?(mochen)
There are two situations need to be clarified based on the testing for different OS, one is making an emergency call on lockscreen and the other is after unlocking the phone. 

In the first situation, the main purpose is to allow user make emergency call without unlocking the phone. This means user might not be the owner of the phone or the situation is too urgent to waste time on unlocking. So I prefer to show notification banner for telling time since it'll be needed when having an emergency call, but the notification banner won't be able to interact with. You can find the similar UX flow from iOS.

As for the second situation, things are pretty simple. The notification banner will function as usual working flow.
Flags: needinfo?(mochen)
I would like to correct my previous comment. Please ignore last one. Sorry for the bothering.

There are two situations need to be clarified based on the testing for different OS, one is making an emergency call on lockscreen and the other is after unlocking the phone. 

In the first situation, the main purpose is to allow user make emergency call without unlocking the phone. This means user might not be the owner of the phone or the situation is too urgent to waste time on unlocking. So I prefer to show status bar for telling time since it'll be needed when having an emergency call, but the notification banner won't be displayed to prevent any distraction or delay. You can find the similar UX flow from iOS.

As for the second situation, things are pretty simple. The status bar and notification banner will function as usual working flow.
So is the current implementation sufficient or do we have to fix this bug?
Flags: needinfo?(mochen)
Attached image Emergency call.jpg
I would say the current implementation sufficient, but the best situation will be showing status bar but deactivating any notification banner while making emergency calls. Please find the attached mockup as example.
Flags: needinfo?(mochen)
[Triage] Minus it temporarily according to Comment 12
blocking-b2g: 2.5? → -
Comment on attachment 8651719 [details] [review]
[gaia] albertopq:1183389-statusbar-emergency > mozilla-b2g:master

Wrong bug number
Attachment #8651719 - Attachment is obsolete: true
Flags: needinfo?(wmathanaraj)
Unassigned, as I have no time to work on this now
Assignee: apastor → nobody
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: