Descrambling has nothing to do with Kodi. If Tvheadend descrambled it, Kodi get a clear stream.
Likely you see at your OScam log what is wrong.
Descrambling has nothing to do with Kodi. If Tvheadend descrambled it, Kodi get a clear stream.
Likely you see at your OScam log what is wrong.
provide_logfile#tab__via_libreelec_settings_add-on
ERROR: PulseAudio: Waited for the Context but it failed
NOTICE: PulseAudio might not be running. Context was not created.
not sure what happen here, from log PulseAudio waits 30sec because audio fails
Remember doing an migration from 4.0 -> 4.2 can create weird bugs/problems, also you probably don't use the new db format that fixes a lot stuff for RPi/SD Card usage. Just to be warned.
usb 1-1.3.2: device descriptor read/64, error -110
usb 1-1.3.2: new high-speed USB device number 8 using dwc_otg
usb 1-1.3.2: device descriptor read/64, error -110
usb 1-1.3.2: device descriptor read/64, error -110
usb 1-1.3.2: new high-speed USB device number 9 using dwc_otg
usb 1-1.3.2: device descriptor read/8, error -110
usb 1-1.3.2: device descriptor read/8, error -110
usb 1-1.3.2: new high-speed USB device number 10 using dwc_otg
usb 1-1.3.2: device descriptor read/8, error -110
usb 1-1.3.2: device descriptor read/8, error -110
hub 1-1.3:1.0: unable to enumerate USB device on port 2
usb 1-1.3.3: new high-speed USB device number 11 using dwc_otg
usb 1-1.3.3: device descriptor read/64, error -110
usb 1-1.3.3: device descriptor read/64, error -110
usb 1-1.3.3: new high-speed USB device number 12 using dwc_otg
usb 1-1.3.3: device descriptor read/64, error -110
usb 1-1.3.3: device descriptor read/64, error -110
usb 1-1.3.3: new high-speed USB device number 13 using dwc_otg
usb 1-1.3.3: device descriptor read/8, error -110
usb 1-1.3.3: device descriptor read/8, error -110
usb 1-1.3.3: new high-speed USB device number 14 using dwc_otg
usb 1-1.3.3: device descriptor read/8, error -110
usb 1-1.3.3: device descriptor read/8, error -110
hub 1-1.3:1.0: unable to enumerate USB device on port 3
Display More
... hmm looks like driver error
at S905x not much I can do
you have to compare lsmod before and after the suspend, this needs to be identical
I would bet dvb_usb_v2nd dvb_core could be removed.
Btw you can try it without suspend:
systemctl stop service.tvheadend42
lsmod | paste
modprobe -r MODULENAME1
modprobe -r MODULENAME2
....
lsmod | paste
^^^ note/keep open
modprobe MODULENAME2
modprobe MODULENAME1
....
lsmod | paste
^^^ compare with the first lsmod if every module is loaded again (should be identical)
Not that i would know, but remember that multiple pvr clients are not supported and known to be broken.
Normally 1sec is already enough BUT who knows what's wrong so try 5sec. If this works reliable lower the value.
Even with fu slow devices 5dec should be more then enough.
If you still get the problems try to get a log after the problem appears.
dmesg | paste via shell
Is it at restart or do you use suspend/standby?
Pls also try to just use the delayed start of Tvh instead to wait for the tuners.
I believe I have seen the counter is increasing while viewing one channel for a longer time and this is not normal.
a low count is not problematic (this results in no error at the stream), if you have 10/minute or something it is still okay
no idea why this happens at newer kernels, maybe older kernels hide this error or newer kernel are worse in some aspect - no idea
he "Continuity errors" are still there e.g. 20
as long this errors are appearing only one time and are not endless increasing this is completely okay, those errors are normal - just switch channels then you have those errors
but this changes should go into official releases ASAP
not possible as it would break it for other people
With LE9 you can choose between "standard" and additional drivers - so it should be fixed there.
Could you also refresh with Kodi 17.6 aka 8.2.1, please?
yes need to rebuild a bit and include the xbox driver then I push a release
vm was full ;D currently rebuilding
I'm pretty sure the answer is NO
and you are right
hmm then this "should" be normal, I would bet at not that good reception - but not that easy to really figure out the problem here