which ever build in use can be updated to your recent build for wp2 ?
The update should work starting from v9.0. As far as I remember, I tried it years ago.
Regardless, it is recommended to make a backup before the update.
Posts by dtech
-
-
I am currently using LE9.0.2 on my wp2, How can I update it to LTS build 9.2.8 ?
All important information is in the leading post:
Install an update package:
To install the update, you need to download, and then copy the update file (*.tar) to the Update folder via SMB, and then restart the device. The update process will start automatically after the restart. -
If Docker runs, it's a route to running a newer Tvheadend version (there is an official container these days).
Tvheadend v4.3-2180 (last updated Feb 2024) can be found in my built-in repo as binary service, so docker is actually not required.
-
I found out that my s805 only have 343mb ram detected . If my box is having 512mb ram. How much ram it supposed to detect? Is 343mb correct?
During the boot process, the kernel reserves the amount of memory required for itself and for the hardware-based functions predefined in the dtb, so you see the reduced memory displayed.
Code: dmesg
Display More[ 0.000000@0] Total memory is 510 MiB [ 0.000000@0] Reserved low memory from 0x06000000 to 0x0b9fffff, size: 90 MiB [ 0.000000@0] mesonfb0(low) : 0x06100000 - 0x07900000 ( 24 MiB) [ 0.000000@0] mesonfb1(low) : 0x07900000 - 0x07a00000 ( 1 MiB) [ 0.000000@0] deinterlace0(high) : 0x1e800000 - 0x20000000 ( 24 MiB) [ 0.000000@0] mesonstream0(high) : 0x1e000000 - 0x1e800000 ( 8 MiB) [ 0.000000@0] vdec0(low) : 0x07a00000 - 0x0ba00000 ( 64 MiB) [ 0.000000@0] ppmgr0(high) : 0x1d000000 - 0x1e000000 ( 16 MiB) ... [ 0.000000@0] Memory: 64MB 16MB 278MB = 358MB total [ 0.000000@0] Memory: 347536k/347536k available, 19056k reserved, 0K highmemI found out sometime I got 2 CPU and sometimes I got 3 CPU but never have 4 CPU running simultaneously
The CPU cores are switched on and off dynamically by the CPU govenor in the background, this has energy-saving reasons and also reduces unnecessary heat dissipation. Of course, under heavy load, all 4 cores are used.
This function is especially important in the case of the m201d, because quite a few boxes do not have a heatsink on top of the S805 SoC.
-
ok , but I thought docker didn't work with libreelec 9.2.8.14 32bits ,
if work how to install docker
thank
Docker never worked under builds based on the amlogic 3.10 kernel.
-
I apologize to everyone, I have not been active in the last period. Unfortunately, this will continue to be the case in the near future, but I will try to take the time to answer questions when my free time allows.
I'm using an S912 box with this build, and I found that some H265/1080p files (can't put the link because ©) can't be played with the hardware decoder.
I checked the demo you sent and it is a known issue with older versions that playback errors can occur with some 10-bit H.265 files on hardware accelerated playback. This affects not only the S912, but also the S905x series SoCs. Unfortunately, with the kernel v3.14, the microcode of the decoders is closed source, so these playback problems cannot be fixed in this version.
However, newer LE versions are based on the mainline kernel, which is no longer based on binary microcode from the BSP kernel.
-
Keep getting this on Amlogic S802, the PCB has "M9&M8_V1.0" on it, AIDA64 says SoC model: AMLogic Meson8 AML8726-m8, so I think it's the k200 board, I believe it uses Broadcom network chip...
This PCB is also assembled with S802 (m8) and S812 (m8m2) SoCs. However, AIDA may not accurately display this SoC. Nevertheless, it is recommended to try the k200 image, the majority of Broadcom/Ampak wifi chips work with the v3.14 kernel.
-
Here are photos of the PCB. Let me know what you find.
Sorry for the late reply, but I haven't seen one with such a memory configuration so far, so unfortunately I certainly don't have a suitable ROM for this MXQ Pro (GXBB).
-
If you can send some high quality photos of the PCB, I can try to search in my ROM repository to see if I can find a ROM that you can use to restore your box.
However, you will probably need a USB A-A cable.
-
Hi, is it possible to output 1080p video at a frequency of 120Hz?
Sorry for the late answer.
Unfortunately, 60Hz is the maximum refresh rate that these devices can provide, regardless of the resolution.
-
Hi. May be can you upload this file for MXIIIS(802) device?
Thank you
The file is still available now, it has just been moved on the server.
I have set a redirect to the current location, so the link you sent will now work.
-
My TV supports all HDR standards and I don't think it uses HDR to SDR unless it is something wrong with HDMI EDID. I don't see any setting at all about HDR in Player or System.
The S905 (GXBB) does not support HDR output at all. Maybe the HEVC hardware acceleration works with 10 bpp, but the video is displayed with an incorrect color profile. As chewitt wrote earlier...
There is no HDR to SDR conversion for UHD media in the upstream kernel.
Without it, only "washed colors" will appear when HDR content is played, and the TV will never be informed that HDR content is being played. This is a hardware limitation of this SoC, unfortunately nothing can be done about it.
-
This has already been asked by another user, and unfortunately this is still my suggestion:
If you want to use your box to run network services, then LibreELEC is not necessarily the best choice, not least because everything runs with root privileges, and the kernel is also very old.
-
Thank you for this. i was looking mxq
Okay, but since then the bluetooth also works under my LE-9.2 images. The above post is a bit outdated.
-
I still don't understand what you want to achieve with a single dtb file, but a few things are good to know:
- The 3.10 kernel cannot load external dtbs from a file, only the version integrated into the kernel, so the dtb itself is not enough.
- Android (factory) and LE/Armbian (universal) dtbs are not the same, the latter almost always lack the static partition table.
- The dtb you are looking for only says that it is for a device equipped with an S812 SoC and 1GB of RAM. There are quite a few such boxes.
You should get the factory one, either from the manufacturer, or find someone who has the same device on a dedicated Android forum and ask them to make a raw flashdump of the box and upload it somewhere.
We here on this forum, but especially on this topic, probably won't be able to help you.
I would like to ask you that since you want to restore the factory environment, you can either open a new topic here on the forum, or inquire on an Android-specific forum. I would be very happy to help, but unfortunately I indicated before that I can't, so all your requests/questions about restoring the original state are offtopic from now on.
-
Sorry for not replying until now, I've been away from my build environment for quite a few days now, but I'll review your suggestions on what can be implemented in the next version. I would definitely like to ask for your patience for a few days.
This does not make much sense, because the dtb id will not be enough, the size of the partitions can be different per manufacturer and/or model, so it makes no sense to flash a "similar" ROM.
You should get the factory one, either from the manufacturer, or find someone who has the same device on a dedicated Android forum and ask them to make a raw flashdump of the box and upload it somewhere.
We here on this forum, but especially on this topic, probably won't be able to help you.
-
Is there a solution which can restore the partition table like this?the pic below a screenshot before brick
It's probably possible, but I don't know how, that's why I wrote this:
Unfortunately, I'm not an expert in ADB operations or Android-based tricks, I think bumerc can help you more with that.
-
how to test it? i mean how to make a single file for usb_burning_tool? or something which can fix the partitions of the NAND and i am not after latest version i am satisfied with the 4.4 kitkat which was working smooth before it was bricked
Unfortunately, I'm not an expert in ADB operations or Android-based tricks, I think bumerc can help you more with that.
Amlogic USB Burning Tool also requires a specific ROM format, but my images are not firmware/ROM images, only OS images (kernel + rootfs), so these do not contain any manufacturer-specific partitions. (Except M8S+ and WeTek images!)
