You can play an audio file and start browsing the list, but it's not an automated thing. You would need to file a feature request in Kodi forums to see what response it gets from core devs. Sounds horrible to me 
Posts by chewitt
-
-
80Mo is 80MB or 80Kb? .. 80MB would be refused in our main images, but 80Kb would be no issue.
-
-
So the question is: Why is the route to the IPv6 default gateway not automatically added like it is the case for the IPv4 default gateway?
Two reasons, which are self-explanatory:
a) Nobody on LE staff has access to an IPv6 network so we are never testing it
b) None of the ConnMan maintainers have regular access to an IPv6 network, so they are testing infrequently and not seriously
User contributions to IPv6 debugging and fixes are very welcome
-
63 characters is the upper limit allowed for a passphrase in standards, although some routers allow 64 characters. ConnMan enforces the 63 limit. IMHO passwords that long are pointless. The exploits for WiFi networks are always about a protocol vulnerability or something in the iimplementation of a specific chip (at silicon level) or a software component in the wireless stack. Unless it's a WEP network (which is easy) no attacker is going to waste their time trying to brute-force the credential, so anything between 12-20 characters is enough.
Correct Horse Battery Staple | Generate Secure Memorable Passwords
-
There is an open pull-request to restore eSpeak (now eSpeak-NG) in https://github.com/LibreELEC/LibreELEC.tv/pull/5786
Can you explain the purpose for libttspico-utils? - I mean, clearly it does TTS, but how is it used and by what applications?. Apologies if these are dumb questions but current staff don't have much exposure to users with accessibility needs.
-
You get bonus credit if you submit the fix upstream to the add-on repo on GitHub
Here I think? https://github.com/melmorabity/plugin.video.francetv/
-
I suspect this has been fixed in the LE10 codebase. I'm frequently setting passwords via connmanctl and have never seen the behaviour of it prompting in the GUI when I try to configure something from the console.
-
The -wetek-play2.img.gz file is designed to boot the box using mainline u-boot (on SD, with emmc wiped). Use the "box" image and edit the dtb name (to the full name of the play2 dtb) in uEnv.ini if using factory boot firnware. NB: Renaming the KERNEL file guarantees the box will not be able to find it and boot.
-
1. Read RE: Cannot Install/Update Addons
2. You miss that anything found in that folder is experimental and never guaranteed to work or boot.
-
Wonder why libreelec doesn't have some utility to config this through interface..
because every monitor or TV panel is different so it would be fiddly as arse to script (perhaps more than doing it manually) and the number of nVidia users has been declining for years so the need to do it has also reduced.
-
Flirc should be usable with anything that outputs an IR signal. so Yes. Latest version of LE is recommended although this has nothing to do with flirc support which works the same on every release we've ever shipped (that's the wonder of flirc).
-
That is incorrect advice. The hardcoded smbclient default dialect is SMBv2, so if you set a range from SMBv1 to SMBv3 Kodi will continue to use SMBv2; it can auto-negotiate upwards to SMBv3 but not down to SMBv1. The ONLY way to use SMBv1 is to set both min/max to SMBv1.
-
Startup scripts execute /etc/samba/smb.conf unless /storage/.config/samba.conf exists, then it is used. Note that the LE samba shares have a default credential (libreelec:libreelec) so smb://user:pass@ipaddress/ authentication will be required.
-
What I'm doing wrong?
Pulse is configured for Kodi to connect and output audio via a BT speaker. You need to reconfigure pulse audio to use it the other way around and accept audio to play-back on locally connected speakers (or via the DAC card).
See https://wiki.libreelec.tv/configuration/…tooth-receiving - and note that Kodi does not dynamically switch audio routing when you connect the BT device.
-
I only use portainer to create an ubuntu container to run a bash script because it doesn't work in the Libreelec console.
Sounds like "a sledgehammer to crack a walnut" .. bash vs. ash differences can normally be worked around. What's the script?
-
Kodi can run off-screen, but not headless, unless hacks are applied to disable the requirement for video output.
See https://github.com/matthuisman/docker-kodi-headless
The main use-case for Kodi in headless mode is to manage the DB, not for no-GUI playback, and you might not agree that running an Ubuntu based container on LE via Docker is a desirable way to achieve your goal - You'd also still need to builid an LE image that includes Docker and excludes Kodi (as Kodi will not run if there is no GPU). Choose which hoops you want to jump through.
NB: The project has no intention of providing 'headless' images, but you could probably self-build an image with the same headless patches. There are instructions in the wiki for self-building standard images. There are no guides for building a headless image. So it's one of those tasks that will require some initiative. I generally hold the view that people with the skills to do that kind of thing generally don't ask questios on how to do it, they just get on with it. And those that need to ask for help and intructions, normally don't succeed.
-
