Getting hardware rendering codec working for Chrome or firefox in playing 1080p hevc videos via HTML5 video tag

[Shihab Soft]

Is there any possible way to achieve that?

I've tried every sort of ROMs like Prime OS, Bliss OS, Phoenix OS, android 7.1 AOSP, 8.1 and the latest 9.0 r2 iso too..

I am trying to play a 1080p hevc video inside the browser, in latest version that is after 8.1 the video controls will be visible and I'll see the video playback progressing, but with black screen.

In android 7.1 (And all other custom ROMs based on it), nope the video refuses to play even after 720 1Mbps and above. All plays fine upto 720p 1Mbps.

I've read about some limitations here

https://developer.android.com/guide/topics/media/media-formats

But the thing is I am able to play the aforementioned videos flawlessly in my oneplus phone in chrome or firefox.

My system

CPU - i5 2430m

4 GB RAM

Lenovo G570

[Shihab Soft]

Adding to this..

I am actually streaming the 1080p media from my Jellyfin server (Media server)

[Chih-Wei Huang]

Shihab Soft <spk...@gmail.com> 於 2020年5月19日 週二 上午1:28寫道：

>
> Adding to this..
>
> I am actually streaming the 1080p media from my Jellyfin server (Media server)

Please collect logcat for analyzing.

Is there a public server that we can test?

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Shihab Soft]

Hey,

These are the relevant errors I've found in the logs once I started playing the media.

2020-05-19 16:31:01.483 1364-12355/? W/Utils: track of type 'audio/mpeg' does not publish channel mask, channel count 2

2020-05-19 16:31:01.485 1364-12355/? W/NuPlayer: source has video meta but not file meta

2020-05-19 16:31:01.486 1364-12355/? W/Utils: track of type 'audio/mpeg' does not publish channel mask, channel count 2

2020-05-19 16:31:01.486 1364-12355/? W/NuPlayer: source has video meta but not file meta

2020-05-19 16:31:01.487 1364-12355/? W/NuPlayer: source has video meta but not file meta

2020-05-19 16:31:01.489 1361-9668/? E/OMXNodeInstance: setConfig(5510040:ffmpeg.mp3.decoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)

2020-05-19 16:31:01.492 1361-9668/? W/OMXNodeInstance: [5510041:ffmpeg.h264.decoder] component does not support metadata mode; using fallback

2020-05-19 16:31:01.492 1364-12391/? E/ACodec: [OMX.ffmpeg.h264.decoder] storeMetaDataInBuffers failed w/ err -1010

2020-05-19 16:31:01.492 1361-9668/? E/OMXNodeInstance: setConfig(5510041:ffmpeg.h264.decoder, ConfigPriority(0x6f800002)) ERROR: UnsupportedIndex(0x8000101a)

2020-05-19 16:31:01.492 1364-12391/? E/ACodec: Wrong cropped rect (0, 0) - (1280, 544) vs. frame (720, 480)

2020-05-19 16:31:01.492 1364-12391/? E/ACodec: [OMX.ffmpeg.h264.decoder] configureCodec returning error -22

2020-05-19 16:31:01.493 1361-9668/? W/OMXNodeInstance: [5510042:google.h264.decoder] component does not support metadata mode; using fallback

2020-05-19 16:31:01.493 1364-12391/? E/ACodec: [OMX.google.h264.decoder] storeMetaDataInBuffers failed w/ err -1010

2020-05-19 16:31:01.494 1361-9668/? E/OMXNodeInstance: setConfig(5510042:google.h264.decoder, ConfigPriority(0x6f800002)) ERROR: UnsupportedIndex(0x8000101a)

2020-05-19 16:31:01.494 1364-12391/? E/ACodec: Wrong cropped rect (0, 0) - (1280, 544) vs. frame (720, 480)

2020-05-19 16:31:01.494 1364-12391/? E/ACodec: signalError(omxError 0xffffffea, internalError -22)

2020-05-19 16:31:01.494 1364-12390/? E/MediaCodec: Codec reported err 0xffffffea, actionCode 0, while in state 3

2020-05-19 16:31:01.495 1364-12389/? E/MediaCodec: configure failed with err 0xffffffea, resetting...

2020-05-19 16:31:01.496 1364-12389/? E/NuPlayerDecoder: Failed to configure OMX.ffmpeg.h264.decoder decoder (err=-22)

2020-05-19 16:31:01.496 1364-12355/? E/NuPlayer: received error(0xffffffea) from video decoder, flushing(1), now shutting down

2020-05-19 16:31:01.496 4363-5538/com.shihabsoft.jellyfinshihabwebview E/MediaPlayer: error (1, -22)

2020-05-19 16:31:01.496 4363-4363/com.shihabsoft.jellyfinshihabwebview E/MediaPlayer: Error (1,-22)

2020-05-19 16:31:01.496 1364-12355/? W/AMessage: failed to post message as target looper for handler 0 is gone.

2020-05-19 16:31:01.497 4363-4363/com.shihabsoft.jellyfinshihabwebview E/chromium: [ERROR:media_player_renderer.cc(277)] OnError Error: 0

2020-05-19 16:31:01.500 4363-5297/com.shihabsoft.jellyfinshihabwebview E/chromium: [ERROR:batching_media_log.cc(35)] MediaEvent: {"pipeline_error":3}

Btw, as you can see in the logs, it's my own software I've used a webview which latest Chrome Stable offers. This issue is the same with chrome or firefox. I get the same errors.

You can try to play a 1080p video in the demo server Jellyfin provided.

https://demo.jellyfin.org/stable/web/index.html#!/itemdetails.html?id=c541e7545e58b28cd4d0da7aac89d7e8&serverId=713dc3fe952b438fa70ed35e4ef0525a

Username - demo, password - <empty>

Once logged in, re-paste that URL again and load the page, it will lead you to a 1080p h264 video which you can play and troubleshoot.

[Michael Goffioul]

FWIW, it's working fine on my hardware/build. I'm using an Android Q build, with a custom browser-like app that is using WebView from Android System WebView (equivalent to Chrome/80).

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/4b04eb0c-1a1c-40f7-9fc8-2f67b543798a%40googlegroups.com.

[Shihab Soft]

Interesting.

I haven't tried out Android Q yet.. Not sure if something has improved in it.

The same hardware seems to perfectly play the stream in my Lubuntu 18.04 OS. But just not in any Android I've tried so far in my list in the first post.

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

[Shihab Soft]

Oh a quick update.

The link I provided is also playing fine in my setup too. I thought all 1080p streams are not working properly..

Turns out it's just 1080p Hevc, 1080p h264 seems to stream perfectly fine.

So yes my issue still persists, and something's wrong with the playback of 1080p Hevc streams.. To pinpoint any quality above 720p 1Mbps fails.

[Michael Goffioul]

It doesn't look like HEVC in the browser is widely supported: https://caniuse.com/#feat=hevc

Are you positive that for lower resolution, the browser is actually playing HEVC and didn't fall back to some other format?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/922cbd00-5179-4e42-b541-6a351e5d51bb%40googlegroups.com.

[Shihab Soft]

Yes of course I am damn sure about that.

A quality next to 1Mbps which is 1.5Mbps won't work. Only max upto 720p 1Mbps.

Also as I stated before, Chrome on my Lubuntu OS with the same hardware can perfectly stream it. The same with firefox too.

Also in my OnePlus device I can perfectly see the video in my chrome browser too..

[Michael Goffioul]

It would be better if you could provide a way to reproduce the problem.

I was just asking, because I can't find a reference where it says Chrome does support HEVC. E.g. I also found this bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=684382

I also tried the 2 HEVC test streams here and none works on my Chrome desktop (Chrome/81 on Fedora 31), only audio: https://tools.woolyss.com/html5-audio-video-tester/

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/c9f5e61b-766e-4b91-bcb3-dcd6eea6905f%40googlegroups.com.

[Shihab Soft]

Is the logcat posted any helpful?

On Tuesday, May 19, 2020 at 9:25:02 AM UTC+5:30, Chih-Wei Huang wrote:

[Michael Goffioul]

It shows there's an error during codec initialization, alright. It also shows that you're trying to play H264, not HEVC. And it shows it's trying first the FFMPEG based codec, then the Google codec, both failing the same way. So whatever the problem is, it's not specific to Android-x86's use of FFMPEG codecs. Without a way to reproduce the problem, it'll be hard to investigate it.

--

You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/4a851a41-2ac2-4b1b-8407-8266b56ddce5%40googlegroups.com.

[Shihab Soft]

Okay I can create an account and give you access to my media server in private. Okay to send a PM?

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

[Michael Goffioul]

Sure, I can at least give it a try from here.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/fcdc4439-a855-49c3-a61b-9389224db487%40googlegroups.com.

[Shihab Soft]

Okay I've sent the creds privately.

You can test out the only movie there.

For me any resolution above 720p 1Mbps doesn't work in Android x86 in chrome or firefox.

But the same can be played in any resolution, that is even 1080p 60 Mbps with the same hardware in Lubuntu OS.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/fcdc4439-a855-49c3-a61b-9389224db487%40googlegroups.com.

[Michael Goffioul]

I'll have a look. First thing I notice when playing it in my Chrome desktop, is that it's H264, not HEVC. As you kept mentioning HEVC, I'm wondering whether that's expected.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/b333ff59-00d5-4464-8698-2aec02acecc0%40googlegroups.com.

[Michael Goffioul]

I also tried on my Baytrail hardware (running Android Q), and it also worked fine. The video is still H264 (not HEVC), codec is FFMPEG (with VA-API hw accel), and I can play 1080p/60Mbps without any problem. I also switched to 720p/1Mbps, then back to 1080p/60Mbps. No problem.

[Shihab Soft]

Yes may be it was a confusion. Actually that video is a 1080p Hevc encoded. That's why I said Hevc, but the server seems to send transcoded h264.
But anyways, unfortunately it's not working for me.

Max I could get is 720p 1Mbps.

My specs

i5 2430m processor

[Shihab Soft]

Also I was wondering. If you could possibly try the same on latest Android Pie release? I haven't tried Android Q yet. So I can't comment on that.

[Michael Goffioul]

Do you see some HWACCEL log entries in logcat when playing at 720p?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/6f7d02b7-7e32-4f8b-ac46-7f4d13bd2121%40googlegroups.com.

[Shihab Soft]

I'll have to check. Let me see...

[Shihab Soft]

Yes I see this

2020-05-20 21:24:17.048 1372-4911/? I/HWACCEL: hw codec h264 enabled: s=0xf4e65000 ist=0xf45d4000 pix_fmts=53

On Wednesday, May 20, 2020 at 9:09:26 PM UTC+5:30, Michael Goffioul wrote:

Do you see some HWACCEL log entries in logcat when playing at 720p?

On Wed, May 20, 2020 at 11:35 AM Shihab Soft <spk...@gmail.com> wrote:

Yes may be it was a confusion. Actually that video is a 1080p Hevc encoded. That's why I said Hevc, but the server seems to send transcoded h264.
But anyways, unfortunately it's not working for me.

Max I could get is 720p 1Mbps.

My specs

i5 2430m processor

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

[Michael Goffioul]

Ok, that means at least the hw-accel codec can be active. I honestly don't know why it doesn't work on your hardware. For reference, here's the filtered logcat output when playing 1080p/60Mbps on Android-x86 9.0-r2 with Chrome/75 (it works fine):

05-20 11:57:49.130  1497  2210 V FFmpegOMXPlugin: makeComponentInstance 'OMX.ffmpeg.h264.decoder'
05-20 11:57:49.130  1497  2210 D SoftFFmpegVideo: SoftFFmpegVideo component: OMX.ffmpeg.h264.decoder codingType=7 appData: 0xac729a40
05-20 11:57:49.131  1497  2210 D SoftFFmpegVideo: 0xac729900 initDecoder: 0xa8fbbc00
05-20 11:57:49.131  1497  2210 E OMXNodeInstance: setConfig(0xac718060:google.mp3.decoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
05-20 11:57:49.132  1493  7197 I ACodec  : codec does not support config priority (err -2147483648)
05-20 11:57:49.132  1497  2210 E OMXNodeInstance: getConfig(0xac718060:google.mp3.decoder, ConfigAndroidVendorExtension(0x6f100004)) ERROR: Undefined(0x80001001)
05-20 11:57:49.135  1493  7197 I MediaCodec: MediaCodec will operate in async mode
05-20 11:57:49.136  1493  7199 I MediaCodec: [OMX.ffmpeg.h264.decoder] setting surface generation to 1528834
05-20 11:57:49.136  1497  2189 E OMXNodeInstance: getExtensionIndex(0xac718540:ffmpeg.h264.decoder, OMX.google.android.index.enableAndroidNativeBuffers) ERROR: UnsupportedIndex(0x8000101a)
05-20 11:57:49.136  1493  7200 E ACodec  : [OMX.ffmpeg.h264.decoder] setPortMode on output to DynamicANWBuffer failed w/ err -1010
05-20 11:57:49.137  1497  2104 W OMXNodeInstance: [0xac718540:ffmpeg.h264.decoder] component does not support metadata mode; using fallback
05-20 11:57:49.137  1497  2189 I SoftFFmpegVideo: OMX_IndexParamPortDefinition (input) width=1920 height=816
05-20 11:57:49.138  1497  2189 I SoftFFmpegVideo: OMX_IndexParamPortDefinition (output) width=1920 height=816
05-20 11:57:49.138  1497  2189 E OMXNodeInstance: setConfig(0xac718540:ffmpeg.h264.decoder, ConfigPriority(0x6f800002)) ERROR: UnsupportedIndex(0x8000101a)
05-20 11:57:49.139  1493  7200 I ACodec  : codec does not support config priority (err -1010)
05-20 11:57:49.139  1497  2104 E OMXNodeInstance: getConfig(0xac718540:ffmpeg.h264.decoder, ConfigAndroidVendorExtension(0x6f100004)) ERROR: UnsupportedIndex(0x8000101a)
05-20 11:57:49.140  1493  7199 I MediaCodec: MediaCodec will operate in async mode
05-20 11:57:49.167  1497  7203 D SoftFFmpegVideo: ffmpeg got codecconfig buffer
05-20 11:57:49.167  1497  7203 D SoftFFmpegVideo: ffmpeg got codecconfig buffer
05-20 11:57:49.167  1497  7203 D SoftFFmpegVideo: ffmpeg got codecconfig buffer
05-20 11:57:49.168  1497  7203 D SoftFFmpegVideo: ffmpeg got codecconfig buffer
05-20 11:57:51.230  1497  7203 D SoftFFmpegVideo: begin to open ffmpeg decoder(h264) now
05-20 11:57:51.231  1497  7203 D SoftFFmpegVideo: open ffmpeg video decoder(h264) success
05-20 11:57:51.233  1497  7203 I HWACCEL : hw codec h264 enabled: s=0xa8fbbc00 ist=0xa8fe9680 pix_fmts=53
05-20 11:57:51.286  1493  7199 D MediaCodec: [OMX.ffmpeg.h264.decoder] setting dataspace on output surface to #104

Michael.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/319198fc-f8f0-4fdf-9ce6-7a5e5ec3d09e%40googlegroups.com.

[Shihab Soft]

Thanks for the help so far Michael.

Not sure who else can assist here..

@Chih-Wei Huang ?

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/319198fc-f8f0-4fdf-9ce6-7a5e5ec3d09e%40googlegroups.com.

[Michael Goffioul]

As I said, without a way to reproduce the problem, it's gonna be hard to investigate. You're probably the best to do it, if you're willing to build your own Android-x86. 

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/8db9f56d-c391-4cc1-a995-7ef600030fc0%40googlegroups.com.

[Shihab Soft]

Let me know what I could do... I am ready to try out any ISOs too..

Currently it's so annoying now with this issue.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/8db9f56d-c391-4cc1-a995-7ef600030fc0%40googlegroups.com.

[Michael Goffioul]

The error is coming from https://osdn.net/projects/android-x86/scm/git/frameworks-av/blobs/pie-x86/media/libstagefright/ACodec.cpp (line 4972). So you have to work backwards from there. The easiest IMO is to build your own android-x86, deploy it on your device in read-write mode. Then start adding debug lines to the code, recompile the relevant parts, copy them over your device, restart relevant services and test again.

Let's say you make a change in frameworks/av/media/libstagefright/ACodec.cpp, the sequence would more or less be as follows (this is for a 32bits build):

    ./build/soong/soong_ui.bash --make-mode out/target/product/x86/system/lib/libstagefright.so

    adb push out/target/product/x86/system/lib/libstagefright.so /system/lib/libstagefright.so

    adb shell 'kill $(pidof mediaserver)'

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/6ef9e1ec-3c9b-4753-bd51-889874e9d079%40googlegroups.com.

[Shihab Soft]

To be frank, am not even sure where to start. I am not that a savvy when it comes to compiling stuffs and C coding.

But I can try out stuffs like pushing the modified .so libs and testing it out.

Not sure if it's too much, but could you please help out on this? Also I don't have the resources to compile the whole android x86 OS either.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/6ef9e1ec-3c9b-4753-bd51-889874e9d079%40googlegroups.com.

[Michael Goffioul]

I don't think this is gonna work if you cannot compile android-x86 yourself. The next best option is if one of the devs is able to reproduce the problem. If you're ok providing credentials to Chih-Wei and he's ok with it, maybe he can test on his device(s).

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/9acb6870-3600-44a5-b141-0411f702c5f0%40googlegroups.com.

[Shihab Soft]

Also a relevant comment I've found.

https://osdn.net/projects/android-x86/scm/git/frameworks-av/commits/2f1103142fde38b9bdc2514b168d278c0ce08398

[Shihab Soft]

Yeah sure, I can share him the creds.

Also there's a commit link I've posted before, not sure if it's useful.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/9acb6870-3600-44a5-b141-0411f702c5f0%40googlegroups.com.

[Shihab Soft]

Btw, I've decided to compile it on my own, as I've a dedicated server which could do the job easily I guess.

I am currently doing the "repo sync", which is now at around 85%.

What are the next steps, could you please point me somewhere?

Like I saw the instructions on how to build the iso images, but I am just wondering if I can possible just compile that specific .so lib and test it out?

[Shihab Soft]

I just tried it in Qemu in a beafy system. This issue still persists..

Not sure if I could do anything regarding that, that makes it this is not an isolated issue to my device I guess?

[Michael Goffioul]

After the lunch command, I think you should be able to use something like:

./build/soong/soong_ui.bash --make-mode out/target/product/x86/system/lib/libstagefright.so

There are 2 things that may need to be adapted:

- the product name: in the above, it's "x86"

- the library path, in case you're compiling for 64bits: in the above, you might need to use "lib64" instead of "lib"

[Shihab Soft]

Okay thanks.

Not sure how well I am gonna proceed on this. As I've never compiled android neither worked with C codes (in recent times).

Regarding my QEMU comment, if a dev can reproduce this issue on QEMU will he/she be able to rectify this? Because in 2 systems I've tried with QEMU, this issue persisted.

[Mauro Rossi]

Hi,

please try with Chrome version 75 (i.e do not update Chrome) and check if you see the video playback,

then update Chrome to version 81 and check if the video becomes black (with visible controls)

If that's the case then check if you see the following lines in logcat

05-20 22:41:23.665  7190  7211 E NdkImageReader: acquireImageLocked: Output buffer format: 0x4, ImageReader configured format: 0x23

05-20 22:41:23.665  7190  7211 E chromium: [ERROR:image_reader_gl_owner.cc(263)] method fails for some other reasons

Mauro

[Shihab Soft]

Hi Mauro,

I followed you steps..

Tried from version 75.

Controls are visible.

Video attempts to load but with black screen.

The progress bar actually jumps to the position where I last paused.

Video just pauses. The control also shows as paused.

When I press play again, nothing happens.

Same error as in the logcat I posted in my previous comment. And no the logcat you've posted above is not present.

Upgraded to latest chrome which is 81.

Tried to play the same video..

Same as the above, same logcat errors. And no I don't see the logcat you've posted.

[Shihab Soft]

I now tried to comment out the wrong rect check as seen in the logs.

Once bypassing that IF check the video seem to start playing, but lots of green artifacts and glitches appeared and the library crashed as I saw from the logcat.

[Shihab Soft]

Hi Mauro,

You were right!

I started fresh with latest Android 9.0 R2 release with k49 kernel, the video playback was fine in VMWare with chrome 75. (Even tho it was laggy, but it could just be the VMware)

Once I upgraded chrome to the latest version, the video was playing but only black screen.

[Shihab Soft]

One more test on the actual hardware itself.

Android 9.0 R2 k49 kernel with Chrome 75 been actually playing the video flawlessly!

Tried the same in Android 7.1.2 normal 4.1x kernel (Prime os mainline) with Chrome 75 - The same issue persists, video loads then black screen and the playback is auto-paused.

[Chih-Wei Huang]

Shihab Soft <spk...@gmail.com> 於 2020年5月21日 週四 上午12:29寫道：

>
> Thanks for the help so far Michael.
> Not sure who else can assist here..
> @Chih-Wei Huang ?

You can send me a test account surely.

However, Michael is the most experienced guy who can help you here.
He has helped fix most media codecs issue of android-x86.
If he can't help, probably nobody can.

[Michael Goffioul]

On Fri, May 22, 2020 at 2:22 AM Chih-Wei Huang <cwh...@android-x86.org> wrote:

Shihab Soft <spk...@gmail.com> 於 2020年5月21日 週四 上午12:29寫道：
>
> Thanks for the help so far Michael.
> Not sure who else can assist here..
> @Chih-Wei Huang ?

You can send me a test account surely.

However, Michael is the most experienced guy who can help you here.
He has helped fix most media codecs issue of android-x86.
If he can't help, probably nobody can.

I'm happy to investigate, but I can't do it if I can't reproduce the problem. Note that there might be 2 issues at play here:

1. codec initialization failure (the error about wrong cropping rectangle)

2. change in video pipeline in Chrome/80: this is usually visible with an avalanche of errors in logcat related to NdkImageReader

Michael.

[Shihab Soft]

Hi Michael,

I already found a way to reproduce this issue.

As I mentioned in my previous comments.

Kernel 4.9 with Chrome 75 seems to be working perfectly on May hardware. (Android 9.0 rc2)

But when I upgrade to Chrome's latest version, the video is black, but the playback is ongoing..

Also any other kernel like 4.1x seems to halt the playback.

You can reproduce this exactly with VMWare player free.

[Michael Goffioul]

As I said, there may be 2 problems. The one you describe below is similar to a problem due to a change in the video pipeline of Chrome (since Chrome/80), you can find some discussion here:

https://groups.google.com/d/topic/android-x86/BgaWndOl70M/discussion

However, the logcat that you reported initially does not match (no NdkImageReader in the logs, the error seems to come from invalid cropping rectangle). If this is really the same problem, then a solution that worked for me is to allow NV12 format for the codec output (see the discussion in the link above for pointers). But this solution may well be only working for me, because I'm using intel/minigbm with drmfb-composer, and it might not work at all on a stock Android-x86 9.0-r2 (and it may also depends on where you run Android-x86, real hardware vs. VM, as different environment will lead to different gralloc implementation used at runtime).

But before rushing into that, I would advise you to try with another browser (e.g. Firefox) on Android. The video pipeline change should only affect Chrome-based browsers.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/e745506f-e266-42fb-a30f-af369529992c%40googlegroups.com.

[Shihab Soft]

I tried with firefox, it barely seem to show the first frame of the video and hangs there forever.

Also not sure if it'd be helpful, as I said above, I can only get the video to play in Android 4.9 Kernel with chrome 75. And it's butter smooth.

Nothing other than that works with my hardware.

In Android 7.1.2 with Kernel 4.19, the playback doesn't even start.

In Kernel 4.9 with Chrome latest, the playback starts but only black screen.

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.