Tried the upgrade to the test kernelā¦ Put the line into the sources.list (and saved with ctrl+x and y), ran the command - everything like always - , but it outputs only this:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
And after the reboot the kernel version is still: Linux osmc 3.14.29-51-osmcā¦ Whatās happening here?
Any ideas how to force the upgrade to the test kernel - as the sudo apt-get update && sudo apt-get dist-upgrade && reboot with deb http://apt.osmc.tv stretch-devel main added to /etc/apt/sources.list doesnāt seem to work here for some reason?
Thatās the kernel version. Wed Feb 14 23:32:25 is the release date and time. 3.14.29-51 would be the current stable version, released on Tue Jan 2 09:35:33.
Tried a manual reinstall of 3.14.29-57 now. It seems 3.14.29-57 was correctly installed before (I seem to have left the devel source in my sources.list) and had it downgraded to 3.14.29-51 when deleting the line and running sudo apt-get update && sudo apt-get dist-upgrade && reboot againā¦ I donāt know. A bit of confusion here.
sudo apt-get install --reinstall vero364-image-3.14.29-57-osmc did the trick. Iām on Linux osmc 3.14.29-57-osmc #1 SMP Wed Feb 14 23:32:25 UTC 2018 aarch64 GNU/Linux now
WAIT! I think thereās something missing in the build in stretch-devel. I can get it working properly with flac 5.0 and the Sense & Sensibility clip using a mediacenter deb @sam_nazarko sent me but it looks like the published version is different in some way.
Itās in internal version package which was not published at all. With current
vero3 kernel 3.14.29-57
mediacenter 17.6.0-25
you only have the first patch available which maps 5.1 channel audio to PCM 5.1 or better 3/2.1.
Sorry folks for this confusion, the developers have to fiddle out what went wrong when the actual development stretch was published. Please, wait for news.
There is no updated kernel as part of this testing; but you may receive one from other improvements made in the staging repository.
It looks like I forgot to bump the version properly. Iāve done this now and kicked off a build, so the improvements should be available shortly in 30-45 minutes.