[B2G][Clock] vibrate and sound from an alarm continue past 10 minutes

NEW
Unassigned

Status

Firefox OS
Gaia::Clock
3 years ago
3 years ago

People

(Reporter: DerekH, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.0 affected, b2g-v2.1 affected)

Details

(Whiteboard: permafail, URL)

Attachments

(1 attachment)

Description:
When the user allows an alarm to go off for longer than 10 minutes, the sound and vibrate alerts will continue to go off past the 10 minute mark

Repro Steps:
1) Update a Flame to BuildID: 20140527040202
2) Open Clock App
3) Set alarm with Vibrate and Sound on> Wait for alarm to go off
3) Allow the alarm to go off for 10 minutes

Actual:
Sound and Vibrate continue past 10 minutes of the alarm going off

Expected:
Both Sound and vibrate turn off after 10 minutes

2.0 Environmental Variables:
Device: Flame 2.0
BuildID: 20140527040202
Gaia: 6a391274cd436f8f0d1fad2db8c6b4805703259c
Gecko: cbe4f69c2e9c
Version: 32.0a1
Firmware Version: v10G-2

Keywords: Silent, Silence, Ring, Audio, Alarm, Music, Vibrate

Notes: The vibrate will stop when the screen is locked, but when the screen is unlocked the vibrate will resume. Related to bug https://bugzilla.mozilla.org/show_bug.cgi?id=898366

Repro frequency: 100%
See attached: Logcat, Video - http://youtu.be/Zy4Kyni8Fzg

It may be a little hard to see in the video but the status bar says 2:07, and the alarm first went off at 1:56. So 11 minutes had passed.

User Agent 2.0 Flame: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
This issue DOES occur on Buri 2.0


2.0 Environmental Variables:
Device: Buri 2.0 MOZ
BuildID: 20140528040205
Gaia: bc6f07c149770c6e6dfbea941ac65138dc364a15
Gecko: e017c15325ae
Version: 32.0a1
Firmware Version: v1.2-device.cfg
This issue DOES occur on Flame base v10G-2

Flame 1.3:
1.3 Environmental Variables:
Device: Flame 1.3
BuildID: 20140505215459
Gaia: ec462dc62979dae593b4ad96ac3851ccbafe1813
Gecko: Unknown
Version: 28.0
Firmware Version: v10G-2
Created attachment 8430337 [details]
Logcat Flame 2.0
Issue does NOT occur on Buri 1.4

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140523000202
Gaia: 16f7ef17feb08562aa6a3cfd6d561b2fcca652c0
Gecko: 9cc96d59cc30
Version: 30.0
Firmware Version: v1.2-device.cfg
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: [2.0-flame-test-run-1] → [2.0-flame-test-run-1], [2.0-flame-test-run-2]
status-b2g-v2.0: --- → affected
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(ktucker)
Whiteboard: [2.0-flame-test-run-1], [2.0-flame-test-run-2] → permafail
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
status-b2g-v2.1: --- → affected
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
You need to log in before you can comment on or make changes to this bug.