Nope, but you can always install the Jarvis-era "Confluence" skin from the Kodi repo. AFAIK this is still being maintained.
Posts by chewitt
-
-
I'd guess that you only calibrated the 60Hz "desktop" refresh rate, and then Kodi switches to 50Hz (PAL) or 23.976Hz (DVD) for media playback. Kodi requires you to calibrate each refresh rate independently (which is annoying and dumb, but is how it works) so you need to switch the desktop to those modes and repeat the calibration process. See if you can change the TV to "Just Scan" or similar.. modern TVs shouldn't need calibration.
-
It normally requires changes in the low-level firmware. I'm not familiar with RK firmware, but most ARM devices are dependent on closed-source pre-compiled blobs, which will rule out making any changes.
-
Have a look at /storage/.kodi/userdata/sources.xml
-
Our normal approach is to encourage a couple of capable users to create some unofficial community images that are published/shared here in the forums. Set "BUILDER_NAME=stpf99" when you build images and this is embedded and we can see exact stats on the number of users the images attract. If things ever get popular we can move to "adopt" the changes. If not, we don't have to add complexity for a niche audience.
-
If it's anything like the nVidia equivalent, it will require continuous package bumping to match with continuously evolving card drivers and thus will be completely un-maintainable over time. I'm not aware of anyone doing this or working on it.
-
Code
echo "options cfg80211 ieee80211_regdom=US” > /storage/.config/modprobe.d/cfg80211.conf^ until a GUI version of this appears in v9.2.3, run that and reboot, then see if things have improved?
-
-
IIRC evdev is part of the system tools add-on. Install and log out/in from the SSH console for it to be available.
-
Go into Kodi setttings > LE settings > Services .. enable Samba. On boot /storage/.config/samba.conf will be used if itt exists, else the the embedded smb.conf will be used.
-
From personal experience it's tempramental .. keep trying.
-
HEVC will not play unless it's small file sizes because it's being CPU decoded, there is no HW decode support yet. I found 128MB CMA to result in crashing.. I still state that 512MB boards are not supported.
-
There are test images on Index of / but no DVB support at this time so best to stick with older releases.
-
No LE images are using mali now so the mali-utgard package is probably needing some patches or hacks to work around kernel API changes. Lima is quite stable so I wouldn't bother with that change - it's not the source of your issues.
-
Normally (most apps) you supply the IP/hostname of the DB and admin credentials and the app will create whatever database and table structures it needs to operate. Best people to help you get setup with that are Jeedom - we have no clue about their processes.
-
The latest version is LE 9.0.2, but I wouldn't recommend installing to internal emmc as this will complicate future upgrade to our mainline kernel images (still work in progress, but with most of the basics now done). Despite the hype, the performance difference with a resonable SD card is not significant. It's noticeable if you use older slower SD cards and older slower hardware.
-
LibreELEC.tv/linux.aarch64.conf at amlogic-master · chewitt/LibreELEC.tv · GitHub
^ If I change the CMA fall-back value from 256 > 128 and force a 1GB device to 512M via kernel boot params, the Kodi GUI comes up and I can play the 1080p60 version of Big Buck Bunny (test media). I need to run some experiments on a wider variety of hardware and codecs before I can consider making that value the distro default. It's possible that HEVC (which is not supported yet) might require more. Let me know how that works for you?
-
You need to boot from the AMLGX "box" image (edit uEnv.ini and set the correct dtb name) and then copy the AMLGX "khadas-vim" image to /storage; then you can write the "khadas-vim" image to emmc. The emmc image will only boot from an SD card if you erase the emmc first.