Posts by Iridium

Quote from milan0

Is there another way?

Considering the costs of additional hardware it might actually be worth leaving the RPi4 on all the time. It probably wouldn't cost more than $10pa with a decent PSU.

When the RPi is shutdown, it stays shutdown. The only way to do what you require is some sort of smart power plug that will work with your remote.

Sounds like a problem with Widevine (Whatever that is) and not LE. You will need to contact the developer to try and resolve the issue.

To stop the update - turn off automatic update in the addons page.

I'd agree with a RPi4 however, the user occasionally needs Android which, whilst an image for Android is available, it's not particularly usable. Personally, I'd buy a RPi4 just for LE and use a phone/tablet with cast or HDMI for Android.

I'm still using a MECOOL M8S PRO+ which works fine on LE but is only Android 7.

LE mount's USB drives drives by default not SMB.

1) Do you actually need Kodi? If not then you'd be better off using the RPi4 as a NAS solution. Look for OMV or just google NAS raspberry pi - there are other solutions.

2) Have you looked at using profiles within Kodi. That might give you the control you want.

3) A dirty method would be to unmount the drives when Kodi starts, relying on you to mount them when needed.

I would go back to a standard config.txt first. Your overclocking could be the source of your issues.

If I understand it correctly. The on-board EEPROM tells the kernel what model it is, and loads the relevant driver. It would seem that in your case the EEPROM tells the Kernel that it is a digi-pro when it should be just a digi.

So it looks like Hifiberry have shipped a dodgy EEPROM with your board.

In the end it won't make any real difference to it's operation, but I wonder how many other people have had the same issue.

Glad you got it sorted. I was perplexed by your problem and tried to replicate it on an old hifiberry-digi without success,

Hifiberry support (Daniel) has always been excellent IMHO.

So it looks like (cough) someone make a mistake!

Can you, as a test, try dtoverlay=hifiberry-digi-pro and see what the outcome is.

Thanks for sharing your experience.

I've changed the title to [Solved]

1) Try adding your nfs share locally and not through Kodi. Look at Wiki for instructions.

2) Have you turned on UPnP in the LE options?

3) The internal wifi of the RPi is not the best in the world - especially if enclosed in a case or behind a TV. Get a good USB wifi adapter, with a large antenna

Quote

So can someone please tell me how I could "port" EventLIRCd to Kubuntu or any other Linux distro in general ?

You'd be better off asking on the Kubuntu forumKubuntu forum

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:

Please follow:

I have no idea - I am just trying to help.

Try reading the Wiki: IR

You could try adding the mount command to autostart.sh as it *might* work.

Or: Try adding the share manually: Network Shares

The GPIO pin layout is the same as previous 40 pin RPi's so it should work just fine on the RPi4.