Nightly builds

On the latest nightly 1002 I have lost my AVL6862 VIM2 tuner card. My TELESTAR Sat > IP card is still working. I have Crazy cats dvb module loaded - which has always worked with this card in the past. TVH simply reports no source available - though it is present and enabled in TVadapters screen of TVH interface.
I also upgraded the version of TVH server, but the problem was there before this upgrade.


A lot of commits were included in the 20181002 update, though I can’t find anything related to crazycats, mediatree or dvb.
Maybe it was upgraded from the addon repository.
Did you try to downgrade to an older version of crazycats?

Btw: The current 20181003 update again includes a lot of fixes and also Kodi 18 Beta 3.
But I would advise you to wait for the upcoming 20181004 update, because some dvb an TVH related fixes will be included here.
The KVIM2 image should be ready in a few hours.

1 Like

Tried upgrading to 1003, but that made matters worse as it broke the SAT > IP as well.
Going to roll back to 929 and hope for the best.

UPDATE: rolled back to 929, but there was obviously a serious upgrade to the PVR infrastructure since it is refusing to allow me to roll back the TVH client due to incompatible binary. Fubared system.

UPDATE : rolling forward to 1002 brought back the SAT > IP , but the AVL6862 is still broken on both of its internal tuners. This now seems consistent behaviour - and it seems to be related to the PVR binary bump. Will just have to see what tomorrow and 1004 brings. My experience is that once a breakage like this has crept in - the only thing to do is wait for it to get fixed because the only way to roll back is a fresh install which is an unacceptable workload.


Did you uninstall TVH and cleared your package cache before installing a lower version?

Sorry, I didn’t see your second edit.
I think, your best option would be to wait for the 20181004 update then, with the dvb fixes included.

This will have to wait till tomorrow, as its late and its work tomorrow. Cheers.


Sure, I’ll keep my fingers crossed.

Could you please also try this version of crazycat drivers, @afl1 posted before?

OK I upgraded to that version of CVH and then I upgraded to 1004. Still didn’t get anything so I investigated the hardware. Could find nothing wrong but when I put my box back together again everything worked on 1004. I am now not certain what was wrong and have to assume it was not CE at all but a hardware glitch. I am finding the whole VIM2 setup to be very unreliable with frequent dvb drop outs and unpredictable behaviour.

Still, all’s well that ends well.


That’s a really strange problem. Glad you solved it.

There was also a problem with the USB tv tuner (T230C2). I discovered that now there is an option to select DVB driver (program add-ons - LibreElec Module Drivers - chose DVB driver module). I chose the necessary driver (the CrazyCat for my tuner) and the TVH works again

Not sure if anyone else using CoreELEC is having an issue with PVR and channelgroups, but I’m having the issue described in this KODI trac:

Would it be possible to include a patch for extra logging of the PVR component in one of the nightly builds (at least for C2)? I think that might be easier than trying to setup another environment on my own to build CoreELEC and KODI.

The purpose of the nightlies is to provide completely unmodified builds of the master branch on GitHub.
Also generally adding extra logging would flood the log files of everyone downloading it, which should be avoided.

But if you take a look at “Settings > System > Logging”, there is already an option to enable component-specific logging. After activating it, you can select “Verbose logging of PVR component” within the “Specify component-specific logging…” section.
You could also enable debug logging to have a more complete log.

1 Like

Not sure what magic you boys and girls are doing, but the latest nightly (20181004) is just phenomenal :slight_smile:

I had a couple of h265 4K rips that had a lot of hiccups (buffering) and now are buttery smooth!! (Using Emby Server beta in Windows + Emby for Kodi).

A big thank you to all involved! Really cool stuff!



Just a little feedback

Took a sd Card with nightly from Oct. 15th in my wetek play 2.


CEC : Strange behavior with Pioneer AVR and LG TV. Starting ok. Shutting down with TV remote powers TV off and then on again. shutting down with play2 remote does not power off TV.

Timeshift with TV Headend : had to disable timeshifting because liveTV will buffer for some seconds on all channels more or less often.

Longpress OK on the remote from the play2 does not work as aspected.

Erverything else is fine.

I don’t have enough experience with CEC, but there are some CEC options in the settings to play with (in “Settings > System > Input devices > Peripherals > CEC adapter”).
Maybe you can optimize it a bit.

Did you try moving the timeshift path to another location (e.g. an nfs share or attached USB HDD)?
I assume the sd card is just too slow to handle timeshift and you need a pretty fast storage for writing and reading tv streams at the same time - especially HD streams.

SD Card too slow can be the reason. I will test a nfs share.

tried several times with different CEC options.
Sounds strange but if I start the stuff with the play 2 remote then play2 starts, AVR starts, TV starts. For shutdown I have to use the TV remote - then TV stops, AVR stops and play2 also.
Its ok this way.

Using play 2 remote only the TV won´t shut down or comes up again when AVR stops.
I think its my stuff which is not 100% CEC compatible.

What about the OK longpress of the play2 remote. I have seen a thread about this somewhere with a solution but I can´t find it again.

Maybe you could open another thread for your CEC problem, because this is most probably not a problem of the nightlies.
Looking at the commits since 8.95.3, there is nothing, which could break CEC functionality.

The same goes for your remote/longpress problem.
But it seems, using your remote in keyboard mode allows you to configure longpress actions.
Though this is a completely different remote, a slightly modified solution could solve your problem:

Because I’m using a Harmony remote with Bluetooth, I can’t reproduce your problem.

Ok. Thank you

Development seems to have ground to a stop. Does that suggest we are approaching final release, after all Kodi is in beta 3.


Development hasn’t been stopped and the latest nightly already shows “bata 4” in the system information.
Adam has been very busy lately and didn’t have so much time developing for CoreELEC.
Today about 40 new commits were added to GH (including the newest Kodi patches). Therefore you can expect the next nightly version 20181020 later today.

1 Like

Great news.
I understand that the Kodi release candidate is due for release before the end of the year.