Closed Bug 1184734 Opened 10 years ago Closed 7 years ago

[Find My Device] Ringtone/notification volume is not returned to previous level after using the ring command.

Categories

(Firefox OS Graveyard :: FindMyDevice, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: Marty, Unassigned)

Details

(Keywords: feature, Whiteboard: [2.5-Daily-Testing][Spark])

Attachments

(1 file)

Attached file fmd-logcat.txt
Description: If the user activates the Ring command on the FMD website, the device will automatically increase the ringtone volume to the maximum level. After the device finishes ringing, the ringtone/notification volume will stay at the maximum level instead of returning to the previous, user-defined level. Repro Steps: 1) Update a Aries to 20150716033647 2) Log into a Firefox Account 3) Enable Find My Device 4) From another computer or device, navigate to find.firefox.com and log into the same Firefox Account 5) From the website, select the Ring command. 6) After 30 seconds, when the ringing ends, check the device ringtone volume. Actual: The ringtone/notification volume is left at the maximum. Expected: The ringtone/notification volume is returned to the previous level before using the Ring command. Environmental Variables: Device: Aries 2.5 Build ID: 20150716033647 Gaia: 981c61cdeb527fac8f8383c110df0e749eff67ea Gecko: 72835344333f Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 42.0a1 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 Repro frequency: 10/10 See attached: logcat
This issue DOES occur on Flame 2.5, 2.2, 2.1 and 2.0 builds. The ringtone/notification volume is left at the maximum on 2.5 and 2.2 builds. On 2.1 and 2.0 builds, the Media volume is affected instead, but the behavior is the same. Environmental Variables: Device: Flame 2.5 Build ID: 20150715160204 Gaia: b9968cdc4a1dee49848fed6159a59c378cea062d Gecko: 49683d4e9ebd Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 42.0a1 (2.5) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 Environmental Variables: Device: Flame 2.2 Build ID: 20150715002506 Gaia: 84d0c76370dcd3d25813b00de55194730884355b Gecko: a5db6d9850f6 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Environmental Variables: Device: Flame 2.1 Build ID: 20150716001207 Gaia: cc24cce17ab2ebf79f6505103da714fc65bc5ec1 Gecko: 3e0074546463 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Environmental Variables: Device: Flame 2.0 Build ID: 20150716000204 Gaia: b16ba05481e577bc644ed8966f587a70fe2148e6 Gecko: 45795565d229 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 32.0 (2.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Keywords: feature
[Tracking Requested - why for this release]: Since there is no gaia work being done for FMD or FxA, putting it as backlog
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.

Attachment

General

Created:
Updated:
Size: