[UNOFFICIAL][LE12][RK3228/RK3229][box] LibreELEC builds


  • Hi. Your RAM is fine; you have 1GB of RAM in total. You might want to try the LE9.2 versions by knaerzche. If they manage to get the 2.4 GHz SV6051P Wi-Fi working, which works in LE12, it's causing problems. It's not the LE12 distribution itself, it's the motherboard that has just enough. If the knaerzche version works well for you, you can try zram with only 100MB, which might give you an extra 512MB. No more than that. Good luck, regards

    • Your RAM:
      SEC K4B2G0446C (x4)
      This code corresponds to Samsung DDR3 with this specification:
    • K4B2G0446C
    • 2G = 2 Gbit per chip
    • Typical organization: 2Gbit x16
    • Actual calculation
    • 2 Gbit = 256 MB
    • x4 chips → 256 MB × 4 = 1024 MB
  • Hi to all.

    This is an amazing work, all works for my board. IR remote and Kodi works fine...but for my purpose i'd like the Wi-Fi to work. I've reused an old SD card and that doesn't bother me, but if I have to invest in a Wi-Fi flash drive... it needs to be cheap to buy (let me know if any cheap wifi usb working for this is available)

    I already read that SV6256P only works with linux 4.4 kernel. https://github.com/paolosabatino/ssv6x5x/tree/master

    I try build it from your code ilmich changing linux kernel version on my own pc (Windows with Docker) but guess too complex for me and no 'step by step' oficial documentation :/

    I also attach photos of my board.

  • 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.

  • 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.


    Thanks for the reply. It's true, for some reason TVE@20053E00 wasn't implemented for the RK3228, but it was for the RK3288, 3328, etc. I discovered this the hard way: compiling the driver and DRM rejected me, even killing the video, because VoP@ doesn't accept it as a port for TVE@. I had to downgrade to kernel 4.4, where I'll have to recompile my applications. I had everything working in 6.6, but TVE@ was non-negotiable with my superiors. Thanks

  • 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

  • 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.

  • I wasn't sure how you guys would have liked me to contribute, so I posted here on the forum first.

    New pull request, rebased on today's official libreelec-12.2:
    PR: rk322x: port from le12 to le12.2

    Diff blob is the last commit, same as the text file that I had attached to the forum: 3bef6aa

    May need a bit more cleanup, and may contain useless changes, it was just a quick and dirty port, only spent a day trying to compile it on latest LE12.2...

  • 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

  • Hello. Thank you for your hard work, I managed to make my weird RK3229 box potentially useful compared to the hilariously bad stock Android 7.1 OS. I hope I'll be able to set up non-laggy IPTV streaming this time around. (still exploring the features)

    However, I have a problem with the video playback directly from a USB thumbstick. (Oops, just remembered I forgot to try to transfer a video to internal memory and play that, or at least to try a different USB thumbstick, but anyway.) It's just green and corrupted, but audio and subtitles work completely normally, as intended. Happens with any video file format (tried MKV and MP4, I think one of them was 8 or 10-bit, not sure), at any resolution (1920x1080 and 480p), with any HDMI cable and on any display (PC monitor and TV, both non-HDR and 1920x1080). At first I wanted to try and disable hardware acceleration, like with regular Kodi I guess, but it wasn't an option.

    Here is the log pastebin:

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
    I didn't enable component specific debugging for this one though.

    I noticed that during Linux bootup process, right after distro version, there's a line saying [FAILED] Failed to start display.service. If that is of any importance. I didn't find it in the log.

    Didn't test the Wi-Fi (SSV6X5X(SSV6XXX_SDIO)), but I use wired connection anyway, which works normally.

    My TV box is called Selenga R4. See specs under the spoilers. Board and video corruption photos attached.

    The small chip has this written on it: SV6256P TAC2136 1W231BS


    Specs from LibreELEC and Device Info HW Android app

    I hope it's all relevant.


    System memory usage: 136MB / 983MB - 14% // In the hardware list menu. Memory chip is reported by Android as Samsung K8U00M. On board photos you can see the 2G+16G sticker. Not actually 2G, yeah.

    System CPU usage: #0: 0.0% #1: 0.0% #2: 1.9% #3: 21%


    Screen resolution: 1920x1080 @ 60.00 Hz - Full screen // On Android the app reported 720x1280 resolution. Hmmm...

    Operating system: LibreELEC (ilmich): nightly-20260306-1b9970a 12.2 (kernel: Linux 6.16.12) // The stock Android 7.1 OS uses kernel 3.10.104 (guochunyan@scott-PowerEdge-R720xd) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Dec 21 02:53:09 EST 2021


    Filesystems: // "USE PMIC" on Android?

    /dev/mmcblk1p1, 192.0M out of 511.7M used, mounted on /flash

    /dev/mmcblk1p2, 27.8M out of 12.7G used, mounted on /storage


    GPU: Mali400

    OpenGL ES 2.0 Mesa 25.1.9 // On Android: 2.0-88ed5bd.

    GPU temperature: 153 F // Kinda hot?


    CPU: ARMv7 Processor rev 5 (v7l) (that's "seven-L") // RK3229. Android ABI was armeabi-v7a

    BogoMips: 59.29

    Hardware: Rockchip (Device Tree)

    Revision: 0000 // reported as r0p5 on Android

    Serial: 9257abbf42d20b75

    CPU temperature: 154 F

    CPU speed: 600 MHz


    Also has a battery for some reason? Reported by Device info HW on Android. 6700 mAh.

  • hi @GloriousShield3576 can you please share the test file?

    The small chip has this written on it: SV6256P TAC2136 1W231BS

    sadly is an unsupported wifi chip

    I noticed that during Linux bootup process, right after distro version, there's a line saying [FAILED] Failed to start display.service. If that is of any importance. I didn't find it in the log.

    It's normal, but there's no need to worry. I've added official LibreElec support for LCD displays on some boxes. When it doesn't find the hardware configured in DTS (as in your case), it gives that error.