1069148 - Ringtones volume is very low (Played through earpiece?)

Status: RESOLVED DUPLICATE of bug 1065147

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

Description

[vasanth]

[Blocking Requested - why for this release]: Blocking CAF release

Steps to Reproduce:
1. Boot up the DUT
2. Select some ring tone from UI Settings->Sound->Ringtones 
3. Set ring tone volume to high from UI Settings->Sound->Ringtones & Notifications
4. Receive a call
5. Observe that incoming call ringtone volume is very low

Also volume is very low while changing ringtones.

I guess ringtones are played in earpiece instead of speaker?

Device and build Details:
Device msm8x26 QRD KK branch

Gaia : 944e5b4582c4efa1b67cd33245dbb8f6aa25d09f
Gecko: a50444fdaa68fefefc3ecc08d97530e13a4742ab
OS Version: 2.1.0
Platform Version : 34.0a2
Build ID: 20140915184008

Comment 1

[Jason Smith [:jsmith]]

QA Wanted - Can this be reproduced on a Flame KK 2.1 build?

Comment 2

[No-Jun Park [:njpark]]

I tried it on KK 2.1, and I can repro the bug.
1. In settings, adjust the ringtone level.  The phone plays the example ringtone in its correct volume.
2. Exit to homescreen.  Receive incoming call.
Actual:
Initially the ringtone plays at the correct sound level for 1/2 seconds, then it starts to play at reduced sound level.

Version Info:
Gaia-Rev        f0f22bb46c881e02524b3991c2587ff8c0a9fc37
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-aurora/rev/ab2a88c05a4b
Build ID        20140919050548
Version         34.0a2
Device Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20140919.083111
FW-Date         Fri Sep 19 08:31:21 EDT 2014
Bootloader      L1TC10011800

Comment 3

[Jason Smith [:jsmith]]

QA Wanted for branch checks to check if this is a regression.

Comment 4

[Chris Kreinbring [:CKreinbring]]

The bug repros on KK Flame 2.1
Actual result: When the device is called, the ringtone plays at regular volume momentarily before becoming barely audible.  The ringtones are also very quiet when selected on the Sound setting page.

BuildID: 20140919125053
Gaia: f1d3cd2301b604b7b8b8dcf69bd36ba638c1ab44
Gecko: c059221c4637
Platform Version: 34.0a2
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

--------------------------------------------------------------------------------------------------------

The bug does not repro on KK Flame 2.2, Flame 2.0 or Flame 2.0 Base
Actual result: When the device is called, the ringtone plays at regular volume until the call is answered or ended.  On Flame 2.2, the ringtones do play quietly when selected on the Sound setting page.

Flame 2.2
BuildID: 20140919111450
Gaia: 12d634c63ec8a41553a9f150c38260c992dc0020
Gecko: a084c4cfd8a1
Platform Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Flame 2.0
BuildID: 20140919132350
Gaia: d904bc0edc5bda2c29a2ed5dca3c1244f26136e5
Gecko: a491bcbd9dfc
Platform Version: 32.0
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 2.0 Base
BuildID: 20140904160718
Gaia: 506da297098326c671523707caae6eaba7e718da
Gecko: 
Platform Version: 32.0
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 5

[Hema Koka [:hema]]

Blocking Reason: Regression

Jim,

Perhaps not related to ringtone app changes, but if you can investigate and route to the component, it would be helpful.

Thanks
Hema

Comment 6

[Jim Porter (:squib)]

I have no idea, although I've experienced this myself. It would be better to ask someone from systems or comms. The ringtones app shouldn't be able to affect this in any way.

Comment 7

[Hema Koka [:hema]]

Candice/Gregor,

Who would be right person to help investigate?

Thanks
Hema

Comment 8

[Gregor Wagner [:gwagner]]

Can we get the regression window?

Comment 9

[Joshua Mitchell (Inactive)]

(In reply to Gregor Wagner [:gwagner] from comment #8)
> Can we get the regression window?

Greg - this is:
2.0 Unaffected
2.1 Affected
2.2 Unaffected

so there are TWO different regression windows that can be found here. 
We can find the regression cause between 2.0 and 2.1 to identify what broke
or
We can find the 'reverse regression' from 2.1 to 2.2 to find out what 'fixed' the issue in 2.2 to cause it to be unaffected and that can get (hopefully) uplifted to 2.1 to spread the fix to there

which would you prefer?

Comment 10

[Gregor Wagner [:gwagner]]

(In reply to Joshua Mitchell [:Joshua_M] from comment #9)
> (In reply to Gregor Wagner [:gwagner] from comment #8)
> > Can we get the regression window?
> 
> Greg - this is:
> 2.0 Unaffected
> 2.1 Affected
> 2.2 Unaffected
> 
> so there are TWO different regression windows that can be found here. 
> We can find the regression cause between 2.0 and 2.1 to identify what broke
> or
> We can find the 'reverse regression' from 2.1 to 2.2 to find out what
> 'fixed' the issue in 2.2 to cause it to be unaffected and that can get
> (hopefully) uplifted to 2.1 to spread the fix to there
> 
> which would you prefer?

Seems like we are missing an uplift. Lets try the reverse-regression-window and see if we can fix it with uplifting a patch.

Comment 11

[Chris Kreinbring [:CKreinbring]]

Reverse regression window
Last broken
BuildID: 20140919052449
Gaia: d170091ba1b5597b05f37fb259f6b8eb02568798
Gecko: 3475e6a1665a
Platform Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

First working
BuildID: 20140919102949
Gaia: 12d634c63ec8a41553a9f150c38260c992dc0020
Gecko: 74d4fc84e39e
Platform Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Working Gaia / Broken Gecko = No repro
Gaia: 12d634c63ec8a41553a9f150c38260c992dc0020
Gecko: 3475e6a1665a
Broken Gaia / Working Gecko = Repro
Gaia: d170091ba1b5597b05f37fb259f6b8eb02568798
Gecko: 74d4fc84e39e
Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/d170091ba1b5597b05f37fb259f6b8eb02568798...12d634c63ec8a41553a9f150c38260c992dc0020


Mozilla Inbound
Last broken
BuildID: 20140919023749
Gaia: f5e41cebfcafa475ef62aebc7a72448af021cc11
Gecko: ae30e90db6b1
Platform Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

First working
BuildID: 20140919033249
Gaia: 0b27f1302b3d73d28cbb0c79f77c7de3bcd4fc15
Gecko: a649f3a1f9a3
Platform Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Working Gaia / Broken Gecko = No repro
Gaia: 0b27f1302b3d73d28cbb0c79f77c7de3bcd4fc15
Gecko: ae30e90db6b1
Broken Gaia / Working Gecko = Repro
Gaia: f5e41cebfcafa475ef62aebc7a72448af021cc11
Gecko: a649f3a1f9a3
Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/f5e41cebfcafa475ef62aebc7a72448af021cc11...0b27f1302b3d73d28cbb0c79f77c7de3bcd4fc15

Comment 12

[Joshua Mitchell (Inactive)]

It seems like the patch in question (that needs uplifted) just landed on 2.1 yesterday - https://bugzilla.mozilla.org/show_bug.cgi?id=1065147#c20

QA-Wanted to re-test this bug against the latest 2.1 - it should be fixed and we can close this out as fixed

Comment 13

[Joshua Mitchell (Inactive)]

sorry, that NI is unneeded, clearing it

Comment 14

[Joshua Mitchell (Inactive)]

This issue no longer repro's in the latest 2.1 - meaning it was fixed by the patch from bug 1065147



Device: Flame 2.1
BuildID: 20140923142342
Gaia: b542080231bb9cdbdb282ab926965ad3f91f7460
Gecko: fab3c895bc89
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 15

[bhargavg1]

(In reply to Joshua Mitchell [:Joshua_M] from comment #14)
> This issue no longer repro's in the latest 2.1 - meaning it was fixed by the
> patch from bug 1065147
> 
> 
> 
> Device: Flame 2.1
> BuildID: 20140923142342
> Gaia: b542080231bb9cdbdb282ab926965ad3f91f7460
> Gecko: fab3c895bc89
> Version: 34.0a2 (2.1)
> Firmware: V180
> User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

updating the bug correctly to duplicate of bug 1065147