I guess it's possible to write a script to turn off HDMI when it's inactive (but how do you define inactive?) Also I don't believe CEC will wake it up.
Your simplest solution - if you have a normal schedule - is to run a cron or systemd job to turn on HDMI at say 18:00 and turn it off at 23:00.
TBH: It's not really worth it. The RPi4 probably only costs around £10 annually to run.
A check on a S905x box the CPU usage is between 12--> 18% so it's not just RPi.
On a fresh install of 9.2.0 I can confirm that idle Kodi CPU usage is about 15%. However, that is only on 1 core. So the average usage across all 4 cores is below 4%. (Tested with top, iostat, htop and nmon).
Using a boring screensaver (black) drops this to ~10%
Double "however". Turning HDMI off, drops CPU usage to around 1% after ~30s.
It seems a tad high. Is this a stock image or have you added loads of addons?
Guess you need to wait for OSMC then
That's a new one:
The GPIO pin layout is the same as previous 40 pin RPi's so it should work just fine on the RPi4.
We don't maintain Kodi addons so you will need to contact the author directly.
I've got a 4Gb RPi4 too and use it almost exclusively for KODI/LibreELEC.
Would the changes the original poster mentioned have any noticable effects, and where would these be most obvious?
If you're just using it for Kodi/LE then there is no need to change anything. You *might* see some small improvements in GUI response but not enough to warrant the extra cost of cooling devices and *possible* better PSU.
Remember the RPi4 is optimised for *most* usages. What works for one may NOT work for another. Always make any changes in small dosages.
** We do not recommend changing the CPU or GPU frequencies ** but it's your box and you can do what you like... but don't blame us, or anyone else for that matter if things go T*Ts up.
For a starter - start small. Install the heatsink and monitor the temperature. Also keep an eye on the power supply, If it's a crap Chinese clone, then you'll probably get other problems. (Yellow lighting bolt, instability, dead cats etc.)
You *should* be Ok with
If all looks good - temp and power, then try.
You *may* need
If all works well - then great, otherwiseQuote
Which DVB driver module did you load? If the default, try some of the others, It might work
What=192.168.1.207:/tv3 << Note ":" colon.
What is the output of
systemctl start storage-NFSshare.mount
systemctl status storage-NFSshare.mount
Ethernet. Is. Not. An. Option. Do. Not. Even. Suggest. It.
Instead of being aggressive in your post (Which is probably why no one else has bothered to answer), it would have been been better to mention why you cannot connect via Ethernet.
If you're using the internal Wifi, then you shouldn't have any issues. I've connected multiple times with multiple RPi4's. Try supplying screenshots and describe what you are doing.
It might be your SSID or password that are causing the problem, rather than LE itself.
Without the logs, it's going to be difficult to diagnose.
Those values look normal for a RPi4.
I would imagine that bcmstat is showing them as red as it has not been updated for the RPi4 which has faster clock speeds.
So - Nothing to worry about.