I have an H3 board (BananaPi M2+) and I was wondering, will it run Kodi 18?
I know the Allwinner boards are a little temperamental and some only work with Kodi 19, but I saw an old forum with an Openelec image with Kodi 16, so I thought there might be a chance? Does anyone have any experience with this device? Will building LE 9.2 work for it?
Thanks for the help, I think I've figured it out now.
I'm compiling on an Ubuntu-based distro and I had some missing some header files.
sudo apt install libdvd-pkg did the trick for me.
Can anyone tell me what compile command is being used to create the nightlies for the Pine 64+?
I'd like to compile it myself, but I can't find any documentation about compiling LibreElec.
Would it just be the following?
PROJECT=Allwinner ARCH=arm DEVICE=A64 UBOOT_SYSTEM=pine64-plus make image
I'm getting errors with this command.
see issue above - proper fix is to use different library. You can experiment by yourself however you want though. And I'm pretty sure display issue is not connected to it - it happens before Kodi is started.
As far as I can tell, pygobject 3.x versions are all dependent on the 'gobject-introspection' library (whereas pygobject 2.28.7 has an optional '--disable-introspection' flag). I'm happy to keep hammering away at this, but I'm a little out of my depth now. Could someone perhaps give me some pointers as to how I go about adding gobject-introspection as a new package? Do I just drop a new subdirectory in the packages directory, or do I need to enable the additional package elsewhere? Is there any documentation on how to create the package.mk files? It seems the most current libraries use the meson toolchain rather than autotools.
EDIT:
Sorry, I just realised which issue you were talking about and I understand now. The best way forward is to lose all dependencies to gobject entirely by using the dbussy library instead. I'm happy to help with this.
Your display resolution is not so common: Found resolution 1280x1024 with 1280x1024 @ 75.000000 Hz Can you try on something more standard first, like 720p or 1080p? If you're able navigating through Kodi menu, try to select different resolutions and see if that stabilizes it. I suspect this is HDMI or clock driver issue...
I Googled the traceback error and found a similar bug that suggests this comes from trying to import a deprecated Python 2 library (gobject 2.28.7-3) into Python 3.8.
I can see that LibreElec is using this same version, despite newer versions being available. Is it worth patching the PKG_VERSION to point to a newer version that is compatible with Python 3.8 (the most current version is 3.38), or is this likely to break other stuff?
Your display resolution is not so common: Found resolution 1280x1024 with 1280x1024 @ 75.000000 Hz Can you try on something more standard first, like 720p or 1080p? If you're able navigating through Kodi menu, try to select different resolutions and see if that stabilizes it. I suspect this is HDMI or clock driver issue...
It was an HDMI to DVI cable going to a computer monitor. I've tried connecting it to my Sony TV and I'm getting the same error.
And both the monitor and the TV worked fine with the ALPHA 1 nightly.
It doesn't show me the Kodi menu. It never gets past the splash screen. Any other suggestions?
However, this should not cause your behaviour. Did you do your own builds? e.g. are you completely sure it's actually Kodi issue and not kernel update for example?
No I didn't do my own build. The error log I attached came from flashing this image with no additional changes.
Is there any way I can further diagnose this?
I'm having trouble with the latest nightlies for the Pine 64+
I can get nightly-20191226-b814aab which is based on Kodi 19.0 Alpha 1 to work fine, but any of the later builds for Alpha 2, Alpha 3 or Beta 1 don't seem to work. The splash screen flickers during startup and then consistently disappears and reappears. The logs suggest that a fatal error is encountered during the loading of the libreelec addon, something to do with loading glib. I'm assuming this is a Python 3.8 issue?
Is this a known problem? Anything I can do to try and fix this?
