Posts by ghtester

Well, in past I also tried to play with the status read period but without any effect.

I believe the patch could help but the request should perhaps go to Linux developers instead.

I am using both but don't see any advantage 4.3 release over 4.2. From my perspective 4.3 is worse (more bugs / compatibility issues with Kodi ) so I recommend stay on 4.2 but both versions are usable.

BTW. it's possible to install both 4.2 and 4.3 TVH add-ons the same device and switch between easily (keep only one enabled).

It's also important if the wires (including connectors) used are capable enough to transfer power spikes, especially the lowest ground wire on the schema. If this is really the only ground wire, I would avoid using the USB-C power connector and power the RPi from the pins on the large connector instead.

Nevertheless, I think omitting the ground connection between top DC-DC module and RPi is not a good design.

There's missing ground connection between RPi and top DC-DC converter on the diagram...

I suppose it's done through the common ground wire from a single 12V PSU but if not, it could behave very strange.

OK, but if you care so much about security, then LE is not really the best choice for your use cases...

You may lock the working Tvheadend server & client add-ons at working release to avoid automatic updates and do it manually.

BTW. I don't know if it's your case but avoid using Tvheadend server 4.3, use release 4.2 instead.

There's an incompatibility with Kodi so despite the subtitles are present in the stream (and other apps like VLC can display them), Kodi can't sometimes (depends on the stream provider) display them from live stream (playing recorded stream is OK including subtitles) when TvH 4.3 is used.

The same with LE 11 nightly-20230113-4c5c570

[103973.761646] rpivid feb10000.codec: PPS changed

[103973.762687] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103975.892736] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103978.026128] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103980.159510] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103980.159536] usb 1-1.2.3: dvb_usb_v2: streaming_ctrl() failed=-110

[103980.164800] rpivid feb10000.codec: rpivid_h265_stop

[103982.292944] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103984.426400] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103986.559761] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103988.693159] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103990.826595] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103992.959981] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103995.093501] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103997.226777] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[103999.361068] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[104001.493659] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

MyGica DVB-T2 USB adapter is now unusable with LE 11

Look here: https://kodi.wiki/view/List_of_built-in_functions

use kodi-send to send an appropriate command to Kodi.

I believe this feature request is very easy to implement and from my point it makes sense - so the question is - could you please to do it?

As described here:

Post

RE: Basic backup/restore question

I have made an extended backup script which also stores the /flash/config.txt file.

The standard Restore Backup from Kodi's GUI menu Settings-LibreELEC-System-Backup works but the /flash/config.txt file is not restored as the /flash folder is mounted as r/o by default.

I believe it would be useful when the restore part of the official backup-restore script could contain the mount -o remount,rw /flash command before tar command (between lines 33 and 34).

ghtester

November 27, 2022 at 10:01 PM

The current backup procedure does not save any file from the /flash folder but at least the config.txt is very important and may be customized.

That's my case. I also need to backup some personal folders. That's why I created a customized backup script, compatible with the LE's default restore script. Except the files in the /flash folder because it is write protected (mounted as R/O) by default.

The feature request is (at least) to remount the /flash folder as R/W during the restore. Or perhaps even update the backup part to backup the /flash/config.txt automatically. I believe some other users would appreciate that.

Thanks a lot in advance.

Quote from Morphy

I also have a broadlink universal blaster controlled by Home Assistant but for another room I don't want to have to buy another for something which should work with the built in remote.

Yeah I understand. I am controlling (not just) the LE with (any) preferred IR Remote Control.

In my case it is the different type than my LG original to avoid conflict (in fact I don't control the TV anymore with the original IR RC).

I have created the mapping file for my IR RC (currently Samsung) to be used with ir-keytable and configured irexec to run scripts, bound to selected (usually unused) buttons.

See this post: RE: Remote Control

So it is possible for instance to send a commands to Home Assistant through MQTT and much more.

Standby / Power off CEC functions simply does not work on my old LG TV. Due to other limits, especially non-existing CEC standards (regarding to even most basic functions) across devices, I found CEC unusable for my needs.

Therefore I have created a very simple IR transmit hardware and I am now controlling the mentioned TV with IR commands (through ir-ctl utility) which works perfectly without any CEC limits (and it can control not just TVs but any device with IR remote control).

BTW. tested CEC commands with concurrent OSMC with the same / similar results, just:

CECStandby works as Pause

CECToggleState works as Play/Pause toggle

Look here to learn a possible temporary workaround:

Post

RE: LibreELEC-RPi4.arm-9.2.8.img

[…]

Assuming this is an occasional requirement, if you disable DRM Prime in video acceleration settings first, I believe screenshot will work.

popcornmix

November 6, 2022 at 3:48 PM

nightly-20221220-d479071

[191629.143413] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[191629.160188] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[191629.176883] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[192927.110293] rpivid feb10000.codec: phase1_cb: Post wait: 0xffffffff

[192927.127463] rpivid feb10000.codec: phase1_cb: Post wait: 0xffffffff

[192927.143682] rpivid feb10000.codec: phase1_cb: Post wait: 0xffffffff

[192954.847859] usb 1-1.2.3: dvb_usb_v2: rc.query() failed=-71

[192955.061855] usb 1-1.2.3: USB disconnect, device number 6

[192955.330633] r820t 23-003a: r820t_write: i2c wr failed=-19 reg=0c len=1: f1

[192955.804693] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192956.804750] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192957.804824] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192958.804902] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192959.804977] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192960.805052] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192961.805232] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192962.805325] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192963.805666] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192964.805738] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192965.805815] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192966.805889] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192967.805969] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192968.806048] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192969.806428] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192970.806508] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192971.806590] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192972.806715] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192973.806822] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192974.806896] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192975.806946] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192976.807001] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192977.807072] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192978.807145] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192979.807222] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192980.807293] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192981.807364] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192982.807438] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192983.807510] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192984.807582] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192985.807666] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[192986.807740] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

....

....

.....

.....

[194046.890247] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[194047.890341] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[194048.890403] r820t 23-003a: r820t_read: i2c rd failed=-19 reg=00 len=4: f1 5d 7a 1f

[194049.307364] r820t 23-003a: r820t_write: i2c wr failed=-19 reg=06 len=1: b1

[194049.309619] r820t 23-003a: destroying instance

[194049.312272] dvb_usb_v2: 'Astrometa DVB-T2:1-1.2.3' successfully deinitialized and disconnected

[194049.538224] usb 1-1.2.3: new high-speed USB device number 8 using xhci_hcd

[194049.541745] systemd-journald[310]: Data hash table of /run/log/journal/877ce4b44928576324bb64375caf6b34/system.journal has a fill level at 75.1 (1537 of 2047 items, 524288 file size, 341 bytes per hash table item), suggesting rotation.

[194049.541768] systemd-journald[310]: /run/log/journal/877ce4b44928576324bb64375caf6b34/system.journal: Journal header limits reached or header out-of-date, rotating.

[194049.655522] usb 1-1.2.3: New USB device found, idVendor=15f4, idProduct=0131, bcdDevice= 1.00

[194049.655545] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[194049.655552] usb 1-1.2.3: Product: dvbt2

[194049.655559] usb 1-1.2.3: Manufacturer: astrometadvbt2

[194049.663486] usb 1-1.2.3: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state

[194049.822230] usb 1-1.2.3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer

[194049.822284] dvbdev: DVB: registering new adapter (Astrometa DVB-T2)

[194049.822301] usb 1-1.2.3: media controller created

[194049.823994] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.

[194049.844763] i2c i2c-22: Added multiplexed i2c bus 23

[194049.844798] rtl2832 22-0010: Realtek RTL2832 successfully attached

[194049.854807] mn88473 22-0018: Panasonic MN88473 successfully identified

[194049.854948] usb 1-1.2.3: DVB: registering adapter 5 frontend 0 (Realtek RTL2832 (DVB-T))...

[194049.854984] dvbdev: dvb_create_media_entity: media entity 'Realtek RTL2832 (DVB-T)' registered.

[194049.855275] usb 1-1.2.3: DVB: registering adapter 5 frontend 1 (Panasonic MN88473)...

[194049.855299] dvbdev: dvb_create_media_entity: media entity 'Panasonic MN88473' registered.

[194049.855489] r820t 23-003a: creating new instance

[194049.862459] r820t 23-003a: Rafael Micro r820t successfully identified, chip type: R828D

[194049.862520] r820t 23-003a: attaching existing instance

[194049.867375] r820t 23-003a: Rafael Micro r820t successfully identified, chip type: R828D

[194049.873534] rtl2832_sdr rtl2832_sdr.2.auto: Registered as swradio0

[194049.873560] rtl2832_sdr rtl2832_sdr.2.auto: Realtek RTL2832 SDR attached

[194049.873572] rtl2832_sdr rtl2832_sdr.2.auto: SDR API is still slightly experimental and functionality changes may follow

[194049.884539] Registered IR keymap rc-astrometa-t2hybrid

[194049.884684] rc rc2: Astrometa DVB-T2 as /devices/platform/scb/http://fd500000.pcie/pci0000:00/000…/1-1.2.3/rc/rc2

[194049.884878] rc rc2: lirc_dev: driver dvb_usb_rtl28xxu registered at minor = 2, raw IR receiver, no transmitter

[194049.885039] input: Astrometa DVB-T2 as /devices/platform/scb/http://fd500000.pcie/pci0000:00/000…3/rc/rc2/input4

[194049.885380] usb 1-1.2.3: dvb_usb_v2: schedule remote query interval to 200 msecs

[194049.893558] usb 1-1.2.3: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected

[194050.081504] input: eventlircd as /devices/virtual/input/input5

[194054.133910] usb 1-1.2.3: DVB: adapter 5 frontend 0 frequency 0 out of range (174000000..862000000)

[194054.738647] mn88473 22-0018: downloading firmware from file 'dvb-demod-mn88473-01.fw'

[194055.380340] usb 1-1.2.3: DVB: adapter 5 frontend 1 frequency 0 out of range (42000000..1002000000)

[194061.527528] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0

[194061.544059] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[194061.577107] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[194061.594200] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[194066.339629] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0

[194066.339657] rpivid feb10000.codec: Missing DPB ent for col

[194066.339926] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[194066.340277] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[194066.340468] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

[194083.848780] rpivid feb10000.codec: rpivid_h265_stop

[194086.303269] rpivid feb10000.codec: rpivid_h265_start: (1024x544)

[194086.306228] rpivid feb10000.codec: SPS changed

[194086.306251] rpivid feb10000.codec: PPS changed

Check the Kodi's Settings - System - Input - Peripherals menu. You should see the CEC Adapter there.

Look here: RE: Hauppauge WinTV-quadHD USB not recognized in TVHeadEnd on RPi4-8GB

If the issue already disappeared, please mark this thread as Resolved.

I would say now you need to enter the custom URL just like this: https://test.libreelec.tv

OK, I have a different HW so also the drivers may be different. I have no lirc.conf file. But I would check with the irw utility if your scancodes are mapped properly to commands. And if not, check the /storage/.config/rc_maps.cfg file and the mapping file which is the rc_maps.cfg pointing to.

If you don't have these files on your filesystem, then .