Correct me if I am wrong, but should people with a S912 use the builds from [8.90.11a] LibreELEC 9.x for S912
because it is a later version?
This post title needs to be edited so that S912 is removed?
8.90.11a is not newer, versions in community builds are specific to those builds by the individual developer and not respective of where things are with LE.
hi GDPR-2
i have wetek play2 . vdr not stable in libreelec . A break occurs for channels when switching
For example, when you switch channels, it breaks the video channel, and sometimes the channel settles and then goes and after seconds returns
i need vdr stable in libreelec 9I do not like it tvheadend For the difficulty of dealing with it
Can you correct dvb-s wetek for vdr
There are old devices working without problems with vdr
The problem is with the add-on the developer needs to update it for LE9, use 8.2 until they update it or switch to TVH.
Hi Guys.
GDPR-2 , been using your excellent build specifically for Netflix addon. I upgraded from kszaq latest Krypton build by placing the .tar file and dtb.img in update folder. Everything went as planned and addons migrated with no problem.
However, I'm getting an Extendedinfo script error on every reboot. I've uninstalled the addon and reinstalled, but still getting error. It doesn't seem to affect anything, but it's an annoyance. I've Googled, but cannot find a solution.
Can anyone help?
Thanks.
The error might not be related to extendedinfo but one of the addons it depends on, if they fail to load so will extendedinfo but I can't help at all without an error log.
I'm more than happy to help anybody but without error logs I will ignore posts that do not supply one in the future, it says how to report bugs in the first post.
Announcement: Krypton builds are now discontinued.
I would personally like to say thank you as without your contributions and continued support then none of us would be here today.
He doesn't drink.
I guess that makes 2 of us as I'm boring and don't drink haha but thanks anyway.
Display MoreHeureka,
with your devel-version LibreELEC-S905.arm-9.0-devel-20180106155556-r27864-gac50f89.tar
now 3D-autoswitching works again as in kszaq's version 8.2.x !
Thanks a lot for your research and efforts to fix this!
It's a good feeling to see helpful developers around, good job!
nothing to do with me, buy afl1 a beer as he is the one responsible for the fix, I'm glad it's working again for you
It was only minor bug. 3D auto-switching is still broken.
Apologies, it's one issue I haven't had time to look into yet, I just saw the commit message and jumped to conclusions.
Hi. About 3d autoswitch maybe You can ask @sam.nazarko (osmc project developer) . He fixed it in his latest build for vero 4k (amlogic s905x) :
Thanks for the heads up, I have tried to look through the OSMC source but it is a complete patch fest that I can't make head or tails off.
Display MoreJust happened upon this page looking for an update on the progress for 9.0 (been a long time lurker)...
I'd honestly hate for development on this project (s9XX) to end because of some silly argument between developers.
He does abide by this rule adamg, even says so in his post which you seem to have ignored.
He discloses the source by publishing on git, it does not require it to be pushed. You state this in your own quote ("Or listing an offer, good for 3 years, to obtain the code.") so as long as he keeps the git available for 3 years.
Again, just want arguments to end and development to continue. Love this project, have my s905x set up as a home media system for my parents, using a router with a portable drive loaded with all their movies I ripped into .iso's. The like it, its simple enough for me to maintain, and it was cheaply done.
Mainly waiting on 9.0 for K18 push so I can get netflix on the hub and load up some classic games as well.
I have not ignored anything thank you and I have messaged kszaq to apologise if things have been misconstrued. I never stated kszaq does not publish his source if you read the thread correctly.
GPL doesn't oblige you to push the code every time you publish something, it requires you to make code available on demand. It is a courtesy that we all push our code to GitHub. I don't want to argue, it's just sometimes there's too much side work and we forget about things.
I have explained in personal conversation that I have no time to work on Leia, at least not now and I won't push anything I can't test.
Actually GPL does oblige you to push the code every time you publish something
GNU General Public License v2.0 (GPL-2.0) Explained in Plain English - TLDRLegal
Disclose Source
If you distribute this software in an executable, you must make your source code available by providing it alongside your distribution or listing an offer, good for 3 years, to obtain the code.
I'm not implying anything here before you get the wrong end of the stick and I fully understand you have a family and a life beyond LE and don't have the same time for this project any more.
It's really nice to hear personal accusations after issuing a general statement, isn't it?
There is no "upstream" for my work. There's LE master where the code was pushed by you and you stepped up to maintain it. And if you speak about your personal fork, you shouldn't expect the original author to maintain a fork.
I've already pushed all my Kodi patches upstream.
I guess forgetting once (on New Year's Eve) to push 4 commits relevant to the very popular Le Potato board hurt many people? Especially that I pushed them a few hours later.
It was not an accusation it was more of an observation because it is not the first time link. You are not the only person who develops in private forks, so it is in no way meant to be personal, it's just a pet hate of mine, I can understand you not wanting to make work public before it is final, I'm sorry if you misinterpreted this otherwise.
As for the fork it is a community fork which is in the process of being upstreamed, so I would hope you contribute further work there to benefit everybody moving forward.
There is now John Galts HDR work to upstream which is going to be mission impossible, had this been done from day 1 we would be in a much better position with LE/linux-amlogic.
Hello
Yesterday I installed TVH from repo but I found an important problem.
I can lock and watch DVB-C mux, but when I zapping to another channel from another mux, the tuner stop to receive signal. If I restart the service with systemctl restart tvheadend42.service, start to work again.
I downloaded the some version in my PC (I have got TBS tuner) and no bug is present.
Are you sure you are using the same version on your PC because the version included with this build is 4.3-843 which is still pre-release.
Actually we have Krypton builds from me and Leia builds here. I think there is acceptance to have Amlogic support in master LE branch, the thing that really requires work is getting rid of the hackfest (I'm mostly responsible for it...) as much as possible.
This is not totally true, it is only recently that collaboration has been combined recently to reduce the fragmentation and confusion as there was builds from Gendo before I started and there was also builds for S912, I have tried to communicate with all developers to collaborate together on a single source as I believe this is better for the community, more can be accomplished when we work together than when we work apart.
The above goes for you as well kszaq I would like to see some of your work being pushed upstream rather than me having to follow your changes every week, cherry pick and then push, it is very time consuming and also somewhat frustrating, even more so when you forget to push your changes at all and one of us has to poke you to remind you.
I think the main question is: Who "owns" LibreELEC? Some people already knows the answer. And because of this situation is what currently we have and see here. If this would be (more) open project than this amlogic stuff could be already in without much discussion (of course not damaging other devices). Instead we have bunch of different builds from different people. Which is very bad and totally unnecessary.
I know that recent problems are not exclusive to just Amlogic and that you have experienced issues with the iMX6 project vpeter which I'm sad to hear about, there is still issues that need to be resolved but nothing will happen overnight, the only thing we can do is try and work together and encourage FOSS standards or walk away.
I was not aware that the RPi(or any other hardware) impedes piracy, see, every day I can learn new things.
For me the s9xx are the cheapest dvb-s2 receivers I found and livetv works like a charm with kodi.
Anything can be used for piracy, it doesn't matter what we do and it is not our job to impede or prevent it, there is plenty of people who are paid for this work and to be fair I'm sure we have all dabbled in it at some point in our lives so I do not think this should even be a point for discussion, I certainly remember the good old days of recording songs off the radio onto cassette tapes so I can say I'm not innocent.
I wonder, how many of us will be using S9xx boxes in 2-3 years time, when Kodi 19 is released...
This is the point I have been trying to make within LE circles for some time, there is far too much talk on the 'future' within LE rather than talk about the here and now, my own thoughts are lets concentrate on things now and worry about what will happen in the future when we come to it.
I have been trying now for almost 2 months to get a lot of the work for S9xx upstreamed into LE for something that took me just under a week to do in a private fork, it is extremely frustrating for me and a lot of it is people being pedantic and dancing around specifics that really should not matter.
2 great examples of just some of the things I have heard that have held things up.
Do we really want to add support for a box that is mainly used for piracy...
Do we want to add support for something that Chinese companies will undoubtedly advertise as supporting
This is what I find most frustrating as views like this are contradictory to the open-source model and more in line with a business model which is one of the arguments and points I have had made recently internally. There is so much more that is not public knowledge and this only the tip of the iceberg of problems I have encountered.
Not precisely. It is quite possible that S9xx (i.e. S905, S912 and so on) will get v4l2 in mainline kernel. For now most of S905/912 pieces are already supported in mainline, the main thing that is lacking is hardware decoding support. When this happens, we will finally be able to use mainline kernel on our devices.
What will be dropped are 8726MX, S805, S802 and S812 devices as they're very unlikely to get full mainline support.
I very much doubt this will ever happen kszaq, you know what has gone on behind the scenes as much as I do so to suggest otherwise is giving false hope to users, the money from Amlogic to BayLibre has dried up and S9xx is not the core business of Amlogic, it doesn't make them any money any more and we are asking them to go back and support and pour more money into legacy products that they have already moved on from, if the numbers from chewitt are to be believed then there is not even that many people using Amlogic products when compared to the likes of the RPi.
On your comments regarding mainline... some audio work missing and all of the hardware video decoding is missing from mainline, it is not a case of 'when' this will happen it is more of a case of 'if' it will happen, I doubt BayLibre will do this work pro-bono as then Amlogic would have no reason to contribute more towards them.
GDPR-2 I'm waiting tvheadend developers to release Android build.
Then we can use Kodi for Android no matter what right?
I don't know but I would assume that if the code is pulled then no the effect would be the same on the Android version as well, I'm not 100% sure on that though.
There is nothing to worry about in the short term, none of this is on the table until Kodi M, and Kodi L is not even in beta yet.
