1096130 - [FFOS2.0][Woodduck][FM][Calendar][Ringtone] The reminder ringtone will only play in Headset when play the FM with speaker in background.

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::FMRadio, defect, P2)

Description

[sync-1]

DEFECT DESCRIPTION:
 The reminder ringtone will only play in Headset.
 It is very bad experience.
 
 Soul 3.5 FF当外放FM时，日历事件提醒铃声会外放。-- OK
 周琴0752-2639384（61384）
 
  REPRODUCING PROCEDURES:
 1. Enter FM Radio with Headset,
 2. Play the FM in speaker,
 3. Enter Calendar and create an event with reminder,
 4. When the reminder comes, check the ringtone.
 
  EXPECTED BEHAVIOUR:
 It should play in speaker according to the behavior of Soul 3.5 FF.
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:100%
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[Josh Cheng [:josh]]

Hi Norry,
qawanted for Woodduck 2.0M and Flame 2.0/2.1/2.2. Thanks!

Comment 2

[Josh Cheng [:josh]]

Hi Shawn,
Could you please help to check the problem? Thanks!

Comment 3

[shawn ku [:sku]]

Hi Wayne:
 Please help check this issue.
Thanks!!
Shawn

Comment 4

[Wayne Chen [:xwaynec]]

Hi all,

I tried woodduck today's build. It works fine.

From log,

11-10 10:06:53.547 D/AudioMTKPolicyManager(  144): setOutputDevice() output 2 device 0002 delayMs 0
11-10 10:06:53.555 D/AudioMTKPolicyManager(  144): setOutputDevice() setting same device 0002 or null device for output 2

1. device 0006 is headset + speaker, if it still have no alert from speaker. I think partner should check it first

11-10 10:06:53.652 D/AudioMTKPolicyManager(  144): setOutputDevice() output 2 device 0006 delayMs 0
11-10 10:06:54.061 D/AudioMTKPolicyManager(  144): setOutputDevice() output 2 device 0006 delayMs 184
11-10 10:06:54.061 D/AudioMTKPolicyManager(  144): setOutputDevice() setting same device 0006 or null device for output 2
11-10 10:06:55.836 D/AudioMTKPolicyManager(  144): setOutputDevice() output 2 device 0002 delayMs 184


Sincerely,
Wayne

Comment 5

[shawn ku [:sku]]

Hi reporter:
 Per comment 4, there is no such problem from Moz's build.
Please provide log for us to check what went wrong.

Thanks!!
Shawn

Comment 6

[Norry.L.F(Leave from Mozilla)]

Attachment: 1749.MP4

Hi Josh,

We verified it on Flame 2.0/2.1/2.2, and the ringtone can be played from speaker. So this issue can't be reproed.
On Woodduck 2.0m, I can't verify it due to a blocked issue: Bug 1091352 - [Woodduck][v2.0][FM Radio]The device can't play FM radio by speaker.

Attached video and logcat.

----------------------------------
Flame 2.0 build:
Gaia-Rev        d3e4da377ee448f9c25f908159480e867dfb13f3
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/7198906837e7
Build-ID        20141109000201
Version         32.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141109.032915
FW-Date         Sun Nov  9 03:29:26 EST 2014
Bootloader      L1TC00011880
------------------------------
Flame 2.1 build
Gaia-Rev        0ec1925fc37b7c71d129ae44e42516a0cfb013c4
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/97487a2d1ee6
Build-ID        20141109001201
Version         34.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141109.035007
FW-Date         Sun Nov  9 03:50:18 EST 2014
Bootloader      L1TC00011880
------------------------
Flame2.2 build:
Gaia-Rev        5f8206bab97cdd7b547cc2c8953cadb2a80a7e11
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/d380166816dd
Build-ID        20141109160204
Version         36.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141109.193004
FW-Date         Sun Nov  9 19:30:14 EST 2014
Bootloader      L1TC00011880

Comment 7

[Wayne Chen [:xwaynec]]

need info Jason for comment 6 

"On Woodduck 2.0m, I can't verify it due to a blocked issue: Bug 1091352 - [Woodduck][v2.0][FM Radio]The device can't play FM radio by speaker."


Hi Jason,

please help it~

Comment 8

[Wayne Chen [:xwaynec]]

11-18 04:57:00.313 D/AudioMTKPolicyManager(  145): setOutputDevice() output 2 device 0002 delayMs 0
11-18 04:57:00.313 D/AudioMTKPolicyManager(  145): setOutputDevice() setting same device 0002 or null device for output 2
11-18 04:57:00.451 D/AudioMTKPolicyManager(  145): setOutputDevice() output 2 device 0006 delayMs 0
11-18 04:57:01.180 D/AudioMTKPolicyManager(  145): setOutputDevice() output 2 device 0006 delayMs 184
11-18 04:57:01.180 D/AudioMTKPolicyManager(  145): setOutputDevice() setting same device 0006 or null device for output 2
11-18 04:57:02.630 D/AudioMTKPolicyManager(  145): setOutputDevice() output 2 device 0002 delayMs 184

Hi all,

From log, output device 0006 is speaker + headset. And also I'm sure that speaker is fine.

Comment 9

[Josh Cheng [:josh]]

Hi Reporter,
We cannot reproduce this issue in latest driver build. Could you check again? Thanks!

Comment 10

[sync-1]

Hi,all
    i check this problem on latest version, and no such problem again. thanks