[Lock screen] Volume cannot be set to max on lockscreen.

NEW
Unassigned

Status

Firefox OS
Gaia::System::Lockscreen
3 years ago
3 years ago

People

(Reporter: Johnt, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

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

Details

(Whiteboard: [3.0-Daily-Testing], URL)

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8614980 [details]
logcat_20150603_1638.txt

Description:
If the user plays a song while headphones are plugged in and locks the device, they will only be able to set the volume up to about 75%. The hearing damage warning will not appear until the device is unlocked.


Repro Steps:

Prereq: 1st time receiving hearing warning message. Headphones plugged in. Song on device.

1) Update a Flame to 20150603130046
2) Play a song.
3) Lock device.
4) Attempt to turn the volume up to 100%


Actual:
Volume is cannot be set past 75%. No hearing damage warning appears on lockscreen.


Expected:
It is expected that the user will see a hearing warning message as to why the volume cannot be set to max, or be able to set the volume to 100%. 


Environmental Variables:
Device: Flame 3.0 kitkat (319mb)
Build ID: 20150603130046
Gaia: 45dc6306cf502a4f00ae9f8bd8293a8a3a37c07b
Gecko: 0920f2325a6d
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0


User Impact:  User may be confused as to why the volume is not being able to be set past 75% from the Lockscreen without the warning as to why.


Repro frequency: 4/4
See attached: Logcat, Video

https://www.youtube.com/watch?edit=vd&v=m0jAo5JEjrU
(Reporter)

Comment 1

3 years ago
This issue DOES occur on the Flame 2.2, Flame 2.1 and the Flame 2.0.

Result: Volume bar seizes at about 75% on lockscreen without damage to hearing message.

Environmental Variables:
Device: Flame 2.2 Kitkat (319mb)
BuildID: 20150112010228
Gaia: f5e481d4caf9ffa561720a6fc9cf521a28bd8439
Gecko: bb8d6034f5f2
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0a1 (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 Kitkat (319mb)
BuildID: 20150603001203
Gaia: 2304a1f6327c2ccf35d6995ee16f2231ed1f22a3
Gecko: 11e5d073db75
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 Kitkat (319mb)
BuildID: 20150603000203
Gaia: 5552bf529d3d6775a968942e9afa6c1d4037362c
Gecko: ad59a350e122
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?]
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
status-b2g-v2.2: --- → affected
status-b2g-master: --- → affected
Flags: needinfo?(ktucker)
Whiteboard: [3.0-Daily-Testing]
This is a bad end user experience because they won't understand why the volume can't be turned up to max on the lock screen if they have not been prompted the warning before. Not nominating to block on this since this is not a regression but it should be fixed.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in before you can comment on or make changes to this bug.