[Deprecated] Kodi 19 (Matrix) nightly builds for Vero 2 & 4K

The problem is version numbering, you have a higher version number at the moment then the Kodi 19 nightly builds.

They will probably soon come with a better version number for testing again.

Guys, I’m having an issue. I have three Kodi, two on Android and one on Vero 4k. The one on Vero 4k is the main one with the libraries and updates the mysql db. The problem is, Kodi on Android got upgraded to v19 Matrix and now, DB are not good anymore.

Can Vero 4k run v19? It looks like the nightly are on 18.8 and I can’t even make it to install. Saying that there is no updates available.



I’ve red that one. But shouldn’t I be able to run a nightly in the meantime?

Testing builds will show up here when they become available.

Regarding the questions referring to “When…”, I always see Mr. Incredible

I think I was misunderstood. The title of this page is Kodi 19 (Matrix) nightly builds, and there are builds up there. What are those? Matrix or Leia? Matrix is 19, Leia was 18.9, those builds seems to be 18.8? Or is it just the version of the nightly builds that doesn’t make sense?

I’m not looking for the official release, I’m looking for a nightly which would use a Matrix DB.


Kodi 19 is Matrix

On this topic which says Matrix 19 nightly builds, the latest build says [18.8-159] July 2020

Kodi Matrix is v19

Kodi Leia is v18.

The current stable version of OSMC is based on Kodi v18.9.

He’s probably confused why there are v18 links posted on this thread in the first post when the thread is about v19

All of the builds in this thread are based on Kodi v19 (Matrix). The 18.8 versioning refers to the fact that it is pre-release.

1 Like

Yes exactly, then, how can I install the 19 nightly since apt-get update doesn’t see it?

You currently can not. You will have to wait for the new testing being started via devel repository. As indicated here

The databases for both your Kodi 18 and Kodi 19 clients should work at the same time and not interfere with each other. Since they are completely separate they no longer share watched status and have to be updated separately, but they should still work, albeit a bit less useful than before the update. You could use Trakt to bring back some syncing between the clients in the meantime if this is an issue.

They do work, but I used Vero 4k to scan my libraries for changes and only have the mySQL db connection on Android, so now, when I add content, I don’t see them on Android anymore.

It’s not a big deal, I just thought I could use a nightly so it would run the same DB.

Still don’t understand why there was nightly that worked on 19 but they don’t anymore.


That’s the kind of answer I was expecting
ChillboOSMC Skinner


4.9 combined with the @gmc have not been cleared to run together. Additionally, the v19 nightly builds haven’t been updated for quite some time.

So there was a nightly, but since 4.9 came out, nightlies are not compatible :slight_smile:

Hi @fzinken

ls -lah /etc/samba/ | paste-log

osmc@HTPC:~$ smbclient -L localhost
Unable to initialize messaging context
Enter WORKGROUP\osmc’s password:
Anonymous login successful

    Sharename       Type      Comment
    ---------       ----      -------
    osmc            Disk      OSMC Home Directory
    IPC$            IPC       IPC Service (Samba 4.9.5-Debian)
    INTENSO         Disk      Auto-mount Volume
    disk3           Disk      Auto-mount Volume
    Ele             Disk      Auto-mount Volume
    disk1           Disk      Auto-mount Volume
    OneTouch        Disk      Auto-mount Volume

Reconnecting with SMB1 for workgroup listing.
Anonymous login successful

    Server               Comment
    ---------            -------

    Workgroup            Master
    ---------            -------
    WORKGROUP            HTPC

osmc@HTPC:~$ paste-log /etc/samba/smb.conf

Well you managed to go to the old TESTING thread but nevermind let’s stay here.

So all your disks are shared via SMB.
Can you check again from your other machine?

Confirmed in other thread, all working after reboot.