Same here
It doesn't work for me.
Next time, open a proper thread yourself in the appropriate section.
This here is still the News and Announcement forum section.
Same here
It doesn't work for me.
Next time, open a proper thread yourself in the appropriate section.
This here is still the News and Announcement forum section.
I'm afraid, I need to purge the SD and start from scratch. If you agree: Is there a way to manually save the current settings (add-ons, configured shares, DB with information which file was played, ...) so that I don't lose that stuff
Take the SDcard from the RPi and access it from your favorite Linux OS on your PC.
Starting a live session from an Ubuntu USB stick for example should work to access the EXT4 data partition on the SDcard.
From there you can copy files & folders as necessary.
An USB stick can wear out after some time, because of wear and tear of data writing. USB sticks do not have TRIM support.
A hard disk can get defragmented, depended on the disk format and block size you are using.
Are you using an extended cache setting for your Kodi setup?
i have no idea about this error please some solution thank u
You seemed to have copied the server error message from the RealVNC website, so why don't you contact them instead?
Well, you gotta admit. They do look alike quite a bit..
Have you tried finding out what the webpage of the scraper comes up with?
Perhaps it's a info provider hiccup.
Is this forum still alive?
If you are expecting a 24/7 help desk, then you are perhaps expecting the wrong service. LibreELEC and its forum are run by a small number of volunteers, who offer their free time whenever THEY think it is appropriate and possible.
If you can access the RPi4 via SSH, then perhaps you can temporarily reset Kodi into a clean setup and go from there.
Don't install everything like before, just install whatever is necessary for your choppy video playback, and then provide a new log file.
I guess LE10 (first version) will coming when matrix has arrived beta status?
There are only nightly builds for now: Index of /
There is no ETA for LE 10 yet.
OpenELEC 6.0.3 ... That was many many moons ago.
It's best to install LibreELEC fresh, since the latest releases use/need a larger system partition than OpenELEC. Simply upgrading wouldn't work because the system 'blobs' have grown in size since then.
Backups of config files in the userdata folder, such as the advancedsettings.xml & sources.xml file, are best made manually IMO, including the database files in case you are not using a remote MySQL database solution.
Many people have large TVs in a room with public facing windows and this presents a security risk
How often do you have strangers glued to your house windows, staring into your room, while you are entering a Kodi/LibreELEC setup..?
I think we're okay on this matter.
Did you enable SSH during the 'welcome wizard', or did you enable it in the LibreELEC Settings Add-on?
Why Libreelec can't get an addon for it?
Our software is "open source", so everyone can contribute.
We have no magic wand with which we can create new add-ons.
Also, teams LibreELEC and Kodi have enough to deal with already.
Right...
Try connecting to the Rpi-4 via SMB remotely using a desktop or laptop PC.
Then you can copy over the kodi.log file and manually upload it to hastebin or Ubuntu Pastebin .
Should the log still be too long, then cut the file in half, and try uploading it again.
The Wiki has been transformed into a new format two days ago, and some pages may have changed.
You can also try installing the Kodi Log Uploader Add-on, and upload the log file that way.
If you have the laptop connected to the TV (permanently?), then you should be able to disable the laptop's screen and only use the TV. Every laptop has keyboard combinations for that. Actual screen dimming during videos is not supported by Kodi itself. Meaning, perhaps something can be done via the Linux command line using the startup.sh file.
An example with the VGA1 output screen:
Output:
VGA1
And hopefully it works. I would try things out first directly typing on the command line.