This add-on makes it easy to upgrade/downgrade OpenELEC development builds by downloading directly from websites which host them.
It shows a list of available build sources and a list of builds available at the currently selected source.
There is also a service which runs in the background, so when a newer build becomes available, a notification will be shown to enable you to install the update.
To perform an update the add-on will download the (possibly bzip compressed) tar file into the /storage/.update folder. The update will then be installed on the next reboot. This process is as documented on the OpenELEC wiki.
- Install my repository from xbmc.repo.leopold.zip.
One way to do this is to login via ssh and run
wget http://goo.gl/MpUAWy -O xbmc.repo.leopold.zipThen install from zip.
- Install OpenELEC Dev Update from Leopold's Add-ons under Program Add-ons.
Installing this way will ensure that the add-on is kept up-to-date as I push out updates to the repository.
Here is the latest changelog.
- Official Snapshot Builds [Forum]
- Chris Swan (RPi)
- MilhouseVH builds (RPi) [Forum]
- Official Releases
- Official Archive
- DarkAngel2401 Dual Audio Builds [Forum]
Frequently asked questions
- Can I use a URL other than those provided? Yes, an additional custom URL can be configured in the add-on settings.
Is there a way to run it from the command line?
Yes you can log in via ssh and run
chmod +x .kodi/addons/script.openelec.devupdate/download.py ln -s .kodi/addons/script.openelec.devupdate/download.py download.py --help
Please note that this is not an "official" OpenELEC add-on. If you hit any problems with it, don't ask for support from the OpenELEC team, please post on this OpenELEC forum thread or raise an issue. If you have any comments/questions/suggestions please also post on the thread.
Be aware that development builds often have major bugs. you may experience frequent crashes or other problems when using these builds. stick to the official stable builds where possible. Do not use a development build unless there is a specific need.
To avoid potential issues with configuration, it is best to do a fresh install when switching from a stable to a development build, and vice versa.
It is advised to backup the userdata folder when updating. This step can now be automated by the add-on, thanks to the Backup add-on.
- Turn on the 'Debug' option in the add-on advanced settings.
- Restart to start a clean log.
- Run the add-on again to reproduce the error.
- Upload the debug log. There are a couple of ways:
- Log in via ssh and run pastebinit ~/.kodi/temp/kodi.log
- Use the add-on "Kodi Log Uploader".