Simple test is to stop Kodi, rename /storage/.kodi/userdata/guisettings.xml to guisettings-old.xml and restart Kodi. This will give you clean defaults to see if that's the issue. You can always rename back to revert the change.
Posts by chewitt
-
-
The 10.80.0 URL is correct, it means we can step through pre-Alpha, Alpha, Beta, RC and then finally 11.0.0 as the release version. However we are still in the process of merging a large backlog of package change for LE11 (master branch) so we didn't build and publish add-ons yet.
-
is it also possible to run C programs
Sure, you can run C programs. You won't be able to compile them on the box though as there are no compile tools in the OS. I suggest you read https://wiki.libreelec.tv/development-1/build-basics and familiarise yourself with how our distro is packaged. If you want to develop things we are probably not the distro you're looking for
-
tomaszc Most GXM devices have the headphone outputs wired up in device-tree, but I'm pretty clueless about alsa so the images are prob. using an incorrect alsa conf that prevents its use. Or you might need to install alsamixer to unmute things and switch the outputs around. I'm not really sure how all the plumbing fits together so I'm not sure what to advise, sorry.
-
LE 9.80.11 was a pre-Alpha version, so now we have a full LE10 release some cleanup has been done to remove old add-ons from pre-Beta stages that are not being maintained and use disk. Use the 10.0 release and you will have add-ons again. Or you have to self-compile them for the old version you're using.
-
Things that run over the network are generally a good idea as it means you can run whatever you want as a client device with (if needed) a different known-good combination of OS + drivers + firmware on the back end. Hauppague are good. HDHomeRun devices also seem to get good press.
-
Kodi only checks HDMI properties at start, so if you boot without the HDMI cable attached you'll probably get output on-screen, but with some sort of default kernel resolution like 1024x768 not 1080p.
-
It should be TBS upstreaming their work in that repository to the kernel, but for some raison they don't.
TBS has a love/hate relationship with upstreaming. All the people trying to use their devices and/or sustain support in distros are in favour of upstreaming and a couple of years ago they caved into the pressure and started releasing on GitHub which provided a consistent/common source for them. At the same time this has made it easier for cheap Chinese knock-offs of their boards to be produced so part of their team would like to revert to the less accessible "download tarballs via website" approach they had in the past. I'm not sure what the solution is, and it's a hard problem for a small manufacturer so I'm not sure they do either, so I wouldn't expect much change. Most of the drivers are rather messy anyway so the upstreaming process would need a ton of patience and persistence.
-
LE runs "ash" from busybox, not "bash" (or dash) so shell differences could be the problem.
-
I think the settings add-on stuff was removed around 9.0 or 9.2 as it wasn't really needed. These days we detect /storage/.config/lircd.conf (via lircd.service) which runs a helper looking for /storage/.config/lirc_options.conf before executing /usr/sbin/lircd .. no conf files = no need to start lircd (only eventlirc).
-
in LibreELEC (Matrix) 10.0.0 the solution does not work
I've used the capability to overlay firmware files for testing on a Cubox-i image within the last week, so I disagree. Pastebin directory listings to prove you did things correctly.
-
You need to self-compile the entire distro (image) from sources. Read: https://wiki.libreelec.tv/development-1/build-basics
-
Make sure you restore fluxbox too.
-
RPi4 will report as BCM2835 due to compat decisions in the kernel code and depending on what's been queried from userspace. It's not a fake RPi board, it's normal. See some older explanations for RPi3B reporting the same way (it's still the same thing):
-
AppleTV (mk1) uses "atvclient" to process events from the receiver, see GitHub - chewitt/atvclient: AppleTV Remote XBMC Event Client for Linux .. but we dropped the package from LE several years ago now. It's my understanding that the kernel should be able process the events via USBHID, but you will need to use LIRC which is disabled by default. I'm not very clued up on LIRC usage, but https://wiki.libreelec.tv/configuration/…es#lirc-support and iMacIntel - Debian Wiki might give some hints on what to do.
-
Code
mv /storage/.kodi/addons /storage/.kodi/addons-k18 -
LE will boot with a 32MB /storage partition - no files are copied and *everything* is in the read-only squashfs SYSTEM file.
Some of the changes in distributions/LibreELEC/options will cause problems for a Generic build add ATV project/patches and adjust distro options · chewitt/LibreELEC.tv@ca3ee28 · GitHub
-
blackride I looked for hardware differences odroid-c2:hardware:hardware [ODROID Wiki] but HK fiddled with USB a little (the weak part of their designs on multiple boards) but I don't see anything that would impact an SD card. If there were meaningful differences in the dtb files I'd have something to go on .. but both of the visible changes are minor things. As for the future of LE10 .. I keep what does work rebased against LE in the hope people who develop code take an interest, and I do device-tree work to add support for hardware into the upstream kernel, but Amlogic media capabilities in the upstream kernel are not in brilliant shape and I don't code so have limited ability to fix anything. LE releases don't make much sense right now (which is why nightlies are stopped and we are not pushing it at anyone). Maybe things change. Maybe they don't. The future is up to the community..
