Closed Bug 1095716 Opened 11 years ago Closed 10 years ago

[Loop] Unable to mute using volume button while connecting to a loop call.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)

RESOLVED INVALID
blocking-b2g -
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: jthomas, Unassigned)

References

()

Details

(Whiteboard: [2.1-exploratory-3])

Attachments

(1 file)

Description: While the user is attempting to connect to another device using loop the user is unable to mute the volume using the volume down button. Repro Steps: 1) Update a Flame to 20141106001204 2) Attempt to make a call to another device using loop. 3) Press and hold the volume down button. Actual: User is unable to mute the calling tone using the volume down button. Expected: It is expected that the user will be able to mute the calling tone by pressing the volume down button. Flame 2.1 Environmental Variables: Device: Flame 2.1 (319mb) KK Shallow Flash BuildID: 20141107001205 Gaia: 6295f6acfe91c6ae659712747dd2b9c8f51d0339 Gecko: 8c23b4f2ba29 Version: 34.0 (2.1) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency: 100% See attached: Logcat & Video Video: https://www.youtube.com/watch?edit=vd&v=MsKbl3iN5pA
This issue DOES occur on the Flame 2.2 KK (319mb) Flame 2.2 Result: User is unable to mute the calling tone using the volume down button. Device: Flame 2.2 Master (319mb)(Kitkat Base)(Shallow Flash) BuildID: 20141107040206 Gaia: 779f05fead3d009f6e7fe713ad0fea16b6f2fb31 Gecko: 64f4392d0bdc Version: 36.0a1 (2.2 Master) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 --------------------------------------------------- Flame 2.0 Result: Unable to connect to other devices using Loop on 2.0 Flame KK (319mb) Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash BuildID: 20141107000206 Gaia: d3e4da377ee448f9c25f908159480e867dfb13f3 Gecko: 9836e9d81357 Version: 32.0 (2.0) Firmware: V188-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
[Blocking Requested - why for this release]: broken expected functionality
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
CAn, QA please help with a regression window here?
blocking-b2g: 2.1? → 2.1+
NI :baku to help start the investigation here or redirect to right folks.
Flags: needinfo?(amarchesini)
(In reply to bhavana bajaj [:bajaj] from comment #3) > CAn, QA please help with a regression window here? this is not a regression
Sorry for the delay. The issue here is that probably we are 'playing' with the wrong audiochannel when the user wants to change the volume. By default the AudioChannel in use is the 'normal' but this can be changed using AudioChannelManager API. navigator.mozAudioChannelManager.volumeControlChannel = 'telephony' should be enough when we are in a call. But before answering we should set it to 'ringer' because I guess they are 2 different channels. We don't have any API to inform the app if we have an existing active call, and in case we need to differentiate between ringer and telephony, probably we have to extend the AudioChannelManager interface. rlin should now more.
Flags: needinfo?(amarchesini) → needinfo?(rlin)
Dear John, I checked your video clips and found you want to mute the "Incall Volume", right? Refer to GSM phone call, It's by design. Also, while to device is waiting to receiving the incoming call, The user can change the ringtone volume by volume key. https://www.youtube.com/watch?v=R9JvsaVmZT4&list=UU7a75Ihpsdw2d1GqWsvMv3g
Flags: needinfo?(rlin) → needinfo?(jthomas)
Test PVT version: Gaia-Rev ee1e5462fa4777eaa7950e0d75706be4383ec007 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/b2fdfce55253 Build-ID 20141119161200 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141119.195237 FW-Date Wed Nov 19 19:52:47 EST 2014 Bootloader L1TC00011880
Dear Randy, Yes, I was trying to mute the volume while attempting to make a Loop call. It didn't seem to mute completely on the build I originally sent this issue. I see that this is by design after seeing your comment from #7. However it looks like you were able to mute completely in the video you referenced. Please let me know if there is anything else.
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(jthomas) → needinfo?(dharris)
==>it looks like you were able to mute completely in the video you referenced. On that timestamp, the device just rings, not enter the in-call mode. The behavior is muting the ringtone, not the voice sound.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Decided to minus it. Please nominate it again if there is any concern.
blocking-b2g: 2.1+ → -
Beatriz, is it an expected behaviour?
Flags: needinfo?(beatriz.rodriguezgomez)
I think it's working as expected, if you press down the volume (telephony channel) you will able to lower the volume but not completely because there is always a minimum sound. In fact, the behavior in Loop is the same than for the GSM calls in FxOS so imho we should close the bug as Invalid.
Flags: needinfo?(beatriz.rodriguezgomez)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: