Archive:Raspberry Pi FAQ: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
>Niels
No edit summary
(Remove OpenELEC)
(41 intermediate revisions by 12 users not shown)
Line 1: Line 1:
{{Frodo updated}}{{FAQ header|XBMC running on the '''[[Raspberry Pi]]'''.}}
{{XBMC FAQ}}
{{XBMC FAQ}}
{{mininav|[[Raspberry Pi]] }}
'''F'''requently '''A'''sked '''Q'''uestions Kodi running on the '''[[Raspberry Pi]]'''.
__TOC__
__TOC__
{{-}}
{{-}}


==General FAQ==
== General FAQ ==
:<big>''See also: '''[[XBMC all platforms FAQ]]''' for FAQs that apply to all versions of XBMC.''</big>
:<big>''See also: '''[[XBMC all platforms FAQ]]''' for FAQs that apply to all versions of Kodi.''</big>
{| width="100%"
{| width="100%"
<!--{{FAQ|1=doesitblend
<!--{{FAQ|1=doesitblend
Line 16: Line 18:
{{FAQ|1=Install
{{FAQ|1=Install
| BGcolor= WhiteSmoke
| BGcolor= WhiteSmoke
| Question= Installing XBMC on the Raspberry Pi
| Question= Installing Kodi (for Linux) on the Raspberry Pi
| Answer=
| Answer=
{{#lst:Raspberry Pi|install}}
{{main|HOW-TO:Install Kodi on Raspberry Pi}}
{{#lst:HOW-TO:Install Kodi on Raspberry Pi|install}}
}}
}}
{{FAQ|1=Version
| BGcolor= WhiteSmoke
| Question= Can I run Kodi for Android on Raspberry Pi?
| Answer=
* The short answer is no. There are currently no full featured versions of the [[Android|Android operating-system]] that work on Raspberry Pi (first-generation) or Raspberry Pi 2. If and when the [[w:Raspberry Pi Foundation|Raspberry Pi Foundation]] releases a full featured version of Android for Raspberry Pi, (which, if it occurred, would most likely be only for the newer Raspberry Pi 2), then in theory Kodi for Android should just work on it. This will however depend on what is meant by "''full featured''" in fulfilling all the Android API requirements that Kodi needs to fully function properly.
}}
{{FAQ|1=Version
| BGcolor= WhiteSmoke
| Question= Can I run Kodi for Windows on Raspberry Pi?
| Answer=
* No. There are no full featured versions of the [[Windows|Windows operating-system]] that work on Raspberry Pi (first-generation) or Raspberry Pi 2, and there probably never will be. Microsoft have a released an IoT (Internet of Things) version of Windows 10 for Raspberry Pi 2, and by definition that IoT version is not a full featured versions of Windows which is what Kodi for Windows would need to run on the Raspberry Pi.}}


{{FAQ|1=Version
{{FAQ|1=Version
| BGcolor=  
| BGcolor=  
| Question= Is XBMC for Raspberry Pi different from normal XBMC?
| Question= Is Kodi for Raspberry Pi different from normal Kodi?
| Answer=
| Answer=
*The current stable version of XBMC for Raspberry Pi is v12.1 [[Frodo FAQ|Frodo]]. This is the same code that all of the other platforms (Linux, iOS, Mac OS X, Windows, etc) are using.
* The current stable version of Kodi for Raspberry Pi is {{current version}}. This is the same code that all of the other platforms (Linux, iOS, Mac OS X, Windows, etc) are using.
* There are two acceleration options on the Pi. "omxplayer" runs much of the player logic on the gpu which is highest performance option and can handle raw Blu-Ray quality videos. It does not support DVD menus or ALSA audio.
* "MMAL" acceleration uses dvdplayer with hardware acceleration of the video codec. Performance is a little lower than omxplayer, but should still handle most 1080p content.
* By default both are enabled, and omxplayer acceleration will be disabled when not appropriate (i.e. DVDs with menus or when ALSA audio is enabled).
* If you don't play raw Blu-Ray quality videos then disabling omxplayer acceleration is an option which some users may prefer.  
}}
}}


{{FAQ|1=Current_build
{{FAQ|1=Current_build
| BGcolor= WhiteSmoke
| BGcolor= WhiteSmoke
| Question= How do I find out what version of XBMC am I running?
| Question= How do I find out what version of Kodi am I running?
| Answer=
| Answer=
* XBMC main menu > System > Lower submenu > System info. '''Note the alpha version and/or build date.'''
* Kodi main menu > Settings > System information > Summary '''Note the build date.'''  
* '''See also: ''' [[Settings/System_information#Summary|Settins > System information > Summary]]
}}
}}


Line 40: Line 61:
| Answer=
| Answer=
* H.264 (up to High Profile) encoded videos are supported up to 1080P using hardware video decoding. ''Note: [[Hi10P]] will not work.''
* H.264 (up to High Profile) encoded videos are supported up to 1080P using hardware video decoding. ''Note: [[Hi10P]] will not work.''
* For proper HD playback you will need hardware decoding. The Raspberry Pi Foundation offers additional video codec licenses for a few dollars. At the moment you can purchase MPEG2 and VC1, both with support up to 1080P. Others may be available in the future. Read [[#Enabling_additional_video_codecs|below]] on how to enable these.
* MPEG-4 encoded videos are supported up to 1080P using hardware video decoding. This includes XviD and recent versions on DivX (but not the older 3.xx DivX).
* Some SD content can be played back with software decoding.
* The Raspberry Pi Foundation offers additional video codec licenses for a few dollars. At the moment you can purchase MPEG-2 and VC1, both with support up to 1080P. Read [[#Enabling_additional_video_codecs|below]] on how to enable these.
* DVD ISOs and DVD menu navigation is early in development and might not always work.  
* MJPEG, VP6, VP8 and OGG Theora are supported as GPU accelerated software decoders. These are limited to DVD resolutions.
* XBMC on the Raspberry Pi will struggle with DTS audio tracks since it relies heavily on CPU power. The Foundation is reportedly [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=15546 working on] a hardware decoding license, meanwhile use [[Settings/System#Audio_output|passthrough (with a compatible TV and/or receiver) when possible]].
* Codecs without gpu support like DivX 3, msmpeg and sorenson spark will be decoded by dvdplayer on the ARM. Should work for SD resolutions.
* DVD ISOs with menus should work fine (using dvdplayer).
* Software DTS audio decode works well in recent builds. TrueHD audio is CPU intensive and may require overclocking.
}}
}}


Line 50: Line 73:
| Question= Video and audio output on the Raspberry Pi
| Question= Video and audio output on the Raspberry Pi
| Answer=
| Answer=
* Video output via HDMI up to 1080P (the GUI will be rendered at 720P, but video will play up to 1080P).
* Video output via HDMI up to 1080P. The GUI is 1080p by default, but can be reduced in video settings without affecting video resolution.
* Video output via the analog component video (RCA) jack will be in SD.
* Video output via the analog component video (RCA) jack will be in SD.
* Analog audio output via the mini phone jack is supported.
* Analog audio output via the mini phone jack is supported.
* USB audio is currently not supported.
* I2S and USB ALSA audio cards are supported with {{current version}} builds. omxplayer acceleration is not available (it will be disabled automatically).  
* DTS and AC3 audio passthrough audio is supported (and recommended, as it will reduce CPU load on the R-Pi)
* DTS and AC3 audio passthrough audio is supported (and recommended, as it will reduce CPU load on the R-Pi)
}}
{{FAQ|1=Multichannel_Audio
| BGcolor= WhiteSmoke
| Question= How about multichannel audio support?
| Answer=
* By default audio is downmixed to stereo.
* If your receiver/TV supports DTS or AC3 passthrough then enable these in audio settings and you will get 6 channel audio.
* Multichannel PCM audio is supported over HDMI. Note: not all receivers support this and toslink/optical will not.
* Enable by setting the speaker configuration to suitable value (e.g. 5.1 or 7.1).
* If your recevier does not support multichannel PCM, then leave this at 2.0. You can still get multichannel audio through passthrough.
}}
}}


Line 68: Line 102:
In order to enable additional video codecs you should modify ''/boot/config.txt'' and add these lines literally. The method may vary per distribution:
In order to enable additional video codecs you should modify ''/boot/config.txt'' and add these lines literally. The method may vary per distribution:


*Manual: Open ''/boot/config.txt'' with a text editor like nano or vi, and add the keys.
* Manual: Open ''/boot/config.txt'' with a text editor like nano or vi, and add the keys.
*[[XBian]]: You can add/remote your keys using [http://xbian.org/getting-started/configuring-xbian/ XBian-config]. After reboot your keys will be entered and ready to use.
* [[XBian]]: You can add/remote your keys using [http://xbian.org/getting-started/configuring-xbian/ XBian-config]. After reboot your keys will be entered and ready to use.
*[[Raspbmc]]: Navigate to {{highlight|Programs -> Raspbmc Settings -> System Configuration -> MPEG2 codec license/VC1 codec key}}. Enter your keys with the onscreen keyboard then XBMC will prompt you to reboot. After reboot your keys will be entered and ready to use.
* [[OSMC]]: Go in to My OSMC -> Pi Config. Navigate to Codecs and enter your keys with the on-screen keyboard. After a reboot your keys will be entered and ready to use.
* [[OpenELEC]]: Type <code>mount /flash -o remount,rw</code> to remount the boot partition in read/write mode. The file to edit is located in ''/flash/config.txt'', and contains stubs for the license keys. Add the keys using nano or vi.
}}
}}


Line 87: Line 120:
| Question= Add-ons and skins
| Question= Add-ons and skins
| Answer=
| Answer=
*XBMC for Raspberry Pi is a full version of XBMC and will be able to use all non-platform specific [[add-ons]] and [[skins]]. More feature rich (CPU demanding) skins like AEON Nox might not run smoothly, so keep to "lighter" skins.
* Kodi for Raspberry Pi is a full version of Kodi and will be able to use all non-platform specific [[add-ons]] and [[skins]]. More feature rich (CPU demanding) skins might not run smoothly, so keep to "lighter" skins.
*Recommended lite skins include: Confluence (default skin), Metropolis, Quartz, Quartz Reloaded, Slik, xTV-SAF.
* Recommended lite skins include: Estuary (default skin), Confluence, Amber, Metropolis, Quartz, xTV-SAF. Aeon Nox 5 is quite usable.
}}
}}


Line 96: Line 129:
| Answer=
| Answer=
* It is not possible to use traditional "shutdown" on the Raspberry Pi. The only way to power it off is to disconnect the power.  
* It is not possible to use traditional "shutdown" on the Raspberry Pi. The only way to power it off is to disconnect the power.  
* ALWAYS select the shutdown command in XBMC before powering off the Raspberry Pi. Failure to do so can corrupt the XBMC library databases, other databases, or even other OS files.
* ALWAYS select the shutdown command in Kodi before powering off the Raspberry Pi. Failure to do so can corrupt the Kodi library databases, other databases, or even other OS files.
* Most users leave the Raspberry Pi on all the time, as it uses very little power (the cost of electricity for a year is about the price of a hamburger).
* Most users leave the Raspberry Pi on all the time, as it uses very little power (the cost of electricity for a year is about the price of a hamburger).
}}
}}
Line 104: Line 137:
| Question= Remotes for Raspberry Pi
| Question= Remotes for Raspberry Pi
| Answer=
| Answer=
* Any '''[[Keyboard]]''' such as wired, wireless, bluetooth. This includes "keymotes" such as a Rii or [[Boxee remote]].
{{see|Raspberry Pi#Remote controls}}
* '''[[Web interface]]s''', including add-on interfaces.
* XBMC '''[[:Category:Smartphone and tablet remotes|smartphone and tablet remote apps]]'''.
* Other IR remotes can be used with USB IR receivers such as the '''[[Flirc]]'''.
* '''[[CEC]]''' - Includes Informations about the next standart Protocol to control the Raspberry and your TV.
* '''GPIO IR receiver''' - A simple bare IR receiver can be connected to the R-Pi's GPIO pins using [http://forum.stmlabs.com/showthread.php?tid=5549 these instructions].
}}
}}


Line 116: Line 144:
| Question= MySQL library sharing
| Question= MySQL library sharing
| Answer=
| Answer=
* If you are using [[MySQL]] library sharing features, please note that your library will only sync with the Raspberry Pi if all your other XBMC instances are running the same version ([[#Current_build|how to check your version]]).
* If you are using [[MySQL]] library sharing features, please note that your library will only sync with the Raspberry Pi if all your other Kodi instances are running the same version ([[#Current_build|how to check your version]]).
}}
}}
|}
|}


==Troubleshooting==
== Troubleshooting ==
{{see also|Troubleshooting}}
{{see also|Troubleshooting}}
{| width="100%"
{| width="100%"
Line 126: Line 154:
{{FAQ|1=Forum|2=IRC
{{FAQ|1=Forum|2=IRC
| BGcolor=
| BGcolor=
| Question= Getting more help with XBMC for Raspberry Pi
| Question= Getting more help with Kodi for Raspberry Pi
| Answer=
| Answer=
* '''[http://forum.xbmc.org/forumdisplay.php?fid=166 XBMC for Raspberry Pi specific help forum]'''
* '''[http://forum.kodi.tv/forumdisplay.php?fid=166 Kodi for Raspberry Pi specific help forum]'''
* '''[http://webchat.freenode.net/?channels=libreelec #libreelec]''' [[w:IRC|IRC]] channel on Freenode (Webchat)
* '''[irc://irc.freenode.org/xbmc-rpi #xbmc-rpi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org.
* '''[irc://irc.freenode.org/xbmc-rpi #xbmc-rpi]''' [[w:IRC|IRC]] chat channel on irc.freenode.org.
* '''[http://webchat.freenode.net/?channels=xbmc-rpi #xbmc-rpi]''' [[w:IRC|IRC]] channel on Freenode (Webchat)
* '''[http://webchat.freenode.net/?channels=xbmc-rpi #xbmc-rpi]''' [[w:IRC|IRC]] channel on Freenode (Webchat)
* '''[http://webchat.freenode.net/?channels=openelec #openelec]''' OpenELEC [[w:IRC|IRC]] support on Freenode (Webchat)
* '''[http://webchat.freenode.net/?channels=xbian #xbian]''' XBian [[w:IRC|IRC]] support on Freenode (Webchat)
* '''[http://webchat.freenode.net/?channels=xbian #xbian]''' XBian [[w:IRC|IRC]] support on Freenode (Webchat)
* '''[http://webchat.freenode.net/?channels=raspbmc #raspbmc]''' Raspbmc [[w:IRC|IRC]] support on Freenode (Webchat)
* '''[http://webchat.freenode.net/?channels=osmc #osmc]''' OSMC [[w:IRC|IRC]] support on Freenode (Webchat)
* Also see the individual XBMC/OS distribution documentation and support forums noted '''[[Raspberry Pi/FAQ#Install|above]]'''.
* Also see the individual Kodi/OS distribution documentation and support forums noted '''[[Raspberry Pi/FAQ#Install|above]]'''.
* For general Raspberry Pi info and help be sure to see http://raspberrypi.org and the very excellent '''[http://elinux.org/R-Pi_Hub Raspberry Pi Wiki]'''
* For general Raspberry Pi info and help be sure to see http://raspberrypi.org and the very excellent '''[http://elinux.org/R-Pi_Hub Raspberry Pi Wiki]'''
}}
}}
Line 143: Line 171:
| Answer=
| Answer=
:''See '''[[How-to:Submit a proper bug report]]''' for bug reporting details and  '''[[Debug log]]''' for how to post the debug log.''
:''See '''[[How-to:Submit a proper bug report]]''' for bug reporting details and  '''[[Debug log]]''' for how to post the debug log.''
*[[Userdata folder]]:
* [[Userdata folder]]:
**OpenELEC: {{highlight|/storage/.xbmc/userdata/}}
** LibreELEC: {{highlight|/storage/.kodi/userdata/}}
**Raspbmc: {{highlight|/home/pi/.xbmc/userdata/}}
** OpenELEC: {{highlight|/storage/.kodi/userdata/}}
**XBian: {{highlight|/home/xbian/.xbmc/userdata/}}
** OSMC: {{highlight|/home/osmc/.kodi/userdata/}}
*[[Debug log]]:  
** XBian: {{highlight|/home/xbian/.kodi/userdata/}}
**OpenELEC: {{highlight|/storage/.xbmc/temp/xbmc.log}}
* [[Debug log]]:  
**Raspbmc: {{highlight|/home/pi/.xbmc/temp/xbmc.log}}
** LibreELEC: {{highlight|/storage/.kodi/temp/kodi.log}}
**XBian: {{highlight|/home/xbian/.xbmc/temp/xbmc.log}}
** OpenELEC: {{highlight|/storage/.kodi/temp/kodi.log}}
** OSMC: {{highlight|/home/osmc/.kodi/temp/kodi.log}}. On OSMC, a Debug log can be uploaded via My OSMC -> Log Uploader.
** XBian: {{highlight|/home/xbian/.kodi/temp/kodi.log}}
}}
}}


{{FAQ|1=Language
{{FAQ|1=Language
| BGcolor=
| BGcolor=
| Question= Wrong language displayed in XBMC
| Question= Wrong language displayed in Kodi
| Answer=
| Answer=
* If you're getting a different language displayed in XBMC than the one you've set in {{highlight|bordered=yes|[[Settings/Appearance#International|Settings -> Appearance -> International]]}}, it could be caused by your TV's language settings over [[CEC]].  
* If you're getting a different language displayed in Kodi than the one you've set in {{highlight|bordered=yes|[[Settings/Appearance#International|Settings -> Appearance -> International]]}}, it could be caused by your TV's language settings over [[CEC]].  
* Go into {{highlight|bordered=yes|[[Settings/System#Input devices|Settings -> System -> Input devices -> Peripherals -> RasPi CEC module -> Use TV's language]]}} and set to off.
* Go into {{highlight|bordered=yes|[[Settings/System#Input devices|Settings -> System -> Input devices -> Peripherals -> RasPi CEC module -> Use TV's language]]}} and set to off.
}}
}}
Line 172: Line 202:
| Question= Performance: video buffering, stuttering, choppiness  
| Question= Performance: video buffering, stuttering, choppiness  
| Answer=
| Answer=
* Switch to a different network protocol (especially if you are using SMB), i.e. [[NFS]], [[FTP]], [[WebDAV]], etc.
{{main|Raspberry Pi#Maximizing performance}}
* Try sharing the media on another device to rule out a device-specific (or network) issue. Note: The Raspberry Pi can sometimes have a problem supplying enough power to a USB WiFi dongle. Try a wired ethernet cable to rule out this problem.
{{#lst:Raspberry Pi|performance}}
* Turn off thumbnails, {{highlight|XBMC > Settings > Video > File}} and deselect 'generate thumbnails'.
}}
* Make sure the video is using the h.264 codec (up to High Profile. Hi10P will not work), or, if a codec was purchased and enabled, MPEG-2 or VC-1.
 
* Movies with DTS audio tracks will stutter since the Raspberry Pi lacks CPU power to properly decode this. Use [[Settings/System#Audio_output|audio passthrough]] if your TV/receiver supports, or consider reconverting the audio track (or add a converted secondary track to preserve the original DTS track). Note: Raspberry Pi developers have written code to process DTS streams in hardware however they are waiting on a response from DTS regarding licensing. See [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=15546 this Raspberry Pi forum entry].
{{FAQ|1=Memory Usage
* If your TV/receiver supports it, AC3 can also use [[Settings/System#Audio_output|audio passthrough]] to reduce the work on the CPU. To determine which audio codecs your HDMI-connected TV supports, you can log in to your chosen distribution, via SSH, and run this command: <code>/opt/vc/bin/tvservice -a</code> (on OpenELEC: <code>tvservice -a</code>).
| BGcolor= WhiteSmoke
* If RSS feed is enabled, disable it in settings. This makes the main menu a bit faster.  
| Question= Memory usage (especially with 256M Pi)
| Answer=
* gpu_mem should be set to 128M on a Pi1, 256M on a Pi2. On a 256M Pi1 it is recommended to set it to 112M. On a 512M Pi1 it may be worth increasing this if you are running heavy skins or if you want to increase the default fanart resolution or colour depth. 256M should be more than enough on a Pi1, although 320M on a Pi2 may be appropriate if using higher resolution imageres/fanartres and also higher colour.
* A 256M Pi is quite short on memory. Be careful with running other apps in the background (e.g. torrents) or installing add-ons that consume memory.
* The default cachemembuffersize will be 2M for a 256M Pi, and 20M for a 512M Pi1/Pi2. You can use 0 to cache to sdcard.
* Reducing the "GUI resolution limit" (e.g. to 720p) in settings/system/video will save memory. This is a default on a 256M Pi. Video will still play at full resolution (e.g. 1080p).
* Enabling "higher colour depth artwork" will use more memory. It should be disabled on 256M Pi.
* Reducing imageres/fanartres will reduce memory usage.
}}
 
{{FAQ|1=TV is not detected unless powered on first
| BGcolor=
| Question=TV is not detected unless powered on first
| Answer=
* Some TVs/receivers only report their capabilities (EDID) through HDMI when powered on before the Pi.
* If TV doesn't get the right resolution or CEC doesn't work when Pi is powered before the TV/receiver then you can:
* Run: <code>sudo tvservice -d edid.dat</code> (after booting with TV/receiver powered on first)
* copy the edid.dat to the FAT partition (/boot on raspbmc and /flash on openelec)
* and add to config.txt: <code>hdmi_edid_file=1</code> and <code>hdmi_force_hotplug=1</code>
* Note: if you change TV/receiver or use a different HDMI input you should capture a new edid.dat file
* You can use '''[https://github.com/neatsoft/rpi-edid-lock Raspberry Pi EDID locker]''' to run all these commands at once.
}}
 
{{FAQ|1=Videos don't play from archives
| BGcolor= WhiteSmoke
| Question=Videos don't play from archives
| Answer=
* When browsing, any archives need to be extracted to identify the content. This can be very slow and even cause out-of-memory crashes with large archive files.
* On the Pi this is now optional (enabled by default), enable or disable with: {{highlight|bordered=yes|[[Settings/Appearance#File lists|Settings -> Appearance -> File lists -> Support browsing into archives]]}}
* If your library does contain rar files, beware of disabling - you may need to rescan library after enabling again. Also note that subitles in rar won't work when disabled.  
* Note: using rar files doesn't save any space as video files are already highly compressed, so just extracting them would be the preferred solution.
}}
 
{{FAQ|1=Coloured square appears on screen
| BGcolor=
| Question=Coloured square appears on screen
| Answer=
* A coloured square may appear in the top right corner of screen to warn you of problems that should be remedied.* More info [http://www.raspberrypi.org/forums/viewtopic.php?f=29&t=82373 here].
* A multicoloured square means the voltage is too low. You should try a better power supply or cable between power supply and Pi (Note: under-voltage detection is only supported on B+ and Pi 2)
* A red square means temperature is high (85'C) and overclock has been disabled. This is pretty rare, but can occur in a hot environment, with a case with no ventilation and with the Pi on hot equipment.
}}
 
{{FAQ|1=Audio or video dropouts on HDMI
| BGcolor= WhiteSmoke
| Question=Audio or video dropouts on HDMI
| Answer=
* If the dropouts only occur when playing video with "adjust display refresh rate to match video" enabled, then try adding hdmi_clock_change_limit=20 to config.txt
* If the dropouts occur when cpu is busy (e.g. scrolling through library) then an insufficient power supply is most likely.  
* If the dropouts occur randomly, or you have interference visible, then try config_hdmi_boost from [http://elinux.org/R-Pi_Troubleshooting#Troubleshooting_power_problems here]
}}
}}


|}


{{Helix updated}}


[[Category:XBMC Manual]]
[[Category:Manual]]
[[Category:FAQ]]
[[Category:FAQ]]
[[Category:Troubleshooting]]
[[Category:Troubleshooting]]

Revision as of 03:44, 10 July 2018

Template:XBMC FAQ

Home icon grey.png   ▶ Raspberry Pi ▶ Raspberry Pi FAQ

Frequently Asked Questions Kodi running on the Raspberry Pi.


General FAQ

See also: XBMC all platforms FAQ for FAQs that apply to all versions of Kodi.

Installing Kodi (for Linux) on the Raspberry Pi

Link
Easy / Kodi centric distributions


Advanced / can be used with Kodi

Note that Arch ARM provides different Kodi packages optimized for different RPi models. All builds offer some flavor of HW accelerated decoding just like LibreELEC. The following packages will supply the current stable version of Kodi:

kodi-rpi for RPi 3/4/400

kodi-rpi-legacy for RPi 2

Users wanting to track the master branch may select:

kodi-rpi-git for RPi 3/4/400 only

  • Raspberry Pi OS - Up-to-date versions (Currently Leia 18.7) of Kodi are now on the default Raspbian repositories. See full guide here.

Can I run Kodi for Android on Raspberry Pi?

Link
  • The short answer is no. There are currently no full featured versions of the Android operating-system that work on Raspberry Pi (first-generation) or Raspberry Pi 2. If and when the Raspberry Pi Foundation releases a full featured version of Android for Raspberry Pi, (which, if it occurred, would most likely be only for the newer Raspberry Pi 2), then in theory Kodi for Android should just work on it. This will however depend on what is meant by "full featured" in fulfilling all the Android API requirements that Kodi needs to fully function properly.

Can I run Kodi for Windows on Raspberry Pi?

Link
  • No. There are no full featured versions of the Windows operating-system that work on Raspberry Pi (first-generation) or Raspberry Pi 2, and there probably never will be. Microsoft have a released an IoT (Internet of Things) version of Windows 10 for Raspberry Pi 2, and by definition that IoT version is not a full featured versions of Windows which is what Kodi for Windows would need to run on the Raspberry Pi.

Is Kodi for Raspberry Pi different from normal Kodi?

Link
  • The current stable version of Kodi for Raspberry Pi is Kodi v20.5 Nexus. This is the same code that all of the other platforms (Linux, iOS, Mac OS X, Windows, etc) are using.
  • There are two acceleration options on the Pi. "omxplayer" runs much of the player logic on the gpu which is highest performance option and can handle raw Blu-Ray quality videos. It does not support DVD menus or ALSA audio.
  • "MMAL" acceleration uses dvdplayer with hardware acceleration of the video codec. Performance is a little lower than omxplayer, but should still handle most 1080p content.
  • By default both are enabled, and omxplayer acceleration will be disabled when not appropriate (i.e. DVDs with menus or when ALSA audio is enabled).
  • If you don't play raw Blu-Ray quality videos then disabling omxplayer acceleration is an option which some users may prefer.

How do I find out what version of Kodi am I running?

Link

Video and audio formats the Raspberry Pi can playback

Link
  • H.264 (up to High Profile) encoded videos are supported up to 1080P using hardware video decoding. Note: Hi10P will not work.
  • MPEG-4 encoded videos are supported up to 1080P using hardware video decoding. This includes XviD and recent versions on DivX (but not the older 3.xx DivX).
  • The Raspberry Pi Foundation offers additional video codec licenses for a few dollars. At the moment you can purchase MPEG-2 and VC1, both with support up to 1080P. Read below on how to enable these.
  • MJPEG, VP6, VP8 and OGG Theora are supported as GPU accelerated software decoders. These are limited to DVD resolutions.
  • Codecs without gpu support like DivX 3, msmpeg and sorenson spark will be decoded by dvdplayer on the ARM. Should work for SD resolutions.
  • DVD ISOs with menus should work fine (using dvdplayer).
  • Software DTS audio decode works well in recent builds. TrueHD audio is CPU intensive and may require overclocking.

Video and audio output on the Raspberry Pi

Link
  • Video output via HDMI up to 1080P. The GUI is 1080p by default, but can be reduced in video settings without affecting video resolution.
  • Video output via the analog component video (RCA) jack will be in SD.
  • Analog audio output via the mini phone jack is supported.
  • I2S and USB ALSA audio cards are supported with Kodi v20.5 Nexus builds. omxplayer acceleration is not available (it will be disabled automatically).
  • DTS and AC3 audio passthrough audio is supported (and recommended, as it will reduce CPU load on the R-Pi)

How about multichannel audio support?

Link
  • By default audio is downmixed to stereo.
  • If your receiver/TV supports DTS or AC3 passthrough then enable these in audio settings and you will get 6 channel audio.
  • Multichannel PCM audio is supported over HDMI. Note: not all receivers support this and toslink/optical will not.
  • Enable by setting the speaker configuration to suitable value (e.g. 5.1 or 7.1).
  • If your recevier does not support multichannel PCM, then leave this at 2.0. You can still get multichannel audio through passthrough.

Enabling additional video codecs

Link

You can buy additional video codecs (VC-1 - used in some bluray discs, and MPEG-2) from the Raspberry Pi Foundation online shop. After purchase the keys are emailed to you, looking like this (invalid keys used for example):

decode_MPG2=0x1cc591c7
decode_WVC1=0x8aa09876

In order to enable additional video codecs you should modify /boot/config.txt and add these lines literally. The method may vary per distribution:

  • Manual: Open /boot/config.txt with a text editor like nano or vi, and add the keys.
  • XBian: You can add/remote your keys using XBian-config. After reboot your keys will be entered and ready to use.
  • OSMC: Go in to My OSMC -> Pi Config. Navigate to Codecs and enter your keys with the on-screen keyboard. After a reboot your keys will be entered and ready to use.

Accessing media

Link
  • You can connect to media that's being shared from a computer, HTPC, or NAS device on your local network.
  • You can access media on the main SD card or from the USB ports (hard drives, USB stick drives, hubs, all supported).

Add-ons and skins

Link
  • Kodi for Raspberry Pi is a full version of Kodi and will be able to use all non-platform specific add-ons and skins. More feature rich (CPU demanding) skins might not run smoothly, so keep to "lighter" skins.
  • Recommended lite skins include: Estuary (default skin), Confluence, Amber, Metropolis, Quartz, xTV-SAF. Aeon Nox 5 is quite usable.

How to properly shutdown/disconnect

Link
  • It is not possible to use traditional "shutdown" on the Raspberry Pi. The only way to power it off is to disconnect the power.
  • ALWAYS select the shutdown command in Kodi before powering off the Raspberry Pi. Failure to do so can corrupt the Kodi library databases, other databases, or even other OS files.
  • Most users leave the Raspberry Pi on all the time, as it uses very little power (the cost of electricity for a year is about the price of a hamburger).

Remotes for Raspberry Pi

Link
See: Raspberry Pi#Remote controls

MySQL library sharing

Link
  • If you are using MySQL library sharing features, please note that your library will only sync with the Raspberry Pi if all your other Kodi instances are running the same version (how to check your version).

Troubleshooting

Getting more help with Kodi for Raspberry Pi

Link

Userdata folder and logs

Link
See How-to:Submit a proper bug report for bug reporting details and Debug log for how to post the debug log.
  • Userdata folder:
    • LibreELEC: /storage/.kodi/userdata/
    • OpenELEC: /storage/.kodi/userdata/
    • OSMC: /home/osmc/.kodi/userdata/
    • XBian: /home/xbian/.kodi/userdata/
  • Debug log:
    • LibreELEC: /storage/.kodi/temp/kodi.log
    • OpenELEC: /storage/.kodi/temp/kodi.log
    • OSMC: /home/osmc/.kodi/temp/kodi.log. On OSMC, a Debug log can be uploaded via My OSMC -> Log Uploader.
    • XBian: /home/xbian/.kodi/temp/kodi.log

Wrong language displayed in Kodi

Link

Raspberry Pi known issues

Link

Frodo issues

Performance: video buffering, stuttering, choppiness

Link

Note: Some of these tweaks are more aimed at the Pi 1 CPUs (A, B, A+, B+, Compute Module, Zero) as they only have a slow single-core CPU. Raspberry Pi 2/3 probably doesn't need some of these tweaks to run Kodi really well, but it also won't hurt anything, if you really want to push things to their limit.

  • Avoid "heavy" skins and lots of "service" type add-ons that run in the background.
  • Turn off RSS feeds and any scrolling text options for your skin. Depending on the skin/text, this can really boost a Pi 1, sometimes even a Pi 2/3.
  • Use an SD card with good rewrite speeds. The class of the SD card doesn't always mean it will be better, as that speed classification is for sustained reading and writing, whereas for Kodi, random read/write speeds are more important.
  • You can also try a combination of SD and fast USB drive for your Kodi install, but with the recent software improvements even just using a good SD card is about as fast as using a fast USB drive.
  • Avoid using wifi. If you do use wifi, use a wifi adapter that contains two antennae (internal or external) that advertises "300 Mbps". Otherwise, stick to wired ethernet, local USB drives, or ethernet-over-power devices (like Homeplug).
  • Try using NFS file shares instead of SMB file shares.
  • Overclock. Most Pi's can handle a significant overclock, as long as they have a good power supply. There is no universal setting that will work for everyone (except for the default speed that you get without overclocking). Try various overclocking settings and run Kodi for a while to see if it's stable. If one group of overclocking settings causes crashes, try a group of lower settings.
Note: Overclocking is pretty important for the Raspberry Pi 1 (A, B, A+, B+) and Zero, but much less so on the Pi 2/3 due to the multiple CPU cores as well as increased speed per core. You can still overclock the Pi 2 if you really want to, but for most users it makes little difference.
  • By default, "Extract thumbnails from video files" (in Media Video Settings) is disabled on the Pi, improving browsing performance.
  • For smoother video playback, enable "Adjust display refresh rate" in |playback settings
  • When using dvdplayer, "Sync playback to display" for sync method are recommended; see playback settings.
  • Make sure the video is using H.264 (up to High Profile — Hi10P will not work), or MPEG-4, or, if additional codecs have been enabled, MPEG-2 or VC-1.
  • Passthrough is recommended as it lowers CPU usage for DTS and AC3. Use audio passthrough if your TV/receiver supports it.
  • To determine which audio passthrough formats your HDMI-connected TV supports, you can log in via SSH and run this command: /opt/vc/bin/tvservice a (on LibreELEC: tvservice -a).
  • For locally connected drives containing videos and music, the filesystem can have an impact on read and write speeds. NTFS for example tends to be much slower on any Linux-based system than the more native ext2, ext3, etc.
  • If you use MySQL, you will want to make sure that your images are pre-cached using the Texture Cache Maintenance utility tool. Local libraries typically don't need this as their images are cached when videos are scanned in. Using MySQL can improve performance as the database queries are handled by another machine.
  • Organizing your movies in single folders for each movie, rather than all movies in one folder, is recommended. The individual folders reduce the time it takes for Kodi to look for supporting media like external subtitles, which makes browsing, scanning and starting playback a little faster. You might also want to consider pre-scraping the meta data using a Library manager to reduce the time it takes to scan in both movies and TV shows.

Memory usage (especially with 256M Pi)

Link
  • gpu_mem should be set to 128M on a Pi1, 256M on a Pi2. On a 256M Pi1 it is recommended to set it to 112M. On a 512M Pi1 it may be worth increasing this if you are running heavy skins or if you want to increase the default fanart resolution or colour depth. 256M should be more than enough on a Pi1, although 320M on a Pi2 may be appropriate if using higher resolution imageres/fanartres and also higher colour.
  • A 256M Pi is quite short on memory. Be careful with running other apps in the background (e.g. torrents) or installing add-ons that consume memory.
  • The default cachemembuffersize will be 2M for a 256M Pi, and 20M for a 512M Pi1/Pi2. You can use 0 to cache to sdcard.
  • Reducing the "GUI resolution limit" (e.g. to 720p) in settings/system/video will save memory. This is a default on a 256M Pi. Video will still play at full resolution (e.g. 1080p).
  • Enabling "higher colour depth artwork" will use more memory. It should be disabled on 256M Pi.
  • Reducing imageres/fanartres will reduce memory usage.

TV is not detected unless powered on first

Link
  • Some TVs/receivers only report their capabilities (EDID) through HDMI when powered on before the Pi.
  • If TV doesn't get the right resolution or CEC doesn't work when Pi is powered before the TV/receiver then you can:
  • Run: sudo tvservice -d edid.dat (after booting with TV/receiver powered on first)
  • copy the edid.dat to the FAT partition (/boot on raspbmc and /flash on openelec)
  • and add to config.txt: hdmi_edid_file=1 and hdmi_force_hotplug=1
  • Note: if you change TV/receiver or use a different HDMI input you should capture a new edid.dat file
  • You can use Raspberry Pi EDID locker to run all these commands at once.

Videos don't play from archives

Link
  • When browsing, any archives need to be extracted to identify the content. This can be very slow and even cause out-of-memory crashes with large archive files.
  • On the Pi this is now optional (enabled by default), enable or disable with: Settings -> Appearance -> File lists -> Support browsing into archives
  • If your library does contain rar files, beware of disabling - you may need to rescan library after enabling again. Also note that subitles in rar won't work when disabled.
  • Note: using rar files doesn't save any space as video files are already highly compressed, so just extracting them would be the preferred solution.

Coloured square appears on screen

Link
  • A coloured square may appear in the top right corner of screen to warn you of problems that should be remedied.* More info here.
  • A multicoloured square means the voltage is too low. You should try a better power supply or cable between power supply and Pi (Note: under-voltage detection is only supported on B+ and Pi 2)
  • A red square means temperature is high (85'C) and overclock has been disabled. This is pretty rare, but can occur in a hot environment, with a case with no ventilation and with the Pi on hot equipment.

Audio or video dropouts on HDMI

Link
  • If the dropouts only occur when playing video with "adjust display refresh rate to match video" enabled, then try adding hdmi_clock_change_limit=20 to config.txt
  • If the dropouts occur when cpu is busy (e.g. scrolling through library) then an insufficient power supply is most likely.
  • If the dropouts occur randomly, or you have interference visible, then try config_hdmi_boost from here