mkdir -p /storage/.config/firmware/rtl_bt
echo "55ab 2387 0000 " > /storage/.config/firmware/rtl_bt/rtl8761a_config.bin
rebootThe "firmware" file is just a text file in the vendor driver package, so ^ should create it with the same content. No guarantee it works, but.. no harm in trying..
[ 60.143680] Bluetooth: Core ver 2.22
[ 60.143693] NET: Registered protocol family 31
[ 60.143694] Bluetooth: HCI device and connection manager initialized
[ 60.143698] Bluetooth: HCI socket layer initialized
[ 60.143699] Bluetooth: L2CAP socket layer initialized
[ 60.143702] Bluetooth: SCO socket layer initialized
[ 60.148528] usbcore: registered new interface driver btusb
[ 60.158058] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 60.159228] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 60.159230] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8761a_fw.bin
[ 60.159952] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8761a_config.bin
[ 60.159968] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761a_config.bin failed with error -2
[ 60.159973] Bluetooth: hci0: RTL: cfg_sz -2, total sz 20204
[ 60.183360] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 60.183362] Bluetooth: BNEP filters: protocol multicast
[ 60.183366] Bluetooth: BNEP socket layer initialized
[ 62.428020] Bluetooth: hci0: command 0xfc20 tx timeout
[ 70.321349] Bluetooth: hci0: RTL: download fw command failed (-110)^ looks like rtl8761a_fw.bin exists but rtl8761a_config.bin is missing .. although I don't see it in the upstream linux-firmware repo:
I'm not sure what the story is .. but should give you something to go looking for. If you can find the firmware file, put it in /storage/.config/firmware/rtl_bt/ and reboot and it will be overlayed onto /usr/lib/firmware/rtl_bt where it needs to be.
Cache settings can smooth out the ebbs/flows of a wireless connection where you get sudden drops in bandwidth, because buffering more data helps paper over the gap when it happens (and then normal throughput resumes). However it can *never* solve the more fundamental problem of there not being enough bandwidth for a sustained large file transfer. In fact, since you force it to queue more data before play start, if you saturate the link and the supply of data cannot keep up, you will also wait longer for it to resume because we need to buffer into a larger cache. Users always add cache and this negatively impacts the problem, ergo reducing the cache size might improve it, albeit there's a razor thin margin involved. All connections fluctuate a little, so a little cache always helps, and by default Kodi uses a little cache.
TL/DR; If the network can't keep up the solution is always to fix the network not fiddle with cache settings.
You can also use LE10 nightly images and the "tubed" add-on which does not require API keys.
You cannot add drviers yourself, they need to be baked into the image. Start with sharing the "dmesg | paste" and "lsusb | paste" output so we can see what the Linux kernel does (or doesn't do) with the device and how the device identifies itself.
I suspect you need to edit Chrome settings and tell Chrome where to find some fonts that support Chinese charaters. I'd guess that by default it probably uses a minimal font that only has support for "Western" characters. I'm fairly sure Chrome uses its own fonts not the Kodi fonts (hence the difference).
Use the "Bluetooth Audio Switcher" add-on in the LE add-on repo.
It is not possible to prevent the OSD popup on change as this is core behaviour in Kodi and there is no configuation option to prevent it. However you could clone/rename and modify the skin files to show a popup that displays nothing on-screen.
In our opinion this is not a problem that needs to be fixed. In addition, the LE10 change to GBM/V4L2 mean that RPi0/1 are no longer on our list of official target hardware which further weakens the argument for adding complexity to support their use-case.
Привет. Форум на английском языке. Пишите на русском и английском языках (гугл переводчик).
I've not read the backlog on this thread (so not paying attention to deails) but this is Argon related: [script.service.argonforty-device] 0.0.1 by ArgonForty · Pull Request #1830 · xbmc/repo-scripts · GitHub
I have mine installed on my laptop connected to my 50in tv but its not displaying right .. so you guys created an OS for Kodi that is primarily used to view movies and tv shows but you didn't think to have it detect automatically external tvs connected by HDMI?
LE is focussed on HTPC devices with a single active video output so there is no need for all the overhead of multi-screen management or auto-detect as you'd find (and need) in a Desktop oriented distro. Laptops can run LE but they are not and never have been (even in OE days) a target device for support. If another distro works better for you than LE, use it, whatever works for you works for us.
There is no issue with gaming on LibreELEC, it's a supported (within reasonable hardware limits) Kodi feature and quite popular; if a little complicated to setup until you understand the moving parts. LE is using libretro emulators and emphasis is on "retro" which typically means pre-internet gaming so there probably aren't many online multiplayer ROMs around and research for that is probably easier done in gaming oriented forums where users are more familiar with ROM/emultator capabilities.
Nightlies (for now)
Team call didn't happen yet .. soon insh'allah 
On the interenet everything is legal somewhere and illegal somewhere else. ...stream is primarily used for piracy and is thus against our (and Kodi) forum rules (our forum, our rules, nothing to do with legality). Show us a clean system and support can continue.
It should work, but if there are any problems nobody around here really remembers anything about that box now.
Rename /storage/.config/system.d/openvpn.service.sample to /storage/.config/system.d/openvpn.service and read the file for further instructions on how to setup a boot-time OpenVPN service.
