Chromium?

  • I guess you're also not using Mir? Sorry if that's off-topic but what are you using (any documentation available) ?


    Nothing :) on our arm platforms kodi runs directly on the frame buffer device.

  • Just installed Chromium 8.0.102 on a LE 7.90 alpha build for Chromebox. Flash is running great, but I noticed page scrolling a full screen video is very choppy. I have tried turning hardware acceleration on and off (choosing Intel for on as the Chromebox is a celeron CPU), but no difference between the two. Is this a LE 7.90 alpha bug? Or a Kodi setting I need to fix? Thanks!


  • Just installed Chromium 8.0.102 on a LE 7.90 alpha build for Chromebox. Flash is running great, but I noticed page scrolling a full screen video is very choppy. I have tried turning hardware acceleration on and off (choosing Intel for on as the Chromebox is a celeron CPU), but no difference between the two. Is this a LE 7.90 alpha bug? Or a Kodi setting I need to fix? Thanks!


    The chromium hardware accelleration settings are very much a hack. It may work it may not, there isn't much I can do about it.


    check the special page 'chrome://gpu' and see what the render methods say.


    also make sure that chromium isn't running in the background because when you change the settings for chromium from kodi they won't change.
    in chromium settings ('chrome://settings') scroll to the bottom and disable running in the background.

  • The chromium hardware accelleration settings are very much a hack. It may work it may not, there isn't much I can do about it.


    check the special page 'chrome://gpu' and see what the render methods say.


    also make sure that chromium isn't running in the background because when you change the settings for chromium from kodi they won't change.
    in chromium settings ('chrome://settings') scroll to the bottom and disable running in the background.


    OK I did as you suggested and disabled running in the background. I also disabled hardware acceleration in both chrome://settings and the add-in settings. Page scrolling is still very choppy compared to chromium on my previous Openelec build. Here's the output of my chrome://gpu screen:Graphics Feature Status

    • Canvas: Software only, hardware acceleration unavailable
    • Flash: Software only, hardware acceleration unavailable
    • Flash Stage3D: Software only, hardware acceleration unavailable
    • Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
    • Compositing: Software only, hardware acceleration unavailable
    • Multiple Raster Threads: Disabled
    • Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
    • Rasterization: Software only, hardware acceleration unavailable
    • Video Decode: Software only, hardware acceleration unavailable
    • Video Encode: Software only, hardware acceleration unavailable
    • WebGL: Unavailable


    Driver Bug Workarounds

    • clear_uniforms_before_first_program_use
    • count_all_in_varyings_packing
    • disable_post_sub_buffers_for_onscreen_surfaces
    • scalarize_vec_and_mat_constructor_args


    Problems Detected

    • GPU process was unable to boot: GPU access is disabled in chrome://settings.
      Disabled Features: all
    • Clear uniforms before first program use on all platforms: 124764, 349137
      Applied Workarounds: clear_uniforms_before_first_program_use
    • Mesa drivers in Linux handle varyings without static use incorrectly: 333885
      Applied Workarounds: count_all_in_varyings_packing
    • Disable partial swaps on linux drivers: 339493
      Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
    • Always rewrite vec/mat constructors to be consistent: 398694
      Applied Workarounds: scalarize_vec_and_mat_constructor_args
    • Raster is using a single thread.
      Disabled Features: multiple_raster_threads
    • Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
      Disabled Features: native_gpu_memory_buffers


    Version InformationData exported7/11/2016, 8:59:59 PMChrome versionChrome/50.0.2661.75Operating systemLinux 4.6.2Software rendering list version0Driver bug list version8.59ANGLE commit idunknown hash2D graphics backendSkiaCommand Line Args--user-data-dir=/storage/.kodi/userdata/addon_data/browser.chromium/profile --test-type --start-maximized --enable-gpu-rasterization --enable-accelerated-2d-canvas --ignore-gpu-blacklist --ppapi-flash-path=/storage/.kodi/addons/browser.chromium/bin/PepperFlash/libpepflashplayer.so --alsa-output-device=hdmi:CARD=HDMI,DEV=0 --window-depth=24 --flag-switches-begin --flag-switches-endDriver InformationInitialization time0In-process GPUtrueSandboxedfalseGPU0VENDOR = 0x0000, DEVICE= 0x0000OptimusfalseAMD switchablefalseDriver vendorMesaDriver version11.2.2Driver date Pixel shader version Vertex shader version Max. MSAA samples Machine model name Machine model version GL_VENDORIntel Open Source Technology CenterGL_RENDERERMesa DRI Intel(R) Haswell MobileGL_VERSION3.0 Mesa 11.2.2GL_EXTENSIONS Disabled Extensions Window system binding vendor Window system binding version Window system binding extensions Window managerFluxboxCompositing managerNoDirect renderingYesReset notification strategy0x0000GPU process crash count0Compositor InformationTile Update ModeOne-copyPartial RasterDisabledGpuMemoryBuffers StatusATCSoftware onlyATCIASoftware onlyDXT1Software onlyDXT5Software onlyETC1Software onlyR_8Software onlyRGBA_4444Software onlyRGBX_8888Software onlyRGBA_8888Software onlyBGRX_8888Software onlyBGRA_8888Software onlyYUV_420Software onlyYUV_420_BIPLANARSoftware onlyUYVY_422Software only

  • I use to maintain a smooth scrolling patch but dropped it when updating chromium as it didn't apply anymore, that might be it

  • Ah yes maybe that's it. Can I downgrade to an earlier version? Or I can wait for you to add it back to the next build.

  • I installed the chromium build available from the openelec repo and this one still had slow scrolling and lagging, where it used to run fine on my OE build. So I'm guessing it's an LE issue or krypton alpha bug? All my movies and videos play fine btw

  • Could we get a setting for interface zoom (x1.25, x1.50, x2.00) like in the older plugin below:
    name="chromium", version="6.0.7", provider-name="joseba (devel.ba [at] hotmail [dot] com)"


    It really helps with how chromium looks like from "tv watching distance" on a 40" 1080p, etc.


    Thanks!


  • Could we get a setting for interface zoom (x1.25, x1.50, x2.00) like in the older plugin below:
    name="chromium", version="6.0.7", provider-name="joseba (devel.ba [at] hotmail [dot] com)"


    It really helps with how chromium looks like from "tv watching distance" on a 40" 1080p, etc.


    Thanks!


    Hi guys


    i have a OTT MXQ box now installed libreelec 7.0.2.4 on it, and i found this chromium thread , i am interested in finding out if its possible to install it on my STB and if i can run Netflix on it ?


    Has anyone tested it and had any success?


    Any hints or comments are welcomed


    thxs
    Tester100


  • chromium add-on is for x86_64 hardware only

  • chromium add-on is for x86_64 hardware only


    Hi Irusak


    thanks for your reply.



    I wonder how the android 5.1 runs netflix plugin natively on the amlogic s905 i have one with android 5.1 running ok, perhaps we could copy some info? or run it in libreelec as external app plugin?

  • tester100 : Let us know when you finish reverse engineering the pre-compiled Android binary code and have something to share that we can compile to use in LE. Thx :)

  • chromium add-on is for x86_64 hardware only


    Hey guys, I understand that Chromium is x84_64 only, but for the SBC touting users, wouldn't this be a viable alternative: Raspberry Pi • View topic - Kweb Suite (Minimal Kiosk Browser, omxplayerGUI) ?


    I'm not a coder, so I don't know what this would imply in terms of development, to add it to LibreELEC, but it would be good to get a sort of browser for those websites/services that don't have a Kodi add-on.

  • Nope. It requires a large pile of libraries that we don't currently require and X windows, which is present in Raspian but not LE.