1167536 - [Clock]After a conversation is ended, the alarm will ring immediately.

Status: RESOLVED WONTFIX

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

Description

[SandKing]

Attachment: Bug log: logcat_1607.txt

[1.Description]:
[Nexus 5][v2.2&v3.0][Flame][v2.2&v3.0][Clock]If we answer an incoming call when an alarm is ringing, this alarm will ring again immediately after the call is ended.
See video:"1607.mp4".
See log:"logcat_1607.txt"
Found time: 16:07

[2.Testing Steps]: 
1. Launch clock and new an alarm.
2. When the alarm is ringing, we receive an incoming call from device B.
3. Answer the call.
4. Device B ends the call.

[3.Expected Result]: 
Step 4
situation 1. The alarm should be snoozed by default(Same with Android)
situation 1. The alarm should be silenced after the conversation is end.(Same with IOS)

[4.Actual Result]: 
4.The alarm will ring again(If user moves the phone from his ear not in time, there is the risk to hurt his ear.).

[5.Reproduction build]: 
Device Flame 2.2(Affected):
Build ID               20150521002508
Gaia Revision          bc42fbc12d622bffd7e8afcb8d56f8a1d9773c60
Gaia Date              2015-05-20 22:32:56
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/6e4eaf59efda
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150521.040918
Firmware Date          Thu May 21 04:09:27 EDT 2015
Bootloader             L1TC000118D0

Device Flame 3.0(Affected):
Build ID               20150521160241
Gaia Revision          1126d8bee559f7cde675df2fcc6c196da9cfeba1
Gaia Date              2015-05-21 21:23:56
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/3e737d30f842
Gecko Version          41.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150521.193021
Firmware Date          Thu May 21 19:30:31 EDT 2015
Bootloader             L1TC000118D0

Device Nexus 5_2.2(Affected):
Build ID               20150521002508
Gaia Revision          bc42fbc12d622bffd7e8afcb8d56f8a1d9773c60
Gaia Date              2015-05-20 22:32:56
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/6e4eaf59efda
Gecko Version          37.0
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150521.040628
Firmware Date          Thu May 21 04:06:43 EDT 2015
Bootloader             HHZ12f

Device Nexus 5_3.0(Affected):
Build ID               20150521160241
Gaia Revision          1126d8bee559f7cde675df2fcc6c196da9cfeba1
Gaia Date              2015-05-21 21:23:56
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/3e737d30f842
Gecko Version          41.0a1
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150521.193039
Firmware Date          Thu May 21 19:30:54 EDT 2015
Bootloader             HHZ12f

[6.Reproduction Frequency]: 
Always Recurrence,5/5

[7.TCID]: 
Free Test

[8. Note]:
User may not move mobile from ear timely in following situations: 
1. During a call, the call will ends automatically if the signal is weak.
 2.Or the call is eneded by the other side. 
So this behaviour is very unfriendly to users.

Comment 1

[SandKing]

Attachment: Bug video: 1607.mp4

Comment 2

[Edward Chen[:edchen]]

This is not a bug, just user experience issue. NI UX team to clarify which situation is good behavior.

Hi Harly, 

Please help to give feedback for this issue.

Comment 3

[Harly Hsu[:harly]]

After checking with UX for clock and sound, it is the expected behaviour that alarm resumes after call is ended according to the document listed in bug 1068219. Also, when the call has ended, alarm will gradually increase the volume to the original volume; therefore, the statement that "If user moves the phone from his ear not in time, there is the risk to hurt his ear" might not be a huge concern. Thanks :)

Comment 4

[BMO Automation]

Firefox OS is not being worked on