It's sounds like the device is EFI booting and ends up following the "run" configuration (not sure how or why.. that's the only explanation). I've observed that EFI support tends to get worse the older machines are .. maybe that's the reason.
Anyway .. what happens when you type "installer" instead of leaving it alone?
I haven't used Amlogic BSP kernel images on anything since ~November 2018 so I have no idea, sorry.
Kodi outputs progressive and interlaced media output is faked, e.g. 1080i@25 (typical PAL content) will be output as 1080p@50 (one interlaced frame per refresh, so double the number of interlaced frames). This means even if it can see 1080i in the list, it will choose 720p as the desktop resolution. I forget how things have evolved over Kodi releases, but IIRC this has been the behaviour for some time but older releases wrongly reported things so people believe they were using 1080i desktop in the past when they weren't.
It should be in Kodi v18.6 when that ships (no ETA at the moment).
Английский язык пожалуйста
The commit message is misleadingly worded. VP9 and HEVC share some common pluming which is provided by that commiit. In the same series you also have the full VP9 decoder. HEVC is still missing from the line-up. We are now in the odd situation of having the firmware that was missing a few months ago, but now the driver is absent. Previous patches that added HEVC support are not aligned to the updated firmware and recent compliance changes in APIs .. so rework is needed. Google (who is funding most of the current development) cares most about H264 and VP9 so those are being done first (annoyingly).
Kodi sucks a bit at presenting games, there is still no database to store the configuration needed for a specific game rom. In short, Emulators are just background plumbing and are not the thing you navigate from. You need to start from a game rom, then you're prompted for the Emulator to use with that rom. Then the game launches. This is where add-ons like "Internet Archive Game Launcher" are useful, because they create the searchable front-end interface to navigate from. The only games that will show up under "Home > Games" are games that are natively compiled to run on the host platorm (no emulator involved) e.g. 2048 and the Bomberman clone in our game repo.
mkdir -p /storage/.config/firmware/mediatek
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/mt7610u.bin -O /storage/.config/firmware/mediatek/mt7610u.bin
reboot^ run those commands (mind the line-wrap on wget) .. working?
"GUI at 1080p" means leave (or set) the default resolution to 1080p.
If the phone ends up with a link-local address (169.x.x.x) the iPhone will not see the connection as routable so data continues to work as normal. The hotspot feature in ConnMan (the connection manager) only allows you to set on/off and ssid/passphrase though (same as the phone hotspot which is what the feature was designed for) .. so it's not possible to set/control that.
In theory if you share a hotspot from the phone you achieve the same thing (RPi and Phone have an IP connection) but the phone remains the internet connected device. I've never tested to see whether the Phone can see the Kodi Airplay target in this mode though. Go see if that works?
To do it the lazy but more risk-prone way, you need to SSH in and run three commands:
touch /storage/.update/.nocompat
wget http://releases.libreelec.tv/LibreELEC-RPi4.arm-9.2.0.tar
rebootThis will disable the compat check (else we detect RPi4 is the wrong image for your RPi2(3) device and abort update) and then we download the RPi4 image and reboot. On reboot it will update to the RPi4 image. On reboot after updating it should fail to boot. You can now power off the RPi3 and move the SD card to the RPi4, which should boot. Remove any overclock/tuning etc. from config.txt before booting the RPi4 - it's not necessary.
If you want to play safe, make a backup first, then you can always clean install the RPi4 and restore the previous configuration.
LE settings will configure the embedded Samba "server" and Kodi settings configures the Samba "client" (smbclient). Both include the word "Samba" but are otherwise completetly unrelated.
If you find a "geekbox" remote it visually looks similar .. but that's no guarantee of it using the same IR codes. IMHO the amount of time you spend searching for and trying various conf files will be greater than the effort of manually configuring one.
The reason the SSV6051P driver works on the RK BSP kernel (and current Amlogic BSP kernels) has nothing to do with RK having better open-source compatibility. It is simply due to RK using an old kernel. I forget the exact kernel version where things break, but once you move beyond Linux 4.11 or 4.12 there are major crypto API changes and the driver no longer compiles. If you're lucky RK might task one of their internal devs to rewrite it at some point, but IMHO that's a long shot.
Support for "SMB browsing" only exists in the SMB1 (NT1) protocol which is now deprecated almost everywhere due to the huge number of security issues it contains. There is no native support for browsing in SMB2 or higher, it's not part of the protocol, you have to use an entirely new discovery protocol (ONVIF). "under the hood" Kodi uses the Samba smbclient which does not include ONVIF support, so once you start using SMB2 or SMB3 (the default in Kodi v17 and up and all current versions of Windows) there is no support for browsing. If browsing is essential, i.e. you're not capable of learning an alternative way of doing things, you must downgrade all your 'server' devices to SMB1 and then force both min/max SMB protocol support in the Kodi SMB client to SMB1. Then everything speaks SMB1 which supports browsing. If you choose the sensible option and keep your devices on SMB2 you just need to configure things properly (once, in sources.xml) and that should be it. As a rule anything you serve media from should be on a static address (via DHCP reservation in the router is easiest) and then you can configure sources using an IP or a hostname. As long as something on the network is a master browser the names should resolve. At least, that's my personal experience. I set sources.xml once ~8 years ago pointing at a device called MEDIABOX and haven't changed it since (the box has changed, but the share names remained the same, so no reason to change clients).
If the script dumped things in the configured locations /storage/.config/argononed.conf will contain something like:
55=10
60=55
65=100
Left value is temp in ºC and right value is percentage of fan speed. So change values as you like and then reboot or restart the argononed systemd service, e.g. "systemctl restart argononed.service" to effect the change.
Then rejoice that fans in cases are totally unnecessary (and suck for HTPC devices) and put it back to normal so you can't hear it.
I just picked up one of these remote for my Coreelec box but i am unable to remap two of the buttons.
CE is 95% our codebase, but we don't bother to track what they leave out, or what special "fixes" are in-place that might break anything. So the best place to ask for support on their releases is their forum. Thanks.
