1122538 - [Flame] No sound played by the speaker when receiving incoming call/sms/mms/email or preview ringtones on the phone after OS upgrade

Status: RESOLVED DUPLICATE of bug 1107534

(Firefox OS Graveyard :: AudioChannel, defect)

Description

[Nicolas Mandil (:NicolasWeb)]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150112203352

Steps to reproduce:

1. use the phone for month without issue
2. receive call/sms/mms/email (normal mode, volume 'open')
3. in Settings try to preview other ringtones
4. reset factory settings in recovery mode, do again 2 & 3
5. flash the phone with the lastest base image, do again 2 & 3


Actual results:

1. everything works
2, 3, 4. no sound played at all - vibrator works - ticking problem start (already reported in an other bug)
5. no sound played at all except once the first time I tried to preview a ringtone


Expected results:

sound should be eared

FFOS 2.0

Comment 1

[Nicolas Mandil (:NicolasWeb)]

I need to flash it to dev build, so it's time to ask me any debug data or debug scenario
(I'm just an advanced user, but can do some advanced things : month ago I build FFOS)

Comment 2

[Nicolas Mandil (:NicolasWeb)]

I use base image v188, build 20141016183911

Comment 3

[Nicolas Mandil (:NicolasWeb)]

Attachment: LogCat vhen receiving an incoming sms

LogCat without filter because I don't know what to filter...
LogCat-SMS-1 : Screen Locked
LogCat-SMS-2 : Screen unlocked (less noise maybe)

Comment 4

[Nicolas Mandil (:NicolasWeb)]

Attachment: LogCat vhen receiving an incoming sms-2

Comment 5

[Nicolas Mandil (:NicolasWeb)]

Attachment: media.audio_policy-Sound NOT working

return of adb root && adb wait-for-device && adb shell dumpsys media.audio_policy

Comment 6

[Nicolas Mandil (:NicolasWeb)]

I have sounds on the headphone outpout.

Comment 7

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Hi Wesly,
I'm not sure if this was fixed by new base image. 
You may have more information to share.

Comment 8

[Wesly Huang (EPM)]

Hi Nicolas:

Two thoughts from me

A. your device have HW issue since STR#2.

B. you change SW to v188 based image since STR#2, since in v188 there is a ticking noise problem in SW (that fixed in v18D), even all cases I heard is sound works normal w/ ticking noise.

Do you have v18D SW? (this is b2g internal released for Mozilla QA-ing, not yet published) if you don't, would you try the older v180 base SW (can find in MDN), so know if B is the case you encountered. Thanks.

Comment 9

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Step 3) in Settings try to preview other ringtones

I tried step 3 just by itself and could not hear the sounds on the flame; I am not sure about step 2 as of yet.

I think this might be a gaia bug

Configuration : 
Gaia-Rev        1d53fb07984298253aad64bfa4236b7167ee3d4d
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/b2b10231606b
Build-ID        20150128010234
Version         38.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150127.035842
FW-Date         Tue Jan 27 03:58:52 EST 2015
Bootloader      L1TC000118D0

Comment 10

[Nicolas Mandil (:NicolasWeb)]

Attachment: Sound-1.txt - v180-Just Flashed- Previewing ringtone-Sound once then nothing

Hi Wesly,

Here are my investigation results :

- I flashed my Flame with Base Image v180.
- I enable remote debugging
- Lunch Logcat
- Tried to preview an other ringtone, then an other one
- Cancelled (Done button not clicked)
>> Result : The issue is 5. of comment #0 (no sound played at all except once the first time I tried to preview a ringtone)
>> UI : the first item of ringtones list is a "o" but without text (list or file corruption ?)

- Stopped Logcat, thought to reboot, then thought that I should try (but forget to run again logcat...) 
- Plug headphone + try to preview ringtones
>> sound works well on headphone

- unPlug headphone + try to preview ringtones
>> sound works well *on the speaker* !! (Sound-2.txt)

- Reboot the phone
>> sound still works well on the speaker and headphone (Sound-3.txt)

- Reflash to v180
>> sound still works well on the speaker and headphone (Sound-4.txt)

- Reflash to v188
>> sound still works well on the speaker and headphone (Sound-5.txt)
>> empty UI in ringtones list disappear

- Reflash to v180
>> sound still works well on the speaker and headphone (Sound-6.txt)
>> empty UI in ringtones list appear again (ringtones list bug.png)

- ScreenShot of ringtones list
- Set others Ringtone & Alert than 'Firefox OS' that exist on BI v123 & v180 & v188 : 'Disco Drive' and 'Cloche' (Bell in French)
- Reflash to v123
>> sound still works well on the speaker and headphone (Sound-7.txt)
>> empty UI in ringtones list disappear again, but no sound is pre-selected

- FOTA to v188 (to 20141107 34Mb, then to 20141107 74Mb)
- Enable adb
>> sound still works well on the speaker and headphone (Sound-8.txt)
>> empty UI in ringtones list still not present
>> Settings UI Ringtone='Disco Drive' , Alert='Cloche' BUT Select sound Panes = "Firefox OS" (UI Panes.png)

- Set language to English
>> Settings UI Ringtone and Alert show 'Change'

Comment 11

[Nicolas Mandil (:NicolasWeb)]

Attachment: Sound-2.txt - sound works well *on the speaker* after plug-in/out headphones - Logcat

For others attachments listed in comment #10 ask me ;-)

Comment 12

[Nicolas Mandil (:NicolasWeb)]

Attachment: ringtones list bug.png

Comment 13

[Nicolas Mandil (:NicolasWeb)]

Attachment: media.audio_policy-Sound Working

Return of 
After having plug in/out headphone as described in comment #10

Comment 14

[Andrea Marchesini [:baku]]

rlin, it seems that this bug is related to audio routing.  Can you take a look and give a feedback? Thanks!

Comment 15

[Wesly Huang (EPM)]

(In reply to Nicolas Mandil (:NicolasWeb) from comment #10)
> Hi Wesly,
> 
> Here are my investigation results :
>

So sounds to me 2 issues in total in your latest test, which is bit different from comment#0 (which including no sound for sms/mms/incoming call)?

Issue#1, no sound for ringtone preview except first time, as Andreas suggests could be audio path issue 

> - I flashed my Flame with Base Image v180.
> - I enable remote debugging
> - Lunch Logcat
> - Tried to preview an other ringtone, then an other one
> - Cancelled (Done button not clicked)
> >> Result : The issue is 5. of comment #0 (no sound played at all except once the first time I tried to preview a ringtone)

Issue#2: no text for first ringtone in list, but ok if you change to English (what's the language used before changing to English?)

> >> UI : the first item of ringtones list is a "o" but without text (list or file corruption ?)
> - Set language to English
> >> Settings UI Ringtone and Alert show 'Change'

Comment 16

[Randy Lin [:rlin] - Be Mozillian on 2015/01/26]

Hi Alastor, 
Could you follow this?
You may request TPE's QA to help reproduce this one, thanks.

Comment 17

[Nicolas Mandil (:NicolasWeb)]

> So sounds to me 2 issues in total in your latest test, which is bit
> different from comment#0 (which including no sound for sms/mms/incoming
> call)?

I think there are 3 issues. I'm not sure how they are linked (related?) together.
 
> Issue#1, no sound for ringtone preview except first time,
Not only ringtone preview, but any sound that should output by the speaker (as said in comment #0) : notification, sms/mms/incoming/call/email

> as Andreas suggests could be audio path issue
OK. Let's wait Andreas' answer to know if the component of this bug should be changed so.

> Issue#2: no text for first ringtone in list, but ok if you change to English
> (what's the language used before changing to English?)
It was French ;-)
The issue is not exactly this.
Issue#2 : no text for first ringtone in list (English thing is for the 3th issue)
It happen when you back-flash the device *without* setting *before* a ringtone and alert sound that exist in that previous base image.

Issue#3: Mismatch between UIs Settings/Sound and Settings/Sound/Select Sound (for Ringtones & Alerts)
Settings UI Ringtone='Disco Drive' , Alert='Cloche' BUT Select sound Panes = "Firefox OS" (UI Panes.png)
This happen when you FOTA to next BI. It becomes again consistent if you switch to an other language for the whole UI (v123->v188 & French->English in comment #10)

Depending on investigation, does Issue#3 need a that I report a following bugs please ?
(Answering with my next comment will be easier I hope)

Comment 18

[Nicolas Mandil (:NicolasWeb)]

My today's investigation ;-)

1-Important investigation to make //I can't anymore because of 3.2
- Do STR are sensitive to FOTA vs Flashing ? //I didn't took any notes about this, but I persisted using FOTA instead of Flashing : could be that flashing is out of STR

2-Step to Reproduce (STR)
// Make as if you've always been on BI v123 and never on v180 or v188
- Flash to v123, (set French language for me)
- Enable adb
- Set ringtones='Disco Drive' & Alerts='Cloche' (Bell in French)
- Disable screen saver (screen time out = never) and screen lock (Monitoring with adb + Downloading issues in my case ; could come from my modem but to be sure)
- Update to FOTA 20141107  3.4 Mb
- Update to FOTA 20141107 72.8 Mb //your are now on the v188
- Preview a ringtone (then cancel it or validate it)
- Incoming call, incoming sms
=> Actual results <= : No sound on the speaker

3-Step to Solve (STS)
These are alternatives :
3.1
- do STR
- plug in/out headphones
=> Actual results <= : Sound on the speaker. STR again make the issue again

3.2 (Full resolved)
- do STR
- *by the settings app* reset the phone //Not sure if this is related to this STS, but I done it
- Restart you phone in Recovery Mode
- Wipe cache
- Wipe data/Reset Factory
=> Actual results <= : Sound on the speaker, *even* if you make again STR
/!\ according to comment #0 STR 'reset factory settings in recovery mode' shouldn't solve the issue. So There should be something that helped 3.2 STS to solve the issue.

Nahoki, as you experienced the issue :
- can you investigate these STR but with flashing ?
- do you confirm these STR and STS ?

4-Investigation that could be needed for a fix
- others devices than Flame ?
- v123 -> v188 -> next BI (currently tested V18D) : is the issue still here if no STS made ?
- v123 -> next BI (currently tested V18D) : is the issue still here if no STS made ?

Comment 19

[Alastor Wu [:alwu]]

I tested it on V18D and latest Gecko version, the problem still exists.

I am not sure that is related to audio routing. Because sometime even I use the headphone, the sound is still silent.

I check the state from dumpsys, the stream doesn't be muted, and the output device seems correct.
 
But here is some thing strange to me. That is the sound from the setting app is fragmentary. The sound doesn't playback smoothly. 

----

And I check the previous Gecko version, this problem isn't exist.
So maybe we could ask QA to find the problematic patch.

Gaia-Rev        ff6dbb006e4e60edba697639aa2a2a199b07069b
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/30920bcb070a
Build-ID        20140923160207
Version         35.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20140923.192209
FW-Date         Tue Sep 23 19:22:19 EDT 2014
Bootloader      L1TC000118D0

Comment 20

[Alastor Wu [:alwu]]

This problem doesn't exist in previous gecko version, 
Could you help me to find the problematic patch? 
Thanks!

Comment 21

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Maybe this might be related: bug 1107534

Comment 22

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

regression range looks like it's on 2.2 : 
hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c007f1136acd&tochange=acc3209d766a

https://bugzilla.mozilla.org/show_bug.cgi?id=1107534#c3

Comment 23

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

This might not be the same:
build: 20141117080828 actually works for me straight off with just going to settings and preview.
build: 20150112010228 was broken.

Trying to narrow regression range.

Comment 24

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

FYI, for future reference, when asking for a regression window, regressionwindow-wanted +qawanted will get the attention of our qawanted crew to deliver a regression window.

Comment 25

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

STR:
1. flash devices using images
2. go through FTE, exit FTE
3. launch settings
4. select sound 
5. select ringtones
6. select a ringtone that is different from the default such as cunning

Expected: preview sound is heard
Actual: no sound

broken: 2014-12-15-04-02-01
broken: 2014-11-30-04-02-07
broken: 2014-11-23-04-02-09
broken: 2014-11-20-04-02-05
Works: 2014-11-18-04-02-05
broken: 2014-11-19-04-02-05
broken: 2014-11-18-14-40-12

Checking range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7913c9392c5f&tochange=084441e904d1
Possibly:
http://hg.mozilla.org/mozilla-central/rev/acc3209d766a
https://hg.mozilla.org/integration/mozilla-inbound/rev/acc3209d766a

Checking inbound:
ok : 20141118083012
broken : 20141118113125
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=0794e627093c&tochange=af4b8990fd98

Suspect:
[e-mail]
Wed Nov 19 08:34:31 2014 +0000 3870aaf0cf48	Blake — Bug 1100820 - Stop reading output data from MediaCodecProxy. r=edwin.

Working on a build with this backed out...

Comment 26

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Oops.  please ignore from the last comment: 

Checking range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7913c9392c5f&tochange=084441e904d1
Possibly:
http://hg.mozilla.org/mozilla-central/rev/acc3209d766a
https://hg.mozilla.org/integration/mozilla-inbound/rev/acc3209d766a

I was typing in notes, and realized I had that portion wrong.

Comment 27

[Nicolas Mandil (:NicolasWeb)]

(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #22)
> regression range looks like it's on 2.2 : 

I reported the bug on Flame using the 2.0 version. All my STR are without 2.2 (but with 1.3 and 2.0). So that's quite strange...
I had it with build 20141016183911 that is BI v188

Comment 28

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Hrm.  I have v18D on my device.

I should try with v188 to see if that makes a difference...

Comment 29

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Hi Nicolas, I don't see any of these builds on our FTP server.  Where are you getting these builds from? 2.0 seems to be working fine for me on v188.

Note:
1) v18D fixed a few things including bug 1093715; which may be related to what you're seeing Nicolas.  We're trying to work with T2M and trying to sign off on a build that is already setup to OTA with our server.
2) Finding a bug in 2.2 < is great... 2.2+ would be even better as there's more likely a chance that the bug will get fixed.  Esp if it's on the nightly.  Having said that, a bad bug like this may get more attention for 2.2 <

The preview ring is not working per comment 25, though for 2.2; we do need to fix that part.

Comment 30

[Nicolas Mandil (:NicolasWeb)]

First, I'm sick, so sorry for my direct writing in any case. I'm kind of a zombie right now :-s
> Hi Nicolas, I don't see any of these builds on our FTP server.  Where are
> you getting these builds from?
On MDN Flame's page : https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame/Updating_your_Flame#Updating_your_Flame%27s_software

>2.0 seems to be working fine for me on v188.
Not for me. Did you tried to follow my updating STR (steps that all users had to do) of comment #18 ?

> Note:
> 1) v18D fixed a few things including bug 1093715; which may be related to
> what you're seeing Nicolas.  We're trying to work with T2M and trying to
> sign off on a build that is already setup to OTA with our server.
I could have tried V18D, but as said in comment #18, my steps to solve (STS) get me to a point where I can't anymore reproduce the bug the ways I know. It could be nice if you do.

> 2) Finding a bug in 2.2 < is great... 2.2+ would be even better as there's
> more likely a chance that the bug will get fixed.  Esp if it's on the
> nightly.  Having said that, a bad bug like this may get more attention for
> 2.2 <
Sure I agree, but :
1- I'm not a developer, just a dogfooding user
2- Flame's users have had FxOS 1.3 and FOTA to 2.0.
   -> that's why I've noticed this bug on 2.0
   -> as a FOTA to 2.2 (V18D+) will be soon released, and this bug seems to my STR related to FOTA update, I think that's quite important to find it on 2.0 (and to fix it on the next update released to users [aka V18D+] as it forbid to use the phone ;-) )
  -> my plan was to try it on nightly, but as said, I'm no more able to reproduce it :-s

> The preview ring is not working per comment 25, though for 2.2; we do need to fix that part.
I agree, thanks for your help !
STR from comment #18 and comment #25 lead maybe to similar but not same bugs. Doing the STR of comment #18 could help to know it, and be sure to fix it for 2.2

You can find me on IRC with my nickname if needed (when I'm not recovering...)

Comment 31

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Sorry to hear that you are sick.  I hope you get better soon.

That explains a lot.  If you're flashing FOTA and going from one version to another via the FOTA; then it's not our code.  I cannot be sure if what you are experiencing is T2M's issue in their build or if there's something in ours...

I'll take a closer look.

Comment 32

[Elie]

Attachment: VIDEO0279_Compress.MP4

Comment 33

[Shally Li（leave from Mozilla）]

Per Comment 24 and Comment 25 ,clear "regressionwindow-wanted".

inbound Regression Window:

Last Working: 20141118035525    --->preview ringtones sound is heard
Gaia-Rev        4aee256937afe9db2520752650685ba61ce6097d
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/7913c9392c5f
Build-ID        20141118035525
Version         36.0a1
Device-Name     flame
FW-Release      4.4.2

First Broken: 20141118082629    --->no sound
Gaia-Rev        4aee256937afe9db2520752650685ba61ce6097d
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/084441e904d1
Build-ID        20141118082629
Version         36.0a1
Device-Name     flame
FW-Release      4.4.2

Last Working gaia + First Broken gecko --> Issue DOES occur (no sound,please see attachments)
Gaia-Rev        4aee256937afe9db2520752650685ba61ce6097d
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/084441e904d1
Build-ID        20141118082629
Version         36.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150209.040038
FW-Date         Mon Feb  9 04:00:51 EST 2015
Bootloader      L1TC000118D0

First Broken gaia + Last Working gecko --> Issue does NOT occur (preview ringtones sound is heard)
Gaia-Rev        4aee256937afe9db2520752650685ba61ce6097d
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/7913c9392c5f
Build-ID        20141118035525
Version         36.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150209.040038
FW-Date         Mon Feb  9 04:00:51 EST 2015
Bootloader      L1TC000118D0


Note:
No sound in Settings->Sound->Ringtones on Flame v2.2&3.0.

Comment 34

[Shally Li（leave from Mozilla）]

Attachment: logcat_1638.txt

Comment 35

[Shally Li（leave from Mozilla）]

Attachment: Last Working gaia&First Broken gecko.MP4

Comment 36

[Nicolas Mandil (:NicolasWeb)]

(In reply to Shally from comment #33)
> No sound in Settings->Sound->Ringtones on Flame v2.2&3.0.

Thank you Shally for working on the regression window.
I reported this bug on a Flame using v2.0 (Base Image v188 found in MDN). Check comment #18 and comment #25
v2.0 : (should be) affected (but not reported in this bug flag yet)
v2.1 : not affected
v2.2 : affected
v3.0 : affected

That's quite strange. There could be 2 regressions windows ?
Shally, could you check v2.0 please ?

Comment 37

[Shally Li（leave from Mozilla）]

(In reply to Nicolas Mandil (:NicolasWeb) from comment #36)
> That's quite strange. There could be 2 regressions windows ?
> Shally, could you check v2.0 please ?

ok,I will check v2.0.

Comment 38

[Shally Li（leave from Mozilla）]

Hi Nicolas,

    I can't repro this bug on Flame v2.0 (Base Image v188),and I can't do FOTA and no BI v123 in our side as mentioned in comment 18.If you can repro,you could set flag to "affected".

Thank you very musch.

Working Flame v2.0 build (base image:v188):
20140923160206(the earliest build)
20141015160202
20141016000201
20141016160207
20141107000206
20141107160202
20141212132154
20150111160204
20150112000204
20150112160233
20150112105648
20150112152717
20150211000203

Comment 39

[Nicolas Mandil (:NicolasWeb)]

Hi Shally,
I reproduce the bug today on v2.0 on base image v188 that is build 20141016183911.
I just reset the phone to factory settings in recovery mode. (so 3.2 of comment #18 do not finally full resolve after waiting for days).
As said, I already had this bug in v2.0, but I can't set the affected flag : can you do it please ?

I noticed in your previous comment that to report v2.0 unaffected, (it seems to me that) you didn't checked build 20141016183911, that is the one with I reproduced this bug on v2.0 (that is v188 on MDN)

Alstor, Shally : can you check that build exactly (that is the one that has been released to users) ? Is there a way to find a regression window from that build ?
v123 : http://cds.w5v8t3u9.hwcdn.net/v123.zip 
v188: http://cds.w5v8t3u9.hwcdn.net/v188.zip
You just need to enable WiFi to FOTA from v123 to v188.

To reproduce that bug today, my Flame stayed power-off in it box for more than 10 days. Huge strange situation ! Maybe something that prevent me to reproduce the bug on 3.2 of comment #18, or many build testing one after other on one phone, prevent at some point to have this bug and that could be why your regression window do not match with the build I used to report this bug.
I still had resolved this by plug-in headphones.

Should I add keyword : regressionwindow-wanted ?

Comment 40

[Shally Li（leave from Mozilla）]

(In reply to Nicolas Mandil (:NicolasWeb) from comment #39)
> As said, I already had this bug in v2.0, but I can't set the affected flag :
> can you do it please ?
> 
> I noticed in your previous comment that to report v2.0 unaffected, (it seems
> to me that) you didn't checked build 20141016183911, that is the one with I
> reproduced this bug on v2.0 (that is v188 on MDN)

Hi Nicolas,

    There is no build 20141016183911 in our side,and I can't do FOTA,but according to Comment 39, mark v2.0 as affected.

Thank you for your kindly reply.

Comment 41

[Nicolas Mandil (:NicolasWeb)]

Requesting addition to UX-Most-Wanted and blocking 2.2 as this sound wired for users.

Comment 42

[Stephany Wilkes]

Not a UX issue if it relates to firmware, as we can't control that. But yes, sound should work, and the 2.2? nomination makes sense, especially since this is probably a regression.

Comment 43

[Nicolas Mandil (:NicolasWeb)]

Not sure if that is related to Gonk/Gecko/... : changing Firmware to OS in summary
(you can check comment #19,comment #31, comment #33 to know more)

Comment 44

[bhavana bajaj [:bajaj]]

blocking as this is a regression and NI'ing bobby chein(EPM audio channel?) to move this along.

Comment 45

[Alastor Wu [:alwu]]

Hi, all,
Is the primary problem of this issue no preview ringtone?
If so, I am working to fix it now in Bug 1107534.

Comment 46

[Nicolas Mandil (:NicolasWeb)]

Hi Alastor,
The primary issue of this bug is no sound at all by the speaker.
So Bug 1107534 is a Sub-bug

Comment 47

[Pi Wei Cheng [:piwei] (inactive)]

1) We cannot do regression windows on OTA issues because we cannot control which build it OTA's to - if this really is related to OTA.

2) There is no point finding a window using steps at comment 25 because it'll just point to the same window as bug 1107534 comment 3. Note that the window provided at comment 33 is found in Central, if we narrow down the window in inbound it'll be the same as 1107534.

3) Comment 39 mentions build ID 20141016183911 but I cannot locate this build anywhere within the pvt server or in our own inventory of builds, so I shallow flashed a tinderbox build 20141016184643 (v2.0) on top of v188 base and I cannot reproduce this issue before or after factory resetting the phone. In this environment I also tried comment 0's steps without the last step (OTA) and I cannot reproduce the bug.

Removing window-wanted tag due to our inability to reproduce this bug. NI Naoki to further investigate.

Comment 48

[Bobby Chien]

[Blocking Requested - why for this release]:

(In reply to bhavana bajaj [:bajaj] from comment #44)
> blocking as this is a regression and NI'ing bobby chein(EPM audio channel?)
> to move this along.

As discussion with Alastor, we can't reproduce this in our development phone. There is no evident info shows this bug as blocker so far. I will unblock this bug. Alastor will continue work on bug 1107534 to see any problem after bug fix.

please nominate this if bug is reproducible.

Comment 49

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I can still reproduce comment 25.  From the sounds of the reporter it should be listed separately.  Filing separate bug.

Comment 50

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Oh never mind.  bug 1107534 is filed and is a blocker.

Comment 51

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

So I installed v188 and then checked for updates, and don't see any.  I'm not sure how you are FOTAing.
It doesn't quite make sense to me.

I am thinking that this might be a duplicate of bug 1107534.

Comment 52

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

To note, I found some bugs that were interesting that may be related to the underlying issue and it's quite possible that it's a gonk related issue : 

Here are the list of bugs: bug 1107534 -> bug 1139157 -> https://bugzilla.mozilla.org/show_bug.cgi?id=1147386#c11 -> bug 1150128

Comment 53

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Bobby please see the following bugs I mentioned.  As per comment 50 and comment 52, I think this is a dup of those chains of bugs.

Comment 54

[Bobby Chien]

as comment 51.