Posts by chewitt

The short answer is no. However, in our add-on repo there's a Bluetooth audio device switcher that is functionally similar to what you need; it detects the connection of the BT device (over d-bus) and auto-switches the Kodi audio output from alsa to pulse-audio. It's probably not impossible to extend that or plagiarise the device switching code to work with other devices (USB devices don't generate d-bus events so another method of initiating the switch is required) but if you don't have the developer skills to do that yourself the challenge is always finding a willing volunteer who does.

Amazon-VOD from the Sandman79 repo is the only one that works for me

If you run "systemctl restart kodi" does HDMI audio appear?

If yes it's a simple timing issue where the audio drivers haven't loaded before Kodi starts so the alsa devices can't be auto-detected. Adding a "wait for network" delay via LE settings should fix that. It's badly named and will act as an arbitrary Kodi startup delay.

It might be easier to explain what you're trying to functionally achieve? then we can suggest other approaches.

Plan B .. get a USB flirc dongle

K18 has officially added the ability to play DRM'd content via inputstream.adaptive and a helper add-on that acquires the needed Google libwidevine libraries with varying degrees of complexity. There are also unofficial community add-ons for Netflix/Amazon (and some others) that leverage the DRM playback capabilities. These are not official in two senses: a) not distributed via the official Kodi repo, b) not endorsed or created by the respective content providers. Several content providers have indicated that adding them to the official Kodi repo will trigger action. so they remain available only from their unofficial but well known (non-pirate) repo sources that are safe to install.

It should run on variants with any RAM size. It means the bootloader cannot find a FAT partition with that UUID so it bails and doesn't boot.

HEVC is supported via software decode since LE 8.2 (K17) but LE 9.0 (K18) will perform better due to further optimisations. You will need RPi3B/3B+ to use it and mild overclock (with a heatsink) helps .. because it's software decoded.

Make a backup and move it off-box. Clean install LE. Selectively restore thumbnails, DB files and config xmls from the backup. Do not simply restore the backup else you also restore a ton of crap that isn't required.

If you share "dmesg | paste" and "lsusb -v | paste" output (URLs) with the controller attached we can see the device ID's are, and start investigating.

*DEBUG* log .. else we can't see the detail needed to diagnose things.

2019-03-11 22:36:08.402 T:1790935920   ERROR: GetAddon failed on addon plugin.radio.dancefloor
2019-03-11 22:36:08.402 T:1790935920   ERROR: SQL: [Addons27.db] SQLite error SQLITE_CORRUPT (database disk image is malformed)

^ delete the DB file. It will be recreated on restart, but with add-ons disabled, so you will need to go re-enable them.

You need to set a Samba username/password in the LE settings add-on (and leave SMB2/3 defaults enabled, not SMB1). Win10 requires authenticated SMB connections.

Five Ninja's ran a successful kickstarter and shipped product, but RPi2 appeared shortly after the CM(1) based slice appeared which reduced demand and I also have an impression the folks behind the company had crazy-busy day jobs so the venture didn't quite get the attention it needed to survive in the long-term. Last I heard Pimoroni retains a small spares stock to service customers, but otherwise Slice has come to an end. In the future LE will drop support for the dedicated image; it's not worth sustaining for the small number of users. Instead we will roll it into our normal Pi images.

Our master branch bumped from SSL 1.0 to 1.1 which includes a breaking API change. All binary add-ons will need to be rebuilt, re-published, and re-downloaded by users. Master is in a pre-Alpha state at the moment so we are fine to do this, i.e. user update issues are not something we consider at this stage of LE 9.2 development.

Are you trying to update (via tar file) or do a clean reinstall of the OS?

The big change between OE (and older LE versions) and LE 8.2 or newer is that SMB1 is no longer used by default (client or server). LE clients will need to set user/pass credentials on all shares accessed, configure Kodi to use them, and use SMB2/3 *or* (against our advice) force Kodi to use SMB1 by setting the Kodi SMB client (in Kodi settings) to use min/max SMB1. Really ancient old NAS may also need the SMB legacy security option checking. If using LE as the server; we now default to SMB2/3 but this can be changed. Older Samba clients may default to SMB1 so cannot see the shares requiring config in the LE settings add-on to be changed *or* (better) you should update the Samba version on the other Linux OS to something less prehistoric.