Archive:Kodi v15 (Isengard) FAQ

From Official Kodi Wiki
Revision as of 08:40, 19 May 2015 by Fritsch (talk | contribs) (The "o" screen doesn't show the video FPS anymore)
Jump to: navigation, search

Template:Kodi FAQ

Home icon grey.png   ▶ FAQs
▶ Releases
▶ Kodi v15 (Isengard) FAQ

Template:Isengard box

Frequently Asked Questions for upgrading to the upcoming Kodi v15 (codename Isengard) from a previous version. Includes how to enable some of the new features, where some controls got moved to, etc.

1 General FAQ

See also: All platforms FAQ for an FAQ that applies to all versions of Kodi.

1.1 What is Kodi? What is Isengard?

Kodi is the new name for XBMC media center. "Isengard" is the codename for version 15, just as "Gotham" was the codename for XBMC v13 and "Helix was the codename for Kodi v14". You will often see "v15" and "Isengard" used interchangeably in the community. It might be a little confusing with so many new names being used, but this is simply the new version of Kodi/XBMC. As long as you call it version 15/v15/Isengard, then everyone in the community will know what you are talking about.

1.2 Changelog

See: Kodi v15 (Isengard) changelog (and add-on developers should also see Isengard API changes)

1.3 What are some of the noticeable new features?

In addition to many "under the hood" improvements, some of the visible additions to v15 include:

1.4 Seeking/skip steps are different

Skip steps is a new seeking function that has been implemented into Kodi as of v15, and is a method of additive skipping (also known as additive seeking) that applies to both videos and music. This allows the user to skip backwards and forwards with the left and right cursor keys (this is the default keyboard and remote mapping), and by pressing these keys multiple times they can skip with increasingly larger steps.

1.5 SmallStepBack doesn't seem to work

In Keymaps the SmallStepBack action ID has been replaced by seek(-7). Users with custom keymaps should apply this change as well. SmallStepBack will still work, but it will default to the first back step in skip steps.

1.6 HOW-TO:Install languages offline

HOW-TO:Install languages offline

2 New system requirements

2.1 Android 4.2 required

Android 4.2 is now the minimal supported version for Kodi to run on Android platform.

2.2 iOS 5.1.1 required

iOS 5.1.1 is now the minimal supported version for Kodi to run on a jailbroken "iDevice".

2.3 Mac OS X 10.7 required

Mac OS X 10.7 is now the minimal supported version for Kodi to run on the Mac platform.

2.4 OUYA needs OS upgrade to run v15

Due to the new system requirements and lack of needed updates from the OUYA company, OUYA's Android-based OS is unable to run Kodi v15. The OUYA hardware can still be used for Kodi, but will need a replacement for the OUYA OS. There is a work-in-progress guide in doing so at HOW-TO:Install CyanogenMod on OUYA. It might even be possible to still use OUYA games on CM 11, or at least have some kind of dual booting option for users who want to retain access to their old OUYA games.

2.5 Apple TV 2 is no longer supported

Apple TV 2 is no longer supported as of v15. See here for details.

3 Upgrading

Stop hand.png If you are upgrading from XBMC v13 to Kodi v15 then please read Migration from XBMC to Kodi first.

Stop hand.png Always backup your settings before upgrading, just incase!

3.1 How do I upgrade from v14 to v15?

  • ANDROID USERS: Don't uninstall an earlier version of Kodi/XBMC before installing the new version. Uninstalling first would remove all of your settings. Just install the new version and it will replace the older version and retain your settings.
  • In most cases you can just install Kodi v15 over Kodi v14. All your settings and library are saved and will continue to work in the new version. See Installing for specific install instructions.
  • Interface skins that worked in Kodi v14 should still work in v15.
  • Most other add-ons that worked in Kodi v14 should still work in v15.
  • If you have any issues (settings not being copied over, blank screens, etc) when updating from versions older than v14: remove the new version, install the older version of Kodi/XBMC from , and then upgrade to the next version. In other words, if you have v13, first update to v14, and then install v15.

3.2 MySQL

As long as your MySQL server is set up to allow XBMC/Kodi to make new databases for the upgrade itself (see MySQL/Upgrading) then you don't need to do anything for upgrading a MySQL set up for Kodi. Even if you use "XBMC" in your advancedsettings.xml file, you can leave this the same and everything will still work.

4 Where did it this or that go?

4.1 advancedsettings.xml changes

  • <hideallitems> - For both the <videolibrary> and <musiclibrary> sections, this is replaced by a GUI option in v15 Isengard
  • <SmallStepBackSeconds> - In v15 the SmallStepBack action ID has been replaced by seek(-7) in default keymaps. See skip steps for details. When the original SmallStepBack action ID is used it defaults to the first backwards additive seeking value.
  • <timeseekforward>/<timeseekbackward> - In v15 these tags are replaced by GUI options via additive seeking, which is configured in the GUI. See skip steps for details.

4.2 Add-on manager: navigation changes

Editor note: Need a blurb here about the add-on manager changes. Full details should then be updated to the main add-on manager page.

4.3 Add-on manager: checking for new updates

In most Kodi interface skins, including the default skin Confluence, the button to check for new add-on updates has been moved to the lefthand sidebar menu. When you've gone into Settings → Add-ons you can press (left) to show the menu and update button.

4.4 Automatic crop black bars setting

The video playback setting for cropping black bars has been removed due to various bugs. Team Kodi is looking for any developers who might be interested in creating replacement code and is willing to guide them. Please inquire on the development forum for more information.

4.5 Apple File Protocol (AFP) has been removed

Unfortunately, the AFP client has now been removed from Kodi. When AFP was first added to Kodi (then called XBMC) it was to help those Mac users who had issues with SMB sharing. However, the AFP client has always had major crashing issues, and the open source project behind it was no longer maintained. Team Kodi looked for a replacement and even tried to make our own replacement AFP client code, but in the end it didn't work out.
Users who have AFP file servers can use path substitution to change those URLs into another formatted protocol. We recommend using NFS or getting SMB to work by reading SMB/Mac. Editor note: maybe make a mini-how-to for the path subs.

4.6 HTSP has been removed

The HTSP protocol was a way for older versions of Kodi/XBMC to access Tvheadend before PVR/live TV features were officially added to Kodi/XBMC. Now that PVR/live TV has been supported since v12.0 (January 29th, 2013), and replaced the need for HTSP support, the HTSP protocol has finally been retired. Please see our PVR guide for details on how to set up the Tvheadend PVR add-on.

5 Troubleshooting

5.1 What are some of the known issues in Isengard?

See: Common issues

5.2 Where can I get more help?

The general and platform specific FAQs, the Kodi support forums:, and/or the #kodi IRC chat channel on

5.3 The "o" screen doesn't show the video FPS anymore

In the codecinfo window, the one that shows when you press o on a keyboard, the FPS data no longer reports video FPS.
In past versions of Kodi/XBMC (before v15) this value reported the estimated frames per second for the actual video itself, but was horribly inaccurate most of the time. Due to those inaccuracies, and various other code changes, the setting has been changed to only report what FPS the graphical interface (the buttons, menus, etc) is being rendered at. This doesn't actually mean anything for most users, but just understand that this no longer has anything to do with the video FPS.
If you want to check if your video playback is working as it should, watch the skip and drop values. If those stay low, nothing to worry about. Increasing skip value means, that video frames cannot be rendered in time. If you even see dropping, then it's our last resort, as the system seems to be too slow to play that video and we told the decoder to throw away complete frames. Also take care that the codecinfo window byself puts more pressure on the hardware. Open it from time to time only and compare the skip / drop values.

6 See also

Template:Upgrade FAQs