Yes (and no). The hardware is capable but Intel Linux driver support for HDR is still on the learner slopes of the support curve.
Posts by chewitt
-
-
If you're using the TV remote and it "just worked" you're using CEC to control the pi. Reconnect the Pi directly to the TV (remove the HDMI switch) and test again. If it all works, your HDMI switch disrupts CEC and we have a starting point to investigate from.
-
You could create /storage/.config/autostart.sh and add something like:
(
sleep 10
systemctl restart <name of service>
)&
The trick will be figuring out what service needs to be restarted.
I'm sure that's the wrong solution though. What IR hardware is being used?
-
is this on RPi hardware (or something else with no RTC chip) ?
-
-
It sounds like a bug in either the Android app or the Kodi XML-RPC api that mobile apps use to control Kodi. The only thing you can do it update to newer releases - all development on LE7/Kodi16 stopped ~2 years ago.
-
I've used 'dar' for mail server backups in the past as it has a useful combination of tar and rsync features, but it can be complex and it's probably easier to work with rsync which is already included in the OS.
NB: It would be nice to have a decent wiki page with some sample scripts that hook into cron for scheduling to describe this stuff. The step beyond that is expanding features in the settings add-on, although we're more likely to rewrite the add-on (to make it easier to maintain and expand) before that happens.
-
Just a hunch .. change the partition labels on the SD card so they are not LIBREELEC/STORAGE.
-
Have you been reading the SD card in other machines? .. apart from a complete networking failure the only reason the SSH daemon will fail to start is a change to permissions on the server private key. I've occasionally seen people mounting the /storage partition in another OS to copy media to the card faster and an inadvertent perms change on /storage/.cache breaks stuff.
-
As I wrote in post #2 .. changes in Win10 mean Kodi needs to use an authenticated SMB connection to the Win10 shares. This means you need to set a user/pass (credential) on the Win10 share (as guest access no longer works after the update) and you need to (re)configure Kodi to access the 'source' (the Win10 share) using the same credential.
-
The last four major versions of Windows all require different solutions. Then throw macOS and occasionally Linux into the frame. Then sprinkle the three major evolutions of Samba that could be involved. Then mix it up whether LE is the server or the client. So there's 100+ possible combinations of problem and no simple way to provide an answer. Reporting users typically don't provide enough information while responding users chip in with the answer to their problem which may not be the same as the reported problem. Few staff deeply understand how the whole shizzle hangs together and they're not always on-point, and not always perfect either. Any threads started on this topic become definitively confusing rather quickly. Sorry that's not the answer you'd like, but that's the current reality. Hopefully in a couple of years MS stops reconfiguring Windows in each update and there's a more consistent position!
-
Learn how to use passwords on shares .. in Win10, LE, and Kodi.
-
LibreELEC build's aren't official for the Rock, and the development ones are laggy, buggy, and unstable.
At the point where the lead developers for RK hardware think it's ready we'll release something. Until then you're running a known-to-be unfinished work. We expect the codebase to have bugs. You should expect them too.
-
Win10 has probably applied updates during the reboot that change it's SMB configuration. It now requires an authenticated connection to shares so you need to edit sources (in Kodi and on Win10) and set credentials. Win10 will also expect an authenticated connection when it connects to the LE samba server; if you have enabled the user/pass function the default is libreelec/libreelec.
-
chewitt, could you make LE repo available for S905/aarch64 Leia Kodi 18.
No. Official releases will use 64-bit (aarch64) kernel and 32-bit (arm) userspace to ensure libwidevine.so is available for Netflix/Amazon support. There are no plans to release aarch64 addons so "update" to the S905/arm image and addons should be available.
-
should be fixed now if you refresh the repo
-
Displaying upgrade messages in the GUI only works for English (without a large translation effort) and also requires the functionality of the settings add-on to be extended, which is probably more work than supporting SMB issues in the forums
-
I've updated the addons webserver to map S905/aarch64 against Odroid_C2/aarch64 which should make add-ons available to the LE8.2 (Kodi 17.6) images. Reboot or force-refresh the LE repo and it should show content now.
