Posts by GDPR-2

    I only have a S905X M8S Pro + but the u-boot code for its bigger brother would be very similar.

    Using the MECOOL IR remote you can turn it Off / On. No idea about Suspend.

    The MINIX A2/A3 lite plug and play remote will only turn MINIX devices Off / On with its power button unless by some miracle it's Power - IR signal works with other devices as well. All other buttons on the remote work with pretty much anything you plug it into.


    Myself and GDPR-1 have both toyed with this remote, he had thoughts that the IR power on/off was actually sending an amremote compatible signal, neither of us have checked this though.

    8.90.11a,8.90.1, 8.90.1 lepotato,8.2.2.2 .....

    I'm completely confused in these images

    what other images are there libreelec?

    how do they differ and which is the most stable?

    Thank you


    All of these are community builds and not official, what that means is releases compiled by individual developers, version numbers are incremental to the changes and do not represent any official LE version.

    8.90.11a was the last release by afl1 for S912

    8.90.1 is the latest release by myself and afl1 for multiple devices

    LePotato is a device similar to Odroid C2/Khadas KVIM

    What are those changes? Could you give us an advance? In the past, they removed support for some tricky hardware, but the efforts from the community of developers behind Amlogic to merge all of this must be presented, not as signs of trickiness, but as effective support...

    I hope you change your mind and go on collaborating with the rest to fight back and make this come true! :)


    I only know what I have been told from people who are part of Team Kodi but the plan is to remove support for amcodec and the mess that is the 3.14 kernel and to only support devices which use mainline kernel and conform to v4l2 api's.

    Once this is done it will basically make it impossible to provide any releases with a newer version of Kodi, this is not happening yet but it will happen at some point in the future.

    Given that Amlogic devices do not conform to the above and it is unlikely that they will, it basically means we are working with devices with a limited lifespan in terms of Kodi support.

    It would take me far too long to explain the full details of absolutely everything but it appears S912 may survive, S905 and S905X there is uncertainty and S8XX will be guaranteed to be dropped.

    I do not believe there is anything we as developers or you as end-users can do to sway Team Kodi's mind, they are trying to force change in the industry and personally I believe they are making the right decision, Google is doing the same in regards to Android OEMs as well.

    I appreciate everyones kind comments, it means a lot.

    I've just had a productive conversation on the phone with chewitt for more than 2 hours, I need to reflect on what was discussed as this is not something either of us wanted.

    There is a team meeting tonight where many issues will be discussed with Amlogic builds being one of them, I can understand and acknowledge where the issues lie with Amlogic and that its a technical debate not meant for the forums.

    There was acknowledgement that some problems exist so hopefully during the debate some agreements can be made, I'm still unsure on how to move forward presently though but I'm more hopeful now than I was before, the main sticking point is that Team Kodi plan to introduce changes in Kodi v19 possibly that would remove all of the current hacks and workarounds that make Amlogic work at present and therefore will make Amlogic devices incompatible with LE/Kodi in the future.

    I have argued in the past that these devices can and should be supported until those changes are made, maybe not so much in an official capacity but I see no harm in adding the code directly to the LE base and then making community builds and this is the main sticking point, in adding support for a set of devices that potentially *may* to be removed, this is where much of the fights have been fought around.

    Adding support in a personal fork for Amlogic devices has irked some developers as they see it as an attempt to fork LE in the same way LE did to OE which I can categorically state it is not, it was created mainly so Amlogic developers could collaborate together on community builds.

    As GDPR-1 has pointed out, support has existed for Amlogic devices for some time with community LE builds, but nobody has taken the time to upstream this directly to LE, I have taken a lot of heat for this from other developers and this is something was has been a huge burden and has taken a heavy toll on me, every contribution has been a fight rather than a thank you, I am in no way blaming anybody for this as I undertook this task on my own reconnaissance with no input from anybody, the heat received and what I deemed to be a lack of support from more senior LE developers is ultimately what has led to this point today.

    At the end of the day I don't have the time or the desire to fight with anybody, I don't need the stress or hassle in my life when at the end of the day all I am trying to do is help the community, I hope things can get better and that from the ashes of this that there will be a positive outcome, for now the dust needs to settle and I would ask that people try not to inflame tensions any further.

    Thanks,

    Adam

    I'm sorry to inform everybody but I will no longer be contributing to LibreELEC or these forums.

    I have been trying for a number of weeks to add support for Amlogic devices to LibreELEC but at every step of the way I have been met with resistance, poor attitudes and even out right refusal to support these devices and never once a thank you.

    There is technical reasons some would argue for some of this but I believe this to just be an excuse for other reasons as these builds have shown just how well LE runs on our devices.

    There is more of a willingness to support products people do not use anyore (x86) and old products (Raspberry Pi) rather than products that are new and rising in popularity.

    LibreELEC is not a project that I consider to be free and open-source and is somewhat reminicient of problems experienced with OpenELEC, it is tightly controlled in the vision of a select few and allows for sponsorship from vendors to impede development.

    I started contributing to LE with the interests of the community at heart, you guys where my priority as without you guys LE would not exist, it has not all been negative, however I find myself not wanting to carry on any longer.

    I had created a community github repository specifically for Amlogic devices out of my frustrations with the lack of willingness to support Amlogic devices and invited a number of developers who had collaborated with me to join this and it has worked great, there has been even more development with Amlogic than there has been in some time, however... some within LE took a dim view of this for reasons I just can not fathom with some even going as far as calling me a 'dick', if the core of LE was not as broken as it is then I would never had needed to do this.

    I had refrained from airing my distaste in public until now and had hoped to carry on working with the community rather than officially with LE but with the removal of my 'Developer' tag on these forums it is just another sign of just how bad things are with LE and is the last straw for me.

    I would like to thank the following people for supporting me afl1  kszaq  GDPR-1

    I ve been eyeing the Minix U9-H for some time now but its way more expensive than M8S Pro L. To be honest are there any real differences in these 2 boxes?

    Don't quote me on this because I will probably get shot, but I believe the price difference is partly due to the fact that the U9-H has licensed Play Ready, Widevine and Dolby Audio.

    Minix has a community that it actively engages with via forums and software updates. Minix is not your typical Chinese company.

    I was also kindly provided with a U9-H by Minix so I could bring LE9 to it :) I have to say I though I hardly use it, I have far too many devices sitting around :(

    My friend is in a different country/different ISP. I would love that the problem is me, even though it is quite difficult to make an error between copying a .tar file, rebooting the box, opening an addon an starting a stream.

    My friend has another sd card with 8.2 on it, he will have a look. Since the error is not easy to reproduce it will take a while. I really enjoy your LE 9 build so I would like to stay with it.

    It's not *my* build, it's a community build with contributions from many people I'm just hosting it :)

    I did not try it yet but what I can tell you is that I have kodi running since more than a year and only recently I saw this to happen within the last 2 months. I'm quite sure it started in LE 9 but not since the beginning of LE 9. A friend of mine reports the same issue now that I made him aware of it.

    I will try to check for LE 8.2.

    Is your friend with the same ISP as well? I'm starting to think your problem is pebkac. If 9.0 is unusable switch back to 8.2, no guarantees are given with any release. Amlogic is a mess until we get mainline kernel and v4l2 support.

    Please try the following build to see if it fixes your 3D issue link


    I'm compiling a copy of LE with the amcodec reverted which I suspect may be the issue, it will take a few hours though so I will post a link later on.

    If it's not the issue then 3d has been broken upstream in Kodi and the best person to contact would probably be peak3d as I believe he is the current maintainer for AML in Kodi.

    Can I have some of whatever your smoking?

    hi GDPR-2


    What's the problem vdr in le9 is not work setting setup searth sattelite ?

    channel.conf work but not stable While switching between channels and with oscam

    There is hope to see a stable version working without problems with your build ?

    I'm not sure, I don't have any boxes with DVB, afl1 may be able to help further

    I understand what you mean, when i build packages für my arch vdr i change the release number

    Code
    pkgrel=1

    yep that's pretty much exactly what I think we should start doing with future releases, we bump pkg_rev in the source though and it would solve all of these problems with the binary addons

    pvr.iptvsimple

    I found this in my log

    Code
    16:45:00.461 T:3999454096   ERROR: GetDirectory - Error getting
    16:45:11.075 T:4092732416   ERROR: Previous line repeats 2 times.
    16:45:11.075 T:4092732416   ERROR: Add-on 'pvr.iptvsimple' is not compatible with Kodi
    16:45:36.416 T:3988976528   ERROR: Previous line repeats 1 times.
    16:45:36.416 T:3988976528   ERROR: CAddonInstallJob[inputstream.rtmp]

    before with 8.90.0 was no problem. Online update was not possible, handmade installation from admag-addons-repo solved the problem ....

    The problem is you have a cached version located in your addons/packages directory so when you are attempting to update it Kodi will not download the newer version.

    You can force an update by refreshing the repositories, selecting the add-on and then reinstall it.

    The reason this also happens is because the add-on developer does not push a new version number each time he pushes an update, there is 2 workarounds to this, we can either include the add-on with the build or we can bump the version numbers manually each time there is an update the add-on. I will discuss both options with afl1 to decide what is best for the next release.

    I tried another dtb file, the 2Gb version did not work. I could not boot up LibreElect. I tried both 100bit and 1Gbit ethernet.

    I even tired not having a DTB file at all, boots up but still no internet connection or valid IP address.

    When I tried the 3db 1 gbit dtb file, I do get a valid IP address but does not connect to anything. I test by adding more weather providers and by connecting to my NAS but can't located. Very frustration.

    Silly question but are you renaming the dtb to dtb.img when you are trying them.

    Sorry for a noob question: When I try to install a specific addon (retroarch) a popup shows 'os.libreelec.tv not available'. How can I solve that?

    Just ignore it and press okay

    Is it easy for us to do by installing the LCDproc addons (kodi repo & libreelec repo) or does the driver need to be in the kodi build itself (or dtb)? If it's in the kodi build is it in a form of commit? Which one is it so that I ask kszaq to build a version with your commit?

    unfortunately not, it has nothing to do with lcdproc and has to be baked directly into the build and then a modified dtb has to be used, it's the fd628 driver for reference.