Posts by chewitt

    Raspberry Pi drivers and firmware should be used in matched combinations. BB using random kernels frequently results in mismatched combinations that result in minute but significant differences. If you have greater skills on this topic than the Pi Foundation engineers who wrote the code and advise us to avoid this; we bow in awe of your superior knowledge and pithy comments.

    If you prefer to waste another distro's time that's completely fine with us. If you decide you'd prefer to receive support here please install LE (which is very robust) and we'll look at the problem. If you run BB you are not running LE.

    Just ship a standard LE image which contains standard Kodi, and an intro email/pdf that explains how to install two add-ons. You save the need for a custom image and loads of extra effort, and the sooner you teach customers how to install their own add-ons from the Kodi repo, the sooner they are independent people who don't need you to spoon feed them.

    Kodi runs as a GLES app directly on the framebuffer, no Windowing system. I'll also caution that mono support is an endangered species because it's a major pain in the butt to cross-compile (automated builds fail regularly) and we're in the process of reconfiguring add-ons that depend on it to use .net core which is lighter and easier to work with. Once that's done the current mono add-on will be removed from our add-on repo. To add extra incentive; our current (limited) support for .net things has been tested solely with the couple of add-ons that use it, so we couldn't comment on what support there is for your unknown application.

    The general solution sequence with most Pi connectivity issues is:

    Disable wifi

    Check power supply

    Use an external dongle

    The radio hardware in RPi0/3B devices is basically the same and is renowned for being "close, but no cigar" on performance. Using an external dongle is normally the thing that gets people happy.

    connman stores 'profiles' for a connection and each profile has its own 'settings' file. You'll find them under /storage/.cache, but connman manages those files so unless you apply changes before the connman daemon is started any manual changes you make either a) don't have any effect, or b) will be wiped when connman state changes. Making changes through the GUI is the correct approach.

    The mismatch between BB kernels and our system frequently causes weird intangible problems that take an age to diagnose and magically go away when you run our kernel and our system. We have no idea if BB is the source of your issue or not, but if you insist on running BB we have sub-zero interest in investigating further - because we've wasted too much time on BB installs in the past.

    GitHub - procount/pinn: An enhanced Operating System installer for the Raspberry Pi is an enhanced/evolved version of noobs that might be worth looking at.

    1. Create a .strm file that links to the direct URL of the camera stream: Internet video and audio streams - Official Kodi Wiki and browse to the file via the Videos view then add to the favourites list.

    2. There are no camera drivers or camera apps in the OS so you cannot stream 'from' LE to YouTube (or any other service)

    3. BLE devices may not work correctly on Amlogic devices due to the older kernel. Otherwise BT devices should just work.

    4. No, because there is no Miracast or AirPlay (video) support in Kodi.

    The Kodi trademark rules require you to completely rebrand Kodi if you make any modifications to default Kodi and this includes the installation of add-ons (regardless of the source). Although it is still technically breaking the rules, the one type of add-on that nobody would complain about is a language pack add-on so the customers GUI and first-run experience is in their local language.

    I have been experiencing some issues running LibreElec on BerryBoot (bootloader). Any ideas?

    If you install the engine from a Ford Fiesta in a BMW it still looks like a BMW but it doesn't run/go like one. LE is much the same.

    Choose between:

    a) Using a native LibreELEC install so you are using OUR kernel and drivers with our core system.

    b) Using whateverthefcuk kernel BerryBoot happens to have packaged this week, with all the driver mismatches with our core system.

    If you choose B, we consider all bugs and misery to be self-inflicted and we refuse further support.

    Hopefully that clarifies our ongoing opinion of BerryBoot installs :)