1015520 - [ringtones] Ringtone preview shouldn't use the "ringtone" audio channel

Status: RESOLVED WONTFIX

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

Description

[Jim Porter (:squib)]

Right now, we set the ringtone preview in the picker to play the sound using the "ringtone" audio channel. However, this is bad, since it could block out an actual incoming call.

Still, we need a way to set the priority so that other audio is muted. Ideas?

Comment 1

[Tiffanie Shakespeare [:tif]]

Ya - totally agree. The preview should be de-prioritzied to let incoming calls override. Perhaps use the music channel?

Omega - have you thought about this one?

Comment 2

[Omega Feng [:Omega] [:馮於懋]]

ni? new UX owner Jenny.

Comment 3

[Jenny Lee]

> Ya - totally agree. The preview should be de-prioritzied to let incoming
> calls override. Perhaps use the music channel?

Hello Tiffanie, it makes more sense that ringtone preview and incoming call use the same channel as they are both ringers. However, when there's a call incoming while previewing ringtone, the incoming call should interrupt and stop ringtone preview from playing immediately. At this moment, user will focus on the attention screen brought up by the incoming call. After the call ends, ringtone preview will then resume. Thanks!

Comment 4

[bhavana bajaj [:bajaj]]

(In reply to Jim Porter (:squib) from comment #0)
> Right now, we set the ringtone preview in the picker to play the sound using
> the "ringtone" audio channel. However, this is bad, since it could block out
> an actual incoming call.
> 
> Still, we need a way to set the priority so that other audio is muted. Ideas?

Is this suppressing the call completely and we get no indication, which is when I would block on. But otherwise if you re in ringtones and just the current tone is not audible not sure if this would be a blocker, can you help understand ?

Comment 5

[Marcia Knous [:marcia]]

We should do some more exploratory testing of this during the bug bash tomorrow and try to nail down exactly what happens - once that is the clarified it will be easier for the triage team to make a call.

Comment 6

[Kate Glazko]

Ok, took some steps to reproduce this today. Here's what happened:
1.) Go to Ring Tones in Settings, and click on a ring tone. Let it play.
2.) From a different device, call your phone.
3.) The GUI will appear for the call, but for about 3 seconds, the ringtone you were playing with in step 1 will continue playing on top of your actual ring tone.

Comment 7

[bhavana bajaj [:bajaj]]

(In reply to kglazko from comment #6)
> Ok, took some steps to reproduce this today. Here's what happened:
> 1.) Go to Ring Tones in Settings, and click on a ring tone. Let it play.
> 2.) From a different device, call your phone.
> 3.) The GUI will appear for the call, but for about 3 seconds, the ringtone
> you were playing with in step 1 will continue playing on top of your actual
> ring tone.

i saw this bug along with Kate, we did see the incoming call while we were selecting the ring tone , not something I would block a release for.

Comment 8

[Tiffanie Shakespeare [:tif]]

I see your point and I totally agree - however, for those users who are visually impaired they may not be able to notice the incoming call without the additional sound feedback.

I've NI'd someone from the accessibility team to add their comments as to the degree of impact and whether they think it should be nominated as a blocker or not.

(In reply to bhavana bajaj [:bajaj] from comment #7)
> (In reply to kglazko from comment #6)
> > Ok, took some steps to reproduce this today. Here's what happened:
> > 1.) Go to Ring Tones in Settings, and click on a ring tone. Let it play.
> > 2.) From a different device, call your phone.
> > 3.) The GUI will appear for the call, but for about 3 seconds, the ringtone
> > you were playing with in step 1 will continue playing on top of your actual
> > ring tone.
> 
> i saw this bug along with Kate, we did see the incoming call while we were
> selecting the ring tone , not something I would block a release for.

Comment 9

[David Bolter [:davidb] (NeedInfo me for attention)]

Tiffanie thanks for asking, this is indeed important for VI users. We're targeting b2g 2.1 for actually supporting this user base so I wouldn't block 2.0 here. Thanks again.

Comment 10

[Tiffanie Shakespeare [:tif]]

Thanks David for the quick reply. Totally cool then to remove the nomination for 2.0 blocker if that's what we want to do.

Comment 11

[BMO Automation]

Firefox OS is not being worked on