Closed
Bug 1151692
Opened 9 years ago
Closed 9 years ago
During incoming call, the Volume Down button mutes the ringtone but not Volume Up
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(tracking-b2g:backlog, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
WONTFIX
tracking-b2g | backlog |
People
(Reporter: pmathur, Unassigned)
Details
(Whiteboard: [2.2-nexus-5-l])
Steps to reproduce 1. From another phone, make a call to the Nexus 5 device. 2. On the Nexus 5 device, use the hardware Volume Up or Down button to change the ringer volume. Expected Results The ringer can be adjusted with the hardware Volume Up and Down buttons. Actual Results The first time the hardware Volume Up or Down button is pressed, the volume goes to mute. Pressing the hardware Volume Up or Down buttons does not take the volume out of mute state. Test Environment Gaia-Rev a6351e1197d54f8624523c2db9ba1418f2aa046f Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c3335a5d3063 Build-ID 20150406002503 Version 37.0 Device-Name hammerhead FW-Release 5.0 FW-Incremental eng.cltbld.20150406.035814 FW-Date Mon Apr 6 03:58:30 EDT 2015 Bootloader HHZ12d
Updated•9 years ago
|
Flags: needinfo?(hcheng)
Comment 1•9 years ago
|
||
Sorry, but I cannot reproduce this bug with below pvt eng build. * Test Env: Build ID 20150406162505 Gaia Revision 485322797a069e5b185931e87d15d4e921e25b64 Gaia Date 2015-04-06 18:36:29 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/f766e5052b39 Gecko Version 37.0 Device Name hammerhead Firmware(Release) 5.0 Firmware(Incremental) eng.cltbld.20150406.195612 Firmware Date Mon Apr 6 19:56:28 EDT 2015 Bootloader HHZ12d
Flags: needinfo?(hcheng)
Comment 2•9 years ago
|
||
When the call is coming, press volume up, the ringtone will become louder. But if you press volume down, device will enter mute status. Fail rate:5/5 Nexus 5_2.2 version: Build ID 20150406002503 Gaia Revision a6351e1197d54f8624523c2db9ba1418f2aa046f Gaia Date 2015-04-03 22:06:41 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c3335a5d3063 Gecko Version 37.0 Device Name hammerhead Firmware(Release) 5.0 Firmware(Incremental) eng.cltbld.20150406.035757 Firmware Date Mon Apr 6 03:58:14 EDT 2015 Bootloader HHZ12d
Updated•9 years ago
|
Whiteboard: [2.2-nexus-5-l]
Comment 3•9 years ago
|
||
I think this behavior has been implemented as expected. I've always seen the callscreen behave like this. I just checked 2.1, it reproduces there. QA wanted to check 1.4 on Buri to see if it was there. If so, no need to check further. If not, please check Flame 1.4. Build ID 20150406161207 Gaia Revision 87e55a7ec688138812181747f690fd188d2a0668 Gaia Date 2015-04-03 21:43:01 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/747b6132c44d Gecko Version 34.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20141120.194707 Firmware Date Thu Nov 20 19:47:17 EST 2014 Bootloader L1TC00011880
blocking-b2g: 2.2? → ---
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → affected
Keywords: qawanted
Comment 4•9 years ago
|
||
I see behavior on comment 2 but NOT behavior on comment 0 with Buri v1.4. With incoming call ringing, device responds to volume UP as expected, but as soon as volume DOWN is pressed once it mutes the ring and cannot be unmuted for the duration of the incoming ringing. I do NOT see what's being described on comment 0 which is ring mutes regardless of what I press - this is NOT observed. Note setting tracking flag because I'm not sure if the behavior I'm seeing is what the reporter was seeing. Tested on: Device: Buri 1.4 BuildID: 20150204000206 Gaia: 04265f42139a7a5c611c45e4869582642927e835 Gecko: af6e951d18ca Version: 30.0 (1.4) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Note that there are no newer v1.4 Buri builds on PVT website. This is the newest.
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 5•9 years ago
|
||
I think the behavior seen is the one in comment 2. On comment 2, it happened on the same build and was reproduced 5 times. Hence, this is not a Nexus 5 issue. We'll need some UX input to confirm it the behavior is the one we expect.
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → affected
Flags: needinfo?(cawang)
Summary: [Nexus 5] During incoming call, Volume Up and Down buttons stop responding after trying to change the call volume once → During incoming call, Volume Up and Down buttons stop responding after lowering the call volume once
Comment 6•9 years ago
|
||
Hi I think the rule here is that if the phone is ringing, tapping all the hardware keys (volume up/ down and power key) will switch it to mute mode. The behavior in comment 2 is not expected. Because if the volume up key can really adjust ringtone at that moment, then the volume down should work the same way too and then users have no way to enter mute mode with this rule. So I'd still go with my suggestion here (all hardware keys -> mute). Thanks!
Flags: needinfo?(cawang)
Updated•9 years ago
|
tracking-b2g:
--- → backlog
Summary: During incoming call, Volume Up and Down buttons stop responding after lowering the call volume once → During incoming call, the Volume Down button mutes the ringtone but not Volume Up
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•