Video driver is broken for S912 (Yoka KB2 3/32, both q200 and q201 dtbs): video glitches, decoding errors and freezing.
UI deadlocks randomly too.
In terms of technical value, your FEEDBACK is a bit like "my car drives funny, it has rattles and squeaks" 
LE is multi-user in the sense that there are some internal accounts/groups for OS services, but really everything intentionally runs as root and trying to change that based on an understanding of how a conventional distro works (hint: we are not a conventional distro) falls under the "pushing water uphill" category of efforts. I'd advise settling for root login with SSH key auth, which is as simple as pushing your private keys to the required places under /storage/.ssh/ and then enabling "disable password authentication" in LE settings.
Logs please. We suck at ESP.
That sounds awesome! I have an 9.2. Installed to internal On my play 2. Any chance there will be a chance to upgrade it?
The changes are in the nightly files now *but* like all LE10+ images it requries clean-install, there is no upgrade. To use the upstream u-boot on the box you need to first boot from the 'box' image then use emmctool to erase emmc (removing all traces of vendor u-boot) and then write the -wetek-play2.img.gz file to emmc. I strongly suggest you experiment with the 'box' image first before doing that, as while the LE11 codebase is quite usable on S905/S905X/S912 devices now, it's not as feature complete as the legacy one. If people do this and then want to go back, I do have a raw disk copy of the factory Android image on emmc which can be restored.
In the absense of a boot log to show what the system is doing I have no clue and CvH will be the same. Neither of us are mind readers.
I've not tried that, and I don't know how it would work out, but I do know there are no controls to select which WiFi interface on the host is used for a tether. That's because ConnMan was originally designed for mobile phones where there is only ever one interface for each technology, so the controls are intentionally simple.
Official:Forum rules/Banned add-ons - Official Kodi Wiki
TL/DR; we are delighted that there is one less working pirate install out there.
Make sure the filename has a .config extension or it won't be detected.
For x86_64 devices, yes. For ARM devices, no. There is a long-term effort to add a browser to Kodi, but it's a one-man long-term effort and the one man has a busy day-job and it's a non-trivial task, so progress is rather slow.
Kodi will cache to /storage/.kodi/temp *BUT* unless your network is broken Kodi does not need to deviate from default settings; and if the network *is* broken the correct solution is fixing the network, not crippling Kodi with weird cache changes.
There are techniques for inserting local modules in LE, but since the modules you need MUST be compiled for the exact major.minor kernel version that we are using the chances of you being able to grab something from another distro are low. It will be easier to compile your own image with the right options set.
Would this be the only Odroid device, that LE would support ? (I currently use CE on a C4)
Newer Amlogic hardware like C4/HC4/N2/N2+ is currently better with CE, but we do support it with the upstream codebase; the problem item is hardware decoding but for users who only need 1080p support (which is more than you realise) the boards have enough CPU to software decode everything well. The upstream codebase is cleaner/lighter than the vendor one and it continues to grow users. LE also supports C2 which has been dropped by CE; again with the upstream codebase which works better on older hardware (vdec drivers work and were written for older hardware which is one reason why things don't work so well on newer hardware). It doesn't have all the features of the vendor code but it's daily driver useable.
LE needs to push RK images onto upstream u-boot, and then we can start adding newer board families again. M1 support should be relatively simple as there is good upstream activity on the RK3568 SoC now. Hopefully HK upstream the board at some point.
Kodi also supports screen "calibration" where you can move the screen borders. It's not ideal for best reproduction, but if that's the only option, it's the only option. Calibration is applied to individual resolution/refresh combinations, so perhaps only calibrate 1080p@60 so the desktop looks right and leave everything else. Video playback will overscan as e.g. [email protected] isn't calibrated, but then Kodi isn't having to manipulate (squash) the image in software, which is a good thing.
You probably need to enable CONFIG_SENSORS_NCT6775=m in the Generic kernel defconfig before lm_sensors will be able to see data. You cannot add kernel modules etc. to a running LE system as there is no package-management, but for those with a tinker mindset it's fairly simple to build a custom LE image with the changes needed. See https://wiki.libreelec.tv/development-1/build-basics .. and if adding the module works, read https://wiki.libreelec.tv/development-1/git-tutorial and send us a pull-request to enable it in the main image.
RPi4 and RPi3B+ can natively boot from the SSD drive (not SD) and I believe (fuzzy memory now, as it's been a while) that RPi3B can do the same as long as the firmware has been updated. Write the LE image to the drive then modify cmdline.txt to use /dev/sda1 and /dev/sda2 instead of the default mmcblkX device.
cd /storage/.config
cp /etc/connman/main.conf connman_main.conf
sed -i 's/TetheringTechnologies = wifi/TetheringTechnologies = wifi,ethernet/g' connman_main.conf
reboot
<ssh in again>
connmanctl tether ethernet on^ This enables Ethernet tethering. You can now connect the RPi4 to the Hotel WiFi and connect to the RPi4 using an Ethernet cable connected to a laptop. The laptop will obtain a private IP from the RPi4 to browse the Internet; which will be blocked, but you'll be prompted for access details that you can enter in the laptop browser. The Hotel WiFi then sees (and remembers) the MAC address of the RPi4, so as long as you remain a guest (or until you're forced to reauthenticate again) you can remove the laptop and use the RPi4. To remove the tether, SSH to the RPi4 and run "connmanctl tether ethernet off" - the RPi4 will be on the .1 address of whatever private subnet is used for the tether.
If no laptop, there's no way around the problem.
Test again with an 11.0 nightly..
IR power on requires the correct bl301 blob from the manufacturer when compiling u-boot. LE does not support reading remote.conf files on the SD card - that's somehing that CE built that requires their boot firmware - and that's supported in their forum, not here.