1146751 - [Video][Nexus 5] The 3gpp video sent from Nexus 5 via BT or e-mail can't be played or found.

Status: RESOLVED WONTFIX

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

Description

[Hermes Cheng (inactive after July 27, 2015)]

Attachment: video cannot be played.png

Found this bug when verifying bug 1144579.

* Description: when received a 3gpp video file from BT, NFC or e-mail, user cannot play that video after tapping "file received" notification.

* STR:
1. use anther device to send a 3gpp file via BT, NFC, or e-mail
2. use current phone to receive that file
   i. if sent via e-mail, open e-mail to download that attachment
3 [review]. After receiving, tap "file received" notification to play that 3gpp video

* Actual result:
Got a message as attachment saying: "Video cannot be played...format is not supported"

* Expected result:
Video can be played without any error.

* Environment:
Build ID               20150323162503
Gaia Revision          e54c4ed1cc188f70ddf1156534d364005dc45490
Gaia Date              2015-03-23 19:09:26
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/7ba1778d237b
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150323.200543
Firmware Date          Mon Mar 23 20:05:54 EDT 2015
Bootloader             L1TC000118D0

Comment 1

[Hermes Cheng (inactive after July 27, 2015)]

Attachment: 3gpp received from BT.log

Comment 2

[Hermes Cheng (inactive after July 27, 2015)]

Attachment: 3gpp downloaded from email.log

W/Video   ( 7489): [JavaScript Warning: "Media resource blob:app://video.gaiamobile.org/4e7c7c2e-5324-4eaf-8076-f659ec0382d3 could not be decoded." {file: "app://video.gaiamobile.org/view.html" line: 0}]

Comment 3

[Hema Koka [:hema]]

Can you check this out, Russ? Probably similar to the other bug that you fixed.

Comment 4

[Russ Nicoletti [:russn]]

Hermes, can you play the video in the video app? 

I suspect the problem is with gecko decoding the video which would be unrelated to whether it is an attachment or transferred via bluetooth.

Comment 5

[Hermes Cheng (inactive after July 27, 2015)]

(In reply to Russ Nicoletti [:russn] from comment #4)
> Hermes, can you play the video in the video app? 
No, I can't. I even cannot find that file in Video app.
> 
> I suspect the problem is with gecko decoding the video which would be
> unrelated to whether it is an attachment or transferred via bluetooth.

I found this bug is Nexus 5 specific bug. If the 3gpp is recorded by flame, it is ok.

* The updated STR: (Nexus5 -> Flame)
1. use Nexus 5 to record a video. (3gpp video)
2. sent the video at step 1 to another device via BT(Flame, in my test)
3. After receiving, tap "file received" notification to play that 3gpp video

After step 3, the 3gpp file cannot be played, and also cannot be found at video app.

Comment 6

[Russ Nicoletti [:russn]]

The problem appears to be more basic than the updated bug summary suggests. The problem appears to be 3gpp videos taken with Nexus5 device cannot be decoded.

Chris, can you take a look at this bug (and update the product/component based on what you find)? Thanks.

Comment 7

[Chris Pearce [:cpearce (Not reading bugmail)]]

Steven Lee, is someone on your team available to look into this?

Comment 8

[StevenLee[:slee]]

Attachment: video recorded by nexus 5

Hi Blake.

This is what I recorded from nexus 5-L. I cannot play it on flame, either. Here is the information I dumped from ffmpeg.

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'VID_0001.3gp':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2015-03-31 15:53:50
  Duration: 00:00:01.41, start: 0.000000, bitrate: 18874 kb/s
    Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 1920x1080, 16414 kb/s, SAR 1:1 DAR 16:9, 29.61 fps, 29.75 tbr, 90k tbn, 180k tbc (default)
    Metadata:
      rotate          : 90
      creation_time   : 2015-03-31 15:53:50
      handler_name    : VideoHandle
    Side data:
      displaymatrix: rotation of -90.00 degrees
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 97 kb/s (default)
    Metadata:
      creation_time   : 2015-03-31 15:53:50
      handler_name    : SoundHandle

Comment 9

[Blake Wu [:bwu][:blakewu]]

Thanks for your info. 
(In reply to StevenLee[:slee] from comment #8)
> Created attachment 8585936 [details]
> video recorded by nexus 5
> 
> Hi Blake.
> 
> This is what I recorded from nexus 5-L. I cannot play it on flame, either.
> Here is the information I dumped from ffmpeg.
> 
> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'VID_0001.3gp':
>   Metadata:
>     major_brand     : mp42
>     minor_version   : 0
>     compatible_brands: isommp42
>     creation_time   : 2015-03-31 15:53:50
>   Duration: 00:00:01.41, start: 0.000000, bitrate: 18874 kb/s
>     Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p,
> 1920x1080, 16414 kb/s, SAR 1:1 DAR 16:9, 29.61 fps, 29.75 tbr, 90k tbn, 180k
I think the root cause of this problem is the resolution, 1920x1080, is not supported on Flame[1].

[1]https://dxr.mozilla.org/mozilla-central/source/dom/media/omx/OMXCodecProxy.cpp#181

Comment 10

[StevenLee[:slee]]

(In reply to Blake Wu [:bwu][:blakewu] from comment #9)
> > 1920x1080, 16414 kb/s, SAR 1:1 DAR 16:9, 29.61 fps, 29.75 tbr, 90k tbn, 180k
> I think the root cause of this problem is the resolution, 1920x1080, is not
> supported on Flame[1].
Resolve as WONTFIX since flame doesn't support this resolution.

Comment 11

[Hermes Cheng (inactive after July 27, 2015)]

It is possible that users download such kind of video files to their flame.
Is it possible to tell user that the resolution is not supported?

Comment 12

[Blake Wu [:bwu][:blakewu]]

(In reply to Hermes Cheng[:hermescheng] from comment #11)
> It is possible that users download such kind of video files to their flame.
> Is it possible to tell user that the resolution is not supported?
For a better user experience, it would be better to show user something informative that user can know a received or pushed file exists but not supported. 
I heard about this feature before, but don't know why it is not implemented. 
Russ, 
Do you know about it?

Comment 13

[Russ Nicoletti [:russn]]

I have heard of such a feature. There is some discussion in bug 823588. IIRC there is another bug but unfortunately, I can't locate it. David (djf) may recall more about this feature.