Yes I can confirm it works fine if you push 'o' button on keyboard, it can also be displayed / hide with console commands:
kodi-send -a 'Playerprocessinfo'
or
kodi-send --button=o
The debug info can be activated / deactivated through CTRL+SHIFT+O
or by:
kodi-send -a 'PlayerDebug'
Display MoreThe PI 2 had some problems with 1080p streams. After a overclock and turning off de-interlacing, it runs finally smoothly.
The Pi 3 had never such issues. It runs perfectly.
The Pi 4 has still some jittering/running on slow motion and the GUI has some flicker problems.
...
Overall, nothing really works. The GUI flickering is still a problem and UHD streams are still running not smoothly.
Could it just be a big malfuction at all PI4s beause even after a years, there is still no real funcional graphics driver?
You don't say which LE you are running and which stream is it and it is very important to know what's a current capability of your HW and SW to achieve expected results.
I wouldn't say all RPi 4 devices are malfunctioning, it's a great piece of HW for such a low price. Most likely, as it is still a bit new device, the SW still needs to be finalized to fully utilize the HW. RPi 3 is already finished in this matter, RPi 4 not yet but the developpers are doing a great job and there are many updates in nightly LE builds so it will be better and better
Read this post, it's from January so may not reflect the progress, but you may learn something: RE: Raspi 4B 4G stuttering + tearing
How do you disable one tuner, other than through the tvh software which likely doesn't turn it off, it just doesn't use it?
Yes, if the utility software (through which you are changing the transfer modes etc.) does not allow to do it at hardware level, at least in Tvheadend server uncheck Enabled: checkbox for one of demodulators in Configuration - DVB Inputs - TV adapters - ....ATSC#2 - Basic settings
It should be possible to do it somehow at driver level but can't say how-to details remotely.
JO above talked about the the Si2151 as being a very compatible tuner, but I can't find it anywhere to buy.
Si2151 is a radio chip inside your (and many others) TV stick, it's not a complete TV tuner.
OK, thanks a lot for your reaction.
The seeking issues I have encountered were like sometimes the 'cursor' jumped outside the Timeshift window borders when I tried to move back or forward and then it was jumping back only (to nonsense minus values) even if I wanted move forward. So the only solution was to stop playing the channel and start again (so whole Timeshift data were lost).
I would say that main reason why it happens is a temporary bad signal (this happens as I have indoor antenna only) so the data stream suffer some corruption. Then also the Timeshift may have unpredictable behavior (but should not perhaps jump outside borders anyway). I'll see if there's any change in latest builds or not (I understand it should be still the same for H265 but who knows 
).
I still had an occasional seeking issues with H265 (using Live TV and Timeshift in RAM only) on recent LE 9.80 nightly builds, I supposed to be the Tvheadend 4.2's issue but perhaps I don't understand how it works together...
It's a bit older thread and I have not tested if it's still valid but you may try:
RE: Can I add WiFi config to SD card pre-install? (headless setup)
If you can't change the wi-fi password at all (at least temporarily), you may also finish the setup with some another / temporary wi-fi AP, perhaps using mobile hotspot at your phone. Then maybe connect through SSH and try steps outlined here (but it's even older thread):
I can confirm an issue with special characters that can't be used also for 'tethered' Wireless Access Point names.
...the tuner functionality in LibreELEC is passing a signal.
Well, in general it's true but I don't think the tuner itself is an issue here.
More likely the demodulator LG LGDT3306a or the Empia EM28274 USB controller which may need a specific settings. I would say it should be possible to make this stick working properly but it's necessary to try everything we recommended here... Connecting through an USB hub with external power supply. Try connecting to both USB 3.0 / USB 2.0 ports. Try both bulk / isochronous transfer modes. Try disabling one tuner. Try another LE build (newest 9.80 nightly or an older 9.2.5 with CrazyCat drivers). And try all possible combinations... Yes it's a lot of testing to do but there should be a solution.
Look here: Geniatech / Mygica A681 ATSC USB tuner
As per my good experiences with Geniatech / MyGica DVB-T2 tuners, I would perhaps give this vendor a try.
There is also forum at their site which you can visit and ask questions there before you buy. And you can always return the device if it won't work.
If it's original 15W adapter, it should be OK otherwise you would see a yellow lightning flashing in right top screen corner.
But the question is if the USB stick is not at the USB port's power limit... As recommended earlier, consider trying an USB hub with external power supply adapter (even USB 2.0 should be enough), it's always good to have it even if it won't fix this issue.
Before that, try to disable one tuner and check if it won't help.
ATSC, DTMB, DVB-T/DVB-T2, and ISDB-T - Digital Terrestrial Television (DTT)
NTSC perhaps not = analog = obsolete
DVB-T2 not for North America I don't think.
All the sticks I mentioned also supports DVB-T and Astrometa also supports analog TV / SDR but of course I don't know what's the status in your location.
Edit: Ahh, just looked at your tuner so it's ATSC. See the comparison: 201908_dvb_and_atsc3_compared_infographic_a5.pdf
So you can't realy use any tuners we mentioned here...
It looks you already gave it up so the last advice - I would try to disable one tuner and check if there's any change...
Also make sure you have the latest USB firmware installed on your RPi 4B ( see RE: Is it possible already to set up a rpi4 with kernel 5.4? ). There're some updates regarding to isochronous transfers in past as well.
And do not underestimate the power for your devices, it's really important.
Regarding to another DVB-T2 sticks, I am using MyGica T230C, T230C2 and two Astrometa models with Sony & Panasonic demodulators.
T230C / C2 is working best on latest LE versions, with Astrometa I had more struggling but currently it's working also fine for me (and the hardware has some advantages, like SDR functionality and the driver supports all IR protocols).
The problem is - you usually don't know what exactly you'll receive when ordering on eBay / Aliexpress. The stick may look the same but inside the HW is different. But I have ordered MyGica tuners through Aliexpress from original store and negotiated the specific version before.
I would say it's a converter (with an input data file for Germany already present there) which will work for any country (or any specific location).
So if you install DVB Tools add-on, use w_scan in Croatia and put the scan file to that convertor, you should get the Tvheadend's definition file for that specific location. It's not so hard to do it even manually for several channels visible around or edit the current ones (to change the Delivery system from DVB-T to DVB-T2 and a Bandwith appropriately).
Or a wait until somebody refreshes the default definition files.
Kodi only accepts htsp
The client is HTSP so that''s probably why.
Nevertheless, pass is default and also used for recording.
I have never struggled with stream settings as defaults worked. Now I tried to enable the Restart on error: option and disable the Switch to another service: option for both htsp and pass profiles to see if there's any change when the signal level drops...
Possible bad (new) Haupagge tuner?
Well, try the USB 2.0 port as well... USB 3.0 is not always the best choice for some devices. Also, the dual tuner stick is a bit power hungry. There's no extra power reserve on USB ports of RPi 4B, it also depends on your power supply. So you may try to use some USB hub with external power (or make a USB cable fork to bring a hard 5V to your USB tuner).
My tuners sometimes hangs after switching to another channel but it's then visible in dmesg output and in this case USB port power off / on is necessary to make it working again (I suppose the reason is most likely the low power / long USB extension cord issue).
No problem.
I have upgraded to LE 9.80 couple weeks / months ago so you may be in different situation. I am sure I had to reinstall some (or even all) old add-ons (one time, after upgrade from LE 9.2.6 to 9.80 nightly) and I did NOT need to install them from .zip or from another 3rd party source.
Subsequent 9.80 nightly build upgrades are sometimes upgrading the installed add-ons automatcally.
You should be able to visit Kodi Settings - Add-ons - Install from repository - All repositories (or LibreELEC Add-ons Team LibreELEC - 9.80.8 which should be also visible there).
Then (after old versions are uninstalled and device rebooted) install:
> Services - Tvheadend Server 4.2 Team LibreELEC - 9.80.8.125
> PVR clients - Tvheadend HTSP Client Adam Sutton.... 8.1.2.1
BTW. in Settings - System - Add-ons I have enabled Unknown sources and set Update official add-ons from > Official repositories only (default)
If nothing works and you don't mind the current settings, start the fresh LE 9.80 nightly installation from scratch using the .gz image.
Well, in my case the aq drops to zero (sometimes) only when there's a bad DVB-T2 signal reception, then audio stops (and can be recovered only by tuning to another channel or by stopping and starting play on the same channel) but in most cases the video is still running, sometimes in worst cases it also stops.
So from my perspective the audio is more sensitive to data stream corruption than video. I would expect audio could be recovered when the signal level returns to good value but usually it does not happen. As soon as the stream is corrupted, from point of corruption the data is (at least partially) useless - it's visible also when Timeshift is active - as soon as the 'aq=zero' issue happens, after that point audio is silent even if you skip forward, when you return before that point, audio + video is OK.
So the question is - could the data stream suffer a corruption in your case as well? And the wait is due to missing (corrupted) block or is that nonsense?
Don't you see any Transport Errors / Continuity Errors in Tvheadend's Status page on your adapter?
but tvh 4.2 is not compatible,
??? There're Tvheadend Server 4.2 9.80.8.125 and Tvheadend HTSP Client 8.1.2.1 in add-ons list in this build, I suppose you just need to reinstall them if the previous releases persisted after the upgrade.
Maybe there's not only LE... And in this case the 60 GB is really not so much...
I have 40 GB SATA HDD and there's multiboot - RPi OS and LE.
Also for some recordings from Live TV it's always good do have some space.
To show the currently installed bootloader version / config:
rpi-eeprom-update
vcgencmd bootloader_version
vcgencmd bootloader_config
Make sure you have the HDD adapter powered properly (external power is best, although for SSD HDD it should not be necessary but depends on HDD model).
BTW. em28xx is NOT the HDD adapter, this is your DVB-C/T USB stick (which may be also a bit power hungry)
Regarding to newer kernel, you may try the latest test LE 9.80 Nightly build from today which already has 5.10.1 kernel version ( LibreELEC-RPi4.arm-9.80-nightly-20201219-c7aa22f.tar )
The firmware version check / update can be easily done from Kodi - Settings - Libreelec - Updates - Firmware Updates
An alternative upgrade to the latest USB firmware:
cd /tmp
wget -c https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware-2711/latest/vl805-000138c0.bin
rpi-eeprom-update -u /tmp/vl805-000138c0.bin
reboot
#An alternative upgrade to the latest (stable) bootloader:
cd /tmp
wget -O pieeprom.bin -c https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware-2711/latest/pieeprom-2024-05-17.bin
rpi-eeprom-config pieeprom.bin > bootconfDefault.txt
# default config
cat bootconfDefault.txt
vcgencmd bootloader_config > bootconf.txt
# current config
cat bootconf.txt
rpi-eeprom-config /tmp/pieeprom.bin --config /tmp/bootconf.txt --out /tmp/pieeprom
rpi-eeprom-update -d -f /tmp/pieeprom
reboot
#Edit (2022-08-05) - bootloader link updated to current stable version
Edit (2024-06-06) - USB firmware and bootloader links updated to latest available versions
- added -u parameter to USB firmware update command which is now necessary