Closed
Bug 1076971
Opened 10 years ago
Closed 6 years ago
Proximity sensor to turn off screen causes problems when tasked away from a call
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: epang, Unassigned)
References
Details
(Whiteboard: ux-tracking)
Attachments
(1 file)
9.16 MB,
video/mp4
|
Details |
The Proximity sensor to turn off the screen when a user has their phone to their ear causes problems when the user tasks away from a call and is using their device. For example, the user may need to use the search or the utility tray (to return to the active call). But since their finger goes close to the sensor the screen goes black (see attached video). This feels broken and was really frustrating when I needed to get back to my call. The proximity sensor to turn off the screen should be disabled when the user is not on the call screen. STR 1. Call phone and answer call 2. Press home key, wait for toast to go up 3. Try to pull down utility tray (or place your finger close to the sensor)
Comment 1•10 years ago
|
||
Interestingly I have the reverse problem: when keeping the Flame close to my ear the phone frequently turns on causing me to touch buttons with my cheek without realizing it :-/ Maybe the sensitivity of the sensor is exaggerated or needs a better hysteresis to prevent these kind of annoyances? Can we do anything in Gecko about it?
Updated•10 years ago
|
Whiteboard: , ux-most-wanted-nov2014 → ux-most-wanted-nov2014
Updated•10 years ago
|
Whiteboard: ux-most-wanted-nov2014 → ux-most-wanted-nov2014, 2x-uxnom
Comment 2•9 years ago
|
||
adding qawanted - is this still an issue or can we close? Thanks!
Whiteboard: ux-most-wanted-nov2014, 2x-uxnom → ux-tracking
Comment 3•8 years ago
|
||
I am seeing this issue still occurring on the latest Aries 2.6 and Flame 2.6. Environmental Variables: Device: Aries 2.6 [Full Flash] BuildID: 20160114140113 Gaia: 2d6c11a1e82bd9f9b7491863c8d1ea4a14aea69f Gecko: 27eb5e90eeee2e6a1ffe61c368c294d3de51b797 Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56 Version: 46.0a1 (2.6) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0 Device: FlameKK 2.6 [Full Flash][512mb] BuildID: 20160114030239 Gaia: 2d6c11a1e82bd9f9b7491863c8d1ea4a14aea69f Gecko: 6fa2ab99f52feb1b6ead5581b8f5d398546a55a5 Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a Version: 46.0a1 (2.6) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0
Flags: needinfo?(ktucker)
Comment 4•8 years ago
|
||
This could be fixed by only turning off the screen if the callscreen is not visible, but it would require a fairly ugly hack in the system app to work.
Updated•8 years ago
|
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 5•6 years ago
|
||
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.
Description
•