Can't get Kodi to run with Retropie 3.7
-
Thanks for the response and sorry about the long error log. I had read the post you cited before posting mine. With all due respect, the post doesn't provide a solution to the problem. As with the case of the original post, I am using a PS3 controller connected via USB. I am already well aware of the Bluetooth problem with the Pi3. However, unlike the original poster, I started with a clean install of Retropie 3.7. So the original post doesn't really help me. This the reason for my post.
-
@Boomer543 I cannot replicate the issue on a clean Retropie 3.7 image install + Kodi from experimental (not changed es_systems.cfg). Also without bluetooth controllers.
Please reinstall Kodi again, and try again from Ports, without changing es_systems.cfg. If the error persists, put the full log on pastebin, and indicate every device model connected to the RPi including the Amperes of the PSU. -
This post is deleted! -
@Hellcube That is offtopic.
Create a new topic with a title like "How to autostart Kodi in RetroPie, and add a shortcut to ES" or something like that.
Has you may know, both Kodi and ES don't support X server on the Raspberry Pi, you cannot open ES without closing Kodi first.
-
Tried it again and it still crashes. Here's the link to the crash log: <script src="//pastebin.com/embed_js/2mRyWAvT"></script>
Using a Pi3 with a fresh installation of RetroPie 3.7. Using the recommended 5v 2.5A power supply referenced in the wiki. Have a PS3 controller attached with a USB cable. Have a Logitech K260 keyboard and mouse connected via a USB dongle. Using the overclock settings suggested by the Wiki.
If it's not a simple correction, it's no big deal. I have Kodi running on other systems.
Thanks!
-
@Boomer543
So you are using overclocking ? Than most probably thats the problem. Disable overclock and try again.
You should have said that in the beginning, to not waste our time.
If you posted the full log that would be visible also, so next time post full logs. -
@Rascas I don't believe that I had overclocked when I first posted my error issue. If Kodi doesn't work with overclocking, maybe it would avoid wasting people's time in the future to make that clear somewhere. Thanks for letting me know.
I tried to post the complete error log, but didn't realize I couldn't copy and paste the whole thing from a terminal window. Looking for the proper solution for that problem in case I need it some other time.
Sorry for wasting your time.
-
@Boomer543 Kodi works with overcloking, it depends on how much you overclock, the settings etc. Not all the boards are the same also, so the amount that you can overclock one Pi can be different from another. Also some SD cards dont't get well with overclock. It also can depend on the PSU.
So like you can see there are many factors that you to consider when making overcloking. -
HI, I'm facing the exact same issue described here in the first post, same HW/SW config, no overclocking. Any news about a possible solution?
-
@Jona1975 Post your Kodi log.
https://retropie.org.uk/forum/topic/3/read-this-first
Also, remove your .kodi folder (/home/pi/.kodi) and try again. This will reset your Kodi settings! -
Couldn't collect the logs because now I'm facing ssh issues.. but meantime I've installed the just-released Kodi 16.1 and it works! :)
-
I recently did a full install from downloaded image and had just about everything setup that I wanted on a 128GB stick and went to check on Kodi today and it just kicks me back to the Ports menu? That kinda what you've experienced? I tried the refresh script and exited, reloaded then reinstalled Kodi again and still same kickback to ports menu.
SOOO...I guess I'll try removing the .kodi folder and see if I can reinstall again thru the experimental menu to see if that fixes my problem. I've only ever used an xbox 360 controller upon first boot of emulation station....never did the keyboard configuration but when I did configure it (everything but the analog sticks) whenever I went into Kodi it stuck all the way to the left on Weather. You could hold down the key and it would try going to the right but kept repeating like a key was stuck to the left. Even tried different keyboards (one wireless one wired) so dunno what's up with that. Anyone had any problems with a multiple controls setup like that screwing things up (keyboard and xbox 360)?
-
same problem here. after update kodi (via experimental packages) from version 15.2 to 16.1 app keeps kicking me out to ports menu. i removed kodi (also manually all other kodi folders) and try to install it again. i get the same kickback problem.
im using pi3 with rpi3.7 and ps3 controller (usb connected).
someone ex[erienced the same problem ? any ideas what is possibly wrong ? kodi is my must have on retropie :/
cheers -
One thing that I remembered now is that unofficial addons and specially skins (unless the default one) can make Kodi stop working after upgrades. Some addons and skins needs changes to work in newer versions of Kodi.
If you move/remove the /home/pi/.kodi folder, to force a Kodi settings reset, it will most likely work.This should be known by old Kodi users.
That is why it is recommend to backup your settings before upgrading.If something like this happens, another solution is to downgrade Kodi version.
If the skin is the problem, you can edit /home/pi/.kodi/userdata/guisettings.xml and change the skin line to Kodi's default:<skin default="true">skin.confluence</skin>
You have been warned, so think twice before rushing to update Kodi when a new Kodi version is available.
-
The configuration of controllers in ES, are independent of Kodi, so it doesn't affect Kodi.
Reletevely to Keyboards and Joysticks in Kodi, I also never experienced any problem, besides the one here https://retropie.org.uk/forum/topic/453/kodi-16-1-is-out/3 which is fixed in Kodi 16.1.
I only used a XBOX 360 controller, but without the xboxdrv, and it worked fine in Kodi. With the xboxdrv I don't know, it was fixed in the Kodi source code, not by me.
-
@Rascas I submitted a PR for the Xboxdrv name but for some reason it was reverted (perhaps due to being superceded by the new joypad support in kodi 17- idk)
https://github.com/xbmc/xbmc/commit/377fbb08d3adf85d753e752745069435d24b0845
-
@herb_fargus Yeah I noticed that. It is strange that it was reverted back with the reason "superceded" because it will only be superceded in Kodi 17, but that is like every other joystick keymaps currently present. In Kodi 17, there is/will be a specific addon to handle joysticks.
Can you test the XBOX 360 controller with xboxdrv in Kodi to see if there is any problem ? -
@Rascas hmm... It seems to cause issues. I guess I can see why they reverted it. Perhaps it didn't like the parentheses or something in the master keymap. I'll post the crashlog
-
@Rascas Here are the crash logs:
I have disabled CEC through my boot config.txt so I wonder if that also may be affecting it.
It seems to try and start up two kodis or at least was glitching a bit while it tried and failed to initialise the xboxuserpace driver. it eventually did load and the buttons worked but the directions with the analog and dpad did not work at all. I'll try re-enabling my cec utils and see if that helps
EDIT cec changes did nothing, same issue.
The only way I could get it to go left or right was to press the analog stick buttons and move it around but it definitely wasnt usable. Perhaps it is still best to leave joypad support to be done manually for now (at least for the userspace driver) my logitech f310 on the otherhand works great.
-
I noticed a few problems with using the xboxdrv with the builtin kodi xml as well, so I mapped out a simple one that works for me. I think the issue was that xboxdrv uses buttons for L2 and R2, so the axis and buttons get shifted.
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.