Closed Bug 865754 Opened 7 years ago Closed 7 years ago

[Dialer] When a second incoming phone call occurs, do not automatically turn on the screen

Categories

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

All
Gonk (Firefox OS)
defect
Not set

Tracking

(blocking-b2g:leo+, b2g18 fixed)

RESOLVED FIXED
blocking-b2g leo+
Tracking Status
b2g18 --- fixed

People

(Reporter: tchevalier, Assigned: etienne)

References

()

Details

(Whiteboard: u=fx-os-user c=scravag-sprint p=1)

Attachments

(1 file)

Currently, when you receive a second incoming call, even if you keep the phone near your ear, the screen is automatically turned on (and you can't control that), resulting your cheek to accidentally pick up the new call.

IMHO, a little delay using the proximity sensor is better than accidentally picking up a call. I don't know how long this delay could be, but the user can even use the power button to manually turn it on, I guess?
Yep, now that we have the proper tone playing to signal the call waiting I think we should stop turning on the screen automatically.

Ayman, does this have your UX stamp of approval?
Flags: needinfo?(aymanmaat)
(In reply to Etienne Segonzac (:etienne) from comment #1)
> Yep, now that we have the proper tone playing to signal the call waiting I
> think we should stop turning on the screen automatically.
> 
> Ayman, does this have your UX stamp of approval?

yes
Flags: needinfo?(aymanmaat)
blocking-b2g: --- → leo?
Whiteboard: u=fx-os-user c=scravag-sprint-may-20-31 p=1
Whiteboard: u=fx-os-user c=scravag-sprint-may-20-31 p=1 → u=fx-os-user c=scravag-sprint p=1
Attached patch Patch proposalSplinter Review
Assignee: nobody → etienne
Attachment #753346 - Flags: review?(timdream)
Attachment #753346 - Flags: review?(timdream) → review+
blocking-b2g: leo? → leo+
https://github.com/mozilla-b2g/gaia/commit/7c52767685ab0fe73bebc3182ce56827b8a7a573
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Uplifted 7c52767685ab0fe73bebc3182ce56827b8a7a573 to:
v1-train: 544d0f0d864b7076ae18e92a770674271bc27ae8
Flags: in-moztrap?
Flags: in-moztrap? → in-moztrap+
QA Contact: amiller
You need to log in before you can comment on or make changes to this bug.