Official Kodi Wiki - User contributions [en]

Settings/Live TV/Channels

2026-06-17T05:36:39Z

Postcd: /* "with" does not give absolute clarity about direction */

{{Mininav|[[Settings]]|[[Settings/Live_TV|PVR & Live TV]] }}

__TOC__

<gallery mode="packed" widths="600px" heights="337px">
File:Settings-PVR-Channels-01.jpg
</gallery>

= General =

== Synchronise channel groups from backend(s) ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| Imports channel groups from the backend (if supported) and deletes user-created groups from the frontend if they are not found on the backend server.
|}

== Use channel order from backend(s) ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| Sort channels by the channel number used by the backend, but apply local numbering for the channels.
|}

== Use channel numbers from backend ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| When enabled, {{Kodi}} will use the channel numbering from the backend.<br />When disabled, {{Kodi}} will assign numbering or you may use the Channel Manager to manually configure them.<br />To avoid conflict between PVR servers, this setting is available only when a single PVR backend is used.
|}

== Start group channel numbers from 1 ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| When the previous setting is disabled, {{Kodi}} can apply sequential numbering starting from channel 1
|}

== Channel manager ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| Opens the Channel Manager, which allows modifying the channel ordering, channel names, icons, etc.<br>
See: '''[[Settings/Live_TV/Channel_manager|Channel Manager]]'''
|}

== Group manager ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| Opens the Group Manager, which allows for the management of channel groups and their populations.<br>
See: '''[[Settings/Live_TV/Group_manager|Group Manager]]'''
|}

== Search for channels ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| Instruct the backend to search for channels (if supported by the add-on and backend)
|}

= Icons =

== Folder with channel icons ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| Folder containing TV and Radio channel logos to be displayed in {{kodi}}.
Logo files should be either *.png or *.jpg.
For the logos to automatically match with their respective channels, one of the following conditions must be met:
# The logos must have the exact same name as the channel or
# Named with the id in iUniqueId of the TVxx.db (eg. 1558003334.png).
#* If the channel label has formatting codes such as colours, bold or italics, they must be in the filename
#* Any '/' character must be replaced by '_' in the filename (eg. ''[COLOR red]My Channel[/COLOR]'' will be named ''[COLOR red]My Channel[_COLOR].png'').
See- '''[[Live TV Artwork]]'''
|}

== Scan for missing icons ==
{|
|- valign="top"
| width=120px| {{nowrap|'''Settings level:'''}}
| Advanced
|- valign="top"
| '''Description:'''
| Scan the nominated folder for channel icons missing from {{kodi}}
|}

{{Top}}
{{Updated|21}}

[[Category:PVR]]
[[Category:Settings]]

Archive:Linux FAQ

2020-01-28T09:10:56Z

Postcd: /* How to autostart Kodi in desktop mode */

{{mininav| [[Linux]] {{l2| [[FAQ]] }} }}

{{notice|1= {{bigger|1= The Linux FAQ is going though a major overhaul and some things might be missing. For a copy of the old version see '''[http://wiki.kodi.tv/index.php?title=Linux_FAQ&oldid=76795 here]'''.}} }}

{{Kodi FAQ}}

<section begin="intro" />'''F'''requently '''A'''sked '''Q'''uestions for Kodi running under Linux-based operating systems.<section end="intro" />

__TOC__
{{-}}

== General FAQ ==
:{{big|''See also: '''[[All platforms FAQ]]''' for FAQs that apply to all versions of Kodi.''}}

=== Supported Linux distributions ===
:* Team Kodi provides precompiled binaries for Ubuntu from the '''[[Team Kodi PPA]]'''. In the future there will also be precompiled binaries for Debian and Steam OS.
:* Team Kodi recognizes '''[[LibreELEC]]''' versions of Kodi as "pretty damn awesome".
:* Generally speaking, as long as Kodi is compiled per recommended guidelines (see '''[[HOW-TO:Compile Kodi for Linux]]'''), those builds are considered "kosher".
:* Kodi builds that use external ffmpeg/libav are not supported and are strongly discouraged.

=== Supported hardware ===
For x86 hardware:
{{collapse top}}
:{{#lst:Supported hardware|Linux}}
{{collapse bottom}}

=== How to install or update Kodi for Linux ===
{{Main|HOW-TO:Install Kodi for Linux}}

; Ubuntu:
{{#lst:Team Kodi PPA|repos}}

; For other supported distros, see [[HOW-TO:Install Kodi for Linux]]

=== Kodi for Linux version ===
: The current stable version of Kodi for Linux is {{Current version}}. This is the same code that all of the other platforms (Android, iOS, Mac, Windows, etc) are using.

=== What version/nightly build/beta of Kodi am I running? ===
: Kodi main menu > System > Lower submenu > System info. '''Note the build date.'''

=== Programs and tools to help with Kodi ===
: For a list of programs and tools to help with Kodi, such as renaming files, managing media, file sharing, and more, see '''[[Supplemental tools/Linux]]'''

=== How to autostart Kodi in desktop mode ===

A)

<pre>
sudo sed -i "1i @kodi" /etc/xdg/lxsession/LXDE-pi/autostart
</pre>

or B)

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

Source of this information is [[HOW-TO:HOW-TO:Autostart_Kodi_for_Linux#Configure_Kodi_to_autostart|HOW TO: Autostart Kodi for Linux]]

=== What are the differences between Ubuntu + Kodi and LibreELEC? ===
* '''Ubuntu + Kodi:''' This setup will give you the full Unity desktop environment that has enough software installed to be a general computing solution.
* '''[[LibreELEC]]:''' An appliance distribution. Getting software other than what is provided in the basic distribution will be a little difficult, but not impossible.

== Troubleshooting ==
{{see also|Troubleshooting}}

=== Getting more help with Kodi for Linux ===
:* '''[http://forum.kodi.tv/forumdisplay.php?fid=52 Kodi for Linux specific help forum]'''
:* '''[irc://irc.freenode.org/Kodi #Kodi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org.

=== Userdata folder and logs ===
:{{Main|Userdata folder|Debug log}}
:{{editor note|this needs filling out}}

=== Audio issues ===
:For most audio issues, including configuration examples, see '''[[Audio]]''' and '''[[Audio troubleshooting]]'''.

=== Video tearing on Nvidia GPUs ===
: When Kodi is used with Nvidia hardware, tearing will occur when the X composite extension is used.

:* '''Solution 1:''' Enable "Unredirect Fullscreen Window" in Compiz Config Settings Manager. [http://ubuntuforums.org/showthread.php?p=11145045#post11145045]
:*# Install CCSM (Compiz Config Settings Manager): <code>sudo apt-get install compizconfig-settings-manager</code>
:*# Open Compiz Config Settings Manager
:*# Check the option "Unredirect Fullscreen Window", which should be under the "Composite" section.

:* '''Solution 2:''' Disable the composite extension.
:::'''1.''' Add this to the end of /etc/X11/xorg.conf: (make a new file if xorg.conf doesn't exist)
<pre>Section "Extensions"
Option "Composite" "Disable"
EndSection</pre>
:::'''2.''' Then log in with a gnome classic session (without the composite extension compiz doesn't work).
:::'''3.''' Also make sure to set Vertical blank sync to Always enabled in Kodi.

:* '''Solution 3:''' Disable the use of the SDL backing store - this is a bug in Ubuntu which will probably be fixed in due time but could cause tearing right now: http://askubuntu.com/questions/450593/how-do-i-eliminate-screen-tearing-on-14-04-and-xbmc-with-nvidia-331/450673#450673

=== Why can't I update Kodi on Ubuntu 13.04, 13.10, or other release? ===
: The precompiled binaries from the Team Kodi PPA only work with Ubuntu releases that are still getting support. When Ubuntu drops support for a version then our PPA stops making a binary for it. Simply update Ubuntu itself and then Kodi updates should work again. If you don't want to update Ubuntu that often then we recommend using a long term support (LTS) version of Ubuntu, such as 14.04, which will be supported until 2019.

{{Helix updated}}

[[Category:Manual]]
[[Category:FAQ]]
[[Category:Linux|*]]
[[Category:Troubleshooting]]

HOW-TO:Autostart Kodi for Linux

2020-01-28T09:06:52Z

Postcd: /* Configure Kodi to autostart - new option to achieve it. Tested on Raspbian 10. */

<section begin="intro" /><big>Any or all or a combination of these methods can be used to configure a Debian-based X Window System to boot directly to Kodi. This should work on any Linux using the X Window System, but these instructions are particular to Debian derivatives, such as Ubuntu. A server edition is best for running only Kodi, but this page assumes booting into a desktop OS, not a server distro. However, the instructions here can be used for a server distro with even less configuration than for a desktop. Experiment inside VirtualBox before you apply any of these to your system and make a backup.</big><section end="intro" />

__TOC__

== Installing the X11 Window System ==

Even if you are using something like [https://github.com/graysky2/kodi-standalone-service Kodi Standalone Service], you still need use a WM or a DE that installs the '''x-window-manager''' software package.

To ensure you have this installed use the '''which''' command.

<pre>
which x-window-manager
</pre>

If there is no such package, you can use '''apt''' to search your Linux distributions repository.

<pre>
apt-cache search x-window-manager
</pre>

This will generate a list of packages containing '''x-window-manager''', which cannot be installed alone. If you are not using a DE, you need to use a WM. And, you can also use a compositing WM like Compiz, for fast 3D effects.

[https://wiki.archlinux.org/index.php/Compiz Compiz - ArchWiki]

A note on using Kodi Standalone Service, this package runs Kodi as a '''systemd''' service and disables the login for user '''kodi''' and will not work when autologin is enabled. In fact, it will break the login process if you autologin user '''kodi''' and run Kodi Standalone Service at the same time. This package is installed automatically with the standard Kodi package when you install Kodi on Raspbian, but must be configured manually for all other Linux distributions. You can run the '''which''' command to find this package as well.

<pre>
which kodi-standalone
</pre>

Be advised, Kodi Standalone Service still launches the Kodi GUI and still requires a WM even though it is running as a '''systemd''' service. When you install a WM such as '''xfwm4''' (the WM for XFCE4), the CLI will tell you if it provides the '''x-window-manager''' package.

<pre>
Setting up xfwm4 (4.12.4-1) ...
update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
</pre>

If you do not see this message at the end of the installation, the WM you selected does not provide this software package and may not actually be a complete WM itself but only part of a package containing a WM.

For a great example on exactly how you would do this with '''xfwm4''', see this ArchWiki entry.

[https://wiki.archlinux.org/index.php/Xfwm XFWM - ArchWiki]

Most systems utilize the client version of the X11 software an Xsession requires.

For more X11 features and functionality, you may optionally upgrade to the server software packages for the X Window System.

<pre>apt install xauth xorg xinit xserver-xorg-core xserver-xorg xserver-common</pre>

The Ubuntu wiki is usually a good source of information.

[https://wiki.ubuntu.com/CustomXSession CustomXSession - Ubuntu Wiki]

Custom user sessions can be created with the X11 Window System to run scripts, autostart apps, and launch a WM or DE.

LightDM is used for autologin.

== Customize LightDM to autologin ==

You can utilize the ability to customize LightDM data manager by changing the builtin custom configuration file '''50-myconfig.conf''' using '''nano''' or another text editor. If you have no DE or WM you can install '''lightdm''', but should make sure to do a bit of research before you do. Most versions of Linux use LightDM, but many server versions do not. For Ubuntu Server with no DE, for example, installing '''lightdm''' is okay and necessary. Changing the behavior of LightDM is done using a custom '''50-myconfig.conf''' configuration file.

To see if you have '''lightdm''' use '''which'''.

<pre>
which lightdm
</pre>

If not, install it with '''apt'''.

<pre>
apt install lightdm
</pre>

Configure LightDM for autologin to boot directly to Kodi.

<pre>
nano /etc/lightdm/lightdm.conf
</pre>

Uncomment the following line.

<pre>
#autologin-user=
</pre>

And add the user you want to autologin. The user is named '''kodi''' in this example.

<pre>
autologin-user=kodi
</pre>

And then you can create /etc/lightdm/lightdm.conf.d/50-myconfig.conf, but ensure the settings in /etc/lightdm/lightdm.conf agree.

Create a custom configuration file called '''50-myconfig.conf''' using '''nano''' or other CLI text editor.

<pre>
mkdir /etc/lightdm/lightdm.conf.d/
nano /etc/lightdm/lightdm.conf.d/50-myconfig.conf
</pre>

Inside this new file add the following text.

<pre>
[SeatDefaults]
autologin-user=kodi
</pre>

CTRL +O +Enter +X to save and exit from '''nano'''.

== Configure Kodi to autostart ==

Configure Kodi to autostart.

A)

<pre>
sudo sed -i "1i @kodi" /etc/xdg/lxsession/LXDE-pi/autostart
</pre>

B)

<pre>
mkdir -p ~/.config/autostart
ln -s /usr/bin/kodi ~/.config/autostart
</pre>

This method of autostart requires a desktop environment or DE. This is done a bit differently by each DE. Some helpful links can easily be found in today's Web search using any search engine.

[http://edoceo.com/gui/xfce-autostart-apps Autostart Apps in XFCE]

And this link shows how to autostart an app in LXDE on Raspbian.

[http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/auto-running-programs-gui Auto running programs LXDE - Raspberry Pi Projects]

The Raspberry Pi is a bit more of a tweak, but these are excellent links that will tell you how. The first link is the most helpful to making sure Kodi autostarts in Pi, and utilizes a '''crontab'''. There are many settings on the Pi that control boot, and the first link gives the best most trouble-free way to boot directly to Kodi.

[https://www.leowkahman.com/2016/03/05/lamp-stack-on-raspberry-pi-with-kodi-running-at-startup/ LAMP stack on Raspberry Pi with Kodi running at startup]

In the above link, the author describes using Crontab (short for "Cron table") to boot directly to Kodi.

<pre>
apt install cron
crontab -e
</pre>

Cron will ask you to choose a text editor from available options. I choose option 2 for '''nano'''.

In the new Crontab, enter the following text.

<pre>
@reboot kodi --standalone
</pre>

You could also consider using Crontab to run a script, much like described on this page in the section entitled "Run kodi in a window manager" if you scroll down the page.

[https://wiki.archlinux.org/index.php/Kodi Kodi - Run kodi in a window manager]

Instead your Crontab could look like this.

<pre>
@reboot startx
</pre>

And create an '''~/.xinitrc''' file.

<pre>
nano ~/.xinitrc
</pre>

The '''~/.xinitrc''' file should look like this.

<pre>
#!/bin/bash
kodi --standalone #(this is proper syntax for most Kodi installs)
#kodi-standalone #(this is the syntax that works on Raspbian, not other Pi operating systems)
sudo chvt 2
sleep 1
sudo chvt 1
</pre>

Raspbian has a repository package for everything, so kodi-standalone can be run as a package rather than a command argument.

Make sure to make '''~/.xinitrc''' executable by running.

<pre>
chmod +x ~/.xinitrc
</pre>

To ensure no password is required by '''sudo''' for any user logging in when this script runs, you must edit /etc/sudoers or run the '''visudo''' command if it is installed to edit /etc/sudoers.

You can install '''visudo''' from your Linux distributions default repository.

<pre>
apt install sudo
</pre>

To use '''visudo''' simply run the command in the terminal.

<pre>
visudo
</pre>

For any non-root users, create an entry in /etc/sudoers with '''nano'''.

<pre>
nano /etc/sudoers
</pre>

Create an entry on any line that is comfortable to you like shown here.

<pre>
kodi ALL=NOPASSWD: /usr/bin/chvt
# pi ALL=NOPASSWD: /usr/bin/chvt #(if you do not add user kodi)
</pre>

The above example is for users '''pi''' and '''kodi'''.

If you decide not use a Cron table, you can always remove it again.

<pre>
crontab -r
</pre>

This is a quick reference for Crontab.

[http://www.adminschoice.com/crontab-quick-reference Crontab Quick Reference]

These linked pages facilitate more tweaks and settings relevant to other uses of the X Window System on Pi.

[http://ozzmaker.com/enable-x-windows-on-piscreen/ Enable X Window System on PiScreen]

Other things to tweak on Raspbian.

[https://yingtongli.me/blog/2016/12/21/splash.html Raspbian splash screen guide - Clean up the boot process]

[https://scribles.net/lightning-bolt-under-voltage-warning-on-raspberry-pi/ Under voltage warning and disabling splash screen on Raspbian]

[https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie Remove boot messages all text in Raspbian - Raspberry Pi Stack Exchange]

And, if you would rather, it is easier to follow the process provided by this link to modify the Raspbian image before installing it onto the microSD card.

[https://wiki.debian.org/RaspberryPi/qemu-user-static Modifying Raspbian with qemu-user-static]

The above link describes removing the DE from a Raspbian image, though Raspbian Lite is a much better starting point for using Qemu for this purpose.

You can also use the X11 Window System to autostart Kodi by placing a startup script in the /etc/X11/Xsession.d/ directory.

[https://debian-administration.org/article/50/Running_applications_automatically_when_X_starts Running applications automatically when X starts]

<pre>
nano /etc/X11/Xsession.d/startup-local
</pre>

Insert this text into the new file. Use CTRL + O + Enter + X to save the file.

<pre>
#!/bin/sh
/usr/bin/kodi
</pre>

If you have a WM, such as Blackbox you can add it here as well.

<pre>
#!/bin/sh
blackbox &
/usr/bin/kodi
</pre>

Set permissions to make it executable. Use the ampersand to run each command in the background till the last line or your script will get stuck on the first line.

<pre>
chmod 755 /etc/X11/Xsession.d/startup-local
</pre>

If Kodi is not installed at the standard path, find it using the '''which''' command.

<pre>
which kodi
</pre>

This feature is available on X Window System operating systems most Linux distributions use the X Window System.

== Create custom Xsession script ==

To create a custom Xsession script with a text editor we start with an '''xinitrc''' script. For more detail on how to create and use '''xinit''', there is a great guide available here.

[https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions Guide to X11 - Starting Sessions - WikiBooks]

<pre>
nano ~/.xinitrc
</pre>

To run Kodi full-screen make sure the text reads:

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Replace the '''gnome-session''' with the DE or WM command you are using. See the last section for examples.

To make '''~/.xinitrc''' executable use.

<pre>
chmod +x ~/.xinitrc
</pre>

Use '''sudo''' and the '''~/.xinitrc''' file to configure '''~/.xsession'''.

<pre>
sudo -H -u kodi bash -c "ln -s ~/.xinitrc /home/kodi/.xsession"
</pre>

Make sure the path goes to user's home directory. In this example, the user is '''kodi'''.

You need to use '''sudo''' to run this command. If you do not have '''sudo''', install it.

<pre>
apt install sudo
</pre>

If you create a symbolic link and want to remove it, simply remove the existing '''.xsession''' file you created.

<pre>
rm /home/kodi/.xsession
</pre>

On some systems using a DE such as Gnome, not all systems using Gnome, it may be necessary for '''.xsession''' to be '''.xsessionrc'''. Though this is more likely the case for organization network computers than a personal one, where configurations may vary on a diversity of machines. Most of the time, it will be '''.xsession''' rather than '''.xsessionrc''' that you want to create.

You can also create the '''.xsession''' script directly in the home directory, rather than link it from '''~/.xinitrc'''. This is necessary if you create multiple custom Xsession scripts for multiple users, and you do not in that case link '''~/.xinitrc''' to '''.xsession'''.

To enable multiple displays edit the '''.bashrc''' file.

<pre>
nano ~/.bashrc
</pre>

Add the following text.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 3 ]]; then
exec startx
fi
</pre>

For two monitors add the following as shown.

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -le 2 ]]; then
exec startx
fi
</pre>

For a single monitor use:

<pre>
if [[ ! $DISPLAY && $XDG_VTNR -eq 1 ]]; then
exec startx
fi
</pre>

If you wish to remain logged in after quitting X, remove the '''exec''' from the above. Other configurations can be applied, but are irrelevant to autostarting Kodi.

[https://wiki.archlinux.org/index.php/Xinit#Autostart_X_at_login Xinit Autostart X at login]

If you are using LightDM and you just want to create a new login entry for user '''kodi''', you must create a new file.

<pre>
nano /usr/share/xsessions/custom.desktop
</pre>

And insert the following text.

<pre>
[Desktop Entry]
Name=Xsession
Exec=/etc/X11/Xsession
</pre>

This will create a new login option for the custom Xsession. Only this one entry is necessary for LightDM and X11 to find the '''~/.xsession''' script in each user's home directory.

You can use any window manager or desktop enviroment with a custom Xsession script as long as it is installed.

You do this by creating '''~/.xinitrc''' script that contains the command to start the WM or DE.

For instance, if you are using FluxBox.

<pre>
#!/usr/bin/env bash
exec fluxbox &
/usr/bin/kodi -fs
</pre>

The <code>-fs</code> option is full-screen.

To run Gnome in the background, but launch Kodi in the foreground.

<pre>
#!/usr/bin/env bash
exec gnome-session &
/usr/bin/kodi -fs
</pre>

Use the '''~/.xinitrc''' file to configure '''~/.xsession''' to create a custom login for any user, not just Kodi.

<pre>
sudo -H -u [username] bash -c "ln -s ~/.xinitrc ~/.xsession"
</pre>

You must reconfigure Xserver for any user that is not a privileged user to be able to start a custom Xsession.

<pre>
dpkg-reconfigure xserver-xorg-legacy
dpkg-reconfigure xserver-xorg
</pre>

When you reconfigure X11 with these commands, choose to allow non-root users (anybody) to start an Xsession. You should see your changes take effect after rebooting.