Posts by chewitt

If you run "dmesg | paste" and share the URL, we should be able to see the BT firmware that's missing.

Err, yes.

LibreELEC.tv/linux.arm.conf at libreelec-8.0 · LibreELEC/LibreELEC.tv · GitHub

config for the driver is enabled in the kernel, so I would guess the answer is yes.

Share a kodi debug log and a sample of one of the problem files (30 second or so is enough).

Restore bootsector.img to the card; this nukes any previous formatting and should leave the card in a state where Windows (or any other OS) can format the card again.

Most devices probably work (or support can be added easily) but unless you tell us the actual chipset used by the card it's not possible to provide a definitive answer.

I'm not interested in Addons27.db as it's just a truncated zero byte file. I'm interested in the previous DB, e.g. Addons20.db if you were running Jarvis. Upload the file somewhere and share please.

Take backups using the OE settings add-on and move them off-box for safe keeping. Then use the LE .tar file to update the OE installs. After updating do a hard reset from inside the LE settings add-on to have a "clean install" to work from. The LE/OE backup files are just standard tar archives so it's simple to unpack them and stop kodi.service before selectively moving essential files back to the right places and restarting kodi.service.

Install the system-tools add-on and use hd-idle

kodi: bumps to binary-addons by chewitt · Pull Request #1559 · LibreELEC/LibreELEC.tv · GitHub <= will get merged/built/pushed in the next day or so

Building LE images in that frankenstein Windows/bash environment is not supported; meaning nobody on staff does this and nobody on staff has ever been interested in figuring out how to make it work. We're not aware that anyone has ever seriously evaluated whether it can work?

However, if you run Ubuntu 16.04 in Hyper-V all your random build errors will magically go away

Staff here will not provide support to people with that repo on their system. No matter which add-on you downloaded from that site and whether it was a weeny little util app or pirate stream crapware. You can debate it to yourself all you like. It's a point of principle.

NB: I typed "hd-idle libreelec" into Google and was unsurprised to see links to content in our GitHub repo as the first link.

projects/Generic/filesystem/lib/firmware/myfirmware.dat <= will add a specific file to a specific folder in the image

Honestly no idea. I'm using iPlayer daily on an S905 box (WP2, so an official build not community stuff) and have never seen anything like this.

Debug log would be nice to see.

If you restore bootsector.img to the USB using our writer app (or any other) then Windows will be able to see and reformat the whole USB drive again.

calibrate the screen?

14:11:58.766 T:139659820879168 NOTICE: ADDONS: Using repository superrepo.kodi.krypton.all

Line 196 in your log file means your problem is not our problem.

Community builds are more bleeding edge and experimental (although curated by competent experimenters) and improvements to straighten things out are achieved by a "two steps forwards, one step backwards" trial and error process. As issues are discovered/fixed/proven, changes are committed back to the common codebase used in official releases and we roll things up into the next maintenance release.

In the case of audio things; current community builds are playing about with a proposed PR on github. This PR is likely to be amended/reworked in the coming week or so based on newly learned things. Then follows more testing.. because we are working from a shitty (inherited) kernel codebase so we are conservative with changes; the more you change the more fugly stuff that surfaces, needing more effort.