Closed Bug 897354 Opened 11 years ago Closed 6 years ago

[FM] : When user gets a incoming call notification, user is still be able to connect to FM app

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: leo.bugzilla.gaia, Unassigned)

References

Details

(Whiteboard: [AUDIO_COMPETING] [UX_TRIAGED][priority])

1. Title: When user gets a incoming call notification, User is still able to connect to FM app
2. Precondition: connect Wired headset to the device
3. Tester's Action: 
		1. Recieve a incoming call notification
		2. when the device rings, press home button key 
		3. Open FM app
		4. FM app opens , but no sound from FM(Phone keeps ringing/vibrating)
4. Detailed Symptom (ENG.): In case of incoming call notification, user still able to open FM app
5. Expected : 
6. Reproducibility: Y
1)Frequency Rate : 100%
7.Gaia Master/v1-train : Reproduced
8.Gaia Revision:
Also i would like to add some more points, 

1. The same behaviour is seen even in music/video 
2. After receiving the call also, user is able to access FM (No Sound from FM )
Flags: needinfo?(dkuo)
Leo, please see bug 894272 comment 1, which I described before to explain why this should be expected for music/video, and my result is different from yours in comment 1, I can hear music after I answer the call.

And for FM, looks like we cannot hear the sound before/after answering the call, this is probably a restriction because FM doesn't use audio/video elements, it used mozFMRadio api so the priority of the audio channel is already managed.

I am not sure what's the latest policy of the audio channel, myabe we can needinfo Alive or Marco for more information.

Alive/Marco, can you explain the current policy of the audio channel on FM app?
Depends on: 894272
Flags: needinfo?(dkuo) → needinfo?(mchen)
Flags: needinfo?(alive)
Why do we need to block the user from opening any app?

FM, in audio policy, should have the same behavior like any content playing/music app.
Flags: needinfo?(alive)
Whiteboard: [AUDIO_COMPETING]
Just heard from Alive that Randy should have some idea about the audio policy on FM.
Flags: needinfo?(mchen) → needinfo?(rlin)
Also needinfo Casey to help to give some inputs here.
Flags: needinfo?(kyee)
Update to the right UX, Rob, can you help to comment on this? thanks.
Flags: needinfo?(kyee) → needinfo?(rmacdonald)
Hi all,

One policy of audiochannel is that the foreground app is always allowed to play so FM app can be opened and play broadcast. This align to all of other apps.

From technical view, in order to listen the stream from FM Chip the AUDIO_DEVICE_OUT_FM should be set. But audio policy will ignore it when phone state is alert or in_call, this caused that even FM app is allowed to play but there is no sound because the Audio HAL limited the routing path to AUDIO_DEVICE_OUT_FM.

So I think from SW perspective of view this behavior is correct but the wrong result (no FM audio) is caused by platform/HW limitation.
Flagging Sri just in case there's any product work that may be relevant here.
Flags: needinfo?(skasetti)
I think there is no FM + voice downlink audio patch right now. I suggest the UI should block the opening FM radio in phone call.
Flags: needinfo?(rlin)
Does iOS or android block the user from 'opening' FM app during phone call?
For ringtone + FM case, android phone would block user to switch to FM radio(keep UI in the incoming call screen), iOS doesn't have FM function.
(In reply to Randy Lin [:rlin] from comment #11)
> For ringtone + FM case, android phone would block user to switch to FM
> radio(keep UI in the incoming call screen), iOS doesn't have FM function.

Randy, Is this because of your comment 9? Is the voice downlink audio patch being tracked by another bug?
(In reply to Sri Kasetti from comment #12)
> (In reply to Randy Lin [:rlin] from comment #11)
> > For ringtone + FM case, android phone would block user to switch to FM
> > radio(keep UI in the incoming call screen), iOS doesn't have FM function.
> 
> Randy, Is this because of your comment 9? Is the voice downlink audio patch
> being tracked by another bug?

This is device's(HW) limitation. On gecko/gonk side, we can't enable this capacity of FM radio + voice call audio mixing path.
Since this is a HW limitation let's make sure the user experience is better. Rob, as in comment 11 we should block opening the FM radio app in this scenario. Can you comment on this?
Flags: needinfo?(skasetti)
[UX_TRIAGED]

This is an edge case that when incoming call is ringing but the user turns to open some apps instead of answering the call, like FM, Music or Video, we probably will allow FM/Music/Video to play while ringing in the future, but currently this is not a blocker and won't be, since it's a strange scenario. And we believe when the gaia management is enabled in the future, this issue will be considered and fixed.
Flags: needinfo?(rmacdonald)
Whiteboard: [AUDIO_COMPETING] → [AUDIO_COMPETING] [UX_TRIAGED]
Whiteboard: [AUDIO_COMPETING] [UX_TRIAGED] → [AUDIO_COMPETING] [UX_TRIAGED][priority]
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.