Posts by Da Flex

Quote from niek

mmh i cannot find the directory \Kodi\userdata

/storage/.kodi/userdata/advancedsettings.xml is the right location.

Regular log at log level 1 please...

Adding a power button to your RPi is the easiest solution:

Thread

RPi4 GPIO using in LibreELEC

Dear All,

Is it possible use GPIO pins with LibreELEC on RPi4? My idea is use some GPIO pin for LED in the power button for signaling that system is running. Now I´m using only standard shut down funtion in Kodi and RPi4 weak-up function with button on GPIO pins 5 and 6 made by this manual:

How to Add a Power Button to Your Raspberry Pi - howchoo

All manuals I found for this is for NOOBS but not for LibreELEC

Thanks

Radek

Foxbiker

August 16, 2019 at 10:23 PM

Better ask HiFiBerry. RPi5 is pretty new, so it could be a HiFiBerry driver issue.

sky42 had good progress with his N100 during the last weeks (see link at post #5). Maybe ask him for 4k HDR 4.4.4.

Yes, very likely an LSPCON chip issue. You should avoid any DP->HDMI converter (internal or external):

Post

RE: Time to upgrade my NUC. What's hot today?

[…]



As you can see on this block diagram, NUC11PAxxx does not have a native HDMI port. It is using a DP->HDMI protocol converter (PCON) chip. It is more than likely the source of your audio passthrough issues. So this is not a gen11 issue but an issue specific to that NUC model. There is nothing to fix from LE/Kodi side.

smp

January 15, 2024 at 2:36 AM

Incomplete log at log level 0.

Activate log level 1 by creating an advancedsettings.xml file.

Reboot, replicate the issue, and post the resulting URL of pastekodi.

Quote from Da Flex

Activate log level 1 by creating an advancedsettings.xml file, and reboot.

2024-01-22 20:51:40.366 T:985      info <general>: Disabled debug logging due to GUI setting. Level 0.

Not sure whether it's CEC-related at all.

It could be something else, too. Provide the log when the error appears again.

PS: Activate log level 1 by creating an advancedsettings.xml file, and reboot. When the error appears, login by SSH, and post the result of pastekodi.

Quote from niek

If my HTPC is CEC competable?

Obviously not.

Your do HTPC--HDMI-->TV--HDMI-->AVR. That's a problem, because AVR doesn't get the CEC initialization sometimes.

Can you go HTPC--HDMI-->TV and HTPC--S/PDIF-->AVR? Then you don't need CEC initialization.

Quote from josh4trunks

Do you have a CEC capable LE system? Like Raspberry Pi or USB CEC adapter?

Yes, RPi. When you activate another source on TV, then the TV usually switches to that source. The same happens by source reboot. Otherwise CEC adapter is needed to initialize the system.

I think the latter is the case here: HTPC is already on, and has to say "hello" to TV when it's turned on. It does so by being an A/V source to the TV, but not by sending a "hello" CEC signal. So the AVR probably doesn't get a CEC initialization signal, and audio routing is incorrect.

Quote from niek

So i wondering if it is possible that my HTPC (which is connected to the TV by HDMI) could also switch automaticaaly the TV and SONOS on )

If you don't have a CEC adapter in your menu (see post #4), then the answer is no.

fsck on terminal.

Quote from niek

But is there a way that my htpc can send a signal to my tv through hdmi, to turn on tv?

Yep, click at Settings --> System --> Input --> Peripherals --> CEC Adapter, and you'll see all the options.

Do you have SSH access after starting LE? If so, you can use the nano editor to create the file.

I bet your /storage file system has errors. In that case it can be helpful to use a repair tool onto that partition.

1. activate log level 1 by creating advancedsettings.xml
2. reboot
3. login by SSH
4. run pastekodi
5. post the resulting URL