Posts by chewitt

There is nothing wrong with the app, only the untrusted signature. It seems there is no alternative to paying for the Apple developer account so the image can be signed with a trusted cert.

Drives are mounted via udevil so you would need to clone the udev rule that mounts removable drives to /storage/.config/udev.rules.d and edit it to mount them somewhere else. NB: If you have two drives with the same LABEL the second one to mount will be LABEL-1 so they will not mount to the same name. You can't control probe order (which determines mount order) so it's best to ensure they have unique names.

Remove aany changes from /storage/.kodi/.smb/user.conf and /storage/.config/samba.conf .. and on the Windows box you should be able to select Avahi/Bonjour/ZeroConf network browsing to find the LE Samba share correctly. Win10 always wants to authenticate connections so you will need to enable authentication and set the user/pass details. If that doesn't work, enable SMB client debug logging in Kodi on the Windows side and share the log.

Please try Dropbox - LibreELEC.USB-SD.Creator.macOS.dmg - Simplify your life it has tweaks that I am working on for the USB/SD app to run on Catalina which has broadly the same requirements as Big Sur. The image and app are signed, but not with an Apple-trusted cert, so you will need to visit the security settings to allow that etc.

The drive should spin down into a low-power mode automatically and you can change the params of this with "hdparm" but you cannot fully turn off the drive; unless you have "smart" power sockets that can be controlled through software.

I'd also be stunned if it had 4GB RAM, as I've never seen/heard on a P281 (S905W) device with more than 1GB.

CE is probably a better option as P281 devices are usually ultra cost-engineered (worst-spec RAM, worst-spec WiFi, 10/100 Ethernet, etc.) so you will probably need the vendor kernel for driver support.

The FIPs contain RAM timing data (acs.bin) so if this is wrong the box doesn't boot, which is not impossible to recover from but needs you to short emmc pins to prevent [wrong] vendor u-boot from being found/used. If I want to experiment I will take a backup of emmc then zero emmc. The box will then boot the experimental signed u-boot from USB/SD card, and worst case if nothing works I can put vendor u-boot on an SD/USB to recover the system. If you can get u-boot sources it's simple to extract the FIPs. Alternatively, if they will not share the sources, please loop me into an email conversation with the developers and I can explain which files I want.

Do you see the same behaviour in the LE10 beta?

Please fork u-boot on GitHub and push changes. It is sometimes hard to follow your descriptions (lots of enthusiasm, but light on technical detail) so commits in a branch are always good to review

I moved your post - please do not hijack random threads.

It probably needs changes in the greeksubs add-on to handle redirection to sites with self-signed certificates, i.e. accept them.

Settings > Services > Control .. Did you enable the web interface?

I've not heard a high-pitched hiss before, but full-range staccato a.k.a "Machine Gun" noise is a known driver problem. I've not seen lockups from this though, so it would be good to capture "journalctl | paste" when that happens to see if there are error messages?

p.s. I'm aware of the older device-tree (original source for CE is an LE repo).

Also update to LE10b1 .. there are many changes/fixes. Maybe problem already fixed?

LE settings Add-on > Services. In Estuary skin the add-on is linked in Kodi settings. In other Skins you may only find it under Program Add-ons.

Do not add ".apps.googleusercontent.comSecret" to the info being presented. Below is an example of how a working config looks (with some random characters in the keys changed).

In /storage/.kodi/userdata/addon_data/plugin.video.youtube/settings.xml:

    <setting id="youtube.allow.dev.keys">true</setting>
    <setting id="youtube.api.config.page" default="true">false</setting>
    <setting id="youtube.api.id">955724949404-88ed74c3e6e73e8ch35t9qr15t0ab7rb</setting>
    <setting id="youtube.api.key">AIzaSyDi4CaM69OCjHDfr2GZ1WYZM3w7oMEzGsY</setting>
    <setting id="youtube.api.secret">C760ubRG-KAYR3pglQyc5m1n</setting>

In /storage/.kodi/userdata/addon_data/plugin.video.youtube/

{
    "keys": {
        "developer": {},
        "personal": {
            "api_key": "AIzaSyDi4CaM69OCjHDfr2GZ1WYZM3w7oMEzGsY",
            "client_id": "955724949404-88ed74c3e6e73e8ch35t9qr15t0ab7rb",
            "client_secret": "C760ubRG-KAYR3pglQyc5m1n"
        }
    }
}

First line of Log:

2019-04-11 16:28:40.923 T:3012019536 NOTICE: Starting Kodi (18.9 (18.9.0) Git:leia_pi4_18.9-Leia). Platform: Linux ARM 32-bit

Last line of Log:

2019-04-11 16:42:38.308 T:3012019536 NOTICE: XBApplicationEx: application stopped!

RPi has no RTC chip. If network does not provide NTP correctly dateTime starts from GCC release date. If this happens system dateTime is before start date for TLS certificate in Kodi repository and (on your system) certifcate not valid so Kodi cannot connect to repo.

Something is wrong with NTP process in your environment. We cannot see problem from Kodi log, need system log.

Share URL from "journalctl | paste" or "journalctl -b 0 --no-pager > /storage/log.txt" and copy to pastebin site.

Пишите по-английски пожалуйста.