OSMC's June update is here with Kodi v20 - OSMC

Reboot twice, play a minute of a file where you expect the subs to automatically be enabled, then stop playback, upload logs via My OSMC add-on, then post the url that was returned in this thread.

Default playback settings to see if the preference was saved and to check your language preferences against the language shown in the audio and sub tracks.

With all due respect to Sam I don’t share his “hunch.” The database does store which sub was selected for a file when it was manually changed but that isn’t exactly the situation your talking about.

I don’t know that I’ve ever heard of a tool for Kodi like this ever being made.

Not that I think you need to, but for the sake of completeness you can use the Trakt add-on for this or their is also the built-in option of exporting your library to individual files which will save all your currently scraped metadata including watched status. If you scrape a source with these files present the data will be pulled from these local files instead of searching online. By default Kodi does not import the watched status from here and you would need to make an advancedsettings.xml file with an import watched status setting inside in order to affect that change.

For the Beta user, is there something to do or will that reguar fit in? Since we (I) added the osmc-devel.list to apt?

That file is automatically removed after a number of days so people who sign up to staging for specific testing purposes don’t inadvertently stay in staging. Only people who have manually edited sources.list to add the dev repo would need to manually undo their changes.

Hi!

Since the 20.1 update my Amazon remote (1st gen) is not working anymore on my raspberry3b.

It is not even discoverable in MyOSMC Bluetooth.

Anyone has the same problem?
Any clues what I could do?

I notice this got fixed. :+1:

I had a second update prompt last night for my Vero 4K+ (like a subsequent revision of the June update that I had already installed), after installation I found it had reset some menu settings and had wiped out the Menu customisation extension. I had to reinstall that then re-apply my menu customisations.

You may wish to start a new post with logs as we haven’t released any additional updates.

I did a clean re-install when Nexus was on the stable channel and I also had one more additional update to install ca. 2 days later.

I suspect that will be a small kernel update (had an APT packaging issue); but it’s cosmetic so just a version bump. We haven’t actually changed any code that to cause the above user to have a problem.

@sam_nazarko here’s my apt.log for all of this year:

Start-Date: 2022-11-24  21:47:35
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -f -y dist-upgrade
Install: vero364-image-4.9.269-16-osmc:arm64 (4.9.269-16-osmc, automatic)
Upgrade: libntfs-3g883:armhf (1:2017.3.23AR.3-4+deb11u2, 1:2017.3.23AR.3-4+deb11u3), libgssapi-krb5-2:armhf (1.18.3-6+deb11u2, 1.18.3-6+deb11u3), tzdata:armhf (2021a-1+deb11u7, 2021a-1+deb11u8), ntfs-3g:armhf (1:2017.3.23AR.3-4+deb11u2, 1:2017.3.23AR.3-4+deb11u3), libexpat1:armhf (2.2.10-2+deb11u4, 2.2.10-2+deb11u5), libkrb5support0:armhf (1.18.3-6+deb11u2, 1.18.3-6+deb11u3), libxml2:armhf (2.9.10+dfsg-6.7+deb11u2, 2.9.10+dfsg-6.7+deb11u3), libkrb5-3:armhf (1.18.3-6+deb11u2, 1.18.3-6+deb11u3), vero3-mediacenter-osmc:armhf (19.5.0-7, 19.5.0-10), base-files-osmc:armhf (3.2.3, 3.2.4), libk5crypto3:armhf (1.18.3-6+deb11u2, 1.18.3-6+deb11u3), libksba8:armhf (1.5.0-3, 1.5.0-3+deb11u1), vero364-kernel-osmc:arm64 (3.9.251, 3.9.253)
End-Date: 2022-11-24  21:48:34

Start-Date: 2022-11-24  21:48:42
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -y purge vero364-image-4.9.113-64-osmc vero364-image-4.9.269-9-osmc
Purge: vero364-image-4.9.269-9-osmc:arm64 (4.9.269-9-osmc), vero364-image-4.9.113-64-osmc:arm64 (4.9.113-64-osmc)
End-Date: 2022-11-24  21:48:43

Start-Date: 2023-02-09  21:14:41
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -f -y dist-upgrade
Install: edid-decode:armhf (0.1~git20201230.95d81c9-2, automatic), vero364-image-4.9.269-21-osmc:arm64 (4.9.269-21-osmc, automatic)
Upgrade: libcurl4:armhf (7.74.0-1.3+deb11u3, 7.74.0-1.3+deb11u5), bind9-host:armhf (1:9.16.33-1~deb11u1, 1:9.16.37-1~deb11u1), libconfuse-common:armhf (3.3-2, 3.3-2+deb11u1), libtasn1-6:armhf (4.16.0-2, 4.16.0-2+deb11u1), libconfuse2:armhf (3.3-2, 3.3-2+deb11u1), mediacenter-addon-osmc:armhf (3.0.758, 3.0.761), libtiff5:armhf (4.2.0-1+deb11u1, 4.2.0-1+deb11u3), libamcodec-osmc:armhf (2.0.0-1, 2.1.0-1), libtinyxml2.6.2v5:armhf (2.6.2-4, 2.6.2-4+deb11u1), vero3-device-osmc:armhf (1.5.1, 1.5.2), vero3-mediacenter-osmc:armhf (19.5.0-10, 19.5.0-15), base-files-osmc:armhf (3.2.4, 3.2.5), armv7-evrepeat-osmc:armhf (0.1.0-2, 0.1.0-4), base-files:armhf (11.1+deb11u5, 11.1+deb11u6), distro-info-data:armhf (0.51+deb11u2, 0.51+deb11u3), mariadb-common:armhf (1:10.5.15-0+deb11u1, 1:10.5.18-0+deb11u1), libssl1.1:armhf (1.1.1n-0+deb11u3, 1.1.1n-0+deb11u4), nano:armhf (5.4-2+deb11u1, 5.4-2+deb11u2), bind9-libs:armhf (1:9.16.33-1~deb11u1, 1:9.16.37-1~deb11u1), libmariadb3:armhf (1:10.5.15-0+deb11u1, 1:10.5.18-0+deb11u1), sudo:armhf (1.9.5p2-3, 1.9.5p2-3+deb11u1), libksba8:armhf (1.5.0-3+deb11u1, 1.5.0-3+deb11u2), curl:armhf (7.74.0-1.3+deb11u3, 7.74.0-1.3+deb11u5), vero364-kernel-osmc:arm64 (3.9.253, 3.9.260), openssl:armhf (1.1.1n-0+deb11u3, 1.1.1n-0+deb11u4)
End-Date: 2023-02-09  21:15:47

Start-Date: 2023-02-09  21:15:54
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -y purge vero364-image-4.9.269-14-osmc
Purge: vero364-image-4.9.269-14-osmc:arm64 (4.9.269-14-osmc)
End-Date: 2023-02-09  21:15:55

Start-Date: 2023-05-09  20:53:42
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -f -y dist-upgrade
Install: vero364-image-4.9.269-26-osmc:arm64 (4.9.269-26-osmc, automatic)
Upgrade: libcurl4:armhf (7.74.0-1.3+deb11u5, 7.74.0-1.3+deb11u7), udev:armhf (247.3-7+deb11u1, 247.3-7+deb11u2), armv7-network-osmc:armhf (1.9.6, 1.9.7), libnss-myhostname:armhf (247.3-7+deb11u1, 247.3-7+deb11u2), libavahi-compat-libdnssd1:armhf (0.8-5+deb11u1, 0.8-5+deb11u2), libtinfo5:armhf (6.2+20201114-2, 6.2+20201114-2+deb11u1), libtinfo6:armhf (6.2+20201114-2, 6.2+20201114-2+deb11u1), tzdata:armhf (2021a-1+deb11u8, 2021a-1+deb11u10), libpam-systemd:armhf (247.3-7+deb11u1, 247.3-7+deb11u2), libavahi-common-data:armhf (0.8-5+deb11u1, 0.8-5+deb11u2), libavahi-core7:armhf (0.8-5+deb11u1, 0.8-5+deb11u2), mediacenter-addon-osmc:armhf (3.0.761, 3.0.766), mediacenter-skin-osmc:armhf (19.1.3-7, 19.1.4-2), libtiff5:armhf (4.2.0-1+deb11u3, 4.2.0-1+deb11u4), libsystemd0:armhf (247.3-7+deb11u1, 247.3-7+deb11u2), avahi-daemon:armhf (0.8-5+deb11u1, 0.8-5+deb11u2), libxml2:armhf (2.9.10+dfsg-6.7+deb11u3, 2.9.10+dfsg-6.7+deb11u4), systemd:armhf (247.3-7+deb11u1, 247.3-7+deb11u2), libudev1:armhf (247.3-7+deb11u1, 247.3-7+deb11u2), debian-archive-keyring:armhf (2021.1.1, 2021.1.1+deb11u1), vero3-mediacenter-osmc:armhf (19.5.0-15, 19.5.0-16), base-files-osmc:armhf (3.2.5, 3.2.9), grep:armhf (3.6-1, 3.6-1+deb11u1), base-files:armhf (11.1+deb11u6, 11.1+deb11u7), libnss3:armhf (2:3.61-1+deb11u2, 2:3.61-1+deb11u3), ncurses-base:armhf (6.2+20201114-2, 6.2+20201114-2+deb11u1), armv7-connman-osmc:armhf (1.4.0-3, 1.41-1), mariadb-common:armhf (1:10.5.18-0+deb11u1, 1:10.5.19-0+deb11u2), libavahi-common3:armhf (0.8-5+deb11u1, 0.8-5+deb11u2), armv7-splash-osmc:armhf (1.3.8, 1.3.9), libmariadb3:armhf (1:10.5.18-0+deb11u1, 1:10.5.19-0+deb11u2), systemd-sysv:armhf (247.3-7+deb11u1, 247.3-7+deb11u2), libgnutls30:armhf (3.7.1-5+deb11u2, 3.7.1-5+deb11u3), curl:armhf (7.74.0-1.3+deb11u5, 7.74.0-1.3+deb11u7), libncursesw5:armhf (6.2+20201114-2, 6.2+20201114-2+deb11u1), libncursesw6:armhf (6.2+20201114-2, 6.2+20201114-2+deb11u1), vero364-kernel-osmc:arm64 (3.9.260, 3.9.266), ncurses-bin:armhf (6.2+20201114-2, 6.2+20201114-2+deb11u1), libavahi-client3:armhf (0.8-5+deb11u1, 0.8-5+deb11u2), libncurses5:armhf (6.2+20201114-2, 6.2+20201114-2+deb11u1), libncurses6:armhf (6.2+20201114-2, 6.2+20201114-2+deb11u1)
End-Date: 2023-05-09  20:55:27

Start-Date: 2023-05-09  20:55:35
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -y purge vero364-image-4.9.269-16-osmc
Purge: vero364-image-4.9.269-16-osmc:arm64 (4.9.269-16-osmc)
End-Date: 2023-05-09  20:55:36

Start-Date: 2023-06-08  20:44:03
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -f -y dist-upgrade
Install: libspdlog1:armhf (1:1.8.1+ds-2.1, automatic), vero364-image-4.9.269-27-osmc:arm64 (4.9.269-27-osmc, automatic)
Upgrade: libwebpmux3:armhf (0.6.1-2.1, 0.6.1-2.1+deb11u1), libssh-4:armhf (0.9.5-1+deb11u1, 0.9.7-0+deb11u1), mediacenter-skin-osmc:armhf (19.1.4-2, 20.0.0-4), libwebpdemux2:armhf (0.6.1-2.1, 0.6.1-2.1+deb11u1), vero3-mediacenter-osmc:armhf (19.5.0-16, 20.1.0-4), base-files-osmc:armhf (3.2.9, 3.3.2), armv7-connman-osmc:armhf (1.41-1, 1.41-2), libwebp6:armhf (0.6.1-2.1, 0.6.1-2.1+deb11u1), libssl1.1:armhf (1.1.1n-0+deb11u4, 1.1.1n-0+deb11u5), vero364-kernel-osmc:arm64 (3.9.266, 3.9.267), vero3-ftr-osmc:armhf (1.6.0, 1.6.1), openssl:armhf (1.1.1n-0+deb11u4, 1.1.1n-0+deb11u5)
End-Date: 2023-06-08  20:45:10

Start-Date: 2023-06-08  20:45:17
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -y purge vero364-image-4.9.269-21-osmc
Purge: vero364-image-4.9.269-21-osmc:arm64 (4.9.269-21-osmc)
End-Date: 2023-06-08  20:45:18

Start-Date: 2023-06-10  23:08:48
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -f -y dist-upgrade
Install: vero364-image-4.9.269-28-osmc:arm64 (4.9.269-28-osmc, automatic)
Upgrade: vero364-kernel-osmc:arm64 (3.9.267, 3.9.268)
End-Date: 2023-06-10  23:08:55

Start-Date: 2023-06-10  23:09:02
Commandline: /usr/bin/apt-get-real -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -y purge vero364-image-4.9.269-26-osmc
Purge: vero364-image-4.9.269-26-osmc:arm64 (4.9.269-26-osmc)
End-Date: 2023-06-10  23:09:03

That last update was just cosmetic (to fix an APT issue) as explained above.

I can’t see anything after that date which would’ve caused you to have to reconfigure everything. Let’s keep an eye on things. I suggest taking a backup just in case.

Cheers

Sam

1 Like

Thanks Sam. I’m not too fussed. I only have some minor customisations, mostly just adding ‘TV in progress’ to the main screen and hiding some of the ones I don’t use.

But I did notice it reset the display to ‘hide watched’ too, and I had to flick that over too.

@Chillbo has updated the skin to add the missing play button back, make it the default selection action in the info screen, as well as add in a tweak to the default widgets (skin may need to be reset for that change to take effect). If you wanted to test it out early…

To test this 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
  3. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
  4. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you remove /etc/apt/sources.list.d/osmc-devel.list after updating.

This will deactivate the staging repository. You can do so with the following command:
sudo rm /etc/apt/sources.list.d/osmc-devel.list.

Please note that we will automatically disable this update channel after 14 days on your device in case you forget to do so to ensure that your system reverts to the stable update channel.

1 Like

I updated my raspberry pi 4 three days ago and now, when I’m watching downloaded HD 1080p movies, my RPi is experiencing 40-50% CPU load instead 5-10% as before.

Hi, I can confirm the Play button is back after installing the update; I’ve tested it with movies and TV shows.
Big thanks to you and Chillbo!!!

2 Likes

Has anyone else had any playback issues since the update?

Since the update I’ve been having issues where the picture would freeze sporadically - you can hear the audio carrying on, almost as if it’s buffering, but it stops after a few seconds.

I’ve also started seeing issues in the journal logs about Mesa errors that were not there prior to the update - I’ve also spotted some bcm2835_codec buffer errors.

I’ve tried moving the .kodi folder elsewhere and setting up from scratch but am still having the same issue both on streamed and local files. I am wondering (as I’ve not seen others with the same issue) whether there’s something in the config.txt that might be causing it and doesnt need to be there - I don’t suppose anyone can ping me over whats in the vanilla build config and I can built up from there.

Logs
https://paste.osmc.tv/nubotolabe

I rebooted the RPi and load issue is gone for whatever reason.

[pi4]
dtoverlay=rpivid-v4l2
arm_64bit=1
kernel=kernel.img

[all]
dtoverlay=vc4-kms-v3d,cma-512
disable_overscan=1
start_x=1
disable_splash=1
disable_fw_kms_setup=1
hdmi_ignore_cec_init=1
include config-user.txt

[pi02]
dtoverlay=vc4-kms-v3d,cma-256

[board-type=0x0e]
dtoverlay=vc4-kms-v3d,cma-256