I'm using an RPi 3B+ with a CEC Panasonic TV, too, and it still works fine. On the RPi side, CEC is active by default. On the TV side, check that Viera Link is active (different name for CEC). Maybe your Panasonic TV got an update.
If that doesn't help, try a different HDMI cable.
On a touch-screen-only system without RC, you should try to find the dev of the skin first. Those devs are usually at the main Kodi forum.
If that's not possible, you can attach a physical button at the GPIO, and define it as "back navigation". Easy to do, but ugly.
We're not the developers of that skin. As a workaround you can define "back navigation" on your remote control.
Here is an example to define the yellow button as "back navigation" at /storage/.kodi/userdata/keymaps/remote.xml :
<keymap>
<global>
<remote>
<red>VolumeDown</red>
<green>VolumeUp</green>
<yellow>Back</yellow>
<blue>ContextMenu</blue>
</remote>
</global>
</keymap>Papalapa Login by SSH, go into the folder by cd /storage/.update and download the file by wget <URL> .
Edit: using powering down of the kodi menu did create a failure. powering down ignoring, reboot, system halted. it stagnated in LibreELEC icon.(this is the nightly build.)
I'm sure this will be fixed at the stable version. You can help to fix this bug, if you provide a link to a log file. Then we can see what goes wrong when you try to shutdown. I suggest to open a new thread at our bug report sub-forum for this issue.
You can mark this thread as solved by editing your first post.
The cause might be a higher audio data rate of Spotify, compared to your NAS music. If the Spotify add-on has an option to reduce that data rate, give it a shot.
9.2.4 ?
It's based on Kodi 18.8 and available as test build. No ETA for stable release.
That's an unusual error, so my bet is an AVR issue. After many years the audio channel relays might get weak.
This is an English-only forum. Please translate your content.
PS: Thanks.
A link to a log file is definitely necessary in this case.
Can you do a test with the standard EFI firmware? Just to close out errors on that part.
Technically it's possible. Idea: Pair your RC with the RPi, attach a Bluetooth adapter to the RPi and pair your Fire TV stick with that adapter. Someone successfully did an IR-to-IR project, which could be helpful for Bluetooth, too: click.
You can mark the thread as solved, if we're done.
Will it work to stick the card in 8gb unit, experience one reboot, then switch to 1gb boot to grab the last log? Thx
Yes, or grab the current log from microSD by using your PC. Activate logging by using your working RPi.
We are looking for good conversation, too, but pretty often we just get spam.
At which point is your question related to LibreELEC?
Please post a link to a kodi.log.
Maybe Raspbian boots into a lower resolution, compared to LE. Make sure your HDMI cable is 2.0 or 2.1 standard. That's needed for 4K.
I'm running out of ideas. Wild theory: The HDMI cable catches some interfering electromagnetic signals, which triggers the wake-up. If you have another HDMI cable, give it a shot. If you buy a new one, make sure it's HDMI 2.0 / 2.1 standard. Those standards are known to have good shielding.
OK, then you're probably right: The RPi must down-sample the stream somewhere. An RPi doesn't have a very fast data bus, so I think the down-sampling happens due to hardware limitation. LE usually deals with A/V streams, so my advice is to use an audio-optimized OS. Such an OS might be slow on video playback, but has the ability to deal with higher audio bit rates.
There already is an LE audio mod for RPi 2/3, which can deal with higher audio bit rates. Maybe those devs will switch to RPi 4 next.
