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.allLine 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.
Prove with evidence that you are not creating so-called "builds" or wizards full of pirate add-on crapware and we will consider further help. Sadly that is the main reason why people hack Kodi apks on Android, and we have no desire to see the same scumbags adopt our distro.
GitHub - chewitt/LibreELEC.tv at leiot-8.0 has a second 'distro' option (LEIoT) to build that drops Kodi/media stuff and gives you a console-only version of LibreELEC about 75MB in size. Last time I built an image it failed on something, but it's probably minor. It needs further work to add a docker package to the image (which will bump image size); then you can pull the LinuxServer.io tvheadend container and leave it to rot hidden in a cupboard somewhere. I might blow the dust off this in the near future, but no guarantees.
Just connect a keyboard and run the USB in 'live' mode.
I split the thread because your issue has nothing to do with the other persons issue. I've re-read what you wrote 3-4 times and cannot understand what exactly you're trying to do? - initial install to an SD card or something to do with add-ons/repos?
scareyb - repeat with a different SD card, same result?
Sounds like something to be reported to Kodi devs via their forums.
C2 has an official build. Have you tried it?
Was trying to understand the relationship between the two more. Why is it there is a need for community builds?
Why do people pimp their cars? .. there's always someone that wants something different.
Unless there is something you really must have that's available in a community build, stick with official.
Raspberry Pi hardware is not the fastest out there, and it doesn't play every codec out there, but no other hardware receives anything close to the A1++ support and attention to detail that we see from the Pi Foundation staff to ensure Kodi runs great. The on-board audio is nothing special but there are a huge number of i2s DACs available, and there's no reason why the USB device you already have shouldn't be usable.
This is a desktop casting client. It will not help you to 'cast' things to the speakers/display connected to an LE/Kodi HTPC.
Kodi runs great on an RPi3 but if you install the amount of pirate add-on crapware that your log shows I would expect problems. Aside from the dubious legal status of those add-ons (and banned in this forum) they are poorly coded and frequently attempt to detect and break other 'competing' add-ons to drive user traffic to their forums where you generate adsense profits for the scum who operate the sites.
As you have discovered, the problem follows you between LE, OE, OSMC, which proves it is not an OS problem. If you purchase a NUC and reinstall the same crap it will run the crap faster, but equally crappy.