Kodi 20.4 "Nexus" – Release
It looks like one last hurrah was premature for the “Nexus” line: we find ourselves back again already, this time with a new 20.4 release.
An assortment of bug fixes, some backports, no real new features. Full changelog since 20.3 on Github, as usual.
Release notes
Build
- A backport aimed at fixing the failure rate of binary addon builds has been merged by @garbear.
Input
- Update to the controller addons.
Platform Specific
-
Android
- Several fixes have been backported from master to fix deployment issues on Google Play. Thanks to @joseluismarti for working with us on these.
- A number of fixes backported to resolve input issues (remotes/controllers).
-
iOS/tvOS
- A long-time-coming fix to reduce black screen playback when interlaced content is played on iOS/tvOS. Users should no longer have to specifically disable VTB Hardware playback for most interlaced content. Please keep in mind some methods of content playback (HTTP URLs provided in .strm files) will still be affected.
- A memory leak with game controllers on iOS/tvOS has been fixed by @kambala-decapitator.
-
tvOS
- @kambala-decapitator fixed what seems to be a long standing bug regarding framework
plist
metadata for shared library frameworks.
- @kambala-decapitator fixed what seems to be a long standing bug regarding framework
-
Windows
- A fix for
AESinkWASAPI
to improve fallback when the exact output channel layout isn’t supported by drivers or hardware.
- A fix for
Thanks, as always, to everyone who has helped us track down and fix any issues. We endeavour to minimise the issues everyone experiences, but with such a large project, and the fact everyone contributing to Kodi is a volunteer, issues and bugs are a part of life. if you happen to experience any bugs/issues, don’t hesitate to reach out on the forums, or raise an issue on Github.
As this is a point release, there are no major changes since the previous version, and you should be fine to install this straight over the top of any existing Kodi 20.x installation – indeed, this will happen automatically on many platforms. However, as for all software installations, back up your userdata beforehand if you’ve any doubts or have anything you can’t afford to lose (and definitely do this if you’re going for a major version upgrade).
A list of all changes for this version can be found at GitHub. If you want to read back on the full history of v20 itself, or of previous versions, you can find the corresponding articles in the relevant blog posts.
Application deployment on different platforms (notably the Microsoft Store) can vary considerably due to circumstances outside of our control, so just be patient, and the update will inevitably find its way through.
Android Deployment
We always do what’s known as a “staged” roll out for Android – so, if you don’t receive the update immediately, be patient, as it will come through over the next week. As the majority of fixes are related to Google Play deployment, we will deliberately be cautious with the schedule. If you do receive 20.4 and have any issues with the deployment, please let us know as soon as possible.
Leave a Reply
Want to join the discussion?Feel free to contribute!