<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 20/05/15 21:43, Peter Bennett
(cats22) wrote:<br>
</div>
<blockquote cite="mid:555CF1D5.2000607@comcast.net" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 05/20/2015 03:42 PM, Gordon McCrae
wrote:<br>
</div>
<blockquote cite="mid:555CE3AF.3070108@googlemail.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Was this a while ago that you had to compile? Perhaps it was
simply an issue with your chosen disto, we all get that
sometimes. I use OpenSUSE 13.2 and the standard RPMs had
everything I needed. Similarly, on Android it was just a case of
downloading the .apk and installing that, no need to root
anything.<br>
<br>
</blockquote>
This was a two or three months ago - my distro is "raspbian" which
is the raspberry Pi version of Debian, and the version of Kodi on
there simply did not work with the mythtv pvr plugin that was
there. I located other repositories that were recommended but
there were library issues such as this:<br>
ERROR: Unable to load
/home/pi/.kodi/addons/pvr.mythtv/pvr.mythtv.so, reason:
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version
`GLIBCXX_3.4.20' not found (required by
/home/pi/.kodi/addons/pvr.mythtv/pvr.mythtv.so)<br>
This seems to be a compatibility problem between the library
version installed in Linux and the version the application was
compiled under.<br>
There are other distributions "OSMC" and "Openelec", which are
appliance load and go types of solutions, these work better but I
prefer to have control over the system and these are rather opaque
in how they are set up.<br>
<br>
Also there is a bug in Kodi with the remote I am using and
Raspberry pi - I made a source patch to get around that - I have
logged a Kodi bug and supplied the patch, but nobody seems to be
taking any action about fixing the upstream source.<br>
<br>
Peter<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
Ah, see this is where half of the "this doesn't work" quotes come
from. I'm not getting at you, but you have chosen to stick to a
specific distribution, for all the right reasons, and within that
distribution you have specific issues, so it's not a problem with
KODI as such, but with KODI on raspbian.<br>
<br>
I had a similar issue recently when I bought a new Lenovo Z50-70 and
installed OpenSUSE 13.2 only to discover that there was a known
problem with the then current kernel version and the left mouse
button on the touchpad. <br>
<br>
The solution was to either put up with it (tapping the touchpad
itself worked fine as a left click), install an external mouse, or
install an "unstable" kernel RPM. I chose to simply go for the "tap
the touchpad", as this is my normal left click action when using a
touchpad, and a month or so later a newer kernel was pushed out
which fixed the problem.<br>
<br>
What I'm trying to say is that you can't really blame KODI for the
issues, rather it's down to a combination of the KODI version,
developers and the distro release folks. You're obviously in a more
restricted position than me, as I can always go and use any x86
based distro, but the same concept holds, I was just lucky that KODI
worked fine for me, including the MythPVR plugin. Like you, I choose
to use a distro I'm familiar and comfortable with rather than go and
use something like MythBuntu which is reported to work "out of the
box" because I like being able to configure the system just the way
I like it.<br>
<br>
Cheers<br>
Gordon<br>
</body>
</html>