.. and not using Berryboot - it's causing tons of issues, so please test with a clean installation on a separate SD card. Using Berryboot with LE is not supported.
so long,
Hias
See the post above...
Posts by ghtester
-
-
So the original question is not clear enough and you need to search for HDMI CEC related threads.
-
-
The same isue on LE Nightly 20220218.
-
-
I think in your case it could be related with the Youtube add-on.
I am also experiencing a memory leak in Kodi when using Live TV so it looks like a more general Kodi's bug in (at least) recent LE Nightlies.
-
No crashlog - no problem...
-
Log is http://ix.o/3PIM
This site can’t be reached
Check if there is a typo in ix.o.
Use pastecrash to get a link to crash log and share it.
-
Encountered on RPi 4B/2GB after upgrade from 20220212.
2022-02-15 01:48:05.466 T:3457 INFO <general>: initializing python engine.
2022-02-15 01:48:06.218 T:3457 INFO <general>: ### [XBMC LCDproc] - Connected to LCDd at 127.0.0.1:13666, Protocol version 0.4 - Geometry 16x2 characters (80x16 pixels, 5x8 pixels per character)
2022-02-15 01:48:06.247 T:3457 INFO <general>: ### [XBMC LCDproc] - Empty driver information reply
2022-02-15 01:48:06.389 T:3457 INFO <general>: ### [XBMC LCDproc] - Loading settings from /storage/.kodi/addons/script.xbmc.lcdproc/resources/LCD.xml.defaults
2022-02-15 01:48:06.395 T:3457 INFO <general>: ### [XBMC LCDproc] - Loading settings from /storage/.kodi/userdata/LCD.xml
2022-02-15 01:48:06.705 T:3457 ERROR <general>: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <class 'LookupError'>
Error Contents: unknown encoding: hd44780-a02
Traceback (most recent call last):
File "/storage/.kodi/addons/script.xbmc.lcdproc/main.py", line 33, in <module>
xbmclcd.RunLCD()
File "/storage/.kodi/addons/script.xbmc.lcdproc/resources/lib/xbmclcdproc.py", line 103, in RunLCD
self._LCDproc.Render(settingsChanged)
File "/storage/.kodi/addons/script.xbmc.lcdproc/resources/lib/lcdbase.py", line 550, in Render
self.SetLine(mode, outLine, line, self.m_lcdMode[mode][inLine], bForce)
File "/storage/.kodi/addons/script.xbmc.lcdproc/resources/lib/lcdproc.py", line 575, in SetLine
bstrScrollMode = self.m_Settings.getLCDprocScrollMode().encode(self.m_strLCDEncoding)
LookupError: unknown encoding: hd44780-a02
-->End of Python script error report<--
2022-02-15 01:48:06.740 T:3457 INFO <general>: Python interpreter stopped
Update - I had to disable the Use alternate charset option.
-
-
Well, I was facing to similar issue a couple months ago. Look here what helped: RE: LE 11 Nightly - KODI does not start on RPi 4B after upgrade to 20211007
-
No problem, you don't need to put whole RPi in front. It's all about the IR LED position & power. The cable / wires to IR LED and IR sensor can be long and thin enough so it's up to you which design you select. If you plan to control just your single TV, I believe you can do it so the both IR sensors can be almost invisible, even without opening the TV box.
-
Both outlined solutions should work, a relay everytime and IR if your TV can be controlled through IR Remote Control (in this case you can use RPi to send IR commands through a simple HW with IR diode to TV). I am using both methods. IR is more universal (and safe as you don't need to work with High Voltage circuits) so you can record IR commands from original IR Remote Control for any IR controlled device and then send these IR commands from RPi to devices (including but not only power on / power off).
Only one IR Remote Control is necessary - even from your old TV - to control RPi and RPi can control your TV or another devices around (that are covered by the IR diode range).
-
Kodi on 'client' RPi 4B/2G crashed after switching to another TV channel, at the same time on the 'server' RPi 4B/4G Tvheadend 4.2 server restarted.
-
BTW. another quick memory leak encountered on 'client' RPi 4B/2GB (in the meantime upgraded so running LE Nightly 20220212-d9a07e9):
top - 22:58:46 up 5:45, 1 user, load average: 1.63, 1.43, 1.31
Tasks: 155 total, 2 running, 153 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 16.7 sy, 0.0 ni, 83.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 1847.1 total, 37.2 free, 1605.0 used, 204.8 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 152.7 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1662 root 20 0 2076732 1.5g 84236 R 50.0 82.5 71:02.91 kodi.bin
The memory suddenly started decreasing - about 0,5 MB per second.
After moving Timeshift back (Left Arrow IR Remote key) it stabilized:
top - 22:59:22 up 5:45, 1 user, load average: 1.62, 1.45, 1.32
Tasks: 155 total, 1 running, 154 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.6 us, 2.8 sy, 0.6 ni, 91.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 1847.1 total, 753.4 free, 906.3 used, 187.4 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 853.0 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1662 root 20 0 1358388 843396 84192 D 16.9 44.6 71:12.32 kodi.bin
-
I agree we are sliding to OT, so the last remark...
Regarding to relays - it is much more dangerous than IR because of a high voltage in the circuit. So be careful if you don't have an experience with this. There are some nice examples:
Raspberry Pi power on - enable relayThere are loads of Youtube videos on how to control a relay, but I simply want to be able to power up my Pi and let it activate a relay. Then, when I power it…raspberrypi.stackexchange.comHow to Control a Relay using Raspberry Pi | Electronics HubIn this project, we will learn about Relay and Relay Module, interface a Relay with Raspberry Pi and see how to control a Relay using Raspberry Pi. This…www.electronicshub.org -
No problem, I understand your trouble, despite I did not expect the major request reason described.
Please note if there's an issue with a single backlight LED, you can expect some another LEDs failing soon as well...
BTW. I saw even so burned out backlight LED that the white folio around was burned too. So it might be even dangerous when not fixed. And the recommended fix is to replace the whole backlight if possible.
FYI there's an example regarding to IR send / receive hardware. Of course the CR2032 battery is not necessary as the circuit can be powered from RPi. https://www.digikey.com/en/maker/blogs…-a-raspberry-pi
The software utilities are already part of LE and it just need to be configured easily.
-
Well, I am using Timeshift by default (permanently enabled) while I am watching Live TV. So it's always somehow related with the described issues. I am rarely watching recordings so all described issues are related to Live TV + DVB-T2.
There were always issues with Timeshift but I don't know if a memory leak was there as well in past as I started discovering the issues more deeply several weeks ago. And some issues were hard to address on the same device. Now, separated to 2 devices, some issues are more visible. But it looks to me some issues (that forced me to analyzing it) appeared in recent Nightly builds with updated kernel release.
In general, I am observing the (not just memory) issues depends on:
- moving the Timeshift point
- data stream speed (more often at higher data rates)
- uptime / time of using (watching the same channel, usually several hours are needed to encounter the trouble).
And now I can confirm the DVB-T adapter firmware reload happens due to Tvheadend 4.2 service's (unexpected) restart on 'server' RPi 4B/4GB device (without OOM killer action).
BTW. this is a current top output on 'client' RPi 4B/2GB after almost 19 hours:
top - 12:58:08 up 18:42, 1 user, load average: 1.69, 1.43, 1.41
Tasks: 156 total, 1 running, 155 sleeping, 0 stopped, 0 zombie
%Cpu(s): 6.2 us, 3.4 sy, 0.2 ni, 90.0 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st
MiB Mem : 1847.1 total, 963.3 free, 540.3 used, 343.4 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 1203.6 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1660 root 20 0 1054956 480324 100192 D 32.1 25.4 236:23.04 kodi.bin
After restarting (just) Kodi:top - 13:26:12 up 19:10, 1 user, load average: 1.61, 1.37, 1.35
Tasks: 155 total, 1 running, 154 sleeping, 0 stopped, 0 zombie
%Cpu(s): 7.3 us, 3.1 sy, 0.2 ni, 89.4 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st
MiB Mem : 1847.1 total, 1284.2 free, 237.2 used, 325.7 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 1525.1 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10968 root 20 0 751632 155516 80752 D 21.5 8.2 0:17.31 kodi.bin
