I think that helps, thank you very much mate!
And that's it? Really not more to implement?
I know I'm far away from being able to expect help with my problem within this forum but I'll try anyway as this place is my last hope. So here's my problem:
Beside LibreELEC, for Retro gaming reasons, I have set up "Batocera.linux" on another Linux based HTPC system, with exactly the same hardware, for which I'm having a hard time trying to make WOL work, while on the LibreELEC system WOL is indeed working without problems.
I asked Batocera support for help and there was one guy telling me that there is no solution as Realtek NICs do disable WOL by default when there is a non-Windows OS running on top of the hardware. Beside the news that WOL is not only BIOS setting dependent but also OS dependent, I thought "this can't be true" and for testing I tried to install a generic x86_64 Ubuntu Server system onto the HTPC. And really, WOL is not working with this setup too.
Now my question is: What kind of magic have LibreELEC developers implemented to make WOL work on Realtek drivers on a non-Windows system?
Again: I know, here in this forum I cannot expect anything for other systems than LibreELEC but I am very thankful for any hint as I don't know where else it would make sense to ask. You LE devs somehow have done the trick and I really want to learn how to make WOL work on Linux systems on those Realtek NICs.
Did you also mention there are several emulators not installing correcty while installing them via the wizard?
I have experienced this with LibreELEC and also on Windows/Kodi.
This causes the wizard to bring up the following message at the end:
I would be happy if I would overthinking the problem, already described here btw.
LE just loses the default screen setting sometimes. Unfortunately I was not able to reproduce the issue (yet), it comes and it goes unexpectedly.
Those entries within advancedsettings.xml, in my experience, are the most reliable way to load those settings before kodi starts, when settings within guisettings.xml on the other hand are just saved on poweroff/reboot as you've already mentioned within the other topic. They obviously can be lost/overwritten in some cases, at least on my system.
New website is the bomb, I really like the new style!
In advancedsettings.xml I was able to set a fixed resolution whenever LE boots up, like this example:Code
AFAIK those two settings are always going together (please correct me if I'm wong), meaning:
videoscreen.screenmode setting is always going together with videoscreen.resolution setting.
Now the problem is, when I want to play around with fixed screen settings to find out which one fits best, I always have to set the resolution manually first within the GUI, then open the guisettings.xml file and watch out for the according lines which are holding the two values I need for the advancedsettings.xml.
As you can imagine this is pretty boring, especially because I have to outcomment those two lines within advancedsettings.xml to make guisettings.xml active again, just to set another resolution manually.
Is there a file or a list somewhere which holds all those possible values which are going together from which I can copy-paste those values?
This is mainly because you have chosen to create an independent profile, created from scratch instead of copying settings from master profile, right? I am using it this that way too, btw.
In this case you can "install" your prefered language via add-ons individually for any profile. Works for me without problems.
I am using the Xbox 360 controller for playing games with LibreELEC. Unfortunately the Xbox360 controller is not able being powerred off manually via hardware button by default.
There are indeed some community scripts for Winodws which are doing exactly this but I have not found anything similiar for Linux.
The only thing I found was xpad but I am not sure if and how this could be used within LibreELEC.
Any hints or experiences about this?
After struggling around now with autoexec.py, cronjobs and autostart.sh I found out there is a much better solution:
Add two according XML code lines into advancedsettings.xml to tie the screen resolution to fixed values like this (example for 1080p/60Hz):Code
After lots of tests now I mentioned the "abstracted" XML entries as shown above are not very reliable and pretty unstable.
But it's really stable with the "full" XML entries instead, like this:Code
Have a look into the last provided link above for further explanation.
OK, so can I set this setting on the start of LE via script so that I will not have to change it manually again?
I made the following script which I have tested and is indeed working to change the according value within guisettings.xml when executing manually from command line but I am not sure whether I have to auto-start the script via autoexec.py (which runs before user-login AFAIK) or via autostart.sh (which runs after user-login AFAIK).
I guess when running it via autostart.sh I would also need a command to restart some kind of screen service/process or similiar? I don't think the screen settings will apply on-the-fly automatically by just changing the videoscreen.screenmode value within guisettings.xml, will they? If I need to restart a specific service/process, which additional command would I need to restart the according service/process?
Or could I just use autoexec.py to start the script? In this case, would the script being executed before the screen settings apply to the TV screen?
Here's the script's content I made:Bash
Not sure if this is a bug or an uncoverable behaviour because of all those fancy screen features TVs have implemented nowadays.
It happened a couple of times now but I cannot say exactly when this is happening but sometimes after starting LE I got the behaviour that LE has set the default screen resolution itself from 1080p/60Hz to 4096p/30Hz. Then I have to set it back to 1080p/60Hz manually.
My TV is indeed a 4K TV but I want to keep 1080p/60Hz for different reasons.
Now my questions are:
Why is it even possible LE changes this by itself?
Is there any way I can prevent this behaviour (I don't know if it would help but the idea of taking 4096p/30Hz out of the whitelist would not be an adorable option to me)?
Could it be that LE loses this specific setting after a crash?
Thanks for your investigation.
I had a really hard journey today to make everything work after a lot of hours messing around with IAGL on LibreELEC.
First thing I did was to check your hint:
vfs.libarchive/vfs.rar were already on the latest version and active, so that hint did unfortunately not help anything.
So I decided to reinstall LE10.0 RC1 from scratch and after the first start I was indeed able to run some games which did not work before, but unforunately only once and then not again. I mentioned that on the very first run of a game I was asked for choosing an emulator but on further starts of the same game(s) I was indeed aksed again but the strange thing was that some emulators were disappeared and did not show up anymore altough they were indeed installed.
I was messing around with re-installing IAGL a few times and I tried to download emulators from different repositories but nothing helped.
Then I thought the problem could be the use of multiple user profiles in LibreELEC. I wanted to give it a shot and installed LE10.0 RC1 again from scratch without multiple user profiles and "Bingo!", that was it. I don't know what exactly the proplem is according to multiple user profiles but maybe you can find out and/or tell me/us.
But: Even without the use multiple user profiles I still ran into a strange issue:
After the installation of the IAGL addon, for setting everything up, I chose to use the wizard which was asking me for "archive.org" login. After putting my according e-mail address it told me that the e-mail address was not found within the "archive.org" database. After inserting the same e-mail address again the e-mail address was accepted somehow. Then, on the next step, it asked for the according "archive.org" account password. After inserting the password there was a message showing up that some games may not work without a registered "archive.org" account, but what's pretty disturbing abut this message is that it won't tell you if the password was right or wrong, it's just this message. So you have no idea if the message was just an additional information or if it was an explicit warning because of a wrong inserted password.
Then, after installing all emulators and downloading all game lists, on the very end of the wizard, the setup assistant showed up "Setup could not be completed to launch games with RetroPlayer" which gave me a bad feeling again. And indeed I was not able to run most of the games. So I went through IAGL addon settings and mentioned that the "archive.org" account I have inserted on the wizard was not being saved so I tried to insert it via the IAGL addon settings manually again. Then I checked for "account confirmation" (I don't remember how exactly the option is called within the IAGL addon settings) and got the message that the account was found successfully.
After that I was able to run all games I have tried yet (I will test more games these days and report back if something does not work).
Just to be clear: I did all those steps twice from scratch and as described on the official IAGL Github instructions, just to be sure that this was not happening because of a mistake of myself (which am pretty sure right now).
Plus, if you don't mind, I would like to set an "improvement request" for the IAGL setup wizard: It would be very convenient to have an option to choose to install all available emulators without having to confirm every single one of them to be installed (which is obviously pretty annoying because there are a lot of them).
Thank you and if you have any question or need any further information I can provide, I am happy to help.
I'm the addon author. There looks like there's an issue with vfs.libarchive/Kodi with LE based on the log. The error is:
Which is an error I've never seen. It points to LE not supporting the archive protocol. I'll have to dig into this a little more.
Good news, at least to me, that it seems not to be my mistake
Edit: Thank you for answering my question and for helping me out with this, mate
Sometimes it's better checking the logfiles first by myself I guess.
Resolving the permission issue of mySQL Database resolved the issue.
Thanks and sorry anyway.
Sorry about that.
As I don't know if I can and -if yes- how to provide .old logfiles via LE webserver I'll upload the file here. I hope this is okay.
Since LE 10.0 RC1 on generic x64 device I'm not able to play any of my MKV movies stored on a remote SMB share anymore.
I can navigate through the SMB share but when I start playing a file it shows a black screen immediately for about 3 to 5 seconds and then it puts me back to my profiles login screen.
Here are the dubug logs:
Note: I don't have any other format than MKV movies so I was not able to test any onther container format.