Kodi (Port) won't save any changes made to the default settings.
-
@rascas Could you update the script for v17.4 so we can see if it's been fixed ? As I say, if you choose 'Exit' back to emulationstation and then 'Shutdown' from there then everything is fine.
-
Kodi 17.4 is already available on Raspbian Stretch. We don't have plans to update it on Raspbian Jessie. You will have to wait until RetroPie supports Stretch.
-
@rascas that's a shame - a bit premature to drop Jessie updates imho. RetroPie is not switching to stretch anytime soon (there are lots of things to sort for stretch). I may have to consider managing our own port in that case.
-
Wow, pretty much replies at once :D
Thx for help to everyone, who's trying ^^
Let's do it one by one ...
@Rascas i'll post the log, asap and if it's still neccessary after all the initial hints posted there.
@maxbeanz the setting were resetted, even i was shutting down in kodi. And it was not only about skin settings. Also Add-Ons and such were reset to defaults, but add-ons keep being installed.
"I set up my visible categories like Movies, TV Shows, Videos then after choosing 'Shutdown' a few times Kodi starts up with all the Categories back as default. Not sure if it's the exact same problem as above but it's a similar problem."
This is exactly, what happens to me. As only it starts every time with the default settings.
It's sad the know bug will not be fixed on jessie, as (like @BuZz said) the stretch upgrade will not come that soon.
I will try the "first exit, then shutdown" thing.
Is there a way to switch RetroPie to kinda "beta" version with stretch support, so it will get kodi 17.4 already now? -
@renegade2k no. Stretch is not supported yet. We will start adding support after 4.3. even then it will be considered beta until well tested before we switch officially.
-
@buzz The thing is, the changes between Kodi 17.3 and 17.4 are really small, specially on the RPi. The only change that I see that can be related to this is this one:
https://github.com/xbmc/xbmc/commit/49ec2e107fa702d8de691bd55b0b0cb516eea88fBut again, I really doubt that's is their problem, because it only triggers a skin settings save right after you change it, it will always save if you do "Exit" or "Shutdown" in Kodi, even without it this commit.
Continuing to build and support Kodi on Jessie, means 2 more builds (ARMv6 and ARMVv7) + testing it on different systems. We are basically 2 guys doing this on our free time and it requires even more time for us. I would rather spend time helping you porting RetroPie to Stretch than spending more time on this.
-
@rascas I understand but I have many more packages to maintain. I won't release stretch support until I am sure it's ready and stable, and I want to get 4.3 out first. There may be even more Kodi updates before RetroPie is fully stable on stretch - so if you drop support I have no choice but to look into maintaining Kodi ourselves.
-
@buzz I am not dropping support on RetroPie, we still develop and support another OS for the RPi which is still based on Raspbian Jessie also and also includes RetroPie. The thing is, I don't really see an urgency to update it on Jessie. If you all can prove me that their problems are fixed on 17.4, I will update it. Nobody even posted the always required information and their Kodi logs, nobody can support anything like that...
-
@rascas I can only say that I too have seen the skin settings problem on one of my systems in the past. Seems to be ok now - I probably rebooted rather than exiting at the time - also if Kodi crashes on exit (which it has done in the past), I guess this could cause it to not save too. should rebooting from Kodi save them ?
Please can I have a link to your package sources, as I may as well use them as a base if I am going to include Kodi in RetroPie
[edit] actually they may be available from
apt-get source
- I'll check.
[edit] they don't seem to be actually, so if you can provide them that would be useful thanks. -
@buzz Kodi can crash on "Exit" only if you are using "kodi-standalone", this was discussed here more than once. Your script on RetroPie-Setup uses "kodi" and crash on exit won't happen. But I have seen here some tutorials, and also on RetroPie github, a part recommending it to use "kodi-standalone" instead. I change it, but some clever guy changed it back...
The Kodi main packages sources aren't available, because the internal cmake system doesn't have an option to create them, this was also already commented upstream, nobody cared...
The original Kodi source is well know, and ours is here:
https://github.com/PIPplware/xbmc -
@rascas thanks for the info.
-
@buzz Offtopic but. you don't seem to have some sources available like sdl2, etc. Can you please point me to the original source code that you are using for RetroPie ?
[edit] Nevermind, it seems to be just the upstream or from https://github.com/RetroPie/SDL-mirror
-
@rascas yep. Check the scriptmodules as they reference all the source repos.
-
@renegade2k Try this - set your system up how you want it, then go to the system menu and change your skin to a different one (I presume you're not using Estuary given your problem, so switch to that) and then switch back again.
-
@BuZz I have made new 17.4 packages for both Stretch and Jessie, which includes some minor optimizations and information missing. I think the guys from the Raspberry Foundation forgot to upload the Jessie ones, so if you want them you can grab them from the pipplware repo, like you used to. Cheers.
-
@rascas thanks for that. Appreciated. I removed your repo I think, maybe I shouldn't have. Hopefully they will update.
-
@rascas I was going to switch back to using the pipplware bintray repo, so that current users can get 17.4 (and for future updates), but it's currently erroring.
W: Failed to fetch http://dl.bintray.com/pipplware/dists/jessie/main/binary/./Packages 403 Forbidden W: Failed to fetch http://dl.bintray.com/pipplware/dists/jessie/armv7/binary/./Packages 403 Forbidden E: Some index files failed to download. They have been ignored, or old ones used instead.
-
@BuZz that bintray account was suspended, because they say that it was causing a lot of traffic and we are not supposed to use it for something like that.
You can use our original repo instead:http://pipplware.pplware.pt/pipplware/dists/jessie/main/binary/
PS: The armv7 repo is not needed anymore because the packages now contain both armv6 and armv7 binaries, which are automatically chosed according to the user RPi version.
-
@rascas That's a bit crap - so you were going over the 1TB/month there, or they just didn't like the amount ? I'm sure in the past they didn't include a limit. Will switch to your repo thanks - if you need some space for package hosting I could provide some if bandwidth will be a problem at your current host.
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.