Posts by Da Flex

The log has a "timeout waiting for buffer". And at your other thread I see a "segmentation fault" and an "out of memory". I suggest a RAM test.

Write a Python script, started from autostart.sh.

Sounds like a bug of the skin. Ask the developer of the skin to update the icons.

Quote from Kantilo

I activated the passtrough in Kodi (DTS and AC3), but my TV put me Dolby Digital Stereo on 5.1 audio tracks

What happens if you try to play the test file, as suggested by user mglae?

PS: Should be the same device number on both setting lines, like two times DEV=0 or two times DEV=1.

Compared to my RPi output, I have the same audio device at those settings (rest looks OK):

Quote from Besuz

Code

1. <setting id="audiooutput.audiodevice">ALSA:hdmi:CARD=HDMI,DEV=1</setting>
2. <setting id="audiooutput.passthroughdevice">ALSA:hdmi:CARD=HDMI,DEV=0</setting>

Quote from racelife

So I should be fine?

Absolutely.

Quote from Kodiuser102

Kodi will always see the CEC Adapter is present, and the Bravia will always see the device. However it's always displayed as remote_1 now, and it used to say Kodi.

The Kodi CEC Adapter is an add-on with it's own settings. Play around with those settings. If you have other Kodi controllers activated (like a game pad), deactivate them for testing.

Quote from pimp1310

i want to use this on my firetv too.

there i only can use the autostart file (autoexec.py) of Kodi, is this in the "autoexec.py" compatible?

Try this autostart.sh:

PS: Should be guide-zattoo.xml, maybe spelling error on your code.

I would check the settings of the TV (Bravia Sync). Look at the settings of "Control for HDMI" and "HDMI Device Selection".

Quote from racelife

is it counting all cores so maxing out would be 400%?

Yes. The last value is the sum, Kodi is using at all CPU cores.

I'm running dual-boot Win10 / Kubuntu since a couple of years. I always install Windows first, and the Linux OS after that. Should work with LE, too. Sometimes one have to re-select the Linux bootloader at the EFI menu when major updates overwrite the EFI settings. But that's not very often the case.

PS: Having a fresh thread for this issue would be nice. Especially because it's maybe a backup bug. The original issue has been solved, I think, and should be marked that way.

I bet some temporary files are responsible for different backup size. A quality backup system shouldn't copy those stuff, so it's maybe a small bug.

Having a long LE run time, it seems like increasing temporary data will lead to an out-of-memory error, see here. If so, we have a heavy Kodi bug.

Quote from kurai

Thanks for responding, but we're already quite a long way past that kind of thing.

No problem, you're just already deep into it.

So, I assume you know that all add-ons are OK, and all switchable services (Bluetooth etc.) are OK, too.

You can play around with compile switches now, and start inserting your own debug log messages. That's the way I would go from there.

OK, I expected something like that. And you probably already have log level 1 activated to see as much as you can.

- You can deactivate add-ons for testing.

- You can look at the tmpfs entries of the "df -h" output. I think tmpfs runs at the RAM, too.

You could use the command "top -o %MEM" to see what process uses most RAM (on top of the list).

Quote from rdorsch

Can RPi 3B+ go to suspend and resume (that would be a real reason to drop the cubox-i )

A couple of months ago I was trying to switch off / on the display of the RPi 3B+, which is some kind of a suspend mode. I was able to switch off the display, but switching it on again didn't worked (Kodi issue, I guess).

So, I have been quit the idea of an always-on-device, and built in a power button, which works fine.