I will try to get Kodi 17 (Krypton) up and running with the plugin, I will need to test a new/different repo for that. volumio-kodi-plugin_1.2.4.zip (208 KB)
Hi!
Thank you for the plugin. I use a previous version on 2.041
I tested the last version on a dev volumio 2.114
WebUI stops working during installation due to a no “space left on device”. Sudo journalctl -f shows a loop. Not sure if it come from plugin or volumio… I’m going to reflash a sd card to see if it still happens.
I have to move on from Kodi as a DLNA renderer as it wasn’t possible to have gapless playback. Plus I got too many skips during playback too.
So did an installation of Volumio 2.041 and applied both plugin version 1.2.3 and 1.2.4. In both instances Kodi does not load up.
Following that I installed Volumio 2.114 and applied plugin version 1.2.4. Kodi loaded up successfully. However, when I2S is selected in plugin settings, the sound card does not show up in Kodi audio settings. When I2S is not selected ALSA shows up but with a generic BCM soundcard and sound only plays on HDMI still.
I did in one instance manage to get kodi play from the sound card as intended by just restarting Kodi. ie Shutdown Kodi and relaunch using SSH. However, when I restarted volumio, I would lose audio from the sound card and thereafter I wasn’t able to shut down kodi from kodi interface and replicate activating the sound card.
I will keep trying with a fresh install and let you know the results.
Update: Fresh install of Volumio 2.114. Activate I2S. Restart. Install kodi plugin 1.2.4. (3 windows indicating successful installation)Activate plugin. Restart. Kodi does not launch.
I’m going to need a little bit more info, is there still no crash log? Can you try deactivating and activating the plugin while running “journalctl -f” over SSH and post back the results?
Sound over the DAC must be enabled in the plugin settings, after that you need to restart Kodi (deactivate and activate plugin). It might take a few seconds for the soundcard to initiate, you also might want to turn off GUI sounds and keep alive in Kodi. If one source is playing, the other cannot claim the device, this is not something I can fix.
Just a quick update; I’ve now had one instance in which Kodi was not installed properly… will investigate! All scripts have been written, but the ‘apt-get install’ failed at some point, not sure how and why yet.
I might abandon testing on the 2.041 image, since I think some kernel updates were added in the new images. Not entirely sure, but I’m getting libbrcmGLESv2.so-missing errors on that image when installing Krypton. At this moment this error is beyond me. Maybe someone who knows can jump in? After some hours googling I did not find a viable solution.
Also I think I confirmed that sometimes apt-get update fails, in which case Kodi installation does too… Not sure how to fix this, as I don’t want it to loop… and when it fails it needs a reboot.
So when Kodi does not start, but the plugin seems to be installed successfully:
volumio@volumio:~$ ls -al /home/kodi/
ls: cannot access /home/kodi/: No such file or directory
volumio@volumio:~$ journalctl -f
No journal files were found.
Update: I followed your instructions to uninstall, restart and try again and I got Kodi to launch. It seems the installation of kodi took the longest during the unpacking. Upon completion of unpacking when [Install]
WantedBy = multi-user.target
Added the systemd unit happens, kodi fires up right away with no need to restart volumio.
I am now going to retest the I2S option and report back.
Super that it fires up now! Not sure why it sometimes fails, it has to do with apt-get update (which gets stuck somehow), but it doesn’t happen every time
Update on getting I2S working on kodi. In order to get audio on kodi to the sound card these are the steps taken after installing plugin:
Switch off sound card option.
Restart volumio
Select alsa: bcm option on kodi audio settings.
Shutdown kodi only
Restart kodi only
Sound card output works for kodi. Audio setting on kodi changed automatically from alsa:bcm to alsa:iqaudiodac. (Even though allo 2.1 is selected on volumio options)
0.7s delay option still not working on kodi even when selected and kodi restarted. Currently done through the kodi interface itself as default audio option.
If volumio is restarted with I2S option selected to “on” on kodi plugin settings, kodi will default back to hdmi and the option to select sound card will disappear. Repeat steps above to reinstate sound card.
I am a beginner trying to install kodi on volumio 2. I have successfully installed the plugin and activated this.
Now, when I play some video files, only the sound is played. The TV screen is on the volumio command prompt. I am sure that I have got some easy configurations wrong.
Hey, it does look like it yes, I imaged the 2.114 (i.e. no OTA update).
After 2 minutes the second update (known bug) starts and the installation of packages starts to fail:
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Unable to connect to archive.raspbian.org:http:
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Err http://archive.raspbian.org/raspbian/ jessie/main libjs-jquery all 1.7.2+dfsg-3.2
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Unable to connect to archive.raspbian.org:http:
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Err http://archive.raspbian.org/raspbian/ jessie/main upower armhf 0.99.1-3.2
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Unable to connect to archive.raspbian.org:http:
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Err http://archive.raspbian.org/raspbian/ jessie/main usbmuxd armhf 1.0.8+git20140527.e72f2f7-2
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Unable to connect to archive.raspbian.org:http:
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Err http://archive.raspbian.org/raspbian/ jessie/main libc6-dbg armhf 2.19-18+deb8u7
Mar 06 12:28:05 Volumio3B sudo[1735]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/tee /etc/ld.so.conf.d/00-vmcs.conf
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Unable to connect to archive.raspbian.org:http:
Mar 06 12:28:05 Volumio3B sudo[1735]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Err http://archive.raspbian.org/raspbian/ jessie/main usbmuxd armhf 1.0.8+git20140527.e72f2f7-2
Mar 06 12:28:05 Volumio3B sudo[1735]: pam_unix(sudo:session): session closed for user root
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Unable to connect to archive.raspbian.org:http:
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Err http://archive.raspbian.org/raspbian/ jessie/main libc6-dbg armhf 2.19-18+deb8u7
Mar 06 12:28:05 Volumio3B volumio[1285]: info: Unable to connect to archive.raspbian.org:http:
Mar 06 12:28:06 Volumio3B volumio[1285]: info: Fetched 40.9 MB in 2min 0s (338 kB/s)
Mar 06 12:28:06 Volumio3B volumio[1285]: info: Preparing the Kodi user and groups
If I try to install manually after all failures are done I get stuck at this:
with 2.114, you can now customize DNS servers in Network Preferences.
You may want to input your ISP well-known DNS (or eventually Google’s if you don’t care they track you), and check if it works better.
Apparently this did not prevent the problem… not sure if it is my network or unavailability of the archive… Will keep investigating.
Also the bug is still there that after 2 minutes of execution of an installation script a new instance is launched. I’m trying to work around it, but it’s difficult… I’ll keep you posted.
if worse goes to worse you may add the culprit server IP and name in /etc/hosts.
But would be better to find root cause… What’s in your /etc/resolv.conf?
Haven’t had this problem anymore in the tests of today! yay!
So I took some time to rewrite some parts of the installation script, I’ve had some successful installations since (no more installing twice).
Also I made three packages:
Jarvis (Kodi 16)
Krypton Beta (Kodi 17.0) → this one has trouble starting in the script, so the Kodi-specific settings are not written:
a. Playing GUI sounds
b. Keeping the audio device alive
c. Not using the GPU for resampling
Krypton RC1 (Kodi 17.1) → this one is from another archive which I found after scouring the web for many hours
There was also a problem with persistent mounts in Kodi which I fixed too, some rights issue with sources.xml. And I introduced extra settings (which are also set in the installation script):
En- and disable Kodi GUI sounds
En- and disable Kodi audio keep alive
And as always, if you find something, please let me know!
PS: since I had to wait for another installation I got around testing both Krypton builds on a Pi1 B+, they do work! So, you can use these on a Pi1 (and Pi2/Pi3 obviously). Performance is somewhat laggy, but that is to be expected for a single-core SoC, playback is ok for the most part, just don’t go over 20-30 mbps, the killa sample (bird scene) @40mbps is killing the Pi (a Pi2 and Pi3 have zero performance issues with that sample). volumio-kodi-plugin_krypton_rc1_2.1.4.zip (209 KB) volumio-kodi-plugin_krypton_beta_2.0.4.zip (209 KB) volumio-kodi-plugin_jarvis_1.3.0.zip (209 KB)
FYI, 17.1 brings an important bugfix for python based kodi plugins (there are many): it should bring significant performance improvement on Pi platform…
hello,
Can’t install krypton version, a error occurs.
It seems install.sh is not executable ( chmod +x)
And even with that it does not install.
sudo joutnalctl -f returns :
Mar 12 10:30:30 volumio-buro volumio[1074]: info: END DOWNLOAD: http://127.0.0.1:3000/plugin-serve/volumio-kodi-plugin_krypton_rc1_2.1.4.zip
Mar 12 10:30:34 volumio-buro volumio[1074]: info: Checking if plugin already exists
Mar 12 10:30:34 volumio-buro volumio[1074]: info: Rename folder
Mar 12 10:30:35 volumio-buro volumio[1074]: info: Move to category
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Checking if install.sh is present
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Executing install.sh
Mar 12 10:30:36 volumio-buro sudo[1376]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/sh /data/plugins//miscellanea/Kodi Krypton RC1/install.sh
Mar 12 10:30:36 volumio-buro sudo[1376]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 12 10:30:36 volumio-buro sudo[1376]: pam_unix(sudo:session): session closed for user root
Mar 12 10:30:36 volumio-buro volumio[1074]: [sudo] password for volumio: sh: 0: Can't open /data/plugins//miscellanea/Kodi
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Install script return the error Error: Command failed: echo volumio | sudo -S sh /data/plugins//miscellanea/Kodi Krypton RC1/install.sh > /tmp/installog
Mar 12 10:30:36 volumio-buro volumio[1074]: [sudo] password for volumio: sh: 0: Can't open /data/plugins//miscellanea/Kodi
Mar 12 10:30:36 volumio-buro volumio[1074]: info: An error occurred installing the plugin. Rolling back config
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Plugin folders cleanup
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning into folder /volumio/app/plugins/
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning category audio_interface
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning category miscellanea
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning category music_service
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning category plugins.json
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning category system_controller
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning category user_interface
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning into folder /data/plugins/
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Scanning category miscellanea
Mar 12 10:30:36 volumio-buro volumio[1074]: info: Plugin Kodi Krypton RC1 found in folder but missing in configuration. Removing folder.
Mar 12 10:30:37 volumio-buro volumio[1074]: info: Scanning category music_service
Mar 12 10:30:37 volumio-buro volumio[1074]: info: Plugin folders cleanup completed
Mar 12 10:30:37 volumio-buro volumio[1074]: info: Error: Error
Mar 12 10:30:37 volumio-buro volumio[1074]: info: Folder /tmp/downloaded_plugin removed
Mar 12 10:30:37 volumio-buro volumio[1074]: info: Folder /tmp/downloaded_plugin.zip removed
Mar 12 10:36:56 volumio-buro systemd[1]: Starting Cleanup of Temporary Directories...
Mar 12 10:36:56 volumio-buro systemd[1]: Started Cleanup of Temporary Directories.
All scripts have been written, but the ‘apt-get install’ failed at some point, not sure how and why yet.
yay!