Closed Bug 1246003 Opened 9 years ago Closed 7 years ago

Vibration setting in clock is not retained as off when creating a new alarm

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.5 affected, b2g-master affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.5 --- affected
b2g-master --- affected

People

(Reporter: jthomas, Unassigned)

References

()

Details

(Whiteboard: [2.6-Daily-Testing][Spark])

Attachments

(1 file)

Description: If the user creates an alarm with the vibration setting set as disabled the alarm will still have the vibration enabled when setting another new alarm. Note: This is inconsistent when compared to the System Alarm Volume that is retained each time a new alarm is made. Repro Steps: 1) Update a Aries to 20160204110219 2) Select the Clock app 3) Select New Alarm button 4) Toggle off the Vibrate setting 6) Create a new Alarm Actual: Vibrate remains enabled. Expected: It is expected that the vibrate will be disabled on the next created alarm. Environmental Variables: Device: Aries KK 2.6 BuildID: 20160204110219 Gaia: 4f0e2a1a42a2d049b6fe8f4f095cdcdf0fd5465c Gecko: f53533d9eb771f3251921949ab2c888def70f41f 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 User Impact: The user will have to disable the vibration each time a new alarm is created. Repro frequency: 5/5 See attached: Logcat & Video Video: https://youtu.be/491aUWBRj-k
This issue DOES occur on Flame 2.6 and Flame 2.5 Result: Vibration setting is enabled when a new alarm is created, even if disabled in the previously created alarm. Environmental Variables: Device: Flame KK 2.6 [Full Flash] (512mb) BuildID: 20160204030239 Gaia: 4f0e2a1a42a2d049b6fe8f4f095cdcdf0fd5465c Gecko: 03297f8c28a08d2b39a252c7b368524d9e69da69 Gonk: 8a066f7fa7410e32b58def35f322aa33f03db283 Version: 46.0a1 (2.6) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0 Environmental Variables: Device: Flame KK 2.5 [Full Flash] (512mb) BuildID: 20160122182929 Gaia: 53ba710af4baa6ea89f07f5d4bca36dc05476136 Gecko: a93cb087427579663dc1e72b835a35cbcf9baaba Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a Version: 44.0 (2.5) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: [2.6-Daily-Testing][Spark]
Status: NEW → RESOLVED
Closed: 9 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Resolution: --- → INVALID
Other settings are maintained if changed while creating an alarm so this is inconsistent. Reopening this issue.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Closed: 9 years ago7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: