Well, as luck would have it, the volume thing is not an issue for me as I let the AV-receiver box handle that aspect of things 
As far as the remote goes, I may also be in luck. I'm using the Logitech Harmony system (fingers crossed it stays alive) and I have the facility to have the remote send any arbitrary key-command(s) for a given button.
Thanks for the pointers of what to look at - I'll report back when I've had a chance to poke around in more detail.
...that's usually handled by special (background) services of desktop environments, but LE doesn't include a full desktop environment so the buttons on your keyboard/remote won't have any effect.
Ah - that kinda-sorta has a bearing on a question I had.
Ideally I'd like to use the same IR-remote I use in main LibreELEC/Kodi via lirc & keymaps, but haven't had a chance yet to poke around seriously.
VaccuumTube's in-app settings dialogue says it uses up/down arrows to navigate, but it doesn't seem to recognise them on the bluetooth keyboard or IR-remote I'm using.
I was going to ask how keyboard/mouse/remote handling & configuration worked in the Flatpak environment, but if there isn't any plumbing for it, because of lack of a "proper" desktop environment ... ??
Most excellent - cheers 
Hi Hias, CvH.
I see the newer Flatpak addons being merged into LibreELEC:master tree but they aren't yet available from the addon repo (current version 12.80.7).
Is it just a matter of me being patient till there's a repo update built & published ?
... THERE IS NO SUCH THING AS KIOSK MODE. Feel free to prove me wrong with a screenshot from the Kodi GUI - anywhere it says Kiosk.
Some skins have their own notion of "kiosk mode" and have toggles for it in their particular settings menus.
(Transparency being one I can see, as I still have it installed)
That might be where the confusion comes from i.e. It's language in some 3rd party skins but *NOT* a core Kodi thing.
I've just installed the official Steam Link remote gamestreaming client from https://flathub.org/en/apps/com.valvesoftware.SteamLink
Works great 
Just trying Chromium this very minute on an Odroid H4 (Alder Lake N97). 
Very nice work.
That sounds fantastic.
Looking forward to trying them out when Generic/x86_64 happens
The source of the problem looks like it has been identified in the ALSA maintainer's Git.
Now it's a question of waiting till they can generate and publish a fix so that the LibreELEC team can integrate it.
No - not only you
It's been reported in the LibreELEC developer's Github:
[BUG] [LE13] with kernel 6.18 HDMI Audio has vanished #10775
TL;DR
Weirdness with random USB <-> SATA adapter. Booting once with disk attached somehow reset/cleared the issue and it now sleeps/resumes as expected.
Not worth anyone elses brainpower to dig deeper into root issue, so marked as solved.
Finally got around to poking at this in a more organized way.
The hardware that triggers the bug turns out to be a USB SATA adapter (JMicron JMS578 based).
No onboard SATA sockets on this SBC, just NVME, so I use this to plug in an ancient spare SATA SSD to do occasional full disk image block-based backup snapshots with Clonezilla - more frequent when I'm futzing around with LE nightlies. I usually leave the adapter plugged in and only stick the SSD on the end when I want to trigger a backup.
(Script detects SSD volume being mounted, runs efibootmgr --bootnext 3; to select the SSD at next boot instead of the default NVME device with LE on it, reboots, runs an automated Clonezilla session from the SSD, saves the backup locally to a dedicated partition on the SSD, then reboots again, once done, from the default NVME boot device, back into LE.)
Aaaaaanyway - systematically going through the various bits of installed hardware, the hang on resume-after-sleep went away after unplugging/boot/replugging/boot of the JMicron SATA adapter (without and disk attached).
Puzzling - I saw that lsusb / dmsg only listed the JMicron device when it had a disk attached. I unmounted the disk and unplugged, leaving USB adapter in place and rebooted ... and now the sleep resume test worked just fine, as it did with LE12.x stable.
Huh.
Now I can't recreate the hang condition.
Maaaaybe there's only power running through the adapter's chipset when there's a SATA device attached, completing a circuit?
Maaaaybe booting with a SATA disk attached reset/cleared some non-volatile state register in UEFI ?
Maaaaybe some change to S3 sleep parameters/implementation was buried in the depths of one of the kernel releases ?
Maaaaybe it's just ghosts ?
This seems like a bizarre edge case of circumstances and hardware unlikely to ever affect anyone else, and ultimately not worth wasting any of the LibreELEC team's time on, so I'll close this and we can all move on with our lives
On an Odroid H4 (Intel N97 Alder Lake x86 SBC) attempting resume from S3 sleep now results in a locked up state where system powers on but does not progress to restoration of OS & Kodi state.
It's a hard lock-up - doesn't respond to the reset button and requires a 4-second press on PWR to force hard power off. System does a normal cold boot at next power-on.
Has something fundamental changed in LE13 with the resume/sleep management ? (Maybe kernel version or something in the Linux scaffolding of LE's x86 build ?)
For further information, state & meaning of the 5 onboard diagnostic LEDs:
- Red (PWR) – Solid light when DC power is supplied
– Blue (left, SLEEP) – turns off only when the system enters into suspend mode
– Blue (right, PMIC) – turns on only when the major power rails are working
– Amber (SATA) – Flashes when SATA data transfers
– Green (NVMe) – Flashes when NVMe data transfersIn normal powered-down state with PSU still connected:
\ Red \ - - - - \ - - - - \ - - - - \ - - - - \
In regular powered on running state (Amber & Green flash as disk I/O happens) :
\ Red \ Blue-L \ Blue-R \ - - - - \ - - - - \
After a failed resume the system LEDs show:
\ Red \ Blue-L \ - - - - \ Amber \ - - - - \
The presence of the solid Amber LED (SATA) seems slightly anomalous - there are no SATA devices present, the only disk in the system is an M.2 NVME
In normal operation and with prior LE12 builds the Green NVME was the only I/O LED that flashes at any point.
Grasping at straws ... Perhaps something is making a faulty assumption that a SATA device should be present, and is hanging the resume process as it waits for a response that will never come ?
I am somewhat stuck at this point as I don't have a further way to diagnose the resume process - logging stops in what looks like a normal manner after S3 sleep is triggered and proceeds to shutdown state. Given that I have to hard power-off and cold boot after this point there isn't any logging available for the S3 resume sequence, just the kodi.old.log to the point of sleep shutdown.
Any pointers would be appreciated.
The python 3.13.9 version included with the LE 13/Kodi 22 "Piers" nightly builds breaks compatability with Milhouse's texturecache.py (v2.5.4) database maintenance script that's included in /flash at /usr/bin/texturecache.py
rainman74 has built an updated (v2.5.5) version that works with python 3.13+ (see Kodi forum post https://forum.kodi.tv/showthread.php…0283#pid3230283)
Milhouse's no longer updated original GIT: https://github.com/MilhouseVH/texturecache.py
rainman74's updated GIT: https://github.com/rainman74/texturecache.py
Can we get the updated version bundled, please ?
Can confirm the efibootmgr solution works fine with the Odroid x86 boards. (I've done it on H3 & H4)
I just made a few scripts to pick which boot option to use on next boot:-
e.g. boot_to_windows.sh, boot_to_linux.sh etc.
#!/bin/bash
efibootmgr --bootnext 2; rebootThen you can either
... and so on.
Only major pain in the butt I really encountered was Windows' habit of assuming it's the only OS on the disk and then take full control of the drive's boot setup and re-write it whenever it updates to a new point-release, resulting in having to redo/re-apply the grub shenanigans.
Ah. I *think* I see what you are getting at, but I'm not at all a code-wrangler, so please correct me if I've misunderstood, or missed your point entirely...
If the utmp/wtmp options are explicitly not compiled in then there's simply no data for the PrintLastLog function to present ?
EDIT:
Doh - I'm blind - I completely missed the --disable-lastlog line outright.
Thanks for the quick answers. 
I would like to enable the SSH PrintLastLog option, so that it displays before the standard MOTD as follows:-
Last login: Sat Mar 23 20:31:23 2024 from 192.168.1.2
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (community): nightly-20240311-86dba4b (Generic.x86_64)
LibreELEC:~ #It's part of the vanilla OpenSSH sshd configuration options and is listed as a commented out flag in LibreELEC's /etc/ssh/sshd_config ...
#PrintLastLog yesThe normal LibreELEC method of supplying sshd overrides via /storage/.cache/services/sshd.conf ...
SSH_ARGS=""
e.g.
SSH_ARGS="-o 'PrintLastLog yes'"... doesn't work. I've tried various ways to quote-encapsulate and supply yes|true|on|=yes|=true|=on type Boolean arguments to the -o options but haven't got anywhere.
Am I just mangling the syntax for a thing that *should* work, or is the LibreELEC sshd compiled without that particular bit of functionality that the regular OpenSSH one has ?
Thanks.
Quick bit of advice needed - before I dive into the rabbit hole of attempting to get a Wayland build of chrome/chromium running on LE12-Generic (NON legacy) ... are there any glaringly obvious STOP signs that more experienced code wranglers are already aware of that would make this a doomed attempt ?