[TESTING] Kodi v20.1 builds


The next version of Kodi v20 (codename Nexus) was released in January. Since then, we’ve been working on bringing this up for OSMC.

Supported platforms

This release supports:

  • Vero 4K
  • Vero 4K +
  • Raspberry Pi 2
  • Raspberry Pi 3
  • Raspberry Pi 4 / 400

How to update

Updating from a stable version of OSMC

If you’re running a stable version of OSMC, then you should be able to update from a compatible platform without issue. Please make sure that you system is up to date first by going to My OSMC → Updates and initiating an update check; installing any outstanding updates.

Updating via the command line

To install the update:

  1. Login via the command line
  2. Run the following command to add the staging repository:
    echo 'deb http://apt.osmc.tv bullseye-devel main' | sudo tee /etc/apt/sources.list.d/osmc-devel.list

Go to My OSMC → Updates again, and initiate an update check. Install the updates when prompted.

Tracking releases

There will inevitably be outstanding issues, so we plan to push some further test builds over the coming days as we receive feedback. Please keep in mind that the above command will need to be re-run every 14 days.

Known issues

Currently, we are aware of the following issues:

  • TBC

Frequently asked questions

Q: I’ve installed the update and now I only have a black screen or a sad face loop, how do I fix this?
A: It’s possible that your Kodi userdata is causing an issue with the new version. The first recommendation would be to move it away and allow Kodi to generate a new userdata directory. This can be done by executing the following commands after accessing the command line:

sudo systemctl stop mediacenter
mv ~/.kodi ~/.kodi-backup
sudo systemctl start mediacenter

Before attempting this, you may wish to try a more conservative approach, and delete ‘Addons.db’ only, as reports from users suggest that add-on migration is the problem

Q: I only see a black screen / hang on migrating add-ons, what should I do?
A: If you encounter this problem and a consider amount of time (more than half an hour) has passed, you should log in to the system and execute the above instructions from the previous question.

Q: I am using a shared library? Has the database version changed?
A: Yes. You should check that your other Kodi clients are compatible with Kodi Nexus before upgrading.

Q: Are add-ons supported by Kodi Matrix supported in Kodi Nexus?

A: Not necessarily. We suggest checking first before upgrading.

Q: I can’t find my add-ons anymore
A: To ensure compatibility where possible, Kodi disables any non-official add-ons by default when a new major version is released. You should be able to enable them manually under Settings. Note that this does not necessarily mean they be compatible with the new version of Kodi.

Q: Will my current skin work with Kodi Nexus
A: Every Kodi version involves changes to the skinning engine. It’s advised to check with the developer of the skin you are using. The official OSMC skin and official Kodi Estuary skins are supported and maintained for Kodi Nexus.

Q: My add-ons are not working, what can I do?
A: You should notify the developer of this add-on and ask them if there is a version compatible with the new version of Kodi. Unfortunately OSMC cannot do anything about this.

Q: How can I downgrade?
A: Unfortunately, downgrading is not trivial. However we will maintain Matrix images on our website for some time. If you discover a bug or issue, we are more interested in fixing it, as there will be users in a similar position, rather than having users downgrade.

Q: I don’t see all of my skin’s menus. What can I do to resolve this?
A: Please wait a few moments for the skin menus to be rebuilt. This may take a while to update if you have a number of add-ons on your system. If the issue persists, you should check that your skin is indeed compatible.

Q: CEC has stopped working, what can I do?
A: Power off your TV and device at the mains for 60 seconds, including your AV receiver if you have one. This usually resolves CEC issues.

Q: My question is not answered and I am experiencing an issue, what can I do?
A: Please start a new forum post, with detailed information so that we can assist you with your problem.


  • 11/05/2023: initial release
  • 27/05/2023: Fix a logging issue and some string mismatches on Vero 4K / 4K+

Let me know how you get on,




Great news the test release for Kodi 20.1 is available. Will install very soon :slight_smile:

On a RPI4 the Upgrade went smooth. None from above Q&A happend.

New MySQL Video-DB was successfully created. For Music there was no change.

Up to now, no changes noticeable.

One night in on the Vero 4K+ update, no issues. As usual, the database update (using MariaDB) always convinces me that it has hung, but it does finish. I’m glad to have access to the updated Estuary skin (and the mod I do for it). There are some subtle but useful improvements in that skin.

I’m sure @chillbo would like t know which you find useful.

1 Like

Updated two Vero 4K+ with no issues. Played some files including 3D MKV and so far everything plays fine. Thank you for this great update!

1 Like

There are details on all the skinning engine changes for Nexus at:


Here are a few that I think are useful (I believe they are all incorporated into Estuary):

@chillbo has incorporated that but I for one have found these labels are not being added automatically when upgrading from Matrix to Nexus. My theory about why that is means it shouldn’t be happening only on OSMC.

We’d be interested to know if others have the same issue.

Upgrade went fine. Database migration seemed to complete ok but getting these errors on database now.

Running MariaDB on Docker.

Initialize, updating databases…
2023-05-12 08:11:42.499 T:2952 info : Running database version Addons33
2023-05-12 08:11:42.502 T:2952 info : Running database version ViewModes6
2023-05-12 08:11:42.504 T:2952 info : Running database version Textures13
2023-05-12 08:11:42.505 T:2952 debug : connect replacing configured host with resolved host
2023-05-12 08:11:42.509 T:2952 info : MYSQL: Connected to version 10.6.12-MariaDB
2023-05-12 08:11:42.518 T:2952 info : Running database version MyMusic82
2023-05-12 08:11:42.518 T:2952 debug : connect replacing configured host with resolved host
2023-05-12 08:11:42.529 T:2952 info : Attempting to update the database MyVideos121 from version 119 to 121
2023-05-12 08:11:42.530 T:2952 debug : Mysql Start transaction
2023-05-12 08:11:42.536 T:2952 error : SQL: Can’t determine list of routines to drop.
2023-05-12 08:11:42.537 T:2952 error : Exception droping old analytics from MyVideos121
2023-05-12 08:11:42.538 T:2952 debug : Mysql rollback transaction
2023-05-12 08:11:42.539 T:2952 debug : connect replacing configured host with resolved host
2023-05-12 08:11:42.545 T:2952 error : Unable to open database: MyVideos120 [1049](Unknown database ‘MyVideos120’)
2023-05-12 08:11:42.545 T:2952 debug : connect replacing configured host with resolved host
2023-05-12 08:11:42.555 T:2952 info : Old database found - updating from version 119 to 121
2023-05-12 08:11:42.558 T:2952 error : SQL: Can’t create database for copy: ‘MyVideos119’ (1007)
2023-05-12 08:11:42.558 T:2952 error : Unable to copy old database MyVideos119 to new version MyVideos121
2023-05-12 08:11:42.562 T:2952 info : Running database version TV40

Never mind. I was able to fix it my running the command mysql_upgrade in the mariadb console.

Maybe this will help others??

Updated two Veros, no regressions so far.

Is there anything about 20.x that would improve HDR to SDR conversion on the Vero compared to 19.x? Perhaps just a placebo effect on my part that my HDR mkvs are looking good on my ancient Panny plasma, I only tend to look at that as a curiosity.

well one glitch: even though my Vero with TVHeadend server has been on Kodi 20 for nearly 24hrs, I have some channels that now have no EPG info. Oddly, even though BBC 1HD and BBC 2HD are on the same mux, I have EPG info for BBC 2 but not for BBC 1. I hope I don’t have to re-start from scratch, any ideas?

Not just OSMC. It appears to require at least a refresh of the item to get those labels in. For anything new you scrape they will get included, but I think they are attached to a part of the database that is tied to show/movie scraping. The only way to get it in there is for a scrape or a refresh (at least that I’ve figured out).

apologies for cluttering the thread, I just returned from holiday and I figured out that my BBC ONE HD service has become “BBC ONE Lon HD” while I was away, but because the first thing I did was to update OSMC when I got back, I asssumed that was the issue, when all I needed to do was to remap my services. Doh!

works fine, no errors so far

Same here, no issues … all my test files work perfectly :+1:

No apologies needed. Thanks for the hint I had the same issue, also ‘use channel numbers from backend’ not working which was solved by wiping the EPG cache.

Does this mean we will (at last) be getting local news in HD?

looks like it, I notice my kitchen TV, which uses Freesat, now has a regional BBC HD feed at channel 101.

After about 2 minutes live HD-stream freezes, no connection everything stops, cannot reboot, have to unplug in order to restart osmc…

SD Card issue? Check if you can write files to the SD Card, reboot and check if file still there.

FileNotFoundError: [Errno 2] No such file or directory: '/home/osmc/.kodi/temp/kodi.old.log'