I'm not sure who you're messaging. There is nobody called Jack Ma on LE staff, and adding his address here doesn't magically send email. And that git repo is nothing to do with us. Very confusing ![]()
Posts by chewitt
-
-
The download area lists full releases only. Hence Slice (and Generic, and RPi, etc.) show LibreELEC 8.2.5 which is still the latest full release.
Once LibreELEC 9.0 moves out of beta to full release .. links will be updated.
-
An Intel Core i7 with 4x cores and SSD takes around 3.5 hours. First time compile will be significantly longer as sources for the 380+ packages used need to be downloaded. If your Internet connection isn't quick..
-
As promised several months ago .. these changes should make using OpenVFD easier openvfd: reimplement openvfd support by chewitt · Pull Request #3227 · LibreELEC/LibreELEC.tv · GitHub
Long-term goal is to add a conf pick-list in the settings add-on, but that depends on my Python skills which are a bit rubbish

-
-
Try using the "wait for network" delay (which is just a dumb countdown timer) in LE settings to delay start by 10 seconds. It sounds like a starting driver timing or sequencing issue and that might resolve it.
-
-
-
Projector supports HDMI 1.4 (up to 4K30) not HDMI 2.0 (up to 4K60)?
-
Honestly.. no idea. Copy the "before" dtb.img and experiment. You can't break anything

-
OpenELEC has *never* released an S912 image.
-
Code
fdtput -t s /flash/dtb.img /i2c@c1108500/pcf8563@51 status "okay" echo "aml_i2c" > /storage/.config/modprobe.d/rtc.conf echo "rtc_pcf8563" >> /storage/.config/modprobe.d/rtc.conf^ run than and reboot and it should be all that's needed to make it work (famous last words). It updates the device tree with the node required and then sets the modules to be loaded on boot. The dtb.img change should persist until something replaces the file (e.g. an OS update).
-
Also check List of built-in functions - Official Kodi Wiki .. you can start the screensaver (and any other command will stop) .. so maybe a combination of "sed" to change the setting and then "kodi-send" for the start command.
-
You need to create the profiles.xml file and stash it somewhere in the image, e.g. /usr/config/profiles/profiles.xml, and then you need to modify the Kodi startup script (kodi.sh) to check whether /storage/.kodi/userdata/profiles.xml exists, and if not (because it's first boot) copy it from the /usr/config location before Kodi is started. You can do this within the Kodi package.mk.
-
Well.. even if you don't know what's there, the module list would mean something to other people.
-
If you degrade your Win boxes back to SMB1 and use a wildly out of date OE image .. sure it works. If that's all you want .. fine. If you want to use a secure Win setup your boxes need to disable SMB1 (and with that .. browsing them is dead) and use SMB2/3. At this point the old OE image will fail to work because it has no support for SMB2/3. You'll need an LE image which supports SMB2/3 just fine. Get the current Beta.Create a Kodi user/pass on Windows and assign read rights for that user to the shares (and forget that guest access ever existed). If your Win boxes allow SMB2/3 all you now need to do is manually configure the sources in Kodi to use the same kodi user/pass credential.
Or you can keep wildly changing stuff and hoping it works. Or stick to OE (but then future posts should be in the OE forum not here).
-
I'm just one of the two people who implemented SMB2/3 support in Kodi. I think i'm under-qualified to help further.
-
"lsmod" will list the active kernel modules