Is it really necessary to force users to use pippleware's KODI?
-
Hi,
I never thought I would post a topic on this forum because RetroPie worked fine for me all this time.
But lately when I update RetroPie it updates KODI with pippleware's version, I don't want that to happen. Besides it installs a new repro which I really don't like.
KODI from Jessie works just fine on my PI2, can't say that about pippleware's version, it just restarts and keeps restarting. This is really starting to annoy me, wasting my time purging pippleware's KODI and reinstalling KODI from Jessie when I could be playing classic games from the past.
Please fix this. Purging kodi and kodi-bin before updating apparently doesn't help.
Thanks.
BTW: when I uninstall KODI in retropie_setup the ports menu disappears, I have to install/reinstall something to make the ports menu available again.
-
BTW: when I uninstall KODI in retropie_setup the PORTS menu disappears, I have to install/reinstall something to make the PORTS menu available again.
-
I could be wrong, but I'm of the opinion that running KODI outside of it's own stand-alone distribution for the Pi will always be problematic in one way or another. A fully capable KODI install needs the kind of care that can't happen as a second class citizen in another distribution. Constant optimizations and enhancements are being developed specifically for the Pi that seem to take longer to filter into a vanilla install.
Perhaps this is the very reason that the pippleware version was chosen and if so, it appears that it's still a less than desirable option, but to say that you're being "forced" to use it might be a bit extreme when there are some truly amazing stand-alone distributions of KODI available for the Pi. This post is not meant to be confrontational. It's only meant to express my own personal outlook on where I see KODI's ideal environment on the Raspberry Pi and where it might offer the least amount of headaches.
RetroPie v4.5 • RPi3 Model B • 5.1V 2.5A PSU • 16GB SanDisk microSD • 512GB External Drive
-
You are not forced. You can remove the retropie one and install the Jessie one manually. The pipplware one is better from my experience . Newer, joypad support, and some pi extras
-
@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. -
@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.
-
@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)
-
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.
-
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.
-
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.
-
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.
-
Please post some logs:
/tmp/runcommand.log
/home/pi/.kodi/temp/kodi.log -
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.
-
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.
-
That's fine by me.
-
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: 1Now 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!
-
Wait! you never told us where you hid the money.
-
I might cover that in my next appearance...
Until then, toto has left the building!
-
@toto If you don't want to help other people on this forum, why did you even start this post??
-
You might not have noticed but I even posted a simple solution (apt-pinning) to my problem above which also could help others.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.