Is it really necessary to force users to use pippleware's KODI?

Rascas

@toto This was already explained various times. The PiPplware Kodi version is optimized for the Raspberry Pi. I can do pretty much everything with it that I can do with OpenELEC/OSMC, it is compiled with pretty much the same patches and the additional joystick support which the others don't have in the stable versions. The joystick support is not perfect but it is better than nothing in my opinion. BTW I am the guy responsible for it. On the other way, the version on Raspbian is still 15.2 at least the last time I checked and that's the one is the vanilla Kodi version without the Pi optimizations. I know that because I use the same debian scripts.
So if you have a problem with Kodi, please say what it is exactly and post some Kodi logs. Most likely you are using some old addons that don't have proper support for 16.1 or some joystick that is causing problems. Try without joysticks connected to see if the problem still remains.
If you are not interested in that just remove the repo and force reinstall Kodi in terminal.

mediamogul

@Rascas said in Is it really necessary to force users to use pippleware's KODI?:

I can do pretty much everything with it that I can do with OpenELEC/OSMC, it is compiled with pretty much the same patches and the additional joystick support

I've been a big fan of OSMC and OpenELEC, mostly because the enhancements you mention have been absent in most other Pi releases. As such, I've never even installed KODI on RetroPie. Your post has made me very interested to try it now. It would be nice to not have to switch out cards between the two most popular Pi applications.

I make use of KODI's feature set from one corner to another and I have a few questions forming in my head about this version, but I should probably do some reading on pipplware first, as I'm sure the information is out there. My first step will be to repeat the name "pipplware" several more times this morning, because it's just fun to say.

herb_fargus

@Rascas btw I played with some test builds of kodi 17 and I really liked the new joypad config, that should render some of the configs we add by default obsolete if they have been causing issues (the latest kernel has some issues with the xboxdrv)

Rascas

Yes, I think it will be much better. I will make a new Kodi 17 build when the first beta comes out or so. Right now I am quite busy and I am almost sure it will take some work to get the joystick working, at least i had in the previous Kodi 17 build.

toto

I know I can revert back to Raspbians KODI after upgrading, been there done that several times, that's not the point here.
The point is that pipplewares version isn't working for me, it just crashes all the time.

I would be happy using pipplewares version if it didn't crash. To test it again I just purged Raspbians KODI (and all relevant packages) moved the .kodi dir to a temp dir and installed pipplewares version but to no avail. It just keeps crashing!

This is with Raspbian Jessie Lite (not altered very much, just added some console software).

Raspbians KODI works very well for me, it would be nice to have the option to choose which version you would like to use instead of just adding a repro and updating KODI to that version.

And yes IMHO this kind of forces people to use a specific version of KODI (unless you're prepared to waste some time on it) while on the other hand you're are free to use wichever emulator you want to use for any kind of system.

Rascas

Did you at least tried with a really clean install, without your old .kodi settings ? And check or post some logs ? I could help you with that, but I am not interested in spending time giving support for an old, unoptimized Kodi version. I am not a RetroPie maintainer, just this Kodi version maintainer.

toto

@Rascas

My Jessie Lite setup is up to date and as you can read above I indeed moved my .kodi dir to a temp dir before trying pipplewares version so it as good as a clean install as you can get. Like I posted above it is pretty much an unaltered Jessie Lite setup.

Rascas

Please post some logs:
/tmp/runcommand.log
/home/pi/.kodi/temp/kodi.log

toto

I'm sorry but I removed all the logs and reinstalled Raspbians KODI after testing. I'm really not to bothered doing that all over again.

I just keep it as it is for now, everything I want is working fine.

BuZz

Doesn't help us though - and bear in mind people may not be "bothered" to help you next time you have a problem either! it goes both ways.

toto

That's fine by me.

toto

For anyone interested, this fixes my initial annoyance.

Create or edit /etc/apt/preferences with the following text:

Package: *
Pin: origin *.bintray.com
Pin-Priority: 1

Now KODI and related packages won't be updated/upgraded to pipplewares version.

That's it from me, you can now delete my account at your convenience.

Thanks!

mediamogul

Wait! you never told us where you hid the money.

toto

I might cover that in my next appearance...

Until then, toto has left the building!

glennlake

@toto If you don't want to help other people on this forum, why did you even start this post??

toto

@glennlake

You might not have noticed but I even posted a simple solution (apt-pinning) to my problem above which also could help others.

BuZz

No actual need to pin it - if you uninstall kodi from retropie-setup (at least on v4.x) it removes the repo and packages - and jessie version can be installed. Or manually uninstall and remove /etc/apt/sources.list.d/pipplware.list

[edit] correction it wont uninstall the repo without a dependencies removal currently.

sudo ./retropie_packages.sh kodi depends remove

toto

Just got home and decided to have another go at this although I'm perfectly happy with apt-pinning myself it might help others.

Tried it with another SD card (Raspiban Jessie Full edition unaltered, up to date only RetroPie installed). The same thing happens when I use pipplewares KODI, it just segment faults. I have saved the log file (only KODIs, started from console).

If people are still interested I could post that log file.

BuZz

Yes please. (via pastebin.com or similar).

toto

@BuZz

Pinning was the best option for me because when you update installed binaries from retropie-setup it installs pipplwares repro again and you can start over again. This way pipplwares repro gets ignored when you upgrade.