Who’s demanding anything? Did I say fix it or else? I’m offering suggestions to help fix the problem. Whether Troy or his staff want to try to fix it is up to them. They seem to take a lot of pride in what they do, and they should. So I would think they would want to fix it.
And what alternative are you referring to? The Official Kodi? I’m already using it, without any problems whatsoever on any device. Another v21 fork? There isn’t another v21 available in the Toolbox.
You do know that the reason for forks is to try/test different addons to see if they work properly with the version of Kodi being tested, v21 in this case. Do you think I’m using the fork in lieu of the Official Kodi?
Again, an error is an error. Others are having the same problem with the same fork. What is the point of testing different addons if the fork is the source of the errors. We won’t know until another is made or edited. Again, I’m not demanding anything. Just offering a suggestion. If it doesn’t bother you, well then don’t worry about it.
Again, you would think that whatever they make available for us users, they would want it to work properly, and would welcome users feedback with regards to errors, bugs, and other things. I’ve offered my suggestions on what I think may be the problem, and what might fix it.
I was snarky? “You get what you pay for.” You call that helpful? Gimme a break… And the fork is not working fine, as others have mentioned as well. I do like things to work the way they’re supposed to. I’m sure Troy and others do too. If I have to wait until v21.1 is released, then I’ll have to wait. Thanks for your reply…
Ok everyone please take a step back. Sorry I should have been reading this but as I’ve given up on Kodi I wasn’t paying attention. That and I’m dealing with a very disconcerting issue myself and that also contributed to my missing this. Now to save me time rereading all this tete et tete can someone tell me exactly what fork is not working properly and I will pass the information on to Troy. Thank you.
Ok I read this thread from top to bottom. Without irritating anyone, and not needing a rebuttal, it seems this is kinda blown out of proportion. I have sent a link to this thread to Troy and requested his expertise. I am sure he’ll have a look and hopefully a solution for the issues. Thank you for your patience everyone.
Regarding the problem with this Fork, I will have my developer leave out the extras in the next update which will be 21.1 and it will be 100% barebones as far as addons are concerned. It’s been awhile since Kodi was updated so I would guess it will be soon. If we don’t see an update soon then I will fix the current one.
I, for one, am very pleased that Troy responded positively to this thread and is going to have his dev create a completely bare bones kodi fork. I certainly hope that will remove your concerns @firestick59 and give you what you want.
Thanks Troy. I apologize for all the drama. What first started as a simple observation, request, and suggestion, descended into Kaos (sorry about that chief!). As I mentioned earlier in the thread, it may/may not be the addons causing the problem. The fork is acting exactly like the beta v21 prior to it going final, and after it went final, the errors went away.
That’s why I was asking if the fork may or may not have been made by a beta v21 by accident. Again, I’m not accusing anybody of anything, but we’re all human and “stuff” happens. That may/may not be what happened, but something to check before the next fork is made.
As I said earlier as well, this site has been an invaluable resource for help, advice, and information. I’ve learned a lot along the way. Many other users come here for the same. I’m just trying to determine what the problem is, and am offering suggestions to help solve it. Again, sorry for all the drama. As always, thank you for all you do!
