Nothing happens when i use that command at ssh terminal, but I already have requests installed.
About that. Yes, kodi will not show the dialog box if the addon is already installed, even if it is installed and deactivated. It will just ignore the "request" to install it.
Instead of tracking down connman for errors and new messages when the rpi is not wirelessly connected, I decided to give it a static ip.
It has become really annoying to unplug and move the rpi next to the router and connect it via ethernet, because it happens roughly once every 2 days. If that has no results, I will stop using the nightly on the rpi as well
Tqdm is a python library for progress bars, nothing more.
The requests library exists as a kodi addon in the main repo, so you can just ssh the libreelec system and run
kodi-send --action="InstallAddon(script.module.requests)"A prompt will appear on kodi, as shown in the screenshot below, so you just press yes there.
The reason for the above is that, since kodi 17, search does not return results for addons of the "script.module.*" family. If it did, you could just search for it from within kodi and install it as any other addon.
It's ok. I am going hands on then, via adb. Results in a few minutes.
---edit
Sorry for the 2 hour delay. It worked. It returns the dtb file like it would do under linux.
What you are looking for is not accidentally the device-tree ID?
Codecat /proc/device-tree/amlogic-dt-id
Can this run, and return the right result, on android too?
Well, thank you too, for the script 
I will keep using the nightly on the rpi3b+ though.
There you go. I switched to estuary just for the screenshot. It is from the services submenu and the settings level is highlighted on the bottom left corner. I can't help you more than that, and probably noone else can.
Yes, I was not running 0.08 on the screenshots above, but 0.07. I said I was waiting for a new set of nightly builds so as to test 0.07 because I thought its bug on generic-legacy was fixed. It was not, so I upgraded to 0.08 once the forementioned upgrade was done.
First upgrade with 0.08 on generic-legacy was successful. Sadly, it is the end of the x64 nightlies for me today because I am tired of testing something that has iffy behavior on my hardware's wifi. I may check again when 11 reaches alpha or beta, but right now all I want to do is to open a bug report on kodi (bug that appears in 18, 19 and 20) and delete the whole thing.
This is libreelec settings, it has nothing to do with kodi settings. Choose another submenu from the settings, e.g. interface, or wait for someone that uses the estuary skin to guide you further.
I do not use it because I absolutely hate tile-styled interfaces, so I can't help you more.
Shocked!
Can I run that and boot from a usb device? Now I may try that lakka s805 image I wanted! Thank you for the info.
You were right about 0.07 and generic-legacy. Screenshots are from the x64 and the rpi3 installations. I updated them to 0.08 and I am waiting for tomorrow.
As for the mediafire link. Wget-ing it results in an html file. I named it "whatever" because the redirections that wget has to go through add my public ip to it
$ wget https://download1322.mediafire.com/7yyjs05bvw0g/xp2d64y5k06skp4/get_nightly.sh -O whatever
--2022-06-30 12:04:30-- https://download1322.mediafire.com/7yyjs05bvw0g/xp2d64y5k06skp4/get_nightly.sh
Resolving download1322.mediafire.com (download1322.mediafire.com)... 205.196.123.10
Connecting to download1322.mediafire.com (download1322.mediafire.com)|205.196.123.10|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.mediafire.com/download_repair.php?flag=4&dkey=7yyjs05bvw0&qkey=xp2d64y5k06skp4&ip=x.x.x.x [following]
--2022-06-30 12:04:31-- http://www.mediafire.com/download_repair.php?flag=4&dkey=7yyjs05bvw0&qkey=xp2d64y5k06skp4&ip=x.x.x.x
Resolving www.mediafire.com (www.mediafire.com)... 104.16.203.237, 104.16.202.237
Connecting to www.mediafire.com (www.mediafire.com)|104.16.203.237|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
--2022-06-30 12:04:31-- http://www.mediafire.com/download_repair.php?flag=4&dkey=7yyjs05bvw0&qkey=xp2d64y5k06skp4&ip=x.x.x.x
Reusing existing connection to www.mediafire.com:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘whatever’
whatever [ <=> ] 43.42K 237KB/s in 0.2s
2022-06-30 12:04:32 (237 KB/s) - ‘whatever’ saved [44457]
$ file whatever
whatever: HTML document, ASCII text, with very long lines (9111)
$ head -1 whatever
<!DOCTYPE html> <html lang="en-US" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />Having said that, I offer to add it as a gist and I (promise that I) will keep updating with every new release that you make.
It leads to the raw text version of the gist, so one can use it with wget directly.
https://gist.githubusercontent.com/pitsi/121409e48df9529feb6e8b18bd8aa303/raw/11f1bb1502e2e5506e124ef8338432ec1b82b4e8/get_nightly.sh---edit
I can now confirm that v0.08 works properly on generic-legacy. I just noticed a new image was uploaded earlier today, so I made the upgrade via the script.
Le is running from the nand.
I also learned that they occasionally use an old usb stick and that the tvbox always is connected to the power plug, so is turned on via its remote. So I asked the family to completely disconnect it from the power supply, wait a bit and then reconnect it. And it stayed on the mxq logo for less than 20 seconds.
I also noticed that, yesterday, systemd-analyze blame has kodi.service top the board with like 45-50 sec to start, way more than the wait-time-sync.service which comes second at ~10. Kodi itself though is available and operational in less time than that.
There are no devices connected to it. Just the hdmi cable and the power supply.
Does anyone use the all black s805 mxq? I did the upgrade to 9.2.8.4 today and I could not help but notice how much time the mxq logo stays on the screen while booting up. It is shown for like 1 minute! After that, le takes less than 30 seconds to boot to kodi.
Since there are no new nightlies today, because the last commit is still f7f28a7, I will keep 0.07 and test it and I will upgrade to 0.08 afterwards.
Yes, when I wrote msg 46 both installations had v0.06 of it. And yes, I am also confused about why it happens only on the generic-legacy.
I am now upgrading them to v0.07 of the script, but due to the lack of new images (both of them are on 20220627-f7f28a7), I will post any new findings tomorrow.
Thank you I will try it once I get the tvbox on my hands. However, the owner will try it himself first and may not send it to me 
Is there a procedure that must be done so as to boot it from the sd card?
Ok, let me make the question straight: can I install any of the available libreelec-aml images to it?