Posts by jim_p

Here is the short story of how I got it with le 11, i.e. omitting the failed parts and the obvious ones like "I copied the dtb file".

Prepare sd card with ce 9.2.x because your images did not support s905 at that time > boot to android (4.4 I think) > sideload terminal app > launch terminal app > su to get root > reboot update > insert sd > boot to ce from the sd > ssh to it > installtointernal > android gone > (fast forward to 2023) > prepare sd with le 11 > ssh to ce > reboot update > insert sd > boot to le 11 on the sd > bootloader altered so as to boot only from the sd > lose any access to internal mmc since then

Tldr version: there is nothing related to android in it since 2021 and the only workaround to boot from the sd without the reset button was to run reboot update in a terminal.

Statements like this make me regret trying le 11 even more

There are 3 holes under the reset button. 2 of them connect to each other via that copper "line", so I soldered the button between the remaining one and one of those 2. I don't know anything else. And the reset button was supposed to solve all that compatibility mess.

How can I install your s905 image on an mxq pro 4k that already has the latest development version of le 12 and boots ONLY from its sd slot and with a specific sd card?

Preface: ~9 months ago I installed le 11 on an sd card, completely unaware that after that the tvbox will boot ONLY from it and never from its internal storage. If you want more info, there is a thread I started for that.

And since chewitt no longer creates images for le 11, I updated it to the development ones of le 12, which are available from the same testing folder of his.

Last but not least, the tvbox now has a reset button, but it does not seem to do much.

So, I downloaded the s905 image for it, flashed it to a 16gb sd card with rufus, deleted dtb.img and replaced it with the proper one from the device trees folder (there is actually a file named mxq_pro_4k), inserted the sd card, pressed the reset button, powered it on and... nothing showed up except the amlogic logo with the tiger. What else can I do?

Thank you

May I now ask were is the mesa-demos package?

Really sorry for spamming this thread, but it is the most relevant one for what I want to ask.

On le 10 generic x64, which package contains glxinfo? It was on virtual.multimedia-tools on le 9, but now I can't find it.

I want glxinfo's output to check which mesa version le 10 is using. The same applies for le 11, although I want to find the answer for le 10 first.

I am interested in 2 things for each version: the kernel it uses (uname -r) and its mesa version (some line in glxinfo -B).

I got a reset button in the tvbox! And it cost me more than it should.

I do not have the tvbox in my hands yet, but the technician (who took the photo) said it does nothing when pushing it, it just stays on the amlogic logo with the tiger and nothing more. In fact, he said it did the same just by short-wiring the contacts there, thus a button would be pointless, but I told him to install it anyway.

And that is why I asked on dtech's thread about what it should do. So, what do I do now?

Honest noob question. It has to do with the all black s805 mxq that has le installed to its internal rom.

What would/should happen if I do the toothpick method without having an sd/usb plugged in? In plain english, Just insert the toothpick in the av port, click the reset button inside it and plug the power supply in the wall outlet.

Answering on a similar fashion to your answers, although I agree on all three.

- In case something happens or if I want to make a fresh install e.g. on usb and boot from there, can I reinstall the patched image with which the wifi works? No. Please note that I asked if I can boot from usb with the current status on my thread earlier today but got no answer.

- 11.0.3 updates iwd and connman. Last summer (from late May to early September 2022 actually), I tested and updated through every single nightly of le 11 on my rpi3b+. The one thing that made me give up was the inconsistency on the wireless's behavior (connectivity mostly), which continued all the way to 11.0.2. To be fair, I borrowed an rpi3b+ from a friend on late April (of 2023) and tested it again, but the issues were still there, so it was not a hw issue on my end.

Sadly, that thing was also present (in a different form, but still related to connectivity) on my hw with the nightlies of x64, which I tested for ~1 month before also giving up and it was also present up until 11.0.2 too. Tbh, that iwd + connman combination was the buggiest thing of le 11 and I keep my fingers crossed that it is fixed now on 11.0.3, because I tested it 1-2 times and it worked with no issues.

On the other hand, the... "way"* of the patched amlgx image discouraged me from testing if its wifi had similar issues. If there is an issue with that too, will I get the update that fixes it? No.

- Likewise, will it get updates for the dozens of packages that 11.0.3 updates to their new versions, e.g... kodi at 20.2? Also no.

So yea, it is a big deal for me, sorry.

* "Way" = having to use a patched image file to get wireless working, because it does not work with the stock one.

---edit

I spoke too soon for the underlined part, it still has the same issue. Goodbye le 11 on x64 as well, see you in le 12.

Sorry for reopening the thread 5+ months later, but I had more important stuff to do outside of le. Since there will be no unofficial images for amlgx in the near future, on which I had to rely for its wifi, time to move on.

First and foremost, my stupid neighbor kept the tvbox for almost 1 month before me asking when will it be ready. He said he did not and will not fix it because he does not like me cursing/swearing (not at him, cursing/swearing in general)! Sadly, I did not find another technician to do it since then, so it still has no reset button.

No reset button = no way to make it boot from its emmc. A workaround to boot it to recovery by having an empty update.zip file in the root of the sd (found on xda) does not seem to work with the new booting procedure. At this point, I thought that I'd rather use that small sd for something else and make the tvbox boot from usb. Is that possible? These are my last attempts to make it work with le 11, because the time I have wasted on this I would rather spend it on dtech's build of le 9 for s905 or lakka or emuelec.

Great (sad and angry emoji here). Thank you for removing the ones for amlgx but leaving the pre-alpha quality ones for amlmx...

This means that on my s905 box I am stuck with a system that can only connect via ethernet, because that is what works with the official image.

Will there be new images for 11.0.3 at http://chewitt.libreelec.tv/testing?
Please note that the ones in there are not actually of 11.0.2 as mentioned in their names, but simply post-11.0.1 ones.

Understandable

If I try booting it with the generic amlgx image, like I did for my old s905 tvbox, what side effects may I encounter? Or what can I check if it boots properly?

In case it does not have a reset button, I really do not want to make it boot ONLY from the sd card, like I accidentaly did for mine.

Quote from dtech

I revoked the first release (20220716) and released a new image (20220718) for S805 and S8X2 devices only. But the main version is not changed, it is still v9.2.8.10. (The release date is checked for the automatic update, not the major version number.

I assume you mean 2023 at the dates there... Anyway, I just saw the new images on github. I am off to update.

---edit

And mdns works again! Thank you for the quick fix.

So the 9.2.8.10 is the fixed image? Or a newer one is on the way?

Also, le-aml has automatic updates? What do I use then as custom url under the update settings?

In early June I was trying to teach my friend how to update it manually by downloading the right file and transfering it to the box...

Any chance of getting le 11 to work on this s912 device?
https://www.amazon.com/Ocamo-Android-…/dp/B07F27RC8H/

I will get one in my hands next week probably.

Quote from dtech

Now we just need to find out under which version it broke because the avahi-daemon won't start under any of my v3.10 boxes.

(However, it is flawless under all v3.14 devices.)

But if I start the daemon with the --no-drop-root argument, it works fine.

Does this mean it's a known issue? Do you want me to check something on my end too?

I will return the tvbox to the family tomorrow morning

Maintenance day today for the mxq, after spending ~2 years at kids' hands. And some stuff I learned.

Little Faye complained on Friday that it no longer plays youtube. Not only it could not connect to the home's wifi, the wifi interface was not even available as an option to enable/disable under libreelec settings! Its free space was a bit less than 1`mb, which is odd because "all I have ever put in the tvbox are some photos of flamengos" (she actually said that!), and they were about ~10mb in total.

Where did all the space go? In thumbnails! The ~/.kodi/userdata/Thumbnails folder was ~4GB and, according to texturecache P, 99% of them were thumbnails from youtube videos, probably tens of thousands of them! I assume that the tvbox has slow emmc, because it had deleted less than 1gb of data after 1 hour! I simply stopped it, stopped kodi with systemctl stop kodi and deleted the folders in there one by one.

Moreover, I noticed that htop showed only 2 available cpu cores! Is that true? The first one was at ~60% usage all the time and the second one was below 10% all the time. Its temperature though was at 70+C! That is inside an air conditioned room at 28C, because it is afternoon here and everything outside my window is "burning" at 35C!

So, I cleaned everything up, did the upgrade to .10 that was released yesterday and so far the mdns does not seem to work and I use the full up to ssh to it.

So, I tried the ova file for the generic x64 non-legacy. It has the same issue with the partition resizing, but the update function works properly, Then I tried the ova file for le 10, which has neither of the 2 forementioned issues and it just worked properly on first try.