Posts by afl1

Quote from jxt

afl1

I did a clean install on the sdcard, did not help.

I made a log. Please see, as it becomes time.

Thank you

It looks like issue in tvheadend.

2017-08-21 17:16:47.732 [WARNING] linuxdvb: Availink avl6862 #0 : DVB-S #0 - retune
2017-08-21 17:16:49.122 [WARNING] TS: 36E/12341L/СТС Transport error indicator (total 1)
2017-08-21 17:16:51.749 [  ERROR] descrambler: ECM - key late (7507 ms) for service "СТС"
2017-08-21 17:16:57.224 [   INFO] subscription: 0003: "127.0.0.1 [  | Kodi Media Center ]" unsubscribing from "СТС", hostname="127.0.0.1", username="127.0.0.1", client="Kodi Media Center"
2017-08-21 17:16:57.226 [   INFO] mpegts: 12015.18R in 36E - tuning on Availink avl6862 #0 : DVB-S #0
2017-08-21 17:16:57.462 [   INFO] subscription: 0006: "127.0.0.1 [  | Kodi Media Center ]" subscribing on channel "THT HD", xweight: 150, adapter: "Availink avl6862 #0 : DVB-S #0", network: "36E", mux: "12015.18R", provider: "HTB+", service: "THT HD", profile="htsp", hostname="127.0.0.1", username="127.0.0.1", client="Kodi Media Center"
2017-08-21 17:17:09.087 [WARNING] subscription: 0006: service instance is bad, reason

Try to use this version:

service.tvheadend42-8.2.112e.zip

Also you can try to use my testing version corresponding to LE 8.1.5

LibreELEC-S905.arm-8.2-devel-201708221034-g8c1f5c4-I.img.gz

This version is built for KI Pro, you have to replace dtb.img with nougat dtb: Index of /s905/8.2/device_trees/

In this version are some fixes for amlogic rendering and controlling amlogic codec by kodi.

Quote from sauna

Hi afl1.can you build on the amiko a4 dvb-s2 libreelec version with the support of s2?

No, there is no public linux driver for m88dm6000.

Quote from jxt

Hi afl1

You will no longer collect firmware for s905?

On firmware from kzaq since version 8.1.0 on power-up, tvheadend shows satellite channels (dvb-s2) for 10-15 seconds and the picture freezes. Then there is no signal. If you reboot K1 plus, then all the channels work fine.

On your firmware this was not.

Thank you!

There is no issue with tvheadend and LE 8.2 versions . I've been verified version 8.1.5 on my KI Plus and there are no channel freezes for DVB-S2.

Try clean installation on new SD card.

I stopped building LE 8.x as internal dvb driver is included in kszaq builds and there is no reason to build parallel versions.

P.S.:

For serious reporting provide debug logs from kodi and tvheadend.

Quote from nmadrane

Oh I see, I forgot to mention that I am using VDR (not TVHeadend). Is there a generic way to scan, independently of TVHeadend or VDR ?

No other way for KII Pro.

Quote from nmadrane

Hi AFL, thanks for your feedback. So what is the prefered way to scan for DVB-T or DVB-T2 channels with your version ?

In Tvheadend select for Network: 'Pre-defined muxes' and for Network discovery: 'New muxes + changed muxes'. Also verify parameters for predefined muxes, for some country this db is outdated.

Quote from nmadrane

Hi,

I am using 8.0.1i. Quite old but anyway...

I am trying to scan DVB-T frequencies with w_scan (I have a KII Pro with DVB-S2/T2)

I am running the following command :

w_scan -c MA

But w-scan is not able to get any frequency. Here is what I get :

Code

w_scan version 20141122 (compiled for DVB API 5.10)
using settings for MOROCCO
Country identifier MA not defined. Using defaults.
scan type TERRESTRIAL, channellist 4
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
        /dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Availink avl6862": very good :-))

Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.10
frontend 'Availink avl6862' supports
DVB-T2
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
FREQ (0.95MHz ... 2.15MHz)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Scanning DVB-T...
Scanning 7MHz frequencies...
177500: (time: 00:00.000)        skipped: (freq 177500000 unsupported by driver)

initial_tune:2710: Setting frontend failed QAM_AUTO f = 177500 kHz I999B7C999D999T999G999Y999 (0:0:0)
184500: (time: 00:00.000)        skipped: (freq 184500000 unsupported by driver)

initial_tune:2710: Setting frontend failed QAM_AUTO f = 184500 kHz I999B7C999D999T999G999Y999 (0:0:0)
191500: (time: 00:00.000)        skipped: (freq 191500000 unsupported by driver)

initial_tune:2710: Setting frontend failed QAM_AUTO f = 191500 kHz I999B7C999D999T999G999Y999 (0:0:0)
198500: (time: 00:00.000)        skipped: (freq 198500000 unsupported by driver)

Display More

Same output with 8 Mhz frequencies.

Any idea ?

Display More

The way have is done scan in w_scan is unsupported in my driver.

I can't compare Android driver, there are no sources for it. I use for tuner (Rafael R848) driver from crazycat media_build. Verify parameter for transponders and try to use better LNB.

In box KIII Pro (S912) with Android 7.1.1 this issue is presented.

Quote from okra

The tuner does not see my DVB-S tuner, it's just a DVB-T tuner

Have you installed service.tvheadend42-9.0.112e.zip. from zip?

TVheadend from LE repository behaves as you reported above and it doesn't work even for DVB-T.

LE test build with the latest Kodi Leia 18.0-Alpha1 and Nougat kernel (kszaq).

LibreELEC-S905.arm-9.0-devel-201708140759-gb649026-I.img.gz

This build is built for KI Pro, for other S905 device replace dtb (Nougat) in SD.

Installing new addon services is broken. After installing new services (tvheadend, oscam, ...) run vias ssh script 'fixaddonservices' and reboot box.

pvr.hts is already preinstalled you need only enable it.

TVheadend42 in Raybuntu repository is broken use service.tvheadend42-9.0.112e.zip.

You can use this .img for upgrade already prepared SD card putting it to /storage/.update.

If you upgrading from MM version don't forget add Nougat dtb in /storage/.update.

For older TV or DVI connection switch to RGB use following ssh command and reboot box.

echo "echo 'rgb,8bit' > /sys/class/amhdmitx/amhdmitx0/attr" > /storage/.config/autostart.sh

Don't install this version to internal NAND. This is only pre alpha version. There are massive frame skippings UHD fps > 30.

For live debug info use keyboard shortcut Shift-Ctrl-O.

Netflix/Amazon Prime VOD Support

Run the following:

curl -Ls http://nmacleod.com/public/libreelec/getwidevine.sh | bash

Then install one of the following addons:

Netflix addon or install netflix repository from "LibreELEC Addon" repository, and install "netflix" from the netflix repository.

Amazon Prime VOD addon

Quote from Newtman

Hi afl1,

A friend with the some problem just open an issue in TVH.

Look here:

ATSC_C and DVB_C malfunction - Tvheadend

Is really uncomfortable use DVB-C Annex B as ATSC-C... The zapping is too slow and the channels haven't got name.

kszaq, pls, compile tvheadead42 with patch tvheadend42-04_dvb_c_annexB.patch to test fix for this issue. Currently I am unable to build addons for LE 8.2.

THX

Quote from Newtman

Hello kszaq , I'm TVH + Kodi + TBS 6522 user and now I bought a KI Pro. My principal use is with DVB-C Annex B provider, I know is a "rare" standard but supported by your LibreELEC but with few issues.

When crazycat developed the TBS6522 support for annex B I found the some issues.

The first problem is the frontend, TVH detect my provider as ATSC-C, not DVB-C in consecuence I can't import my configuration from TVH (PC) to the KI Pro.

Second, TVH can't detect channel names.

Both problems were present in crazycat's drivers before he solve the frontend of it.

Here a log of the problem:

subscription: 0003: "scan" subscribing to mux "489MHz", w-eight: 5, adapter: "Availink avl6862 #0 : ATSC-C #0", network: "Provider ATSC-C", service: "Raw PID Subscription"

linuxdvb: Availink avl6862 #0 : ATSC-C #0 - poll TIMEOUT

linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 61 [e=Operation not permitted]

linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 63 [e=Operation not permitted]

linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 64 [e=Operation not permitted]

linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 67 [e=Operation not permitted]

linuxdvb: Availink avl6862 #0 : ATSC-C #0 - failed to config dmx for pid 4385 [e=Operation not permitted]

inuxdvb: Availink avl6862 #0 : ATSC-C #0 - poll TIMEOUT

mpegts: 489MHz in Provider ATSC-C - scan complete (partial - 32/1 tables)
subscription: 0003: "scan" unsubscribing

Is possible solve it?

Thanks!

Display More

Tvheadend is different project, for principal issues you have to complain on tvheadend forum. But I had the same question on tvheadend forum and Jaroslav Kysela explain me: ATSC-C means DVB-C Annex B. BTW there is no standard ATSC-C, this is only introduced by tvheadend.

Quote from Hans Gruber

Thanks for the reply. I do have a roof aerial (which I'm pretty much stuck with for now) but do get the occasional glitch on HD signals using the tuner built-in to the TV so there could be some signal issues. I think I'm only about 12 miles from the transmitter with not much in between. Could it be that my old USB tuner is more sensitive and works better with a weaker signal? I could plug the old tuner in but I went for the KI Pro to remove some of the cables hanging out the box. I'll attach my service.log just in case it shows up anything useful/interesting.

Oh also unrelated to this issue I noticed that the HDMI cable supplied with the KI Pro wouldn't supply any CEC data, changing cables fixed it but it seemed a bit odd.

I see from log there are issues only with 745.8 and 777.8. They only use mode DTG-3, all other muxes use DTG-6 or DTG-8. I am sure issue is in weak signal. Changing little bit frequency can improve signal. Most important is SNR. Verify it in tvheadend->Status->Stream for every mux. SNR have to be >25 dB

Quote from Hans Gruber

I've just got a KI Pro to replace a Mini MX III with an external USB DVB-T tuner but I'm having a bit of an issue in TVHeadend. The muxes on frequencies 745.833Mhz and 777.833Mhz are failing to scan on the KI Pro, but not on the old box using a "Silicon Labs Si2168" adaptor. If I manually choose 746Mhz and 778Mhz it scans ok but the network discovery thing seems to want to add back the old frequencies. It also seems to be duplicating some of the channels but assigning different channel numbers to them.

Same results with kszaq's 8.1.3 and 8.0.2e releases. I'm in UK using the Tacolneston transmitter (Tacolneston (Norfolk, England) Full Freeview transmitter | UK Free TV 📺). I'm attaching the logs but I'm not sure if they're the right ones, and sorry if my explanation doesn't make much sense! :p

Any ideas?

edit: I think the duplicate channel thing might be unrelated. It seems some channels are being moved around by Freeview.

You can disable network discovery in tvheadend. I verified predefined muxes in tvheadend for Tacolneston, UK and the data are correct. Most likely issue is in weak signal. Try to use antenna with better gain.

P.S.

For fixing issues in tvheadend you have to add log from tvheadend:

/storage/.kodi/userdata/addon_data/service.tvheadend42/service.log

Quote from ozkaradag

Greetings,

TVHeadend Server now works correctly, thanks afl1.

But now PVR TVH is not installed and the existing one is not deleted.

Best regards...

Display More

Try this one: pvr.hts-999.4.1.2.2.zip

Quote from ozkaradag

Greetings,

I found the Mecool K1 Pro, a nice device.

I set this image up, but the TVHeadend inside the repo recognizes the tuner only as DVB-T.

How can I fix it?

Or what can I do?

Thanks in advance.

Best regards...

Display More

Tvheadend in GDPR-1 repositories is broken. Use this service.tvheadend42-9.0.1.112d.zip .

Quote from zbigzbig20

afl1 , now your builds with nougat kernel supports wetek dvb again? codesnake fixed this driver . I tested it on kszaq test build with nougat kernel and works nice

I stopped build Krypton versions (LE 8.x) as there are fully supported internal dvb driver in versions by kszaq. Also Krypton development stopped, there are no fixes for rendering (skipped frames). I am following Leia development, but there are CPU performance issues in rendering. Only S912 versions has acceptable builds for now.