TvHeadend Not Working


#12

Thanks @grahamh, just checked that in the configuration and the Sony DVB-T is the only one enabled.

Any other thoughts as to how I can fix my issue? Because as far as I can tell, I have performed all installation and setup correctly…

My thoughts at this stage are:

  1. Faulty tuner

  2. Corrupted OSMC installation

  3. Corrupted SD card

But I really don’t know tbh


#13

Some hints from my experience:

  1. These USB sticks (I have 3 of different makes) are not as sensitive as the tuners in TVs. Just because you get a good signal for your TV doesn’t mean it’s good enough for a USB stick. If I use just one stick, the signal can be be marginal - I now have an aerial amplifier to feed two sticks and TV at the same time. Also, make sure you have got decent aerial cabling. http://www.aerialsandtv.com/cableandleads.html

  2. For some reason, if you ever enable then disable the Realtek tuner things go wonky. The fix is to wipe just the hardware configs and re-tune:

    sudo systemctl stop tvheadend
    rm ~/.hts/tvheadend/input/linuxdvb/adapters/*
    sudo systemctl start tvheadend


#14

Thanks for that information @grahamh.

  1. I understand that this is the case and have read a little about USB tuner sensitivity. However I don’t feel that this explains why I had signal before and not now (also back when the signal was coming through, I was experimenting with using a UHF amplifier and it didn’t seem to make any discernible difference to the signal so I stopped using it). I feel that something else is wrong (be it hardware, software or config). When it was coming through, the signal wasn’t perfect, but it was definitely watchable. Now suddenly I am unable to get any signal at all and am unable to watch anything.

  2. Thanks for this suggestion. I don’t think I have enabled the Realtek tuner, but it’s definitely worth a try (I’m willing to try just about anything at this point). How do I re-tune without running the whole setup wizard again? Or is that what I need to do?


#15

Actually, if you already have channels scanned, there is no need to re-tune those. What I suggested doesn’t wipe the tuning data. It should (!) gradually pick up any channels you were missing.

Thought: You could also try a powered hub in case it’s not getting enough juice.

Yeah, I’ve had a few of these things. I can never actually measure any improvement in signal level, but since installing the latest I’ve never seen any picture breakup/blocking which was happening too often before.


#16

OK, I’ll give that a go when I get home tonight :slightly_smiling_face:.

An interesting thought. I’ll see if I can give that a go as well. Thanks for the suggestion.


#17

Thanks again for your suggestion @grahamh, I have run the above commands and all three tuners show up as expected. I have now enabled the Sony DVB-T however when I attempt to watch a channel it now says “No free adapter available” :confused:


#18

Really though I don’t think I should need to go in and manually remove adapters etc if I have completely removed and reinstalled the entire TvHeadend OSMC app multiple times. Each time I did that I should have been starting with a fresh instance of the program.

Also in terms of powered hubs and aerial amplifiers, I’m open to forking out money to improve signal and quality. However the key word there is “improve”. I’m not getting any signal at all and I am on my TV. So I guess I’m not really happy to spend on additional devices on the maybe that it’ll “improve” my issue.


#19

Nope, removing the APP will not remove the config at all.


#20

True, but running this command

before removing the app (which I did each time) should. Correct?


#21

As you know, with digital, you pretty much have a signal or you don’t, and the cliff-edge is steep.

I guess it’s possible you do have a duff stick, since you say it worked at first (presumably all conditions the same as now), but only @sam_nazarko can deal with that.


#22

Looking at the image you don’t have a network assigned to the adaptor.


#23

damn could have seen that, well spotted :slight_smile:


#24

A good point, I guess I did know that, but had forgotten.


#25

Yes @rantanplan1, quite right, it was well spotted. Thanks @the_bo, that has resolved the “No Signal” and “No free adapter available” issue :slightly_smiling_face:. I remember configuring that when I went through the initial setup wizard, so when I removed the adapter config it must have been removed.

Excited by the fact that I was actually able to watch something I left it on a channel to see how well it performed. It seemed to be doing pretty well and then suddenly froze.

I looked at the TvHeadend WebGUI and saw that it was indicating that it had signal. But on the Status/Subscription page I noticed that there were a lot of errors

So I looked at the TvHeadend logs available through the GUI and there is just this repeating over and over:

2019-01-15 05:59:58.003 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Corrupted PES header (errors 967)
2019-01-15 05:59:59.318 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 10071)
2019-01-15 06:00:00.492 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2194)
2019-01-15 06:00:00.765 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 239340)
2019-01-15 06:00:01.443 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 73156)
2019-01-15 06:00:02.901 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 131)
2019-01-15 06:00:08.335 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769: Invalid start code ec:09:81
2019-01-15 06:00:09.518 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 10196)
2019-01-15 06:00:10.593 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2215)
2019-01-15 06:00:10.784 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 242891)
2019-01-15 06:00:11.463 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 74247)
2019-01-15 06:00:13.301 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 134)
2019-01-15 06:00:18.982 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769: Invalid start code 20:08:8c
2019-01-15 06:00:19.559 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 10340)
2019-01-15 06:00:20.667 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2245)
2019-01-15 06:00:20.768 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 247433)
2019-01-15 06:00:21.489 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 75954)
2019-01-15 06:00:26.313 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 136)
2019-01-15 06:00:29.136 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769: Invalid start code 0d:e2:6f
2019-01-15 06:00:29.594 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 10514)
2019-01-15 06:00:30.804 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 252999)
2019-01-15 06:00:30.848 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2293)
2019-01-15 06:00:30.954 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Corrupted PES header (errors 59)
2019-01-15 06:00:31.501 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 77884)
2019-01-15 06:00:38.262 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 145)
2019-01-15 06:00:39.491 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769: Invalid start code 9e:bb:a6
2019-01-15 06:00:39.608 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 10701)
2019-01-15 06:00:40.830 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 258464)
2019-01-15 06:00:40.861 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2341)
2019-01-15 06:00:41.492 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 80002)
2019-01-15 06:00:42.194 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770: Invalid start code 2a:1b:48
2019-01-15 06:00:48.430 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 150)
2019-01-15 06:00:49.504 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769: Invalid start code d7:ab:83
2019-01-15 06:00:49.713 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 10924)
2019-01-15 06:00:50.821 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 264074)
2019-01-15 06:00:50.917 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2405)
2019-01-15 06:00:51.496 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 82030)
2019-01-15 06:00:52.920 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770: Invalid start code 1a:b8:ef
2019-01-15 06:00:59.711 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 11155)
2019-01-15 06:01:00.643 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Corrupted PES header (errors 1078)
2019-01-15 06:01:00.827 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 269899)
2019-01-15 06:01:01.439 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2471)
2019-01-15 06:01:01.529 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 84253)
2019-01-15 06:01:01.704 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 158)
2019-01-15 06:01:06.734 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770: Invalid start code b0:f8:63
2019-01-15 06:01:09.718 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 11396)
2019-01-15 06:01:10.655 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Corrupted PES header (errors 1110)
2019-01-15 06:01:10.863 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 275905)
2019-01-15 06:01:11.505 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2536)
2019-01-15 06:01:11.552 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 86406)
2019-01-15 06:01:12.629 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 162)
2019-01-15 06:01:16.840 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770: Invalid start code 9d:21:83
2019-01-15 06:01:19.738 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 11600)
2019-01-15 06:01:20.806 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769: Invalid start code 66:0c:7c
2019-01-15 06:01:20.857 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 281049)
2019-01-15 06:01:21.508 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2592)
2019-01-15 06:01:21.542 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 88149)
2019-01-15 06:01:29.600 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 168)
2019-01-15 06:01:29.881 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 11797)
2019-01-15 06:01:30.861 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 286193)
2019-01-15 06:01:30.862 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Corrupted PES header (errors 1156)
2019-01-15 06:01:31.518 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2632)
2019-01-15 06:01:31.550 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 89891)
2019-01-15 06:01:34.869 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770: Invalid start code 4f:6d:9e
2019-01-15 06:01:39.891 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 11982)
2019-01-15 06:01:40.895 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 290794)
2019-01-15 06:01:41.158 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Corrupted PES header (errors 1175)
2019-01-15 06:01:41.566 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 91261)
2019-01-15 06:01:42.072 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2684)
2019-01-15 06:01:45.011 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770: Invalid start code 75:0f:19
2019-01-15 06:01:49.228 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 173)
2019-01-15 06:01:50.076 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 12147)
2019-01-15 06:01:50.876 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 294971)
2019-01-15 06:01:51.570 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 92701)
2019-01-15 06:01:51.757 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Corrupted PES header (errors 1198)
2019-01-15 06:01:52.497 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2739)
2019-01-15 06:02:00.342 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 12254)
2019-01-15 06:02:00.893 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 297543)
2019-01-15 06:02:01.573 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 93416)
2019-01-15 06:02:01.744 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Corrupted PES header (errors 1205)
2019-01-15 06:02:04.392 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2761)
2019-01-15 06:02:07.597 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Corrupted PES header (errors 175)
2019-01-15 06:02:10.549 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Continuity counter error (total 12303)
2019-01-15 06:02:10.914 TS: DVB-T Network/177.5MHz/7 Melbourne Transport error indicator (total 298910)
2019-01-15 06:02:11.608 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Continuity counter error (total 93743)
2019-01-15 06:02:11.825 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2AUDIO @ #770 Corrupted PES header (errors 73)
2019-01-15 06:02:11.864 TS: DVB-T Network/177.5MHz/7 Melbourne: MPEG2VIDEO @ #769 Corrupted PES header (errors 1214)
2019-01-15 06:02:14.387 TS: DVB-T Network/177.5MHz/7 Melbourne: TELETEXT @ #772 Continuity counter error (total 2777)
2019-01-15 06:02:16.922 tbl-eit: eit: 177.5MHz in DVB-T Network: invalid checksum (len 1086, errors 11)

#26

Doing a bit of searching into the above errors, I found this thread on the Kodi forum. It seems to me to be related or a similar issue…


#27

Thanks for your suggestions and advice. I’m thinking I will try getting an appropriate amplifier and a powered USB hub and see if that makes a difference.

Do you have any suggestions as to what I should be looking for with regards to amplifiers? Would something like this work?


#28

That’s the sort of thing. I got an amplifier with 3 outputs to feed 2 sticks and my TV. If you use a passive splitter to feed more than one device you will lose signal because of the inevitable impedance mis-match. That site I mentioned above is a mine of information about such things, but I doubt they would deliver to you from Sheffield.

Before getting a powered hub, you could stick a voltmeter on the relevant IO pins of the Pi to see if you get a steady 5v+. You didn’t mention if you are hanging anything else off the Pi USB sockets.


#29

I probably wouldn’t need to split the signal at this stage. So something with just the one output should be fine.

The only other thing using the USB sockets on the Pi is an OSMC bluetooth dongle.

Thanks for that suggestion, but how do I tell which are the relevant IO sockets to test with the voltmetre?


#30

Search the RPi website.


#31

Hi graham,

You can check this website: https://www.raspberrypi-spy.co.uk/2012/06/simple-guide-to-the-rpi-gpio-header-and-pins/

Essentially you should check a combination of 5v pin and ground (Pin 2, and ground or pin 4 and ground). If the voltimeter says it’s 5v and it’s steady then it’s ok.