Posts by ilmich

    Hi all,

    a new build of libreelec 12 available.

    This release introduces major changes that will help me maintain my future builds (Libreelec and beyond) more efficiently. Unfortunately, developing for these Android boxes is difficult because there are so many variants on the market that I unfortunately don't own and can't test. Therefore, this build should be considered experimental, and I recommend testing it first on a spare SD card.

    The main changes are as follows:

    - Updated to libreelec 12.2.1
    - Mainline uboot with legacy spl/tpl
    - ALSA-based audio stack (pulseaudio completely removed and new software introduced for Bluetooth audio profiles)
    - A couple of new boxes

    A big thank to jock2 for his valuable work on armbian which is the basis for this big refactor of my codebase.

    Cheers
    Michele

    hi bilel,

    If you have stock Android on your internal memory, the only image that might work is for the A1, as you were told.
    If it doesn't work, it means you have an RK3318, which is slightly different from the RK3328. I recently received an android box with the RK3318 as a gift, which has the same problem, and I was thinking of doing an unofficial build for it (as Chewitt told you, officially supporting android boxes is a pain).

    Starting from the official LE-12.2 (latest today), I was able to port ilmich 's le12-rk322x-wip on the latest. Had to remove a couple of the RTL81xx drivers as they were not easy to compile on latest kernel, but re-enabled 8723CS so my T95d box has wifi again!

    There's probably more to tidy up, but I've aimed at maintaining all RK3xxx there (not tested).

    Attached: git diff official/libreelec-12.2 HEAD

    sydra Thanks a lot. Do you think you could make a pull request on my github repository? I've started upgrading, but it's a bit of a hassle because the kernel suddenly changed, and I had to revise a few things (with Libreelec 13 I'll have to revise a few things, because it's becoming difficult to maintain everything). Maybe we can join forces.

    Varo95 unfortunately, you're unlucky; that chip isn't well-supported. Introducing the 4.4 kernel into my builds requires a lot of work, and it's unlikely to work because Kodi uses the mainline kernel's hardware decoding support, which is different from the 4.4 kernel's. As for USB Wi-Fi devices, I've never encountered one that didn't work (almost all work with new kernels, or at least there's a driver I could include). They also work better than integrated Wi-Fi because:

    - integrated chip drivers are often soft-mac, meaning the CPU handles channel encryption, which overloads the board.
    - antennas are practically non-existent, so reception is poor.

    sergio.damian.galvan analog video output isn't implemented at the moment, and I don't know if it ever will be. The driver isn't difficult to make, but I'm personally short on free time.

    finotti It's strange, the 6051p driver is the most tested and widely used (almost all my boards have it). I need a complete log (I haven't opened it, but I think you only attached the Kodi one). You can find the information on how to do this in the first post.

    hi, 4k problem is in the start of system the image jumps and tends to green as if it were an unsupported resolution, then once kodi starts it works fine.....for the no response it was not directed directly to you I thought someone else could answer too, we all work it's just a hobby of course, thanks

    ciao,

    all 322x SoCs support 4K. Depending on the type of DDR installed (DDR2 or DDR3), you may experience performance degradation (DDR3 is faster and therefore plays 4K streams smoothly compared to DDR2). Your box is a new model for me, and while I've learned over time that the design is fundamentally similar to all boxes (the generic DTS boot 99.9% of the time), there may be some small differences. So besides trying another cable (if I'm not mistaken there are specific ones for 4k), I'd need a log (you'll find how in the first post), to know if you're using the generic DTS or one of the supported ones, and possibly a link to the original firmware (or alternatively a dump of your emmc, or even better, a dump of the first 128MB of your eMMC) so I can extract the stock firmware DTS.

    Grazie

    @matheusdanoite in your case, I need to try to figure out if there is a driver that can be used. I remember seeing something here on the forum, but I don't remember where.

    not any answer ...

    Like those working on the Libreelec project, I'm a volunteer who dedicates part of my free time to something I enjoy, and I'm not paid to do it. The project isn't dead (I recently purchased the beloved/hated HongTop H20, and some users want to donate boxes to support my work). But precisely because I dedicate my free time to it, I obviously have little of it these days/months.

    is there ANY way to write this or any other build to a NAND, without using multitool? my MXQ-4K doesnt boot it, yet it boots LibreElec without issue.

    Unfortunately, as stated in the first post, NAND is not supported because the driver found in the bsp rockchip kernel is obfuscated and does not compile with new kernels.

    Tsurugi as for the wifi, I have to port some drivers from libreelec 11. Instead, for the 4k problem, please explain better. Are you having problems with playback or with the Kodi GUI?

    So Wuk-jvi , if you want to compile a version that works, these are the generic instructions, change this script https://github.com/LibreELEC/Libr…r#L347C1-L350C9 adding the flag I indicated earlier and run the build as shown here

    But keep in mind that performance will never be the same as the original board because the RAM is slower. The problem with LibreElec is relative, but it's worth mentioning.

    chewitt the truth is that while Rockchip's upstream support is decent, for RAM management purposes, it's currently preferable to use the proprietary binary (rkbin miniloader). Libreelec supports this type of bootloader where tpl/spl are proprietary and the uboot proper upstream is used.

    I don't use this board daily. I bought it to help with support, but I solved the problem by adding that flag.

    So Wuk-jvi , if you want to compile a version that works, these are the generic instructions, change this script https://github.com/LibreELEC/Libr…r#L347C1-L350C9 adding the flag I indicated earlier and run the build as shown here

    You have the same problem as me. As described here, unfortunately a fake version of the board is being sold (I can't tell you if it's due to Radxa or the distributor). In fact, some voltage regulators are missing (I presume) and the RAM is different. Rockchip's proprietary bootloader recognizes them and in fact, from the serial port output, the clock set in the distro that works(dietpi) is 666MHz. The Libreelec bootloader (which is the upstream one) for this board sets it to 800MHz as it should be if everything were according to the official specifications.

    Unfortunately, this board doesn't work at this frequency. There's no solution at the moment, or at least the legacy bootloader should be used in Libreelec as well.

    Samui67 you can use dd to take only the first 100 MB for example like this

    dd if=unpacked.img of=first_100_mb.img bs=1M count=100

    Confirmed. The USB port on the HDMI side - if it is connected with my PC - is showing the SSD (4TB) correctly and it is read/write accessible. But it is not detected as drive in LibreELEC!

    Could you send me a dmesg of libreelec? What filesystem is the hard disk formatted with?