If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[B2G][Flame][Clock] An alarm triggering while another is being created causes loss of information

NEW
Unassigned

Status

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

People

(Reporter: rpribble, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

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

Details

(Whiteboard: [273MB-Flame-Support], [2.0-exploratory], URL)

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8458364 [details]
Logcat.txt

Description:
If an alarm triggers while the user is creating another alarm in the clock, the user will lose their current progress on the alarm creation and will be returned to the main screen of the clock app. The alarm being created will not have been saved.

Repro Steps:
1) Update a Flame to BuildID: 20140717000201
2) Set an alarm in the Clock app to trigger within the next few minutes
3) Install and launch Cut the Rope from the marketplace
4) Play game until alarm rings

Actual:
The user will lose the information on their current alarm creation.

Expected:
No unintentional loss of information ever occurs.

Environmental Variables:
Device: Flame 2.0 MOZ ril (273MB)
Build ID: 20140717000201
Gaia: aa4f795b81c6147d67c4f06009e166debcf8856e
Gecko: 0ec0b9ac39f0
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozila/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.

Notes:

Repro frequency: 100%
See attached: Video, logcat
(Reporter)

Comment 1

3 years ago
Attaching video (http://youtu.be/PZ0aXKuPozA).

Adding qawanted to check the different branches.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
(Reporter)

Updated

3 years ago
QA Contact: rpribble
(Reporter)

Comment 2

3 years ago
This issue also occurs on the  Flame v2.1 Master (273MB), Buri v2.1 Master, Flame v2.0 MOZ ril (512MB), Buri v2.0 MOZ ril, Flame v1.4 MOZ ril (273MB), and Buri v1.4 MOZ ril.

Environmental Variables:
Device: Flame Master (273MB)
Build ID: 20140718040202
Gaia: Unknown
Gecko: e6e8c93a1b6e
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

v2.1 Environmental Variables:
Device: Buri Master
BuildID: 20140718040202
Gaia:
Gecko: e6e8c93a1b6e
Version: 33.0a1
Firmware Version: v1.2-device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Environmental Variables:
Device: Flame 2.0 MOZ ril (512MB)
Build ID: 20140718000232
Gaia: 34c24749e78496ac1317f4ddb573281c0ef2995e
Gecko: 76309f978531
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Buri 2.0 MOZ ril
Build ID: 20140718000232
Gaia: 34c24749e78496ac1317f4ddb573281c0ef2995e
Gecko: 76309f978531
Version: 32.0a2 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

v1.4 Environmental Variables:
Device: Flame v1.4 MOZ ril (273MB)
BuildID: 20140718000231
Gaia: e0a732cf172d125eadfad59f0faf8f73b62012b8
Gecko: 074223c547af
Version: 30.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

v1.4 Environmental Variables:
Device: Buri v1.4 MOZ ril
BuildID: 20140718000231
Gaia: e0a732cf172d125eadfad59f0faf8f73b62012b8
Gecko: 074223c547af
Version: 30.0
Firmware Version: v1.2-device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

The user will lose the information on their current alarm creation.
Assignee: nfong → nobody
Component: Pre-Installed Apps → Gaia::Clock
Keywords: qawanted
Product: Marketplace → Firefox OS
Summary: [B2G][Flame][Clock] An alarm triggering while another app is in use causes abnormal results → [B2G][Flame][Clock] An alarm triggering while another is being created causes loss of information
Version: Avenir → unspecified
Please attach a clearer video. There is a glare on the screen so it is hard to see what is actually taking place. Also, you state that when an alarm goes off while playing "Cut the rope" but I don't see that in your video.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(rpribble)
(Reporter)

Comment 4

3 years ago
Updating video attachment (http://youtu.be/uek0eU8ZVwI).

Corrected repro steps:
1) Update a Flame to BuildID: 20140717000201
2) Set an alarm in the Clock app to trigger within the next few minutes
3) Create another alarm and begin filling out information fields until the original alarm that was set triggers (do not save it  yet)
4) Observe user is taken back to main page of clock app and the information for the second alarm being set is lost
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(rpribble) → needinfo?(ktucker)
Please update the appropriate tracking flags.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(rpribble)
(Reporter)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
status-b2g-v1.4: --- → affected
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
Flags: needinfo?(rpribble) → needinfo?(ktucker)
(Reporter)

Comment 6

3 years ago
Updating video.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
You need to log in before you can comment on or make changes to this bug.