TROYPOINT Kodi 21.1 Fork Now Available

The new Kodi 21.1 Fork is now available through the TROYPOINT Toolbox.

Due to many requests, we’ve removed the Input Stream Helper addon in this fork as it was causing some conflicts with some addons.

This fork is bare-bones Kodi 21.1 except for the TROYPOINT splash screen, icons, and unknown sources is turned on by default. Due to legal requirements by Kodi, we can’t use their logos in forks that we create.

Have fun!

3 Likes

Hello Troy et al…

Wow, that was fast! I hate to say it, but the v21.1 fork has the same errors as the previous v21 fork. I also get the “playback failed” error when setting the “views” options in Fen Light. After selecting the desired view, the busy icon spins endlessly. Pressing the back button on the remote then displays the “playback failed” error, when there is no playback of any video happening at all.

I tried to re-download the v21.1 fork again from the Toolbox, but the link for the v21.1 fork doesn’t connect. In fact, none of the fork links connect (at least for me when I just tried them), but all the links for the “stable” Kodi versions connect with no problem.

I’ve updated my Official Kodi v21 to v21.1 (downloaded from kodi.tv) and I don’t get any errors in any of my addons installed. In fact, I installed inputstream.adaptive (as an option when installing the Crew), and again, no errors appear in any addons at all in the Official v21.1.

So, I don’t know what to tell you. Something in the forks is causing these errors, at least for me. Can someone please try again with this new version and tell me if you’re experiencing the same thing? Some may claim that since the videos play correctly (after clicking past the errors) that it doesn’t matter, but that’s not the point, right?

I’ve already expressed my thoughts about that, so I’ll leave it to Troy and his developers to see if they can come up with a solution, if so desired. Thanks again for all your hard work, it’s much appreciated!

Downloaded just fine for me, AROUND 73MBs. Unfortunately it isn’t compatible with my Pixel Tab.

Hello @firestick59 I’m seeing same problem as you. I will look further into this. Not sure what the problem is. Thanks for posting.