Closed Bug 1205377 Opened 9 years ago Closed 9 years ago

[Notifications]The "Playing song" icon doesn't appear in status bar after finishing a voice call

Categories

(Firefox OS Graveyard :: AudioChannel, defect, P4)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:2.5+, b2g-v2.2 unaffected, b2g-master affected)

RESOLVED DUPLICATE of bug 1199605
blocking-b2g 2.5+
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- affected

People

(Reporter: MaxIvanov, Assigned: alwu)

References

Details

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

Attachments

(1 file)

Attached file logs.txt
Description:
After ending a voice call a user is not notified in a status bar that a song is playing. 

Repro Steps:
1) Update a Flame to 20150916030229
2) Go to Music app and play any song
3) Press "home button" observe "Song is playing" icon in a notification bar
4) Start a voice call
5) Finish a voice call
6) Observe a status bar

Actual:
No "Song is playing" icon in a status bar


Expected:
"Song is playing" icon in a status bar

Environmental Variables:
Device: Flame 2.5
Build ID: 20150916030229
Gaia: 994ff1537c2d7ca4d1658806c50f3ceba1053f9b
Gecko: 3e8dde8f8c174cce2c0b65c951808f88e35d1875
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Repro frequency: (100 %)
See attached: (video clip, logcat)
https://youtu.be/4AHq8mSTfmU
This issue DOES occur on Flame 2.5 and Aries 2.5 and does NOT on Flame 2.2 
Result:"Song is playing" icon is not showed in a status bar

Device: Flame 2.5
Build ID: 20150916030229
Gaia: 994ff1537c2d7ca4d1658806c50f3ceba1053f9b
Gecko: 3e8dde8f8c174cce2c0b65c951808f88e35d1875
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0
-----------------------------------------------------------------

Device: Aries 2.5
Build ID: 20150916015546
Gaia: 994ff1537c2d7ca4d1658806c50f3ceba1053f9b
Gecko: 3e8dde8f8c174cce2c0b65c951808f88e35d1875
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 43.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regression
Whiteboard: [2.5-Daily-Testing][Spark]
[Blocking Requested - why for this release]:

Regression that will be encountered by end users.
blocking-b2g: --- → 2.5?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Contact: sleedavid
blocking-b2g: 2.5? → 2.5+
Priority: -- → P4
B2G inbound window: 

Last Working
Environmental Variables:
Device: Flame 2.5
BuildID: 20150914235936
Gaia: 01cf74daf8e1c1fbc945dd61ff0b2524f4b06b8e
Gecko: 64960a58c9857af68b994ae8f303e708205ac8f6
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

First Broken
Device: Flame 2.5
BuildID: 20150915002837
Gaia: 01cf74daf8e1c1fbc945dd61ff0b2524f4b06b8e
Gecko: 5a91d8cf566dc4879a7b7e10dd41fc349cfddf61
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0


First broken Gecko Last working Gaia - Repro
Gaia: 01cf74daf8e1c1fbc945dd61ff0b2524f4b06b8e
Gecko: 5a91d8cf566dc4879a7b7e10dd41fc349cfddf61

Last working Gecko first broken Gaia - NoRepro
Gaia: 01cf74daf8e1c1fbc945dd61ff0b2524f4b06b8e
Gecko: 64960a58c9857af68b994ae8f303e708205ac8f6

Gecko Pushlog: 
http://hg.mozilla.org/integration/b2g-inbound/pushloghtml?fromchange=64960a58c9857af68b994ae8f303e708205ac8f6&tochange=5a91d8cf566dc4879a7b7e10dd41fc349cfddf61

This issue appears to be caused by changes made in bug # 1129882
Blocks: 1129882
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Alastor this is another issue that seems to have been caused by the changes for bug 1129882.  Can you please take a look?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado) → needinfo?(alwu)
Assignee: nobody → alwu
Flags: needinfo?(alwu)
Component: Gaia::Music → AudioChannel
Hi, Jim,
Do you know where is the code about handling the play icon in status bar? (In music app)
Thanks!
Flags: needinfo?(squibblyflabbetydoo)
I found the possible root cause, that is we don't send the "audiochannelchanged" event to notify the sound manager when we resume the music. Therefore, we would get the wrong current audio channel.

Ex.
1. Play music
   - current channel = content
2. Start telephony, and pause music
   - current channel = telephony
3. Stop telephony, and resume music 
   - current channel = none (X)

---

Hi, Evan,
Could we send this event when resume audio?
Thanks!
Flags: needinfo?(evan)
I don't think we do anything special in the music app, except for setting the audio channel in the manifest.
Flags: needinfo?(squibblyflabbetydoo)
Hi Alastor,

The patch for Bug 1199605 will fix this.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(evan)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: