1096660 - [Loop] Mute button toggle during a call in loop app does not show icon of sound being muted

Status: RESOLVED INVALID

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

Description

[[:SalvadorR]]

Attachment: logcat_20141110_1216.txt

Description:
Mute button toggle during a loop call will not show an icon indicating that the sound is muted, when camera and video toggle show when toggled off/on

Repro Steps:
1) Update a Flame device to BuildID: 20141110001201
2) Start a Loop call
3) Disable sound by touching mute button
4) Observe toggle icons
  
Actual:
Mute toggle does not appear
  
Expected: 
Mute toggle should appear
  
Environmental Variables:
Device: Flame 2.1 (319mb) KK Shallow Flash
BuildID: 20141110001201
Gaia: 0ec1925fc37b7c71d129ae44e42516a0cfb013c4
Gecko: 97487a2d1ee6
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
  
Notes: Toggles appear for camera and mic, but not for mute
  
Repro frequency: 3/3
See attached: Video, Logcat
http://youtu.be/LiyGMusz7II

Comment 1

[[:SalvadorR]]

This issue also occurs on Flame 2.0 and Flame 2.2

Results: Mute icon doesn't appear 

Flame 2.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141110000204
Gaia: d3e4da377ee448f9c25f908159480e867dfb13f3
Gecko: 7198906837e7
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 2.2

Device: Flame 2.2 Master (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141110040206
Gaia: 5f8206bab97cdd7b547cc2c8953cadb2a80a7e11
Gecko: d380166816dd
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Comment 2

[Joshua Mitchell (Inactive)]

NI to Loop owner for blocking call

Comment 3

[Maria Angeles Oteo (:oteo)]

Checking the video and the STR, you are not pressing the mute button (microphone), you are tapping on the speaker one and it's not designed to be shown in the status bar. 

Camera and mute icons are designed to be shown but the speaker is not, so closing the bug as invalid.

Please, reopen the bug or let me know if you see another related issue or my explanation is not clear enough, thanks a lot!