How helpful will this be to getting LibreELEC on allwinner android boxes?
There are already two boxes supported (Beelink X2 - H3 and Beelink GS1 - H6) and support for another one (Tanix TX6 - H6) is close to being ready. Actually, this Tanix TX6 image is known to work on other H6 boxes.
Which android box do you have in mind?
Hello. I installed a new version of Libreelec 9.80 for a single-platinum orange pc plus. When the system starts, it immediately freezes. What should I do?
Serial output would help a lot, but before you capture it, edit extlinux/extlinux.conf on FAT partition and remove last "console" argument.
Anyone has a Pine64 and can confirm the ethernet problem?
I have Pine64+, but I can test it next week at the earliest.
How can I use ffmpeg in OpenELEC build for OPI One Plus with HW h.264 decoding?
In OpenELEC, Kodi is directly talking to CedarX libraries, ffmpeg doesn't do any decoding. In LibreELEC, ffmpeg is responsible for decoding, but AFAIK only libraries are installed, no ffmpeg program.
Any idea how to solve it?
Are you sure you're using correct image? pine64 and pine64-plus are almost the same, except in ethernet configuration. There is also pine64-lts...
New H6 board has been added and it will be available with next nightly build: Beelink GS1
Orange pi lite have different power IC then Orange pi PC, and have a thermal issue. Would you add a temperature monitor on system/info?
For that out of tree patches are needed. I'll add them once they merged into mainline Linux. Latest version of patch series looks promising.
If board is in good enough shape then yes. However, I'm not sure if this board has HDMI enabled in DT. If it isn't, you have to add patch for that in projects/Allwinner/devices/H6/patches/linux
I'm not sure when AW started adding low power coprocessors. I think early SoCs don't have it, but A64 has it.
Some wake up options must be done using coprocessor, but simple ones, like power button press might be easily done already by marking it's interrupt as a wake up source in DT. If IR interrupt would be marked as a wake up source, board would be woken up even when a light in the room is turned on.
any idea if you will add support for pinetab or even pinephone?
Honestly, currently I don't have any plans to do that, as I don't consider these devices to be popular choice for LibreELEC. But now that I think a bit, they could be considered as portable movie players.
However, I don't have any of them, but if there is enough interest, something can be arranged. Maybe you can make another thread with poll to see how much interest there is?
do u know when LibreElec Repo will be available ?
I'm unable to connect using latest op3 image.
According to my info, it was build at 6th August.
For those with HDMI audio issues - multiple people works on multiple drivers which are important for that feature. Please be patient as things are finally moving forward.
I managed to build new images for H3 boards with onboard Realtek WIFI driver (RTL8189FTV). It's not so hard to fix problems with new 5.2 kernel. Thanks for jernej for you help
If someone need WIFI like me here are images for H3 boards.
Images tested only for Orange Pi plus 2E. Other should work also but not tested.
Built from LibreELEC Master Jul 19, 2019 - https://github.com/czosnekdev/lib…pdateformmaster
If you want to provide community builds with wifi enabled on regular basis, I suggest to create separate topic in this forum, otherwise your posts will get quickly lost in the sea of other posts.
hostkit Unfortunately, this won't become official and I stated reasons why many times. If RTL8189FTV/ETV gets supported in mainline kernel then I'll certainly enable the driver. There is some hope for that to happen with rtw88. According to my information, this driver will gain SDIO support some time next year. After that it will still need some RTL8189F specifics to be added...
What switches should I activate to get more info about this issue?
First of all, please tell me which codec is used. You can find this and other information by pressing "o" during playback.
However, much better information can be provided by enabling debug logging in settings and enabling video component logging. This way there will be a ton of log entries, so I suggest you try reproduce issue as quickly as possible and then stop playback. Such log might provide useful clue what's going on. But as you probably already know, everything here is still experimental.
Where can I find the file where is specified which boards are supported?
Supported boards are put into scripts/uboot_helper file.
Hi jernej, no news about lirc?
Patches are ready now, it's just that vacations started, so it will be delayed a little.
Next nightly should have working USB3 on all supported H6 boards and joydev driver enabled (for those who use gamepads).
ilchenko ^
ilchenko I get a green screen with flickering on H6, but normal video on PC, so it's a good sample. I'll take a look, but don't expect quick solutions. Last H264 issue took me half a year to solve and it turned out to be HW quirk.
Okay! No editor to cut with. I will try to install some and send the file to you
You don't need video editor (it will probably do some re-encoding, which is highly undesirable in this case), just use dd or something similar. dd command would look like:
dd if=inputvideo.m2ts of=sample.m2ts bs=1M count=50
