919372 - [B2G][Helix][Audio][tianhuajian]The ringtone has two sounds in lock screen state

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect, P1)

Description

[lecky]

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba)

Steps to reproduce:

A is FFOS phone , B is another phone
1. A in lock screen mode
2. B call A
3. A connect the phone for about 15s
4. A disconnect the phone
5. B call A again




Actual results:

5. Then ringtone in A has two songs.

【Test Count*】：5
【Found Count*】：4
【Gaia commit ID*】: V1.1HD
【Gecko commit ID*】:  1.1.0 HD
【Log*】：The ddms log
【Network environment】：UMTS
【Resume operation】： 





Expected results:

5. The ringtone in A has one song

Comment 1

[lecky]

Attachment: rx_record.part1.rar

Comment 2

[lecky]

Attachment: rx_record.part2.rar

Comment 3

[lecky]

Attachment: rx_record.part3.rar

Comment 4

[lecky]

Attachment: rx_record.part4.rar

Comment 5

[lecky]

I have captured the pcm data in audio hal layer, the data has two audio sound.
So I think this problem is gecko issue.

Comment 6

[Wayne Chang [:wchang]]

QAWANTED to test this, reported as high occurrence (4/5).

Setting leo? for the description, if QA test results do not consider this blocking, please de-nom.

Comment 7

[Jason Smith [:jsmith]]

More details on QA Wanted:

* Does this reproduce on 1.01?
* Does this reproduce on 1.1 leo devices?

Comment 8

[lecky]

 Our test version is V1.1HD， and does not know whether it is can be reproduced on other version.
(In reply to Jason Smith [:jsmith] from comment #7)
> More details on QA Wanted:

* Does this reproduce on 1.01?
* Does this
> reproduce on 1.1 leo devices?

Comment 9

[William Hsu [:whsu]]

Hi, all,

I cannot reproduce this case on following Mozilla build and partner build.

* Test Build:
 + Vendor Build:
  - Gaia:     2a20910ea96efb538ec0c99ff25a540ed641f63f
  - Gecko:   
  - BuildID   20130923135853
  - Version   18.0
  ===> Result: Cannot reproduce

 + Mozilla Build:
  - Gaia:     2a20910ea96efb538ec0c99ff25a540ed641f63f
  - Gecko:    http://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/d4984697d456
  - BuildID   20130926042205
  - Version   18.0
  ===> Result: Cannot reproduce


--------- Removing QAwanted ---------

Comment 10

[lecky]

Hi William,
Can you help me test the issue by the following steps, the difference from before is extended the call time and B disconnect the phone , I find the issue can be reproduced  by the following steps every time.

A is FFOS phone , B is another phone
1. A in lock screen mode
2. B call A
3. A connect the phone for about 30s
4. B disconnect the phone
5. B call A again




(In reply to William Hsu [:whsu] from comment #9)
> Hi, all,

I cannot reproduce this case on following Mozilla build and
> partner build.

* Test Build:
 + Vendor Build:
  - Gaia:    
> 2a20910ea96efb538ec0c99ff25a540ed641f63f
  - Gecko:   
  - BuildID  
> 20130923135853
  - Version   18.0
  ===> Result: Cannot reproduce

 +
> Mozilla Build:
  - Gaia:     2a20910ea96efb538ec0c99ff25a540ed641f63f
  -
> Gecko:   
> http://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/d4984697d456
  -
> BuildID   20130926042205
  - Version   18.0
  ===> Result: Cannot reproduce
> --------- Removing QAwanted ---------

Comment 11

[lecky]

When in the test, there are the following attentions：
1. Once the Phone A has connected , do not touch it , and disconnect the call by phone B
2. The call time between A and B should be more than 10s

Comment 12

[William Hsu [:whsu]]

Hi, Lecky,

So weird.
I can reproduce this case on Mozilla build now.
Thanks for your help. ^^

* Test Build (Mozilla Build)
  - Build ID: 20130927042200

Changing the status to "NEW".

--------------------------------------------------------------------
Hi, Wayne,

Could I have your help?
We need to assign a developer to help on this case since it happened on Mozilla Build.
Thank you.

Comment 13

[Wayne Chang [:wchang]]

Hi William,

Thanks for the update, can you also check Jason's comments on other devices?

(In reply to Jason Smith [:jsmith] from comment #7)
> More details on QA Wanted:
> 
> * Does this reproduce on 1.01?
> * Does this reproduce on 1.1 leo devices?

Also given the specifics required for this to occur, unless this is a regression (not happening on 1.0.1 and other 1.1 devices), this should not block.


Also NI?Marco, if you or someone has some time, please check this with a head start.

Comment 14

[William Hsu [:whsu]]

Hi, Wayne and Jason,

As I tested this bug on v1.0.1, V1.1, and V1.3, I cannot reproduce this case on V1.3 build but I can reproduce this case on V1.0.1 and V1.1 build.
This is a legacy bug of Mozilla Build.

* Test Build:
  + Unagi: (V1.0.1)
   - Gaia:     f000719da5116eca00b78aa8121f38264d3dafee
   - Gecko:    http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/9c62297d11b0
   - BuildID   20130703230201
   - Version   18.0
   ===> Result: Can reproduce

  + LEO: (V1.1.0)
   - Gaia:  02b975e6ce12922928c74276ac7d19432a03f126
   - Gecko: c630289d6388
   - BuildID: 20130929041201
   - Version: 18.0
   ===> Result: Can reproduce
  
  + Hamachi (v1.3)
   - Gaia:     1992915b07cd9d959b26ae0fd0f6d7e549879d72
   - Gecko:    http://hg.mozilla.org/mozilla-central/rev/e56505c62aba
   - BuildID   20130929040201
   - Version   27.0a1
   ===> Result: Cannot reproduce
 

Many thanks!

Comment 15

[lecky]

Hi Wayne,
Since this issue is a legacy bug of Mozilla Build, Can you give us a patch on our build.
For this issue can seriously affect user experience, we hope we can get the patch to test as soon as possible.
Thanks
 (In reply to Wayne Chang [:wchang] from comment #13)
> Hi William,

Thanks for the update, can you also check Jason's comments on
> other devices?

(In reply to Jason Smith [:jsmith] from comment #7)
> More
> details on QA Wanted:
> 
> * Does this reproduce on 1.01?
> * Does this
> reproduce on 1.1 leo devices?

Also given the specifics required for this to
> occur, unless this is a regression (not happening on 1.0.1 and other 1.1
> devices), this should not block.


Also NI?Marco, if you or someone has some
> time, please check this with a head start.

Comment 16

[Wayne Chang [:wchang]]

Not blocking here since it is consistent across v1.1 and not a regression from v1.0.1. In addition the steps are very specific for this to occur, chances are the users would have touched the phone since it is connected, talking on the phone against their face would trigger p-sensor on/off the device screen as well.


(In reply to lecky from comment #11)
> When in the test, there are the following attentions：
> 1. Once the Phone A has connected , do not touch it , and disconnect the
> call by phone B
> 2. The call time between A and B should be more than 10s

Comment 17

[lecky]

If the user use wired headset or BT headset, this issue will be impact the user more frequently.
So I think this issue is serious.
Since the issue is the legacy bug of Mozilla Build, 
I want to know whether you have analyse this issue, and the fixed plan of this bug?

(In reply to Wayne Chang [:wchang] from comment #16)
> Not blocking here since it is consistent across v1.1 and not a regression
> from v1.0.1. In addition the steps are very specific for this to occur,
> chances are the users would have touched the phone since it is connected,
> talking on the phone against their face would trigger p-sensor on/off the
> device screen as well.


(In reply to lecky from comment #11)
> When in the
> test, there are the following attentions：
> 1. Once the Phone A has
> connected , do not touch it , and disconnect the
> call by phone B
> 2. The
> call time between A and B should be more than 10s

Comment 18

[Wayne Chang [:wchang]]

Again, not seeing this as a blocker.

1. For the bug to happen the called party must not touch the device at all after the call has connected, even lighting up the screen would cause the problem to not happen.
2. It only happens once, when receiving subsequent calls the ringtone is normal.

We're not blocking and not fixing this on v1.1.

Evelyn, can you however have someone check this on Master and v1.2?
Use the STR in comment 10.

Comment 19

[Evelyn Hung]

Ian, can you help test the issue on v1.2 and on master? Thanks!

Comment 20

[lecky]

Hi Beatriz,
This issue is a legacy bug of Mozilla Build, 
Wayne had said it is not a blocker, and will not fixing this on v1.1
So please check whether you accept this result?
Thanks

Comment 21

[[e-mail], [e-mail]]

* Test Build:

  + Hamachi (v1.1hd)
  Gaia:     4afe209fb0d5c0e03d655a4e900ab8f13ca8fb4a
  Gecko:    http://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/7cd7f30328e1
  BuildID   20131021042201
  Version   18.0
  ===> Result: can reproduce

  + Hamachi (v1.2)
  Gaia:     4afe209fb0d5c0e03d655a4e900ab8f13ca8fb4a
  Gecko:    http://hg.mozilla.org/releases/mozilla-aurora/rev/7453a764f9a9
  BuildID   20131022004000
  Version   26.0a2
  ===> Result: Cannot reproduce


  + Hamachi (master)
  Gaia:     4afe209fb0d5c0e03d655a4e900ab8f13ca8fb4a
  Gecko:    http://hg.mozilla.org/mozilla-central/rev/7823e2985daf
  BuildID   20131021040204
  Version   27.0a1
  ===> Result: Cannot verify. (Note: No incoming call! There are some blocking issues on master, since we're developing on the chennal.)

Thanks.

Comment 22

[Beatriz Rodríguez [:brg]]

(In reply to lecky from comment #20)
> Hi Beatriz,
> This issue is a legacy bug of Mozilla Build, 
> Wayne had said it is not a blocker, and will not fixing this on v1.1
> So please check whether you accept this result?
> Thanks
Thanks a lot to Ian and William for your investigation in this issue.
I agree with comment 18 and happy to know you cannot reproduce in v1.2 :-)

Comment 23

[Evelyn Hung]

So can we close this as won't fix on v1.1?

Comment 24

[Wayne Chang [:wchang]]

Yes lets do that.
Reopen/file a new bug if this is detected on master.

If anything feels otherwise, please reopen comment here. Thanks.

Comment 25

[lecky]

Hi Wayne,
After discussion We still think this issue will affect user experience seriously .
Although this issue can not be reproduced on V1.2, Can you analyse and give us the patch on V1.1hd.
Thanks.

Comment 26

[Wayne Chang [:wchang]]

We decided not to spend time on this for v1.1 given the uncommon occurrence, it also happens only once when hit and recovers itself after.

Feel free to investigate on v1.1 but at current we do not have resources to continue here.