Difference between revisions of "Kodi"

From ArchWiki
Jump to: navigation, search
m (semi-automatic style fixes, see Help:Style)
m (sytle fixes)
 
(289 intermediate revisions by 62 users not shown)
Line 1: Line 1:
[[Category:Player]]
+
[[Category:Multimedia players]]
XBMC (formerly "Xbox Media Center") is a free, [http://www.gnu.org/copyleft/gpl.html open source (GPL)] multimedia player that originally ran on the first-generation [[Wikipedia:Microsoft Xbox|XBox]], (not the newer Xbox 360), and now runs on computers running Linux, Mac OS X, Windows, and iOS. XBMC can be used to play/view the most popular video, audio, and picture formats, and many more lesser-known formats, including:  
+
[[ja:Kodi]]
 +
[[zh-hans:Kodi]]
 +
Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub that can be installed on Linux, OSX, Windows, iOS and Android, featuring a 10-foot user interface for use with televisions and remote controls.  These can all be played directly from a CD/DVD, or from the hard-drive. Kodi can also play multimedia from a computer over a local network (LAN), or play media streams directly from the Internet. It can also be used to play and record live TV using a tuner, a backend server and a PVR plugin; more information about this can be found on the [http://kodi.wiki/?title=PVR Kodi wiki].
  
* Video - DVD-Video, VCD/SVCD, MPEG-1/2/4, DivX, XviD, Matroska
+
== Installation ==
* Audio - MP3, AAC.  
+
[[Install]] the {{Pkg|kodi}} package. Be sure to install the optional dependencies listed by pacman that apply to your specific use-case.
* Picture - JPG, GIF, PNG.  
+
 
 +
{{Note|Users of Arch ARM should be aware that several different kodi packages with specific hardware support are available.}}
 +
 
 +
== Configuration ==
 +
=== Autostarting at boot or ondemand ===
 +
The {{Pkg|kodi}} package supplies {{ic|/usr/bin/kodi}} which can be run by any user on a on-demand basis.  A stand-alone wrapper script {{ic|/usr/bin/kodi-standalone}} is also provided that allows a minimal system and an unprivileged user to run the application.  The is advantageous for several reasons:
 +
# An unprivileged user cannot access a shell by definition.
 +
# Running without a full blown DE is lighter and more simplistic.
 +
# When paired with a systemd unit (or equivalent, see below), this make the box on which kodi is running more like an appliance and very robust.
  
These can all be played directly from a CD/DVD, or from the hard-drive. XBMC can also play multimedia from a computer over a local network (LAN), or play media streams directly from the Internet. For more information, see the [http://wiki.xbmc.org/index.php?title=XBMC_FAQ XBMC FAQ].
+
There are several methods to it this described below.
 +
{{Warning|Select '''only one''' of the methods listed below.}}
  
As of version 12, it can also be used to play and record live TV using a tuner, a backend server and a PVR plugin; more information about this can be found on the [http://wiki.xbmc.org/?title=PVR XBMC wiki].
+
==== Kodi-standalone-service ====
 +
The {{AUR|kodi-standalone-service}} package provides {{ic|kodi.service}} and automatically creates the unprivileged user to run Kodi in standalone mode.  Although the correct [[Xorg#Driver_installation|driver]] is an assumed dependency, no extra Xorg packages are needed.  [[Start]] {{ic|kodi.service}} and [[enable]] it to run at boot time.  No additional configuration should be required for most users, however, if {{ic|kodi.service}} fails to start, see [[Xorg#Rootless Xorg (v1.16)]].
  
== Installation ==
+
{{Note|
 +
* The kodi user is unprivileged meaning it cannot login (default shell is {{ic|/usr/bin/nologin}}).
 +
* The home directory for the kodi user created is {{ic|/var/lib/kodi}} not {{ic|/home/kodi}}.
 +
}}
 +
 
 +
{{Warning|Users of Arch ARM should not attempt to install this package as breakage will occur!}}
 +
 
 +
==== Xsession with LightDM ====
 +
{{Note|This assumes that the user has created an kodi user named kodiuser on the system and that the following file is present as described.}}
 +
{{Note|1=lightdm does not pull in an X server as a required dependency, it is optional. The X server listed as an optional dependency (xephyr) does not work when run as root by lightdm.service ([https://bugs.archlinux.org/?string=52067 Bug to have optional dependency modified]) ([https://bugs.launchpad.net/lightdm/+bug/852577 Upstream Bug]).  Install [[Xorg#Installation|xorg-server]].}}
 +
 
 +
To use LightDM with automatic login, see [[LightDM#Enabling autologin]] and [[LightDM#Enabling interactive passwordless login]]. ''Kodi'' includes {{ic|kodi.desktop}} as [[xsession]].
 +
 
 +
{{hc|/etc/lightdm/lightdm.conf|2=
 +
[Seat:seat0]
 +
pam-service=lightdm-autologin
 +
autologin-user=kodiuser
 +
autologin-user-timeout=0
 +
user-session=Kodi
 +
}}
 +
 
 +
==== Socket activation ====
 +
 
 +
Socket activation can be used to start Kodi when the user starts a remote control app or on a connection to Kodi's html control port. Start listening with ''systemctl start kodi@user.socket'' (replace ''user'' with the user running Kodi to be started as).
 +
 
 +
The {{AUR|kodi-standalone-socket-activation}} package provides {{ic|kodi@.service}} but not {{ic|kodi@.socket}}. Depending on the setup, one may want to change the port in ''kodi@.socket''. This can be done by manually using the following systemd files.
 +
 
 +
{{hc|/etc/systemd/system/kodi@.service|
 +
<nowiki>[Unit]
 +
Description=Launch Kodi on main display
 +
 
 +
[Service]
 +
Type=oneshot
 +
Environment=DISPLAY=:0.0
 +
Nice=-1
 +
ExecStart=/usr/bin/su %i /usr/bin/kodi
 +
ExecStartPost=/usr/bin/bash -c "sleep 15 && systemctl start kodi@%i.socket"
 +
 
 +
[Install]
 +
WantedBy=multi-user.target</nowiki>}}
 +
 
 +
{{hc|/etc/systemd/system/kodi@.socket|
 +
<nowiki>[Unit]
 +
Conflicts=kodi@%i.service
 +
 
 +
[Socket]
 +
# listen for WOL packets
 +
#ListenDatagram=9
 +
 
 +
# change this to Kodi's http control port
 +
ListenStream=8082
 +
 
 +
[Install]
 +
WantedBy=sockets.target</nowiki>}}
 +
 
 +
==== Start from remote control with LIRC / irexec ====
 +
Kodi can be configured to start via a key press.  Users will need {{AUR|kodi-standalone-service}} and {{Pkg|lirc}}.  This can be useful on setups running 24/7 and having kodi up on demand.
 +
 
 +
See the corresponding [[LIRC]] article and create a functional setup with a remote.  Also, the package {{AUR|kodi-standalone-service}} has to be installed.
 +
 
 +
Generate the file {{ic|/var/lib/kodi/.lircrc}} with the following content:
 +
{{hc|/var/lib/kodi/.lircrc|
 +
<nowiki>
 +
begin
 +
prog = irexec
 +
remote = devinput
 +
button = KEY_MEDIA
 +
config = pgrep kodi-standalone || /usr/bin/kodi-standalone -l /run/lirc/lircd
 +
repeat = 0
 +
end
 +
</nowiki>
 +
}}
 +
 
 +
Adopt {{ic|button}} to whatever button on the remote is to start Kodi.  One can use ''irw'' (see [[LIRC#Usage]]) to find out the correct values for {{ic|remote}} and {{ic|button}}.
 +
 
 +
Next copy {{ic|kodi.service}} from {{ic|/usr/lib/systemd/system/}} to {{ic|/etc/systemd/system/}} and change the line
 +
ExecStart = /usr/bin/kodi-standalone -l /run/lirc/lircd
 +
to
 +
ExecStart = /usr/bin/irexec
 +
 
 +
[[Start]] {{ic|kodi.service}} and [[enable]] it to run at boot time.
 +
 
 +
=== Sharing a database across multiple nodes ===
 +
If multiple PCs on the same network are running Kodi, they can be configured to share a single media library (video and music).  The advantage of this is that key metadata are stored in one place, and are shared/updated by all nodes on the network.  For example, users of this setup can:
 +
* Stop watching a movie or show in one room then finish watching it in another room automatically.
 +
* Share watched and unwatched status for media on all nodes.
 +
* Simplify the setup with only a single library to maintain.
 +
 
 +
Several key things are needed for this to work:
 +
* Network exposed media (via protocols that Kodi can read, e.g. NFS or Samba).
 +
* A MySQL server (Arch uses {{pkg|mariadb}}).
 +
 
 +
{{Note|The following guide is only an example of one configuration and is not meant to be limiting but illustrative.  Key steps are shown but a detailed discussion is not offered.}}
 +
These assumptions are used for the guide, substitute to reflect your setup:
 +
* The media is located under following mount points: {{ic|/mnt/tv-shows}} {{ic|/mnt/movies}} {{ic|/mnt/music}}.
 +
* The network addresses of all nodes are within the 192.168.0.* subnet range.
 +
* The IP address of the machine running both the NFS exports and the MySQL database is 192.168.0.105.
 +
* Each Kodi box is referred to as a node.
 +
* The Linux user running Kodi is 'kodi' on all nodes.
 +
 
 +
For additional info, refer to the [http://kodi.wiki/index.php?title=HOW-TO:Share_libraries_using_MySQL/Setting_up_MySQL#tab=Arch_Linux official Kodi wiki].
 +
 
 +
==== Setup an NFS server ====
 +
This section provides an example using NFS exports, but as mentioned above, any protocol that Kodi can read is acceptable.
 +
 
 +
{{Warning|Kodi is using {{Pkg|libnfs}} to access NFS shares which only supports NFSv3 (see [https://github.com/sahlberg/libnfs/issues/37 #37] and [https://github.com/sahlberg/libnfs/issues/156 #156]). Therefore do not setup a NFSv4-only server or Kodi will only be able to list the shares but cannot access them.}}
 +
{{Note|Users only need one box on the LAN to serve the content, therefore, do not repeat this for each node.  The following example assumes the user is running Arch Linux, but any NFS server will work, be it Linux or BSD, etc.}}
 +
 
 +
The NFS server is provided by {{Pkg|nfs-utils}} and this only needs to be installed on the box serving up the content.
 +
 
 +
Setup the shares:
 +
# mkdir -p /srv/nfs/{tv-shows,movies,music}
 +
# mount --bind /mnt/tv-shows /srv/nfs/tv-shows
 +
# mount --bind /mnt/movies /srv/nfs/movies
 +
# mount --bind /mnt/music /srv/nfs/music
 +
 
 +
Add the corresponding entries for these bind mounts to {{ic|/etc/fstab}}:
 +
/mnt/tv-shows /srv/nfs/tv-shows none bind 0 0
 +
/mnt/movies  /srv/nfs/movies  none bind 0 0
 +
/mnt/music    /srv/nfs/music    none bind 0 0
 +
 
 +
Share the content in {{ic|/etc/exports}}:
 +
 
 +
/srv/nfs          192.168.0.0/24(ro,fsid=0,no_subtree_check)
 +
/srv/nfs/tv-shows 192.168.0.0/24(ro,no_subtree_check,insecure)
 +
/srv/nfs/movies  192.168.0.0/24(ro,no_subtree_check,insecure)
 +
/srv/nfs/music    192.168.0.0/24(ro,no_subtree_check,insecure)
 +
 
 +
{{Tip|This example sets-up read-only exports.  See {{ic|man exports}} for additional options and configurations.}}
 +
 
 +
Whenever changes are made to {{ic|/etc/exports}}, always refresh the exports:
 +
# exportfs -rav
 +
 
 +
[[Start]] {{ic|rpcbind.service}} and {{ic|nfs-server.service}} and [[enable]] them to start automatically.
 +
 
 +
Optionally check with:
 +
# showmount -e localhost
 +
Export list for localhost:
 +
/srv/nfs/tv-shows 192.168.0.0/24
 +
/srv/nfs/movies 192.168.0.0/24
 +
/srv/nfs/music 192.168.0.0/24
  
{{Note|These instructions assume you have a working X installation. If you have not done this yet, please consult [[Beginners_Guide#Graphical_User_Interface]].}}
+
{{Note|If the box is using a firewall, ensure that it is not blocking connections. This is beyond the scope of this article.}}
  
[[pacman|Install]] {{Pkg|xbmc}} from the [[official repositories]].
+
==== Install and setup the MySQL server ====
If you plan to use the pvr extensions of xbmc you will need to install {{Pkg|xbmc-pvr-addons}}.
+
The box running the library needs to be available 24/7 and is commonly the same box that holds the media.
 +
{{Note|The following example assumes the user is running Arch Linux, but any MySQL server will work, be it Linux or BSD, etc.}}
  
== Configuration ==
+
The MySQL server is provided by {{Pkg|mariadb}} and this only needs to be installed on one box that all nodes can access.
  
=== Autostarting at boot ===
+
[[Start]] {{ic|mysqld.service}} and [[enable]] it to run at boot time.
  
To use XBMC on HTPC you may want to start XBMC automatically on boot. Since version 11.0-11 '''xbmc''' package includes the xbmc group, user, and service file necessary to do this.
+
First time setup:
 +
# mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql
 +
# mysql_secure_installation
 +
    <<follow the in-script prompts and answer "Y" to all the questions>>
  
To make XBMC start at system boot you should simply enable the service:
+
$ mysql -u root -p
 +
    <<enter the mysqld root password assigned in the first step>>
 +
MariaDB [(none)]> CREATE USER 'kodi' IDENTIFIED BY 'kodi';
 +
MariaDB [(none)]> GRANT ALL ON *.* TO 'kodi';
 +
MariaDB [(none)]> flush privileges;
 +
MariaDB [(none)]> \q
  
  # systemctl enable xbmc
+
One can optionally disable binary logging if the mysql server is only used for kodi by editing {{ic|/etc/mysql/my.cnf}} and commenting the following line:
 +
  #log-bin=mysql-bin
  
=== Enabling shutdown, restart, hibernate and suspend ===
+
No other setup to the MySQL server should be needed.
 +
{{Note|If the box is using a firewall, ensure that it is not blocking connections.  This is beyond the scope of this article.}}
  
Since version 12 XBMC supports power management via systemd logind daemon. To enable it you should have {{Pkg|polkit}}, {{Pkg|upower}} and {{Pkg|udisks}} installed on your system.
+
==== Setup Kodi to use the MySQL library and the NFS exports ====
 +
Since this example makes use of NFS shares, an optional dependency of Kodi is now required to access them. Ensure that each of the Kodi nodes has {{Pkg|libnfs}} installed.
  
In case XBMC is started using the systemd service, the session might not get initialzed properly and therefore polkit may not allow the shutdown or reboot of the system. If this happens, adding the following rule file will allow users in the ''power'' and ''storage'' group to shutdown, restart, hibernate and suspend computer.
+
===== Setup Kodi to use the common MySQL database =====
 +
To tell Kodi to use the common database, insure that Kodi is not running, then create the following file:
 +
{{hc|~/.kodi/userdata/advancedsettings.xml|
 +
<advancedsettings>
 +
  <videodatabase>
 +
    <type>mysql</type>
 +
    <host>192.168.0.105</host>
 +
    <port>3306</port>
 +
    <user>kodi</user>
 +
    <pass>kodi</pass>
 +
  </videodatabase>
  
{{hc|/etc/polkit-1/rules.d/10-xbmc.rules|2=
+
  <musicdatabase>
polkit.addRule(function(action, subject) {
+
    <type>mysql</type>
     if(action.id.match("org.freedesktop.login1.") && subject.isInGroup("power")) {
+
    <host>192.168.0.105</host>
        return polkit.Result.YES;
+
     <port>3306</port>
     }
+
    <user>kodi</user>
});
+
     <pass>kodi</pass>
 +
  </musicdatabase>
  
polkit.addRule(function(action, subject) {
+
  <videolibrary>
     if (action.id.indexOf("org.freedesktop.udisks") == 0 && subject.isInGroup("storage")) {
+
     <importwatchedstate>true</importwatchedstate>
        return polkit.Result.YES;
+
    <importresumepoint>true</importresumepoint>
    }
+
  </videolibrary>
});
+
</advancedsettings>
 
}}
 
}}
  
=== Using a remote controller ===
+
{{Tip|If using {{AUR|kodi-standalone-service}}, the default for the profile is {{ic|/var/lib/kodi/.kodi}} and be sure to chown the newly created file to the kodi user and group, i.e. {{ic|chown -R kodi:kodi /var/lib/kodi}}}}
 +
 
 +
===== Setup network shares =====
 +
Load Kodi and define the network shares that correspond to the exports by browsing to the following within the interface:
 +
Video>Files>Add Videos>Browse>Network Filesystem(NFS)
 +
 
 +
After a few seconds, the IP address corresponding to the NFS server should appear.
  
As XBMC is geared toward being a remote-controlled media center, if your computer has an IR receiver, you will probably want to set up a remote using [[LIRC]]. Once you are sure your remote is working properly (tested with {{ic|$ irw}}), add '''lircd''' to your [[Daemons#Starting_on_Boot|DAEMONS Array]] and you will be ready to create an Lircmap.xml file for it.
+
Select {{ic|/srv/nfs/tv-shows}} from the list of share and then "OK" from the menu on the right.  Assign this share the category of "TV Shows" to setup the appropriate scraper and to populate the MySQL database with the correct metadata.
  
Using your favorite text editor, you will need to go in and create an [[Wikipedia:XML|XML]] file at {{ic|~/.xbmc/userdata/Lircmap.xml}} (note the capital 'L'). Lircmap.xml format is as follows:
+
Repeat this browsing process for the "movies" and "music" and then exit Kodi once properly configured. At this point, the MySQL tables should have been created.
  
{{bc|1=<lircmap>
+
{{Note|Even if Kodi is running on the same box that is also running the NFS exports and MySQL server, one '''must''' setup the media using the nfs shares only!}}
  <remote device="devicename">
 
      <XBMC_button>LIRC_button</XBMC_button>
 
      ...
 
  </remote>
 
</lircmap>}}
 
  
* '''Device Name''' is whatever LIRC calls your remote. This is set using the '''Name''' directive in lircd.conf and can be viewed by running {{ic|$ irw}} and pressing a few buttons on the remote. IRW will report the name of the button pressed and the name of the remote will appear on the end of the line.
+
==== Cloning the configuration to other nodes on the network ====
 +
To set up another Kodi node on the network to use this library, simply copy {{ic|~/.kodi/userdata/advancedsettings.xml}} to that box and restart Kodi.
  
* '''XBMC_button''' is the name of the button as defined in [http://wiki.xbmc.org/index.php?title=Keymap.xml keymap.xml].
+
{{Note|There is NO need to copy any other files or to do any other setup steps on the new kodi node. The nfs exports, the metadata for the programming, any stop/start times, view status, etc. are all stored in the MySQL tables.}}
  
* '''LIRC_button''' is the name as defined in {{ic|lircd.conf}}. If you automatically generated your lircd.conf using {{ic|# irrecord}}, these are the names you selected for your button then. Refer back to [[LIRC]] for more information.
+
=== Using a remote control ===
 +
As Kodi is geared toward being a remote-controlled media center via an official app, physical remote control, or USB/bluetooth keyboard/mouse.
  
* You may want to check out the very thorough [http://wiki.xbmc.org/index.php?title=Lircmap.xml Lircmap.xml] page over at the [http://wiki.xbmc.org/index.php?title=Main_Page XBMC Wiki] for more help and information on this subject.
+
==== Using the Android or iOS app ====
 +
Both Android and iOS users can use the official app (currently free of charge) to control kodi once it is correctly setup to do so. Steps to configure both Kodi and the app are detailed on the [http://kodi.wiki/view/Official_Kodi_Remote Official Kodi Remote] page.
  
==== MCE remote with Lirc and Systemd ====
+
==== Using a physical remote control ====
 +
Any PC with a supported IR receiver/remote, can use remote using [[LIRC]] or using the native kernel supported modules.  Configuring specific remotes with lirc is covered on the [[LIRC]] article.
  
Install {{Pkg|lirc-utils}} and link the mce config:
+
To work properly with Kodi, a file will be required that maps the lirc events to Kodi keypresses.  Create an [[Wikipedia:XML|XML]] file at {{ic|~/.kodi/userdata/Lircmap.xml}} (note the capital 'L').
  
# ln -s /usr/share/lirc/mceusb/lircd.conf.mceusb /etc/lirc/lircd.conf
+
{{Note|Users running Kodi started with {{AUR|kodi-standalone-service}} will find the kodi home (~) under {{ic|/var/lib/kodi}} and should substitute this in for the shortcut above. Also make sure that if creating this file as the root user, it gets proper ownership as kodi:kodi when finished.}}
 +
Lircmap.xml format is as follows:
  
Then, make sure the remote is using the lirc protocol:
+
{{bc|1=<lircmap>
$ cat /sys/class/rc/rc0/protocols
+
  <remote device="devicename">
If not, issue:
+
      <XBMC_button>LIRC_button</XBMC_button>
# echo lirc > /sys/class/rc/rc0/protocols
+
      ...
 +
  </remote>
 +
</lircmap>}}
  
A udev rule can be added to make lirc the default. A write rule does not seem to work, so a simple RUN command can be executed instead.
+
* '''Device Name''' is whatever LIRC calls the remote. This is set using the '''Name''' directive in lircd.conf and can be viewed by running {{ic|$ irw}} and pressing a few buttons on the remote. IRW will report the name of the button pressed and the name of the remote will appear on the end of the line.
  
{{hc|/etc/udev/rules.d/99-lirc.rules|2=
+
* '''XBMC_button''' is the name of the button as defined in [http://kodi.wiki/index.php?title=Keymap.xml keymap.xml].
KERNEL=="rc*", SUBSYSTEM=="rc", ATTR{protocols}=="*lirc*", RUN+="/bin/sh -c 'echo lirc > $sys$devpath/protocols'"}}
 
  
{{Note|If this does not work, follow the suggestion to use tmpfiles.d as specified in the [[LIRC#Kernel_module_change|LIRC wiki]] to set the remote to the lirc protocol at boot time.}}
+
* '''LIRC_button''' is the name as defined in {{ic|lircd.conf}}. If lircd.conf was autogenerated using {{ic|# irrecord}}, these are the names selected for the buttons. Refer back to [[LIRC]] for more information.
  
Next, specify the lirc device. This varies with kernel version. As of 3.6.1 {{ic|/dev/lirc0}} should work with the default driver.
+
* A very thorough [http://kodi.wiki/index.php?title=Lircmap.xml Lircmap.xml page] hosted on the [http://kodi.wiki/index.php?title=Main_Page Kodi Wiki] should be consulted for more help and information on this subject as this is out of scope of this article.
  
{{hc|/etc/conf.d/lircd.conf|2=
+
=== HDMI-CEC with Pulse Eight USB-CEC ===
#
 
# Parameters for lirc daemon
 
#
 
  
LIRC_DEVICE="/dev/lirc0"
+
An elegant way of getting remote functions in Kodi is using [[wikipedia:Consumer_Electronics_Control#CEC|CEC]], a protocol that is part of the HDMI specification. Most modern TVs support CEC, although some manufacturers advertise the feature under other names. Apart from a CEC-enabled TV some hardware that takes the CEC signals coming from the TV and present them in a way that Kodi can understand is also needed. One such device is the [http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx USB-CEC adapter] from Pulse Eight. Hooking up the USB-CEC is pretty simple, but in order for it to work in Arch we have to do a few things.
LIRC_DRIVER="default"
 
LIRC_EXTRAOPTS=""
 
LIRC_CONFIGFILE=""}}
 
  
The default service file for lirc ignores this conf file. So we need to create a custom one.
+
Install {{ic|libcec}}.
  
{{hc|/etc/systemd/system/lirc.service|2=
+
When connected, the USB-CEC's {{ic|/dev}} entry (usually {{ic|/dev/ttyACM*}}) will default to being owned by the {{ic|uucp}} group, so in order to use the device the user running Kodi needs to belong to that group. The user also needs to belong to the {{ic|lock}} group, otherwise Kodi will be unable to connect to the device. To add a user to both groups, run
[Unit]
 
Description=Linux Infrared Remote Control
 
  
[Service]
+
# usermod -aG uucp,lock [username]
EnvironmentFile=/etc/conf.d/lircd.conf
 
ExecStartPre=/usr/bin/ln -sf /run/lirc/lircd /dev/lircd
 
ExecStartPre=/usr/bin/ln -sf /dev/lirc0 /dev/lirc
 
ExecStart=/usr/sbin/lircd --pidfile=/run/lirc/lircd.pid --device=${LIRC_DEVICE} --driver=${LIRC_DRIVER}
 
Type=forking
 
PIDFile=/run/lirc/lircd.pid
 
  
[Install]
+
If more than one user uses Kodi, repeat the command for all those users. If, for example, one is using {{ic|kodi-standalone}}, the relevant command is
WantedBy=multi-user.target}}
 
  
Finally, enable and start the lirc service:
+
# usermod -aG uucp,lock kodi
  
# systemctl enable lirc
+
Remember that modifying the groups of any logged in users means those users need to log out and login again in order for the changes to take effect.
# systemctl start lirc
 
  
This should give a fully working mce remote.
+
{{Note|Trying to use the USB-CEC without belonging to above groups may lead to problems, including Kodi crashes, so make sure the correct user belongs to both groups.}}
  
=== Fullscreen mode stretches XBMC across multiple displays ===
+
==Tips and Tricks ==
 +
=== Keep a log of what is watched ===
 +
Keep track of every video watched on kodi with {{AUR|kodi-logger}}.
  
If you have got a multi-monitor setup and do not want XBMC to stretch across all screens, you can restrict the fullscreen mode to one display, by setting the environment variable SDL_VIDEO_FULLSCREEN_HEAD to the number of the desired target display. For example if you want XBMC to show up on display 0 you can add the following line to your [[Bashrc]]:
+
=== CLI tool for kodi ===
 +
A powerful CLI tool for use with kodi is {{AUR|texturecache}}.  Users can accomplish many task from library management to querying what is currently playing.
  
SDL_VIDEO_FULLSCREEN_HEAD=0
+
=== Enable Hardware video acceleration ===
 +
Enable and configure [[Hardware video acceleration]] to speed up playback performance.
  
{{Note|Mouse cursor will be held inside screen with XBMC.}}
+
Restart Kodi and enable the hardware backend(s) in Playback under Settings.
  
 
=== Slowing down CD/DVD drive speed ===
 
=== Slowing down CD/DVD drive speed ===
Line 140: Line 310:
 
}}
 
}}
  
Replace {{ic|sr0}} with the device name of your optical drive. Replace {{ic|-x 2}} with {{ic|-x 4}} if you prefer 4x-speed instead of 2x-speed.
+
Replace {{ic|sr0}} with the device name of the optical drive. Replace {{ic|-x 2}} with {{ic|-x 4}} if the preference is 4x-speed instead of 2x-speed.
  
 
After creating the file, reload the udev rules with
 
After creating the file, reload the udev rules with
 
  # udevadm control --reload
 
  # udevadm control --reload
 +
 +
=== Use port 80 for webserver ===
 +
 +
Kodi has a webservice that allows interaction through a web-interface. By default, it uses port {{ic|8080}} as {{ic|80}} requires root privileges. Use the following to permit it to use low port numbers:
 +
  # setcap 'cap_net_bind_service=+ep' /usr/lib/kodi/kodi.bin
 +
 +
[[Restart]] {{ic|kodi.service}} and set port {{ic|80}} in the configuration menu (''Services->Webserver->Port'').
 +
 +
=== Using ALSA ===
 +
 +
If [[PulseAudio]] does not work properly, try using ALSA directly by starting Kodi with the {{ic|1=AE_SINK=ALSA}} environment variable.  The Kodi wiki for NUC devices provides [http://kodi.wiki/view/HOW-TO:Install_Kodi_on_an_Intel_NUC#disable_PulseAudio instructions]
 +
 +
=== Raspberry Pi (all generations) ===
 +
 +
Kodi runs smoothly on the Raspberry Pi (RPi), RPi2, and RPi3. Some helpful tips to consider:
 +
* [[Install]] either the ''kodi-rbp'' (stable) or ''kodi-rbp-git'' (dev) package instead of ''kodi'' from the [http://archlinuxarm.org/packages Arch Linux ARM repository].
 +
* This package ships with a systemd service to run in standalone mode.
 +
* The memory reserved for GPU is 64 MB by default. This is insufficient for GPU accelerated HD video playback. Users can increase this value via a simple edit to the {{ic|gpu_mem}} tag in {{ic|/boot/config.txt}}.  A value of at least 128 MB is recommended for RPi version 1 while a value of 256 is recommended for RPi2 and 3.
 +
 +
=== TV is not detected unless powered on first ===
 +
Some TVs (LG brand for example) only report their capabilities via EDID through HDMI when powered on '''before''' the RPi.  The effects of this can manifest in one of two ways:
 +
# Despite being connected, the TV will be unable to detect a signal from the HDMI source until the RPi is rebooted.
 +
# The signal will be detected but incorrectly by the RPi to the point of the GUI looking distorted when compared to having the TV on first, then rebooting the RPi.
 +
 +
Both conditions are easily fixed. See: [http://kodi.wiki/view/Raspberry_Pi_FAQ#TV_is_not_detected_unless_powered_on_first Raspberry_Pi_FAQ#TV_is_not_detected_unless_powered_on_first].
 +
 +
==== Run kodi in a window manager ====
 +
Users running kodi in a [[Window manager]] may see a black screen at exit.  To fix this, try switching to another tty.  A possible solution is to run kodi with this script (running as the root user):
 +
{{hc|kodi.sh|
 +
#!/bin/bash
 +
kodi-standalone
 +
sudo chvt 2
 +
sleep 1
 +
sudo chvt 1
 +
}}
 +
To make sure that [[sudo]] does not ask for password for {{ic|chvt}} add this line to {{ic|sudoers}} file:
 +
{{hc|/etc/sudoers|
 +
''UserNameHere'' ALL&#61;NOPASSWD: /usr/bin/chvt
 +
}}
 +
 +
==== USB DAC not working ====
 +
Users of USB DAC/sound cards may experience distorted sound/clicks/pops or no sound at all when selecting it from Audio settings.  A possible fix:
 +
 +
Open {{ic|guisettings.xml}} (it should be under {{ic|/var/lib/kodi/.kodi/userdata/}} if using the supplied {{ic|kodi.service}}) and change
 +
 +
<processquality default="'''true'''">'''101'''</processquality>
 +
 +
to
 +
 +
<processquality default="'''false'''">'''100'''</processquality>
 +
 +
== Troubleshooting ==
 +
 +
===Accessing kodi logs ===
 +
In case of an error the first point to start investigation can be {{ic|~/.kodi/temp/kodi.log}}.
 +
 +
=== Fullscreen mode stretches Kodi across multiple displays ===
 +
 +
For a multi-monitor setup, Kodi may default to stretching across all screens.  One can restrict the fullscreen mode to one display by setting the environment variable SDL_VIDEO_FULLSCREEN_HEAD to the number of the desired target display. For example, having Kodi show up on display 0, add the following line to the Kodi user's {{ic|~/.bashrc}} configuration:
 +
 +
SDL_VIDEO_FULLSCREEN_HEAD=0
 +
 +
{{Note|Mouse cursor will be held inside screen with Kodi.}}
 +
 +
=== Video tearing on Intel HD Graphics ===
 +
Users observing tearing when watching a movie try this:
 +
https://bbs.archlinux.org/viewtopic.php?id=176651
 +
 +
Try a different X11 compositor like {{Pkg|compton}} as an alternative with [[Xfce]] which reduces video tearing. There is no essential need to install the intel driver. A tutorial how to configure compton with Xfce can be found [http://duncanlock.net/blog/2013/06/07/how-to-switch-to-compton-for-beautiful-tear-free-compositing-in-xfce/ here].
 +
 +
=== Soft subtitles not displaying ===
 +
 +
The {{Pkg|ffmpeg}} package is used to extract the subtitles.
 +
 +
=== H.264 playback is using only a single core ===
 +
 +
{{Tip|By default, press {{ic|O}} during playback to show codec information and CPU usage. More information about this overlay can be found [http://kodi.wiki/view/Codecinfo here].}}
 +
 +
If your setup does not or cannot make use of hardware acceleration, disable it and explicitly set video decoding to software.
 +
This is because [http://forum.kodi.tv/showthread.php?tid=170084&pid=1789661#pid1789661 H.264 decoding is only multithreaded when video decoding is set to software].
 +
To achieve this, go to {{ic|System Settings}} and then to {{ic|Video}}. Set the {{ic|settings level}} to {{ic|Advanced}} or {{ic|Expert}} and go to {{ic|Acceleration}}.
 +
There, set {{ic|Decoding method}} to {{ic|software}}.
 +
 +
=== Kodi hangs on exit, fully occupying one CPU core, UI unresponsive ===
 +
 +
This problem can arise with third-party plugins installed, there is some issue with their termination[https://www.linuxquestions.org/questions/linux-software-2/kodi-freezes-on-exit-kodi-bin-won't-die-4175588180/],[https://www.reddit.com/r/archlinux/comments/5029oo/kodi_freezes_on_exit_kodibin_wont_die/].
 +
 +
Workaround: find proper UI description file (''DialogButtonMenu.xml'') and tweak exit button type from internal Kodi's ''Quit()'' function call to sending signal from outside system to Kodi. Here is one-liner that makes modifications to any skin from your default Kodi package:
 +
find /usr/share/kodi/addons/skin.* -name DialogButtonMenu.xml | xargs sudo sed -i "s%<onclick>Quit()</onclick>%<onclick>System.Exec ("killall --signal SIGHUP kodi.bin")</onclick>%"
  
 
== See also ==
 
== See also ==
  
* [http://wiki.xbmc.org/index.php?title=Main_Page XBMC Wiki] - Excellent resource with much information about Arch Linux specifically
+
* [http://kodi.wiki/index.php?title=Main_Page Kodi Wiki] - Excellent resource with much information about Arch Linux specifically
 +
* http://superrepo.org/ - xbmc Plug-in library
 +
* http://www.hdpfans.com/thread-329076-1-1.html - Kodi/xbmc Chinese plug-in library installation method
 +
* https://github.com/taxigps/xbmc-addons-chinese - xbmc-addons-chinese
 +
{{Note|xbmc-addons-chinese:Addon scripts, plugins, and skins for XBMC Media Center. Special for chinese laguage.}}

Latest revision as of 10:19, 19 May 2017

Kodi (formerly known as XBMC) is an award-winning free and open source (GPL) software media player and entertainment hub that can be installed on Linux, OSX, Windows, iOS and Android, featuring a 10-foot user interface for use with televisions and remote controls. These can all be played directly from a CD/DVD, or from the hard-drive. Kodi can also play multimedia from a computer over a local network (LAN), or play media streams directly from the Internet. It can also be used to play and record live TV using a tuner, a backend server and a PVR plugin; more information about this can be found on the Kodi wiki.

Installation

Install the kodi package. Be sure to install the optional dependencies listed by pacman that apply to your specific use-case.

Note: Users of Arch ARM should be aware that several different kodi packages with specific hardware support are available.

Configuration

Autostarting at boot or ondemand

The kodi package supplies /usr/bin/kodi which can be run by any user on a on-demand basis. A stand-alone wrapper script /usr/bin/kodi-standalone is also provided that allows a minimal system and an unprivileged user to run the application. The is advantageous for several reasons:

  1. An unprivileged user cannot access a shell by definition.
  2. Running without a full blown DE is lighter and more simplistic.
  3. When paired with a systemd unit (or equivalent, see below), this make the box on which kodi is running more like an appliance and very robust.

There are several methods to it this described below.

Warning: Select only one of the methods listed below.

Kodi-standalone-service

The kodi-standalone-serviceAUR package provides kodi.service and automatically creates the unprivileged user to run Kodi in standalone mode. Although the correct driver is an assumed dependency, no extra Xorg packages are needed. Start kodi.service and enable it to run at boot time. No additional configuration should be required for most users, however, if kodi.service fails to start, see Xorg#Rootless Xorg (v1.16).

Note:
  • The kodi user is unprivileged meaning it cannot login (default shell is /usr/bin/nologin).
  • The home directory for the kodi user created is /var/lib/kodi not /home/kodi.
Warning: Users of Arch ARM should not attempt to install this package as breakage will occur!

Xsession with LightDM

Note: This assumes that the user has created an kodi user named kodiuser on the system and that the following file is present as described.
Note: lightdm does not pull in an X server as a required dependency, it is optional. The X server listed as an optional dependency (xephyr) does not work when run as root by lightdm.service (Bug to have optional dependency modified) (Upstream Bug). Install xorg-server.

To use LightDM with automatic login, see LightDM#Enabling autologin and LightDM#Enabling interactive passwordless login. Kodi includes kodi.desktop as xsession.

/etc/lightdm/lightdm.conf
[Seat:seat0]
pam-service=lightdm-autologin
autologin-user=kodiuser
autologin-user-timeout=0
user-session=Kodi

Socket activation

Socket activation can be used to start Kodi when the user starts a remote control app or on a connection to Kodi's html control port. Start listening with systemctl start kodi@user.socket (replace user with the user running Kodi to be started as).

The kodi-standalone-socket-activationAUR package provides kodi@.service but not kodi@.socket. Depending on the setup, one may want to change the port in kodi@.socket. This can be done by manually using the following systemd files.

/etc/systemd/system/kodi@.service
[Unit]
Description=Launch Kodi on main display

[Service]
Type=oneshot
Environment=DISPLAY=:0.0
Nice=-1
ExecStart=/usr/bin/su %i /usr/bin/kodi
ExecStartPost=/usr/bin/bash -c "sleep 15 && systemctl start kodi@%i.socket"

[Install]
WantedBy=multi-user.target
/etc/systemd/system/kodi@.socket
[Unit]
Conflicts=kodi@%i.service

[Socket]
# listen for WOL packets
#ListenDatagram=9

# change this to Kodi's http control port
ListenStream=8082

[Install]
WantedBy=sockets.target

Start from remote control with LIRC / irexec

Kodi can be configured to start via a key press. Users will need kodi-standalone-serviceAUR and lirc. This can be useful on setups running 24/7 and having kodi up on demand.

See the corresponding LIRC article and create a functional setup with a remote. Also, the package kodi-standalone-serviceAUR has to be installed.

Generate the file /var/lib/kodi/.lircrc with the following content:

/var/lib/kodi/.lircrc

begin
prog = irexec
remote = devinput
button = KEY_MEDIA
config = pgrep kodi-standalone || /usr/bin/kodi-standalone -l /run/lirc/lircd
repeat = 0
end

Adopt button to whatever button on the remote is to start Kodi. One can use irw (see LIRC#Usage) to find out the correct values for remote and button.

Next copy kodi.service from /usr/lib/systemd/system/ to /etc/systemd/system/ and change the line

ExecStart = /usr/bin/kodi-standalone -l /run/lirc/lircd

to

ExecStart = /usr/bin/irexec

Start kodi.service and enable it to run at boot time.

Sharing a database across multiple nodes

If multiple PCs on the same network are running Kodi, they can be configured to share a single media library (video and music). The advantage of this is that key metadata are stored in one place, and are shared/updated by all nodes on the network. For example, users of this setup can:

  • Stop watching a movie or show in one room then finish watching it in another room automatically.
  • Share watched and unwatched status for media on all nodes.
  • Simplify the setup with only a single library to maintain.

Several key things are needed for this to work:

  • Network exposed media (via protocols that Kodi can read, e.g. NFS or Samba).
  • A MySQL server (Arch uses mariadb).
Note: The following guide is only an example of one configuration and is not meant to be limiting but illustrative. Key steps are shown but a detailed discussion is not offered.

These assumptions are used for the guide, substitute to reflect your setup:

  • The media is located under following mount points: /mnt/tv-shows /mnt/movies /mnt/music.
  • The network addresses of all nodes are within the 192.168.0.* subnet range.
  • The IP address of the machine running both the NFS exports and the MySQL database is 192.168.0.105.
  • Each Kodi box is referred to as a node.
  • The Linux user running Kodi is 'kodi' on all nodes.

For additional info, refer to the official Kodi wiki.

Setup an NFS server

This section provides an example using NFS exports, but as mentioned above, any protocol that Kodi can read is acceptable.

Warning: Kodi is using libnfs to access NFS shares which only supports NFSv3 (see #37 and #156). Therefore do not setup a NFSv4-only server or Kodi will only be able to list the shares but cannot access them.
Note: Users only need one box on the LAN to serve the content, therefore, do not repeat this for each node. The following example assumes the user is running Arch Linux, but any NFS server will work, be it Linux or BSD, etc.

The NFS server is provided by nfs-utils and this only needs to be installed on the box serving up the content.

Setup the shares:

# mkdir -p /srv/nfs/{tv-shows,movies,music}
# mount --bind /mnt/tv-shows /srv/nfs/tv-shows
# mount --bind /mnt/movies /srv/nfs/movies
# mount --bind /mnt/music /srv/nfs/music

Add the corresponding entries for these bind mounts to /etc/fstab:

/mnt/tv-shows /srv/nfs/tv-shows none bind 0 0
/mnt/movies   /srv/nfs/movies   none bind 0 0
/mnt/music    /srv/nfs/music    none bind 0 0

Share the content in /etc/exports:

/srv/nfs          192.168.0.0/24(ro,fsid=0,no_subtree_check)
/srv/nfs/tv-shows 192.168.0.0/24(ro,no_subtree_check,insecure)
/srv/nfs/movies   192.168.0.0/24(ro,no_subtree_check,insecure)
/srv/nfs/music    192.168.0.0/24(ro,no_subtree_check,insecure)
Tip: This example sets-up read-only exports. See man exports for additional options and configurations.

Whenever changes are made to /etc/exports, always refresh the exports:

# exportfs -rav

Start rpcbind.service and nfs-server.service and enable them to start automatically.

Optionally check with:

# showmount -e localhost
Export list for localhost:
/srv/nfs/tv-shows 192.168.0.0/24
/srv/nfs/movies 192.168.0.0/24
/srv/nfs/music 192.168.0.0/24
Note: If the box is using a firewall, ensure that it is not blocking connections. This is beyond the scope of this article.

Install and setup the MySQL server

The box running the library needs to be available 24/7 and is commonly the same box that holds the media.

Note: The following example assumes the user is running Arch Linux, but any MySQL server will work, be it Linux or BSD, etc.

The MySQL server is provided by mariadb and this only needs to be installed on one box that all nodes can access.

Start mysqld.service and enable it to run at boot time.

First time setup:

# mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql
# mysql_secure_installation
   <<follow the in-script prompts and answer "Y" to all the questions>>
$ mysql -u root -p
   <<enter the mysqld root password assigned in the first step>>
MariaDB [(none)]> CREATE USER 'kodi' IDENTIFIED BY 'kodi';
MariaDB [(none)]> GRANT ALL ON *.* TO 'kodi';
MariaDB [(none)]> flush privileges;
MariaDB [(none)]> \q

One can optionally disable binary logging if the mysql server is only used for kodi by editing /etc/mysql/my.cnf and commenting the following line:

#log-bin=mysql-bin

No other setup to the MySQL server should be needed.

Note: If the box is using a firewall, ensure that it is not blocking connections. This is beyond the scope of this article.

Setup Kodi to use the MySQL library and the NFS exports

Since this example makes use of NFS shares, an optional dependency of Kodi is now required to access them. Ensure that each of the Kodi nodes has libnfs installed.

Setup Kodi to use the common MySQL database

To tell Kodi to use the common database, insure that Kodi is not running, then create the following file:

~/.kodi/userdata/advancedsettings.xml
<advancedsettings>
  <videodatabase>
    <type>mysql</type>
    <host>192.168.0.105</host>
    <port>3306</port>
    <user>kodi</user>
    <pass>kodi</pass>
  </videodatabase>

  <musicdatabase>
    <type>mysql</type>
    <host>192.168.0.105</host>
    <port>3306</port>
    <user>kodi</user>
    <pass>kodi</pass>
  </musicdatabase>

  <videolibrary>
    <importwatchedstate>true</importwatchedstate>
    <importresumepoint>true</importresumepoint>
  </videolibrary>
</advancedsettings>
Tip: If using kodi-standalone-serviceAUR, the default for the profile is /var/lib/kodi/.kodi and be sure to chown the newly created file to the kodi user and group, i.e. chown -R kodi:kodi /var/lib/kodi
Setup network shares

Load Kodi and define the network shares that correspond to the exports by browsing to the following within the interface:

Video>Files>Add Videos>Browse>Network Filesystem(NFS)

After a few seconds, the IP address corresponding to the NFS server should appear.

Select /srv/nfs/tv-shows from the list of share and then "OK" from the menu on the right. Assign this share the category of "TV Shows" to setup the appropriate scraper and to populate the MySQL database with the correct metadata.

Repeat this browsing process for the "movies" and "music" and then exit Kodi once properly configured. At this point, the MySQL tables should have been created.

Note: Even if Kodi is running on the same box that is also running the NFS exports and MySQL server, one must setup the media using the nfs shares only!

Cloning the configuration to other nodes on the network

To set up another Kodi node on the network to use this library, simply copy ~/.kodi/userdata/advancedsettings.xml to that box and restart Kodi.

Note: There is NO need to copy any other files or to do any other setup steps on the new kodi node. The nfs exports, the metadata for the programming, any stop/start times, view status, etc. are all stored in the MySQL tables.

Using a remote control

As Kodi is geared toward being a remote-controlled media center via an official app, physical remote control, or USB/bluetooth keyboard/mouse.

Using the Android or iOS app

Both Android and iOS users can use the official app (currently free of charge) to control kodi once it is correctly setup to do so. Steps to configure both Kodi and the app are detailed on the Official Kodi Remote page.

Using a physical remote control

Any PC with a supported IR receiver/remote, can use remote using LIRC or using the native kernel supported modules. Configuring specific remotes with lirc is covered on the LIRC article.

To work properly with Kodi, a file will be required that maps the lirc events to Kodi keypresses. Create an XML file at ~/.kodi/userdata/Lircmap.xml (note the capital 'L').

Note: Users running Kodi started with kodi-standalone-serviceAUR will find the kodi home (~) under /var/lib/kodi and should substitute this in for the shortcut above. Also make sure that if creating this file as the root user, it gets proper ownership as kodi:kodi when finished.

Lircmap.xml format is as follows:

<lircmap>
  <remote device="devicename">
      <XBMC_button>LIRC_button</XBMC_button>
      ...
  </remote>
</lircmap>
  • Device Name is whatever LIRC calls the remote. This is set using the Name directive in lircd.conf and can be viewed by running $ irw and pressing a few buttons on the remote. IRW will report the name of the button pressed and the name of the remote will appear on the end of the line.
  • XBMC_button is the name of the button as defined in keymap.xml.
  • LIRC_button is the name as defined in lircd.conf. If lircd.conf was autogenerated using # irrecord, these are the names selected for the buttons. Refer back to LIRC for more information.
  • A very thorough Lircmap.xml page hosted on the Kodi Wiki should be consulted for more help and information on this subject as this is out of scope of this article.

HDMI-CEC with Pulse Eight USB-CEC

An elegant way of getting remote functions in Kodi is using CEC, a protocol that is part of the HDMI specification. Most modern TVs support CEC, although some manufacturers advertise the feature under other names. Apart from a CEC-enabled TV some hardware that takes the CEC signals coming from the TV and present them in a way that Kodi can understand is also needed. One such device is the USB-CEC adapter from Pulse Eight. Hooking up the USB-CEC is pretty simple, but in order for it to work in Arch we have to do a few things.

Install libcec.

When connected, the USB-CEC's /dev entry (usually /dev/ttyACM*) will default to being owned by the uucp group, so in order to use the device the user running Kodi needs to belong to that group. The user also needs to belong to the lock group, otherwise Kodi will be unable to connect to the device. To add a user to both groups, run

# usermod -aG uucp,lock [username]

If more than one user uses Kodi, repeat the command for all those users. If, for example, one is using kodi-standalone, the relevant command is

# usermod -aG uucp,lock kodi

Remember that modifying the groups of any logged in users means those users need to log out and login again in order for the changes to take effect.

Note: Trying to use the USB-CEC without belonging to above groups may lead to problems, including Kodi crashes, so make sure the correct user belongs to both groups.

Tips and Tricks

Keep a log of what is watched

Keep track of every video watched on kodi with kodi-loggerAUR.

CLI tool for kodi

A powerful CLI tool for use with kodi is texturecacheAUR. Users can accomplish many task from library management to querying what is currently playing.

Enable Hardware video acceleration

Enable and configure Hardware video acceleration to speed up playback performance.

Restart Kodi and enable the hardware backend(s) in Playback under Settings.

Slowing down CD/DVD drive speed

The eject program from the util-linux package does a nice job for this, but its setting is cleared as soon as the media is changed.

This udev-rule reduces the speed permanently:

/etc/udev/rules.d/dvd-speed.rules
KERNEL=="sr0", ACTION=="change", ENV{DISK_MEDIA_CHANGE}=="1", RUN+="/usr/bin/eject -x 2 /dev/sr0"

Replace sr0 with the device name of the optical drive. Replace -x 2 with -x 4 if the preference is 4x-speed instead of 2x-speed.

After creating the file, reload the udev rules with

# udevadm control --reload

Use port 80 for webserver

Kodi has a webservice that allows interaction through a web-interface. By default, it uses port 8080 as 80 requires root privileges. Use the following to permit it to use low port numbers:

 # setcap 'cap_net_bind_service=+ep' /usr/lib/kodi/kodi.bin

Restart kodi.service and set port 80 in the configuration menu (Services->Webserver->Port).

Using ALSA

If PulseAudio does not work properly, try using ALSA directly by starting Kodi with the AE_SINK=ALSA environment variable. The Kodi wiki for NUC devices provides instructions

Raspberry Pi (all generations)

Kodi runs smoothly on the Raspberry Pi (RPi), RPi2, and RPi3. Some helpful tips to consider:

  • Install either the kodi-rbp (stable) or kodi-rbp-git (dev) package instead of kodi from the Arch Linux ARM repository.
  • This package ships with a systemd service to run in standalone mode.
  • The memory reserved for GPU is 64 MB by default. This is insufficient for GPU accelerated HD video playback. Users can increase this value via a simple edit to the gpu_mem tag in /boot/config.txt. A value of at least 128 MB is recommended for RPi version 1 while a value of 256 is recommended for RPi2 and 3.

TV is not detected unless powered on first

Some TVs (LG brand for example) only report their capabilities via EDID through HDMI when powered on before the RPi. The effects of this can manifest in one of two ways:

  1. Despite being connected, the TV will be unable to detect a signal from the HDMI source until the RPi is rebooted.
  2. The signal will be detected but incorrectly by the RPi to the point of the GUI looking distorted when compared to having the TV on first, then rebooting the RPi.

Both conditions are easily fixed. See: Raspberry_Pi_FAQ#TV_is_not_detected_unless_powered_on_first.

Run kodi in a window manager

Users running kodi in a Window manager may see a black screen at exit. To fix this, try switching to another tty. A possible solution is to run kodi with this script (running as the root user):

kodi.sh
#!/bin/bash
kodi-standalone
sudo chvt 2 
sleep 1
sudo chvt 1

To make sure that sudo does not ask for password for chvt add this line to sudoers file:

/etc/sudoers
UserNameHere ALL=NOPASSWD: /usr/bin/chvt

USB DAC not working

Users of USB DAC/sound cards may experience distorted sound/clicks/pops or no sound at all when selecting it from Audio settings. A possible fix:

Open guisettings.xml (it should be under /var/lib/kodi/.kodi/userdata/ if using the supplied kodi.service) and change

<processquality default="true">101</processquality>

to

<processquality default="false">100</processquality>

Troubleshooting

Accessing kodi logs

In case of an error the first point to start investigation can be ~/.kodi/temp/kodi.log.

Fullscreen mode stretches Kodi across multiple displays

For a multi-monitor setup, Kodi may default to stretching across all screens. One can restrict the fullscreen mode to one display by setting the environment variable SDL_VIDEO_FULLSCREEN_HEAD to the number of the desired target display. For example, having Kodi show up on display 0, add the following line to the Kodi user's ~/.bashrc configuration:

SDL_VIDEO_FULLSCREEN_HEAD=0
Note: Mouse cursor will be held inside screen with Kodi.

Video tearing on Intel HD Graphics

Users observing tearing when watching a movie try this: https://bbs.archlinux.org/viewtopic.php?id=176651

Try a different X11 compositor like compton as an alternative with Xfce which reduces video tearing. There is no essential need to install the intel driver. A tutorial how to configure compton with Xfce can be found here.

Soft subtitles not displaying

The ffmpeg package is used to extract the subtitles.

H.264 playback is using only a single core

Tip: By default, press O during playback to show codec information and CPU usage. More information about this overlay can be found here.

If your setup does not or cannot make use of hardware acceleration, disable it and explicitly set video decoding to software. This is because H.264 decoding is only multithreaded when video decoding is set to software. To achieve this, go to System Settings and then to Video. Set the settings level to Advanced or Expert and go to Acceleration. There, set Decoding method to software.

Kodi hangs on exit, fully occupying one CPU core, UI unresponsive

This problem can arise with third-party plugins installed, there is some issue with their termination[1],[2].

Workaround: find proper UI description file (DialogButtonMenu.xml) and tweak exit button type from internal Kodi's Quit() function call to sending signal from outside system to Kodi. Here is one-liner that makes modifications to any skin from your default Kodi package:

find /usr/share/kodi/addons/skin.* -name DialogButtonMenu.xml | xargs sudo sed -i "s%<onclick>Quit()</onclick>%<onclick>System.Exec ("killall --signal SIGHUP kodi.bin")</onclick>%"

See also

Note: xbmc-addons-chinese:Addon scripts, plugins, and skins for XBMC Media Center. Special for chinese laguage.