Pricewise the OSMCremote and a FLIRC is about the same, OSMC RF remote works out of the box.
Posts by MatteN
-
-
RF is better than IR, no need for a clear view between remote and device, you cant tuck it away in a cupboard.
On my J5040 with LE12 i can start the device with OSMCremote when its been shutdown.
-
-
Not many pc's have built in support for CEC.
-
Way lot cheaper to buy a remote just for controlling the PC, like this one https://osmc.tv/store/product/osmc-remote-control/ it works out of the box, i have 5 of those.
-
For normal use there isn't a very big difference in speed, its way faster when rebooting for an update, its about half the time with ssd.
-
One of my Pi4's is running LibreELEC-RPi4.aarch64-13.0-nightly-20240516-8f6f9a1 (same buildnumber as 20240517) and Gismeteo without any problems.
-
The usual explanation is that Windows sucks...
-
Just download and drop the image in the Update-folder and reboot.
-
I'll probably take mine apart at some point to see if there's a CEC header as the BIOS seems to suggest. If it's there and the header seems to match what the Intel NUC's use, I'll get the Pulse8 adapter for it and test. Ofcourse, I'll also share pictures for the community to see I probably am not the only one that wants this.
If it doesn´'t have the CEC header, I'll try to see if I can get a response from the Pulse8 team, asking if the CEC Adapter is compatible with HDMI 2.0b (or newer) and thus would not disrupt any 4K60 UHD (or better) content. Otherwise, I'll get a wireless keyboard that uses a dedicated RF transmitter which does not rely on the OS. Those should be able to wake up the system.
As a side note, my system doesn't have bad coil whine. It does make a tiny bit of electrical noise, but it's so low volume that I have to put my ear right up to the box in a quiet room to be able to hear it.
For Kodi the OSMC RF-remote works out of the box.
-
Switched to legacy but no change in high CPU utilization. Debug-Log file attached. Could only mitigate the effect a little bit by disabling CPU turbo mode in BIOS.
Intend to go back to 11.06 by Sunday latest via a fresh installation but have to get my hands on a Windows PC first as I have seen, that the image creator is currently not available for Linux.
Try Etcher, https://etcher.balena.io/#download-etcher
-
I use OSMC-remotes on 4 Pi4 and 1 Pi5 without any problems, all of them boots from SSD.
-
MatteN pretty sure 11.0.6 was fine, can't remember this scenario occurring; looking at the change logs from 12 beta 2 to the pre release I'd be amazed if the behaviour wasn't still there, I'll confirm after testing once it's been built
I'm never on Stable build longer then to the next nightly is released.
-
Not sure when this started for me but its been there a while, i have four Pi4 but only one thats on 24/7 and shows this behaviour, maybe i should leave the others on for now and see what happens.
-
I'm using a RPI4 8GB which is on 24/7, connected only via an ethernet cable, with 12 Beta 2, after running for 24 hours I'm unable to connect using the host name from any linux or android devices; if I go into the Libreelec Configuration Addon the top option on the connection is connect rather than disconnect, implying it's not connected at all, but when you choose the connect option it results in a Input/output error - see attachment log file snippet; the RPI4 is however still accessible using the static IP Address it has been assigned, so it is connected but somehow has lost the ability to be access via the hostname , the only way I've found to resolve the issue is to reboot the RPI4 and all then works until a day passes and then it is again unreachable via the hostname until a further restart; using 12 Beta 1 or 11.0.6 this didn't happen
I have the same experience, but using the IPadress works just fine so no big deal.
-
-
Because i had some unused parts lying around.
-
firmware update can be done from BIOS
Stuff still needs case, keyboard/remote, cooling
Only thing missing now is RAM, probably gets here this weekend, got all the other stuff already.