When sharing the video by the SMS while playing the video, it will remain the voice of video flows. Then, voice only flows back

NEW
Unassigned

Status

Firefox OS
Gaia::Browser
3 years ago
3 years ago

People

(Reporter: hansu9866, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(blocking-b2g:-, tracking-b2g:backlog, b2g-v2.1 affected, b2g-v2.2 affected)

Details

(Whiteboard: TD505)

(Reporter)

Description

3 years ago
[Detail] 
Tap the share icon while playing the video, then, if you select SMS / Email, voice continues to flow. 
In addition, tap the [discard] about creating a Message and return to the video playback screen, then only the audio is played 


[Preparations] 
None 

[Steps to Reproduce] 
1. Tap [Youtube] icon on Home screen. 
2. Play any video. 
3. Tap the share icon, then tap the [SMS] icon. 
4. Tap [×] icon at the upper left on ""Create New Message"", then tap the [Discard]. 

[Results] 
Voice continues to flow in the SMS screen. 
Voice only be played When you return to the video playback screen. 

[Expected Results] 
Voice does not flow in the SMS screen. 
Video and audio flows back to the video playback screen. 

[Recovery procedure] 
Recover when you play the same video new. 

[Demerit to a user] 
Disadvantage for user would be middle because of functionla problem. 

[Note] 
v2.2:Reproduced
(Reporter)

Updated

3 years ago
blocking-b2g: --- → 2.2?
Flags: needinfo?(wchang)
(Reporter)

Updated

3 years ago
Whiteboard: TD505
(Reporter)

Updated

3 years ago
Flags: needinfo?(ryang)
Hi Hansu, 

not sure why this bug is on 2.2?  are you sure about this ?

Did you also test on Madai 2.0 and Flame 2.0? 
and Please provide the details of its log and device information otherwise we couldn't move forward.

Thank you very much!
Flags: needinfo?(ryang) → needinfo?(hansu9866)
(Reporter)

Comment 2

3 years ago
Hi Rachelle Yang, 

> not sure why this bug is on 2.2?  are you sure about this ?
> I change blocking-b2g:2.2 to 2.0, during first test, i use nexus4 v2.2

> Did you also test on Madai 2.0 and Flame 2.0? 
> yes, two devices are reproduce. and I have local builds.

git commit information is below.

> Flame 2.0 
> gecko: 8aa6a54001a97eff2cde8c5a3e14e7ebe88199c3
  gaia: 31a49c7932c7085961760a6bef9ed381ea38d7e3

> Nexus 2.2
> gecko: a310d15a38b57c2150caabf94715872b33ab53d9
> gaia: 931d547dbd2f4664b6a3c1ff5e4244bca52f96ad
blocking-b2g: 2.2? → 2.0?
Flags: needinfo?(hansu9866)
(Reporter)

Updated

3 years ago
Flags: needinfo?(ryang)
Hi Steve, 

Could you please kindly help look into this issue ?

Thank you very much!
Flags: needinfo?(ryang) → needinfo?(schung)
This part is not controlled by message/email or any callee activity, the video element play/resume is controlled by system/platform side, and video will play while window is in foreground and pause in background. The problem is even the youtube app is covered by activity window, window management still treat it as foreground, so the video will still play at this moment. Ni? Alive about the window management and video element control, but I think it's known issue for a long time.
Flags: needinfo?(schung) → needinfo?(alive)
Keywords: qawanted

Updated

3 years ago
Keywords: qawanted
Hi Steven and Alive, thanks for your time.

So based on your comments,  May I know this is the current design on FFOX 2.0 ?

any plan for changing this will be made on 2.1 or 2.2 ?

Thanks!
Flags: needinfo?(schung)
Flags: needinfo?(alive)
Hi Mike, Would you please help check if this scenario also happens on 2.1 and master ?
Flags: needinfo?(mlien)
Keywords: qawanted
(In reply to Rachelle Yang [:ryang][ryang@mozilla.com] from comment #6)
> Hi Steven and Alive, thanks for your time.
> 
> So based on your comments,  May I know this is the current design on FFOX
> 2.0 ?
> 
> any plan for changing this will be made on 2.1 or 2.2 ?
> 
> Thanks!

The root cause is the platform process priority issue and nobody is actively working on that;
hence no plan could be made.
Flags: needinfo?(alive)
Clear ni since Alive already replied in comment 8
Flags: needinfo?(schung)
(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #8)
> (In reply to Rachelle Yang [:ryang][ryang@mozilla.com] from comment #6)
> > Hi Steven and Alive, thanks for your time.
> > 
> > So based on your comments,  May I know this is the current design on FFOX
> > 2.0 ?
> > 
> > any plan for changing this will be made on 2.1 or 2.2 ?
> > 
> > Thanks!
> 
> The root cause is the platform process priority issue and nobody is actively
> working on that;
> hence no plan could be made.

Correct: it seems https://bugzilla.mozilla.org/show_bug.cgi?id=994518 is taken by Gabriele and it's blocking bug 892371

Comment 11

3 years ago
wait for qawanted v2.1 & master results
Flags: needinfo?(mlien)
Since there are two ways to access Youtube, (web/app) I'm posting results for both of these because they behave differently.

Using Flame build 2.2 KK
Youtube Web - Bug does NOT exist. Video and Audio cease when share button is tapped.

Youtube App - Bug DOES exist but only the audio playing in SMS. Once the sms is discarded, video continues to play and video is seen and audio is heard.

Tested with Shallow Flash on 319mb using Engineering builds
Environmental Variables:
Device: Flame 2.2 KK
BuildID: 20141030042717
Gaia: cddf7f505c4c280bacb74c22af3fa4959ccb555a
Gecko: 46cab998bd31
Version: 36.0a1 (2.2) 
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

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

Using Flame build 2.1 KK
Youtube Web - Bug DOES exist but only the audio playing in SMS. Once the sms is discarded, video continues to play and video is seen and audio is heard.

Youtube App - Bug DOES exist but only the audio playing in SMS. Once the sms is discarded, video continues to play and video is seen and audio is heard.

Tested with Shallow Flash on 319mb using Engineering builds
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141030033816
Gaia: dabe2aea8bfc3e4a989b63d2711accd0e31c2d39
Gecko: 810a4fb6911a
Version: 34.0 (2.1) 
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1: --- → affected
status-b2g-v2.2: --- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: croesch
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
[Blocking Requested - why for this release]:
might involve lots of modifications. push to 2.1 ?
blocking-b2g: 2.0? → 2.1?
[Tracking Requested - why for this release]:

(In reply to Rachelle Yang [:ryang][ryang@mozilla.com] from comment #13)
> [Blocking Requested - why for this release]:
> might involve lots of modifications. push to 2.1 ?

Not a recent regression or a use case that would block ship the release. Also there is a a way to recover from this by re-playing, so not a ship blocker.
blocking-b2g: 2.1? → -
tracking-b2g: --- → ?

Updated

3 years ago
Flags: needinfo?(wchang)
You need to log in before you can comment on or make changes to this bug.