Kodi.Launcher.Flatpak.Omega.sh
- Flatpak.Omega.jpg (39.1 KiB) Viewed 66 times
Old updates shown in pics, ask for details to make your own if you got basic editing skills.
- Kodi.Launchers.jpg (232.28 KiB) Viewed 636 times
Just click on a build, all necessary actions will be done, and Kodi will open your build
Kodi check loads a blank Kodi you prepared, with Diggz URL and wizard so you can install a new build faster. Clicking on Store builds will delete that build if you don't rename it to include it in a Kodi launcher properly.
Video:
.
.
Available versions:
Kodi.Launcher.Dual.sh ----- Dual multi launcher -System Omega & Flatpak Matrix.
Kodi.Launcher.Flatpak.Dual.sh ----- Flatpak only dual multi launcher -Nexus & Matrix.
Kodi.Launcher.Flatpak.Omega.sh ----- Flatpak only Omega multi launcher.
Kodi.Launcher.sh ----- Simple Nexus or Omega multi launcher.
Download any of the above here:
https://mega.nz/folder/aeBiABAB#8VbOIeUJggEstJVTwlHqXg
Make it executable eg with:
chmod +x Kodi.Launcher.sh
Dependencies: yad, thunar, kitty.
.
Another approach is to use both Flatpak Kodis on the same Launcher, and use another Launcher for eg Kodi Omega:
.
.
Notes on making it work, renaming or removing builds from Kodi Launcher:
Flatpak Kodi (system Kodi uses .kodi instead of data, replace data with .kodi below for the current version) uses one exclusive folder named data and executes only that, so a renaming procedure must take place to select multiple builds.
The big issue was to find a way for Launcher to automatically recognize the build in "data" folder, and rename it to the build name, so you can change builds.
The solution I'm using is to place empty text filenames inside each build that the script recognizes, so place those text files and rename your builds folders according to the app. Example in .kodiX folder, there is the Xenon Plus build, and you have to place inside the folder an empty text file named: XenonPlus