Posts by TnT666

Thanks for the prompt response.

I did that and replicated the problem. That's pretty easy as it almost happens immediately - to the point I have to rush into settings to turn either WiFi or CEC off or I won't get a chance.

I did the paste system logs, there was two options - the crash log and normal so I did both.

Crash version:
https://paste.libreelec.tv/ethical-sawfly.log

Normal:
https://paste.libreelec.tv/proud-flea.log

Then I thought maybe I should replicate it with the default skin just in case.

Crash version:
https://paste.libreelec.tv/fluent-snail.log

Normal:
https://paste.libreelec.tv/stirred-rat.log

I noticed on the debug display when WiFi and CEC were both on the FPS would drop to 0.3, and the Kodi-CPU would shoot up to nearly 200%, and that is not even doing anything, just in the menu.

Thanks again.

Hi,
I've seen people talking about issues with LE12 for WiFi and for CEC separately, but I haven't seen someone mention this issue.

If WiFi is connected AND CEC is enabled it will just crash constantly.. seemingly in about 30 seconds.
If WiFi is disconnected or Ethernet is connected and CEC is enabled things seem to work fine.
If WiFi is connected and CEC is disabled things (mostly) work fine - it might randomly freeze after an hour or two, or not at all.

How I discovered this:

I did a fresh install of LibreELEC 12.0 on a new SD card for a RPI4 (upgrading from a RPI3 I'd been using with LibreELEC flawlessly for years), and set it up, scanned the library etc with ethernet connected, but as soon as I tried WiFi the problems arose. I tried another install on a different SD card and RPI4, but was the same.

Then I noticed if I plugged the micro HDMI into the second port it didn't crash as often. But I needed CEC to work, so I changed the settings and the issues came back.
So I did those tests above to narrow down the issue.

When 12.0.1 was available I tried upgrading, and have subsequently tried a couple of the nightly builds, including the latest (LibreELEC-RPi4.aarch64-12.0-nightly-20240917-7de0439.img) in the hope the issue would be fixed but it still persists.