Closed
Bug 1038691
Opened 11 years ago
Closed 7 years ago
When the clock alarm goes off while the user is in a call while the device is close to your ears, no alarm window shows
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)
RESOLVED
WONTFIX
People
(Reporter: jsmith, Unassigned)
References
Details
Breakout of [A] in https://bugzilla.mozilla.org/show_bug.cgi?id=1026167#c73.
STR
1. Set an alarm to go off soon
2. Get onto a phone call with the phone close to your ears
3. Wait for the alarm to go off
4. Check the phone
Expected
An alarm window should be shown in the foreground.
Actual
The dialer window remains in the foreground.
Reporter | ||
Comment 1•11 years ago
|
||
I'm qawanted to see what steps the user needs to do in this situation to shutoff the alarm if the alarm window does not show up in the foreground.
Keywords: qawanted
Comment 2•11 years ago
|
||
This bug repro's on: Flame 2.1 Master, Flame 2.0, Flame 1.4
**NOTE** For 2.1 builds, I had to use July 7th builds because Alarms don't trigger in more current builds. Blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=1037079
Actual Results: With an alarm set to go off when on a call, if the phone is close to your ear, no alarm window appears in the foreground. The call must be ended before the alarm window appears.
Environmental Variables:
Device: Flame Master
Build ID: 20140707224330
Gaia: 1dc9e53393ae4680a174dffa44a958ec564ebbe8
Gecko: c45f6e6d6005
Version: 33.0a1 (Master)
Firmware Version: v122
-----------------------------------------------
Environmental Variables:
Device: Flame 2.0
Build ID: 20140716084350
Gaia: 5fa5611fc747d397dbaa2c5ccdc776f1dfd2b6e8
Gecko: 3045ff641a0b
Version: 32.0a2 (2.0)
Firmware Version: v122
-----------------------------------------------
Environmental Variables:
Device: Flame 1.4
Build ID: 20140716073943
Gaia: edec55eb65b4b8be3e44bedab2949f295784dff1
Gecko: 90162ab32776
Version: 30.0 (1.4)
Firmware Version: v122
-----------------------------------------------
-----------------------------------------------
This bug does NOT repro on: Buri 2.1
Actual Result: The alarm window appeared in the foreground over the dialer on alarm trigger.
Environmental Variables:
Device: Buri Master
Build ID: 20140707224330
Gaia: 1dc9e53393ae4680a174dffa44a958ec564ebbe8
Gecko: c45f6e6d6005
Version: 33.0a1 (Master)
Firmware Version: v1.2device.cfg
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: croesch
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Reporter | ||
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 3•10 years ago
|
||
Hi, alive
I wanna test bug 1038691, but it depends on this bug. Could you provide any information about this bug?
Flags: needinfo?(alive)
Comment 4•10 years ago
|
||
(In reply to Star Cheng [:scheng] from comment #3)
> Hi, alive
>
>
> I wanna test bug 1038691, but it depends on this bug. Could you provide any
> information about this bug?
It's typo. It should be bug 1038693 instead of bug 1038691.
Comment 5•10 years ago
|
||
It seems this bug is not a regression and the result is expected.
Now when we are on a call, we will turn on proximity sensor.
It means if the phone is nearby your face it will automatically turn off screen.
In this case turn on the screen when alarm is on seems strange.
I don't know what we should do in this case, maybe UX could answer what we want here.
Flags: needinfo?(alive)
Comment 6•10 years ago
|
||
Is this another dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=1026167 ?
Comment 7•10 years ago
|
||
After checking master, I believe this issue is fixed, please check it again.
Flags: needinfo?(scheng)
Comment 8•10 years ago
|
||
Cool, it is fixed on master branch. I have flashed latest SW on flame device. The behavior fits the comment 0 of this bug. Could you provide the bug number and set this bug as duplicate?
Thanks
Flags: needinfo?(scheng) → needinfo?(alive)
Comment 9•10 years ago
|
||
(In reply to Star Cheng [:scheng] from comment #8)
> Cool, it is fixed on master branch. I have flashed latest SW on flame
> device. The behavior fits the comment 0 of this bug. Could you provide the
> bug number and set this bug as duplicate?
>
> Thanks
I am not sure but I "guess" it's bug 927862.
Flags: needinfo?(alive)
Comment 11•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•